EvidenceSheet
NIST CSF 2.0 · GV - Govern

GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission.

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

  • Enforcement evidence (audit findings, disciplinary records redacted) · HR system / LMS

governing documentDocuments that govern the control

  • Policy review schedule with last and next review dates · Policy repository / GRC workspace
  • Change log per policy with rationale and approver · Policy repository / GRC workspace
  • Communication plan for policy updates · Policy repository / GRC workspace
  • Annual policy effectiveness review report · 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

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-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced · GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders