6.2.1 Establishing business continuity objectives
Establish business continuity objectives at the relevant functions and levels; each must be consistent with the continuity policy, measurable where practicable, informed by applicable requirements, and monitored, communi
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Evidence of monitoring against each measure · SIEM / log platform
periodic reviewEvidence produced at each review
- Communication records for the objectives · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Retained objective register showing function, level, measure and owner · Policy repository / GRC workspace
- Update history for the objective set · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Objectives only at corporate level, so no function owns one
- Measurability waived without any judgement recorded on why it was impracticable
- Objectives inconsistent with the policy, most often on recovery ambition
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.2 Business continuity objectives and planning to achieve them · 6.2.2 Determining business continuity objectives