What an RTO Measures
An RTO concerns a usable service, rather than the repair time for an isolated server. Specify the functional state required at the end of recovery and identify who accepts the result. Restoring an application without its authentication service or data may not meet an agreed target.
Service owners need to define the point at which users can resume critical operations. A partially restored service may satisfy an interim target only when that reduced capability has been explicitly agreed.
Assess the Consequences of Downtime
Use a business impact analysis to understand how interruption affects essential service delivery, dependent customers, contractual commitments and safety where relevant. Prioritise restoration according to consequences that develop over time, not according to the relative age or popularity of applications.
An objective taken from a generic template might be either unnecessarily expensive or dangerously slow. Record which business consequences and assumptions informed the target.
Map Dependencies and Available Resources
Identify the systems, networks, identity services, third-party providers, staff, facilities and credentials needed to restore each service. A four-hour application objective will be unrealistic if a required shared platform cannot be recovered in less than six hours.
Document recovery sequencing and alternatives. Supplier commitments should be examined against the organisation's end-to-end restoration target, rather than treated as proof of service recoverability.
Test Actual Restoration Time
An RTO is a planning target, not evidence of tested capability. Run recovery exercises using representative disruptions and measure the interval until the defined service outcome is reached. Record dependencies that delayed restoration, manual interventions and workarounds.
Where actual recovery takes longer than the objective, explain the discrepancy, approve corrective actions and retest consequential failures. Leadership should see unresolved gaps rather than only the original target.
Keep the Legal and Evidence Record Accurate
The general Directive requires proportionate continuity measures. Regulation (EU) 2024/2690 contains more detailed requirements for particular digital and ICT provider categories and should not be applied indiscriminately to all NIS2 entities.
Retain impact analysis, approved recovery objectives, dependency maps, test results, exceptions and relevant Member State guidance. Reassess objectives after significant changes.
Questions on the text
Does NIS2 require a four-hour RTO?
No uniform four-hour RTO appears in Article 21 for every covered entity. Objectives depend on risk, service needs and any additionally applicable rules.
Is RTO the same as RPO?
No. RTO concerns restoration time, while RPO concerns acceptable data loss measured in time.