Continuity, backup and recovery
Criticality, continuity plan, backup policy, recovery objective, exercise and recovery evidence. A successful backup does not confirm recoverability.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 5 findings · 13 questions
Criticality and objectives Business impact and dependencies establish scoped recovery objectives.
Impact analysis
Impact analysis connects business needs to recovery targets and dependency order.
Recovery objectives
Recovery objectives state acceptable recovery time and data loss for a defined scope.
- Which business need sets the recovery time objective and recovery point objective in this service recovery objective record?
- Which scope and verification method does this recovery objective record specify?
Dependency order
Dependency order identifies recovery prerequisites and responses to unavailable dependencies.
- Which dependencies must recover first under this recovery plan and in which order?
- Which fallback does this recovery plan specify for an unavailable dependency?
Plans, backups and evidence Continuity arrangements, backup policies and recovery evidence support preparedness for disruption.
Backup and plan
Backup policies and continuity plans define protection, activation, responsibilities and recovery arrangements.
Backup policy
A backup policy defines coverage without treating backup completion as recovery evidence.
- Which data and configurations does this backup policy cover?
- Does this backup policy distinguish successful backup jobs from evidence of recoverability?
Continuity plan
A continuity plan states activation criteria, accountable roles, continuity arrangements and recovery procedures.
- Which activation criteria and decision authority does this continuity plan specify?
- Which response responsibilities and escalation authority does this continuity plan assign to each role?
- Which arrangements does this continuity plan specify to sustain prioritized activities during disruption?
- Which recovery procedures and return-to-normal criteria does this continuity plan reference?
Restore test
Restore tests record recovery conditions, measured outcomes and unresolved failures.
Recovery evidence
Recovery evidence connects observed results to the applicable objectives.
- Which versions and environment did this restore test use?
- Were the recovery time and data loss measured in this restore test within the applicable objectives?
- Which failures recorded in this exercise remain open?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseRSK
- Industry
- Cross-industry
- Tags
- EM-RSK-04W2subjectBusinessImpactAnalysisContinuityPlanBackupPolicyRestoreTestRecoveryEvidence
What it is Filled
Criticality, continuity plan, backup policy, recovery objective, exercise and recovery evidence. A successful backup does not confirm recoverability.
Why it exists Filled
Criticality, continuity plan, backup policy, recovery objective, exercise and recovery evidence. A successful backup does not confirm recoverability.
Distinguishing features Filled
- Backup and restore are distinct; a backup succeeding says nothing about whether recovery works.
- Recovery objectives always carry a scope and a way to verify them.
- Only a recorded restore test or real recovery proves recoverability.
- Distinct from incident handling, which deals with a disruption as it happens rather than preparedness for it.
What robots and AI may and may not do Filled
Must not
- Report recovery time and recovery point objectives as met because the backup job succeeded.
- Mark a service recoverable without supporting evidence from a recorded restore test or recorded real recovery.
- Delete or overwrite backups outside the retention policy.
- Start a production restore or failover on its own initiative.
- Hide a failed exercise step from the exercise report.
Only with a human decision
- A responsible human must authorize invoking the continuity plan or declaring a disaster.
- A responsible human must authorize accepting a recovery objective that the last test did not meet.
- A responsible human must authorize changing backup retention for regulated data.
May
- Compare measured restore times and data loss with the stated objectives.
- List services whose restore was never tested or tested on outdated versions.
- Show the dependency order a recovery must follow.
- Draft an exercise report from recorded test results.
- Use a recorded restore test or recorded real recovery as evidence of recoverability.
Moral aspects Filled
- Unrecoverable services can harm customers, patients or citizens who depend on them.
- False assurance about recovery shifts risk onto those who cannot see it.
- Backups hold personal data that keeps privacy obligations during retention.
Who is affected
- Customers and users of critical services
- Operations and IT staff
- Regulators and insurers
Owners Filled
Steward
The risk owner, the information security lead or internal audit, depending on the record.
Master systems
- GRC platform
- Identity and access management system
- SIEM
- Service desk
Links to other meta-models Filled
neighbor
- EM-OPS-01
- EM-PRD-02
- EM-TEC-04
references
- WM-ACT-043 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by the service or process identifier, with plans, policies and restore tests identified by their own identifiers and dates.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a service, an RTO or RPO, a backup policy or a restore test result.
- Often confused with backup job logs or with incident records.
Capabilities and actions required Filled
- Recovery chains can be rehearsed with a dependency deliberately unavailable.
- Restore test history shows whether objectives are trending towards or away from targets.
Hazards and failure modes required Filled
- Silent backup corruption discovered only at restore time.
- Circular dependencies that block recovery in practice.
- Backups exposed to the same failure or attack as the primary data.
Standards and interfaces required Filled
- ISO 22301 for business continuity management systems.
- ISO/IEC 27031 for ICT readiness for business continuity.
- NIST SP 800-34 Contingency Planning Guide for federal information systems.
Context of use required Filled
- Used by continuity, IT operations and security teams for critical services.
- Regulated sectors such as finance and health often mandate tested recovery.
Sources Filled
- NIST CSF/AI RMF: governance and risk functions
- ODRL/PROV: authority, grounds and evidence
- GRC/IAM/BCM practice and NIST SP 800-34 for recovery
- NIST Cybersecurity Framework - Checked live (HTTP 200) on 2026-10-07.
- NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems - Checked live (HTTP 200) on 2026-10-07.
- W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
- W3C PROV Overview - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to link RTO/RPO to the business need?
- Which dependencies must recover first?
- What proves an actual recovery?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-rsk-04/brief.json, ver-cy/world-models/card-supplements/em-rsk-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.