A.5 Organizational controls

A.5.30 ICT readiness for business continuity

Not mandatory by default – decided in your SoA

What it means in plain language

New in 2022: make sure IT systems can be recovered within the times the business needs (RTO/RPO), and test it.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Teams should connect business continuity expectations to concrete ICT recovery design, rather than treating recovery as a generic IT backup topic. The strongest implementation links RTO and RPO targets to named services, recovery dependencies, and evidence from rehearsals, so management can judge whether the plan matches business tolerance for disruption and whether gaps need treatment in the ISMS.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Critical services lack documented RTO/RPO, so recovery arrangements cannot be checked against business needs during a disruption review.
  • Disaster recovery tests exist, but scenarios omit identity, network, or cloud dependencies, leaving realistic recovery gaps unexercised.
  • Test results are filed without named actions, owners, or retest dates, weakening follow-up under improvement and corrective action processes.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Map each in-scope system to a business owner, recovery objective, and recovery point target in the ICT Continuity Plan. Use inputs from the business continuity procedure, application inventory, and supplier architecture notes so dependencies such as DNS, identity, and storage are visible before a disruption exposes them.
  • Define recovery methods for each tier: alternate site, cloud region failover, rebuild from backup, or manual workaround. Assign accountable roles for decision-making, technical restoration, and business validation; record escalation paths, minimum staffing, and communications triggers for extended outages or partial service restoration.
  • Run scenario-based exercises on a risk-based cadence, such as annual full recovery tests for critical services and tabletop exercises for lower-impact systems. Include evidence of timing, failed steps, data-loss checks, and business sign-off that recovered outputs are usable, not merely that systems powered on.
  • Track exceptions and gaps as formal actions with due dates, owners, and verification criteria. When recovery times or data loss exceed targets, link the issue to the risk treatment plan, update backup or redundancy procedures, and retain the revised plan, test script, screenshots, logs, and approval trail.

What an auditor will ask to see

  • Signed ICT Continuity Plan with service list, RTO/RPO table, dependencies, and role assignments.
  • Disaster recovery exercise pack containing scenario, timestamps, restoration logs, and business validation notes.
  • Corrective action record showing failed recovery point, root cause, remediation, and retest confirmation.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.30. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.29 — Information security during disruption and A.8.13 — Information backup. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.