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 prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface.

DISA Rule

SV-281277r1166783_rule

Vulnerability Number

V-281277

Group Title

SRG-OS-000028-GPOS-00009

Rule Version

RHEL-10-700740

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure RHEL 10 to prevent a user from overriding settings for graphical user interfaces.

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

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.

Update the "/etc/dconf/db/local.d/locks/session" file to prevent nonprivileged users from modifying the screensaver lock:

$ sudo vi /etc/dconf/db/local.d/locks/session

/org/gnome/desktop/screensaver/lock-enabled

Run the following command to update the database:

$ sudo dconf update

Check Contents

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

Verify RHEL 10 prevents a user from overriding the screensaver lock-enabled setting with the following command:

$ gsettings writable org.gnome.desktop.screensaver lock-enabled
false

If "lock-enabled" is writable, and the result is "true", this is a finding.

Vulnerability Number

V-281277

Documentable

False

Rule Version

RHEL-10-700740

Severity Override Guidance

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

Verify RHEL 10 prevents a user from overriding the screensaver lock-enabled setting with the following command:

$ gsettings writable org.gnome.desktop.screensaver lock-enabled
false

If "lock-enabled" is writable, and the result is "true", this is a finding.

Check Content Reference

M

Target Key

5733