Security incidents are not always caused by attackers.
Many are caused by systems simply running out of capacity.
Annex A 8.6 exists to ensure organisations proactively manage capacity for information processing resources, so systems continue to operate reliably and securely as demand changes.
This control is about preventing failure through foresight, not reacting after disruption.

Annex A 8.6 of ISO 27001:2022 focuses on capacity management.
At a practical level, this means:
The control does not require unlimited capacity. It expects organisations to understand demand and manage risk deliberately.
Information systems depend on finite resources, including:
When capacity is insufficient:
Capacity failures often look like technical issues, but they are predictable and preventable.
Annex A 8.6 ensures organisations treat capacity as a security and continuity concern, not just an IT performance issue.
This control supersedes ISO 27001:2013 Annex A 12.1.3 and reflects modern environments, including cloud and elastic infrastructure.
A pragmatic approach to Annex A 8.6 typically includes the following elements.
Organisations should identify:
Understanding which systems are sensitive to capacity constraints is the starting point for effective planning.
Capacity management relies on visibility.
Organisations should monitor:
Monitoring should identify issues before service levels are affected.
Capacity planning should consider:
Annex A 8.6 explicitly expects planning for future demand, not just present needs.
Where systems are critical, organisations may:
Testing reveals capacity limits that monitoring alone may not expose.
Some resources cannot be expanded instantly.
Organisations should consider:
Resources that are harder or slower to expand typically require more conservative planning.
Annex A 8.6 supports managing both sides of the equation.
Demand management may include:
Reducing unnecessary demand often delivers faster risk reduction than adding capacity.
Where cloud services are used, organisations should consider:
Cloud reduces capacity risk — but does not eliminate the need for planning.
Capacity risk often concentrates in:
Annex A 8.6 expects awareness of dependency and concentration risk.
Capacity failures directly affect continuity.
Capacity planning should align with:
Capacity shortfall during an incident can turn disruption into outage.
Annex A 8.6 does not require:
It does require organisations to:
Most capacity failures are visible long before they become incidents.
Capacity problems rarely appear overnight.
Annex A 8.6 is about keeping systems available under pressure.
When capacity management is implemented effectively:
Attackers exploit weak capacity.
Users suffer when systems are overloaded.
Annex A 8.6 ensures organisations stay ahead of both.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today