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

Objectives generic and not measurable

`GV.RM-01` Risk management objectives are established and agreed to by organizational stakeholders

Q: What evidence do auditors commonly ask for on GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders?

Risk management charter with objectives and KPIs; Board approved risk objectives statement; Mapping of cyber objectives to enterprise objectives; Risk committee terms of reference; Annual objectives attestation.

Risk management objectives are established and agreed to by organizational stakeholders

Source: NIST CSF 2.0, GV.RM-01. 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

Policy repository / GRC workspace

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

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

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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 sheet

GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes… · GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained