BCR-09 Disaster Response Plan
Maintain an approved disaster response plan covering natural and man-made events, and update it at least annually or when something significant changes.
4
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
- Annual update record and change-triggered updates · Document repository
governing documentDocuments that govern the control
- The approved disaster response plan with its version and date · Policy repository / GRC workspace
- Coverage of both natural and man-made scenarios · Document repository
- Named response roles with deputies · 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
- Plan covers technology failure only and ignores physical and human-caused events
- Named responders no longer in post
- Update triggered by nothing, so the plan drifts from reality
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 sheet