ISO 27001 Annex A 7.11: Supporting utilities

What Control 7.11 means in practice

Protect information-processing facilities from loss or instability of power, cooling, communications and other utilities. The useful question is not whether a policy mentions the topic, but whether scope, decisions, ownership and records show a repeatable response to actual risk.

Design should fit the organization’s services and dependencies. A smaller team can use lightweight records and existing platforms; a complex environment normally needs clearer separation of duties, automated coverage checks and governed exceptions.

Implementation steps

1. Step 1. Define ownership, scope and operating criteria for supporting utilities.
2. Step 2. Implement continuity arrangement that fits the organization’s risks, services and working practices.
3. Step 3. Integrate the activity with relevant change, exception and review processes.
4. Step 4. Review performance and improve the arrangement when risks, technology or obligations change.

Translate each step into an owner, trigger, expected record and review rule. This makes the activity testable and prevents an attractive document from becoming the whole implementation.

What good implementation looks like

• recent samples show supporting utilities operating across the intended scope
• exceptions and adverse results have accountable decisions and verified closure
• review results lead to measurable correction or improvement

These outcomes should be observable in normal work, not only during audit preparation. Owners should be able to explain weak results, accepted exceptions and the next improvement action.

Implementation evidence and effectiveness evidence

Implementation evidence shows that the arrangement exists. Effectiveness evidence shows whether it produces the intended result across the relevant scope and over time. Auditors commonly corroborate both.

How an auditor may test Control 7.11

1. Select a representative in-scope service, asset or process.
2. Confirm the accountable owner and expected operation.
3. Trace a recent example: A critical service is tested against agreed recovery needs, dependencies and improvement actions after the exercise.
4. Inspect the operating record and corroborating technical evidence.
5. Compare the design with evidence that the control operated effectively.
6. Follow an exception or adverse result through decision and closure.
7. Review trends, metrics and improvement decisions.

Questions to prepare for

• How is supporting utilities implemented in practice?
• Who owns the activity and how are decisions approved?
• Show me a recent example from operation through review.
• How are exceptions, changes or overdue actions handled?

Practical examples

Useful performance and coverage measures

• in-scope coverage for supporting utilities
• overdue exceptions or actions by age
• repeat findings identified through review

Use measures to expose coverage, timeliness, recurrence and exception age. Raw activity volume is not success; a metric should help an owner decide or investigate.

Approach for smaller and mature organizations

Smaller organization

Use a clear owner, a proportionate working record, built-in platform capability and a scheduled review. Sample real activity instead of creating duplicate paperwork for supporting utilities.

Mature or complex organization

Define service-level ownership, automated coverage reporting, integrated workflow, risk-based exceptions and independent assurance across business units and technology platforms.

Practical implementation checklist

• □ Define ownership, scope and operating criteria for supporting utilities.
• □ Implement continuity arrangement that fits the organization’s risks, services and working practices.
• □ Integrate the activity with relevant change, exception and review processes.
• □ Review performance and improve the arrangement when risks, technology or obligations change.
• □ Sample evidence has been checked for operation and effectiveness.
• □ Exceptions have owners, rationale, review dates and closure evidence.

Common implementation mistakes

• documenting supporting utilities without consistent operation
• unclear ownership or review frequency
• evidence that does not cover the full ISMS scope
• exceptions accepted without risk-based approval or follow-up

Related controls, clauses and resources