EvidenceSheet

7.11 Supporting utilities

Requires information processing facilities to be shielded from power loss and from other disruption arising when supporting utilities fail.

5
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Testing records demonstrating the arrangements work under load, including full transfer tests not just idle starts · Document repository
  • Maintenance and inspection records including fuel supply, battery condition and contract cover · Vendor register / contract repository

governing documentDocuments that govern the control

  • Identification of the supporting utilities each information processing facility depends on, covering power, cooling, water, telecommunications and ventilation · Policy repository / GRC workspace
  • The protective arrangements, such as uninterruptible power supply, generator, redundant feeds and cooling redundancy, matched to the availability requirement · Policy repository / GRC workspace
  • Alarm and monitoring evidence for utility failure, and the response procedure · Policy repository / GRC workspace

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

7.10 Storage media · 7.12 Cabling security