We never hold your keys or your customers' money
Keystone Registry prepares transactions; you sign them in your own custody. Personal data stays encrypted and off chain, and the audit trail is built so no one can quietly rewrite it, including us.
Status as of . We hold no SOC 2 report or other certification today, and we say so until we do.
Controls and their status
- No customer keys or funds Built
- We never hold investor funds or customer private keys. Every enforcement transaction is prepared unsigned and signed in your own custody. The only signing key Keystone holds is its own audit-anchoring key.
- Personal data stays off chain Built
- Holder identity never goes on a blockchain; only hashes do. Identity fields are encrypted per record with AES-256-GCM under a per-tenant key, and exact-match search uses keyed blind indexes rather than plaintext.
- Tenant isolation Built
- Database row-level security keeps every customer's data separate, tested with two tenants that cannot read or write each other's rows.
- Append-only records Built
- Holder records and audit events are never updated or deleted in place; the database refuses it. Corrections are new events.
- Tamper-evident audit trail Built
- Each audit event carries the hash of the one before it, and the chain's head is anchored on the XRP Ledger. Anchoring and verification are tested on the XRPL testnet.
- Keys in AWS KMS In development
- Tenant encryption keys and the anchoring key live in AWS KMS and never leave it. The KMS signer for anchors is in development.
- Security policies In development
- Information security, access, change, vendor, incident response, continuity, retention, and Regulation S-P privacy and breach procedures are drafted and in review. They are not yet approved.
- Penetration test Planned
- An external penetration test before the first customer goes live.
- SOC 2 Planned
- We do not hold a SOC 2 report or any other certification today. A SOC 2 Type I audit is planned before general availability.
Report a security issue
Email security@keystoneprotocol.io with what you found and how to reproduce it. Please do not access other people's data or disrupt the service while testing.
Bring your security questionnaire
We walk through testnet tokens end to end with synthetic data: a holder record, a blocked transfer, a prepared freeze, a reserve coverage check, and chain verification.