Screen Lock Not Enforced

Devices are not set by policy to lock after a period of inactivity, so an unattended session stays open to anyone with physical access.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator
CVSS 4.01 CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-613: Insufficient Session Expiration
OWASP Top 10A07:2025 Authentication Failures
CategorySecurity Misconfiguration

Description

The device is not configured by central policy to lock the user's session after a period of inactivity. Unless users remember to lock their screens each time they step away, an unattended workstation or laptop stays signed in, and anyone with physical access to it can act as the signed-in user: reading and sending email, opening files and internal applications, approving requests in the user's name, or running commands. A keystroke-injection device plugged into an unlocked session can install malware or create persistence within seconds, and where the user has administrative rights, the whole device and everything that account can reach is exposed.

Related forms are a timeout that is very long, one that users can change or switch off, and a screen saver that starts without requiring the user to sign in again when it ends. Exploitation needs physical presence at a moment when a device has been left unlocked, so the risk is greatest in shared offices, public areas and for staff who work in public places, and lowest where physical access is tightly controlled.

On Windows the lock is normally enforced through the security policy Interactive logon: Machine inactivity limit or the screen saver policies under User Configuration\Administrative Templates\Control Panel\Personalization; on macOS through a configuration profile; and on Linux desktops through settings such as the GNOME idle-delay and lock-enabled keys. The weakness is identified by reviewing the effective policy on a sample of devices, for example with gpresult or the device management console, and by leaving a session idle to see whether it locks. Physical security reviews often find it directly, as unlocked and unattended devices.

Remediation

Enforce an automatic lock on every workstation and laptop through central policy, so that protection does not depend on each user:

  • Windows: set Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Machine inactivity limit to the organisation's chosen timeout. The CIS Benchmarks recommend 900 seconds (15 minutes) or less, but not 0, which turns the limit off. The screen saver policies Enable screen saver, Password protect the screen saver and Screen saver timeout achieve the same per user, and Intune offers equivalent settings for managed devices.
  • macOS: deploy a configuration profile that starts the screen saver after the chosen idle time and requires a password immediately when it starts or the display sleeps.
  • Linux desktops: set the GNOME keys org.gnome.desktop.session idle-delay and org.gnome.desktop.screensaver lock-enabled as system defaults through dconf and lock them so that users cannot change them, or use the equivalent for the desktop in use.
  • Use shorter timeouts for privileged access workstations and for devices in public areas.
  • Remind staff to lock their screen whenever they leave the device (Windows logo key + L on Windows, Control + Command + Q on macOS).

Confirm the fix by checking the applied policy on a sample of devices and leaving a test session idle beyond the timeout to confirm that it locks and requires authentication to resume.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Windows and Linux Hosts Findings

Every Windows and Linux Hosts finding