Help Center/Governance, RBAC & Security Desk/How to open "Audit Command Center" (Audit & Governance) and read it
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to open "Audit Command Center" (Audit & Governance) and read it

The newest entries of the platform audit ledger with independent re-verification of the Security OS hash chain.

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

Ask AI Copilot

Step-by-Step Procedure

1

Open the screen

In the admin sidebar open the "Audit & Governance" group and click "Audit Command Center" (address /admin/audit). Under the title the line "Data: ..." names where the figures come from: Live: i8_audit_ledger. Read-only and immutable..

2

Read the KPI tiles

Tiles: "Ledger entries (all time)", "Ledger entries, last 24 h", "Shown here", "Security OS chain". A tile that says "unavailable" means its source could not be read; it is never shown as zero.

3

Read the table

Columns: When, Source, Action, Actor, Target, Severity, Hash, Integrity. Each row is one audit entry, newest first (up to 300 per source). Actors are masked (first and last characters only). Integrity says VERIFIED or TAMPERED only for entries that belong to the Security OS hash chain, HASHED for entries that carry a stored hash, and NOT_CHAINED for plain ledger appends, which no chain attests.

4

Read the chain tile

See "How to read the Integrity column and the Security OS chain tile".

5

Know the limits

It is read-only and immutable: no button edits, hides or removes an audit entry, and a source that cannot be read is named in the description instead of being shown as empty.

Expected Operational Outcome

You can read the live data and use the actions this screen really implements.

Troubleshooting & Failure Modes

Symptom: Failed to load audit/overview: HTTP 403
Likely Cause: The operations API requires an administrator principal.
Resolution: Sign in with an administrator account and click "Retry".
Symptom: A tile or the description says a table "has not been created in this database"
Likely Cause: A database section (918 or 919) has not been applied yet.
Resolution: Ask the platform owner to run npm run db:apply:insight-security. Until then the screen reports it and offers no write buttons.

Was this guide helpful?

Help us refine our platform documentation