DCS-15 Secure Utilities
Utility services such as power, water and telecommunications are protected, monitored, maintained and tested at scheduled intervals to show they continue to work.
Source: CSA CCM v4.1, DCS-15. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Utility service monitoring and alarm logs · SIEM / log platform
periodic reviewEvidence produced at each review
- UPS and generator test and load test records · Backup / DR tooling
- Fuel supply contracts and refuelling records · Vendor register / contract repository
governing documentDocuments that govern the control
- Maintenance schedules and completed work orders · Document repository
- Contract terms on utility testing where the customer relies on them · Vendor register / contract repository
First move
Common gaps auditors find
- Generators started but never tested under load
- Single utility feed with no monitoring of supply quality
- Test intervals defined but missed without follow-up
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