GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated.
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
- Annual critical service review minutes · Vendor register / contract repository
governing documentDocuments that govern the control
- Critical service catalog with objectives and tolerances · Policy repository / GRC workspace
- Business impact analysis aligned to critical objectives · Policy repository / GRC workspace
- Capability map linking security to mission outcomes · Document repository
- RTO and RPO commitments per critical service · 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
- BIA outputs not referenced in security investment
- Critical services list inconsistent across teams
- Tolerances expressed in IT terms, not customer outcomes
- Service catalog and CMDB diverge
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-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed · GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated