GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties.
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
- Feedback loop records on report usefulness · Document repository
governing documentDocuments that govern the control
- Communication plan for cyber risk across stakeholder tiers · Policy repository / GRC workspace
- Reporting templates tailored by audience · Document repository
- Escalation pathway from analyst to board · Policy repository / GRC workspace
- Sample board report with decision asks · Policy repository / GRC workspace
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
- Same report sent to every audience
- Escalation only triggered by incidents
- Feedback never incorporated
- Reports lack a decision request
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.RM-04 Strategic direction that describes appropriate risk response options is established and communicated · GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated