BCM-03 Planning business continuity
Implement a single documented continuity and contingency planning framework derived from the impact analysis and anchored to standards in a statement of applicability, covering scope, plan accessibility, named owners, co
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Plan set demonstrably built on the outputs of the impact analysis · Policy repository / GRC workspace
- Statement of applicability naming the standards the planning follows · Policy repository / GRC workspace
- Plan ownership and approval record with scheduled review dates · Policy repository / GRC workspace
- Recovery procedure including manual workarounds and component restoration order · 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
- Plans stored only in systems that become unavailable in the scenarios they address
- Restoration sequence for infrastructure components not prioritised or agreed with customers
- Each team keeps its own plan format, so there is no single consistent framework
- Customer notification channels absent from the plans
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 sheetBCM-02 Business impact analysis policies and instructions · BCM-04 Verification, updating and testing of the business continuity