GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered
Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered.
5
artefacts
1
held by a system
0
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
- Regulator and customer engagement log · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Stakeholder register with cybersecurity interests captured · Policy repository / GRC workspace
- Internal and external stakeholder communication plan · Policy repository / GRC workspace
- Workshop notes from stakeholder discovery sessions · Document repository
- Board reporting cadence for cyber matters · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Customers as stakeholders not represented
- Stakeholder needs never re-validated
- Regulators only contacted in incidents
- Internal audit not in the stakeholder map
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 sheetGV.OC-01 The organizational mission is understood and informs cybersecurity risk management · GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed