Skip to content

Architecture & Security

This section is for security architects, engineering CISOs, and implementing engineers doing technical due diligence on AtmanID. The depth is implementation-level — code references, schema details, mitigation strategies, accepted risks. If you’re evaluating AtmanID for compliance posture (SOC 2, certifications, subprocessors), the Trust page on the main app is your starting point — that’s the procurement surface. This section is the engineering surface.

Different audience, different content depth, different question being answered:

Surface Audience Question
/trust (AtmanID website) Procurement, security shopping “Are you SOC 2? What subprocessors? Can we get the report?”
/architecture/ (here) Security architect, engineering CISO “How does the tenant isolation actually work? Can I review the audit chain design? What’s your threat model?”
Compliance Hub, in your tenant Customer operator “Show me MY tenant’s posture, MY audit log, MY current SoD violations.”

Both readers are sometimes the same human at different funnel positions — a CISO doing pre-purchase evaluation today and post-purchase architecture review next month. The two surfaces complement each other; don’t conflate them.

What’s in this section

Multi-tenancy isolation

How AtmanID isolates tenant data — PostgreSQL Row-Level Security on every tenant table, a tenant context set on every query from the signed-in session, Iris queries the server builds rather than the model, and the CI checks and database canaries that stop regressions.

Audit chain integrity

How AtmanID’s audit chain works — an append-only audit log, hash-chained per tenant, with the chain head signed outside the database. Recent entries are re-verified nightly, and a weekly job walks the whole history and checks it against the signed chain heads (a run that reaches its time limit is reported as incomplete, never as verified). Also covers the X-Request-Id → audit-record correlation an auditor uses to reconstruct who did what, when.

Threat model

Threat model (STRIDE) — threat surface by component, mitigations and accepted risks.

Encryption posture

Encryption posture — at rest, in transit, key management and rotation.

RBAC architecture

RBAC architecture — per-tenant permissions checked on every request, what happens if the permission store is unreachable, and what is recorded.

Data residency and recovery

Data residency + disaster recovery — where data lives, how it is recovered, and the multi-region roadmap.

Compliance mapping

Compliance mapping — SOC 2 status and readiness, and how controls map to NIST CSF and ISO 27001.

What’s NOT in this section

  • Compliance certifications + subprocessor list — these live on the Trust page (the procurement surface). When AtmanID adopts a hosted trust portal (Drata/Vanta/SafeBase/Conveyor), that becomes the deep-dive evidence layer.
  • Customer operational dashboards — your tenant’s compliance posture, audit log search, SoD violations live in the AtmanID app. This section is general architecture; that’s per-tenant operational data.
  • API endpoint signatures — those live in API Reference. This section answers “how does the system architecturally work”; the API reference answers “how do I call endpoint X.”
  • Specific feature how-to guides — those live in Guides. This section answers “how does the audit chain work in design”; guides answer “how do I run a certification campaign in practice.”

How to read this section

Pick the page that matches your concern:

  • “How do you prevent tenant A from seeing tenant B’s data?” → Multi-tenancy isolation
  • “How do you prove the audit log wasn’t tampered with after the fact?” → Audit chain integrity — DB-enforced append-only, a hash chain, and chain heads signed outside the database
  • “What’s your STRIDE-style threat model?” → Threat model — full STRIDE table with mitigations and accepted risks

Adjacent

© AtmanID · Privacy