STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Red Hat Enterprise Linux 10 Security Technical Implementation Guide

V-281274

CAT II (Medium)

RHEL 10 must prevent a user from overriding the disabling of the graphical user interface autorun function.

Rule ID

SV-281274r1197245_rule

STIG

Red Hat Enterprise Linux 10 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000778CCI-001958

Discussion

Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., Transport Layer Security [TLS], WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators. Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163

Check Content

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 disables ability of the user to override the graphical user interface autorun setting.

Check that the autorun setting is set to prevent user modification with the following command:

$ gsettings writable org.gnome.desktop.media-handling autorun-never
false

If "autorun-never" is writable, the result is "true". 

If this is not documented with the information system security officer as an operational requirement, this is a finding.

Fix Text

Configure RHEL 10 so that the GNOME desktop does not allow a user to change the setting that disables autorun on removable media.

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/00-security-settings-lock" file to prevent user modification:

$ sudo vi /etc/dconf/db/local.d/locks/00-security-settings-lock

/org/gnome/desktop/media-handling/autorun-never

Update the dconf system databases:

$ sudo dconf update