AC-11 Device lock
Requires a session to be locked after an organization-defined period of inactivity or on user command, hiding what was on screen, and to stay locked until the same user re-authenticates through the normal identification
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Sample of workstation configuration compliance results across the estate · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Screenshot or configuration export showing the pattern hiding the previous display · Identity provider / directory
governing documentDocuments that govern the control
- Endpoint policy object or MDM profile showing the configured inactivity lock timeout · Policy repository / GRC workspace
- Exception register for devices where the lock is relaxed, with approval and compensating measures · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Lock timeout enforced on corporate laptops but not on shared operational consoles or kiosks
- Screen lock configured as a user preference that a user can disable
- Re-entry allowed with a local unlock that bypasses central authentication
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 sheetAC-10 Concurrent Session Control. Limit the number of concurrent sessions for each [organization-defined] to [organization-defined] · AC-12 Session control