A.8.14 Redundancy of information processing facilities
Information processing facilities are to be built with enough redundancy to satisfy availability requirements. Purpose (stated in ISO/IEC 27002:2022): keeps information processing facilities running without interruption. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.14.
Source: ISO/IEC 27001:2022, A.8.14. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.
Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Failover test records, preferably from production, showing failover worked as intended · Backup / DR tooling
governing documentDocuments that govern the control
- Statement of Applicability entry for control A.8.14, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
- Documented availability requirements for business services and systems · Document repository
- Architecture diagrams showing redundancy such as dual providers, redundant networks, separate data centres, redundant power and load-balanced instances · Policy repository / GRC workspace
- Procedures for activating redundant components, stating whether activation is automatic or manual · Policy repository / GRC workspace
First move
Common gaps auditors find
- Redundant components exist but failover has never been tested
- Both internet links run through the same physical route or provider
- The secondary site has weaker security controls than the primary
- Single points of failure remain in supporting components such as DNS or identity services
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet