IR-3 Detection and analysis - create incidents based on high-quality alerts
Establish a process to create high quality alerts and measure their quality, so analysts prioritise real incidents rather than spending time on false positives.
4
artefacts
2
held by a system
1
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 quality metrics such as true positive rate per rule · SIEM / log platform
- Analyst feedback loop on alert usefulness · SIEM / log platform
periodic reviewEvidence produced at each review
- Detection rule review and retirement process · SIEM / log platform
governing documentDocuments that govern the control
- Lessons learned feeding new or tuned rules · 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 measurement so poor rules are never retired
- rules added continuously and never removed
- analyst feedback collected informally and lost
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 sheetIR-2 Preparation - setup incident notification · IR-4 Detection and analysis - investigate an incident