DCS-10 Surveillance System
Operate surveillance across the datacentre outer perimeter and every entry and exit point to detect attempts at unauthorised entry or exit.
4
artefacts
3
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Recording retention and its configuration · Cloud console / configuration management
- Evidence surveillance is monitored or alerts are acted on · SIEM / log platform
- Maintenance records showing the system is operational · Document repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Camera coverage plan against the perimeter and all access points · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Blind spots at access points that the coverage plan does not acknowledge
- Cameras recording with nobody reviewing and no alerting
- Failed cameras unnoticed because there is no health check
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-09 Secure Area Authorization · DCS-11 Unauthorized Access Response Training