6.2 Business continuity objectives and planning to achieve them
Set business continuity objectives and plan concretely how each of them will be achieved.
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
- Evidence objectives are monitored and reported · Policy repository / GRC workspace
- Evidence the objective set is updated as the organization changes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Documented objectives with the plan attached to each · 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
- Objectives stated as aspirations with no plan behind them
- Objectives never measured, so achievement is asserted rather than shown
- Objective set unchanged over years despite material change in the business
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 sheet6.1.2 Addressing risks and opportunities · 6.2.1 Establishing business continuity objectives