EvidenceSheet

GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction

Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction.

6
artefacts
1
held by a system
4
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

  • KPI/KRI dashboard tied to strategic objectives · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Strategy review meeting cadence and minutes · Policy repository / GRC workspace
  • Adjustments documented after strategy reviews · Document repository
  • Annual cyber strategy refresh record · Document repository
  • Action items from prior reviews and their closure status · Document repository

governing documentDocuments that govern the control

  • Comparison of strategy targets vs. actual outcomes · 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

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.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated · GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks