NIST 800-53 Rev 5
424 controls available
Device Lock
Access Control
Control Statement
Prevent further access to the system by {{ insert: param, ac-11_odp.01 }} ; and Retain the device lock until the user reestablishes access using established identification and authentication procedures.
Discussion
Device locks are temporary actions taken to prevent logical access to organizational systems when users stop work and move away from the immediate vicinity of those systems but do not want to log out because of the temporary nature of their absences. Device locks can be implemented at the operating system level or at the application level. A proximity lock may be used to initiate the device lock (e.g., via a Bluetooth-enabled device or dongle). User-initiated device locking is behavior or policy-based and, as such, requires users to take physical action to initiate the device lock. Device locks are not an acceptable substitute for logging out of systems, such as when organizations require users to log out at the end of workdays.
- Framework
- NIST SP 800-53 Rev 5
- Family
- Access Control
- Baselines
- moderate, high
Related Frameworks
6 paths across 2 frameworks
Related Frameworks
NIST 800-1711 mapping
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI5 mappings
- DISA · 2025-01-23 · disa_cci_list · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
- DISA · 2025-01-23 · disa_cci_list · equivalent
Related STIGs
153 STIGs reach this control through 5 CCIs. Expand a row to see the responsible NICE and O*NET roles.