Security architecture
Compliance isn't a checkbox bolted on at the end — it's enforced at the database, on every write, for every tenant.
The ledger that links
Not a log you hope no one edited — a cryptographic chain that proves no one did. Every event is signed, sealed, and linked to the one before it.
The same identity can never sign both sides. Enforced at the database trigger, not the UI.
Every entry hashes its predecessor. Change one row and the whole chain breaks — tamper-evident by construction.
DSCSA EPCIS, audit chains and vertical events reject UPDATE and DELETE at the database.
Service identities are minted as SPIFFE IDs with 24h-expiring credentials, so agent actions stay attributable in the audit trail.
Illustrative example — not live customer data
Controls
Tenant data is isolated at the database via current_setting('app.current_tenant_id') — not application code you have to trust.
DSCSA EPCIS, audit chains and vertical events reject UPDATE and DELETE with EXCEPTION triggers.
Every audit entry hashes its predecessor, so any tampering breaks the chain and is detectable.
The same identity can never sign both sides of a control. Enforced at the trigger level.
Service identities are minted as SPIFFE IDs with 24h-expiring credentials, so agent actions are attributable in the audit trail.
Datadog spans capture tokens, duration and provider; the CT-15 CI gate blocks merges if the eval pass rate drops below its 96% floor.
Give your compliance team a system of record they can defend — line by line, signature by signature.