8.6 Evaluation of business continuity documentation and capabilities
Evaluate whether the business impact analysis, risk assessment, strategies, solutions, plans and procedures remain suitable, adequate and effective, carrying out those evaluations through reviews, analysis, exercises, te
5
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
- Partner and supplier continuity capability assessments with evidence behind them · Vendor register / contract repository
governing documentDocuments that govern the control
- Evaluation records covering each element of the BCMS documentation set · Document repository
- Compliance and conformity evaluation results · Document repository
- Post incident and post activation evaluations · Document repository
- Documentation update records traceable to evaluation findings · 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
- Supplier continuity accepted on a self assessment questionnaire with nothing verified
- Evaluation performed only on the anniversary, never after an actual activation
- Findings raised but documentation not updated, so the next responder uses the superseded version
- Legal and regulatory compliance evaluation omitted from the continuity evaluation entirely
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 sheet8.5 Exercise programme · 9.1 Monitoring, measurement, analysis and evaluation