An audit trail you cannot quietly rewrite.
Audit trail
Every admission decision is hashed when it is written and sealed under signed checkpoints that chain back to the first one. The signing key lives in a Secret in your cluster, not in the database, so rewriting history takes two different accesses.
Every evidence document re-checks the whole ledger and says whether it is intact. Changes made through the console, from policy edits and break-glass to triage and evidence exports, are kept in a separate audit log with who and when.
Step by step.
Each record is hashed
SHA-256 over its content, by the operator, when it is written.
Records are sealed
Hourly by default, or every 10,000 records: a signed Merkle root.
Seals are chained
Each checkpoint carries the hash of the one before.
Every document re-checks
Chain, record hashes, roots and counts, signatures.
Tampering is named
An edited record appears by id.
The ledger check's result, intact or not and why, is a section of every evidence package.
- DORA4 clauses
- NIST SP 800-1904 clauses
- NIST SSDF4 clauses
- NIST SP 800-535 clauses
- ISO/IEC 270015 clauses
- GDPR Article 323 clauses
- PCI DSS3 clauses
- MAS TRM7 clauses
- Essential Eight2 clauses
- ISMAP10 clauses
- ISMS-P10 clauses
57 clauses across 11 frameworks cite at least one of these statements.
Install it yourself.
Create an account, confirm your e-mail with the code we send, take the free Community key from the Licenses page, and install with Helm.
Create an account