EvidenceSheet

9.1.2 Roles and responsibilities for performing activities in Requirement 9 are documented, assigned, and understood

Roles and responsibilities for performing activities in Requirement 9 are documented, assigned, and understood.

4
artefacts
0
held by a system
4
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

  • Documented descriptions of roles for Requirement 9 activities, covering entry authorisation, visitor management, media inventory and device inspection · Physical access / facilities
  • Assignment records naming who holds each role · Physical access / facilities
  • Interview confirmation that assigned personnel understand their day to day physical security responsibilities · Physical access / facilities
  • Evidence of coverage outside business hours and at each site · Physical access / facilities

governing documentDocuments that govern the control

none for this control

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

9.1.1 All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties · 9.2.1 Appropriate facility entry controls are in place to restrict physical access to systems in the CDE