Sekit CSF · Backup & Recovery · Policy
RCF-0250RTO/RPO definitions
Maximum acceptable recovery time and data loss are formally defined for all critical systems
Mapping at a glance
RCF-0250RTO/RPO definitionsBackup & Recovery · Policy
RCF-0250 maps to 4 controls across the published frameworks. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.5.1Policies for information securitysupportsSekit's RTO/RPO definitions policy is part of A.5.1's topic-specific policy layer: it sets the maximum tolerable downtime and data loss allowed for each critical system.A.5.30ICT readiness for business continuitysupportsDefining maximum tolerable downtime and data loss for each critical system is the business continuity target that ICT readiness must be built to meet, not the delivery capability itself.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Disaster recovery plan and runbooks
The plan defining how long each critical system can be down (RTO/RPO) and the step-by-step guides to recover it after a serious failure.
From the Sekit evidence catalog
This topic through the other lenses
All Backup & Recovery controls
Ask Sekura: “What evidence proves RCF-0250?”
Also via MCP, free with account