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.
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
- Strategy approval record from executive leadership · Document repository
periodic reviewEvidence produced at each review
- 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
Mostly documents and reviews. Pull the 1 system-held artefact from your Document repository 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
- 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 suppliers and other third parties