Encryption posture
This page states what AtmanID’s encryption guarantees and what it does not. Implementation detail is available under NDA through the Trust page.
At rest
- Everything in the database, and every uploaded file, is encrypted at rest by the hosting providers with AES-256, using provider-managed keys.
- High-risk secrets get a second, application-layer layer: connector credentials for your target systems, MFA (TOTP) secrets, inbound and outbound webhook secrets, and SIEM credentials. Each record is encrypted with AES-256-GCM under its own data key, and that data key is wrapped by a key held in a cloud key management service, which never leaves it. Newly written records are bound to their tenant, so a record copied into another tenant’s row does not decrypt; records written before that binding was introduced still decrypt without it. Decryption requires the full 16-byte GCM authentication tag, so a truncated tag is rejected.
- Passwords, MFA backup codes and API keys are stored as one-way hashes. Passwords are salted bcrypt hashes; MFA backup codes are bcrypt hashes (older codes: keyed HMAC-SHA256); API keys, which are long random values, are SHA-256 hashes, and a key is shown once. The one exception: when a new API key needs a second administrator’s approval, the approved key is held encrypted (AES-256-GCM) until the requester collects it, once, and the encrypted copy is then deleted.
In transit
- All traffic to AtmanID is HTTPS (TLS 1.2 or later; TLS 1.3 is preferred). Every response sends a two-year HSTS header, so browsers will not fall back to plain HTTP.
- Connections from AtmanID to its database, file storage, AI provider, email provider and your connected systems use TLS.
- Outbound webhooks are signed (HMAC-SHA256) so your receiver can confirm a delivery came from AtmanID and was not altered.
Key management
- Encryption keys for application-layer secrets live in a cloud key management service. Every record has its own data key, so there is no single static key in the application’s configuration for those secrets.
- A small number of lower-risk configuration values are encrypted with AES-256-GCM under a platform key held as an encrypted environment variable, rather than under per-record data keys. Older records written in that format before the move to the key management service still decrypt.
- Platform secrets — session signing, database credentials, and keys for third-party services — are held as encrypted environment variables in the hosting platform and rotated when there is a reason to: a change in who has access, a suspected exposure, or the provider’s guidance. They are not yet rotated on a fixed schedule.
- Customer-held credentials — API keys and webhook secrets — are rotated by the customer. API keys can be rotated without downtime: create a new key, move callers to it, then revoke the old one.
What is not encrypted at the application layer
These are protected by storage encryption and access control, but not by the extra application-layer layer:
- Audit records and identity data (names, emails, roles, entitlements). These have to be searchable and filterable; encrypting them in the application would prevent that.
- Configuration, such as approval workflows and policies.
What this design does not provide
- Customer-managed keys. Storage encryption uses provider-managed keys, not a key per tenant or a key you control. Customer-managed keys are on the roadmap.
- HSM-backed platform secrets. Platform secrets are held in the hosting platform’s encrypted environment variables, not a hardware security module. A compromise of the hosting account could expose them.
- Separately keyed backups. Backups are encrypted by the database provider under the same provider-managed scheme as the live database.
- FedRAMP authorization. Not held; it would require customer-managed keys and dedicated infrastructure.
Adjacent reading
- Multi-tenancy isolation — the tenant boundary inside the database
- Data residency and disaster recovery — where data lives and how it is backed up
- Compliance mapping — how these controls map to frameworks
© AtmanID · Privacy