A.8.14 Technological
Redundancy of information processing facilities
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (23)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CP-2mostlycovers — A.8.14's redundancy mechanisms (e.g., failover sites, mirrored processing) directly implement the bulk of CP-2's recovery objectives, priorities, metrics, and continuity-of-essential-functions requirements, but a residual of CP-2 (e.g., explicit plan documentation, role assignments, testing, and full incident handling) sits outside pure redundancy.
- CP-7mostlycovers — A.8.14's requirement for redundancy of processing facilities (to ensure continuous operation) directly accounts for the core of CP-7's alternate-site mandate, but leaves a residual of formal agreements, specific RTO parameters, and explicit equipment/supply provisioning that sit outside A.8.14's scope.
- CP-10partialcovers — A.8.14's narrow focus on redundant facilities (hardware, sites, networks) for continuity addresses only a slice of CP-10's broader recovery/reconstitution requirements (backups, known-state restoration, procedures, timelines after any disruption).
Aligned NIST CSF 2.0 outcomes (14)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- PR.IR-03fullcovers — The ISO control's mandate to design and implement redundant architectures, failover procedures, and testing directly fulfills the CSF outcome of achieving resilience requirements in both normal and adverse situations.
- PR.IR-04domain mandateimplements — A.8.14's operational redundancy mechanisms give direct effect to maintaining adequate resource capacity for availability within PR.IR-04's domain, though the CSF outcome does not name redundancy specifically
Related weaknesses / CWE (1668)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Mitigated MITRE ATT&CK techniques (2683)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- T1486mostlyprevents — Redundancy of processing facilities (duplicated components, mirrored data centres, redundant networks/power, automatic failover, load-balanced instances) ensures business services and data remain available from the alternate path even after encryption of the primary copy, directly closing the availability interruption named by T1486; the bounded remainder is the window before failover completes or non-replicated data that was solely on the encrypted instance.
- T1489mostlyrecovers — A.8.14's redundant service instances and failover mechanisms restore availability when an adversary stops a service on one system, following the same logic as the T1529 anchor: the technique presupposes access to a single system at a time, and we cannot infer the adversary has stopped services on all redundant instances. The remainder is the case where the adversary stops services across many/all instances or uses cloud APIs (e.g., DisableAPIServiceAccess) to disable services organization-wide, which redundancy of individual instances does not address.
- T1495mostlyrecovers — Redundant facilities restore service from a clean copy when the primary is corrupted, but firmware corruption can spread to identical redundant components if the adversary reaches them, leaving a bounded remainder.
- T1498mostlyrecovers — A.8.14 designs/implements redundancy (mirrored datacenters, load-balanced instances, duplicated components, failover procedures) and explicitly tests failover so that availability of processing facilities can be restored after a network-bandwidth-exhausting DoS has occurred.
- T1529mostlyrecovers — OWNER RULING 2026-09-10, `mostly` CONFIRMED. Distinguished from A.8.14 -> T1499.004 because this technique presupposes some level of access; that access is by nature to a single system at a time, and we cannot infer that whoever gained it has or will gain access to the redundant devices. So failover genuinely restores here.
- T1561mostlyrecovers — Redundant facilities continue providing service when one system's disks are wiped, genuinely restoring availability through failover; the remainder is the data on the wiped system itself (which redundancy does not restore — that is A.8.13's job) and the risk that worm-like propagation reaches the redundant facility as well.
- T1561.001mostlyrecovers — A.8.14 restores service continuity through failover to redundant facilities, but T1561.001 explicitly includes worm-like network propagation that can reach and wipe the redundant systems too, and the destroyed disk content itself is not recovered by facility redundancy (only the processing role is) — so what is restored is a slice of the impact, not the bulk.
- T1561.002mostlyrecovers — A.8.14's redundant facilities genuinely restore availability when a system's disk structures are wiped, because the failover node retains intact MBR/partition tables and can take over; the bounded remainder is worm-like propagation that reaches the redundant systems as well, since the clause does not guarantee isolation of redundant infrastructure from the same access vector.
- T1578.003mostlyrecovers — A.8.14's redundant facilities and failover procedures restore the service capacity lost when a cloud instance is deleted, with the bounded remainder being forensic artifacts that redundancy does not preserve.
- T1485partialprevents — Redundancy of processing facilities (duplicated systems, mirrored data centres, load-balanced instances, failover procedures) ensures continued availability of services even after data destruction on primary components, directly preventing the adversary's goal of sustained availability interruption.
- T1485partialrecovers — Redundant facilities with mirrored data can recover data that existed on the redundant copy at last sync, but T1485 explicitly notes worm-like propagation via Valid Accounts, credential dumping and SMB shares, so destruction can reach the redundant facility too; data modified or created after the last sync is also lost, leaving a named remainder.
- T1489partialprevents — A.8.14 designs redundancy and failover (duplicated components, mirrored datacenters, load-balanced instances, redundant networks/power) so that stopping/disabling a primary service or facility does not render the overall capability unavailable, directly preventing the availability impact of T1489; it is only partial because the control does not stop the adversary from successfully executing the stop/disable action itself on any given instance.
- T1496.001partialprevents — A.8.14 designs in redundancy (spare components, mirrored datacenters, load-balanced instances, dual suppliers) so that hijacked compute on primary facilities can fail over without losing availability, directly stopping the technique's impact on system/service availability; it is only partial because the control does not stop initial compromise or resource consumption on any single instance and the guidance is explicitly about meeting defined availability requirements rather than universal coverage.
- T1496.001partialrecovers — A.8.14's redundant facilities can absorb workload when a system is overwhelmed by compute hijacking, restoring service availability through failover; however, the malware continues running on the compromised system, the redundant nodes may themselves be targeted, and the underlying compromise is not addressed by redundancy alone — mirroring the capacity-based remainder that bounded A.8.14 against T1499.004.
- T1498partialprevents — A.8.14 designs in redundancy (multiple ISPs, redundant networks, geo-separated mirrored DCs, load-balanced instances, duplicated components) that keeps services available when bandwidth to any single path is exhausted, directly stopping the availability loss named by T1498; it is only partial because the control is silent on volumetric scale (e.g. a multi-Tbps DDoS can still saturate even redundant links) and on the non-redundancy aspects (spoofing, botnet recruitment) also named in the technique.
- T1498partialresponds — A.8.14's alert mechanisms, activation procedures for redundant components, and continued availability during repair directly enable containment/eradication of an in-flight Network DoS once underway (e.g. via failover to mirrored systems or load-balanced instances), with the named remainder being impact already realized before activation.
- T1498.001partialprevents — A.8.14 designs in redundancy (multiple instances, load balancing, separate data centres, redundant networks/power) so the service can continue operating when a direct network flood saturates one path or instance, thereby preventing the technique from fully denying availability; it is only partial because the control does not stop the flood packets from reaching and consuming resources on the primary path, nor does it address volumetric attacks that can overwhelm even redundant capacity.
- T1498.001partialrecovers — Redundancy restores service capacity after a flood saturates a single node, but the attack continues to reach the failover target and component-level bandwidth limits remain, so what is restored does not survive the ongoing flood.
- T1498.002partialprevents — A.8.14 designs in redundancy (multiple instances, load balancing, separate data centres, redundant networks/power) so that reflected/amplified traffic can be absorbed or failed-over without full loss of availability; this stops the DoS outcome for the targeted service but does not stop the reflection packets from being generated or reaching the reflectors.
- T1499partialprevents — A.8.14 designs/implements redundancy, failover, and alerts to ensure continued availability despite resource exhaustion or crashes at the endpoint, directly stopping successful DoS impact in covered architectures, but leaves residual gaps for un-redundant single points, non-production-tested failover, and non-endpoint network saturation aspects of the class.
- T1499partialrecovers — A.8.14's redundant facilities and failover genuinely restore service when an endpoint is taken down by DoS, but the attack often continues to reach the failover node — sustained resource-exhaustion and exploitation-based endpoint DoS can take down the redundant system too, so what is restored does not always survive an attack that is still running.
- T1499.001partialprevents — Redundancy of facilities (duplicated components, mirrored data centres, load-balanced instances, failover procedures) allows continued service availability when one instance is exhausted by the OS-level flood, but does not stop the technique from successfully exhausting the primary target's OS resources or limits.
- T1499.001partialrecovers — A.8.14's redundant facility can take over when the primary is exhausted, but T1499.001 is a continuous capacity-exhaustion attack that reaches the failover node identically — restoring an equivalent OS with the same finite resource limits does not increase capacity, and the ongoing flood will exhaust the redundant system in turn, matching the T1499.004 anchor's reasoning.
- T1499.002partialprevents — A.8.14 designs in redundancy (duplicated components, geo-separated DCs, load-balanced instances, failover) so that exhaustion of one service instance does not stop overall availability, directly preventing the DoS impact of T1499.002; it is only partial because the control does not stop the flood from reaching and exhausting any single instance, nor does it address all exhaustion vectors (e.g. protocol-level CPU costs before load-balancing engages).
- T1499.002partialrecovers — A.8.14's redundancy (load-balanced parallel instances, multiple data centres, multiple ISPs) genuinely restores service when a component is overwhelmed, but T1499.002 is a capacity-based vector that continues to reach whatever the redundant system restores to; if the flood exceeds total capacity across the redundant set, the failover node is taken down too, so what is restored does not survive the attack that is still running.
- T1499.003partialprevents — A.8.14 designs in redundancy (duplicated components, failover, multiple instances, separate data centres) so that exhausting one path or instance still leaves capacity available, directly stopping the availability loss named by the technique; it is only partial because the control does not stop the flood from reaching or consuming resources on the primary instance(s) and the guidance is silent on application-level resource throttling or request filtering.
- T1499.003partialrecovers — Redundancy and load balancing across parallel instances can restore availability when one component is exhausted, but T1499.003 is a capacity-based vector that continues to hit the redundant instances; restoring an identical copy does not increase total capacity beyond what the attacker can also exhaust, so recovery is bounded against an ongoing flood.
- T1499.004partialprevents — A.8.14 designs in redundancy, failover, and alerts so that an exploitation-induced crash of a primary component does not produce sustained unavailability, but the control does not stop the vulnerability from being exploited or the crash from occurring in the first place.
- T1499.004partialrecovers — OWNER RULING 2026-09-10, regraded `mostly` -> `partial`. A.8.14 is a control that restores, but the technique is a denial of service and restoring an identical copy does not increase capacity, while a capacity-based vector is likely here. For a non-capacity vector such as ping-of-death the restoration is short-lived in many cases: a continuous attack takes the failover node down too.
- T1499.004partialresponds — A.8.14's alert mechanisms, failover activation procedures, and continued availability during repair directly act on an in-progress exploitation-induced crash/DoS (the technique already running) to contain impact and restore service, but this is bounded to redundancy-triggered recovery rather than full incident response containment/eradication of the adversary.
- T1529partialprevents — Redundancy of processing facilities (duplicated components, mirrored data centres, load-balanced instances, failover procedures) ensures continued availability despite a shutdown/reboot on any single instance, so the technique cannot achieve its availability-destruction goal on the service as a whole; it is only a slice because the control does not stop the shutdown command itself from executing on an individual component.
- T1561partialprevents — Redundancy of processing facilities (duplicated components, mirrored data centres, failover procedures, multiple suppliers) ensures continued availability after a disk wipe occurs on primary systems, which directly prevents the technique from achieving its availability-interruption goal on the overall service; it does not stop the adversary from executing the wipe itself.
- T1561.001partialprevents — Redundancy of processing facilities (duplicated components, mirrored data centres, load-balanced instances, failover procedures) allows continued availability after a disk-wipe event on primary systems, thereby preventing the adversary's goal of sustained availability interruption; it does not stop the wipe technique itself from executing on any given system.
- T1561.002partialprevents — A.8.14 designs in redundant facilities (mirrored data centres, duplicated components, automatic failover, multiple suppliers) so that a wiped primary boot structure still leaves the system/network available via the redundant path, directly stopping the availability-loss goal of T1561.002; partial because the control is silent on preventing the wipe itself on any given component and the attacker can still destroy structures on non-redundant elements.
- T1561.002partialresponds — A.8.14's failover and tested redundancy can contain the blast radius of a realized disk-structure wipe on one node by restoring service from the surviving redundant instance, but the technique's mechanics (especially worm-like propagation across mirrored systems or shared networks) often take out both primary and redundant facilities before or during activation, leaving only a slice addressable by response.
Prevented OWASP Web Top 10 (2025) risks (3)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.