GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained
Risk appetite and risk tolerance statements are established, communicated, and maintained.
5
artefacts
0
held by a system
2
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
- Risk appetite statement signed by the board · Policy repository / GRC workspace
- Annual appetite review minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Tolerance thresholds expressed quantitatively where feasible · Document repository
- Cascade of appetite into operational limits · Document repository
- Breach handling procedure for appetite excursions · 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
- Appetite stated qualitatively only
- Operational limits not aligned to appetite
- Breaches not surfaced to the board
- No appetite for emerging threats
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-01 Risk management objectives are established and agreed to by organizational stakeholders · GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes