ISO 27001:2022 · Technological controls
ISO 27001:2022 8.6: Capacity management
ISO 27001:2022 8.6 covers Capacity management. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.6, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Capacity is managed reactively after outages.
Resource use is to be monitored and adjusted to fit present and expected capacity needs. Purpose (stated in ISO/IEC 27002:2022): keeps enough capacity available in systems, staff, offices and other facilities. 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.6.
What evidence supports 8.6?
- Annex A technological controlStatement of Applicability entry for control A.8.6, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlCapacity requirements for critical systems, facilities and teams reflecting business criticality
- Annex A technological controlMonitoring dashboards and alert thresholds for key resources such as CPU, memory, storage, bandwidth and licences
- Annex A technological controlStress or load test results confirming capacity for peak demand
- Annex A technological controlCapacity forecasts considering new business requirements, trends and long lead-time or high-cost resources
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.6, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Capacity is managed reactively after outages
- Load testing is never done before peak business periods
- Dependence on single key individuals is not treated as a capacity risk
- Cloud autoscaling limits are set without considering cost or quota ceilings
How it maps to SOC 2
- A1.1 high Capacity management is how availability commitments are kept.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.