PS-03 Perimeter Protection
Build the outer shell of cloud service buildings to physically resist and detect intrusion, with external doors, windows, walls and locking mechanisms that withstand a burglary attempt for at least ten minutes.
4
artefacts
0
held by a system
1
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
- Maintenance and function test records for perimeter alarm contacts · Physical access / facilities
governing documentDocuments that govern the control
- Resistance class certificates for external doors, windows and locking cylinders · Policy repository / GRC workspace
- Shell construction drawings showing the wall, roof and floor build up · Policy repository / GRC workspace
- Coverage plan for intrusion detection on the outer skin of the building · 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
- Resistance ratings claimed for the main entrance while service and loading doors are ordinary construction
- False ceilings or raised floors permitting a rated wall to be bypassed
- Roof lights and ventilation openings excluded from the resistance assessment
- Alarm zones disabled during building works and never re enabled afterwards
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