Edge Register
Standards ยท ISO 22301

ISO 22301:2019

Rendered when the buyer ticks "ISO 22301:2019". The register cites 3 of its 57 clauses, behind 3 findings: intermittent or no link, and no backup stated, concentration in one class or one link type, financial entity site with no recovery objective, and on the duty rows of every site it reaches.

Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Source framework: ISO 22301:2019. What it attaches to a site: the ISO 22301 regime page.

Clauses cited

3 of 57
ISO 22301 8.4.1 General

Put in place and keep up a response structure that allows relevant interested parties to be warned and informed in good time. It needs plans and procedures for steering the organization through a disruption and for triggering the continuity solutions, identified and documented from the strategies and solutions that were selected, and procedures that are specific about the first steps to take, adaptable as internal and external conditions change, centred on the impact of incidents, effective at keeping that impact small, and clear about roles and responsibilities.

Evidence an auditor accepts: Documented response structure; Procedures stating immediate steps and the roles that take them; Traceability from selected strategies and solutions to the documented plans
Common gap: Procedures written for one rehearsed scenario, brittle against anything else
Source framework: ISO 22301:2019
ISO 22301 8.4.4 Business continuity plans

Document and keep up business continuity plans that lead teams through response and recovery. Taken together, the plans set out: the actions for keeping prioritized activities going, or restoring them, within time frames fixed in advance; how the disruption and the response will be monitored; the thresholds set beforehand, and the process, for triggering the response; procedures for delivering products and services at the capacity agreed; and how the immediate effects are handled with regard to people's welfare, avoiding further loss, and the environment. Each plan must state its purpose, scope and objectives; the roles and duties of the team that carries it out; the actions that put the solutions into effect; the supporting information needed to trigger, run, coordinate and communicate the response, including the triggering criteria, internal and external interdependencies, what resources are needed, what must be reported, and how the response is stood down; and it must be usable and to hand when and where it is needed.

Evidence an auditor accepts: Plan set with each plan carrying every required element; Activation criteria and thresholds stated in the plan itself; Interdependency and resource sections reconciled to the BIA
Common gap: Plans that cover activation and response but have no stand down, so the organization never formally returns to normal
Source framework: ISO 22301:2019
ISO 22301 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.

Evidence an auditor accepts: Documented restoration and return to normal processes; Criteria for deciding that temporary measures can be withdrawn; Evidence of use, from exercises or real events, including backlog clearance
Common gap: Recovery treated as implicit once the incident is closed, with no process behind it
Source framework: ISO 22301:2019

See which clauses your list engages

Paste the list and every site names the clauses behind it, filtered to the regimes that apply to you. Eight sites free, no account.

Build my edge register