GRC-02 Risk Management Program
Run a documented enterprise risk management programme, sponsored by leadership, that identifies, evaluates, assigns ownership of, treats and accepts cloud security and privacy risks.
4
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
- Formal risk acceptance records with the accepting authority · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The enterprise risk management policy and procedure · Policy repository / GRC workspace
- The risk register showing cloud security and privacy risks · Policy repository / GRC workspace
- Risk owners named and treatment plans recorded · 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
- Cloud risks absent from an otherwise functioning enterprise register
- Risks accepted informally with no named accepting authority
- Treatment plans with no owner or completion date
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 sheetGRC-01 Governance Program Policy and Procedures · GRC-03 Organizational Policy Reviews