Encryption model & independent audits
How this is scored
What the vendor can prove about its security design: end-to-end encryption with named algorithms and key derivation, which fields are encrypted on the device and which are not, independent audits and penetration tests with published results, a bug bounty, and incident history disclosed.
0 — Vault contents are readable by the vendor by its own description: server-side encryption with keys the vendor holds, or no encryption of stored credentials.
3 — Client-side or end-to-end encryption described with the algorithms named; key derivation, audits and the scope of what is encrypted are basic or not described.
5 — A published security whitepaper or security page naming algorithms, key derivation and the client-side encryption model, and an independent audit, penetration test or certification (ISO 27001, SOC 2) named.
8 — A stated list of which fields are and are not encrypted (including URLs and metadata), recurring independent penetration tests or code audits with dates and reports or summaries published, a public bug bounty or vulnerability disclosure policy, past security incidents documented with their impact, and open-source clients or cryptography that can be reviewed.
10 — The design is verifiable end to end: full source or cryptographic design public, every field encrypted client-side including metadata, audits by named firms repeated yearly with full reports, a threat model that states what a compromise of the vendor's servers would expose, and incident post-mortems published.
The Compliance Auditor
The zero-knowledge page names AES256-GCM, RSA 2048-bit and PBKDF2-HMAC SHA256 with 100,000 iterations, states the server cannot decrypt user passwords, and names the fields encrypted client-side (passwords and TOTP secrets), with TLS hardening guidance alongside. I found no public information on independent audits, penetration tests, a certification with a published report, a bug bounty, or disclosed incidents; the homepage's compliance-standard names are not audit evidence. The pages also state the zero-knowledge layer currently reaches only the web client, with other client apps blocked from those encrypted values. 2 3 1