BCM-04 Verification, updating and testing of the business continuity
Review, update and test the impact analysis and the continuity and contingency plans at least annually and after significant organisational or environmental change, involving affected tenants and relevant third parties,
4
artefacts
0
held by a system
2
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
- Test schedule and completed test reports covering the past twelve months · Document repository
- Evidence that affected tenants and relevant third parties took part in a test · Vendor register / contract repository
governing documentDocuments that govern the control
- Change log showing plans updated after an organisational or environmental change · Policy repository / GRC workspace
- Follow up actions raised from test findings with their closure status · 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
- Testing limited to desk walkthroughs with no technical recovery attempted
- Customers and suppliers never involved, so external dependencies stay untested
- Plans reviewed annually but not refreshed after a major platform change
- Test findings written up but never actioned
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 sheetBCM-03 Planning business continuity · COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements