6.8.1 Secure areas
Secure area controls covering the security perimeter, entry, offices and facilities, protection against external and environmental threats, working in secure areas and delivery and loading areas apply as the base guidanc
3
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Perimeter and entry control evidence for areas holding personal data · Data governance / DLP tooling
governing documentDocuments that govern the control
- Working practices for secure areas · Document repository
- Delivery and loading area controls · Document repository
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
- Secure area designation applied to server rooms only, leaving records storage unclassified
- Entry logs kept but never reviewed
- Delivery areas providing an unescorted route past areas holding personal data
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