Tenant and property isolation

Tenant and property boundaries separate guests, reservations, rooms, billing, users and operational records between clients and properties.

Role-based access

Reception, management, administration and the platform have different permissions. Libar supports MFA, recovery codes and additional checks for sensitive actions; actual MFA activation and access policies must be confirmed for users and the property.

Audit and Control of Sessions

Security and audit logs, session review and revocation, CSV exports and network allow/block rules give the team a record and a way to respond.

Data protection and life cycle

HTTPS transport, backup tools and a record of important actions form part of the technical foundation. Retention and anonymisation are supported, while periods and production activation require an approved policy and legal basis. Backup and recovery scope is confirmed by contract; a full recovery test requires a separate check.

Evidence of readiness, not certificates

Libar has documented controls and readiness evidence aligned with ISO/IEC 27001:2022, CSA CCM / CAIQ v4.1, OWASP ASVS/WSTG and GDPR-oriented practices. Formal ISO certification, a SOC 2 audit, CSA STAR registration and an independent penetration test are not complete.

Checks that exist today

Non-destructive security smoke tests, control tests, data isolation checks and E2E browser scenarios provide measurable evidence of current readiness. They do not replace a future independent penetration test or formal audit.