GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
Strategic direction that describes appropriate risk response options is established and communicated
Source: NIST CSF 2.0, GV.RM-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
- Strategy approval record from executive leadership · Document repository
- Annual strategy review and refresh records · Document repository
governing documentDocuments that govern the control
- Cybersecurity strategy document with three to five year horizon · Document repository
- Roadmap aligned to strategic pillars and resourcing · Document repository
- Strategy traceability matrix to investments · Policy repository / GRC workspace
First move
Common gaps auditors find
- Strategy reads as a backlog rather than direction
- Roadmap unfunded beyond year one
- No traceability from strategy to capability outcomes
- Strategy refreshed only when leadership changes
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 sheetGV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes · GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from…