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 documented model names AES-256 and FIPS 140-2 encryption of "all sensitive data such as passwords, documents and authentication options", with split encryption keys held between the customer's own web configuration and database, key rotation with published timings, and export of keys as split secrets — but no field-level statement of what is and is not encrypted. A vulnerability disclosure process with CVSS 3.1 triage is published; I found no public information on independent audits, penetration tests by named firms, or any disclosed incident history. The ISO 27001, GDPR and SOC 2 references describe the product's audit trail helping enterprises comply, not a certification of Click Studios itself. 3 4 9