8.4.4 Business continuity plans
Document and maintain business continuity plans that guide teams through response and recovery, collectively containing the actions to continue or recover prioritized activities within predetermined time frames, the mean
5
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
- Evidence of availability at the point of use, including offline copies · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Plan set with each plan carrying every required element · Policy repository / GRC workspace
- Activation criteria and thresholds stated in the plan itself · Policy repository / GRC workspace
- Interdependency and resource sections reconciled to the BIA · Policy repository / GRC workspace
- Stand down process defined · 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 that cover activation and response but have no stand down, so the organization never formally returns to normal
- Agreed capacity omitted, so continuing an activity at any level counts as success
- Welfare and environmental consequences unaddressed
- Plans held only in a document management system that the disruption may take out
- Interdependencies listed inside the plan that contradict the BIA
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 sheet