Skip to content

Compliance mapping

This page maps AtmanID’s product controls to common frameworks, to help you place AtmanID in your own compliance programme. It describes what the product is designed to support; it is not a statement of certification. For questionnaires and documents under NDA, use the Trust page.

Attestation status

AtmanID does not yet hold a SOC 2 report, an ISO 27001 certificate, a HIPAA attestation, or any other third-party attestation. Nothing on this page should be read as one. When an attestation is obtained, it will be listed on the Trust page with its date and scope.

  • PCI DSS is out of scope: AtmanID does not store, process or transmit payment card data.
  • FedRAMP is not held and not on the near-term roadmap.
  • GDPR and CCPA: AtmanID provides features that help customers meet their obligations — erasure with audit redaction, configurable retention, export — and a data processing agreement can be put in place. Compliance with these laws depends on how each customer uses the product, so AtmanID does not describe itself as “compliant” with them.
  • HIPAA: AtmanID is not positioned for protected health information today; ask before storing any.

Product controls and where they help

Product control Supports Detail
Role-based access, checked on every request, per-tenant and live-editable SOC 2 CC6.1–CC6.3 · ISO 27001 A.5.15, A.5.18, A.8.2 · NIST CSF 2.0 PR.AA RBAC architecture
MFA, enforced per tenant by role SOC 2 CC6.1 · ISO 27001 A.8.5 · NIST CSF 2.0 PR.AA Threat model
Tenant isolation in the database SOC 2 CC6.1, C1.1 · ISO 27001 A.8.3 · NIST CSF 2.0 PR.DS Multi-tenancy isolation
Append-only, hash-chained audit log with signed checkpoints and regular verification SOC 2 CC7.2, CC4.1 · ISO 27001 A.8.15 · NIST CSF 2.0 DE.CM Audit chain integrity
Audit export to your SIEM SOC 2 CC7.2 · ISO 27001 A.8.16 · NIST CSF 2.0 DE.CM, DE.AE Audit chain integrity
Access reviews and certification campaigns SOC 2 CC6.2, CC6.3 · ISO 27001 A.5.18 · NIST CSF 2.0 PR.AA Product documentation
Joiner, mover and leaver automation with revocation SOC 2 CC6.2 · ISO 27001 A.5.16, A.5.18 · NIST CSF 2.0 PR.AA Product documentation
Separation-of-duties rules SOC 2 CC6.1 · ISO 27001 A.5.3 Product documentation
Encryption at rest and in transit; application-layer encryption for high-risk secrets SOC 2 CC6.1, CC6.7 · ISO 27001 A.8.24 · NIST CSF 2.0 PR.DS Encryption posture
Point-in-time database recovery SOC 2 A1.2 · ISO 27001 A.8.13 · NIST CSF 2.0 RC.RP Data residency + DR
Erasure with audit redaction; configurable retention SOC 2 C1.2, P4 · ISO 27001 A.8.10 · GDPR Art. 17 Audit chain integrity
Evidence packs generated from the audit log Audit fieldwork for any of the above Compliance Hub

NIST mappings use CSF 2.0, which added a Govern function and reorganised several categories from 1.1. AtmanID’s product controls sit mainly in Protect (PR.AA, PR.DS), Detect (DE.CM, DE.AE) and Recover (RC.RP).

Where the product does not yet help

  • Separate backups outside the database provider, and regional failover. See Data residency + DR.
  • Customer-managed encryption keys. See Encryption posture.
  • Masking of production data in non-production environments.
  • Customer-visible logging of operator access to production. See Threat model.
  • Cryptographic proof of deletion.
  • Data residency outside the United States.

Organisational controls

Frameworks such as SOC 2 and ISO 27001 also cover the organisation running the service — personnel security, training, incident response, vendor management and risk assessment. AtmanID is an early-stage company; these controls will be described, with evidence, as part of a future attestation, and are available for discussion under NDA in the meantime. This page covers product controls only.

Adjacent reading

© AtmanID · Privacy