LOG-03 Security Monitoring and Alerting
Watch applications and their underlying infrastructure for security-relevant events, and alert responsible stakeholders when those events and their metrics cross defined thresholds.
4
artefacts
3
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
- Alert rules and their thresholds · SIEM / log platform
- Routing showing which stakeholder receives which alert · SIEM / log platform
- Records of alerts raised and the response · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The list of security-relevant events monitored per application and platform · Policy repository / GRC workspace
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
- Events collected but no alerting configured on them
- Alerts routed to a queue nobody owns
- Application layer events omitted while infrastructure is well covered
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-02 Audit Logs Protection · LOG-04 Audit Logs Access and Accountability