EvidenceSheet

GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced.

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 role review minutes · Identity provider / directory

governing documentDocuments that govern the control

  • RACI matrix across cyber roles · Policy repository / GRC workspace
  • Job descriptions with cyber duties for non security roles · Policy repository / GRC workspace
  • Delegations of authority for security decisions · Document repository
  • Onboarding pack confirming role responsibilities · 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

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 sheet

GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving · GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies