Audit ledgers
How SENTRA records administrative actions so that any later change to the record is visible.
| Where | What is recorded | Protection |
|---|---|---|
| Licensing Authority | Every sign-in (and refused attempt), key reveal, bundle download, approval, issue, revocation, authority enrolment and sync, import, key and user change, policy change, seal/unseal, release approval, publication and withdrawal | Each entry AES-256-GCM encrypted and hash-chained to the previous one (SHA-256), each chain value sealed with an HMAC under a vault key; one-click verification of the whole chain |
| SENTRA AI Threat Shield | Security decisions and administrative changes | A tamper-evident ledger that can be verified and exported |
| SENTRA Network Threat Shield | Every administrative change from the console and the command line | One JSON line per entry holding the SHA-256 of the previous entry; sentra-nts audit verify checks it; secrets are never written |
| SENTRA VIEW | Staff actions across the fleet | Entries chained by hash |
In a hash chain each entry includes a fingerprint of the one before it. Editing, deleting or reordering any past entry changes every fingerprint after it, so verification shows exactly where the record was altered.
What is never written to a ledger#
The Licensing Authority's trail names what was done (for example "revealed licence OTG-…"), by whom, from where and when; it never holds passwords, 2FA codes, recovery codes, licence keys or private keys. The NTS ledger likewise never writes passwords, tokens, 2FA codes or mail passwords.