top of page

How LAAVAT protects your keys

You are trusting us with the keys your devices trust
This is how your keys are stored, who can use them, and what the realistic worst case looks like.

Certified and audited

ISO 27001

ISO/IEC 27001:2022, certificate 244147 from British Assessment Bureau under UKAS accreditation. Certified since December 2022 and assessed every year.

Key storage

Keys are generated in AWS CloudHSM and never exist in plaintext outside it. Signing happens inside the HSM.

Dual control

Administrative HSM operations run under dual control, and offline key export takes a two-person ceremony.

The security model in four parts

Tenant isolation

Your application stack, database and audit data are separate from every other customer's, and the HSM itself enforces key ownership.

Access and approvals

Access follows the groups in your identity provider. Approval rules and quorum are set for your tenant, with a complete audit log.

Key custody

Export is designed in. Signing and CA keys leave only through an audited two-person ceremony, and every export is an audit event.

The realistic worst case

The main risk is unauthorised use of your keys, not extraction. Such use stays inside your tenant and is recorded in the audit log.

See it in practice

​

Pick your hardware or update tool and watch a team go from first login to a signed release, in about 90 seconds.

Have a security questionnaire?

bottom of page