BCR-05 Documentation
Produce and hold the documentation the continuity and resilience programme depends on, make it reachable by the people authorised to use it, and review it on a set cycle.
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
- Review records against the defined cycle · Document repository
- Evidence of offline or alternate-site availability · Document repository
governing documentDocuments that govern the control
- The documentation set the programme depends on, with owners · Document repository
- Access arrangements proving authorised responders can reach it during an outage · 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
- Continuity documentation stored only on the system it is meant to recover
- Review cycle defined but not performed
- No record of who is authorised to access it
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 sheetBCR-04 Business Continuity Planning · BCR-06 Business Continuity Exercises