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 security pages name the algorithms (AES-256 GCM, RSA-2048, Elliptic Curve with ECC-256 keys), the master-password key derivation (PBKDF2 at 1,000,000 iterations), and state that record-level keys generated on the client encrypt logins, file attachments, TOTP codes, payment information, URLs and custom fields, with FIPS 140-3 validated cryptographic modules. Independent validation is named and recurring — NCC Group and CyberTest penetration tests, a Bugcrowd bug bounty with public vulnerability disclosure, ISO 27001 audited annually and SOC 2 certification. We found no public information on published penetration-test reports or dates, past security incidents, or reviewable client source code. 3 5 6 12 5