GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
Cybersecurity risk management activities and outcomes are included in enterprise risk management processes.
5
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- Joint risk committee meeting records · Document repository
governing documentDocuments that govern the control
- ERM framework with cyber risk integrated · Document repository
- Risk taxonomy shared across enterprise and cyber registers · Policy repository / GRC workspace
- Cross register reconciliation reports · Policy repository / GRC workspace
- Combined risk reporting pack for the board · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Cyber register siloed from enterprise register
- Different scoring scales prevent comparison
- Reconciliation manual and infrequent
- Combined reporting summarized to invisibility
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-02 Risk appetite and risk tolerance statements are established, communicated, and maintained · GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated