A.8 Technological controls

A.8.14 Redundancy of information processing facilities

Not mandatory by default – decided in your SoA

What it means in plain language

Build enough redundancy into IT facilities to meet availability requirements.

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

Redundancy supports availability without promising that every outage is preventable. The focus is on identifying which processing facilities need resilience, what dependency failures can defeat failover, and who confirms that design assumptions still match the business service levels. Distinguish redundant components from genuine recovery capability, because duplicated hardware alone does not address application state, configuration drift, or shared-service bottlenecks.

Common auditor findings to check for

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

  • A secondary site or cloud zone exists, but the application still depends on one identity service, one DNS path, or one storage tier, so failover stops at the first shared dependency.
  • Failover was designed for a previous workload profile; new transaction volumes or batch jobs exceed the standby capacity, causing degraded performance after switchover.
  • Redundancy arrangements are undocumented or untested, so staff cannot prove which services fail over automatically, which need manual intervention, or who authorizes the cutover.

How you can implement it

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

  • Have the service owner, infrastructure architect, and continuity lead define the required level of redundancy from business impact analysis, threat scenarios, and supplier constraints. Document whether resilience is active-active, active-passive, or component-level, and record any nonredundant dependencies such as third-party identity, internet transit, or external message queues.
  • Describe each critical facility in the procedure with explicit failover triggers, target recovery sequence, and rollback conditions. Include network links, firewalls, load balancers, storage, compute, licensing, and configuration synchronisation. Without these dependency details, a nominally redundant platform can still fail because the switchover path was incomplete.
  • Test redundancy under controlled conditions. A tabletop exercise shows decision flow, but periodic technical failover proves service continuity and exposes hidden coupling, such as stale replicas or certificate issues. Capture service-impacting observations, elapsed times, and manual steps so engineering backlog items can be prioritised with clear ownership.
  • After infrastructure changes, supplier migrations, or major release deployments, reassess whether the redundant design still matches the original resilience objective. Record any reduced tolerance, compensating monitoring, or temporary single points of failure in the risk register and track their closure through change management and management review.

What an auditor will ask to see

  • Information Processing Facilities Redundancy procedure with service tiers, failover criteria, dependency map, and named technical approvers.
  • Failover exercise record showing timestamps, service checks, manual interventions, rollback decision, and issues logged for correction.
  • Architecture or topology diagram identifying primary and secondary components, shared dependencies, and links to the continuity or recovery plan.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.8.13 — Information backup and A.5.30 — ICT readiness for business continuity. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core 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.