5.2.1 Establishing the business continuity policy
Top management must set a business continuity policy that suits the organization's purpose, gives a frame for setting continuity objectives, and commits the organization to satisfying applicable requirements and to conti
3
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
- Approval record naming the top management body and the date · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Approved policy carrying an explicit commitment to applicable requirements and to improvement · Policy repository / GRC workspace
- Traceability from the policy to the continuity objectives set under it · 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
- Generic policy text lifted from a template that says nothing about this organization's purpose
- Commitments to requirements or improvement missing or implied only
- Objectives set with no reference back to the policy framework
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 Policy · 5.2.2 Communicating the business continuity policy