ISO 27001:2022 Annex A 7.11 – Supporting Utilities Explained

Information systems fail quietly when the utilities they depend on fail first.

Annex A 7.11 exists to ensure organisations protect and manage supporting utilities — such as power, water, cooling, and telecommunications — so failures do not compromise information availability, integrity, or continuity.

This control is about infrastructure resilience, not just facilities management.

ISO 27001

Quick Guide: Annex A 7.11 at a Glance

Annex A 7.11 of ISO 27001:2022 focuses on supporting utilities for information processing facilities.

At a practical level, this means:

  • Identifying utilities that information systems depend on
  • Protecting utilities from failure, disruption, or misuse
  • Reducing single points of failure
  • Ensuring utility failure does not compromise information security
  • Supporting availability and business continuity objectives

The control does not require guaranteed uptime. It expects organisations to understand dependency and manage risk deliberately.

In-Depth Guide to Annex A 7.11

What Is Annex A 7.11 and Why Does It Matter?

Information systems rely on utilities such as:

  • Electricity and power distribution
  • Cooling and environmental control
  • Water and drainage
  • Telecommunications and connectivity

When these fail:

  • Systems shut down unexpectedly
  • Data may be lost or corrupted
  • Availability objectives are missed
  • Recovery becomes slower and less predictable

Annex A 7.11 ensures organisations treat utilities as part of the information security ecosystem, not as a separate operational concern.

This control replaces ISO 27001:2013 Annex A 11.2.2, with increased emphasis on network separation and secure connectivity.

How to Implement Annex A 7.11 Effectively

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

1. Identify Utility Dependencies

Organisations should identify which utilities support:

  • Information processing facilities
  • Critical systems and services
  • Security and monitoring infrastructure

Dependencies are often broader than initially assumed.

2. Protect Utilities From Failure and Interruption

Protection measures should be proportionate to risk and may include:

  • Redundant power feeds
  • Backup power or failover arrangements
  • Environmental controls and alarms
  • Physical protection of utility equipment

The goal is to reduce likelihood and impact, not eliminate all risk.

3. Follow Manufacturer and Supplier Guidance

Utilities and supporting equipment should be:

  • Configured correctly
  • Operated within design limits
  • Maintained in line with manufacturer guidance

Improper configuration is a common cause of avoidable failure.

4. Inspect, Test and Maintain Utility Equipment

Supporting utilities should be:

  • Inspected and tested periodically
  • Maintained proactively
  • Reviewed after failure or significant change

Unmaintained utilities degrade silently until failure occurs.

5. Reduce Single Points of Failure

Where justified by risk, organisations should consider:

  • Multiple utility feeds
  • Separate physical routing
  • Diverse suppliers

Single points of failure undermine availability objectives quickly.

6. Separate Utility Networks From IT Networks

Where utilities use network connectivity:

  • Networks supporting utilities should be segregated from IT networks
  • Access should be restricted and controlled

This reduces the risk of compromise spreading between operational and information systems.

7. Restrict Internet Connectivity for Utility Equipment

Internet access for utility equipment should:

  • Be permitted only where necessary
  • Be implemented securely
  • Be monitored and controlled

Unnecessary connectivity increases attack surface without benefit.

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.

Emergency and Failure Considerations

Annex A 7.11 also supports preparedness for failure scenarios.

Organisations should consider:

  • Clear emergency contacts and escalation paths
  • Emergency switches or isolation mechanisms
  • Emergency lighting and communications
  • Safe shutdown and recovery procedures

Response capability matters as much as prevention.

Practical Considerations

Annex A 7.11 does not require:

  • Data centre–grade infrastructure everywhere
  • Elimination of all utility risk
  • Over-engineered solutions

It does require organisations to:

  • Understand utility dependency
  • Treat utilities as information security enablers
  • Align protection with availability and continuity needs

Many outages are caused by utilities, not cyber incidents.

Common Challenges and How to Overcome Them

  • Treating utilities as purely facilities issues
  • Recognise utility failure as an information security risk
  • Hidden single points of failure
  • Map dependencies and review architecture
  • Unsecured network-connected utility equipment
  • Segregate and restrict utility networks
  • Reactive maintenance only
  • Inspect and test utilities proactively

Utility failures rarely announce themselves.

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 7.11 is about protecting what information systems rely on to stay operational.

When supporting utilities are managed effectively:

  • Availability risk is reduced
  • Outages are shorter and less severe
  • Recovery is more predictable
  • Information security objectives are easier to meet

Systems do not fail in isolation.
Annex A 7.11 ensures the foundations they stand on are not ignored.

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