ISO 27002:2022
Technological controls – ISO 27002:2022

ISO 27002:2022 8.14: Redundancy of information processing facilities

Information processing facilities are to be built with enough redundancy to satisfy availability requirements. Purpose: keep processing facilities operating without interruption. Guidance: identify availability requirements for business services and information systems and design and build a systems architecture with redundancy that meets them. Redundancy can mean duplicating facilities partly or completely, from spare components to two of everything. Plan and implement procedures for bringing redundant components and facilities into use, stating whether they are always active or activated automatically or manually in an emergency; redundant elements must be secured as strongly as the primary ones. Mechanisms should alert the organization to failures, allow the planned procedure to run and keep services available while facilities are repaired or replaced. Consider contracting several providers for network and critical processing services, internet access among them; redundant networks; mirrored systems in two data centres in different locations; physically redundant power supplies or sources; multiple parallel software instances with automatic load balancing within or across data centres; and duplicated components within systems (processors, disks, memory) or networks (firewalls, routers, switches). Where it applies, and ideally on live systems, test that failover between components works as intended. Other information: redundancy is closely linked to ICT readiness for continuity (5.30), especially where recovery times are short; copying data to duplicates can introduce integrity errors and weakly secured duplicates can compromise confidentiality, so both must be designed for; redundancy does not usually cure faults within an application; public cloud allows multiple live copies in several places, failing over and balancing load automatically, discussed in ISO/IEC TS 23167.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 64 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 10 controls

  • CP-6 Alternate Storage Site
  • CP-7 Alternate Processing Site
  • CP-7(1) Alternate Processing Site | Separation from Primary Site (CP-7(1))
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • CP-7(3) Alternate Processing Site | Priority of Service (CP-7(3))
  • CP-8 Telecommunications Services
  • CP-8(1) Telecommunications Services | Priority of Service Provisions (CP-8(1))
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))

FedRAMP Moderate · 10 controls

  • CP-6 Alternate Storage Site
  • CP-7 Alternate Processing Site
  • CP-7(1) Alternate Processing Site | Separation from Primary Site (CP-7(1))
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • CP-7(3) Alternate Processing Site | Priority of Service (CP-7(3))
  • CP-8 Telecommunications Services
  • CP-8(1) Telecommunications Services | Priority of Service Provisions (CP-8(1))
  • CP-8(2) Telecommunications Services | Single Points of Failure (CP-8(2))
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-7(18) Boundary Protection | Fail Secure (SC-7(18))

NIST SP 800-53 Rev 5 · 9 controls

ISO 22301:2019 · 4 controls

  • 8.3.2 Identification of strategies and solutions
  • 8.3.3 Selection of strategies and solutions
  • 8.3.4 Resource requirements
  • 8.3.5 Implementation of solutions
  • ISM-0570 Maintaining backup email gateways
  • ISM-1438 CDNs for high availability website hosting
  • ISM-1580 Automatic failover between availability zones

MTCS (Singapore) · 3 controls

  • 19.6 Reliability and resiliency
  • A.26 Disclosure: Storage redundancy and elasticity
  • A.7 Disclosure: Availability
  • 19.5.24.C.02 19.5.24.C.02 Consider availability risks in VoIP and UC design
  • 22.1.23.C.01 22.1.23.C.01 Design cloud architecture for availability risks
  • 23.2.17.C.01 23.2.17.C.01 Availability risks in public cloud design

C5 (Germany) · 2 controls

  • C5-OPS-17 Logging and Monitoring - Availability of the Monitoring Software
  • C5-PS-02 Redundancy model
  • CFTC-SS-10 Geographic Dispersal of Backup Infrastructure and Personnel
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

DORA · 2 controls

  • DORA-Art.12 Backup policies and procedures, restoration and recovery
  • DORA-Art.7 ICT systems, protocols and tools

NIST SP 800-161 Rev 1 · 2 controls

  • P2-3.5.1 P2-3.5.1 Availability mechanisms against loss of 3DS processing
  • P2-3.5.2 P2-3.5.2 Availability mechanisms monitored and maintained

SOC 2 · 2 controls

  • SOC2-A1.1 A1.1 Managing processing capacity
  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • B.7.2.2 B.7.2.2 Technology: network capacity, resilience and space conditioning
  • CPS230-P41 BCP Execution Capability and Tolerance Breach Reporting

IEC 62443 · 1 control

  • 62443-4-2-CR-7-1 Component Denial-of-Service Protection

ISO 27001:2022 · 1 control

  • 8.14 Redundancy of information processing facilities

ISO 27701:2019 · 1 control

NIS2 Directive · 1 control

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

NIST SP 800-172 · 1 control

  • 3.13.3e Confuse and Mislead Adversaries

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Technological controls – ISO 27002:2022

You are reading one control. How much of ISO 27002:2022 have you already done?

ISO 27002:2022 8.14 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 64 it maps to, and the evidence behind each claim, over MCP and REST.