Guide/Security
Evidence Automation
The Evidence Automation page (GRC menu) shows, per framework, the freshness status of evidence collected automatically by connectors, so you can see at a glance where evidence is out of date and needs a new sync.
Status categories
| Status | Colour | Meaning |
|---|---|---|
| Fresh | Green | Automatic evidence (with findingId/validity defined) still within its validity period |
| Stale | Amber | Automatic evidence whose validity (expiresAt) has already expired: needs a connector re-sync |
| Manual | Grey | Evidence uploaded manually (with no findingId or validity) |
| No evidence | Red | Control with no associated evidence |
What it shows
- Global KPIs: total count by status (Fresh / Stale / Manual / No evidence) and coverage percentage for the entity/tenant
- Per framework: a distribution bar of the 4 statuses and a list of controls with stale evidence, for immediate action
- The validity of automatic evidence (
expiresAtfield inEvidence) is set by the source connector at ingestion time and cannot be edited manually
What it is for
Before an audit or certification renewal, this view lets you quickly identify controls whose technical evidence (Prowler, EterScan, GitHub, Microsoft 365, etc.; see section 19, Integrations) is no longer valid, avoiding reliance on out-of-date data during an assessment.