Anyone can promise zero-knowledge. Veridenti is built so the promise is enforced by math.
The architecture, cryptography, and compliance posture of the Veridenti platform — written for your security team to verify, and plain enough for the board to read.
Architecture
Built so we can't read it.
Every vault is encrypted on the device that owns it, with a key derived from a passphrase Veridenti never receives. What crosses the wire — and what rests in our cloud — is ciphertext. A breach of our infrastructure yields data no one can decrypt, including us.
What Veridenti never sees
- Your master passphrase — entered on-device, consumed by the KDF, never transmitted.
- Derived or vault keys — key material exists only in device memory.
- Vault plaintext — logins, notes, TOTP seeds, and custom fields are encrypted before they leave.
- Recovery shares — Shamir shares go to your designated officers, never to us.
- Browsing telemetry — no phone-home by default; posture is computed on the endpoint.
What our servers store
- Encrypted vault blobs — AES-256-GCM ciphertext, opaque to us.
- Wrapped shared-vault keys — sealed to each member's P-256 public key; only that member can unwrap.
- Org & admin events — who joined, what policy changed — in an append-only hash chain.
- Account & billing metadata — the minimum needed to run the service.
- Region-pinned at rest — data stays in its assigned region and fails closed if the pin can't be honored.
Cryptography
Boring, modern, verifiable.
No invented ciphers, no proprietary "military-grade" hand-waving. Veridenti composes well-studied primitives the way cryptographers recommend — and publishes exactly how, so your team can check the work.
Vault encryption
Every vault is sealed with AES-256-GCM — authenticated encryption, so tampered ciphertext is rejected, not silently decrypted.
AES-256-GCM · AEADKey derivation
The vault key is derived on-device from your passphrase by PBKDF2-HMAC-SHA256 (310,000 iterations), making large-scale guessing attacks prohibitively expensive. Neither the passphrase nor the key ever leaves the endpoint.
PBKDF2-SHA256 · 310k · client-side onlyShared vaults
A shared vault has one symmetric key, wrapped separately for each member using ECDH-ES over NIST P-256. The server relays wrapped keys it cannot open; removing a member removes their wrap.
ECDH-ES · P-256 · per-member key wrapAudit integrity
Every admin and org event is appended to a hash chain: each record commits to the one before it. Rewriting history breaks the chain — visibly, verifiably.
append-only · hash-chained · verifiable| Function | Primitive | Notes |
|---|---|---|
| Vault encryption | AES-256-GCM | Authenticated encryption (AEAD); integrity failures reject the payload outright. |
| Key derivation | PBKDF2-SHA256, 310k, on-device | Executed client-side; passphrase and derived key never transit the network. |
| Shared-vault key exchange | ECDH-ES, NIST P-256 | Vault key wrapped per member; revocation removes only that member's wrap. |
| Organization recovery | Shamir secret sharing, M-of-N | Quorum of customer-designated officers; Veridenti holds no share. |
| Governance boundary | Personal: org-blind · Work: customer-quorum recoverable | Personal vaults have no Org Recovery Key and are zero-knowledge to both Veridenti and the organization. Work vaults on an enrolled profile carry an ORK recoverable only by the customer's own M-of-N officer quorum — never by Veridenti. |
| Audit integrity | append-only hash chain | Each event commits to its predecessor; the chain is independently verifiable. |
| Transport | TLS 1.2+ | Defense in depth — the payload is already ciphertext before it reaches the pipe. |
Recovery
Recovery without a backdoor.
Zero-knowledge usually forces a hard trade: lose the passphrase, lose the vault — or give the vendor a master key and lose the guarantee. Veridenti splits the organization recovery key with M-of-N Shamir secret sharing across officers you designate. Any quorum can recover a locked account. No single person can. And Veridenti holds no share at all.
“A recovery system the vendor can operate alone is a backdoor with better branding. Ours requires a quorum of your own officers — and we couldn't join it if we were ordered to.”
Veridenti design principle № 2Governance
An audit log no one can quietly edit.
Every administrative action — a policy change, a member added, a vault shared, a session revoked — is appended to a hash chain. Each record commits to the one before it, so inserting, deleting, or rewriting an event breaks the chain in a way anyone can detect. Your auditors verify the math; they don't have to trust our export.
Append-only by design
Events can be added, never edited or removed. The log your auditor reads is the log that was written.
Independently verifiable
Recompute the chain from any export and compare heads. Integrity holds or it doesn't — no trust required.
Streams to your SIEM
The same events flow to Splunk or Datadog natively, and to Microsoft Sentinel or any SIEM via a generic HTTPS collector.
Compliance posture
Stated plainly, claimed carefully.
Security vendors are graded on honesty first. Here is exactly where Veridenti's compliance program stands today — what is live, what is in progress, and what is on the roadmap — with nothing rounded up.
| Item | Status | Detail |
|---|---|---|
| Zero-knowledge architectureDevice-side encryption; ciphertext-only cloud; no vendor-held keys | Live | Enforced by construction, not policy. No phone-home by default; telemetry is strictly opt-in. |
| SOC 2Independent attestation of security controls | Readiness in progress | Formal readiness program under way; Type I targeted first, with the full policy pack and control mapping in place. |
| ISO/IEC 27001Information-security management certification | Planned | On the roadmap following SOC 2; the same control set is being built to serve both. |
| Data residencyRegion-pinned storage that fails closed | Region-pinned | Global today; EU/US and per-country pinning available on Enterprise contract. If a pin can't be honored, writes fail closed — data never spills to another region. |
| DPA / BAAData-processing & business-associate agreements | At contracting | DPA and, for HIPAA-regulated customers, a BAA are in preparation and provided at contracting. |
| Breach monitoringLeaked-password & breached-domain checks | Live · on-device | Computed on the endpoint with no phone-home — exposure is flagged without your credentials ever leaving the device. |
| SSO (SAML/OIDC) + SCIMIdentity federation and automated provisioning | Live | Included on Enterprise plans (50+ seats); available as an at-cost add-on for smaller teams. |
| Tamper-evident auditHash-chained, integrity-verifiable event log | Live | Append-only chain covering all admin and org events; verifiable from any export. |
Our commitment: we publish status, not spin. When SOC 2 attestation completes, this datasheet — and the claims your procurement team relies on — will be updated the same day.
Operations
Plugs into the stack you already run.
Zero-knowledge doesn't mean zero visibility. Org-level events stream to your SIEM in real time, and data residency is enforced the only way that matters: the write fails before the pin is violated.
SIEM integration
Splunk HEC and Datadog natively; Microsoft Sentinel — and any SIEM — via a generic HTTPS collector. Events carry admin and org activity only; vault contents are never present.
Residency that fails closed
Vault data is pinned to its assigned region. If the pin can't be honored, the write is refused — it is never silently routed elsewhere. Global today; EU/US and per-country pinning on Enterprise contract.
Next step
Hand this to your security team.
Everything above is designed to survive scrutiny: primitives your cryptographers recognize, an audit chain they can recompute, and a vendor that architecturally cannot read your data. We'll answer the hard questions directly.
Security review, on your terms
Architecture Q&Asecurity@veridenti.com — direct line to the team that built it
Pilots & pricingsales@veridenti.com — Enterprise plans from 50 seats
Start todayveridenti.com — deploy in a week, not a quarter