Help Center/Governance, RBAC & Security Desk/How to tell chained audit blocks from plain appends
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to tell chained audit blocks from plain appends

The Provenance column shows whether a row is a hash-chained Security OS block or an ordinary row that proves nothing on its own.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Look at the Provenance column

A green "Chained #N" badge marks a block of the Security OS ledger that links to the block before it. A grey "Plain append" badge marks a normal row.

2

Know what each means

An edited or removed chained block breaks the chain and would be caught on the ledger-integrity screen. A plain row is only a record: the table has no trigger blocking UPDATE or DELETE, so it is not proof.

3

Check the Digest column

It shows the first 14 characters of the stored hash or "no digest stored" when the row carries none.

Expected Operational Outcome

You can judge how much evidential weight each audit row carries.

Was this guide helpful?

Help us refine our platform documentation