[non-validated] DORA SFS 9 / SF 5: Redundant capacity during recovery
Generated catalog draft. No operational assessment or human approval is claimed.
[non-validated] This question has unresolved selected work.
Question
[non-validated] Does the entity implement redundant capacity for critical services during recovery operations as specified in the DORA topic boundaries?
Explanation
[non-validated] Does the entity maintain documented redundant capacity to ensure service availability during recovery operations as specified in the DORA topic boundaries?
Criterion and evidence
Actor: Designated entity under repository topic boundaries. Scope: Implementation of redundant capacity for critical services during recovery operations per repository topic allocation. Evidence period: Current review period as defined in repository template. Required evidence: Documented technical specifications confirming redundant capacity meets repository-defined recovery objectives. Negative criterion: Evidence shows inadequate redundant capacity or absence of documented implementation. Missing evidence: Pending until repository-aligned documentation of redundant capacity is provided. Alternatives: No valid alternatives satisfy the criterion; redundant capacity must be explicitly documented per repository topic boundaries under repo-only constraints.
AI assistance prompt
Develop sixteen bounded yes/no factors for DORA: Backup, restoration and recovery. Protect backup copies and demonstrate restoration and recovery against stated objectives. Cover backup scope, segregation and protection, restoration testing, recovery priorities/objectives, redundant capacity and reconciliation of recovered information. Keep business continuity policy in SFS 8 and evidence of real execution separate from proposed procedures. DORA article references: 12. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.
Clarifications
What evidence should be checked?
Technical specifications and operational evidence demonstrating redundant capacity implementation per repository topic boundaries. Synthetic fixtures confirm technical documentation dated within review period (satisfied), single-point-of-failure reports (failed), or missing documentation (pending).
Are alternatives permitted?
No alternatives satisfy the criterion; redundant capacity must be explicitly documented per repository topic boundaries under repo-only constraints. Missing evidence remains pending.
References
DORA: Backup, restoration and recovery