DCS-07 Controlled Access Points
Build physical security perimeters around people, data and systems, including a perimeter separating administrative and business areas from data storage and processing areas.
4
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
- Evidence the administrative to data area boundary is enforced · Document repository
- Assessment of perimeter effectiveness · Document repository
governing documentDocuments that govern the control
- Site plans showing defined perimeters and the internal separation · Policy repository / GRC workspace
- Physical controls implementing each perimeter · 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
- Single perimeter at the building edge with no internal separation
- Doors between zones held open for convenience
- Perimeter defined in documentation and absent in the building
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-06 Assets Cataloguing and Tracking · DCS-08 Equipment Identification