BigFix Compliance: Updated DISA STIG Checklist for RHEL 10, published 2026-11-19

Product:
BigFix Compliance

Title:
Updated DISA STIG Checklist for RHEL 10

Security Benchmark:
Red Hat Enterprise Linux 10 Security Technical Implementation Guide, V1R3

Published Sites:
DISA STIG Checklist for RHEL 10, site version 2
(The site version is provided for air-gap customers.)

Details:

Total Fixlets in Site: 426

Total New Fixlets: 4

Total Updated Fixlets:21

Total Deleted Fixlets: 1

New Fixlets:

RHEL 10 must generate audit records for successful and unsuccessful uses of the "useradd" command.

RHEL 10 must implement DoW-approved encryption in the OpenSSL package.

RHEL 10 must implement a FIPS 140-3-compliant systemwide cryptographic policy

RHEL 10 must have mail aliases to notify the information system security officer (ISSO) and system administrator (SA) (at a minimum) of an audit processing failure

Deleted Fixlets:

RHEL 10 must not have a Trivial File Transfer Protocol (TFTP) server package installed unless it is required by the mission, and if required, the TFTP daemon must be configured to operate in secure mode.

Updated Fixlets:

RHEL 10 must not assign an interactive login shell for system accounts.

RHEL 10 user account passwords for new users or password changes must have a 180-day maximum password lifetime restriction in /etc/login.defs.

RHEL 10 must, for user account passwords, have a 180-day maximum password lifetime restriction

RHEL 10 must be configured to use the shadow file to store only encrypted representations of passwords.

RHEL 10 must automatically exit interactive command shell user sessions after 10 minutes of inactivity.

RHEL 10 must have mail aliases to notify the information system security officer (ISSO) and system administrator (SA) (at a minimum) of an audit processing failure.

RHEL 10 must automatically lock graphical user sessions after 10 minutes of inactivity.

RHEL 10 must check the GNU Privacy Guard (GPG) signature of software packages originating from external software repositories before installation.

RHEL 10 must check the GNU Privacy Guard (GPG) signature of locally installed software packages before installation.

RHEL 10 must have GNU Privacy Guard (GPG) signature verification enabled for all software repositories.

RHEL 10 must remove all software components after updated versions have been installed.

RHEL 10 must not have a File Transfer Protocol (FTP) server package installed.

RHEL 10 must have the "rsyslog" package installed.

RHEL 10 must have the "pkcs11-provider" package installed.

RHEL 10 must implement DoW-approved encryption in the OpenSSL package.

RHEL 10 must generate audit records for successful and unsuccessful uses of the "gpasswd" command.

RHEL 10 must generate audit records for successful and unsuccessful uses of the "passwd" command.

RHEL 10 must generate audit records for all account creations, modifications, disabling, and termination events that affect the "/etc/sudoers.d/" directory.

RHEL 10 must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd".

RHEL 10 must require authentication upon booting into single-user and maintenance modes.

RHEL 10 must disable the systemd Ctrl-Alt-Delete burst key sequence.

Additional details:

Both analysis and remediation checks are included.

Some of the checks allow you to use the parameterized setting to enable customization for compliance evaluation. Note that parameterization and remediation actions require the creation of a custom site.

Improved a few checks by adding the pending restart feature to them. The pending restart feature works in the following ways:

The action results will show “Pending Restart” instead of “Fixed” for those checks which require OS reboot.

The check will show relevant for those endpoints until they are rebooted.

Post reboot of the endpoint the action results will show as “Fixed” and the check will be compliant.

Action to take:

To subscribe to the above site, you can use the License Overview Dashboard to enable and gather the site. Note that you must be entitled to the BigFix Compliance product and you must be using BigFix version 11.0.4 and later.

If you use custom sites, update your custom sites accordingly to use the latest content. You can synchronize your content by using the Synchronize Custom Checks wizard. For more information, see Using the Synchronize Custom Checks wizard

More information:
To know more about the BigFix Compliance SCM checklists, please see the following resources:

BigFix Forum:
https://forum.bigfix.com/c/release-announcements/compliance

BigFix Compliance SCM Checklists:

SCM Checklists

We hope you find this latest release of SCM content useful and effective.

Thank you!
– The BigFix Compliance team