Features · Security & Backup · Audit Log Signing
Security & Backup · Audit Log Signing

HMAC-SHA256 chain,
tamper-evident by design.

Every audit entry signed; each signature includes the hash of the previous entry. Removing or editing one entry breaks the chain — provably. Verification UI built in. Compliance-grade evidence without a third-party service.

verify · chain
entry 4821 hash 9f2c… prev 41ab…
entry 4822 hash 41ab… prev 77de…
entry 4823 hash 77de… prev c014…
chain intact · 4823 entries
edit one and every later hash breaks
— Why this matters

An audit log you can edit is a document, not evidence.

01

Tampering should be detectable, not preventable.

Nobody can promise a database row is unreachable. What you can promise is that changing one breaks something visible.

02

Each entry commits to the one before it.

A signature covering the previous entry's hash makes the log a chain. Remove an entry in the middle and every signature after it fails.

03

Auditors ask for a demonstration.

Verification runs in the UI and reports where a chain broke, which is what a SOC 2 or ISO 27001 reviewer actually wants to see.

— What's included

How the chain is built and checked.

HMAC per entry
Every audit entry is signed as it is written.
Previous hash included
The signature covers the preceding entry, so entries are linked rather than merely stamped.
Verification UI
Runs the chain and highlights the broken segment. The entries stay visible — a break is reported, not hidden.
Linear cost
Verifying a million entries takes under ten seconds, so a long history is not a reason to skip the check.
Key kept out of reach
Encrypted at rest, derived from a KMS-backed master key, and not exposed through the API.
— How it works

Detectable, not preventable.

1

HMAC each entry

Every audit row is signed as it is written, with a key kept out of reach of the application that writes them.

2

Chain to the previous

Each signature commits to the hash before it, so removing or editing one row breaks every row after it.

3

Verify on demand

A verification pass walks the chain and shows where it breaks — which is the demonstration an auditor actually asks for.

— Works with

Connected capabilities

— FAQ

Questions, answered honestly.

Where is the signing key kept? +
Encrypted at rest on the platform, derived from a master key in a KMS / HSM-backed store. Not visible via API.
What happens if a signature fails verification? +
The UI shows a red banner highlighting the broken segment. The entries themselves remain visible — the system reports the break, it doesn't hide it.
Is verification expensive? +
Linear in the number of entries; verifying a 1M-entry chain takes under 10 seconds. Optimised for long histories.

Audit evidence you can actually defend.

Audit Log Signing on Enterprise.

Get early access Back to Security & Backup