Skip to content
Technological controls
ISO 27001A.8.14

ISO 27001 Annex A 8.14 Redundancy of information processing facilities

What it says

Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Implement information processing facilities with redundancy sufficient to meet availability requirements, which your organisation sets for its services and systems.

Your organisation must implement information processing facilities, meaning the systems, services, infrastructure and sites that handle information, with redundancy sufficient to meet availability requirements. Redundancy means spare or duplicate components that can take over when one fails. The control sets no fixed level: your organisation sets the availability requirements, and the redundancy must be enough to meet them. A backup alone is not redundancy, because it restores after a loss rather than keeping the service running (Annex A 8.13 covers backups).

Why it matters

A single failed firewall, internet link or power supply can take down every service behind it. Redundancy sized to each service's availability requirement lets it keep running while the failed part is repaired or replaced.

How to implement

  1. Set availability requirements for each business service.

    Agree with each service's business owner how much downtime is acceptable, using your continuity objectives (Annex A 5.30). Then list what the service depends on: servers, network links, power, sites and suppliers.

  2. Remove single points of failure that would breach a requirement.

    Options include spare or duplicate components, a second internet link from another provider, redundant power (Annex A 7.11 covers utilities), load-balanced instances and a second site with mirrored systems. Build only what the requirement needs. Redundancy does not usually help with faults in the application itself.

  3. Bring spare components up to the primary's security level.

    Apply the same settings, patches, access rules and monitoring. Record whether each spare is always running, or starts automatically or by hand, and write the steps for switching over. Alert on any failure, so the loss of a spare is noticed. Catch data copying errors with checksums or record counts.

  4. Check what each bought service really provides.

    Read its availability commitment and the zones or regions it replicates across. Choose a higher tier or multi-zone option if the default falls short. If you cannot change it, add a second provider or a manual fallback, or record the gap and who accepted it.

  5. Test failover and record the result.

    Switch from one component to another, in production where the risk is acceptable, otherwise in a planned window or test environment. Measure the interruption against the requirement and fix what fails. For a bought service, ask for the provider's failover test results.

Keep it running

Treat a failover alert as urgent, because the service may now be running without a spare. Reassess when availability requirements, suppliers or the architecture change, and test again after a significant change.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The availability requirements, compared with the list of business services.

    Look at

    Whether each service has a stated requirement, and whether its business owner agreed it.

    Good evidence

    Every service on the list has a recorded availability requirement agreed by its business owner.

  2. Check 2 of 5What an auditor asks for

    Ask for

    The architecture diagram for a critical service, walked through against the live setup.

    Look at

    Single points of failure, including links that share a carrier or cable path and spares that share a power supply.

    Good evidence

    No single failure would breach the service's availability requirement, or the gap has a recorded risk decision.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Failover test records, or a live failover of a component the auditor picks.

    Look at

    Whether the switch worked as the procedure says, and how long the interruption lasted.

    Good evidence

    The service failed over and stayed within its availability requirement, and any problem found has been fixed.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Settings and monitoring on a redundant component, compared with its primary.

    Look at

    Patch level, configuration, access rules and whether its failure raises an alert.

    Good evidence

    The spare matches the primary's security settings and patch level, and a simulated failure raises an alert.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Availability commitments and uptime reports for a sample of bought services.

    Look at

    The provider's commitment and actual uptime, compared with your requirement, and which zones or regions the service really uses.

    Good evidence

    The commitment and actual uptime meet your requirement, or the shortfall has a fallback or a recorded decision.

Mappings

Closest match in ASD Information Security Manual: ISM-1438, Ensure high availability by using CDNs, which this control covers in full and more.

ASD ISM

ASD Information Security Manual: 3 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.