5.2.2 Communicating the business continuity policy
Hold the business continuity policy as documented information, communicate it within the organization, and make it available to interested parties where that is appropriate.
3
artefacts
0
held by a system
2
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
- Records of communication to staff, including new starters · Policy repository / GRC workspace
- Evidence of external availability where appropriate, and the decision on which parties get it · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Controlled copy of the policy with version and date · 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
- Policy communicated at launch and never to anyone hired since
- External availability neither provided nor consciously declined
- Uncontrolled copies in circulation alongside the current one
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.1 Establishing the business continuity policy · 5.3 Roles, responsibilities and authorities