user-initiated device locking
A security control mechanism by which a user, through deliberate physical action, places a system or endpoint into a locked state that blocks further logical access until re-authentication — as opposed to locks triggered automatically by elapsed inactivity timers or by proximity/environmental sensors. Device locks in general 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. User-initiated device locking is behavior- or policy-based and requires users to take physical action to initiate the device lock. In access-control frameworks it is used to distinguish the voluntary, human-triggered pathway to a session lock from automatic, timer-driven or sensor-driven pathways, and it is enforced either as a behavioral expectation or as an explicit organizational policy requirement applied under controls such as NIST SP 800-53 AC-11.
Framework senses
- §1 · attested_usage_reviewer_confirmed
- No definition is given in NIST SP 800-171r3. The term is attested in use at 1 citation in that document; a definition is pending curation.Increment 2: attested in NIST SP 800-171r3 without a glossary definition.
- §1 · web_lookup_draft
- A security control mechanism by which a user, through deliberate physical action, places a system or endpoint into a locked state that blocks further logical access until re-authentication — as opposed to locks triggered automatically by elapsed inactivity timers or by proximity/environmental sensors. Device locks in general 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. User-initiated device locking is behavior- or policy-based and requires users to take physical action to initiate the device lock. In access-control frameworks it is used to distinguish the voluntary, human-triggered pathway to a session lock from automatic, timer-driven or sensor-driven pathways, and it is enforced either as a behavioral expectation or as an explicit organizational policy requirement applied under controls such as NIST SP 800-53 AC-11.Drafted by the propose-term web lookup (PD-018); a curator confirms or replaces it.