GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated
Outcomes, capabilities, and services that the organization depends on are understood and communicated.
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 dependency walkthrough records · Document repository
governing documentDocuments that govern the control
- Dependency map covering people, process, technology, suppliers · Vendor register / contract repository
- Outcome statements for each critical service · Document repository
- Resilience scenarios spanning interdependencies · Document repository
- Supplier dependency overlay on the service map · Vendor register / contract 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
- Dependency map limited to internal systems
- Fourth party dependencies invisible
- Outcomes stated for IT, not for the customer
- Scenarios assume single point failures only
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-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated · GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction