What is the most common gap auditors find on GV.RM-06?

Method exists on paper, not in tooling

`GV.RM-06` A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is…

Q: What evidence do auditors commonly ask for on GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is…?

Documented risk calculation methodology; Calibration sessions for likelihood and impact estimates; Worked examples applied to recent risks; Methodology peer review notes; Tooling configuration enforcing the method.

A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated

Source: NIST CSF 2.0, GV.RM-06. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

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 sheet

GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from… · GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational…