EvidenceSheet

7.1 Physical security perimeters

Requires security perimeters to be defined and used to protect any area holding information and the assets associated with it.

5
artefacts
0
held by a system
3
at each review
hard
to go live
Physical access / facilities
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 perimeter is physically sound, covering walls, doors, windows, roof and floor voids · Physical access / facilities
  • Records of inspection or testing of perimeter integrity · Physical access / facilities
  • Evidence covering shared and multi tenant buildings, including the boundary between the organisation and other occupants · Physical access / facilities

governing documentDocuments that govern the control

  • Definition of the security perimeters, with site plans or drawings showing the boundary of each area holding information and associated assets · Policy repository / GRC workspace
  • The basis for each perimeter, tied to the classification and criticality of what it protects · 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

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

6.8 Information security event reporting · 7.2 Physical entry