4.4 Business continuity management system
Establish, implement, maintain and continually improve a business continuity management system, including the processes it needs and the way those processes interact, to the requirements of the standard.
3
artefacts
0
held by a system
1
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
- Evidence of operation across a full cycle rather than at implementation only · Document repository
governing documentDocuments that govern the control
- BCMS manual or equivalent showing the constituent processes and their interactions · Document repository
- Process owners named for each BCMS process · 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
- A documented system that exists on paper with no evidence any process actually ran
- Process interactions undocumented, so handoffs between impact analysis, strategy and planning are invisible
- Continual improvement asserted but not evidenced anywhere in the BCMS
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 sheet4.3.2 Scope of the business continuity management system · 5.1 Leadership and commitment