A.7.11 Supporting utilities
Protect information processing facilities from power failures and other utility disruptions.
13
artefacts
3
held by a system
5
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
- Utility outage log · SIEM / log platform
- HVAC temperature and humidity logs · SIEM / log platform
- Data centre environmental monitoring system reports · Physical access / facilities
periodic reviewEvidence produced at each review
- UPS capacity assessment report · Backup / DR tooling
- Generator load test results · Backup / DR tooling
- Real-time power monitoring dashboard screenshots · SIEM / log platform
- Annual UPS service contract · Backup / DR tooling
- Fire suppression system inspection record · Physical access / facilities
governing documentDocuments that govern the control
- Battery replacement schedule · Policy repository / GRC workspace
- Power redundancy design diagram · Policy repository / GRC workspace
- Alarm escalation procedure · Policy repository / GRC workspace
- Service level agreement for generator maintenance · Policy repository / GRC workspace
- Third-party maintenance provider certification · Vendor register / contract repository
First move
Mostly documents and reviews. Pull the 3 system-held artefacts from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- No documented testing of backup power
- Reliance on single power source without redundancy
- Outdated maintenance records
- Missing real-time monitoring alerts
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