LOG-13 Failures and Anomalies Reporting
Report failures and anomalies of the monitoring system itself and notify the accountable party immediately, through a defined process.
4
artefacts
4
held by a system
0
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- The process for detecting and reporting monitoring failures · SIEM / log platform
- Health checks or heartbeat monitoring on log pipelines · SIEM / log platform
- Notification records for recent monitoring failures · SIEM / log platform
- The accountable party named for monitoring health · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
none for this control
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- Log pipeline failures discovered only when someone looks for missing data
- No health monitoring on the monitoring system, so silence looks like calm
- Failures detected but notification delayed to the next business day
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetLOG-12 Access Control Logs · SEF-01 Security Incident Management Policy and Procedures