ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved.
5
artefacts
1
held by a system
0
at each review
hard
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
- Incident response plan with version history · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Business continuity and disaster recovery plans linked to IR · Policy repository / GRC workspace
- Communications plan for incidents · Policy repository / GRC workspace
- Plan approval records from leadership · Policy repository / GRC workspace
- Annual plan test results · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Policy repository / GRC workspace 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
- Plans inconsistent across business units
- IR and BC plans not aligned
- Approval expired
- Tests narrow in scope
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 sheetID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities · ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded