SEF-05 Incident Response Metrics
Define information security incident metrics and monitor them over time.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Reports showing the metrics over time · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Evidence a metric trend prompted an action · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The defined incident metric set, such as detection time, containment time and volume by severity · Policy repository / GRC workspace
- The audience receiving them · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Metrics counting incidents without measuring the response
- Metrics reported once and not trended
- No action ever taken on a deteriorating metric
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 sheetSEF-04 Incident Response Testing · SEF-06 Event Triage Processes