IR-4 Incident Handling
Implement IR capability for preparation, detection/analysis, containment, eradication, recovery.
5
artefacts
1
held by a system
1
at each review
hard
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
- Incident ticket samples covering detection, containment, and lessons learned · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Tabletop and live exercise after action reports · Document repository
governing documentDocuments that govern the control
- Control implementation statement for IR-4 citing the system mission and inheritance from common controls · Document repository
- Incident response plan with severity definitions and escalation paths · Policy repository / GRC workspace
- Incident response team roster with on call rotation · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Detection coverage gaps allow incidents to be discovered externally
- Severity criteria inconsistent across teams leading to under reporting
- Lessons learned captured but corrective actions not tracked to closure
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-3(2) Incident Response Testing | Coordination with Related Plans. Coordinate incident response testing with organizational elements responsible for related plans · IR-4(1) Automated Incident Handling Processes