5.3 Roles, responsibilities and authorities
Top management must assign and communicate the responsibilities and authorities for the roles the BCMS depends on, and must specifically assign responsibility and authority for ensuring the BCMS conforms to the standard
4
artefacts
0
held by a system
2
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
- Named reporting line and evidence of performance reporting to top management · Document repository
- Evidence the assignments were communicated · Document repository
governing documentDocuments that govern the control
- Role descriptions or a responsibility matrix covering BCMS roles · Policy repository / GRC workspace
- Named individual accountable for BCMS conformity · 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
- Roles assigned in a matrix that the holders have never seen
- Conformity accountability and performance reporting rolled into one unfunded part time role
- Deputies undefined, so the BCMS has a single point of failure in its own governance
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 sheet5.2.2 Communicating the business continuity policy · 6.1 Actions to address risks and opportunities