GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks 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
- Tooling configuration enforcing the method · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Methodology peer review notes · Document repository
governing documentDocuments that govern the control
- Documented risk calculation methodology · Document repository
- Calibration sessions for likelihood and impact estimates · Document repository
- Worked examples applied to recent risks · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management 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
- Method exists on paper, not in tooling
- Estimators not calibrated
- Methodology bypassed for time pressure risks
- No peer review of high impact assessments
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-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties · GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions