DCS-11 Surveillance System
Surveillance systems are put in, kept running and actively operated at the datacenter's outer boundary and at every entry and exit point, so that attempts to get in or out without authority are detected.
Source: CSA CCM v4.1, DCS-11. 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
- CCTV retention configuration and sample footage retrieval · Physical access / facilities
- Security operations log of alarms and the responses taken · SIEM / log platform
periodic reviewEvidence produced at each review
- Maintenance and fault records for cameras and recorders · Document repository
- Review records of surveillance logs by security staff · SIEM / log platform
governing documentDocuments that govern the control
- Camera coverage map for perimeter and all entry and exit points · Document repository
First move
Common gaps auditors find
- Blind spots at side doors or loading bays
- Footage recorded but nobody monitors or reviews it
- Failed cameras left out of service for long periods
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 sheetDCS-10 Secure Area Authorization · DCS-12 Adverse Event Response Training