OPS-13 Logging and Monitoring - Identification of Events
Analyse logging data automatically against the defined event criteria, including correlation of relationships between events, and report identified events automatically to the appropriate departments for prompt evaluatio
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
- Detection rule set including the correlation logic for multi source events · SIEM / log platform
- Alert queue extract showing elapsed time from event to notification · SIEM / log platform
- Handover record showing alerts reaching the on call responder · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Tuning history documenting rules added, amended or suppressed · 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
- No correlation configured, so only single event signatures are ever detected
- Alert volume so high that meaningful rules are suppressed wholesale
- Detection content never extended after new services were onboarded
- Events generated with no defined recipient outside business hours
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 sheetOPS-12 Logging and Monitoring - Access, Storage and Deletion · OPS-14 Logging and Monitoring - Storage of the Logging Data