IR-6 Containment, eradication and recovery - automate the incident handling
Automate manual and repetitive incident handling tasks to shorten response time, increase the number of incidents an analyst can handle and reduce the error rate that comes with fatigue.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Automated response playbooks and their trigger conditions · Document repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Execution history with outcomes · Document repository
- Measured change in mean time to contain · Document repository
- Approval gates for automated actions with material impact · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- automation built but never enabled for fear of false positives
- automated containment with no approval gate on high impact actions
- no measurement so the value of automation is unknown
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-5 Detection and analysis - prioritize incidents · IR-7 Post-incident activity - conduct lesson learned and retain evidence