8.4.5 Recovery
Maintain documented processes to restore and return business activities from the temporary measures adopted during and after a disruption.
3
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
- Evidence of use, from exercises or real events, including backlog clearance · Document repository
governing documentDocuments that govern the control
- Documented restoration and return to normal processes · Policy repository / GRC workspace
- Criteria for deciding that temporary measures can be withdrawn · 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
- Recovery treated as implicit once the incident is closed, with no process behind it
- No criteria for withdrawing temporary measures, so workarounds become permanent
- Backlog and data reconciliation built up during the workaround never planned for
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