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 CISO
The security page names the algorithms (AES-256, RSA-2048, FIPS 140-3 validated modules), the key derivation (PBKDF2 with 1,000,000 iterations) and states that record contents including URLs and custom fields are encrypted on the client device — exactly the field-level statement I ask a vault vendor for. Penetration testers are named (NCC Group, CyberTest) and a Bugcrowd-managed bug bounty with a public vulnerability disclosure program is documented, with ISO 27001 audited annually by accredited third-party assessors. We found no public information on published audit reports with dates, a documented incident history, or reviewable open-source clients. 5 6 12 5