Audit Compliance

This screen does two things: it proves the audit records are unbroken, and it shows the audit trail’s summary statistics.

Five chains

Audit records are kept as a chain: each row is tied to the one before it. Altering or deleting a row afterwards leaves the chain inconsistent from that point on, and verification catches it.

Chain	What it protects
Configuration Chain	Configuration changes
Manual Operations Chain	What people did by hand
Event Log Chain	The event log
Auth Attempt Chain	Sign-in attempts
Fired Alarm Chain	Fired alarm records

Verify Now beside each chain walks it from end to end. The verification returns the total record count, how many are valid, how many are broken, and which records they are.

Verify regularly, not when something is wrong

Chain verification is evidence: it shows the audit trail was unbroken up to that moment. Its value comes from running regularly — running it for the first time ahead of an inspection and finding damage tells you nothing about when the damage happened.

Statistics

Configuration changes

Box	What it shows
Total Records	Total audit records
Unique Users (30d)	How many users made a change in the last 30 days
Tables Monitored	How many tables are watched
Last 24h / 7d / 30d	Changes in that period

Manual operations

Box	What it shows
Total Records	Total interventions
Unique Operators (30d)	How many people intervened in the last 30 days
Signed / Unsigned	Interventions with and without an electronic signature
Last 24h / 7d / 30d	Interventions in that period
PIN Compliance	The share of interventions verified with an operation lock password

The signed ratio is a policy indicator

Far more unsigned interventions than signed ones is not a fault — an electronic signature is asked for only where an installation requires one. But under a regulation such as 21 CFR Part 11, this is the first number an inspection asks about.

Related

• Integrity Report — verifying stored fields
• Manual Ops Log — the interventions themselves