GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
The organizational mission is understood and informs cybersecurity risk management.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Annual context review minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Cybersecurity mission statement endorsed by leadership · Document repository
- Business context analysis tying cyber program to strategy · Document repository
- Stakeholder map for cybersecurity governance · Document repository
- Organizational chart showing security accountability · Document repository
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
- Context document predates major business changes
- Cybersecurity mission not referenced in strategy decks
- Subsidiaries outside the stated scope
- No record of board endorsement
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 sheetDE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events · GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered