ISO/IEC 27001:2022 A.7.11 — Supporting utilities

What this control requires

Information processing facilities shall be protected from power failures and other disruptions caused by failures in supporting utilities.

In plain English

Information processing facilities shall be protected from power failures and other disruptions caused by failures in supporting utilities. In practice, this means you can prove you policy information-level controls on a defined cadence.

Why it matters

ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored.

Within Physical controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.7.11) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Management. Document the trigger, the owner and the cadence.
• Physical. Document the trigger, the owner and the cadence.
• Scope: information, management.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Supporting utilities.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• SOC 2 (2017 TSC) C1.2 — Confidential Information Disposal
• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• GDPR Article 8 — Conditions applicable to child's consent in relation to information society services
• NIST SP 800-53 Rev. 5 RA-5(4) — Discoverable Information
• NIST SP 800-171 Rev. 3 3.13.15 — Session Authenticity

Related controls in ISO/IEC 27001:2022

• Annex A A.7.12 — Cabling security
• Annex A A.7.7 — Clear desk and clear screen
• Annex A A.7.13 — Equipment maintenance
• Annex A A.5.13 — Labelling of information
• Annex A A.5.37 — Documented operating procedures
• Annex A A.8.14 — Redundancy of information processing facilities

References

• ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022
• Catalogue identifier: Annex A A.7.11

Topics: governance riskenvironmental controlspolicy management