6.2.2 Determining business continuity objectives
For each objective, determine what will be done, what resources it needs, who is responsible, when it will be completed and how the results will be evaluated.
3
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 the resource named was actually made available · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Plan per objective covering activity, resource, owner, date and evaluation method · Policy repository / GRC workspace
- Evaluation results against the stated method · 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 name an owner and a date and nothing else
- Resource requirement omitted, so the objective competes for unallocated effort
- Evaluation method left undefined until after the deadline passes
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.1 Establishing business continuity objectives · 6.3 Planning changes to the business continuity management system