ISO 22301:2019 — Security and resilience — Business continuity management systems — Requirements¶
International Organization for Standardization. (2019). ISO 22301:2019 — Security and resilience — Business continuity management systems — Requirements.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Fallback Path
- Writing those three things down turns a survey of possibilities into the inspection of a single mechanism.
This sourceRequires documented continuity plans stating the activation criteria and procedure, the roles and authorities that may invoke them, and the minimum acceptable capacity at which prioritised activities must be resumed.
- Writing those three things down turns a survey of possibilities into the inspection of a single mechanism.
- Recovery
- IT and business continuity. Disaster recovery, with recovery-time and recovery-point objectives as engineered targets, and failback and re-baselining after a major incident.
This sourceDefines recovery-time objective (RTO), recovery-point objective (RPO), and the disaster-recovery/failback lifecycle as engineered business-continuity targets.
- IT and business continuity. Disaster recovery, with recovery-time and recovery-point objectives as engineered targets, and failback and re-baselining after a major incident.
Mechanisms¶
- Standby Transport Corridor
- The discipline that keeps it honest is to health-check continuously and rehearse the switch on a schedule, so "ready" is a tested fact rather than a hope.
This sourceRequires continuity arrangements to be exercised on a scheduled basis.
- The discipline that keeps it honest is to health-check continuously and rehearse the switch on a schedule, so "ready" is a tested fact rather than a hope.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:c396ea6dd199 · see in the full table