Security

Datab's security posture is grounded in three principles: bounded agency for the AI agents, audit-first design for every state change, and explicit data residency. The Node is on-premise; the audit log is local; the data is the institution's.

Bounded agents (Orula + Gu)

Atlas identity, prompt checks, policy, approvals, and audit are the intended controls for Orula and Gu. These preview services are being tested against real operator tasks and deployment roles. High-impact actions require institution-approved controls and human authorization before release.

Identity + trust (Atlas)

• Per-institution NIN-hashed registry.
• Atlas HQ federation is subject to institution approval, authenticated transport, and commissioning checks.
• Cross-node lookup and write-back must pass consent, access, and audit checks before activation.

Data residency + privacy

• Operational databases are held on institution Nodes. Optional off-site backup through DDSN requires separate terms, encryption, and restore testing.
• Atlas HQ federation is opt-in and scoped by institution approval.
• Cross-node personal-data handling is reviewed against the approved purpose and institution policy.

Hardening + runbooks

Operator security hardening (SSH posture, firewall, fail2ban) is documented in docs/security/ssh-hardening.md. Five incident-response runbooks live under docs/security/runbooks/: unauthorized admin access, database export attempt, node compromise, lost recovery credentials, snap channel downgrade.

Disclosure

Security disclosures go to databsystems@gmail.comwith subject line SECURITY. Please do not file security issues in a public tracker.