STIGQter STIGQter: STIG Summary: Red Hat Enterprise Linux 10 Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 01 Jul 2026:

RHEL 10 must initiate a session lock for graphical user interfaces when the screensaver is activated.

DISA Rule

SV-281280r1166792_rule

Vulnerability Number

V-281280

Group Title

SRG-OS-000029-GPOS-00010

Rule Version

RHEL-10-700770

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure RHEL 10 to initiate a session lock for graphical user interfaces when a screensaver is activated.

Note: The example below is using the database "local" for the system. If the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory.

Create a database to contain the systemwide screensaver settings (if it does not already exist) with the following command:

$ sudo vi /etc/dconf/db/local.d/00-screensaver

[org/gnome/desktop/screensaver]
lock-delay=uint32 5

The "uint32" must be included along with the integer key values as shown.

Update the system databases:

$ sudo dconf update

Check Contents

Note: This requirement assumes the use of the RHEL 10 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is not applicable.

Verify RHEL 10 initiates a session lock for graphical user interfaces when the screensaver is activated with the following command:

$ gsettings get org.gnome.desktop.screensaver lock-delay
uint32 5

If the "uint32" setting is not set to "5" or less, or is missing, this is a finding.

Vulnerability Number

V-281280

Documentable

False

Rule Version

RHEL-10-700770

Severity Override Guidance

Note: This requirement assumes the use of the RHEL 10 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is not applicable.

Verify RHEL 10 initiates a session lock for graphical user interfaces when the screensaver is activated with the following command:

$ gsettings get org.gnome.desktop.screensaver lock-delay
uint32 5

If the "uint32" setting is not set to "5" or less, or is missing, this is a finding.

Check Content Reference

M

Target Key

5733