Evidence & History
Panaptico keeps the evidence behind every verdict — what was read, when, and against which definition — so an audit or an incident review becomes an export, not a fire drill.
History · Policy
Databases without automated backups
Sep 24 · 06:02
backupConfiguration.enabled = true
Cloud SQL API · definition v3
Sep 23 · 14:40
Remediation · PLAT-209
Sep 23 · 09:15
backupConfiguration.enabled = false
Cloud SQL API · definition v3
Sep 20 · 11:00
Changed by j.rivera
Sep 18 · 06:00
Reported as Unknown, never as Clear
v3
definitions are versioned, so old verdicts stay explainable
Receipts
Policies, monitors, verifications, and capabilities all keep the same four facts for every verdict.
Exactly what was judged, and why it was in scope for that check.
The value Panaptico read from the system that owns it, attributed to its source.
When it was read, and whether that's recent enough to trust for this check.
The version of the rule that judged it, so old verdicts stay explainable after a change.
Reports
Pull a period's capabilities, policies, verification runs, and fixes into one report — every number linked back to its receipts.
Reports
Quarterly IT continuity report
Capabilities
15
6 enabled at quarter end
Policies
29
21 clear · 3 unknown
Verification runs
412
97% passed
Fixes closed
38
each confirmed by evaluation
Capability health, week by week
58 → 70
Still open
3 fixes · 2 checks with stale evidence
Every number links to its receipts
Resource, observed value, time read, definition
412
verification runs this quarter, each one kept
Honest by design
A failed read is recorded as unknown, never back-filled with the last good value.
Every transition is kept — violating, fixed, clear — with the evidence that caused it.
Export history and reports as CSV whenever an auditor, a customer, or a board asks.
Used for
Works with
Connect one system and Panaptico starts keeping receipts from the first evaluation.