A.5.29 Organizational
Information security during disruption
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 (17)
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.5.29's explicit focus on protecting information/assets during disruption directly accounts for the core of CP-2's requirements around maintaining essential functions and recovery during system disruption, but leaves some residual (e.g., detailed metrics, contact lists, and full plan development mechanics) uncovered.
- CP-7partialcovers — A.5.29's broad requirement to protect information/assets during any disruption is substantially addressed by CP-7's specific alternate-site capability for essential functions, but leaves residual aspects (e.g. non-IT assets, non-processing disruptions, or pre-transfer protection) uncovered.
Aligned NIST CSF 2.0 outcomes (15)
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-03domain mandateimplements — A.5.29 operationalizes resilience mechanisms for information/assets in adverse situations, which directly sits inside the PR.IR-03 outcome's domain without the CSF row explicitly naming the ISO control
- RC.RP-01domain mandateimplements — A.5.29's operational requirement to protect assets during disruption directly gives effect to executing the recovery portion of the IR plan (RC.RP-01) as the technical means within the recovery domain
Related OWASP ASVS 5.0 requirements (5)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (2401)
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 (2730)
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
- T1219mostlyresponds — A.5.29 explicitly requires plans that maintain/restore security during disruption, implement compensating controls when primary ones cannot be maintained, and integrate security into business continuity and ICT continuity processes; these directly engage once an adversary has established a RAT C2 channel (the technique is already running) by containing its impact, enabling eradication through restored controls, and bounding further spread during the incident.
- T1489partialresponds — A.5.29 explicitly requires plans, compensating controls, and processes to maintain/restore security of critical business processes during disruption, which directly engages incident response activities (containment via compensating controls or service recovery) once a service-stop technique is underway, but only for the business-critical subset rather than all possible services or full eradication of the actor's action.
- T1499partialresponds — A.5.29 requires plans, controls, and compensating measures to maintain/restore security (including availability) of critical processes once disruption occurs, which engages the containment/eradication slice of `responds` for realized endpoint DoS but leaves the pre-impact detection and full eradication of the attack vector as a remainder
- T1499.001partialresponds — A.5.29 requires plans, processes and compensating controls that activate during disruption to maintain/restore security of critical processes; this engages the core of `responds` (containment/eradication once the OS-exhaustion flood is underway) for the bounded slice of critical-business-process systems, but leaves non-critical systems, non-ICT disruptions, and pre-disruption prevention untouched.
- T1499.002partialresponds — A.5.29 explicitly requires plans that maintain/restore security of critical processes during disruption (including compensating controls and tested continuity plans), which directly engages the core of `responds` (containment/eradication once a DoS flood is underway) for service-exhaustion events that trigger disruption.
- T1499.003partialresponds — A.5.29 explicitly requires plans, compensating controls, and processes to maintain/restore security (including availability) once disruption from an application-exhaustion flood is underway, engaging the core of containment/eradication in response activities, but leaves the bulk of real-time flood handling to other mechanisms.
- T1499.004partialresponds — A.5.29 explicitly requires plans, compensating controls, and processes to maintain/restore security of critical processes during disruption, which engages several IR-4-style response activities (containment via failover/compensating controls, eradication of the DoS condition, and recovery of security posture) once the exploitation is underway, but leaves the core exploit and initial crash outside its direct containment scope.
- T1578.003partialresponds — A.5.29 requires plans, processes and compensating controls that maintain/restore security once disruption (including an adversary-caused deletion of a cloud instance) is underway; this engages the containment/eradication slice of `responds` but leaves the forensic-evidence-removal aspect and non-disruption pre-compromise use cases untouched.
- T1657partialresponds — A.5.29 requires plans, controls, and compensating measures to maintain/restore security (including during/after disruption from ransomware extortion or BEC that realises financial theft), which engages the containment/eradication/follow-up activities of `responds` once the technique is underway; partial because the clause is scoped to business continuity for critical processes rather than full incident response against all financial-theft vectors (e.g., pre-impact social engineering or cryptocurrency exploits).
- T1667partialresponds — A.5.29 explicitly requires plans to maintain or restore information security during disruption, and email bombing is a disruption that buries legitimate communications and impairs business operations — so the clause's continuity-of-security framework is engaged. However, A.5.29 is a process/framework control that mandates plans and compensating controls exist; it does not itself contain or eradicate the inbound mail flood, which depends on email-specific technical controls and the specific plans implemented.
- T1687partialrecovers — A.5.29's compensating-controls framework (c) and its explicit requirement to restore security at the required level and time frame directly address recovery when defensive controls are impaired, which is the state T1687 produces; however, the clause is a process/plan mandate rather than an executing recovery mechanism, and it does not cover detecting the exploitation, removing the adversary's foothold, or patching the underlying vulnerability, so the recovery it enables is a slice of what full restoration requires.
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.