8.4.5 Recovery
Keep documented processes for bringing business activities back to normal, moving them off the stopgap measures put in place while a disruption lasted and after it.
Source: ISO 22301:2019, 8.4.5. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO 22301:2019 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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