EvidenceSheet

9.2.4 Consoles in sensitive areas locked when not in use

Access to consoles located in sensitive areas is restricted by locking them when not in use, so that physical consoles cannot be used by unauthorized personnel.

5
artefacts
2
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Screen lock or session timeout configuration for consoles in sensitive areas · Cloud console / configuration management
  • Group policy or endpoint management export showing enforced lock settings · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

  • Observation record of an administrator attempting console login and finding it locked · Document repository

governing documentDocuments that govern the control

  • Definition and list of sensitive areas and the consoles sited in each · Document repository
  • Procedure requiring consoles to be locked when unattended · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

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.2.3 Physical access to networking and telecommunications hardware restricted · 9.3.1 Procedures are implemented for authorizing and managing physical access of personnel to the CDE, including: • Identifying personnel. • Managing changes to an individual's physical access requirements. • Revoking or terminating personnel identification. •