ISO 27001:2022 Annex A 8.6 – Capacity Management Explained

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.

ISO 27001

Quick Guide: Annex A 8.6 at a Glance

Annex A 8.6 of ISO 27001:2022 focuses on capacity management.

At a practical level, this means:

  • Ensuring sufficient capacity for information processing
  • Preventing system degradation, failure, or denial of service
  • Monitoring current and forecast demand
  • Planning for growth, change, and peak usage
  • Protecting availability of systems and services

The control does not require unlimited capacity. It expects organisations to understand demand and manage risk deliberately.

In-Depth Guide to Annex A 8.6

What Is Annex A 8.6 and Why Does It Matter?

Information systems depend on finite resources, including:

  • Processing power
  • Memory and storage
  • Network bandwidth
  • Cloud service limits
  • Supporting infrastructure

When capacity is insufficient:

  • Systems slow down or fail
  • Security controls may stop functioning correctly
  • Availability objectives are breached
  • Incident response and recovery are impaired

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.

How to Implement Annex A 8.6 Effectively

A pragmatic approach to Annex A 8.6 typically includes the following elements.

1. Identify Capacity-Dependent Systems and Services

Organisations should identify:

  • Business-critical systems
  • Information processing services
  • Infrastructure components that support them

Understanding which systems are sensitive to capacity constraints is the starting point for effective planning.

2. Monitor Capacity and Performance

Capacity management relies on visibility.

Organisations should monitor:

  • Resource utilisation trends
  • Performance thresholds
  • Error rates and degradation indicators

Monitoring should identify issues before service levels are affected.

3. Assess Current and Future Capacity Requirements

Capacity planning should consider:

  • Current operational demand
  • Forecast business growth
  • New services or applications
  • Changes in user behaviour
  • Seasonal or peak usage patterns

Annex A 8.6 explicitly expects planning for future demand, not just present needs.

4. Perform Stress and Load Testing Where Appropriate

Where systems are critical, organisations may:

  • Perform stress testing
  • Simulate peak or failure conditions
  • Validate assumptions about scalability

Testing reveals capacity limits that monitoring alone may not expose.

5. Plan for Capacity Expansion and Lead Times

Some resources cannot be expanded instantly.

Organisations should consider:

  • Procurement and provisioning lead times
  • Cost and complexity of expansion
  • Dependencies on suppliers or third parties

Resources that are harder or slower to expand typically require more conservative planning.

6. Manage Demand as Well as Supply

Annex A 8.6 supports managing both sides of the equation.

Demand management may include:

  • Removing obsolete data
  • Retiring unused systems or services
  • Optimising applications and processes
  • Restricting non-essential activity

Reducing unnecessary demand often delivers faster risk reduction than adding capacity.

7. Consider Cloud and Scalable Resources Deliberately

Where cloud services are used, organisations should consider:

  • Elastic or scalable capacity options
  • Usage limits and throttling
  • Cost implications of scaling

Cloud reduces capacity risk — but does not eliminate the need for planning.

8. Identify Single Points of Capacity Failure

Capacity risk often concentrates in:

  • Shared infrastructure
  • Centralised services
  • Key personnel or specialised resources

Annex A 8.6 expects awareness of dependency and concentration risk.

9. Align Capacity Management With Business Continuity

Capacity failures directly affect continuity.

Capacity planning should align with:

  • Availability objectives
  • Business continuity requirements
  • Incident response and recovery planning

Capacity shortfall during an incident can turn disruption into outage.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Practical Considerations

Annex A 8.6 does not require:

  • Over-provisioning everywhere
  • Complex forecasting models
  • Elimination of all performance risk

It does require organisations to:

  • Monitor and understand capacity
  • Plan ahead rather than react
  • Treat capacity exhaustion as a security and availability risk

Most capacity failures are visible long before they become incidents.

Common Challenges and How to Overcome Them

  • Capacity treated as a performance issue only
  • Recognise capacity exhaustion as an information security risk
  • Reactive scaling after failures occur
  • Monitor trends and plan ahead
  • Ignoring growth and change
  • Include future demand in capacity planning
  • Assuming cloud removes capacity risk
  • Understand limits, throttling, and cost constraints

Capacity problems rarely appear overnight.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 8.6 is about keeping systems available under pressure.

When capacity management is implemented effectively:

  • Availability incidents are reduced
  • Security controls remain effective under load
  • Business growth is supported safely
  • Recovery from incidents is more reliable

Attackers exploit weak capacity.
Users suffer when systems are overloaded.

Annex A 8.6 ensures organisations stay ahead of both.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls