LOG-05 Audit Logs Monitoring and Response
Review security audit logs for activity outside expected patterns and follow a defined process to act on anomalies within a set time.
4
artefacts
0
held by a system
2
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- The defined review and response process with timeframes · SIEM / log platform
- Records of reviews performed and anomalies found · SIEM / log platform
governing documentDocuments that govern the control
- Actions taken on detected anomalies and their closure · Policy repository / GRC workspace
- The baseline of expected activity anomalies are judged against · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Detection working but no defined timeframe for response
- Anomalies recorded and closed with no investigation
- No baseline, so what counts as unusual is left to the reviewer's judgement
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-04 Audit Logs Access and Accountability · LOG-06 Clock Synchronization