A.7 Physical controls

A.7.11 Supporting utilities

Not mandatory by default – decided in your SoA

What it means in plain language

Protect IT from failures of supporting utilities such as power, cooling and telecommunications.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Information processing depends on utilities that can fail independently of the servers and applications they support. Power, cooling and communications outages may create a common failure across otherwise redundant systems. Understanding these dependencies helps the organisation choose proportionate resilience measures and safe shutdown arrangements, rather than assuming that backup hardware or a second connection automatically removes the underlying single point of failure.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Uninterruptible power capacity was sized for an earlier equipment load, and nobody has checked whether it supports the current shutdown or recovery requirement.
  • Two communications services use the same physical route or upstream dependency, so the claimed redundancy does not address a credible local outage.
  • Cooling or power alarms are monitored by a supplier, but escalation contacts and the organisation’s response responsibilities are undefined outside office hours.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Map utility dependencies for critical information-processing locations and services, including shared upstream components. Work with facilities and service owners to identify the impact of loss, acceptable interruption and the assumptions that continuity or recovery plans make about utility availability.
  • Assess resilience options against those requirements, such as alternate supplies, supported shutdown, cooling safeguards or diverse communications. Involve competent specialists for electrical and building work. Record why the chosen measures are sufficient and what residual dependency remains outside the organisation’s control.
  • Maintain and test protective arrangements under safe, authorised conditions that reflect current load and service needs. Document the test scope, results and limitations. A successful indicator light or supplier assertion should not substitute for evidence that the required operating or shutdown sequence works.
  • Define alarm handling, escalation and service restoration responsibilities with internal teams and providers. Review them after equipment changes or utility incidents. Track defects and test failures into action plans, and update recovery assumptions when actual capacity or response performance differs from expectations.

What an auditor will ask to see

  • A utility-dependency assessment linking critical processing services to power, cooling and communications requirements, including shared infrastructure and identified single points of failure.
  • Maintenance and controlled test records demonstrating actual capacity, alarm operation or safe shutdown performance, with the equipment load and test limitations clearly documented.
  • Supplier agreements and response records showing who receives utility alerts, how faults are escalated and how unresolved resilience gaps influence continuity and recovery decisions.

Baseline documents in the kit

These free kit documents help you document or evidence A.7.11. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.30 — ICT readiness for business continuity and A.8.14 — Redundancy of information processing facilities. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.