GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
Risk management objectives are established and agreed to by organizational stakeholders.
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
- Annual objectives attestation · Vendor register / contract repository
governing documentDocuments that govern the control
- Risk management charter with objectives and KPIs · Policy repository / GRC workspace
- Board approved risk objectives statement · Policy repository / GRC workspace
- Mapping of cyber objectives to enterprise objectives · Policy repository / GRC workspace
- Risk committee terms of reference · Document repository
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
- Objectives generic and not measurable
- No mapping to enterprise strategy
- Charter not refreshed after restructures
- Committee minutes lack decision records
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.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission · GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained