ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated…
Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
Source: NIST CSF 2.0, ID.IM-04. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Plan approval records from leadership · Policy repository / GRC workspace
- Annual plan test results · Source control / CI pipeline
governing documentDocuments that govern the control
- Incident response plan with version history · Policy repository / GRC workspace
- Business continuity and disaster recovery plans linked to IR · Policy repository / GRC workspace
- Communications plan for incidents · Policy repository / GRC workspace
First move
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