A.8.6 Technological
Capacity management
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 (12)
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
- SC-6mostlycovers — A.8.6's broad capacity planning for facilities, HR, offices, and processing resources accounts for the bulk of SC-6's resource-availability allocation requirement, but leaves a residual of technical, system-level, and denial-of-service-specific protections untouched.
Aligned NIST CSF 2.0 outcomes (19)
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-04explicit mandateimplements — A.8.6 directly operationalizes the exact resource-capacity outcome that PR.IR-04 names for availability
Related OWASP ASVS 5.0 requirements (10)
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 (3246)
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).
Why these map — rationale
- CWE-1049partialfinds — Capacity management identifies and mitigates resource exhaustion from inefficient large-table queries.
- CWE-1067partialremoves — A.8.6 explicitly lists 'optimizing application code or database queries' as a mechanism to reduce demand, so applying it can remove CWE-1067 instances by adding indexes; however, this is one of six demand-reduction options, triggered by capacity pressure rather than code quality, and reaches only the subset of unindexed queries that surface as utilization problems.
- CWE-1067partialfinds — Capacity management monitoring, tuning, and query optimization can expose performance-degrading sequential scans and their missing indexes, but only for queries whose inefficiency measurably stresses capacity, leaving many non-bottleneck unindexed queries undiscovered.
- CWE-1089partialblocks — A.8.6's guidance includes 'optimizing application code or database queries' to reduce demand and increasing capacity (more powerful processing, memory, storage, cloud elasticity) which can mask the performance impact of excessive indices, so the weakness can be partially blocked from exploitation; however, the control's primary mechanism is planning and monitoring, the table still carries the excessive indices, and the masking depends on capacity actually being provisioned, leaving a nameable remainder.
- CWE-1176partialfinds — Capacity management can drive optimization of CPU-intensive algorithms to prevent resource exhaustion.
- CWE-401partialfinds — Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.
- CWE-674partialfinds — Capacity management includes monitoring and limits that mitigate resource exhaustion from runaway recursion.
Mitigated MITRE ATT&CK techniques (3277)
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
- T1496partialdetects — A.8.6 explicitly requires system tuning/monitoring, stress-tests, detective controls to indicate problems in due time, and manager monitoring of key resource utilization, which surfaces anomalous consumption patterns characteristic of resource hijacking (e.g. cryptomining, bandwidth proxying) on owned systems; partial because the clause's scope is limited to organization-managed facilities and does not address hijacking of co-opted third-party or external resources (e.g. SaaS, victim proxies) named in the technique.
- T1496.001partialdetects — A.8.6 explicitly calls for monitoring utilization of key system resources and putting detective controls in place to indicate problems in due time, and compute hijacking manifests as anomalous resource consumption that such monitoring would surface; however, the clause's monitoring is scoped to capacity planning rather than security threat detection, so it detects the symptom (resource exhaustion) without necessarily distinguishing the technique from legitimate load.
- T1496.002partialdetects — A.8.6 explicitly requires detective controls to indicate capacity problems in due time and mandates monitoring of key system resource utilization, which would surface bandwidth hijacking as anomalous bandwidth consumption; however, the control is oriented toward capacity planning rather than security-specific detection, and distinguishing malicious hijacking from legitimate high bandwidth use depends on the specific detective controls implemented under its mandate.
- T1496.003partialdetects — A.8.6 includes monitoring of key system resource utilization and detective controls to indicate problems in due time; SMS pumping manifests as anomalous SMS volume and cost spikes that capacity monitoring could surface. However, the clause is oriented toward general capacity planning and resource exhaustion, not toward detecting fraud or abuse of messaging services, so the detection is incidental and limited to utilization anomalies rather than the specific attack technique.
- T1496.004partialdetects — A.8.6 requires monitoring utilization of key system resources and putting detective controls in place to indicate capacity problems in due time, which can surface anomalous SaaS consumption, quota exhaustion and cost spikes indicative of hijacking; but the control is scoped to capacity management rather than security monitoring, so it catches utilization-side indicators and not the underlying compromise or lower-level adversary activity.
- T1498partialdetects — A.8.6 explicitly requires detective controls to indicate capacity problems in due time and monitoring of key system resource utilization, which would surface the bandwidth exhaustion symptoms of a network DoS as a side effect of capacity planning; the detection is incidental to the clause's primary provisioning purpose and narrower in scope than dedicated security monitoring (A.8.16), so it catches the symptom but not the attack as such.
- T1498partialprevents — Capacity management can reduce the success of bandwidth exhaustion by planning, stress-testing, and increasing or elastically provisioning capacity while reducing non-critical demand, but it does not stop malicious traffic or guarantee capacity beyond any attack volume.
- T1498.001partialdetects — A.8.6 requires monitoring utilization of key resources and putting detective controls in place to indicate capacity problems in due time, so a sustained flood would surface as resource exhaustion; however, the control's purpose is capacity planning rather than attack identification, and utilization monitoring distinguishes a flood from legitimate load only weakly.
- T1498.002partialdetects — A.8.6 explicitly requires detective controls to indicate capacity problems in due time and monitoring of key resource utilization, which would surface the bandwidth and resource exhaustion symptoms of a reflection amplification attack; however, the clause monitors capacity generically rather than identifying the attack vector, so it detects the symptom without distinguishing reflection amplification from other causes of capacity saturation.
- T1499partialdetects — A.8.6 requires monitoring of key system resource utilization and detective controls to indicate problems in due time, which would surface the resource-exhaustion symptoms of an Endpoint DoS; however, the clause's purpose is capacity planning rather than security detection, and crash-exploitation sub-techniques that do not exhaust monitored resources would not be caught.
- T1499.001partialdetects — A.8.6 explicitly requires detective controls to indicate capacity problems in due time and mandates monitoring utilization of key system resources, which would surface the resource exhaustion symptoms of OS exhaustion floods (TCP state table saturation, CPU exhaustion from ACK flood processing). However, A.8.6 is a capacity management control whose detection language addresses capacity problems generally; distinguishing a deliberate OS exhaustion flood from legitimate load requires the specific detection capabilities of A.8.16 monitoring or intrusion detection systems, not the capacity management process itself.
- T1499.002partialdetects — A.8.6 requires detective controls to indicate capacity problems in due time, which would surface the resource exhaustion caused by a service exhaustion flood, but the clause mandates detection without specifying instrumentation depth, so an implementation monitoring only aggregate resource utilisation is fully conformant and sees the symptom without isolating the flood's signature.
- T1499.003partialdetects — A.8.6 requires detective controls to indicate capacity problems in due time, which would surface an application exhaustion flood as anomalous resource consumption, but the clause mandates detection without specifying instrumentation depth, so what is caught is a slice the implementer chose rather than a bounded remainder of a mechanism that mostly works.
- T1499.004partialdetects — A.8.6 explicitly requires detective controls to indicate problems in due time and monitoring of key system resource utilization, which would surface the availability impact of T1499.004 (crashes, resource exhaustion, DoS conditions), but the clause's monitoring is scoped to capacity/availability problems rather than security exploitation, so it detects the symptoms without necessarily identifying the exploitation itself.
Prevented OWASP Web Top 10 (2025) risks (1)
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.