Guide to the Secure Configuration of Red Hat Enterprise Linux 9
with profile DISA STIG for Red Hat Enterprise Linux 9This profile contains configuration checks that align to the DISA STIG for Red Hat Enterprise Linux 9 V2R7. In addition to being applicable to Red Hat Enterprise Linux 9, this configuration baseline is applicable to the operating system tier of Red Hat technologies that are based on Red Hat Enterprise Linux 9, such as: - Red Hat Enterprise Linux Server - Red Hat Enterprise Linux Workstation and Desktop - Red Hat Enterprise Linux for HPC - Red Hat Storage - Red Hat Containers with a Red Hat Enterprise Linux 9 image
The SCAP Security Guide Project
https://www.open-scap.org/security-policies/scap-security-guide
https://www.open-scap.org/security-policies/scap-security-guide
This guide presents a catalog of security-relevant
configuration settings for Red Hat Enterprise Linux 9. It is a rendering of
content structured in the eXtensible Configuration Checklist Description Format (XCCDF)
in order to support security automation. The SCAP content is
is available in the
Providing system administrators with such guidance informs them how to securely configure systems under their control in a variety of network roles. Policy makers and baseline creators can use this catalog of settings, with its associated references to higher-level security control catalogs, in order to assist them in security baseline creation. This guide is a catalog, not a checklist, and satisfaction of every item is not likely to be possible or sensible in many operational scenarios. However, the XCCDF format enables granular selection and adjustment of settings, and their association with OVAL and OCIL content provides an automated checking capability. Transformations of this document, and its associated automated checking content, are capable of providing baselines that meet a diverse set of policy objectives. Some example XCCDF Profiles, which are selections of items that form checklists and can be used as baselines, are available with this guide. They can be processed, in an automated fashion, with tools that support the Security Content Automation Protocol (SCAP). The DISA STIG, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
scap-security-guide package which is developed at
https://www.open-scap.org/security-policies/scap-security-guide.
Providing system administrators with such guidance informs them how to securely configure systems under their control in a variety of network roles. Policy makers and baseline creators can use this catalog of settings, with its associated references to higher-level security control catalogs, in order to assist them in security baseline creation. This guide is a catalog, not a checklist, and satisfaction of every item is not likely to be possible or sensible in many operational scenarios. However, the XCCDF format enables granular selection and adjustment of settings, and their association with OVAL and OCIL content provides an automated checking capability. Transformations of this document, and its associated automated checking content, are capable of providing baselines that meet a diverse set of policy objectives. Some example XCCDF Profiles, which are selections of items that form checklists and can be used as baselines, are available with this guide. They can be processed, in an automated fashion, with tools that support the Security Content Automation Protocol (SCAP). The DISA STIG, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
Do not attempt to implement any of the settings in
this guide without first testing them in a non-operational environment. The
creators of this guidance assume no responsibility whatsoever for its use by
other parties, and makes no guarantees, expressed or implied, about its
quality, reliability, or any other characteristic.
Evaluation Characteristics
| Evaluation target | unknown |
|---|---|
| Target ID | podman-image://5c7ae581a87ae058a54998f610aec1b666c3dee10794cf96b8250a55c59b5b09 [localhost/ubi9-stig-fips:staging-745eebd580fa9c48ee14931c53bd0003247fb7b8] |
| Benchmark URL | #scap_org.open-scap_comp_ssg-rhel9-xccdf.xml |
| Benchmark ID | xccdf_org.ssgproject.content_benchmark_RHEL-9 |
| Benchmark version | 0.1.80 |
| Profile ID | xccdf_org.ssgproject.content_profile_stig |
| Started at | 2026-06-11T16:45:07+00:00 |
| Finished at | 2026-06-11T16:45:09+00:00 |
| Performed by | unknown user |
| Test system | cpe:/a:redhat:openscap:1.3.13 |
CPE Platforms
- cpe:/o:redhat:enterprise_linux:9
Addresses
Compliance and Scoring
There were no failed or uncertain rules. It seems that no action is necessary.
Rule results
Score
| Scoring system | Score | Maximum | Percent |
|---|---|---|---|
| urn:xccdf:scoring:default | 100.000000 | 100.000000 |
Rule Overview
Result Details
Install AIDExccdf_org.ssgproject.content_rule_package_aide_installed mediumCCE-90843-4
Install AIDE
| Rule ID | xccdf_org.ssgproject.content_rule_package_aide_installed | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90843-4 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | The aide package can be installed with the following command:
$ sudo dnf install aide | ||||||||||||||||||||||||||||||||||
| Rationale | The AIDE package must be installed if it is to be available for integrity checking. |
Build and Test AIDE Databasexccdf_org.ssgproject.content_rule_aide_build_database mediumCCE-83438-2
Build and Test AIDE Database
| Rule ID | xccdf_org.ssgproject.content_rule_aide_build_database | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83438-2 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | Run the following command to generate a new database:
$ sudo /usr/sbin/aide --initBy default, the database will be written to the file /var/lib/aide/aide.db.new.gz.
Storing the database, the configuration file /etc/aide.conf, and the binary
/usr/sbin/aide
(or hashes of these files), in a secure location (such as on read-only media) provides additional assurance about their integrity.
The newly-generated database can be installed as follows:
$ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gzTo initiate a manual check, run the following command: $ sudo /usr/sbin/aide --checkIf this check produces any unexpected output, investigate. | ||||||||||||||||||||||||||||||||
| Rationale | For AIDE to be effective, an initial database of "known-good" information about files
must be captured and it should be able to be verified against the installed files. | ||||||||||||||||||||||||||||||||
| Warnings | warning
In RHEL Image Mode (bootc) systems, the AIDE database must be regenerated after each system update.
Image Mode systems receive updates through new container images that may include modified files.
After applying system updates, run the following commands to regenerate the AIDE database:
$ sudo /usr/sbin/aide --initThen replace the existing database: $ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gzFailure to regenerate the AIDE database after updates will result in false positive alerts for legitimate system changes introduced by the update process. |
Configure AIDE to Verify the Audit Toolsxccdf_org.ssgproject.content_rule_aide_check_audit_tools mediumCCE-87757-1
Configure AIDE to Verify the Audit Tools
| Rule ID | xccdf_org.ssgproject.content_rule_aide_check_audit_tools | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-87757-1 | ||||||||||
| References: |
| ||||||||||
| Description | The operating system file integrity tool must be configured to protect the integrity of the audit tools. | ||||||||||
| Rationale | Protecting the integrity of the tools used for auditing purposes is a
critical step toward ensuring the integrity of audit information. Audit
information includes all information (e.g., audit records, audit settings,
and audit reports) needed to successfully audit information system
activity.
Audit tools include but are not limited to vendor-provided and open-source
audit tools needed to successfully view and manipulate audit information
system activity and records. Audit tools include custom queries and report
generators.
It is not uncommon for attackers to replace the audit tools or inject code
into the existing tools to provide the capability to hide or erase system
activity from the audit logs.
To address this risk, audit tools must be cryptographically signed to
provide the capability to identify when the audit tools have been modified,
manipulated, or replaced. An example is a checksum hash of the file or
files. |
Configure Notification of Post-AIDE Scan Detailsxccdf_org.ssgproject.content_rule_aide_scan_notification mediumCCE-90844-2
Configure Notification of Post-AIDE Scan Details
| Rule ID | xccdf_org.ssgproject.content_rule_aide_scan_notification | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-90844-2 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | AIDE should notify appropriate personnel of the details of a scan after the scan has been run.
If AIDE has already been configured for periodic execution in /etc/crontab, append the
following line to the existing AIDE line:
| /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhostOtherwise, add the following line to /etc/crontab:
05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhostAIDE can be executed periodically through other means; this is merely one example. | ||||||||||||||||||||||||
| Rationale | Unauthorized changes to the baseline configuration could make the system vulnerable
to various attacks or allow unauthorized access to the operating system. Changes to
operating system configurations can have unintended side effects, some of which may
be relevant to security.
Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item. |
Configure AIDE to Use FIPS 140-2 for Validating Hashesxccdf_org.ssgproject.content_rule_aide_use_fips_hashes mediumCCE-88939-4
Configure AIDE to Use FIPS 140-2 for Validating Hashes
| Rule ID | xccdf_org.ssgproject.content_rule_aide_use_fips_hashes | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-88939-4 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | By default, the sha512 option is added to the NORMAL ruleset in AIDE.
If using a custom ruleset or the sha512 option is missing, add sha512
to the appropriate ruleset.
For example, add sha512 to the following line in /etc/aide.conf:
NORMAL = FIPSR+sha512AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. | ||||||||||||||||||||||
| Rationale | File integrity tools use cryptographic hashes for verifying file contents and directories
have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes. | ||||||||||||||||||||||
| Warnings | warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
Configure AIDE to Verify Access Control Lists (ACLs)xccdf_org.ssgproject.content_rule_aide_verify_acls lowCCE-90837-6
Configure AIDE to Verify Access Control Lists (ACLs)
| Rule ID | xccdf_org.ssgproject.content_rule_aide_verify_acls | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||
| Identifiers: | CCE-90837-6 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | By default, the acl option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the acl option is missing, add acl
to the appropriate ruleset.
For example, add acl to the following line in /etc/aide.conf:
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds acl to all rule sets available in
/etc/aide.conf
| ||||||||||||||||||||||
| Rationale | ACLs can provide permissions beyond those permitted through the file mode and must be
verified by the file integrity tools. |
Configure AIDE to Verify Extended Attributesxccdf_org.ssgproject.content_rule_aide_verify_ext_attributes lowCCE-83439-0
Configure AIDE to Verify Extended Attributes
| Rule ID | xccdf_org.ssgproject.content_rule_aide_verify_ext_attributes | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||
| Identifiers: | CCE-83439-0 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | By default, the xattrs option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the xattrs option is missing, add xattrs
to the appropriate ruleset.
For example, add xattrs to the following line in /etc/aide.conf:
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds xattrs to all rule sets available in
/etc/aide.conf
| ||||||||||||||||||||||
| Rationale | Extended attributes in file systems are used to contain arbitrary data and file metadata
with security implications. |
Audit Tools Must Be Group-owned by Rootxccdf_org.ssgproject.content_rule_file_audit_tools_group_ownership mediumCCE-86240-9
Audit Tools Must Be Group-owned by Root
| Rule ID | xccdf_org.ssgproject.content_rule_file_audit_tools_group_ownership | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86240-9 | ||||||||
| References: |
| ||||||||
| Description | Red Hat Enterprise Linux 9 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Audit tools must have the correct group owner. | ||||||||
| Rationale | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data.
Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit information. |
Audit Tools Must Be Owned by Rootxccdf_org.ssgproject.content_rule_file_audit_tools_ownership mediumCCE-86263-1
Audit Tools Must Be Owned by Root
| Rule ID | xccdf_org.ssgproject.content_rule_file_audit_tools_ownership | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86263-1 | ||||||||
| References: |
| ||||||||
| Description | Red Hat Enterprise Linux 9 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.
Audit tools must have the correct owner. | ||||||||
| Rationale | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data.
Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit information. |
Enable Dracut FIPS Modulexccdf_org.ssgproject.content_rule_enable_dracut_fips_module highCCE-86547-7
Enable Dracut FIPS Module
| Rule ID | xccdf_org.ssgproject.content_rule_enable_dracut_fips_module | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | high | ||||||||||||||
| Identifiers: | CCE-86547-7 | ||||||||||||||
| References: |
| ||||||||||||||
| Description |
Red Hat Enterprise Linux 9 has an installation-time kernel flag that can enable FIPS mode.
The installer must be booted with fips=1 for the system to have FIPS mode
enabled. Enabling FIPS mode on a preexisting system is not supported. If
this rule fails on an installed system, then this is a permanent
finding and cannot be fixed.
To enable FIPS, the system requires that the fips module is added in dracut configuration.
Check if /etc/dracut.conf.d/40-fips.conf contain add_dracutmodules+=" fips "
| ||||||||||||||
| Rationale | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to
protect data. The operating system must implement cryptographic modules adhering to the higher
standards approved by the federal government since this provides assurance they have been tested
and validated. | ||||||||||||||
| Warnings | warning
To configure the operating system to run in FIPS 140 mode, the kernel parameter "fips=1" needs to be added during its installation.
Enabling FIPS mode on a preexisting system involves a number of modifications to it and therefore is not supported. warning
System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use cryptographic-based security
systems to protect sensitive information in computer and telecommunication systems
(including voice systems) as defined in Section 5131 of the Information Technology
Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing
and implementing cryptographic modules that Federal departments and agencies operate or are
operated for them under contract.
See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by a vendor that has
undergone this certification. This means providing documentation, test results, design
information, and independent third party review by an accredited lab. While open source
software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to
this process. |
Enable FIPS Modexccdf_org.ssgproject.content_rule_enable_fips_mode highCCE-88742-2
Enable FIPS Mode
| Rule ID | xccdf_org.ssgproject.content_rule_enable_fips_mode | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | high | ||||||||||||||
| Identifiers: | CCE-88742-2 | ||||||||||||||
| References: |
| ||||||||||||||
| Description |
Red Hat Enterprise Linux 9 has an installation-time kernel flag that can enable FIPS mode.
The installer must be booted with fips=1 for the system to have FIPS mode
enabled. Enabling FIPS mode on a preexisting system is not supported. If
this rule fails on an installed system, then this is a permanent
finding and cannot be fixed.
To enable FIPS mode at bootable container build time configure fips=1 kernel argument
in /usr/lib/bootc/kargs.d/01-fips.toml:
kargs = ["fips=1"]Then set the cryptographic policy to FIPS:STIG:
update-crypto-policies --no-reload --set FIPS:STIG
| ||||||||||||||
| Rationale | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to
protect data. The operating system must implement cryptographic modules adhering to the higher
standards approved by the federal government since this provides assurance they have been tested
and validated. | ||||||||||||||
| Warnings | warning
To configure Red Hat Enterprise Linux 9 to run in FIPS 140 mode, the kernel parameter "fips=1" needs to be added during its installation.
Only enabling FIPS 140 mode during the Red Hat Enterprise Linux 9 installation ensures that the system generates all keys with FIPS-approved algorithms and continuous monitoring tests in place.
Enabling FIPS mode on a preexisting system involves a number of modifications to it and therefore is not supported. warning
This rule DOES NOT CHECK if the components of the operating system are FIPS certified.
You can find the list of FIPS certified modules at
https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search.
This rule checks if the system is running in FIPS mode. |
FIPS Must Use a Supported Subpolicyxccdf_org.ssgproject.content_rule_fips_crypto_subpolicy mediumCCE-86538-6
FIPS Must Use a Supported Subpolicy
| Rule ID | xccdf_org.ssgproject.content_rule_fips_crypto_subpolicy | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86538-6 | ||||||
| References: |
| ||||||
| Description | Sub-policies can be used to modify existing crypto policies.
Some sub-policies such as NO-ENFORCE-EMS reduce the security of the system and should not be used.
Other such as AD-SUPPORT should only be enabled if operationally required.
The OSPP, NO-SHA1, NO-CAMELLIA, and ECDHE-ONLY are allowed by this rule. | ||||||
| Rationale | Sub-policies can cause insecure ciphers to be used. | ||||||
| Warnings | warning
This rule does not have a remediation. |
Implement STIG Sub Crypto Policyxccdf_org.ssgproject.content_rule_fips_custom_stig_sub_policy mediumCCE-86570-9
Implement STIG Sub Crypto Policy
| Rule ID | xccdf_org.ssgproject.content_rule_fips_custom_stig_sub_policy | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86570-9 | ||||||
| References: |
| ||||||
| Description | Create a custom cryptographic policy to follow the guidance from DISA. | ||||||
| Rationale | To follow STIG policy. |
Set kernel parameter 'crypto.fips_enabled' to 1xccdf_org.ssgproject.content_rule_sysctl_crypto_fips_enabled highCCE-83441-6
Set kernel parameter 'crypto.fips_enabled' to 1
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_crypto_fips_enabled | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | high | ||||||||||
| Identifiers: | CCE-83441-6 | ||||||||||
| References: |
| ||||||||||
| Description | System running in FIPS mode is indicated by kernel parameter
'crypto.fips_enabled'. This parameter should be set to 1 in FIPS mode.
Red Hat Enterprise Linux 9 has an installation-time kernel flag that can enable FIPS mode.
The installer must be booted with fips=1 for the system to have FIPS mode
enabled. Enabling FIPS mode on a preexisting system is not supported. If
this rule fails on an installed system, then this is a permanent
finding and cannot be fixed.
To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel boot
parameters during system installation so key generation is done with FIPS-approved algorithms
and continuous monitoring tests in place. | ||||||||||
| Rationale | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to
protect data. The operating system must implement cryptographic modules adhering to the higher
standards approved by the federal government since this provides assurance they have been tested
and validated. | ||||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use cryptographic-based security
systems to protect sensitive information in computer and telecommunication systems
(including voice systems) as defined in Section 5131 of the Information Technology
Management Reform Act of 1996, Public Law 104-106. This standard shall be used in designing
and implementing cryptographic modules that Federal departments and agencies operate or are
operated for them under contract.
See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by a vendor that has
undergone this certification. This means providing documentation, test results, design
information, and independent third party review by an accredited lab. While open source
software is capable of meeting this, it does not meet FIPS-140 unless the vendor submits to
this process. |
Install crypto-policies packagexccdf_org.ssgproject.content_rule_package_crypto-policies_installed mediumCCE-83442-4
Install crypto-policies package
| Rule ID | xccdf_org.ssgproject.content_rule_package_crypto-policies_installed | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-package_crypto-policies_installed:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83442-4 | ||||||||
| References: |
| ||||||||
| Description | The crypto-policies package can be installed with the following command:
$ sudo dnf install crypto-policies | ||||||||
| Rationale | Centralized cryptographic policies simplify applying secure ciphers across an operating system and
the applications that run on that operating system. Use of weak or untested encryption algorithms
undermines the purposes of utilizing encryption to protect data. |
OVAL test results details
package crypto-policies is installed oval:ssg-test_package_crypto-policies_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| not evaluated | crypto-policies | noarch | (none) | 1.gitea0f072.el9_8 | 20260224 | 0:20260224-1.gitea0f072.el9_8 | 199e2f91fd431d51 | crypto-policies-0:20260224-1.gitea0f072.el9_8.noarch |
Configure BIND to use System Crypto Policyxccdf_org.ssgproject.content_rule_configure_bind_crypto_policy highCCE-83451-5
Configure BIND to use System Crypto Policy
| Rule ID | xccdf_org.ssgproject.content_rule_configure_bind_crypto_policy | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | high | ||||||||||
| Identifiers: | CCE-83451-5 | ||||||||||
| References: |
| ||||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
BIND is supported by crypto policy, but the BIND configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that the /etc/named.conf
includes the appropriate configuration:
In the options section of /etc/named.conf, make sure that the following line
is not commented out or superseded by later includes:
include "/etc/crypto-policies/back-ends/bind.config";
| ||||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the BIND service violate expectations,
and makes system configuration more fragmented. |
Configure System Cryptography Policyxccdf_org.ssgproject.content_rule_configure_crypto_policy highCCE-83450-7
Configure System Cryptography Policy
| Rule ID | xccdf_org.ssgproject.content_rule_configure_crypto_policy | ||||||||||||||||||||
| Result | pass | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| OVAL Definition ID | oval:ssg-configure_crypto_policy:def:1 | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | high | ||||||||||||||||||||
| Identifiers: | CCE-83450-7 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | To configure the system cryptography policy to use ciphers only from the FIPS:STIG
policy, run the following command:
$ sudo update-crypto-policies --set FIPS:STIG
The rule checks if settings for selected crypto policy are configured as expected. Configuration files in the /etc/crypto-policies/back-ends are either symlinks to correct files provided by Crypto-policies package or they are regular files in case crypto policy customizations are applied.
Crypto policies may be customized by crypto policy modules, in which case it is delimited from the base policy using a colon. | ||||||||||||||||||||
| Rationale | Centralized cryptographic policies simplify applying secure ciphers across an operating system and
the applications that run on that operating system. Use of weak or untested encryption algorithms
undermines the purposes of utilizing encryption to protect data. | ||||||||||||||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
OVAL test results details
check for crypto policy correctly configured in /etc/crypto-policies/config oval:ssg-test_configure_crypto_policy:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/crypto-policies/config | FIPS:STIG |
check for crypto policy correctly configured in /etc/crypto-policies/state/current oval:ssg-test_configure_crypto_policy_current:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/crypto-policies/state/current | FIPS:STIG |
Check if update-crypto-policies has been run oval:ssg-test_crypto_policies_updated:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Var ref | Value |
|---|---|---|
| true | oval:ssg-variable_crypto_policies_config_file_timestamp:var:1 | 1781196292 |
Check if /etc/crypto-policies/back-ends/nss.config exists oval:ssg-test_crypto_policy_nss_config:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Type | UID | GID | Size (B) | Permissions |
|---|---|---|---|---|---|---|
| not evaluated | /etc/crypto-policies/back-ends/nss.config | regular | 0 | 0 | 352 | rw-r--r-- |
Configure Libreswan to use System Crypto Policyxccdf_org.ssgproject.content_rule_configure_libreswan_crypto_policy highCCE-83446-5
Configure Libreswan to use System Crypto Policy
| Rule ID | xccdf_org.ssgproject.content_rule_configure_libreswan_crypto_policy | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | high | ||||||||||||
| Identifiers: | CCE-83446-5 | ||||||||||||
| References: |
| ||||||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
Libreswan is supported by system crypto policy, but the Libreswan configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that the /etc/ipsec.conf
includes the appropriate configuration file.
In /etc/ipsec.conf, make sure that the following line
is not commented out or superseded by later includes:
include /etc/crypto-policies/back-ends/libreswan.config
| ||||||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the Libreswan
service violate expectations, and makes system configuration more
fragmented. |
Configure SSH Client to Use FIPS 140 Validated Ciphers: openssh.configxccdf_org.ssgproject.content_rule_harden_sshd_ciphers_openssh_conf_crypto_policy highCCE-90125-6
Configure SSH Client to Use FIPS 140 Validated Ciphers: openssh.config
| Rule ID | xccdf_org.ssgproject.content_rule_harden_sshd_ciphers_openssh_conf_crypto_policy | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-harden_sshd_ciphers_openssh_conf_crypto_policy:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | high | ||||||||
| Identifiers: | CCE-90125-6 | ||||||||
| References: |
| ||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/openssh.config contains the following
line and is not commented out:
Ciphers aes256-gcm@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr
| ||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the OpenSSH client
violate expectations, and makes system configuration more fragmented. By
specifying a cipher list with the order of ciphers being in a “strongest to
weakest” orientation, the system will automatically attempt to use the
strongest cipher for securing SSH connections. | ||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract.
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
OVAL test results details
test the value of Ciphers setting in the /etc/crypto-policies/back-ends/openssh.config file oval:ssg-test_harden_sshd_ciphers_openssh_conf_crypto_policy:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/crypto-policies/back-ends/openssh.config | Ciphers aes256-gcm@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr |
Configure SSH Server to Use FIPS 140-2 Validated Ciphers: opensshserver.configxccdf_org.ssgproject.content_rule_harden_sshd_ciphers_opensshserver_conf_crypto_policy mediumCCE-87332-3
Configure SSH Server to Use FIPS 140-2 Validated Ciphers: opensshserver.config
| Rule ID | xccdf_org.ssgproject.content_rule_harden_sshd_ciphers_opensshserver_conf_crypto_policy | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87332-3 | ||||||||
| References: |
| ||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oCiphers=aes256-gcm@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr
| ||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the OpenSSH server
violate expectations, and makes system configuration more fragmented. By
specifying a cipher list with the order of ciphers being in a “strongest to
weakest” orientation, the system will automatically attempt to use the
strongest cipher for securing SSH connections. | ||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.configxccdf_org.ssgproject.content_rule_harden_sshd_macs_openssh_conf_crypto_policy mediumCCE-86208-6
Configure SSH Client to Use FIPS 140-2 Validated MACs: openssh.config
| Rule ID | xccdf_org.ssgproject.content_rule_harden_sshd_macs_openssh_conf_crypto_policy | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-harden_sshd_macs_openssh_conf_crypto_policy:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86208-6 | ||||||||
| References: |
| ||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/openssh.config contains the following
line and is not commented out:
MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-512
| ||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the OpenSSH
client violate expectations, and makes system configuration more
fragmented. | ||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
OVAL test results details
test the value of MACs setting in the /etc/crypto-policies/back-ends/openssh.config file oval:ssg-test_harden_sshd_macs_openssh_conf_crypto_policy:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/crypto-policies/back-ends/openssh.config | MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-512 |
Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.configxccdf_org.ssgproject.content_rule_harden_sshd_macs_opensshserver_conf_crypto_policy mediumCCE-87567-4
Configure SSH Server to Use FIPS 140-2 Validated MACs: opensshserver.config
| Rule ID | xccdf_org.ssgproject.content_rule_harden_sshd_macs_opensshserver_conf_crypto_policy | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87567-4 | ||||||||
| References: |
| ||||||||
| Description | Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.
To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oMACS=hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-512
| ||||||||
| Rationale | Overriding the system crypto policy makes the behavior of the OpenSSH
server violate expectations, and makes system configuration more
fragmented. | ||||||||
| Warnings | warning
The system needs to be rebooted for these changes to take effect. warning
System Crypto Modules must be provided by a vendor that undergoes
FIPS-140 certifications.
FIPS-140 is applicable to all Federal agencies that use
cryptographic-based security systems to protect sensitive information
in computer and telecommunication systems (including voice systems) as
defined in Section 5131 of the Information Technology Management Reform
Act of 1996, Public Law 104-106. This standard shall be used in
designing and implementing cryptographic modules that Federal
departments and agencies operate or are operated for them under
contract. See https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf
To meet this, the system has to have cryptographic software provided by
a vendor that has undergone this certification. This means providing
documentation, test results, design information, and independent third
party review by an accredited lab. While open source software is
capable of meeting this, it does not meet FIPS-140 unless the vendor
submits to this process. |
The Installed Operating System Is Vendor Supportedxccdf_org.ssgproject.content_rule_installed_OS_is_vendor_supported highCCE-83453-1
The Installed Operating System Is Vendor Supported
| Rule ID | xccdf_org.ssgproject.content_rule_installed_OS_is_vendor_supported | ||||||||||||||||||
| Result | pass | ||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||
| OVAL Definition ID | oval:ssg-installed_OS_is_vendor_supported:def:1 | ||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||
| Severity | high | ||||||||||||||||||
| Identifiers: | CCE-83453-1 | ||||||||||||||||||
| References: |
| ||||||||||||||||||
| Description | The installed operating system must be maintained by a vendor.
Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
Linux vendor, Red Hat, Inc. is responsible for providing security patches. | ||||||||||||||||||
| Rationale | An operating system is considered "supported" if the vendor continues to
provide security patches for the product. With an unsupported release, it
will not be possible to resolve any security issue discovered in the system
software. | ||||||||||||||||||
| Warnings | warning
There is no remediation besides switching to a different operating system. |
OVAL test results details
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
/etc/almalinux-release exists oval:ssg-test_almalinux:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_almalinux:obj:1 of type file_object
| Filepath |
|---|
| /etc/almalinux-release |
Check Custom OS version oval:ssg-test_almalinux9:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_almalinux9:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/almalinux-release | ^AlmaLinux release 9.[0-9]+ .*$ | 1 |
installed OS part of unix family oval:ssg-test_rhel8_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 8 oval:ssg-test_rhel8:tst:1 false
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| false | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 8 oval:ssg-test_ol8_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol8_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 8 oval:ssg-test_rhevh_rhel8_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel8_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
installed OS part of unix family oval:ssg-test_rhel10_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 10 oval:ssg-test_rhel10:tst:1 false
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| false | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 10 oval:ssg-test_rhevh_rhel10_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel10_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 7 oval:ssg-test_ol7_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol7_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 8 oval:ssg-test_ol8_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol8_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
installed OS part of unix family oval:ssg-test_sle12_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
sled-release is version 6 oval:ssg-test_sle12_desktop:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle12_desktop:obj:1 of type rpminfo_object
| Name |
|---|
| sled-release |
sles-release is version 6 oval:ssg-test_sle12_server:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle12_server:obj:1 of type rpminfo_object
| Name |
|---|
| sles-release |
SLES_SAP-release is version 12 oval:ssg-test_sles_12_for_sap:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sles_12_for_sap:obj:1 of type rpminfo_object
| Name |
|---|
| SLES_SAP-release |
installed OS part of unix family oval:ssg-test_sle15_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
sled-release is version 15 oval:ssg-test_sle15_desktop:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle15_desktop:obj:1 of type rpminfo_object
| Name |
|---|
| sled-release |
sles-release is version 15 oval:ssg-test_sle15_server:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle15_server:obj:1 of type rpminfo_object
| Name |
|---|
| sles-release |
SLES_SAP-release is version 15 oval:ssg-test_sles_15_for_sap:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sles_15_for_sap:obj:1 of type rpminfo_object
| Name |
|---|
| SLES_SAP-release |
SUMA is version 4 oval:ssg-test_suma_4:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_suma_4:obj:1 of type rpminfo_object
| Name |
|---|
| SUSE-Manager-Server-release |
SLE HPC release is version 15 oval:ssg-test_sle_hpc:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle_hpc:obj:1 of type rpminfo_object
| Name |
|---|
| SLE_HPC-release |
installed OS part of unix family oval:ssg-test_sle16_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
SLES-release is version 16 oval:ssg-test_sle16_server:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sle16_server:obj:1 of type rpminfo_object
| Name |
|---|
| SLES-release |
SLES_SAP-release is version 16 oval:ssg-test_sles_16_for_sap:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sles_16_for_sap:obj:1 of type rpminfo_object
| Name |
|---|
| SLES_SAP-release |
sle-ha-release is version 16 oval:ssg-test_sles_16_for_ha:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_sles_16_for_ha:obj:1 of type rpminfo_object
| Name |
|---|
| sle-ha-release |
installed OS part of unix family oval:ssg-test_slmicro5_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
sle-micro-release is version 5 oval:ssg-test_slmicroos5:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_slmicroos5:obj:1 of type rpminfo_object
| Name |
|---|
| SUSE-MicroOS-release |
sle-micro-release is version 5 oval:ssg-test_slmicro5:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_slmicro5:obj:1 of type rpminfo_object
| Name |
|---|
| SLE-Micro-release |
installed OS part of unix family oval:ssg-test_slmicro6_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
sle-micro-release is version 6 oval:ssg-test_slmicro6:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_slmicro6:obj:1 of type rpminfo_object
| Name |
|---|
| SL-Micro-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
/etc/lsb-release exists oval:ssg-test_lsb:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_lsb:obj:1 of type file_object
| Filepath |
|---|
| /etc/lsb-release |
Check Ubuntu oval:ssg-test_ubuntu:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ubuntu:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/lsb-release | ^DISTRIB_ID=Ubuntu$ | 1 |
Check Ubuntu version oval:ssg-test_ubuntu_noble:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ubuntu_noble:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/lsb-release | ^DISTRIB_CODENAME=noble$ | 1 |
Encrypt Partitionsxccdf_org.ssgproject.content_rule_encrypt_partitions highCCE-90849-1
Encrypt Partitions
| Rule ID | xccdf_org.ssgproject.content_rule_encrypt_partitions | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90849-1 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | Red Hat Enterprise Linux 9 natively supports partition encryption through the
Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to
encrypt a partition is during installation time.
For manual installations, select the Encrypt checkbox during
partition creation to encrypt the partition. When this
option is selected the system will prompt for a passphrase to use in
decrypting the partition. The passphrase will subsequently need to be entered manually
every time the system boots.
For automated/unattended installations, it is possible to use Kickstart by adding the --encrypted and --passphrase= options to the definition of each partition to be
encrypted. For example, the following line would encrypt the root partition:
part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASE
Any PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart
must then be protected accordingly.
Omitting the --passphrase= option from the partition definition will cause the
installer to pause and interactively ask for the passphrase during installation.
By default, the Anaconda installer uses aes-xts-plain64 cipher
with a minimum 512 bit key size which should be compatible with FIPS enabled.
Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the Red Hat Enterprise Linux 9 Documentation web site: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening . | ||||||||||||||||||||||||||||
| Rationale | The risk of a system's physical compromise, particularly mobile systems such as
laptops, places its data at risk of compromise. Encrypting this data mitigates
the risk of its loss if the system is lost. |
Ensure /home Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_home lowCCE-83468-9
Ensure /home Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_home | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||
| Identifiers: | CCE-83468-9 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | If user home directories will be stored locally, create a separate partition
for /home at installation time (or migrate it later using LVM). If
/home will be mounted from another system such as an NFS server, then
creating a separate partition is not necessary at installation time, and the
mountpoint can instead be configured later. | ||||||||||||||||||||||||
| Rationale | Ensuring that /home is mounted on its own partition enables the
setting of more restrictive mount options, and also helps ensure that
users cannot trivially fill partitions used for log or audit data storage. |
Ensure /tmp Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_tmp lowCCE-90845-9
Ensure /tmp Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_tmp | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||
| Identifiers: | CCE-90845-9 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The /tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM. | ||||||||||||||||||||||
| Rationale | The /tmp partition is used as temporary storage by many programs.
Placing /tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it. |
Ensure /var Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_var lowCCE-83466-3
Ensure /var Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_var | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||
| Identifiers: | CCE-83466-3 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The /var directory is used by daemons and other system
services to store frequently-changing data. Ensure that /var has its own partition
or logical volume at installation time, or migrate it using LVM. | ||||||||||||||||||||||||
| Rationale | Ensuring that /var is mounted on its own partition enables the
setting of more restrictive mount options. This helps protect
system services such as daemons or other programs which use it.
It is not uncommon for the /var directory to contain
world-writable directories installed by other software packages. |
Ensure /var/log Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_var_log lowCCE-90848-3
Ensure /var/log Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_var_log | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90848-3 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | System logs are stored in the /var/log directory.
Ensure that /var/log has its own partition or logical
volume at installation time, or migrate it using LVM. | ||||||||||||||||||||||||||||
| Rationale | Placing /var/log in its own partition
enables better separation between log files
and other files in /var/. |
Ensure /var/log/audit Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_var_log_audit lowCCE-90847-5
Ensure /var/log/audit Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_var_log_audit | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90847-5 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | Audit logs are stored in the /var/log/audit directory.
Ensure that /var/log/audit has its own partition or logical
volume at installation time, or migrate it using LVM.
Make absolutely certain that it is large enough to store all
audit logs that will be created by the auditing daemon. | ||||||||||||||||||||||||||||||||
| Rationale | Placing /var/log/audit in its own partition
enables better separation between audit files
and other files, and helps ensure that
auditing cannot be halted due to the partition running out
of space. |
Ensure /var/tmp Located On Separate Partitionxccdf_org.ssgproject.content_rule_partition_for_var_tmp mediumCCE-83487-9
Ensure /var/tmp Located On Separate Partition
| Rule ID | xccdf_org.ssgproject.content_rule_partition_for_var_tmp | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83487-9 | ||||||||||||
| References: |
| ||||||||||||
| Description | The /var/tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM. | ||||||||||||
| Rationale | The /var/tmp partition is used as temporary storage by many programs.
Placing /var/tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it. |
Disable the GNOME3 Login Restart and Shutdown Buttonsxccdf_org.ssgproject.content_rule_dconf_gnome_disable_restart_shutdown highCCE-86315-9
Disable the GNOME3 Login Restart and Shutdown Buttons
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_disable_restart_shutdown | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||
| Identifiers: | CCE-86315-9 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | In the default graphical environment, users logging directly into the
system are greeted with a login screen that allows any user, known or
unknown, the ability the ability to shutdown or restart the system. This
functionality should be disabled by setting
disable-restart-buttons to true.
To disable, add or edit disable-restart-buttons to
/etc/dconf/db/distro.d/00-security-settings. For example:
[org/gnome/login-screen] disable-restart-buttons=trueOnce the setting has been added, add a lock to /etc/dconf/db/distro.d/locks/00-security-settings-lock to prevent
user modification. For example:
/org/gnome/login-screen/disable-restart-buttonsAfter the settings have been set, run dconf update. | ||||||||||||||||||||||
| Rationale | A user who is at the console can reboot the system at the login screen. If restart or shutdown buttons
are pressed at the login screen, this can create the risk of short-term loss of availability of systems
due to reboot. |
Disable the GNOME3 Login User Listxccdf_org.ssgproject.content_rule_dconf_gnome_disable_user_list mediumCCE-88285-2
Disable the GNOME3 Login User List
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_disable_user_list | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-88285-2 | ||||||||||||
| References: |
| ||||||||||||
| Description | In the default graphical environment, users logging directly into the
system are greeted with a login screen that displays all known users.
This functionality should be disabled by setting disable-user-list
to true.
To disable, add or edit disable-user-list to
/etc/dconf/db/distro.d/00-security-settings. For example:
[org/gnome/login-screen] disable-user-list=trueOnce the setting has been added, add a lock to /etc/dconf/db/distro.d/locks/00-security-settings-lock to prevent
user modification. For example:
/org/gnome/login-screen/disable-user-listAfter the settings have been set, run dconf update. | ||||||||||||
| Rationale | Leaving the user list enabled is a security risk since it allows anyone
with physical access to the system to quickly enumerate known user accounts
without logging in. |
Enable the GNOME3 Screen Locking On Smartcard Removalxccdf_org.ssgproject.content_rule_dconf_gnome_lock_screen_on_smartcard_removal mediumCCE-86452-0
Enable the GNOME3 Screen Locking On Smartcard Removal
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_lock_screen_on_smartcard_removal | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86452-0 | ||||||
| References: |
| ||||||
| Description | In the default graphical environment, screen locking on smartcard removal
can be enabled by setting removal-action
to 'lock-screen'.
To enable, add or edit removal-action to
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/settings-daemon/peripherals/smartcard] removal-action='lock-screen'Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/settings-daemon/peripherals/smartcard/removal-actionAfter the settings have been set, run dconf update. | ||||||
| Rationale | Locking the screen automatically when removing the smartcard can
prevent undesired access to system. |
Disable GDM Automatic Loginxccdf_org.ssgproject.content_rule_gnome_gdm_disable_automatic_login highCCE-89663-9
Disable GDM Automatic Login
| Rule ID | xccdf_org.ssgproject.content_rule_gnome_gdm_disable_automatic_login | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||
| Identifiers: | CCE-89663-9 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The GNOME Display Manager (GDM) can allow users to automatically login without
user interaction or credentials. User should always be required to authenticate themselves
to the system that they are authorized to use. To disable user ability to automatically
login to the system, set the AutomaticLoginEnable to false in the
[daemon] section in /etc/gdm/custom.conf. For example:
[daemon] AutomaticLoginEnable=false | ||||||||||||||||||||||||
| Rationale | Failure to restrict system access to authenticated users negatively impacts operating
system security. |
Disable GNOME3 Automount Openingxccdf_org.ssgproject.content_rule_dconf_gnome_disable_automount_open mediumCCE-90128-0
Disable GNOME3 Automount Opening
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_disable_automount_open | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90128-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The system's default desktop environment, GNOME3, will mount
devices and removable media (such as DVDs, CDs and USB flash drives) whenever
they are inserted into the system. To disable automount-open within GNOME3, add or set
automount-open to false in /etc/dconf/db/local.d/00-security-settings.
For example:
[org/gnome/desktop/media-handling] automount-open=falseOnce the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/media-handling/automount-openAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||||||
| Rationale | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Disabling automatic mounting in GNOME3 can prevent
the introduction of malware via removable media.
It will, however, also prevent desktop users from legitimate use
of removable media. |
Disable GNOME3 Automount runningxccdf_org.ssgproject.content_rule_dconf_gnome_disable_autorun lowCCE-90257-7
Disable GNOME3 Automount running
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_disable_autorun | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||||
| Identifiers: | CCE-90257-7 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The system's default desktop environment, GNOME3, will mount
devices and removable media (such as DVDs, CDs and USB flash drives) whenever
they are inserted into the system. To disable autorun-never within GNOME3, add or set
autorun-never to true in /etc/dconf/db/local.d/00-security-settings.
For example:
[org/gnome/desktop/media-handling] autorun-never=trueOnce the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/media-handling/autorun-neverAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||||
| Rationale | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Disabling automatic mount running in GNOME3 can prevent
the introduction of malware via removable media.
It will, however, also prevent desktop users from legitimate use
of removable media. |
Set GNOME3 Screensaver Inactivity Timeoutxccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_idle_delay mediumCCE-86510-5
Set GNOME3 Screensaver Inactivity Timeout
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_idle_delay | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-86510-5 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The idle time-out value for inactivity in the GNOME3 desktop is configured via the idle-delay
setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory
and locked in /etc/dconf/db/local.d/locks directory to prevent user modification.
For example, to configure the system for a 15 minute delay, add the following to /etc/dconf/db/local.d/00-security-settings:
[org/gnome/desktop/session] idle-delay=uint32 900 | ||||||||||||||||||||||||||||||||
| Rationale | A session time-out lock is a temporary action taken when a user stops work and moves away from
the immediate physical vicinity of the information system but does not logout because of the
temporary nature of the absence. Rather than relying on the user to manually lock their operating
system session prior to vacating the vicinity, GNOME3 can be configured to identify when
a user's session has idled and take action to initiate a session lock. |
Set GNOME3 Screensaver Lock Delay After Activation Periodxccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_delay mediumCCE-86954-5
Set GNOME3 Screensaver Lock Delay After Activation Period
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_delay | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-86954-5 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | To activate the locking delay of the screensaver in the GNOME3 desktop when
the screensaver is activated, add or set lock-delay to uint32 0
in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/desktop/screensaver]
lock-delay=uint32 0
After the settings have been set, run dconf update. | ||||||||||||||||||||||||||||||
| Rationale | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absence. |
Enable GNOME3 Screensaver Lock After Idle Periodxccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_enabled mediumCCE-89302-4
Enable GNOME3 Screensaver Lock After Idle Period
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_enabled | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-89302-4 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
To activate locking of the screensaver in the GNOME3 desktop when it is activated,
add or set lock-enabled to true in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/desktop/screensaver] lock-enabled=trueOnce the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/lock-enabledAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||||||
| Rationale | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absence. |
Implement Blank Screensaverxccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_mode_blank mediumCCE-88733-1
Implement Blank Screensaver
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_mode_blank | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-88733-1 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
To set the screensaver mode in the GNOME3 desktop to a blank screen,
add or set picture-uri to string '' in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/desktop/screensaver] picture-uri=string ''Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/picture-uriAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||||||
| Rationale | Setting the screensaver mode to blank-only conceals the
contents of the display from passersby. |
Ensure Users Cannot Change GNOME3 Screensaver Settingsxccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_user_locks mediumCCE-87491-7
Ensure Users Cannot Change GNOME3 Screensaver Settings
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_user_locks | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-87491-7 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | If not already configured, ensure that users cannot change GNOME3 screensaver lock settings
by adding /org/gnome/desktop/screensaver/lock-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/lock-delayAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||
| Rationale | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock. As such, users should not be allowed to change session settings. |
Ensure Users Cannot Change GNOME3 Session Idle Settingsxccdf_org.ssgproject.content_rule_dconf_gnome_session_idle_user_locks mediumCCE-85971-0
Ensure Users Cannot Change GNOME3 Session Idle Settings
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_session_idle_user_locks | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-85971-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | If not already configured, ensure that users cannot change GNOME3 session idle settings
by adding /org/gnome/desktop/session/idle-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/session/idle-delayAfter the settings have been set, run dconf update. | ||||||||||||||||||||||||||||
| Rationale | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock. As such, users should not be allowed to change session settings. |
Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3xccdf_org.ssgproject.content_rule_dconf_gnome_disable_ctrlaltdel_reboot highCCE-88653-1
Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_gnome_disable_ctrlaltdel_reboot | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||
| Identifiers: | CCE-88653-1 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | By default, GNOME will reboot the system if the
Ctrl-Alt-Del key sequence is pressed.
To configure the system to ignore the Ctrl-Alt-Del key sequence
from the Graphical User Interface (GUI) instead of rebooting the system,
add or set logout to [''] in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/settings-daemon/plugins/media-keys] logout=['']Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent
user modification. For example:
/org/gnome/settings-daemon/plugins/media-keys/logoutAfter the settings have been set, run dconf update. | ||||||||||||||||||||||
| Rationale | A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot. |
Make sure that the dconf databases are up-to-date with regards to respective keyfilesxccdf_org.ssgproject.content_rule_dconf_db_up_to_date highCCE-87295-2
Make sure that the dconf databases are up-to-date with regards to respective keyfiles
| Rule ID | xccdf_org.ssgproject.content_rule_dconf_db_up_to_date | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | high | ||||||||||||||||
| Identifiers: | CCE-87295-2 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | By default, DConf uses a binary database as a data backend.
The system-level database is compiled from keyfiles in the /etc/dconf/db/
directory by the dconf updatecommand. More specifically, content present in the following directories: /etc/dconf/db/distro.d /etc/dconf/db/local.d | ||||||||||||||||
| Rationale | Unlike text-based keyfiles, the binary database is impossible to check by OVAL.
Therefore, in order to evaluate dconf configuration, both have to be true at the same time -
configuration files have to be compliant, and the database needs to be more recent than those keyfiles,
which gives confidence that it reflects them. |
Install sudo Packagexccdf_org.ssgproject.content_rule_package_sudo_installed mediumCCE-83523-1
Install sudo Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_sudo_installed | ||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||
| Severity | medium | ||||||||||||||||||
| Identifiers: | CCE-83523-1 | ||||||||||||||||||
| References: |
| ||||||||||||||||||
| Description | The sudo package can be installed with the following command:
$ sudo dnf install sudo | ||||||||||||||||||
| Rationale | sudo is a program designed to allow a system administrator to give
limited root privileges to users and log root activity. The basic philosophy
is to give as few privileges as possible but still allow system users to
get their work done. |
Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticatexccdf_org.ssgproject.content_rule_sudo_remove_no_authenticate mediumCCE-83544-7
Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate
| Rule ID | xccdf_org.ssgproject.content_rule_sudo_remove_no_authenticate | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83544-7 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The sudo !authenticate option, when specified, allows a user to execute commands using
sudo without having to authenticate. This should be disabled by making sure that the
!authenticate option does not exist in /etc/sudoers configuration file or
any sudo configuration snippets in /etc/sudoers.d/. | ||||||||||||||||||||||||
| Rationale | Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate. |
Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWDxccdf_org.ssgproject.content_rule_sudo_remove_nopasswd mediumCCE-83536-3
Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD
| Rule ID | xccdf_org.ssgproject.content_rule_sudo_remove_nopasswd | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83536-3 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The sudo NOPASSWD tag, when specified, allows a user to execute
commands using sudo without having to authenticate. This should be disabled
by making sure that the NOPASSWD tag does not exist in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/. | ||||||||||||||||||||||||
| Rationale | Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate. |
Require Re-Authentication When Using the sudo Commandxccdf_org.ssgproject.content_rule_sudo_require_reauthentication mediumCCE-90029-0
Require Re-Authentication When Using the sudo Command
| Rule ID | xccdf_org.ssgproject.content_rule_sudo_require_reauthentication | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-90029-0 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The sudo timestamp_timeout tag sets the amount of time sudo password prompt waits.
The default timestamp_timeout value is 5 minutes.
The timestamp_timeout should be configured by making sure that the
timestamp_timeout tag exists in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/.
If the value is set to an integer less than 0, the user's time stamp will not expire
and the user will not have to re-authenticate for privileged actions until the user's session is terminated. | ||||||||||||||
| Rationale | Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate. |
Ensure invoking users password for privilege escalation when using sudoxccdf_org.ssgproject.content_rule_sudoers_validate_passwd mediumCCE-83529-8
Ensure invoking users password for privilege escalation when using sudo
| Rule ID | xccdf_org.ssgproject.content_rule_sudoers_validate_passwd | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83529-8 | ||||||||
| References: |
| ||||||||
| Description | The sudoers security policy requires that users authenticate themselves before they can use sudo.
When sudoers requires authentication, it validates the invoking user's credentials.
The expected output for:
sudo cvtsudoers -f sudoers /etc/sudoers | grep -E '^Defaults !?(rootpw|targetpw|runaspw)$' Defaults !targetpw
Defaults !rootpw
Defaults !runaspw
or if cvtsudoers not supported:
sudo find /etc/sudoers /etc/sudoers.d \( \! -name '*~' -a \! -name '*.*' \) -exec grep -E --with-filename '^[[:blank:]]*Defaults[[:blank:]](.*[[:blank:]])?!?\b(rootpw|targetpw|runaspw)' -- {} \;
/etc/sudoers:Defaults !targetpw
/etc/sudoers:Defaults !rootpw
/etc/sudoers:Defaults !runaspw
| ||||||||
| Rationale | If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt
the invoking user for the "root" user password. |
Ensure gnutls-utils is installedxccdf_org.ssgproject.content_rule_package_gnutls-utils_installed mediumCCE-83494-5
Ensure gnutls-utils is installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_gnutls-utils_installed | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-package_gnutls-utils_installed:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83494-5 | ||||||||
| References: |
| ||||||||
| Description | The gnutls-utils package can be installed with the following command:
$ sudo dnf install gnutls-utils | ||||||||
| Rationale | GnuTLS is a secure communications library implementing the SSL, TLS and DTLS
protocols and technologies around them. It provides a simple C language
application programming interface (API) to access the secure communications
protocols as well as APIs to parse and write X.509, PKCS #12, OpenPGP and
other required structures.
This package contains command line TLS client and server and certificate
manipulation tools. |
OVAL test results details
package gnutls-utils is installed oval:ssg-test_package_gnutls-utils_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| not evaluated | gnutls-utils | x86_64 | (none) | 4.el9_8 | 3.8.10 | 0:3.8.10-4.el9_8 | 199e2f91fd431d51 | gnutls-utils-0:3.8.10-4.el9_8.x86_64 |
Ensure nss-tools is installedxccdf_org.ssgproject.content_rule_package_nss-tools_installed mediumCCE-89706-6
Ensure nss-tools is installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_nss-tools_installed | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-package_nss-tools_installed:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89706-6 | ||||||||
| References: |
| ||||||||
| Description | The nss-tools package can be installed with the following command:
$ sudo dnf install nss-tools | ||||||||
| Rationale | Network Security Services (NSS) is a set of libraries designed to
support cross-platform development of security-enabled client and
server applications. Install the nss-tools package
to install command-line tools to manipulate the NSS certificate
and key database. |
OVAL test results details
package nss-tools is installed oval:ssg-test_package_nss-tools_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| not evaluated | nss-tools | x86_64 | (none) | 8.el9_4 | 3.112.0 | 0:3.112.0-8.el9_4 | 199e2f91fd431d51 | nss-tools-0:3.112.0-8.el9_4.x86_64 |
Install rng-tools Packagexccdf_org.ssgproject.content_rule_package_rng-tools_installed lowCCE-83504-1
Install rng-tools Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_rng-tools_installed | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | low | ||||||
| Identifiers: | CCE-83504-1 | ||||||
| References: |
| ||||||
| Description | The rng-tools package can be installed with the following command:
$ sudo dnf install rng-tools | ||||||
| Rationale | rng-tools provides hardware random number generator tools,
such as those used in the formation of x509/PKI certificates. |
Install subscription-manager Packagexccdf_org.ssgproject.content_rule_package_subscription-manager_installed mediumCCE-83506-6
Install subscription-manager Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_subscription-manager_installed | ||||||||||
| Result | pass | ||||||||||
| Multi-check rule | no | ||||||||||
| OVAL Definition ID | oval:ssg-package_subscription-manager_installed:def:1 | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83506-6 | ||||||||||
| References: |
| ||||||||||
| Description | The subscription-manager package can be installed with the following command:
$ sudo dnf install subscription-manager | ||||||||||
| Rationale | Red Hat Subscription Manager is a local service which tracks installed products
and subscriptions on a local system to help manage subscription assignments.
It communicates with the backend subscription service (the Customer Portal
or an on-premise server such as Subscription Asset Manager) and works with
content management tools such as .
The package provides, among other things, plugins
to interact with repositories and subscriptions
from the Red Hat entitlement platform - the subscription-manager and
product-id plugins. |
OVAL test results details
package subscription-manager is installed oval:ssg-test_package_subscription-manager_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| not evaluated | subscription-manager | x86_64 | (none) | 1.el9 | 1.29.50 | 0:1.29.50-1.el9 | 199e2f91fd431d51 | subscription-manager-0:1.29.50-1.el9.x86_64 |
Uninstall gssproxy Packagexccdf_org.ssgproject.content_rule_package_gssproxy_removed mediumCCE-83516-5
Uninstall gssproxy Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_gssproxy_removed | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-package_gssproxy_removed:def:1 | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-83516-5 | ||||||
| References: |
| ||||||
| Description | The gssproxy package can be removed with the following command:
$ sudo dnf remove gssproxy | ||||||
| Rationale | gssproxy is a proxy for GSS API credential handling.
Kerberos relies on some key derivation functions that may not
be compatible with some site policies such as FIPS 140. |
OVAL test results details
package gssproxy is removed oval:ssg-test_package_gssproxy_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_gssproxy_removed:obj:1 of type rpminfo_object
| Name |
|---|
| gssproxy |
Uninstall iprutils Packagexccdf_org.ssgproject.content_rule_package_iprutils_removed mediumCCE-83519-9
Uninstall iprutils Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_iprutils_removed | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-package_iprutils_removed:def:1 | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-83519-9 | ||||||
| References: |
| ||||||
| Description | The iprutils package can be removed with the following command:
$ sudo dnf remove iprutils | ||||||
| Rationale | iprutils provides a suite of utlilities to manage and configure SCSI devices
supported by the ipr SCSI storage device driver. |
OVAL test results details
package iprutils is removed oval:ssg-test_package_iprutils_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_iprutils_removed:obj:1 of type rpminfo_object
| Name |
|---|
| iprutils |
Uninstall tuned Packagexccdf_org.ssgproject.content_rule_package_tuned_removed mediumCCE-83521-5
Uninstall tuned Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_tuned_removed | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-package_tuned_removed:def:1 | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-83521-5 | ||||||
| References: |
| ||||||
| Description | The tuned package can be removed with the following command:
$ sudo dnf remove tuned | ||||||
| Rationale | tuned contains a daemon that tunes the system settings dynamically.
It does so by monitoring the usage of several system components periodically. Based
on that information, components will then be put into lower or higher power savings
modes to adapt to the current usage. |
OVAL test results details
package tuned is removed oval:ssg-test_package_tuned_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_tuned_removed:obj:1 of type rpminfo_object
| Name |
|---|
| tuned |
Ensure dnf Removes Previous Package Versionsxccdf_org.ssgproject.content_rule_clean_components_post_updating lowCCE-83458-0
Ensure dnf Removes Previous Package Versions
| Rule ID | xccdf_org.ssgproject.content_rule_clean_components_post_updating | ||||||||||||||||||||
| Result | pass | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| OVAL Definition ID | oval:ssg-clean_components_post_updating:def:1 | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | low | ||||||||||||||||||||
| Identifiers: | CCE-83458-0 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | dnf should be configured to remove previous software components after
new versions have been installed. To configure dnf to remove the
previous software components after updating, set the clean_requirements_on_remove
to 1 in /etc/dnf/dnf.conf. | ||||||||||||||||||||
| Rationale | Previous versions of software components that are not removed from the information
system after updates have been installed may be exploited by some adversaries. |
OVAL test results details
check value of clean_requirements_on_remove in /etc/dnf/dnf.conf oval:ssg-test_yum_clean_components_post_updating:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/dnf/dnf.conf | clean_requirements_on_remove=True |
Ensure EPEL Repository is Disabledxccdf_org.ssgproject.content_rule_ensure_epel_repos_disabled mediumCCE-86845-5
Ensure EPEL Repository is Disabled
| Rule ID | xccdf_org.ssgproject.content_rule_ensure_epel_repos_disabled | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-ensure_epel_repos_disabled:def:1 | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86845-5 | ||||||
| References: |
| ||||||
| Description | The system must not have the EPEL (Extra Packages for Enterprise Linux) repository enabled.
EPEL provides additional packages that are not part of the official RHEL distribution and
may not meet enterprise security requirements.
Check if any repository files in /etc/yum.repos.d/ contain enabled EPEL repositories
by running:
$ grep -r "^\[.*epel.*\]" /etc/yum.repos.d/If EPEL repositories are found, ensure they are disabled by setting enabled=0 in
the repository configuration file. | ||||||
| Rationale | The EPEL repository is not officially supported by Red Hat and may contain packages that have
not been vetted for security in an enterprise environment. Using unsupported repositories can
introduce vulnerabilities, compatibility issues, or packages that do not meet DoD security
requirements. Only packages from authorized repositories should be installed to maintain
system integrity and security. |
OVAL test results details
Ensure no EPEL repository sections exist oval:ssg-test_no_epel_sections:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_epel_section_headers:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| ^/etc/yum\.repos\.d/.*\.repo$ | (?i)^\s*\[[^\]]*epel[^\]]*\] | 1 |
Ensure all EPEL repositories have enabled=0 oval:ssg-test_epel_repos_disabled:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-object_epel_repos_check_disabled:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| ^/etc/yum\.repos\.d/.*\.repo$ | (?i)(?:^\s*\[[^\]]*epel[^\]]*\][\s\S]*?)^\s*enabled\s*=\s*(\S+) | 1 |
Ensure gpgcheck Enabled In Main dnf Configurationxccdf_org.ssgproject.content_rule_ensure_gpgcheck_globally_activated highCCE-83457-2
Ensure gpgcheck Enabled In Main dnf Configuration
| Rule ID | xccdf_org.ssgproject.content_rule_ensure_gpgcheck_globally_activated | ||||||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-ensure_gpgcheck_globally_activated:def:1 | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83457-2 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | The gpgcheck option controls whether
RPM packages' signatures are always checked prior to installation.
To configure dnf to check package signatures before installing
them, ensure the following line appears in /etc/dnf/dnf.conf in
the [main] section:
gpgcheck=1 | ||||||||||||||||||||||||||||||||||||||
| Rationale | Changes to any software components can have significant effects on the
overall security of the operating system. This requirement ensures the
software has not been tampered with and that it has been provided by a
trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. Certificates used to verify the software must be from an approved Certificate Authority (CA). |
OVAL test results details
check value of gpgcheck in /etc/dnf/dnf.conf oval:ssg-test_ensure_gpgcheck_globally_activated:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/dnf/dnf.conf | gpgcheck=1 |
Ensure gpgcheck Enabled for Local Packagesxccdf_org.ssgproject.content_rule_ensure_gpgcheck_local_packages highCCE-83463-0
Ensure gpgcheck Enabled for Local Packages
| Rule ID | xccdf_org.ssgproject.content_rule_ensure_gpgcheck_local_packages | ||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-ensure_gpgcheck_local_packages:def:1 | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83463-0 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | dnf should be configured to verify the signature(s) of local packages
prior to installation. To configure dnf to verify signatures of local
packages, set the localpkg_gpgcheck to 1 in /etc/dnf/dnf.conf. | ||||||||||||||||||||||||||||||
| Rationale | Changes to any software components can have significant effects to the overall security
of the operating system. This requirement ensures the software has not been tampered and
has been provided by a trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. |
OVAL test results details
check value of localpkg_gpgcheck in /etc/dnf/dnf.conf oval:ssg-test_yum_ensure_gpgcheck_local_packages:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/dnf/dnf.conf | localpkg_gpgcheck=1 |
Ensure gpgcheck Enabled for All dnf Package Repositoriesxccdf_org.ssgproject.content_rule_ensure_gpgcheck_never_disabled highCCE-83464-8
Ensure gpgcheck Enabled for All dnf Package Repositories
| Rule ID | xccdf_org.ssgproject.content_rule_ensure_gpgcheck_never_disabled | ||||||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-ensure_gpgcheck_never_disabled:def:1 | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83464-8 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | To ensure signature checking is not disabled for
any repos, remove any lines from files in /etc/yum.repos.d of the form:
gpgcheck=0 | ||||||||||||||||||||||||||||||||||||||
| Rationale | Verifying the authenticity of the software prior to installation validates
the integrity of the patch or upgrade received from a vendor. This ensures
the software has not been tampered with and that it has been provided by a
trusted vendor. Self-signed certificates are disallowed by this
requirement. Certificates used to verify the software must be from an
approved Certificate Authority (CA)." |
OVAL test results details
check for existence of gpgcheck=0 in /etc/yum.repos.d/ files oval:ssg-test_ensure_gpgcheck_never_disabled:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_ensure_gpgcheck_never_disabled:obj:1 of type textfilecontent54_object
| Path | Filename | Pattern | Instance |
|---|---|---|---|
| /etc/yum.repos.d | .* | ^\s*gpgcheck\s*=\s*0\s*$ | 1 |
Ensure Red Hat GPG Key Installedxccdf_org.ssgproject.content_rule_ensure_redhat_gpgkey_installed highCCE-84180-9
Ensure Red Hat GPG Key Installed
| Rule ID | xccdf_org.ssgproject.content_rule_ensure_redhat_gpgkey_installed | ||||||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-ensure_redhat_gpgkey_installed:def:1 | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84180-9 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | To ensure the system can cryptographically verify base software packages
come from Red Hat (and to connect to the Red Hat Network to receive them),
the Red Hat GPG key must properly be installed. To install the Red Hat GPG
key, run:
$ sudo subscription-manager registerIf the system is not connected to the Internet or an RHN Satellite, then install the Red Hat GPG key from trusted media such as the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted in /media/cdrom, use the following command as the root user to import
it into the keyring:
$ sudo rpm --import /media/cdrom/RPM-GPG-KEYAlternatively, the key may be pre-loaded during the RHEL installation. In such cases, the key can be installed by running the following command: sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release | ||||||||||||||||||||||||||||||||||||||
| Rationale | Changes to software components can have significant effects on the overall
security of the operating system. This requirement ensures the software has
not been tampered with and that it has been provided by a trusted vendor.
The Red Hat GPG key is necessary to cryptographically verify packages are
from Red Hat. |
OVAL test results details
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
installed OS part of unix family oval:ssg-test_rhel9_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
redhat-release is version 9 oval:ssg-test_rhel9:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | redhat-release | x86_64 | (none) | 1.0.el9 | 9.8 | 0:9.8-1.0.el9 | 199e2f91fd431d51 | redhat-release-0:9.8-1.0.el9.x86_64 |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
oraclelinux-release is version 9 oval:ssg-test_ol9_system:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_ol9_system:obj:1 of type rpminfo_object
| Name |
|---|
| oraclelinux-release |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
redhat-release-virtualization-host RPM package is installed oval:ssg-test_rhvh4_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhvh4_version:obj:1 of type rpminfo_object
| Name |
|---|
| redhat-release-virtualization-host |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
RHEVH base RHEL is version 9 oval:ssg-test_rhevh_rhel9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_rhevh_rhel9_version:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/redhat-release | ^Red Hat Enterprise Linux release (\d)\.\d+$ | 1 |
Red Hat release key package is installed oval:ssg-test_redhat_package_gpgkey-fd431d51-4ae0493b_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| true | gpg-pubkey | (none) | (none) | 4ae0493b | fd431d51 | 0:fd431d51-4ae0493b | 0 | gpg-pubkey-0:fd431d51-4ae0493b.(none) |
| false | gpg-pubkey | (none) | (none) | 6229229e | 5a6340b3 | 0:5a6340b3-6229229e | 0 | gpg-pubkey-0:5a6340b3-6229229e.(none) |
Red Hat auxiliary key package is installed oval:ssg-test_redhat_package_gpgkey-5a6340b3-6229229e_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| false | gpg-pubkey | (none) | (none) | 4ae0493b | fd431d51 | 0:fd431d51-4ae0493b | 0 | gpg-pubkey-0:fd431d51-4ae0493b.(none) |
| true | gpg-pubkey | (none) | (none) | 6229229e | 5a6340b3 | 0:5a6340b3-6229229e | 0 | gpg-pubkey-0:5a6340b3-6229229e.(none) |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Test installed OS is part of the unix family oval:ssg-test_unix_family:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Family |
|---|---|
| true | unix |
Check os-release ID oval:ssg-test_centos9_name:tst:1 false
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| false | /etc/os-release | ID="rhel" |
Check os-release VERSION_ID oval:ssg-test_centos9_version:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-obj_version_centos9:obj:1 of type textfilecontent54_object
| Filepath | Pattern | Instance |
|---|---|---|
| /etc/os-release | ^VERSION_ID="(\d)"$ | 1 |
CentOS9 key package is installed oval:ssg-test_redhat_package_gpgkey-8483c65d-5ccc5b19_installed:tst:1 false
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| false | gpg-pubkey | (none) | (none) | 4ae0493b | fd431d51 | 0:fd431d51-4ae0493b | 0 | gpg-pubkey-0:fd431d51-4ae0493b.(none) |
| false | gpg-pubkey | (none) | (none) | 6229229e | 5a6340b3 | 0:5a6340b3-6229229e | 0 | gpg-pubkey-0:5a6340b3-6229229e.(none) |
Ensure Software Patches Installedxccdf_org.ssgproject.content_rule_security_patches_up_to_date mediumCCE-84185-8
Ensure Software Patches Installed
| Rule ID | xccdf_org.ssgproject.content_rule_security_patches_up_to_date | ||||||||||||||||||||||||||||||
| Result | notchecked | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-84185-8 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description |
If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
or a yum server, run the following command to install updates:
$ sudo yum updateIf the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the Red Hat Network and installed using rpm.
NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates. | ||||||||||||||||||||||||||||||
| Rationale | Installing software updates is a fundamental mitigation against
the exploitation of publicly-known vulnerabilities. If the most
recent security patches and updates are not installed, unauthorized
users may take advantage of weaknesses in the unpatched software. The
lack of prompt attention to patching could result in a system compromise. | ||||||||||||||||||||||||||||||
| Warnings | warning
Red Hat Enterprise Linux 9 does not have a corresponding OVAL CVE Feed. Therefore, this will result in a "not checked" result during a scan. | ||||||||||||||||||||||||||||||
Configure the Use of the pam_faillock.so Module in the /etc/pam.d/password-auth File.xccdf_org.ssgproject.content_rule_account_password_pam_faillock_password_auth mediumCCE-86932-1
Configure the Use of the pam_faillock.so Module in the /etc/pam.d/password-auth File.
| Rule ID | xccdf_org.ssgproject.content_rule_account_password_pam_faillock_password_auth | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86932-1 | ||||||||||
| References: |
| ||||||||||
| Description | The pam_faillock.so module must be loaded in preauth in /etc/pam.d/password-auth. | ||||||||||
| Rationale | If the pam_faillock.so module is not loaded the system will not correctly lockout accounts to prevent
password guessing attacks. |
Configure the Use of the pam_faillock.so Module in the /etc/pam.d/system-auth File.xccdf_org.ssgproject.content_rule_account_password_pam_faillock_system_auth mediumCCE-86917-2
Configure the Use of the pam_faillock.so Module in the /etc/pam.d/system-auth File.
| Rule ID | xccdf_org.ssgproject.content_rule_account_password_pam_faillock_system_auth | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86917-2 | ||||||||||
| References: |
| ||||||||||
| Description | The pam_faillock.so module must be loaded in preauth in /etc/pam.d/system-auth. | ||||||||||
| Rationale | If the pam_faillock.so module is not loaded the system will not correctly lockout accounts to prevent
password guessing attacks. |
An SELinux Context must be configured for the pam_faillock.so records directoryxccdf_org.ssgproject.content_rule_account_password_selinux_faillock_dir mediumCCE-86249-0
An SELinux Context must be configured for the pam_faillock.so records directory
| Rule ID | xccdf_org.ssgproject.content_rule_account_password_selinux_faillock_dir | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86249-0 | ||||||||
| References: |
| ||||||||
| Description | The dir configuration option in PAM pam_faillock.so module defines where the lockout
records is stored. The configured directory must have the correct SELinux context. | ||||||||
| Rationale | Not having the correct SELinux context on the pam_faillock.so records directory may lead to
unauthorized access to the directory. |
Account Lockouts Must Be Loggedxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_audit mediumCCE-86100-5
Account Lockouts Must Be Logged
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_audit | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86100-5 | ||||||||
| References: |
| ||||||||
| Description | PAM faillock locks an account due to excessive password failures, this event must be logged. | ||||||||
| Rationale | Without auditing of these events it may be harder or impossible to identify what an attacker did after an attack. |
Lock Accounts After Failed Password Attemptsxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny mediumCCE-83587-6
Lock Accounts After Failed Password Attempts
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny | ||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83587-6 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | This rule configures the system to lock out accounts after a number of incorrect login attempts
using pam_faillock.so.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected.
Ensure that the file /etc/security/faillock.conf contains the following entry:
deny = <count>
Where count should be less than or equal to
3 and greater than 0.
In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. | ||||||||||||||||||||||||||||||||||||||
| Rationale | By limiting the number of failed logon attempts, the risk of unauthorized system access via
user password guessing, also known as brute-forcing, is reduced. Limits are imposed by locking
the account. | ||||||||||||||||||||||||||||||||||||||
| Warnings | warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
If the system supports the /etc/security/faillock.conf file, the pam_faillock
parameters should be defined in faillock.conf file. |
Configure the root Account for Failed Password Attemptsxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny_root mediumCCE-83589-2
Configure the root Account for Failed Password Attempts
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny_root | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83589-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | This rule configures the system to lock out the root account after a number of
incorrect login attempts using pam_faillock.so.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. | ||||||||||||||||||||||||||
| Rationale | By limiting the number of failed logon attempts, the risk of unauthorized system access via
user password guessing, also known as brute-forcing, is reduced. Limits are imposed by locking
the account. | ||||||||||||||||||||||||||
| Warnings | warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
If the system supports the /etc/security/faillock.conf file, the pam_faillock
parameters should be defined in faillock.conf file. |
Lock Accounts Must Persistxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_dir mediumCCE-86068-4
Lock Accounts Must Persist
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_dir | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86068-4 | ||||||||
| References: |
| ||||||||
| Description | This rule ensures that the system lock out accounts using pam_faillock.so persist
after system reboot. From "pam_faillock" man pages:
Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be re-enabled after system reboot. If that is undesirable, a different tally directory must be set with the "dir" option.pam_faillock.so module requires multiple entries in pam files. These entries must be carefully defined to work as expected. In order to avoid errors when manually editing these files, it is recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version.
The chosen profile expects the directory to be /var/log/faillock.
To configure the tally directory, add the following line to /etc/security/faillock.conf:
dir = /var/log/faillock
| ||||||||
| Rationale | Locking out user accounts after a number of incorrect attempts prevents direct password
guessing attacks. In combination with the silent option, user enumeration attacks
are also mitigated. | ||||||||
| Warnings | warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
If the system supports the /etc/security/faillock.conf file, the pam_faillock
parameters should be defined in faillock.conf file. |
Set Interval For Counting Failed Password Attemptsxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_interval mediumCCE-83583-5
Set Interval For Counting Failed Password Attempts
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_interval | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83583-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | Utilizing pam_faillock.so, the fail_interval directive configures the system
to lock out an account after a number of incorrect login attempts within a specified time
period.
Ensure that the file /etc/security/faillock.conf contains the following entry:
fail_interval = <interval-in-seconds> where interval-in-seconds is 900 or greater.
In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version. | ||||||||||||||||||||||||||
| Rationale | By limiting the number of failed logon attempts the risk of unauthorized system
access via user password guessing, otherwise known as brute-forcing, is reduced.
Limits are imposed by locking the account. | ||||||||||||||||||||||||||
| Warnings | warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
If the system supports the /etc/security/faillock.conf file, the pam_faillock
parameters should be defined in faillock.conf file. |
Set Lockout Time for Failed Password Attemptsxccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_unlock_time mediumCCE-83588-4
Set Lockout Time for Failed Password Attempts
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_unlock_time | ||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83588-4 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | This rule configures the system to lock out accounts during a specified time period after a
number of incorrect login attempts using pam_faillock.so.
Ensure that the file /etc/security/faillock.conf contains the following entry:
unlock_time=<interval-in-seconds> where
interval-in-seconds is 0 or greater.
pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid any errors when manually editing these files,
it is recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version.
If unlock_time is set to 0, manual intervention by an administrator is required
to unlock a user. This should be done using the faillock tool. | ||||||||||||||||||||||||||||||||||||||
| Rationale | By limiting the number of failed logon attempts the risk of unauthorized system
access via user password guessing, otherwise known as brute-forcing, is reduced.
Limits are imposed by locking the account. | ||||||||||||||||||||||||||||||||||||||
| Warnings | warning
If the system supports the new /etc/security/faillock.conf file but the
pam_faillock.so parameters are defined directly in /etc/pam.d/system-auth and
/etc/pam.d/password-auth, the remediation will migrate the unlock_time parameter
to /etc/security/faillock.conf to ensure compatibility with authselect tool.
The parameters deny and fail_interval, if used, also have to be migrated
by their respective remediation.warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
If the system supports the /etc/security/faillock.conf file, the pam_faillock
parameters should be defined in faillock.conf file. |
Ensure PAM Enforces Password Requirements - Minimum Digit Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_dcredit mediumCCE-83566-0
Ensure PAM Enforces Password Requirements - Minimum Digit Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_dcredit | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83566-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The pam_pwquality module's dcredit parameter controls requirements for
usage of digits in a password. When set to a negative number, any password will be required to
contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each digit. Modify the dcredit setting in
/etc/security/pwquality.conf to require the use of a digit in passwords. | ||||||||||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. |
Ensure PAM Enforces Password Requirements - Prevent the Use of Dictionary Wordsxccdf_org.ssgproject.content_rule_accounts_password_pam_dictcheck mediumCCE-88413-0
Ensure PAM Enforces Password Requirements - Prevent the Use of Dictionary Words
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_dictcheck | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-88413-0 | ||||||||||
| References: |
| ||||||||||
| Description | The pam_pwquality module's dictcheck check if passwords contains dictionary words. When
dictcheck is set to 1 passwords will be checked for dictionary words. | ||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at
guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Passwords with dictionary words may be more vulnerable to password-guessing attacks. |
Ensure PAM Enforces Password Requirements - Minimum Different Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_difok mediumCCE-83564-5
Ensure PAM Enforces Password Requirements - Minimum Different Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_difok | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83564-5 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The pam_pwquality module's difok parameter sets the number of characters
in a password that must not be present in and old password during a password change.
Modify the difok setting in /etc/security/pwquality.conf
to equal 8 to require differing characters
when changing passwords. | ||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources
required to compromise the password. Password complexity, or strength,
is a measure of the effectiveness of a password in resisting attempts
at guessing and brute–force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of different characters during password changes ensures that newly changed passwords should not resemble previously compromised ones. Note that passwords which are changed on compromised systems will still be compromised, however. |
Ensure PAM Enforces Password Requirements - Enforce for root Userxccdf_org.ssgproject.content_rule_accounts_password_pam_enforce_root mediumCCE-86356-3
Ensure PAM Enforces Password Requirements - Enforce for root User
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_enforce_root | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86356-3 | ||||||||||
| References: |
| ||||||||||
| Description | The pam_pwquality module's enforce_for_root parameter controls requirements for
enforcing password complexity for the root user. Enable the enforce_for_root
setting in /etc/security/pwquality.conf to require the root user
to use complex passwords. | ||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise
the password. Password complexity, or strength, is a measure of the effectiveness of a
password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a
password. The more complex the password, the greater the number of possible combinations
that need to be tested before the password is compromised. |
Ensure PAM Enforces Password Requirements - Minimum Lowercase Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_lcredit mediumCCE-83570-2
Ensure PAM Enforces Password Requirements - Minimum Lowercase Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_lcredit | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83570-2 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The pam_pwquality module's lcredit parameter controls requirements for
usage of lowercase letters in a password. When set to a negative number, any password will be required to
contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each lowercase character. Modify the lcredit setting in
/etc/security/pwquality.conf to require the use of a lowercase character in passwords. | ||||||||||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Classxccdf_org.ssgproject.content_rule_accounts_password_pam_maxclassrepeat mediumCCE-83575-1
Ensure PAM Enforces Password Requirements - Maximum Consecutive Repeating Characters from Same Character Class
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_maxclassrepeat | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-83575-1 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The pam_pwquality module's maxclassrepeat parameter controls requirements for
consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters from the same character class. Modify the
maxclassrepeat setting in /etc/security/pwquality.conf to equal 4
to prevent a run of (4 + 1) or more identical characters. | ||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting
attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex a password, the greater the number of possible combinations that need to be tested before the password is compromised. |
Set Password Maximum Consecutive Repeating Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_maxrepeat mediumCCE-83567-8
Set Password Maximum Consecutive Repeating Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_maxrepeat | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83567-8 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The pam_pwquality module's maxrepeat parameter controls requirements for
consecutive repeating characters. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters. Modify the maxrepeat setting
in /etc/security/pwquality.conf to equal 3 to prevent a
run of (3 + 1) or more identical characters. | ||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at
guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks. |
Ensure PAM Enforces Password Requirements - Minimum Different Categoriesxccdf_org.ssgproject.content_rule_accounts_password_pam_minclass mediumCCE-83563-7
Ensure PAM Enforces Password Requirements - Minimum Different Categories
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_minclass | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83563-7 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The pam_pwquality module's minclass parameter controls
requirements for usage of different character classes, or types, of character
that must exist in a password before it is considered valid. For example,
setting this value to three (3) requires that any password must have characters
from at least three different categories in order to be approved. The default
value is zero (0), meaning there are no required classes. There are four
categories available:
* Upper-case characters * Lower-case characters * Digits * Special characters (for example, punctuation)Modify the minclass setting in /etc/security/pwquality.conf entry
to require 4
differing categories of characters when changing passwords. | ||||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts
at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of character categories makes password guessing attacks more difficult by ensuring a larger search space. |
Ensure PAM Enforces Password Requirements - Minimum Lengthxccdf_org.ssgproject.content_rule_accounts_password_pam_minlen mediumCCE-83579-3
Ensure PAM Enforces Password Requirements - Minimum Length
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_minlen | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83579-3 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | The pam_pwquality module's minlen parameter controls requirements for
minimum characters required in a password. Add minlen=15
after pam_pwquality to set minimum password length requirements. | ||||||||||||||||||||||||||||||||||||
| Rationale | The shorter the password, the lower the number of possible combinations
that need to be tested before the password is compromised.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. |
Ensure PAM Enforces Password Requirements - Minimum Special Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_ocredit mediumCCE-83565-2
Ensure PAM Enforces Password Requirements - Minimum Special Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_ocredit | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83565-2 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The pam_pwquality module's ocredit= parameter controls requirements for
usage of special (or "other") characters in a password. When set to a negative number,
any password will be required to contain that many special characters.
When set to a positive number, pam_pwquality will grant +1
additional length credit for each special character. Modify the ocredit setting
in /etc/security/pwquality.conf to equal -1
to require use of a special character in passwords. | ||||||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. |
Ensure PAM password complexity module is enabled in password-authxccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_password_auth mediumCCE-85878-7
Ensure PAM password complexity module is enabled in password-auth
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_password_auth | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-85878-7 | ||||||
| References: |
| ||||||
| Description | To enable PAM password complexity in password-auth file:
Edit the password section in
/etc/pam.d/password-auth to show
password requisite pam_pwquality.so. | ||||||
| Rationale | Enabling PAM password complexity permits to enforce strong passwords and consequently
makes the system less prone to dictionary attacks. |
Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session in /etc/security/pwquality.confxccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_retry mediumCCE-86502-2
Ensure PAM Enforces Password Requirements - Authentication Retry Prompts Permitted Per-Session in /etc/security/pwquality.conf
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_retry | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86502-2 | ||||||
| References: |
| ||||||
| Description | To configure the number of retry prompts that are permitted per-session:
Edit the /etc/security/pwquality.conf to include
retry=3
, or a lower value if site
policy is more restrictive. The profile requirement is a maximum of retry=3
prompts
per session. | ||||||
| Rationale | Setting the password retry prompts that are permitted on a per-session basis to a low value
requires some software, such as SSH, to re-connect. This can slow down and
draw additional attention to some types of password-guessing attacks. Note that this
is different from account lockout, which is provided by the pam_faillock module. |
Ensure PAM password complexity module is enabled in system-authxccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_system_auth mediumCCE-85873-8
Ensure PAM password complexity module is enabled in system-auth
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_pwquality_system_auth | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-85873-8 | ||||||
| References: |
| ||||||
| Description | To enable PAM password complexity in system-auth file:
Edit the password section in
/etc/pam.d/system-auth to show
password requisite pam_pwquality.so. | ||||||
| Rationale | Enabling PAM password complexity permits to enforce strong passwords and consequently
makes the system less prone to dictionary attacks. |
Ensure PAM Enforces Password Requirements - Minimum Uppercase Charactersxccdf_org.ssgproject.content_rule_accounts_password_pam_ucredit mediumCCE-83568-6
Ensure PAM Enforces Password Requirements - Minimum Uppercase Characters
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_ucredit | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83568-6 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | The pam_pwquality module's ucredit= parameter controls requirements for
usage of uppercase letters in a password. When set to a negative number, any password will be required to
contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each uppercase character. Modify the ucredit setting in
/etc/security/pwquality.conf to require the use of an uppercase character in passwords. | ||||||||||||||||||||||||||||||
| Rationale | Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts
at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. |
Set Password Hashing Algorithm in /etc/libuser.confxccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_libuserconf mediumCCE-88865-1
Set Password Hashing Algorithm in /etc/libuser.conf
| Rule ID | xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_libuserconf | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-88865-1 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | In /etc/libuser.conf, add or correct the following line in its [defaults]
section to ensure the system will use the sha512
algorithm for password hashing:
crypt_style = sha512
| ||||||||||||||||||||||||||||||||
| Rationale | Passwords need to be protected at all times, and encryption is the standard method for
protecting passwords. If passwords are not encrypted, they can be plainly read
(i.e., clear text) and easily compromised. Passwords that are encrypted with a weak algorithm
are no more protected than if they are kept in plain text.
This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style
configuration option in /etc/libuser.conf ensures the use of a strong hashing
algorithm that makes password cracking attacks more difficult. |
Set Password Hashing Algorithm in /etc/login.defsxccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_logindefs mediumCCE-90590-1
Set Password Hashing Algorithm in /etc/login.defs
| Rule ID | xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_logindefs | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90590-1 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | In /etc/login.defs, add or update the following line to ensure the system will use
SHA512 as the hashing algorithm:
ENCRYPT_METHOD SHA512
| ||||||||||||||||||||||||||||||||||
| Rationale | Passwords need to be protected at all times, and encryption is the standard method for
protecting passwords. If passwords are not encrypted, they can be plainly read
(i.e., clear text) and easily compromised. Passwords that are encrypted with a weak algorithm
are no more protected than if they are kept in plain text.
Using a stronger hashing algorithm makes password cracking attacks more difficult. |
Set PAM Password Hashing Algorithm - password-authxccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_passwordauth mediumCCE-85946-2
Set PAM Password Hashing Algorithm - password-auth
| Rule ID | xccdf_org.ssgproject.content_rule_set_password_hashing_algorithm_passwordauth | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-85946-2 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The PAM system service can be configured to only store encrypted representations of passwords.
In /etc/pam.d/password-auth, the password section of the file controls which
PAM modules to execute during a password change.
Set the pam_unix.so module in the password section to include the option
sha512 and no other hashing
algorithms as shown below:
password sufficient pam_unix.so sha512
other arguments...
This will help ensure that new passwords for local users will be stored using the sha512 algorithm. | ||||||||||||||||||||||||||||||||
| Rationale | Passwords need to be protected at all times, and encryption is the standard method for
protecting passwords. If passwords are not encrypted, they can be plainly read
(i.e., clear text) and easily compromised. Passwords that are encrypted with a weak algorithm
are no more protected than if they are kept in plain text.
This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style
configuration option in /etc/libuser.conf ensures the use of a strong hashing
algorithm that makes password cracking attacks more difficult. | ||||||||||||||||||||||||||||||||
| Warnings | warning
The hashing algorithms to be used with pam_unix.so are defined with independent module
options. There are at least 7 possible algorithms and likely more algorithms will be
introduced along the time. Due the the number of options and its possible combinations,
the use of multiple hashing algorithm options may bring unexpected behaviors to the
system. For this reason the check will pass only when one hashing algorithm option is
defined and is aligned to the "var_password_hashing_algorithm_pam" variable. The
remediation will ensure the correct option and remove any other extra hashing algorithm
option. warning
The CIS Red Hat Enterprise Linux 9 Benchmark permits both "sha512" and "yescrypt" algorithms for password hashing.
This profile is configured to check for "sha512",
but a system using either algorithm is compliant with the CIS Benchmark requirements.
To use a different algorithm, create a tailored profile and select your preferred value for the var_password_hashing_algorithm_pam variable. |
Disallow Configuration to Bypass Password Requirements for Privilege Escalationxccdf_org.ssgproject.content_rule_disallow_bypass_password_sudo mediumCCE-85967-8
Disallow Configuration to Bypass Password Requirements for Privilege Escalation
| Rule ID | xccdf_org.ssgproject.content_rule_disallow_bypass_password_sudo | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-85967-8 | ||||||||
| References: |
| ||||||||
| Description | Verify the operating system is not configured to bypass password requirements for privilege
escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
$ sudo grep pam_succeed_if /etc/pam.d/sudoIf any occurrences of "pam_succeed_if" is returned from the command, this is a finding. | ||||||||
| Rationale | Without re-authentication, users may access resources or perform tasks for which they do not
have authorization. When operating systems provide the capability to escalate a functional
capability, it is critical the user re-authenticate. |
Install the opensc Package For Multifactor Authenticationxccdf_org.ssgproject.content_rule_package_opensc_installed mediumCCE-83595-9
Install the opensc Package For Multifactor Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_package_opensc_installed | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83595-9 | ||||||||||
| References: |
| ||||||||||
| Description |
The opensc package can be installed with the following command:
$ sudo dnf install opensc | ||||||||||
| Rationale | Using an authentication device, such as a CAC or token that is separate from
the information system, ensures that even if the information system is
compromised, that compromise will not affect credentials stored on the
authentication device.
Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards or similar secure authentication devices issued by an organization or identity provider. |
Install the pcsc-lite packagexccdf_org.ssgproject.content_rule_package_pcsc-lite_installed mediumCCE-86280-5
Install the pcsc-lite package
| Rule ID | xccdf_org.ssgproject.content_rule_package_pcsc-lite_installed | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86280-5 | ||||||||||
| References: |
| ||||||||||
| Description | The pcsc-lite package can be installed with the following command:
$ sudo dnf install pcsc-lite | ||||||||||
| Rationale | The pcsc-lite package must be installed if it is to be available for
multifactor authentication using smartcards. |
Install Smart Card Packages For Multifactor Authenticationxccdf_org.ssgproject.content_rule_install_smartcard_packages mediumCCE-83596-7
Install Smart Card Packages For Multifactor Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_install_smartcard_packages | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83596-7 | ||||||||||
| References: |
| ||||||||||
| Description | Configure the operating system to implement multifactor authentication by
installing the required package with the following command:
The openssl-pkcs11 package can be installed with the following command:
$ sudo dnf install openssl-pkcs11 | ||||||||||
| Rationale | Using an authentication device, such as a CAC or token that is separate from
the information system, ensures that even if the information system is
compromised, that compromise will not affect credentials stored on the
authentication device.
Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards or similar secure authentication devices issued by an organization or identity provider. |
Enable the pcscd Servicexccdf_org.ssgproject.content_rule_service_pcscd_enabled mediumCCE-87907-2
Enable the pcscd Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_pcscd_enabled | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-87907-2 | ||||||||||||
| References: |
| ||||||||||||
| Description |
The pcscd service can be enabled with the following command:
$ sudo systemctl enable pcscd.service | ||||||||||||
| Rationale | Using an authentication device, such as a CAC or token that is separate from
the information system, ensures that even if the information system is
compromised, that compromise will not affect credentials stored on the
authentication device.
Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards or similar secure authentication devices issued by an organization or identity provider. |
Configure opensc Smart Card Driversxccdf_org.ssgproject.content_rule_configure_opensc_card_drivers mediumCCE-89122-6
Configure opensc Smart Card Drivers
| Rule ID | xccdf_org.ssgproject.content_rule_configure_opensc_card_drivers | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-89122-6 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The OpenSC smart card tool can auto-detect smart card drivers; however,
setting the smart card drivers in use by your organization helps to prevent
users from using unauthorized smart cards. The default smart card driver for this
profile is cac.
To configure the OpenSC driver, edit the /etc/opensc.conf
and add the following line into the file in the app default block,
so it will look like:
app default {
...
card_drivers = cac;
}
| ||||||||||||||||||||||||
| Rationale | Smart card login provides two-factor authentication stronger than
that provided by a username and password combination. Smart cards leverage PKI
(public key infrastructure) in order to provide and verify credentials.
Configuring the smart card driver in use by your organization helps to prevent
users from using unauthorized smart cards. |
Disable debug-shell SystemD Servicexccdf_org.ssgproject.content_rule_service_debug-shell_disabled mediumCCE-90724-6
Disable debug-shell SystemD Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_debug-shell_disabled | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-90724-6 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | SystemD's debug-shell service is intended to
diagnose SystemD related boot issues with various systemctl
commands. Once enabled and following a system reboot, the root shell
will be available on tty9 which is access by pressing
CTRL-ALT-F9. The debug-shell service should only be used
for SystemD related issues and should otherwise be disabled.
By default, the debug-shell SystemD service is already disabled.
The debug-shell service can be disabled with the following command:
$ sudo systemctl mask --now debug-shell.service | ||||||||||||||
| Rationale | This prevents attackers with physical access from trivially bypassing security
on the machine through valid troubleshooting configurations and gaining root
access when the system is rebooted. |
Disable Ctrl-Alt-Del Burst Actionxccdf_org.ssgproject.content_rule_disable_ctrlaltdel_burstaction highCCE-90308-8
Disable Ctrl-Alt-Del Burst Action
| Rule ID | xccdf_org.ssgproject.content_rule_disable_ctrlaltdel_burstaction | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90308-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.
To configure the system to ignore the CtrlAltDelBurstAction
setting, add or modify the following to /etc/systemd/system.conf:
CtrlAltDelBurstAction=none | ||||||||||||||||||||||||||||
| Rationale | A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot. | ||||||||||||||||||||||||||||
| Warnings | warning
Disabling the Ctrl-Alt-Del key sequence
in /etc/init/control-alt-delete.conf DOES NOT disable the Ctrl-Alt-Del
key sequence if running in runlevel 6 (e.g. in GNOME, KDE, etc.)! The
Ctrl-Alt-Del key sequence will only be disabled if running in
the non-graphical runlevel 3. |
Disable Ctrl-Alt-Del Reboot Activationxccdf_org.ssgproject.content_rule_disable_ctrlaltdel_reboot highCCE-86667-3
Disable Ctrl-Alt-Del Reboot Activation
| Rule ID | xccdf_org.ssgproject.content_rule_disable_ctrlaltdel_reboot | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||
| Identifiers: | CCE-86667-3 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed.
To configure the system to ignore the Ctrl-Alt-Del key sequence from the
command line instead of rebooting the system, do either of the following:
ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.targetor systemctl mask ctrl-alt-del.target Do not simply delete the /usr/lib/systemd/system/ctrl-alt-del.service file,
as this file may be restored during future system updates. | ||||||||||||||||||||||||||||
| Rationale | A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot. |
Verify that Interactive Boot is Disabledxccdf_org.ssgproject.content_rule_grub2_disable_interactive_boot mediumCCE-87114-5
Verify that Interactive Boot is Disabled
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_disable_interactive_boot | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-87114-5 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | Red Hat Enterprise Linux 9 systems support an "interactive boot" option that can
be used to prevent services from being started. On a Red Hat Enterprise Linux 9
system, interactive boot can be enabled by providing a 1,
yes, true, or on value to the
systemd.confirm_spawn kernel argument in /etc/default/grub.
Remove any instance of systemd.confirm_spawn=(1|yes|true|on)from the kernel arguments in that file to disable interactive boot. Recovery booting must also be disabled. Confirm that GRUB_DISABLE_RECOVERY=true is set in /etc/default/grub.
It is also required to change the runtime configuration, run:
/sbin/grubby --update-kernel=ALL --remove-args="systemd.confirm_spawn" grub2-mkconfig -o /boot/grub2/grub.cfg | ||||||||||||||||||||||||
| Rationale | Using interactive or recovery boot, the console user could disable auditing, firewalls,
or other services, weakening system security. |
Configure Logind to terminate idle sessions after certain time of inactivityxccdf_org.ssgproject.content_rule_logind_session_timeout mediumCCE-90785-7
Configure Logind to terminate idle sessions after certain time of inactivity
| Rule ID | xccdf_org.ssgproject.content_rule_logind_session_timeout | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90785-7 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | To configure logind service to terminate inactive user sessions
after 600 seconds, edit the file
/etc/systemd/logind.conf. Ensure that there is a section
[Login]which contains the configuration StopIdleSessionSec=600
. | ||||||||||||||||||||||||||||||||
| Rationale | Terminating an idle session within a short time period reduces the window of
opportunity for unauthorized personnel to take control of a management
session enabled on the console or console port that has been let unattended. |
Require Authentication for Emergency Systemd Targetxccdf_org.ssgproject.content_rule_require_emergency_target_auth mediumCCE-83592-6
Require Authentication for Emergency Systemd Target
| Rule ID | xccdf_org.ssgproject.content_rule_require_emergency_target_auth | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83592-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | Emergency mode is intended as a system recovery
method, providing a single user root access to the system
during a failed boot sequence.
By default, Emergency mode is protected by requiring a password and is set in /usr/lib/systemd/system/emergency.service. | ||||||||||||||||||||||||||
| Rationale | This prevents attackers with physical access from trivially bypassing security
on the machine and gaining root access. Such accesses are further prevented
by configuring the bootloader password. |
Require Authentication for Single User Modexccdf_org.ssgproject.content_rule_require_singleuser_auth mediumCCE-83594-2
Require Authentication for Single User Mode
| Rule ID | xccdf_org.ssgproject.content_rule_require_singleuser_auth | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83594-2 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | Single-user mode is intended as a system recovery
method, providing a single user root access to the system by
providing a boot option at startup.
By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service. | ||||||||||||||||||||||||||||||
| Rationale | This prevents attackers with physical access from trivially bypassing security
on the machine and gaining root access. Such accesses are further prevented
by configuring the bootloader password. |
Set Account Expiration Following Inactivityxccdf_org.ssgproject.content_rule_account_disable_post_pw_expiration mediumCCE-83627-0
Set Account Expiration Following Inactivity
| Rule ID | xccdf_org.ssgproject.content_rule_account_disable_post_pw_expiration | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83627-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | To specify the number of days after a password expires (which
signifies inactivity) until an account is permanently disabled, add or correct
the following line in /etc/default/useradd:
INACTIVE=35
If a password is currently on the verge of expiration, then
35
day(s) remain(s) until the account is automatically
disabled. However, if the password will not expire for another 60 days, then 60
days plus 35 day(s) could
elapse until the account would be automatically disabled. See the
useradd man page for more information. | ||||||||||||||||||||||||||||||||
| Rationale | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system.
Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials.
Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. |
Assign Expiration Date to Temporary Accountsxccdf_org.ssgproject.content_rule_account_temp_expire_date mediumCCE-90096-9
Assign Expiration Date to Temporary Accounts
| Rule ID | xccdf_org.ssgproject.content_rule_account_temp_expire_date | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-90096-9 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Temporary accounts are established as part of normal account activation
procedures when there is a need for short-term accounts. In the event
temporary accounts are required, configure the system to
terminate them after a documented time period. For every temporary account, run the following command to set an expiration date on
it, substituting USER and YYYY-MM-DD
appropriately:
$ sudo chage -E YYYY-MM-DD USER
YYYY-MM-DD indicates the documented expiration date for the
account. For U.S. Government systems, the operating system must be
configured to automatically terminate these types of accounts after a
period of 72 hours. | ||||||||||||||||||||
| Rationale | If temporary user accounts remain active when no longer needed or for
an excessive period, these accounts may be used to gain unauthorized access.
To mitigate this risk, automated termination of all temporary accounts
must be set upon account creation.
|
Set Password Maximum Agexccdf_org.ssgproject.content_rule_accounts_maximum_age_login_defs mediumCCE-83606-4
Set Password Maximum Age
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_maximum_age_login_defs | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83606-4 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To specify password maximum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MAX_DAYS 60
The profile requirement is 60. | ||||||||||||||||||||||||||||||||||
| Rationale | Any password, no matter how complex, can eventually be cracked. Therefore, passwords
need to be changed periodically. If the operating system does not limit the lifetime
of passwords and force users to change their passwords, there is the risk that the
operating system passwords could be compromised.
Setting the password maximum age ensures users are required to periodically change their passwords. Requiring shorter password lifetimes increases the risk of users writing down the password in a convenient location subject to physical compromise. |
Set Password Minimum Agexccdf_org.ssgproject.content_rule_accounts_minimum_age_login_defs mediumCCE-83610-6
Set Password Minimum Age
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_minimum_age_login_defs | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83610-6 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | To specify password minimum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MIN_DAYS 1
A value of 1 day is considered sufficient for many
environments.
The profile requirement is 1. | ||||||||||||||||||||||||||||||
| Rationale | Enforcing a minimum password lifetime helps to prevent repeated password
changes to defeat the password reuse or history enforcement requirement. If
users are allowed to immediately and continually change their password,
then the password could be repeatedly changed in a short period of time to
defeat the organization's policy regarding password reuse.
Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. |
Set Existing Passwords Maximum Agexccdf_org.ssgproject.content_rule_accounts_password_set_max_life_existing mediumCCE-86031-2
Set Existing Passwords Maximum Age
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_set_max_life_existing | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-86031-2 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | Configure non-compliant accounts to enforce a 60-day maximum password lifetime
restriction by running the following command:
$ sudo chage -M 60
USER
| ||||||||||||||
| Rationale | Any password, no matter how complex, can eventually be cracked. Therefore,
passwords need to be changed periodically. If the operating system does
not limit the lifetime of passwords and force users to change their
passwords, there is the risk that the operating system passwords could be
compromised. |
Set Existing Passwords Minimum Agexccdf_org.ssgproject.content_rule_accounts_password_set_min_life_existing mediumCCE-89069-9
Set Existing Passwords Minimum Age
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_set_min_life_existing | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-89069-9 | ||||||||||||
| References: |
| ||||||||||||
| Description | Configure non-compliant accounts to enforce a 24 hours/1 day minimum password
lifetime by running the following command:
$ sudo chage -m 1 USER
| ||||||||||||
| Rationale | Enforcing a minimum password lifetime helps to prevent repeated password
changes to defeat the password reuse or history enforcement requirement. If
users are allowed to immediately and continually change their password, the
password could be repeatedly changed in a short period of time to defeat the
organization's policy regarding password reuse. |
Verify All Account Password Hashes are Shadowed with SHA512xccdf_org.ssgproject.content_rule_accounts_password_all_shadowed_sha512 mediumCCE-89983-1
Verify All Account Password Hashes are Shadowed with SHA512
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_all_shadowed_sha512 | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-accounts_password_all_shadowed_sha512:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89983-1 | ||||||||
| References: |
| ||||||||
| Description | Verify the operating system requires the shadow password suite
configuration be set to encrypt interactive user passwords using a strong
cryptographic hash.
Check that the interactive user account passwords are using a strong
password hash with the following command:
$ sudo cut -d: -f2 /etc/shadow $6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/Password hashes ! or * indicate inactive accounts not
available for logon and are not evaluated.
If any interactive user password hash does not begin with $6,
this is a finding. | ||||||||
| Rationale | Passwords need to be protected at all times, and encryption is the standard method for
protecting passwords. If passwords are not encrypted, they can be plainly read
(i.e., clear text) and easily compromised. |
OVAL test results details
password hashes are shadowed using sha512 oval:ssg-test_accounts_password_all_shadowed_sha512:tst:1 false
No items have been found conforming to the following objects:
Object oval:ssg-object_accounts_password_all_shadowed_sha512:obj:1 of type shadow_object
| Username | Filter | Filter | Filter |
|---|---|---|---|
| .* | oval:ssg-state_accounts_password_all_shadowed_has_no_password:ste:1 | oval:ssg-state_accounts_password_all_shadowed_has_locked_password:ste:1 | oval:ssg-state_accounts_password_all_shadowed_sha512:ste:1 |
Set number of Password Hashing Rounds - password-authxccdf_org.ssgproject.content_rule_accounts_password_pam_unix_rounds_password_auth mediumCCE-83615-5
Set number of Password Hashing Rounds - password-auth
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_unix_rounds_password_auth | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83615-5 | ||||||||
| References: |
| ||||||||
| Description | Configure the number or rounds for the password hashing algorithm. This can be
accomplished by using the rounds option for the pam_unix PAM module.
In file /etc/pam.d/password-auth append rounds=100000
to the pam_unix.so entry, as shown below:
password sufficient pam_unix.so ...existing_options... rounds=100000
The system's default number of rounds is 5000. | ||||||||
| Rationale | Using a higher number of rounds makes password cracking attacks more difficult. | ||||||||
| Warnings | warning
Setting a high number of hashing rounds makes it more difficult to brute force the password,
but requires more CPU resources to authenticate users. |
Set number of Password Hashing Rounds - system-authxccdf_org.ssgproject.content_rule_accounts_password_pam_unix_rounds_system_auth mediumCCE-83621-3
Set number of Password Hashing Rounds - system-auth
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_password_pam_unix_rounds_system_auth | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83621-3 | ||||||||
| References: |
| ||||||||
| Description | Configure the number or rounds for the password hashing algorithm. This can be
accomplished by using the rounds option for the pam_unix PAM module.
In file /etc/pam.d/system-auth append rounds=100000
to the pam_unix.so entry, as shown below:
password sufficient pam_unix.so ...existing_options... rounds=100000
The system's default number of rounds is 5000. | ||||||||
| Rationale | Using a higher number of rounds makes password cracking attacks more difficult. | ||||||||
| Warnings | warning
Setting a high number of hashing rounds makes it more difficult to brute force the password,
but requires more CPU resources to authenticate users. |
All GIDs referenced in /etc/passwd must be defined in /etc/groupxccdf_org.ssgproject.content_rule_gid_passwd_group_same lowCCE-83613-0
All GIDs referenced in /etc/passwd must be defined in /etc/group
| Rule ID | xccdf_org.ssgproject.content_rule_gid_passwd_group_same | ||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-gid_passwd_group_same:def:1 | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83613-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | Add a group to the system for each GID referenced without a corresponding group. | ||||||||||||||||||||||||||||||||
| Rationale | If a user is assigned the Group Identifier (GID) of a group not existing on the system, and a group
with the Group Identifier (GID) is subsequently created, the user may have unintended rights to
any files associated with the group. |
OVAL test results details
Verify all GIDs referenced in /etc/passwd are defined in /etc/group oval:ssg-test_gid_passwd_group_same:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/passwd | root:x:0:0: |
| true | /etc/passwd | bin:x:1:1: |
| true | /etc/passwd | daemon:x:2:2: |
| true | /etc/passwd | adm:x:3:4: |
| true | /etc/passwd | lp:x:4:7: |
| true | /etc/passwd | sync:x:5:0: |
| true | /etc/passwd | shutdown:x:6:0: |
| true | /etc/passwd | halt:x:7:0: |
| true | /etc/passwd | mail:x:8:12: |
| true | /etc/passwd | operator:x:11:0: |
| true | /etc/passwd | games:x:12:100: |
| true | /etc/passwd | ftp:x:14:50: |
| true | /etc/passwd | nobody:x:65534:65534: |
| true | /etc/passwd | tss:x:59:59: |
| true | /etc/passwd | systemd-coredump:x:999:999: |
| true | /etc/passwd | dbus:x:81:81: |
| true | /etc/passwd | appuser:x:998:998: |
Prevent Login to Accounts With Empty Passwordxccdf_org.ssgproject.content_rule_no_empty_passwords highCCE-83611-4
Prevent Login to Accounts With Empty Password
| Rule ID | xccdf_org.ssgproject.content_rule_no_empty_passwords | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83611-4 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | If an account is configured for password authentication
but does not have an assigned password, it may be possible to log
into the account without authentication. Remove any instances of the
nullok in
/etc/pam.d/system-auth and
/etc/pam.d/password-auth
to prevent logins with empty passwords. | ||||||||||||||||||||||||||||||||||||
| Rationale | If an account has an empty password, anyone could log in and
run commands with the privileges of that account. Accounts with
empty passwords should never be used in operational environments. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
If the system relies on authselect tool to manage PAM settings, the remediation
will also use authselect tool. However, if any manual modification was made in
PAM files, the authselect integrity check will fail and the remediation will be
aborted in order to preserve intentional changes. In this case, an informative message will
be shown in the remediation report.
Note that this rule is not applicable for systems running within a
container. Having user with empty password within a container is not
considered a risk, because it should not be possible to directly login into
a container anyway. |
Ensure There Are No Accounts With Blank or Null Passwordsxccdf_org.ssgproject.content_rule_no_empty_passwords_etc_shadow highCCE-85972-8
Ensure There Are No Accounts With Blank or Null Passwords
| Rule ID | xccdf_org.ssgproject.content_rule_no_empty_passwords_etc_shadow | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | high | ||||||||||||||
| Identifiers: | CCE-85972-8 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | Check the "/etc/shadow" file for blank passwords with the
following command:
$ sudo awk -F: '!$2 {print $1}' /etc/shadow
If the command returns any results, this is a finding.
Configure all accounts on the system to have a password or lock
the account with the following commands:
Perform a password reset:
$ sudo passwd [username]Lock an account: $ sudo passwd -l [username] | ||||||||||||||
| Rationale | If an account has an empty password, anyone could log in and
run commands with the privileges of that account. Accounts with
empty passwords should never be used in operational environments. | ||||||||||||||
| Warnings | warning
Note that this rule is not applicable for systems running within a container. Having user with empty password within a container is not considered a risk, because it should not be possible to directly login into a container anyway. |
Verify Only Root Has UID 0xccdf_org.ssgproject.content_rule_accounts_no_uid_except_zero highCCE-83624-7
Verify Only Root Has UID 0
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_no_uid_except_zero | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83624-7 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | If any account other than root has a UID of 0, this misconfiguration should
be investigated and the accounts other than root should be removed or have
their UID changed.
If the account is associated with system commands or applications the UID should be changed to one greater than "0" but less than "1000." Otherwise assign a UID greater than "1000" that has not already been assigned. | ||||||||||||||||||||||||||||||||
| Rationale | An account has root authority if it has a UID of 0. Multiple accounts
with a UID of 0 afford more opportunity for potential intruders to
guess a password for a privileged account. Proper configuration of
sudo is recommended to afford multiple system administrators
access to root privileges in an accountable manner. |
Ensure that System Accounts Do Not Run a Shell Upon Loginxccdf_org.ssgproject.content_rule_no_shelllogin_for_systemaccounts mediumCCE-83623-9
Ensure that System Accounts Do Not Run a Shell Upon Login
| Rule ID | xccdf_org.ssgproject.content_rule_no_shelllogin_for_systemaccounts | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83623-9 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | Some accounts are not associated with a human user of the system, and exist to perform some
administrative functions. Should an attacker be able to log into these accounts, they should
not be granted access to a shell.
The login shell for each local account is stored in the last field of each line in /etc/passwd. System accounts are those user accounts with a user ID less than
1000. The user ID is stored in the third field. If any system account
other than root has a login shell, disable it with the command:
$ sudo usermod -s /sbin/nologin account
| ||||||||||||||||||||||||||||
| Rationale | Ensuring shells are not given to system accounts upon login makes it more difficult for
attackers to make use of system accounts. | ||||||||||||||||||||||||||||
| Warnings | warning
Do not perform the steps in this section on the root account. Doing so might cause the
system to become inaccessible. |
Enforce usage of pam_wheel for su authenticationxccdf_org.ssgproject.content_rule_use_pam_wheel_for_su mediumCCE-90085-2
Enforce usage of pam_wheel for su authentication
| Rule ID | xccdf_org.ssgproject.content_rule_use_pam_wheel_for_su | ||||||||||
| Result | pass | ||||||||||
| Multi-check rule | no | ||||||||||
| OVAL Definition ID | oval:ssg-use_pam_wheel_for_su:def:1 | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-90085-2 | ||||||||||
| References: |
| ||||||||||
| Description | To ensure that only users who are members of the wheel group can
run commands with altered privileges through the su command, make
sure that the following line exists in the file /etc/pam.d/su:
auth required pam_wheel.so use_uid | ||||||||||
| Rationale | The su program allows to run commands with a substitute user and
group ID. It is commonly used to run commands as the root user. Limiting
access to such command is considered a good security practice. | ||||||||||
| Warnings | warning
Members of "wheel" or GID 0 groups are checked by default if the group option is not set
for pam_wheel.so module. Therefore, members of these groups should be manually checked or
a different group should be informed according to the site policy. |
OVAL test results details
check existence of use_uid option for pam_wheel.so in /etc/pam.d/su oval:ssg-test_use_pam_wheel_for_su:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/pam.d/su | auth required pam_wheel.so use_uid |
Ensure All Accounts on the System Have Unique User IDsxccdf_org.ssgproject.content_rule_account_unique_id mediumCCE-88493-2
Ensure All Accounts on the System Have Unique User IDs
| Rule ID | xccdf_org.ssgproject.content_rule_account_unique_id | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-88493-2 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | Change user IDs (UIDs), or delete accounts, so each has a unique name. | ||||||||||||||
| Rationale | To assure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. | ||||||||||||||
| Warnings | warning
Automatic remediation of this control is not available due to unique requirements of each
system. |
Ensure All Groups on the System Have Unique Group IDxccdf_org.ssgproject.content_rule_group_unique_id mediumCCE-86043-7
Ensure All Groups on the System Have Unique Group ID
| Rule ID | xccdf_org.ssgproject.content_rule_group_unique_id | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-86043-7 | ||||||||||||
| References: |
| ||||||||||||
| Description | Change the group name or delete groups, so each has a unique id. | ||||||||||||
| Rationale | To assure accountability and prevent unauthenticated access, groups must be identified uniquely to prevent potential misuse and compromise of the system. | ||||||||||||
| Warnings | warning
Automatic remediation of this control is not available due to the unique requirements of each system. |
Ensure the Default Bash Umask is Set Correctlyxccdf_org.ssgproject.content_rule_accounts_umask_etc_bashrc mediumCCE-83644-5
Ensure the Default Bash Umask is Set Correctly
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_umask_etc_bashrc | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83644-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To ensure the default umask for users of the Bash shell is set properly,
add or correct the umask setting in /etc/bashrc to read
as follows:
umask 077
| ||||||||||||||||||||||||||
| Rationale | The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users. |
Ensure the Default C Shell Umask is Set Correctlyxccdf_org.ssgproject.content_rule_accounts_umask_etc_csh_cshrc mediumCCE-87721-7
Ensure the Default C Shell Umask is Set Correctly
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_umask_etc_csh_cshrc | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-87721-7 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | To ensure the default umask for users of the C shell is set properly,
add or correct the umask setting in /etc/csh.cshrc to read as follows:
umask 077
| ||||||||||||||||||||
| Rationale | The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users. |
Ensure the Default Umask is Set Correctly in login.defsxccdf_org.ssgproject.content_rule_accounts_umask_etc_login_defs mediumCCE-83647-8
Ensure the Default Umask is Set Correctly in login.defs
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_umask_etc_login_defs | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83647-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To ensure the default umask controlled by /etc/login.defs is set properly,
add or correct the UMASK setting in /etc/login.defs to read as follows:
UMASK 077
| ||||||||||||||||||||||||||||
| Rationale | The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read and
written to by unauthorized users. |
Ensure the Default Umask is Set Correctly in /etc/profilexccdf_org.ssgproject.content_rule_accounts_umask_etc_profile mediumCCE-90828-5
Ensure the Default Umask is Set Correctly in /etc/profile
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_umask_etc_profile | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-90828-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To ensure the default umask controlled by /etc/profile is set properly,
add or correct the umask setting in /etc/profile to read as follows:
umask 077
Note that /etc/profile also reads scripts within /etc/profile.d directory.
These scripts are also valid files to set umask value. Therefore, they should also be
considered during the check and properly remediated, if necessary. | ||||||||||||||||||||||||||
| Rationale | The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users. |
Ensure the Default Umask is Set Correctly For Interactive Usersxccdf_org.ssgproject.content_rule_accounts_umask_interactive_users mediumCCE-90365-8
Ensure the Default Umask is Set Correctly For Interactive Users
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_umask_interactive_users | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-90365-8 | ||||||
| References: |
| ||||||
| Description | Remove the UMASK environment variable from all interactive users initialization files. | ||||||
| Rationale | The umask controls the default access mode assigned to newly created files. A
umask of 077 limits new files to mode 700 or less permissive. Although umask can
be represented as a four-digit number, the first digit representing special
access modes is typically ignored or required to be 0. This requirement
applies to the globally configured system defaults and the local interactive
user defaults for each account on the system. |
Ensure Home Directories are Created for New Usersxccdf_org.ssgproject.content_rule_accounts_have_homedir_login_defs mediumCCE-88983-2
Ensure Home Directories are Created for New Users
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_have_homedir_login_defs | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-88983-2 | ||||||
| References: |
| ||||||
| Description | All local interactive user accounts, upon creation, should be assigned a home directory.
Configure the operating system to assign home directories to all new local interactive users by setting the CREATE_HOME
parameter in /etc/login.defs to yes as follows:
CREATE_HOME yes | ||||||
| Rationale | If local interactive users are not assigned a valid home directory, there is no place
for the storage and control of files they should own. |
Ensure the Logon Failure Delay is Set Correctly in login.defsxccdf_org.ssgproject.content_rule_accounts_logon_fail_delay mediumCCE-83635-3
Ensure the Logon Failure Delay is Set Correctly in login.defs
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_logon_fail_delay | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-83635-3 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | To ensure the logon failure delay controlled by /etc/login.defs is set properly,
add or correct the FAIL_DELAY setting in /etc/login.defs to read as follows:
FAIL_DELAY 4
| ||||||||||||||||||||
| Rationale | Increasing the time between a failed authentication attempt and re-prompting to
enter credentials helps to slow a single-threaded brute force attack. |
Limit the Number of Concurrent Login Sessions Allowed Per Userxccdf_org.ssgproject.content_rule_accounts_max_concurrent_login_sessions lowCCE-83641-1
Limit the Number of Concurrent Login Sessions Allowed Per User
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_max_concurrent_login_sessions | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||
| Identifiers: | CCE-83641-1 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | Limiting the number of allowed users and sessions per user can limit risks related to Denial of
Service attacks. This addresses concurrent sessions for a single account and does not address
concurrent sessions by a single user via multiple accounts. To set the number of concurrent
sessions per user add the following line in /etc/security/limits.conf or
a file under /etc/security/limits.d/:
* hard maxlogins 10
| ||||||||||||||||||||||||
| Rationale | Limiting simultaneous user logins can insulate the system from denial of service
problems caused by excessive logins. Automated login processes operating improperly or
maliciously may result in an exceptional number of simultaneous login sessions. |
Set Interactive Session Timeoutxccdf_org.ssgproject.content_rule_accounts_tmout mediumCCE-83633-8
Set Interactive Session Timeout
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_tmout | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83633-8 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | Setting the TMOUT option in /etc/profile ensures that
all user sessions will terminate based on inactivity. A value of 0 (zero)
disables the automatic logout feature and is therefore not a compliant setting.
The value of TMOUT should be a positive integer, exported, and read only.
The TMOUT
setting in a file loaded by /etc/profile, e.g.
/etc/profile.d/tmout.sh should read as follows:
typeset -xr TMOUT=600
or
declare -xr TMOUT=600
Using the typeset keyword is preferred for wider compatibility with ksh and other shells. | ||||||||||||||||||||||||||||||||
| Rationale | Terminating an idle session within a short time period reduces
the window of opportunity for unauthorized personnel to take control of a
management session enabled on the console or console port that has been
left unattended. |
Ensure that Users Path Contains Only Local Directoriesxccdf_org.ssgproject.content_rule_accounts_user_home_paths_only mediumCCE-87487-5
Ensure that Users Path Contains Only Local Directories
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_user_home_paths_only | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-87487-5 | ||||||
| References: |
| ||||||
| Description | Ensure that all interactive user initialization files executable search
path statements do not contain statements that will reference a working
directory other than the users home directory. | ||||||
| Rationale | The executable search path (typically the PATH environment variable) contains a
list of directories for the shell to search to find executables. If this path
includes the current working directory (other than the users home directory),
executables in these directories may be executed instead of system commands.
This variable is formatted as a colon-separated list of directories. If there is
an empty entry, such as a leading or trailing colon or two consecutive colons,
this is interpreted as the current working directory. If deviations from the
default system search path for the local interactive user are required, they
must be documented with the Information System Security Officer (ISSO). |
All Interactive Users Must Have A Home Directory Definedxccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_defined mediumCCE-88964-2
All Interactive Users Must Have A Home Directory Defined
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_defined | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-88964-2 | ||||||
| References: |
| ||||||
| Description | Assign home directories to all interactive users that currently do not
have a home directory assigned.
This rule checks if the home directory is properly defined in a folder which has
at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
Therefore, this rule will report a finding for home directories like /users,
/tmp or /. | ||||||
| Rationale | If local interactive users are not assigned a valid home directory, there is no
place for the storage and control of files they should own. |
All Interactive Users Home Directories Must Existxccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_exists mediumCCE-83639-5
All Interactive Users Home Directories Must Exist
| Rule ID | xccdf_org.ssgproject.content_rule_accounts_user_interactive_home_directory_exists | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83639-5 | ||||||||
| References: |
| ||||||||
| Description | Create home directories to all local interactive users that currently do not
have a home directory assigned. Use the following commands to create the user
home directory assigned in /etc/passwd:
$ sudo mkdir /home/USER
| ||||||||
| Rationale | If a local interactive user has a home directory defined that does not exist,
the user may be given access to the / directory as the current working directory
upon logon. This could create a Denial of Service because the user would not be
able to access their logon configuration files, and it may give them visibility
to system files they normally would not be able to access. |
All Interactive User Home Directories Must Be Group-Owned By The Primary Groupxccdf_org.ssgproject.content_rule_file_groupownership_home_directories mediumCCE-83629-6
All Interactive User Home Directories Must Be Group-Owned By The Primary Group
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupownership_home_directories | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-file_groupownership_home_directories:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83629-6 | ||||||||
| References: |
| ||||||||
| Description | Change the group owner of interactive users home directory to the
group found in /etc/passwd. To change the group owner of
interactive users home directory, use the following command:
$ sudo chgrp USER_GROUP /home/USER
This rule ensures every home directory related to an interactive user is
group-owned by an interactive user. It also ensures that interactive users
are group-owners of one and only one home directory. | ||||||||
| Rationale | If the Group Identifier (GID) of a local interactive users home directory is
not the same as the primary GID of the user, this would allow unauthorized
access to the users files, and users that share the same group may not be
able to access files that they legitimately should. | ||||||||
| Warnings | warning
Due to OVAL limitation, this rule can report a false negative in a
specific situation where two interactive users swap the group-ownership
of their respective home directories. |
OVAL test results details
All home directories are group-owned by a local interactive group oval:ssg-test_file_groupownership_home_directories:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupownership_home_directories_dirs:obj:1 of type file_object
| Path | Filename |
|---|---|
| Referenced variable has no values (oval:ssg-var_file_groupownership_home_directories_dirs:var:1). |
Enable authselectxccdf_org.ssgproject.content_rule_enable_authselect mediumCCE-89732-2
Enable authselect
| Rule ID | xccdf_org.ssgproject.content_rule_enable_authselect | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-89732-2 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Configure user authentication setup to use the authselect tool.
If authselect profile is selected, the rule will enable the sssd profile. | ||||||||||||||||||||
| Rationale | Authselect is a successor to authconfig.
It is a tool to select system authentication and identity sources from a list of supported
profiles instead of letting the administrator manually build the PAM stack.
That way, it avoids potential breakage of configuration, as it ships several tested profiles
that are well tested and supported to solve different use-cases. | ||||||||||||||||||||
| Warnings | warning
If the sudo authselect select command returns an error informing that the chosen
profile cannot be selected, it is probably because PAM files have already been modified by
the administrator. If this is the case, in order to not overwrite the desired changes made
by the administrator, the current PAM settings should be investigated before forcing the
selection of the chosen authselect profile. |
Verify /boot/grub2/grub.cfg Group Ownershipxccdf_org.ssgproject.content_rule_file_groupowner_grub2_cfg mediumCCE-83848-2
Verify /boot/grub2/grub.cfg Group Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_grub2_cfg | ||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83848-2 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | The file /boot/grub2/grub.cfg should
be group-owned by the root group to prevent
destruction or modification of the file.
To properly set the group owner of /boot/grub2/grub.cfg, run the command:
$ sudo chgrp root /boot/grub2/grub.cfg | ||||||||||||||||||||||||||||||||||||||
| Rationale | The root group is a highly-privileged group. Furthermore, the group-owner of this
file should not have any access privileges anyway. |
Verify /boot/grub2/grub.cfg User Ownershipxccdf_org.ssgproject.content_rule_file_owner_grub2_cfg mediumCCE-83845-8
Verify /boot/grub2/grub.cfg User Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_grub2_cfg | ||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83845-8 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | The file /boot/grub2/grub.cfg should
be owned by the root user to prevent destruction
or modification of the file.
To properly set the owner of /boot/grub2/grub.cfg, run the command:
$ sudo chown root /boot/grub2/grub.cfg | ||||||||||||||||||||||||||||||||||||||
| Rationale | Only root should be able to modify important boot parameters. |
Set the Boot Loader Admin Username to a Non-Default Valuexccdf_org.ssgproject.content_rule_grub2_admin_username highCCE-87370-3
Set the Boot Loader Admin Username to a Non-Default Value
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_admin_username | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||
| Identifiers: | CCE-87370-3 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change.
Do not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. Change the superuser to a different username (The default is 'root'). $ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_usersThe line mentioned above must be followed by the line export superusersso that the superusers is honored.
Once the superuser account has been added, update the grub.cfg file by running:
grub2-mkconfig -o /boot/grub2/grub.cfg | ||||||||||||||||||||||||
| Rationale | Having a non-default grub superuser username makes password-guessing attacks less effective. | ||||||||||||||||||||||||
| Warnings | warning
To prevent hard-coded admin usernames, automatic remediation of this control is not available. Remediation
must be automated as a component of machine provisioning, or followed manually as outlined above.
Also, do NOT manually add the superuser account and password to the
grub.cfg file as the grub2-mkconfig command overwrites this file. |
Set Boot Loader Password in grub2xccdf_org.ssgproject.content_rule_grub2_password highCCE-83849-0
Set Boot Loader Password in grub2
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_password | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83849-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
Since plaintext passwords are a security risk, generate a hash for the password by running the following command: # grub2-setpasswordWhen prompted, enter the password that was selected. | ||||||||||||||||||||||||||||||||
| Rationale | Password protection on the boot loader configuration ensures
users with physical access cannot trivially alter
important bootloader settings. These include which kernel to use,
and whether to enter single-user mode. | ||||||||||||||||||||||||||||||||
| Warnings | warning
To prevent hard-coded passwords, automatic remediation of this control is not available. Remediation
must be automated as a component of machine provisioning, or followed manually as outlined above.
Also, do NOT manually add the superuser account and password to the
grub.cfg file as the grub2-mkconfig command overwrites this file. |
The system must booted with init_on_free=1xccdf_org.ssgproject.content_rule_grub2_init_on_free mediumCCE-87483-4
The system must booted with init_on_free=1
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_init_on_free | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87483-4 | ||||||||
| References: |
| ||||||||
| Description | Setting init_on_free=1 on boot guarantees that pages and heap objects are initialized right after they're freed, so it won't be possible to access stale data by using a dangling pointer. | ||||||||
| Rationale | init_on_free is a Linux kernel boot parameter that enhances security by initializing memory regions when they are freed, preventing data leakage.
This process ensures that stale data in freed memory cannot be accessed by malicious programs. |
Enable Kernel Page-Table Isolation (KPTI)xccdf_org.ssgproject.content_rule_grub2_pti_argument lowCCE-83843-3
Enable Kernel Page-Table Isolation (KPTI)
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_pti_argument | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | low | ||||||||||
| Identifiers: | CCE-83843-3 | ||||||||||
| References: |
| ||||||||||
| Description | To enable Kernel page-table isolation,
add the argument pti=on to the default
GRUB 2 command line for the Linux operating system.
To ensure that pti=on is added as a kernel command line
argument to newly installed kernels, add pti=on to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... pti=on ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="pti=on"If the system is distributed as a bootable container image, GRUB2 can't be configured using the method described above, but the following method needs to be used instead. The kernel arguments should be set in /usr/lib/bootc/kargs.d in a TOML file that has the following form:
# /usr/lib/bootc/kargs.d/10-example.toml kargs = ["pti=on"]For more details on configuring kernel arguments in bootable container images, please refer to Bootc documentation. | ||||||||||
| Rationale | Kernel page-table isolation is a kernel feature that mitigates
the Meltdown security vulnerability and hardens the kernel
against attempts to bypass kernel address space layout
randomization (KASLR). |
Disable vsyscallsxccdf_org.ssgproject.content_rule_grub2_vsyscall_argument mediumCCE-83842-5
Disable vsyscalls
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_vsyscall_argument | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83842-5 | ||||||||||
| References: |
| ||||||||||
| Description | To disable use of virtual syscalls,
add the argument vsyscall=none to the default
GRUB 2 command line for the Linux operating system.
To ensure that vsyscall=none is added as a kernel command line
argument to newly installed kernels, add vsyscall=none to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... vsyscall=none ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="vsyscall=none"If the system is distributed as a bootable container image, GRUB2 can't be configured using the method described above, but the following method needs to be used instead. The kernel arguments should be set in /usr/lib/bootc/kargs.d in a TOML file that has the following form:
# /usr/lib/bootc/kargs.d/10-example.toml kargs = ["vsyscall=none"]For more details on configuring kernel arguments in bootable container images, please refer to Bootc documentation. | ||||||||||
| Rationale | Virtual Syscalls provide an opportunity of attack for a user who has control
of the return instruction pointer. | ||||||||||
| Warnings | warning
The vsyscall emulation is only available on x86_64 architecture
(CONFIG_X86_VSYSCALL_EMULATION) making this rule not applicable
to other CPU architectures. |
Ensure cron Is Logging To Rsyslogxccdf_org.ssgproject.content_rule_rsyslog_cron_logging mediumCCE-83994-4
Ensure cron Is Logging To Rsyslog
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_cron_logging | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83994-4 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Cron logging must be implemented to spot intrusions or trace
cron job status. If cron is not logging to rsyslog, it
can be implemented by adding the following to the RULES section of
/etc/rsyslog.conf:
If the legacy syntax is used:
cron.* /var/log/cronIf the modern syntax (RainerScript) is used: cron.* action(type="omfile" file="/var/log/cron") | ||||||||||||||||||||||
| Rationale | Cron logging can be used to trace the successful or unsuccessful execution
of cron jobs. It can also be used to spot intrusions into the use of the cron
facility by unauthorized and malicious users. |
Ensure Rsyslog Authenticates Off-Loaded Audit Recordsxccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdriverauthmode mediumCCE-86871-1
Ensure Rsyslog Authenticates Off-Loaded Audit Records
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdriverauthmode | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86871-1 | ||||||||
| References: |
| ||||||||
| Description | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs the remote system must be authenticated.
Set the following configuration option in /etc/rsyslog.conf or in a file in /etc/rsyslog.d (using legacy syntax):
$ActionSendStreamDriverAuthMode x509/nameAlternatively, use the RainerScript syntax: action(type="omfwd" Target="some.example.com" StreamDriverAuthMode="x509/name") | ||||||||
| Rationale | The audit records generated by Rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Audit records should be
protected from unauthorized access. |
Ensure Rsyslog Encrypts Off-Loaded Audit Recordsxccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdrivermode mediumCCE-90191-8
Ensure Rsyslog Encrypts Off-Loaded Audit Records
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdrivermode | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90191-8 | ||||||||
| References: |
| ||||||||
| Description | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs off a encryption system must be used.
Set the following configuration option in /etc/rsyslog.conf or in a file in /etc/rsyslog.d (using legacy syntax):
$ActionSendStreamDriverMode 1Alternatively, use the RainerScript syntax: action(type="omfwd" ... StreamDriverMode="1") | ||||||||
| Rationale | The audit records generated by Rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Audit records should be
protected from unauthorized access. |
Ensure Rsyslog Encrypts Off-Loaded Audit Recordsxccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_defaultnetstreamdriver mediumCCE-86782-0
Ensure Rsyslog Encrypts Off-Loaded Audit Records
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_defaultnetstreamdriver | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86782-0 | ||||||||
| References: |
| ||||||||
| Description | Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging. Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.
When using rsyslogd to off-load logs off an encryption system must be used.
Set the following configuration option in /etc/rsyslog.conf or in a file in /etc/rsyslog.d (using legacy syntax):
$DefaultNetstreamDriver gtlsAlternatively, use the RainerScript syntax: global(DefaultNetstreamDriver="gtls") | ||||||||
| Rationale | The audit records generated by Rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Audit records should be
protected from unauthorized access. |
Ensure remote access methods are monitored in Rsyslogxccdf_org.ssgproject.content_rule_rsyslog_remote_access_monitoring mediumCCE-87960-1
Ensure remote access methods are monitored in Rsyslog
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_remote_access_monitoring | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87960-1 | ||||||||
| References: |
| ||||||||
| Description | Logging of remote access methods must be implemented to help identify cyber
attacks and ensure ongoing compliance with remote access policies are being
audited and upheld. An examples of a remote access method is the use of the
Remote Desktop Protocol (RDP) from an external, non-organization controlled
network. The /etc/rsyslog.conf or
/etc/rsyslog.d/*.conf file should contain a match for the following
selectors: auth.*, authpriv.*, and daemon.*. If
not, use the following as an example configuration:
auth.*;authpriv.* /var/log/secure
daemon.* /var/log/messages
| ||||||||
| Rationale | Logging remote access methods can be used to trace the decrease the risks
associated with remote user access management. It can also be used to spot
cyber attacks and ensure ongoing compliance with organizational policies
surrounding the use of remote access methods. |
Enable systemd-journald Servicexccdf_org.ssgproject.content_rule_service_systemd-journald_enabled mediumCCE-85941-3
Enable systemd-journald Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_systemd-journald_enabled | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-85941-3 | ||||||||||
| References: |
| ||||||||||
| Description | The systemd-journald service is an essential component of
systemd.
The systemd-journald service can be enabled with the following command:
$ sudo systemctl enable systemd-journald.service | ||||||||||
| Rationale | In the event of a system failure, Red Hat Enterprise Linux 9 must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to system processes. |
Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Serverxccdf_org.ssgproject.content_rule_rsyslog_nolisten mediumCCE-83995-1
Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Server
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_nolisten | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83995-1 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The rsyslog daemon should not accept remote messages unless the system acts as a log
server. To ensure that it is not listening on the network, ensure any of the following lines
are not found in rsyslog configuration files.
If using legacy syntax:
$ModLoad imtcp
$InputTCPServerRun port
$ModLoad imudp
$UDPServerRun port
$ModLoad imrelp
$InputRELPServerRun port
If using RainerScript syntax:
module(load="imtcp") module(load="imudp") input(type="imtcp" port="514") input(type="imudp" port="514") | ||||||||||||||||||||||
| Rationale | Any process which receives messages from the network incurs some risk of receiving malicious
messages. This risk can be eliminated for rsyslog by configuring it not to listen on the
network. |
Ensure Logs Sent To Remote Hostxccdf_org.ssgproject.content_rule_rsyslog_remote_loghost mediumCCE-83990-2
Ensure Logs Sent To Remote Host
| Rule ID | xccdf_org.ssgproject.content_rule_rsyslog_remote_loghost | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83990-2 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To configure rsyslog to send logs to a remote log server,
open /etc/rsyslog.conf and read and understand the last section of the file,
which describes the multiple directives necessary to activate remote
logging.
Along with these other directives, the system can be configured
to forward its logs to a particular log server by
adding or correcting one of the following lines,
substituting logcollector appropriately.
The choice of protocol depends on the environment of the system;
although TCP and RELP provide more reliable message delivery,
they may not be supported in all environments.
To use UDP for log message delivery: *.* @logcollector
Or in RainerScript: *.* action(type="omfwd" ... target="logcollector" protocol="udp") To use TCP for log message delivery: *.* @@logcollector
Or in RainerScript: *.* action(type="omfwd" ... target="logcollector" protocol="tcp") To use RELP for log message delivery: *.* :omrelp:logcollector
Or in RainerScript: *.* action(type="omfwd" ... target="logcollector" protocol="relp") There must be a resolvable DNS CNAME or Alias record set to "logcollector" for logs to be sent correctly to the centralized logging utility. | ||||||||||||||||||||||||||||
| Rationale | A log server (loghost) receives syslog messages from one or more
systems. This data can be used as an additional log source in the event a
system is compromised and its local logs are suspect. Forwarding log messages
to a remote loghost also provides system administrators with a centralized
place to view the status of multiple hosts within the enterprise. | ||||||||||||||||||||||||||||
| Warnings | warning
It is important to configure queues in case the client is sending log
messages to a remote server. If queues are not configured,
the system will stop functioning when the connection
to the remote server is not available. Please consult Rsyslog
documentation for more information about configuration of queues. The
example configuration which should go into /etc/rsyslog.conf
can look like the following lines:
$ActionQueueType LinkedList $ActionQueueFileName queuefilename $ActionQueueMaxDiskSpace 1g $ActionQueueSaveOnShutdown on $ActionResumeRetryCount -1Or if using Rainer Script syntax, it could be: *.* action(type="omfwd" queue.type="linkedlist" queue.filename="example_fwd" action.resumeRetryCount="-1" queue.saveOnShutdown="on" target="example.com" port="30514" protocol="tcp") |
Ensure rsyslog-gnutls is installedxccdf_org.ssgproject.content_rule_package_rsyslog-gnutls_installed mediumCCE-83987-8
Ensure rsyslog-gnutls is installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_rsyslog-gnutls_installed | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83987-8 | ||||||||
| References: |
| ||||||||
| Description | TLS protocol support for rsyslog is installed.
The rsyslog-gnutls package can be installed with the following command:
$ sudo dnf install rsyslog-gnutls | ||||||||
| Rationale | The rsyslog-gnutls package provides Transport Layer Security (TLS) support
for the rsyslog daemon, which enables secure remote logging. |
Ensure rsyslog is Installedxccdf_org.ssgproject.content_rule_package_rsyslog_installed mediumCCE-84063-7
Ensure rsyslog is Installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_rsyslog_installed | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-84063-7 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | Rsyslog is installed by default. The rsyslog package can be installed with the following command: $ sudo dnf install rsyslog | ||||||||||||||||||||||||
| Rationale | The rsyslog package provides the rsyslog daemon, which provides
system logging services. |
Enable rsyslog Servicexccdf_org.ssgproject.content_rule_service_rsyslog_enabled mediumCCE-83989-4
Enable rsyslog Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_rsyslog_enabled | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83989-4 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The rsyslog service provides syslog-style logging by default on Red Hat Enterprise Linux 9.
The rsyslog service can be enabled with the following command:
$ sudo systemctl enable rsyslog.service | ||||||||||||||||||||||||
| Rationale | The rsyslog service must be running in order to provide
logging services, which are essential to system administration. |
Install firewalld Packagexccdf_org.ssgproject.content_rule_package_firewalld_installed mediumCCE-84021-5
Install firewalld Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_firewalld_installed | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-84021-5 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The firewalld package can be installed with the following command:
$ sudo dnf install firewalld | ||||||||||||||||||||
| Rationale | "Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.
Remote access is access to nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Red Hat Enterprise Linux 9 functionality (e.g., SSH) must be capable of taking enforcement action if the audit reveals unauthorized activity.
Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets)." |
Verify firewalld Enabledxccdf_org.ssgproject.content_rule_service_firewalld_enabled mediumCCE-90833-5
Verify firewalld Enabled
| Rule ID | xccdf_org.ssgproject.content_rule_service_firewalld_enabled | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90833-5 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description |
The firewalld service can be enabled with the following command:
$ sudo systemctl enable firewalld.service | ||||||||||||||||||||||||||||||||||||
| Rationale | Access control methods provide the ability to enhance system security posture
by restricting services and known good IP addresses and address ranges. This
prevents connections from unknown hosts and protocols. |
Firewalld Must Employ a Deny-all, Allow-by-exception Policy for Allowing Connections to Other Systemsxccdf_org.ssgproject.content_rule_configured_firewalld_default_deny mediumCCE-86049-4
Firewalld Must Employ a Deny-all, Allow-by-exception Policy for Allowing Connections to Other Systems
| Rule ID | xccdf_org.ssgproject.content_rule_configured_firewalld_default_deny | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86049-4 | ||||||||
| References: |
| ||||||||
| Description | Red Hat Enterprise Linux 9 incorporates the "firewalld" daemon, which allows for many different configurations. One of these configurations is zones.
Zones can be utilized to a deny-all, allow-by-exception approach.
The default "drop" zone will drop all incoming network packets unless it is explicitly allowed by the configuration file or is related to an outgoing network connection. | ||||||||
| Rationale | Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems.
It also permits outbound connections that may facilitate exfiltration of data. |
Configure Firewalld to Use the Nftables Backendxccdf_org.ssgproject.content_rule_firewalld-backend mediumCCE-86507-1
Configure Firewalld to Use the Nftables Backend
| Rule ID | xccdf_org.ssgproject.content_rule_firewalld-backend | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86507-1 | ||||||||
| References: |
| ||||||||
| Description | Firewalld can be configured with many backends, such as nftables. | ||||||||
| Rationale | Nftables is modern kernel module for controlling network connections coming into a system.
Utilizing the limit statement in "nftables" can help to mitigate DoS attacks. |
Install libreswan Packagexccdf_org.ssgproject.content_rule_package_libreswan_installed mediumCCE-84068-6
Install libreswan Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_libreswan_installed | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-84068-6 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The libreswan package provides an implementation of IPsec
and IKE, which permits the creation of secure tunnels over
untrusted networks. The libreswan package can be installed with the following command:
$ sudo dnf install libreswan | ||||||||||||||||||||||
| Rationale | Providing the ability for remote users or systems
to initiate a secure VPN connection protects information when it is
transmitted over a wide area network. |
Verify Any Configured IPSec Tunnel Connectionsxccdf_org.ssgproject.content_rule_libreswan_approved_tunnels mediumCCE-90319-5
Verify Any Configured IPSec Tunnel Connections
| Rule ID | xccdf_org.ssgproject.content_rule_libreswan_approved_tunnels | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-90319-5 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Libreswan provides an implementation of IPsec
and IKE, which permits the creation of secure tunnels over
untrusted networks. As such, IPsec can be used to circumvent certain
network requirements such as filtering. Verify that if any IPsec connection
( conn) configured in /etc/ipsec.conf and /etc/ipsec.d
exists is an approved organizational connection. | ||||||||||||||||||||||
| Rationale | IP tunneling mechanisms can be used to bypass network filtering. | ||||||||||||||||||||||
| Warnings | warning
Automatic remediation of this control is not available due to the unique
requirements of each system. |
Configure Accepting Router Advertisements on All IPv6 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_ra mediumCCE-84120-5
Configure Accepting Router Advertisements on All IPv6 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_ra | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84120-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_ra = 0 | ||||||||||||||||||||||||||
| Rationale | An illicit router advertisement message could result in a man-in-the-middle attack. |
Disable Accepting ICMP Redirects for All IPv6 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_redirects mediumCCE-84125-4
Disable Accepting ICMP Redirects for All IPv6 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_redirects | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84125-4 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_redirects = 0 | ||||||||||||||||||||||||||||
| Rationale | An illicit ICMP redirect message could result in a man-in-the-middle attack. |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_source_route mediumCCE-84131-2
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv6 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_accept_source_route | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84131-2 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.accept_source_route = 0 | ||||||||||||||||||||||||||||
| Rationale | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.
Accepting source-routed packets in the IPv6 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for IPv6 Forwardingxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_forwarding mediumCCE-84114-8
Disable Kernel Parameter for IPv6 Forwarding
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_all_forwarding | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-84114-8 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.all.forwarding=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.all.forwarding = 0 | ||||||||||||||||||||||
| Rationale | IP forwarding permits the kernel to forward packets from one network
interface to another. The ability to forward packets between two networks is
only appropriate for systems acting as routers. |
Disable Accepting Router Advertisements on all IPv6 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_ra mediumCCE-84124-7
Disable Accepting Router Advertisements on all IPv6 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_ra | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84124-7 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_ra = 0 | ||||||||||||||||||||||||||
| Rationale | An illicit router advertisement message could result in a man-in-the-middle attack. |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_redirects mediumCCE-84113-0
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv6 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_redirects | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84113-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_redirects = 0 | ||||||||||||||||||||||||||||
| Rationale | An illicit ICMP redirect message could result in a man-in-the-middle attack. |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_source_route mediumCCE-84130-4
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv6 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv6_conf_default_accept_source_route | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84130-4 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv6.conf.default.accept_source_route = 0 | ||||||||||||||||||||||||||||||||
| Rationale | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.
Accepting source-routed packets in the IPv6 protocol has few legitimate
uses. It should be disabled unless it is absolutely required. |
Disable Accepting ICMP Redirects for All IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_redirects mediumCCE-84011-6
Disable Accepting ICMP Redirects for All IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_redirects | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-84011-6 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.accept_redirects = 0 | ||||||||||||||||||||||||||||||
| Rationale | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required." |
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_source_route mediumCCE-84001-7
Disable Kernel Parameter for Accepting Source-Routed Packets on all IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_accept_source_route | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-84001-7 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.accept_source_route = 0 | ||||||||||||||||||||||||||||||
| Rationale | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures. This requirement
applies only to the forwarding of source-routerd traffic, such as when IPv4
forwarding is enabled and the system is functioning as a router.
Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for IPv4 Forwarding on all IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_forwarding mediumCCE-87181-4
Disable Kernel Parameter for IPv4 Forwarding on all IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_forwarding | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87181-4 | ||||||||
| References: |
| ||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.forwarding kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.forwarding=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.forwarding = 0 | ||||||||
| Rationale | IP forwarding permits the kernel to forward packets from one network
interface to another. The ability to forward packets between two networks is
only appropriate for systems acting as routers. | ||||||||
| Warnings | warning
There might be cases when certain applications can systematically override this option.
One such case is Libvirt; a toolkit for managing of virtualization platforms.
By default, Libvirt requires IP forwarding to be enabled to facilitate
network communication between the virtualization host and guest
machines. It enables IP forwarding after every reboot. |
Enable Kernel Parameter to Log Martian Packets on all IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_log_martians unknownCCE-84000-9
Enable Kernel Parameter to Log Martian Packets on all IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_log_martians | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | unknown | ||||||||||||||||||||||||||
| Identifiers: | CCE-84000-9 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.log_martians kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.log_martians=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.log_martians = 1 | ||||||||||||||||||||||||||
| Rationale | The presence of "martian" packets (which have impossible addresses)
as well as spoofed packets, source-routed packets, and redirects could be a
sign of nefarious network activity. Logging these packets enables this activity
to be detected. |
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_rp_filter mediumCCE-84008-2
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_rp_filter | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84008-2 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.rp_filter = 1 | ||||||||||||||||||||||||||||||||
| Rationale | Enabling reverse path filtering drops packets with source addresses
that should not have been able to be received on the interface they were
received on. It should not be used on systems which are routers for
complicated networks, but is helpful for end hosts and routers serving small
networks. |
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_redirects mediumCCE-84003-3
Disable Kernel Parameter for Accepting ICMP Redirects by Default on IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_redirects | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84003-3 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.accept_redirects = 0 | ||||||||||||||||||||||||||||||||||
| Rationale | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required. |
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_source_route mediumCCE-84007-4
Disable Kernel Parameter for Accepting Source-Routed Packets on IPv4 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_accept_source_route | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84007-4 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.accept_source_route = 0 | ||||||||||||||||||||||||||||||||
| Rationale | Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures.
Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required, such as when IPv4 forwarding is enabled and the system is legitimately functioning as a router. |
Enable Kernel Parameter to Log Martian Packets on all IPv4 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_log_martians unknownCCE-84014-0
Enable Kernel Parameter to Log Martian Packets on all IPv4 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_log_martians | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | unknown | ||||||||||||||||||||||||||
| Identifiers: | CCE-84014-0 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.default.log_martians kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.log_martians=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.log_martians = 1 | ||||||||||||||||||||||||||
| Rationale | The presence of "martian" packets (which have impossible addresses)
as well as spoofed packets, source-routed packets, and redirects could be a
sign of nefarious network activity. Logging these packets enables this activity
to be detected. |
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_rp_filter mediumCCE-84009-0
Enable Kernel Parameter to Use Reverse Path Filtering on all IPv4 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_rp_filter | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84009-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.default.rp_filter kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.rp_filter=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.rp_filter = 1 | ||||||||||||||||||||||||||||
| Rationale | Enabling reverse path filtering drops packets with source addresses
that should not have been able to be received on the interface they were
received on. It should not be used on systems which are routers for
complicated networks, but is helpful for end hosts and routers serving small
networks. |
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_icmp_echo_ignore_broadcasts mediumCCE-84004-1
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests on IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_icmp_echo_ignore_broadcasts | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84004-1 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.icmp_echo_ignore_broadcasts = 1 | ||||||||||||||||||||||||||||||||||
| Rationale | Responding to broadcast (ICMP) echoes facilitates network mapping
and provides a vector for amplification attacks.
Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network. |
Enable Kernel Parameter to Ignore Bogus ICMP Error Responses on IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_icmp_ignore_bogus_error_responses unknownCCE-84015-7
Enable Kernel Parameter to Ignore Bogus ICMP Error Responses on IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_icmp_ignore_bogus_error_responses | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | unknown | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84015-7 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.icmp_ignore_bogus_error_responses kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.icmp_ignore_bogus_error_responses = 1 | ||||||||||||||||||||||||||||||||||
| Rationale | Ignoring bogus ICMP error responses reduces
log size, although some activity would not be logged. |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfacesxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_send_redirects mediumCCE-83997-7
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_all_send_redirects | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83997-7 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.all.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.all.send_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.all.send_redirects = 0 | ||||||||||||||||||||||||||||||||||
| Rationale | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
The ability to send ICMP redirects is only appropriate for systems acting as routers. |
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Defaultxccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_send_redirects mediumCCE-83999-3
Disable Kernel Parameter for Sending ICMP Redirects on all IPv4 Interfaces by Default
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_ipv4_conf_default_send_redirects | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83999-3 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To set the runtime status of the net.ipv4.conf.default.send_redirects kernel parameter, run the following command: $ sudo sysctl -w net.ipv4.conf.default.send_redirects=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.ipv4.conf.default.send_redirects = 0 | ||||||||||||||||||||||||||||||||||
| Rationale | ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
The ability to send ICMP redirects is only appropriate for systems acting as routers. |
Disable ATM Supportxccdf_org.ssgproject.content_rule_kernel_module_atm_disabled mediumCCE-84137-9
Disable ATM Support
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_atm_disabled | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-84137-9 | ||||||||
| References: |
| ||||||||
| Description | The Asynchronous Transfer Mode (ATM) is a protocol operating on
network, data link, and physical layers, based on virtual circuits
and virtual paths.
To configure the system to prevent the atm
kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
install atm /bin/falseThis entry will cause a non-zero return value during a atm module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install atm /bin/true | ||||||||
| Rationale | Disabling ATM protects the system against exploitation of any
flaws in its implementation. |
Disable CAN Supportxccdf_org.ssgproject.content_rule_kernel_module_can_disabled mediumCCE-84134-6
Disable CAN Support
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_can_disabled | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-84134-6 | ||||||||||
| References: |
| ||||||||||
| Description | The Controller Area Network (CAN) is a serial communications
protocol which was initially developed for automotive and
is now also used in marine, industrial, and medical applications.
To configure the system to prevent the can
kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
install can /bin/falseThis entry will cause a non-zero return value during a can module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install can /bin/true | ||||||||||
| Rationale | Disabling CAN protects the system against exploitation of any
flaws in its implementation. |
Disable IEEE 1394 (FireWire) Supportxccdf_org.ssgproject.content_rule_kernel_module_firewire-core_disabled lowCCE-84060-3
Disable IEEE 1394 (FireWire) Support
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_firewire-core_disabled | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||
| Severity | low | ||||||||||
| Identifiers: | CCE-84060-3 | ||||||||||
| References: |
| ||||||||||
| Description | The IEEE 1394 (FireWire) is a serial bus standard for
high-speed real-time communication.
To configure the system to prevent the firewire-core
kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
install firewire-core /bin/falseThis entry will cause a non-zero return value during a firewire-core module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install firewire-core /bin/true | ||||||||||
| Rationale | Disabling FireWire protects the system against exploitation of any
flaws in its implementation. |
Disable SCTP Supportxccdf_org.ssgproject.content_rule_kernel_module_sctp_disabled mediumCCE-84139-5
Disable SCTP Support
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_sctp_disabled | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84139-5 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The Stream Control Transmission Protocol (SCTP) is a
transport layer protocol, designed to support the idea of
message-oriented communication, with several streams of messages
within one connection.
To configure the system to prevent the sctp
kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
install sctp /bin/falseThis entry will cause a non-zero return value during a sctp module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install sctp /bin/true | ||||||||||||||||||||||||||||||||
| Rationale | Disabling SCTP protects
the system against exploitation of any flaws in its implementation. |
Disable TIPC Supportxccdf_org.ssgproject.content_rule_kernel_module_tipc_disabled lowCCE-84065-2
Disable TIPC Support
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_tipc_disabled | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||
| Identifiers: | CCE-84065-2 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The Transparent Inter-Process Communication (TIPC) protocol
is designed to provide communications between nodes in a
cluster.
To configure the system to prevent the tipc
kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
install tipc /bin/falseThis entry will cause a non-zero return value during a tipc module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install tipc /bin/true | ||||||||||||||||||||||||
| Rationale | Disabling TIPC protects
the system against exploitation of any flaws in its implementation. | ||||||||||||||||||||||||
| Warnings | warning
This configuration baseline was created to deploy the base operating system for general purpose
workloads. When the operating system is configured for certain purposes, such as
a node in High Performance Computing cluster, it is expected that
the tipc kernel module will be loaded. |
Disable Bluetooth Kernel Modulexccdf_org.ssgproject.content_rule_kernel_module_bluetooth_disabled mediumCCE-84067-8
Disable Bluetooth Kernel Module
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_bluetooth_disabled | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84067-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The kernel's module loading system can be configured to prevent
loading of the Bluetooth module. Add the following to
the appropriate /etc/modprobe.d configuration file
to prevent the loading of the Bluetooth module:
install bluetooth /bin/true | ||||||||||||||||||||||||||||
| Rationale | If Bluetooth functionality must be disabled, preventing the kernel
from loading the kernel module provides an additional safeguard against its
activation. |
Deactivate Wireless Network Interfacesxccdf_org.ssgproject.content_rule_wireless_disable_interfaces mediumCCE-84066-0
Deactivate Wireless Network Interfaces
| Rule ID | xccdf_org.ssgproject.content_rule_wireless_disable_interfaces | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84066-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | Deactivating wireless network interfaces should prevent normal usage of the wireless
capability.
Configure the system to disable all wireless network interfaces with the following command: $ sudo nmcli radio all off | ||||||||||||||||||||||||||||||||
| Rationale | The use of wireless networking can introduce many different attack vectors into
the organization's network. Common attack vectors such as malicious association
and ad hoc networks will allow an attacker to spoof a wireless access point
(AP), allowing validated systems to connect to the malicious AP and enabling the
attacker to monitor and record network traffic. These malicious APs can also
serve to create a man-in-the-middle attack or be used to create a denial of
service to valid network resources. |
NetworkManager DNS Mode Must Be Must Configuredxccdf_org.ssgproject.content_rule_networkmanager_dns_mode mediumCCE-86805-9
NetworkManager DNS Mode Must Be Must Configured
| Rule ID | xccdf_org.ssgproject.content_rule_networkmanager_dns_mode | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86805-9 | ||||||||
| References: |
| ||||||||
| Description | The DNS processing mode in NetworkManager describes how DNS is processed on the system. Depending the mode some changes the system's DNS may not be respected. | ||||||||
| Rationale | To ensure that DNS resolver settings are respected, a DNS mode in NetworkManager must be configured. |
Configure Multiple DNS Servers in /etc/resolv.confxccdf_org.ssgproject.content_rule_network_configure_name_resolution mediumCCE-86858-8
Configure Multiple DNS Servers in /etc/resolv.conf
| Rule ID | xccdf_org.ssgproject.content_rule_network_configure_name_resolution | ||||||||||||||||||
| Result | pass | ||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||
| OVAL Definition ID | oval:ssg-network_configure_name_resolution:def:1 | ||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||
| Severity | medium | ||||||||||||||||||
| Identifiers: | CCE-86858-8 | ||||||||||||||||||
| References: |
| ||||||||||||||||||
| Description |
Determine whether the system is using local or DNS name resolution with the
following command:
$ sudo grep hosts /etc/nsswitch.conf hosts: files dnsIf the DNS entry is missing from the host's line in the "/etc/nsswitch.conf" file, the "/etc/resolv.conf" file must be empty. Verify the "/etc/resolv.conf" file is empty with the following command: $ sudo ls -al /etc/resolv.conf -rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.confIf the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file, then verify the following: Multiple Domain Name System (DNS) Servers should be configured in /etc/resolv.conf. This provides redundant name resolution services
in the event that a domain server crashes. To configure the system to contain
as least 2 DNS servers, add a corresponding nameserver
ip_address
entry in /etc/resolv.conf for each DNS
server where ip_address is the IP address of a valid DNS server.
For example:
search example.com nameserver 192.168.0.1 nameserver 192.168.0.2 | ||||||||||||||||||
| Rationale | To provide availability for name resolution services, multiple redundant
name servers are mandated. A failure in name resolution could lead to the
failure of security functions requiring name resolution, which may include
time synchronization, centralized authentication, and remote system logging. | ||||||||||||||||||
| Warnings | warning
This rule doesn't come with a remediation, the IP addresses of local authoritative name servers need to be added by the administrator. |
OVAL test results details
check if dns is set in host line in /etc/nsswitch.conf oval:ssg-test_host_line_dns_parameter_nsswitch:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/nsswitch.conf | hosts: files dns myhostname |
check if more than one nameserver in /etc/resolv.conf oval:ssg-test_network_configure_name_resolution:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/resolv.conf | nameserver 169.254.169.254 |
check if dns is set in host line in /etc/nsswitch.conf oval:ssg-test_host_line_dns_parameter_nsswitch:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| not evaluated | /etc/nsswitch.conf | hosts: files dns myhostname |
check if /etc/resolv.conf is empty oval:ssg-test_file_empty_resolv:tst:1 false
Following items have been found on the system:
| Result of item-state comparison | Path | Type | UID | GID | Size (B) | Permissions |
|---|---|---|---|---|---|---|
| false | /etc/resolv.conf | regular | 0 | 0 | 54 | rw-r--r-- |
Ensure System is Not Acting as a Network Snifferxccdf_org.ssgproject.content_rule_network_sniffer_disabled mediumCCE-83996-9
Ensure System is Not Acting as a Network Sniffer
| Rule ID | xccdf_org.ssgproject.content_rule_network_sniffer_disabled | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83996-9 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The system should not be acting as a network sniffer, which can
capture all traffic on the network to which it is connected. Run the following
to determine if any interface is running in promiscuous mode:
$ ip link | grep PROMISCPromiscuous mode of an interface can be disabled with the following command: $ sudo ip link set dev
| ||||||||||||||||||||||||
| Rationale | Network interfaces in promiscuous mode allow for the capture of all network traffic
visible to the system. If unauthorized individuals can access these applications, it
may allow them to collect information such as logon IDs, passwords, and key exchanges
between systems.
If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information Systems Security Manager (ISSM) and restricted to only authorized personnel. |
Verify Group Who Owns Backup group Filexccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_group mediumCCE-83928-2
Verify Group Who Owns Backup group File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_group | ||||||||||||||||
| Result | pass | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_backup_etc_group:def:1 | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83928-2 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To properly set the group owner of /etc/group-, run the command:
$ sudo chgrp root /etc/group- | ||||||||||||||||
| Rationale | The /etc/group- file is a backup file of /etc/group, and as such,
it contains information regarding groups that are configured on the system.
Protection of this file is important for system security. |
OVAL test results details
Testing group ownership of /etc/group- oval:ssg-test_file_groupowner_backup_etc_group_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_backup_etc_group_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/group- | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_backup_etc_group_0_0:ste:1 |
Verify Group Who Owns Backup gshadow Filexccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_gshadow mediumCCE-83951-4
Verify Group Who Owns Backup gshadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_gshadow | ||||||||||||||
| Result | pass | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_backup_etc_gshadow:def:1 | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83951-4 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To properly set the group owner of /etc/gshadow-, run the command:
$ sudo chgrp root /etc/gshadow- | ||||||||||||||
| Rationale | The /etc/gshadow- file is a backup of /etc/gshadow, and as such,
it contains group password hashes. Protection of this file is critical for system security. |
OVAL test results details
Testing group ownership of /etc/gshadow- oval:ssg-test_file_groupowner_backup_etc_gshadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_backup_etc_gshadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/gshadow- | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_backup_etc_gshadow_0_0:ste:1 |
Verify Group Who Owns Backup passwd Filexccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_passwd mediumCCE-83933-2
Verify Group Who Owns Backup passwd File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_passwd | ||||||||||||||||
| Result | pass | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_backup_etc_passwd:def:1 | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83933-2 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To properly set the group owner of /etc/passwd-, run the command:
$ sudo chgrp root /etc/passwd- | ||||||||||||||||
| Rationale | The /etc/passwd- file is a backup file of /etc/passwd, and as such,
it contains information about the users that are configured on the system.
Protection of this file is critical for system security. |
OVAL test results details
Testing group ownership of /etc/passwd- oval:ssg-test_file_groupowner_backup_etc_passwd_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_backup_etc_passwd_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/passwd- | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_backup_etc_passwd_0_0:ste:1 |
Verify User Who Owns Backup shadow Filexccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_shadow mediumCCE-83938-1
Verify User Who Owns Backup shadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_shadow | ||||||||||||||
| Result | pass | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_backup_etc_shadow:def:1 | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83938-1 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To properly set the group owner of /etc/shadow-, run the command:
$ sudo chgrp root /etc/shadow- | ||||||||||||||
| Rationale | The /etc/shadow- file is a backup file of /etc/shadow, and as such,
it contains the list of local system accounts and password hashes.
Protection of this file is critical for system security. |
OVAL test results details
Testing group ownership of /etc/shadow- oval:ssg-test_file_groupowner_backup_etc_shadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_backup_etc_shadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/shadow- | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_backup_etc_shadow_0_0:ste:1 |
Verify Group Who Owns group Filexccdf_org.ssgproject.content_rule_file_groupowner_etc_group mediumCCE-83945-6
Verify Group Who Owns group File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_etc_group | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_etc_group:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83945-6 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the group owner of /etc/group, run the command:
$ sudo chgrp root /etc/group | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/group file contains information regarding groups that are configured
on the system. Protection of this file is important for system security. |
OVAL test results details
Testing group ownership of /etc/group oval:ssg-test_file_groupowner_etc_group_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_etc_group_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/group | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_etc_group_0_0:ste:1 |
Verify Group Who Owns gshadow Filexccdf_org.ssgproject.content_rule_file_groupowner_etc_gshadow mediumCCE-83948-0
Verify Group Who Owns gshadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_etc_gshadow | ||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_etc_gshadow:def:1 | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83948-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To properly set the group owner of /etc/gshadow, run the command:
$ sudo chgrp root /etc/gshadow | ||||||||||||||||||||||||||||
| Rationale | The /etc/gshadow file contains group password hashes. Protection of this file
is critical for system security. |
OVAL test results details
Testing group ownership of /etc/gshadow oval:ssg-test_file_groupowner_etc_gshadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_etc_gshadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/gshadow | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_etc_gshadow_0_0:ste:1 |
Verify Group Who Owns passwd Filexccdf_org.ssgproject.content_rule_file_groupowner_etc_passwd mediumCCE-83950-6
Verify Group Who Owns passwd File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_etc_passwd | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_etc_passwd:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83950-6 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the group owner of /etc/passwd, run the command:
$ sudo chgrp root /etc/passwd | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/passwd file contains information about the users that are configured on
the system. Protection of this file is critical for system security. |
OVAL test results details
Testing group ownership of /etc/passwd oval:ssg-test_file_groupowner_etc_passwd_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_etc_passwd_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/passwd | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_etc_passwd_0_0:ste:1 |
Verify Group Who Owns shadow Filexccdf_org.ssgproject.content_rule_file_groupowner_etc_shadow mediumCCE-83930-8
Verify Group Who Owns shadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_etc_shadow | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_etc_shadow:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83930-8 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the group owner of /etc/shadow, run the command:
$ sudo chgrp root /etc/shadow | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/shadow file stores password hashes. Protection of this file is
critical for system security. |
OVAL test results details
Testing group ownership of /etc/shadow oval:ssg-test_file_groupowner_etc_shadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_etc_shadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/shadow | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_etc_shadow_0_0:ste:1 |
Verify User Who Owns Backup group Filexccdf_org.ssgproject.content_rule_file_owner_backup_etc_group mediumCCE-83944-9
Verify User Who Owns Backup group File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_backup_etc_group | ||||||||||||||||
| Result | pass | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_backup_etc_group:def:1 | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83944-9 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To properly set the owner of /etc/group-, run the command:
$ sudo chown root /etc/group- | ||||||||||||||||
| Rationale | The /etc/group- file is a backup file of /etc/group, and as such,
it contains information regarding groups that are configured on the system.
Protection of this file is important for system security. |
OVAL test results details
Testing user ownership of /etc/group- oval:ssg-test_file_owner_backup_etc_group_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_backup_etc_group_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/group- | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_backup_etc_group_0_0:ste:1 |
Verify User Who Owns Backup gshadow Filexccdf_org.ssgproject.content_rule_file_owner_backup_etc_gshadow mediumCCE-83929-0
Verify User Who Owns Backup gshadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_backup_etc_gshadow | ||||||||||||||
| Result | pass | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_backup_etc_gshadow:def:1 | ||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83929-0 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To properly set the owner of /etc/gshadow-, run the command:
$ sudo chown root /etc/gshadow- | ||||||||||||||
| Rationale | The /etc/gshadow- file is a backup of /etc/gshadow, and as such,
it contains group password hashes. Protection of this file is critical for system security. |
OVAL test results details
Testing user ownership of /etc/gshadow- oval:ssg-test_file_owner_backup_etc_gshadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_backup_etc_gshadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/gshadow- | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_backup_etc_gshadow_0_0:ste:1 |
Verify User Who Owns Backup passwd Filexccdf_org.ssgproject.content_rule_file_owner_backup_etc_passwd mediumCCE-83947-2
Verify User Who Owns Backup passwd File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_backup_etc_passwd | ||||||||||||||||
| Result | pass | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_backup_etc_passwd:def:1 | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83947-2 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To properly set the owner of /etc/passwd-, run the command:
$ sudo chown root /etc/passwd- | ||||||||||||||||
| Rationale | The /etc/passwd- file is a backup file of /etc/passwd, and as such,
it contains information about the users that are configured on the system.
Protection of this file is critical for system security. |
OVAL test results details
Testing user ownership of /etc/passwd- oval:ssg-test_file_owner_backup_etc_passwd_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_backup_etc_passwd_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/passwd- | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_backup_etc_passwd_0_0:ste:1 |
Verify Group Who Owns Backup shadow Filexccdf_org.ssgproject.content_rule_file_owner_backup_etc_shadow mediumCCE-83949-8
Verify Group Who Owns Backup shadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_backup_etc_shadow | ||||||||||||||||
| Result | pass | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_backup_etc_shadow:def:1 | ||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83949-8 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To properly set the owner of /etc/shadow-, run the command:
$ sudo chown root /etc/shadow- | ||||||||||||||||
| Rationale | The /etc/shadow- file is a backup file of /etc/shadow, and as such,
it contains the list of local system accounts and password hashes.
Protection of this file is critical for system security. |
OVAL test results details
Testing user ownership of /etc/shadow- oval:ssg-test_file_owner_backup_etc_shadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_backup_etc_shadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/shadow- | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_backup_etc_shadow_0_0:ste:1 |
Verify User Who Owns group Filexccdf_org.ssgproject.content_rule_file_owner_etc_group mediumCCE-83925-8
Verify User Who Owns group File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_etc_group | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_etc_group:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83925-8 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the owner of /etc/group, run the command:
$ sudo chown root /etc/group | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/group file contains information regarding groups that are configured
on the system. Protection of this file is important for system security. |
OVAL test results details
Testing user ownership of /etc/group oval:ssg-test_file_owner_etc_group_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_etc_group_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/group | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_etc_group_0_0:ste:1 |
Verify User Who Owns gshadow Filexccdf_org.ssgproject.content_rule_file_owner_etc_gshadow mediumCCE-83924-1
Verify User Who Owns gshadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_etc_gshadow | ||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_etc_gshadow:def:1 | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83924-1 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | To properly set the owner of /etc/gshadow, run the command:
$ sudo chown root /etc/gshadow | ||||||||||||||||||||||||||||
| Rationale | The /etc/gshadow file contains group password hashes. Protection of this file
is critical for system security. |
OVAL test results details
Testing user ownership of /etc/gshadow oval:ssg-test_file_owner_etc_gshadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_etc_gshadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/gshadow | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_etc_gshadow_0_0:ste:1 |
Verify User Who Owns passwd Filexccdf_org.ssgproject.content_rule_file_owner_etc_passwd mediumCCE-83943-1
Verify User Who Owns passwd File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_etc_passwd | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_etc_passwd:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83943-1 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the owner of /etc/passwd, run the command:
$ sudo chown root /etc/passwd | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/passwd file contains information about the users that are configured on
the system. Protection of this file is critical for system security. |
OVAL test results details
Testing user ownership of /etc/passwd oval:ssg-test_file_owner_etc_passwd_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_etc_passwd_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/passwd | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_etc_passwd_0_0:ste:1 |
Verify User Who Owns shadow Filexccdf_org.ssgproject.content_rule_file_owner_etc_shadow mediumCCE-83926-6
Verify User Who Owns shadow File
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_etc_shadow | ||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_owner_etc_shadow:def:1 | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83926-6 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To properly set the owner of /etc/shadow, run the command:
$ sudo chown root /etc/shadow | ||||||||||||||||||||||||||||||||||
| Rationale | The /etc/shadow file contains the list of local
system accounts and stores password hashes. Protection of this file is
critical for system security. Failure to give ownership of this file
to root provides the designated owner with access to sensitive information
which could weaken the system security posture. |
OVAL test results details
Testing user ownership of /etc/shadow oval:ssg-test_file_owner_etc_shadow_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_etc_shadow_0:obj:1 of type file_object
| Filepath | Filter | Filter |
|---|---|---|
| /etc/shadow | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_etc_shadow_0_0:ste:1 |
Verify Group Who Owns /var/log Directoryxccdf_org.ssgproject.content_rule_file_groupowner_var_log mediumCCE-83912-6
Verify Group Who Owns /var/log Directory
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_var_log | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-file_groupowner_var_log:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83912-6 | ||||||||
| References: |
| ||||||||
| Description | To properly set the group owner of /var/log, run the command:
$ sudo chgrp root /var/log | ||||||||
| Rationale | The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel. |
OVAL test results details
Testing group ownership of /var/log/ oval:ssg-test_file_groupowner_var_log_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupowner_var_log_0:obj:1 of type file_object
| Path | Filename | Filter | Filter |
|---|---|---|---|
| /var/log | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupowner_var_log_0_0:ste:1 |
Verify User Who Owns /var/log Directoryxccdf_org.ssgproject.content_rule_file_owner_var_log mediumCCE-83914-2
Verify User Who Owns /var/log Directory
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_var_log | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-file_owner_var_log:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83914-2 | ||||||||
| References: |
| ||||||||
| Description | To properly set the owner of /var/log, run the command:
$ sudo chown root /var/log | ||||||||
| Rationale | The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel. |
OVAL test results details
Testing user ownership of /var/log/ oval:ssg-test_file_owner_var_log_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_owner_var_log_0:obj:1 of type file_object
| Path | Filename | Filter | Filter |
|---|---|---|---|
| /var/log | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_owner_var_log_0_0:ste:1 |
Verify that Shared Library Directories Have Root Group Ownershipxccdf_org.ssgproject.content_rule_dir_group_ownership_library_dirs mediumCCE-89858-5
Verify that Shared Library Directories Have Root Group Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_dir_group_ownership_library_dirs | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-dir_group_ownership_library_dirs:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89858-5 | ||||||||
| References: |
| ||||||||
| Description | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be
group-owned by the root user. If the directories, is found to be owned
by a user other than root correct its
ownership with the following command:
$ sudo chgrp root DIR
| ||||||||
| Rationale | Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership of library directories is necessary to protect
the integrity of the system. |
OVAL test results details
Testing group ownership of /lib/ oval:ssg-test_file_groupownerdir_group_ownership_library_dirs_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupownerdir_group_ownership_library_dirs_0:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupownerdir_group_ownership_library_dirs_0_0:ste:1 |
Testing group ownership of /lib64/ oval:ssg-test_file_groupownerdir_group_ownership_library_dirs_1:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupownerdir_group_ownership_library_dirs_1:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib64 | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupownerdir_group_ownership_library_dirs_0_0:ste:1 |
Testing group ownership of /usr/lib/ oval:ssg-test_file_groupownerdir_group_ownership_library_dirs_2:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupownerdir_group_ownership_library_dirs_2:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupownerdir_group_ownership_library_dirs_0_0:ste:1 |
Testing group ownership of /usr/lib64/ oval:ssg-test_file_groupownerdir_group_ownership_library_dirs_3:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_groupownerdir_group_ownership_library_dirs_3:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib64 | oval:ssg-symlink_file_groupowner:ste:1 | oval:ssg-state_file_groupownerdir_group_ownership_library_dirs_0_0:ste:1 |
Verify that Shared Library Directories Have Root Ownershipxccdf_org.ssgproject.content_rule_dir_ownership_library_dirs mediumCCE-89022-8
Verify that Shared Library Directories Have Root Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_dir_ownership_library_dirs | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-dir_ownership_library_dirs:def:1 | ||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89022-8 | ||||||||
| References: |
| ||||||||
| Description | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be
owned by the root user. If the directories, is found to be owned
by a user other than root correct its
ownership with the following command:
$ sudo chown root DIR
| ||||||||
| Rationale | Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership of library directories is necessary to protect
the integrity of the system. |
OVAL test results details
Testing user ownership of /lib/ oval:ssg-test_file_ownerdir_ownership_library_dirs_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownerdir_ownership_library_dirs_0:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownerdir_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /lib64/ oval:ssg-test_file_ownerdir_ownership_library_dirs_1:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownerdir_ownership_library_dirs_1:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib64 | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownerdir_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /usr/lib/ oval:ssg-test_file_ownerdir_ownership_library_dirs_2:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownerdir_ownership_library_dirs_2:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownerdir_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /usr/lib64/ oval:ssg-test_file_ownerdir_ownership_library_dirs_3:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownerdir_ownership_library_dirs_3:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib64 | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownerdir_ownership_library_dirs_0_0:ste:1 |
Verify that system commands files are group owned by root or a system accountxccdf_org.ssgproject.content_rule_file_groupownership_system_commands_dirs mediumCCE-89442-8
Verify that system commands files are group owned by root or a system account
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupownership_system_commands_dirs | ||||||||||
| Result | pass | ||||||||||
| Multi-check rule | no | ||||||||||
| OVAL Definition ID | oval:ssg-file_groupownership_system_commands_dirs:def:1 | ||||||||||
| Time | 2026-06-11T16:45:08+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-89442-8 | ||||||||||
| References: |
| ||||||||||
| Description | System commands files are stored in the following directories by default:
/bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbinAll files in these directories should be owned by the root group,
or a system account.
If the directory, or any file in these directories, is found to be owned
by a group other than root or a a system account correct its ownership
with the following command:
$ sudo chgrp root FILE
| ||||||||||
| Rationale | If the operating system allows any user to make changes to software
libraries, then those changes might be implemented without undergoing the
appropriate testing and approvals that are part of a robust change management
process.
This requirement applies to operating systems with software libraries
that are accessible and configurable, as in the case of interpreted languages.
Software libraries also include privileged programs which execute with
escalated privileges. Only qualified and authorized individuals must be
allowed to obtain access to information system components for purposes
of initiating changes, including upgrades and modifications. |
OVAL test results details
system commands are owned by root or a system account oval:ssg-test_groupownership_system_commands_dirs:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_groupownership_system_commands_dirs:obj:1 of type file_object
| Path | Filename | Filter | Filter |
|---|---|---|---|
| ^\/s?bin|^\/usr\/s?bin|^\/usr\/local\/s?bin | ^.*$ | oval:ssg-state_groupowner_system_commands_dirs_not_root_or_system_account:ste:1 | oval:ssg-state_groupowner_system_commands_dirs_symlink:ste:1 |
Verify that System Executables Have Root Ownershipxccdf_org.ssgproject.content_rule_file_ownership_binary_dirs mediumCCE-83908-4
Verify that System Executables Have Root Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_file_ownership_binary_dirs | ||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_ownership_binary_dirs:def:1 | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:08+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83908-4 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | System executables are stored in the following directories by default:
/bin /sbin /usr/bin /usr/libexec /usr/local/bin /usr/local/sbin /usr/sbinAll files in these directories should be owned by the root user.
If any file FILE in these directories is found
to be owned by a user other than root, correct its ownership with the
following command:
$ sudo chown root FILE
| ||||||||||||||||||||||||||
| Rationale | System binaries are executed by privileged users as well as system services,
and restrictive permissions are necessary to ensure that their
execution of these programs cannot be co-opted. |
OVAL test results details
binary directories uid root oval:ssg-test_ownership_binary_directories:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_binary_directories:obj:1 of type file_object
| Path | Filename | Filter |
|---|---|---|
| ^\/(|s)bin|^\/usr\/(|local\/)(|s)bin|^\/usr\/libexec | oval:ssg-state_owner_binaries_not_root:ste:1 |
binary files uid root oval:ssg-test_ownership_binary_files:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_binary_files:obj:1 of type file_object
| Path | Filename | Filter |
|---|---|---|
| ^\/(|s)bin|^\/usr\/(|local\/)(|s)bin|^\/usr\/libexec | ^.*$ | oval:ssg-state_owner_binaries_not_root:ste:1 |
Verify that Shared Library Files Have Root Ownershipxccdf_org.ssgproject.content_rule_file_ownership_library_dirs mediumCCE-83907-6
Verify that Shared Library Files Have Root Ownership
| Rule ID | xccdf_org.ssgproject.content_rule_file_ownership_library_dirs | ||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-file_ownership_library_dirs:def:1 | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:08+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83907-6 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be
owned by the root user. If the directory, or any file in these
directories, is found to be owned by a user other than root correct its
ownership with the following command:
$ sudo chown root FILE
| ||||||||||||||||||||||||
| Rationale | Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership is necessary to protect the integrity of the system. |
OVAL test results details
Testing user ownership of /lib/ oval:ssg-test_file_ownership_library_dirs_0:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_library_dirs_0:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib | ^.*\.so.*$ | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /lib64/ oval:ssg-test_file_ownership_library_dirs_1:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_library_dirs_1:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /lib64 | ^.*\.so.*$ | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /usr/lib/ oval:ssg-test_file_ownership_library_dirs_2:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_library_dirs_2:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib | ^.*\.so.*$ | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownership_library_dirs_0_0:ste:1 |
Testing user ownership of /usr/lib64/ oval:ssg-test_file_ownership_library_dirs_3:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_file_ownership_library_dirs_3:obj:1 of type file_object
| Behaviors | Path | Filename | Filter | Filter |
|---|---|---|---|---|
| /usr/lib64 | ^.*\.so.*$ | oval:ssg-symlink_file_owner:ste:1 | oval:ssg-state_file_ownership_library_dirs_0_0:ste:1 |
Ensure rootfiles tmpfile.d is Configured Correctlyxccdf_org.ssgproject.content_rule_rootfiles_configured mediumCCE-86474-4
Ensure rootfiles tmpfile.d is Configured Correctly
| Rule ID | xccdf_org.ssgproject.content_rule_rootfiles_configured | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-rootfiles_configured:def:1 | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86474-4 | ||||||
| References: |
| ||||||
| Description | To set the mode of the root user initialization file /root/.bash_profile,
ensure the following lines are is included in a file ending in .conf under
/etc/tmpfiles.d/.
C /root/.bash_logout 600 root root - /usr/share/rootfiles/.bash_logout
C /root/.bash_profile 600 root root - /usr/share/rootfiles/.bash_profile
C /root/.bashrc 600 root root - /usr/share/rootfiles/.bashrc
C /root/.cshrc 600 root root - /usr/share/rootfiles/.cshrc
C /root/.tcshrc 600 root root - /usr/share/rootfiles/.tcshrc
| ||||||
| Rationale | Local initialization files are used to configure the user's shell environment
upon logon. Malicious modification of these files could compromise accounts upon
logon. |
OVAL test results details
Tests that .bash_logout is configured correctly. oval:ssg-test_rootfiles_configured_bash_logout:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/tmpfiles.d/rootfiles.conf | C /root/.bash_logout 600 root root - /usr/share/rootfiles/.bash_logout |
Tests that .bash_profile is configured correctly. oval:ssg-test_rootfiles_configured_bash_profile:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/tmpfiles.d/rootfiles.conf | C /root/.bash_profile 600 root root - /usr/share/rootfiles/.bash_profile |
Tests that .bashrc is configured correctly. oval:ssg-test_rootfiles_configured_bashrc:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/tmpfiles.d/rootfiles.conf | C /root/.bashrc 600 root root - /usr/share/rootfiles/.bashrc |
Tests that .cshrc is configured correctly. oval:ssg-test_rootfiles_configured_cshrc:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/tmpfiles.d/rootfiles.conf | C /root/.cshrc 600 root root - /usr/share/rootfiles/.cshrc |
Tests that .tcshrc is configured correctly. oval:ssg-test_rootfiles_configured_tcshrc:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Path | Content |
|---|---|---|
| true | /etc/tmpfiles.d/rootfiles.conf | C /root/.tcshrc 600 root root - /usr/share/rootfiles/.tcshrc |
Verify that All World-Writable Directories Have Sticky Bits Setxccdf_org.ssgproject.content_rule_dir_perms_world_writable_sticky_bits mediumCCE-83895-3
Verify that All World-Writable Directories Have Sticky Bits Set
| Rule ID | xccdf_org.ssgproject.content_rule_dir_perms_world_writable_sticky_bits | ||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-dir_perms_world_writable_sticky_bits:def:1 | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83895-3 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | When the so-called 'sticky bit' is set on a directory, only the owner of a given file may
remove that file from the directory. Without the sticky bit, any user with write access to a
directory may remove any file in the directory. Setting the sticky bit prevents users from
removing each other's files. In cases where there is no reason for a directory to be
world-writable, a better solution is to remove that permission rather than to set the sticky
bit. However, if a directory is used by a particular application, consult that application's
documentation instead of blindly changing modes.
To set the sticky bit on a world-writable directory DIR, run the following command: $ sudo chmod +t DIR
| ||||||||||||||||||||||||||||||
| Rationale | Failing to set the sticky bit on public directories allows unauthorized users to delete files
in the directory structure.
The only authorized public directories are those temporary directories supplied with the system, or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system, by users for temporary file storage (such as /tmp),
and for directories requiring global read/write access. | ||||||||||||||||||||||||||||||
| Warnings | warning
This rule can take a long time to perform the check and might consume a considerable
amount of resources depending on the number of directories present on the system. It is
not a problem in most cases, but especially systems with a large number of directories can
be affected. See https://access.redhat.com/articles/6999111.warning
Please note that there might be cases where the rule remediation cannot fix directory permissions.
This can happen for example when running on a system with some immutable parts.
These immutable parts cannot be remediated because they are read-only.
Example of such directories can be OStree deployments located at /sysroot/ostree/deploy.
In such case, it is needed to make modifications to the underlying ostree snapshot and this is out of scope of regular rule remediation. |
OVAL test results details
Check the existence of world-writable directories without sticky bits oval:ssg-test_dir_perms_world_writable_sticky_bits:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_dir_perms_world_writable_sticky_bits:obj:1 of type file_object
| Behaviors | Path | Filename | Filter |
|---|---|---|---|
| Referenced variable has no values (oval:ssg-var_dir_perms_world_writable_sticky_bits_local_mountpoi | oval:ssg-state_dir_perms_world_writable_sticky_bits:ste:1 |
Ensure All World-Writable Directories Are Owned by a System Accountxccdf_org.ssgproject.content_rule_dir_perms_world_writable_system_owned mediumCCE-86469-4
Ensure All World-Writable Directories Are Owned by a System Account
| Rule ID | xccdf_org.ssgproject.content_rule_dir_perms_world_writable_system_owned | ||||||||||||||||||||
| Result | pass | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| OVAL Definition ID | oval:ssg-dir_perms_world_writable_system_owned:def:1 | ||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-86469-4 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | All directories in local partitions which are world-writable should be owned by root or
another system account. If any world-writable directories are not owned by a system account,
this should be investigated. Following this, the files should be deleted or assigned to an
appropriate owner. | ||||||||||||||||||||
| Rationale | Allowing a user account to own a world-writable directory is undesirable because it allows the
owner of that directory to remove or replace any files that may be placed in the directory by
other users. | ||||||||||||||||||||
| Warnings | warning
This rule can take a long time to perform the check and might consume a considerable
amount of resources depending on the number of directories present on the system. It is
not a problem in most cases, but especially systems with a large number of directories can
be affected. See https://access.redhat.com/articles/6999111. |
OVAL test results details
Check the existence of world-writable directories not owned by system accounts. oval:ssg-test_dir_perms_world_writable_system_owned:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_dir_perms_world_writable_system_owned:obj:1 of type file_object
| Behaviors | Path | Filename | Filter |
|---|---|---|---|
| Referenced variable has no values (oval:ssg-var_dir_perms_world_writable_system_owned_local_mountpo | oval:ssg-state_dir_perms_world_writable_system_owned:ste:1 |
Ensure All Files Are Owned by a Userxccdf_org.ssgproject.content_rule_no_files_unowned_by_user mediumCCE-83896-1
Ensure All Files Are Owned by a User
| Rule ID | xccdf_org.ssgproject.content_rule_no_files_unowned_by_user | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83896-1 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | If any files are not owned by a user, then the cause of their lack of ownership should be
investigated. Following this, the files should be deleted or assigned to an appropriate user.
Locate the mount points related to local devices by the following command:
$ findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,)
For all mount points listed by the previous command, it is necessary to search for files which
do not belong to a valid user using the following command:
$ sudo find MOUNTPOINT -xdev -nouser 2>/dev/null | ||||||||||||||||||||||||||
| Rationale | Unowned files do not directly imply a security problem, but they are generally a sign that
something is amiss. They may be caused by an intruder, by incorrect software installation or
draft software removal, or by failure to remove all files belonging to a deleted account, or
other similar cases. The files should be repaired so they will not cause problems when
accounts are created in the future, and the cause should be discovered and addressed. | ||||||||||||||||||||||||||
| Warnings | warning
For this rule to evaluate centralized user accounts, getent must be working properly
so that running the command getent passwdreturns a list of all users in your organization. If using the System Security Services Daemon (SSSD), enumerate = truemust be configured in your organization's domain to return a complete list of users warning
This rule can take a long time to perform the check and might consume a considerable
amount of resources depending on the number of files present on the system. It is not a
problem in most cases, but especially systems with a large number of files can be affected.
See https://access.redhat.com/articles/6999111. |
Enable Kernel Parameter to Enforce DAC on Hardlinksxccdf_org.ssgproject.content_rule_sysctl_fs_protected_hardlinks mediumCCE-84110-6
Enable Kernel Parameter to Enforce DAC on Hardlinks
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_fs_protected_hardlinks | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-84110-6 | ||||||||||||
| References: |
| ||||||||||||
| Description | To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_hardlinks=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_hardlinks = 1 | ||||||||||||
| Rationale | By enabling this kernel parameter, users can no longer create soft or hard links to
files which they do not own. Disallowing such hardlinks mitigate vulnerabilities
based on insecure file system accessed by privileged programs, avoiding an
exploitation vector exploiting unsafe use of open() or creat(). |
Enable Kernel Parameter to Enforce DAC on Symlinksxccdf_org.ssgproject.content_rule_sysctl_fs_protected_symlinks mediumCCE-83900-1
Enable Kernel Parameter to Enforce DAC on Symlinks
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_fs_protected_symlinks | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:07+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83900-1 | ||||||||||||
| References: |
| ||||||||||||
| Description | To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: $ sudo sysctl -w fs.protected_symlinks=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: fs.protected_symlinks = 1 | ||||||||||||
| Rationale | By enabling this kernel parameter, symbolic links are permitted to be followed
only when outside a sticky world-writable directory, or when the UID of the
link and follower match, or when the directory owner matches the symlink's owner.
Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system
accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of
open() or creat(). |
Disable the Automounterxccdf_org.ssgproject.content_rule_service_autofs_disabled mediumCCE-83850-8
Disable the Automounter
| Rule ID | xccdf_org.ssgproject.content_rule_service_autofs_disabled | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83850-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The autofs daemon mounts and unmounts filesystems, such as user
home directories shared via NFS, on demand. In addition, autofs can be used to handle
removable media, and the default configuration provides the cdrom device as /misc/cd.
However, this method of providing access to removable media is not common, so autofs
can almost always be disabled if NFS is not in use. Even if NFS is required, it may be
possible to configure filesystem mounts statically by editing /etc/fstab
rather than relying on the automounter.
The autofs service can be disabled with the following command:
$ sudo systemctl mask --now autofs.service | ||||||||||||||||||||||||||||
| Rationale | Disabling the automounter permits the administrator to
statically control filesystem mounting through /etc/fstab.
Additionally, automatically mounting filesystems permits easy introduction of unknown devices, thereby facilitating malicious activity. |
Disable Mounting of cramfsxccdf_org.ssgproject.content_rule_kernel_module_cramfs_disabled lowCCE-83853-2
Disable Mounting of cramfs
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_cramfs_disabled | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||
| Identifiers: | CCE-83853-2 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description |
To configure the system to prevent the cramfs
kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
install cramfs /bin/falseThis entry will cause a non-zero return value during a cramfs module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install cramfs /bin/trueThis effectively prevents usage of this uncommon filesystem. The cramfs filesystem type is a compressed read-only
Linux filesystem embedded in small footprint systems. A
cramfs image can be used without having to first
decompress the image. | ||||||||||||||||||||||||
| Rationale | Removing support for unneeded filesystem types reduces the local attack surface
of the server. |
Disable Modprobe Loading of USB Storage Driverxccdf_org.ssgproject.content_rule_kernel_module_usb-storage_disabled mediumCCE-83851-6
Disable Modprobe Loading of USB Storage Driver
| Rule ID | xccdf_org.ssgproject.content_rule_kernel_module_usb-storage_disabled | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83851-6 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | To prevent USB storage devices from being used, configure the kernel module loading system
to prevent automatic loading of the USB storage driver.
To configure the system to prevent the usb-storage
kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
install usb-storage /bin/falseThis entry will cause a non-zero return value during a usb-storage module installation
and additionally convey the meaning of the entry to the user in form of an error message.
If you would like to omit a non-zero return value and an error message, you may want to add a different line instead
(both /bin/true and /bin/false are allowed by OVAL and will be accepted by the scan):
install usb-storage /bin/trueThis will prevent the modprobe program from loading the usb-storage
module, but will not prevent an administrator (or another program) from using the
insmod program to load the module manually. | ||||||||||||||||||||||||||||||||||
| Rationale | USB storage devices such as thumb drives can be used to introduce
malicious software. |
Add nosuid Option to /boot/efixccdf_org.ssgproject.content_rule_mount_option_boot_efi_nosuid mediumCCE-86040-3
Add nosuid Option to /boot/efi
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_boot_efi_nosuid | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86040-3 | ||||||||||
| References: |
| ||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /boot/efi. The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot/efi. | ||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from boot partitions. |
Add nodev Option to /bootxccdf_org.ssgproject.content_rule_mount_option_boot_nodev mediumCCE-83884-7
Add nodev Option to /boot
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_boot_nodev | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83884-7 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /boot.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot. | ||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add nosuid Option to /bootxccdf_org.ssgproject.content_rule_mount_option_boot_nosuid mediumCCE-83877-1
Add nosuid Option to /boot
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_boot_nosuid | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83877-1 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /boot. The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot. | ||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from boot partitions. |
Add nodev Option to /dev/shmxccdf_org.ssgproject.content_rule_mount_option_dev_shm_nodev mediumCCE-83881-3
Add nodev Option to /dev/shm
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_dev_shm_nodev | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83881-3 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The nodev mount option can be used to prevent creation of device
files in /dev/shm. Legitimate character and block devices should
not exist within temporary directories like /dev/shm.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm. | ||||||||||||||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /dev/shmxccdf_org.ssgproject.content_rule_mount_option_dev_shm_noexec mediumCCE-83857-3
Add noexec Option to /dev/shm
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_dev_shm_noexec | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83857-3 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The noexec mount option can be used to prevent binaries
from being executed out of /dev/shm.
It can be dangerous to allow the execution of binaries
from world-writable temporary storage directories such as /dev/shm.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm. | ||||||||||||||||||||||||||
| Rationale | Allowing users to execute binaries from world-writable directories
such as /dev/shm can expose the system to potential compromise. |
Add nosuid Option to /dev/shmxccdf_org.ssgproject.content_rule_mount_option_dev_shm_nosuid mediumCCE-83891-2
Add nosuid Option to /dev/shm
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_dev_shm_nosuid | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83891-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The nosuid mount option can be used to prevent execution
of setuid programs in /dev/shm. The SUID and SGID permissions should not
be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm. | ||||||||||||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions. |
Add nodev Option to /homexccdf_org.ssgproject.content_rule_mount_option_home_nodev unknownCCE-83871-4
Add nodev Option to /home
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_home_nodev | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | unknown | ||||||||
| Identifiers: | CCE-83871-4 | ||||||||
| References: |
| ||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /home.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/home. | ||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /homexccdf_org.ssgproject.content_rule_mount_option_home_noexec mediumCCE-83875-5
Add noexec Option to /home
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_home_noexec | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83875-5 | ||||||||||
| References: |
| ||||||||||
| Description | The noexec mount option can be used to prevent binaries from being
executed out of /home.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/home. | ||||||||||
| Rationale | The /home directory contains data of individual users. Binaries in
this directory should not be considered as trusted and users should not be
able to execute them. |
Add nosuid Option to /homexccdf_org.ssgproject.content_rule_mount_option_home_nosuid mediumCCE-83894-6
Add nosuid Option to /home
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_home_nosuid | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83894-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /home. The SUID and SGID permissions
should not be required in these user data directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/home. | ||||||||||||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from user home directory partitions. |
Add nodev Option to Non-Root Local Partitionsxccdf_org.ssgproject.content_rule_mount_option_nodev_nonroot_local_partitions mediumCCE-83873-0
Add nodev Option to Non-Root Local Partitions
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_nodev_nonroot_local_partitions | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83873-0 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The nodev mount option prevents files from being interpreted as
character or block devices. Legitimate character and block devices should
exist only in the /dev directory on the root partition or within
chroot jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
any non-root local partitions. | ||||||||||||||||||||||||
| Rationale | The nodev mount option prevents files from being
interpreted as character or block devices. The only legitimate location
for device files is the /dev directory located on the root partition.
The only exception to this is chroot jails, for which it is not advised
to set nodev on these filesystems. | ||||||||||||||||||||||||
| Warnings | warning
This rule checks only local partitions, identified as those backed by
a device node in /dev. Network file systems such as NFS, CIFS,
GlusterFS and others are excluded because they do not expose local
device nodes. The /boot and /efi partitions are
excluded because they are special partitions usually handled by a
systemd mount unit, and enforcing nodev on them during
operating system installation causes issues. Partitions with the
vfat file system type are excluded because vfat does not
support Unix device special files, so nodev enforcement on
them is not meaningful. |
Add nodev Option to Removable Media Partitionsxccdf_org.ssgproject.content_rule_mount_option_nodev_removable_partitions mediumCCE-83856-5
Add nodev Option to Removable Media Partitions
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_nodev_removable_partitions | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83856-5 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The nodev mount option prevents files from being
interpreted as character or block devices.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. | ||||||||||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. An exception to this is chroot jails, and it is
not advised to set nodev on partitions which contain their root
filesystems. |
Add noexec Option to Removable Media Partitionsxccdf_org.ssgproject.content_rule_mount_option_noexec_removable_partitions mediumCCE-83883-9
Add noexec Option to Removable Media Partitions
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_noexec_removable_partitions | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83883-9 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The noexec mount option prevents the direct execution of binaries
on the mounted filesystem. Preventing the direct execution of binaries from
removable media (such as a USB key) provides a defense against malicious
software that may be present on such untrusted media.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. | ||||||||||||||||||||||
| Rationale | Allowing users to execute binaries from removable media such as USB keys exposes
the system to potential compromise. |
Add nosuid Option to Removable Media Partitionsxccdf_org.ssgproject.content_rule_mount_option_nosuid_removable_partitions mediumCCE-83874-8
Add nosuid Option to Removable Media Partitions
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_nosuid_removable_partitions | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-83874-8 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The nosuid mount option prevents set-user-identifier (SUID)
and set-group-identifier (SGID) permissions from taking effect. These permissions
allow users to execute binaries with the same permissions as the owner and group
of the file respectively. Users should not be allowed to introduce SUID and SGID
files into the system via partitions mounted from removable media.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
any removable media partitions. | ||||||||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Allowing
users to introduce SUID or SGID binaries from partitions mounted off of
removable media would allow them to introduce their own highly-privileged programs. |
Add nodev Option to /tmpxccdf_org.ssgproject.content_rule_mount_option_tmp_nodev mediumCCE-83869-8
Add nodev Option to /tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_tmp_nodev | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83869-8 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /tmp. Legitimate character and block devices
should not exist within temporary directories like /tmp.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp. | ||||||||||||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /tmpxccdf_org.ssgproject.content_rule_mount_option_tmp_noexec mediumCCE-83885-4
Add noexec Option to /tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_tmp_noexec | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83885-4 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The noexec mount option can be used to prevent binaries
from being executed out of /tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp. | ||||||||||||||||||||||||||
| Rationale | Allowing users to execute binaries from world-writable directories
such as /tmp should never be necessary in normal operation and
can expose the system to potential compromise. |
Add nosuid Option to /tmpxccdf_org.ssgproject.content_rule_mount_option_tmp_nosuid mediumCCE-83872-2
Add nosuid Option to /tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_tmp_nosuid | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83872-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp. | ||||||||||||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions. |
Add nodev Option to /var/log/auditxccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nodev mediumCCE-83882-1
Add nodev Option to /var/log/audit
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nodev | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83882-1 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /var/log/audit.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit. | ||||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /var/log/auditxccdf_org.ssgproject.content_rule_mount_option_var_log_audit_noexec mediumCCE-83878-9
Add noexec Option to /var/log/audit
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_noexec | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83878-9 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The noexec mount option can be used to prevent binaries
from being executed out of /var/log/audit.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit. | ||||||||||||||||
| Rationale | Allowing users to execute binaries from directories containing audit log files
such as /var/log/audit should never be necessary in normal operation and
can expose the system to potential compromise. |
Add nosuid Option to /var/log/auditxccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nosuid mediumCCE-83893-8
Add nosuid Option to /var/log/audit
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_audit_nosuid | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83893-8 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /var/log/audit. The SUID and SGID permissions
should not be required in directories containing audit log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit. | ||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from partitions
designated for audit log files. |
Add nodev Option to /var/logxccdf_org.ssgproject.content_rule_mount_option_var_log_nodev mediumCCE-83886-2
Add nodev Option to /var/log
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_nodev | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83886-2 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /var/log.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log. | ||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /var/logxccdf_org.ssgproject.content_rule_mount_option_var_log_noexec mediumCCE-83887-0
Add noexec Option to /var/log
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_noexec | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83887-0 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The noexec mount option can be used to prevent binaries
from being executed out of /var/log.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log. | ||||||||||||||||
| Rationale | Allowing users to execute binaries from directories containing log files
such as /var/log should never be necessary in normal operation and
can expose the system to potential compromise. |
Add nosuid Option to /var/logxccdf_org.ssgproject.content_rule_mount_option_var_log_nosuid mediumCCE-83870-6
Add nosuid Option to /var/log
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_log_nosuid | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83870-6 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /var/log. The SUID and SGID permissions
should not be required in directories containing log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log. | ||||||||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from partitions
designated for log files. |
Add nodev Option to /varxccdf_org.ssgproject.content_rule_mount_option_var_nodev mediumCCE-83868-0
Add nodev Option to /var
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_nodev | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83868-0 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /var.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var. | ||||||||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add nodev Option to /var/tmpxccdf_org.ssgproject.content_rule_mount_option_var_tmp_nodev mediumCCE-83864-9
Add nodev Option to /var/tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_tmp_nodev | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83864-9 | ||||||||
| References: |
| ||||||||
| Description | The nodev mount option can be used to prevent device files from
being created in /var/tmp. Legitimate character and block devices
should not exist within temporary directories like /var/tmp.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp. | ||||||||
| Rationale | The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails. |
Add noexec Option to /var/tmpxccdf_org.ssgproject.content_rule_mount_option_var_tmp_noexec mediumCCE-83866-4
Add noexec Option to /var/tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_tmp_noexec | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83866-4 | ||||||||||
| References: |
| ||||||||||
| Description | The noexec mount option can be used to prevent binaries
from being executed out of /var/tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp. | ||||||||||
| Rationale | Allowing users to execute binaries from world-writable directories
such as /var/tmp should never be necessary in normal operation and
can expose the system to potential compromise. |
Add nosuid Option to /var/tmpxccdf_org.ssgproject.content_rule_mount_option_var_tmp_nosuid mediumCCE-83863-1
Add nosuid Option to /var/tmp
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_var_tmp_nosuid | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83863-1 | ||||||||||
| References: |
| ||||||||||
| Description | The nosuid mount option can be used to prevent
execution of setuid programs in /var/tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp. | ||||||||||
| Rationale | The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions. |
Enable ExecShield via sysctlxccdf_org.ssgproject.content_rule_sysctl_kernel_exec_shield mediumCCE-83970-4
Enable ExecShield via sysctl
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_exec_shield | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83970-4 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | By default on Red Hat Enterprise Linux 9 64-bit systems, ExecShield is
enabled and can only be disabled if the hardware does not support
ExecShield or is disabled in /etc/default/grub. | ||||||||||||||||||||||||
| Rationale | ExecShield uses the segmentation feature on all x86 systems to prevent
execution in memory higher than a certain address. It writes an address as
a limit in the code segment descriptor, to control where code can be
executed, on a per-process basis. When the kernel places a process's memory
regions such as the stack and heap higher than this address, the hardware
prevents execution in that address range. This is enabled by default on the
latest Red Hat and Fedora systems if supported by the hardware. |
Restrict Exposed Kernel Pointer Addresses Accessxccdf_org.ssgproject.content_rule_sysctl_kernel_kptr_restrict mediumCCE-83972-0
Restrict Exposed Kernel Pointer Addresses Access
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_kptr_restrict | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83972-0 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.kptr_restrict=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kptr_restrict = 1
| ||||||||||||||||
| Rationale | Exposing kernel pointers (through procfs or seq_printf()) exposes kernel
writeable structures which may contain functions pointers. If a write vulnerability
occurs in the kernel, allowing write access to any of this structure, the kernel can
be compromised. This option disallow any program without the CAP_SYSLOG capability
to get the addresses of kernel pointers by replacing them with 0. |
Enable Randomized Layout of Virtual Address Spacexccdf_org.ssgproject.content_rule_sysctl_kernel_randomize_va_space mediumCCE-83971-2
Enable Randomized Layout of Virtual Address Space
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_randomize_va_space | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83971-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | To set the runtime status of the kernel.randomize_va_space kernel parameter, run the following command: $ sudo sysctl -w kernel.randomize_va_space=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.randomize_va_space = 2 | ||||||||||||||||||||||||||
| Rationale | Address space layout randomization (ASLR) makes it more difficult for an
attacker to predict the location of attack code they have introduced into a
process's address space during an attempt at exploitation. Additionally,
ASLR makes it more difficult for an attacker to know the location of
existing code in order to re-purpose it using return oriented programming
(ROP) techniques. |
Enable page allocator poisoningxccdf_org.ssgproject.content_rule_grub2_page_poison_argument mediumCCE-83985-2
Enable page allocator poisoning
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_page_poison_argument | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83985-2 | ||||||||||
| References: |
| ||||||||||
| Description | To enable poisoning of free pages,
add the argument page_poison=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that page_poison=1 is added as a kernel command line
argument to newly installed kernels, add page_poison=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... page_poison=1 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="page_poison=1"If the system is distributed as a bootable container image, GRUB2 can't be configured using the method described above, but the following method needs to be used instead. The kernel arguments should be set in /usr/lib/bootc/kargs.d in a TOML file that has the following form:
# /usr/lib/bootc/kargs.d/10-example.toml kargs = ["page_poison=1"]For more details on configuring kernel arguments in bootable container images, please refer to Bootc documentation. | ||||||||||
| Rationale | Poisoning writes an arbitrary value to freed pages, so any modification or
reference to that page after being freed or before being initialized will be
detected and prevented.
This prevents many types of use-after-free vulnerabilities at little performance cost.
Also prevents leak of data and detection of corrupted memory. |
Disable storing core dumpsxccdf_org.ssgproject.content_rule_sysctl_kernel_core_pattern mediumCCE-83961-3
Disable storing core dumps
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_core_pattern | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83961-3 | ||||||||||
| References: |
| ||||||||||
| Description | To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: $ sudo sysctl -w kernel.core_pattern=|/bin/falseTo make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.core_pattern = |/bin/false | ||||||||||
| Rationale | A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data and is generally useful
only for developers trying to debug problems. |
Restrict Access to Kernel Message Bufferxccdf_org.ssgproject.content_rule_sysctl_kernel_dmesg_restrict lowCCE-83952-2
Restrict Access to Kernel Message Buffer
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_dmesg_restrict | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | low | ||||||||||||||||||||
| Identifiers: | CCE-83952-2 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: $ sudo sysctl -w kernel.dmesg_restrict=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.dmesg_restrict = 1 | ||||||||||||||||||||
| Rationale | Unprivileged access to the kernel syslog can expose sensitive kernel
address information. |
Disable Kernel Image Loadingxccdf_org.ssgproject.content_rule_sysctl_kernel_kexec_load_disabled mediumCCE-83954-8
Disable Kernel Image Loading
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_kexec_load_disabled | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83954-8 | ||||||||||||
| References: |
| ||||||||||||
| Description | To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.kexec_load_disabled=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.kexec_load_disabled = 1 | ||||||||||||
| Rationale | Disabling kexec_load allows greater control of the kernel memory.
It makes it impossible to load another kernel image after it has been disabled.
|
Disallow kernel profiling by unprivileged usersxccdf_org.ssgproject.content_rule_sysctl_kernel_perf_event_paranoid lowCCE-83959-7
Disallow kernel profiling by unprivileged users
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_perf_event_paranoid | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | low | ||||||||||||||
| Identifiers: | CCE-83959-7 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: $ sudo sysctl -w kernel.perf_event_paranoid=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.perf_event_paranoid = 2 | ||||||||||||||
| Rationale | Kernel profiling can reveal sensitive information about kernel behaviour. |
Disable Access to Network bpf() Syscall From Unprivileged Processesxccdf_org.ssgproject.content_rule_sysctl_kernel_unprivileged_bpf_disabled mediumCCE-83957-1
Disable Access to Network bpf() Syscall From Unprivileged Processes
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_unprivileged_bpf_disabled | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83957-1 | ||||||||||||
| References: |
| ||||||||||||
| Description | To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: $ sudo sysctl -w kernel.unprivileged_bpf_disabled=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.unprivileged_bpf_disabled = 1 | ||||||||||||
| Rationale | Loading and accessing the packet filters programs and maps using the bpf()
syscall has the potential of revealing sensitive information about the kernel state. |
Restrict usage of ptrace to descendant processesxccdf_org.ssgproject.content_rule_sysctl_kernel_yama_ptrace_scope mediumCCE-83965-4
Restrict usage of ptrace to descendant processes
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_kernel_yama_ptrace_scope | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-83965-4 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: $ sudo sysctl -w kernel.yama.ptrace_scope=1To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: kernel.yama.ptrace_scope = 1 | ||||||||||||||||
| Rationale | Unrestricted usage of ptrace allows compromised binaries to run ptrace
on another processes of the user. Like this, the attacker can steal
sensitive information from the target processes (e.g. SSH sessions, web browser, ...)
without any additional assistance from the user (i.e. without resorting to phishing).
|
Harden the operation of the BPF just-in-time compilerxccdf_org.ssgproject.content_rule_sysctl_net_core_bpf_jit_harden mediumCCE-83966-2
Harden the operation of the BPF just-in-time compiler
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_net_core_bpf_jit_harden | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83966-2 | ||||||||||||
| References: |
| ||||||||||||
| Description | To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: $ sudo sysctl -w net.core.bpf_jit_harden=2To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d: net.core.bpf_jit_harden = 2 | ||||||||||||
| Rationale | When hardened, the extended Berkeley Packet Filter just-in-time compiler
will randomize any kernel addresses in the BPF programs and maps,
and will not expose the JIT addresses in /proc/kallsyms. |
Disable the use of user namespacesxccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces_no_remediation mediumCCE-86209-4
Disable the use of user namespaces
| Rule ID | xccdf_org.ssgproject.content_rule_sysctl_user_max_user_namespaces_no_remediation | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86209-4 | ||||||
| References: |
| ||||||
| Description | To set the runtime status of the user.max_user_namespaces kernel parameter,
run the following command:
$ sudo sysctl -w user.max_user_namespaces=0To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
user.max_user_namespaces = 0When containers are deployed on the machine, the value should be set to large non-zero value. | ||||||
| Rationale | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or system objectives.
These unnecessary capabilities or services are often overlooked and therefore may remain unsecured.
They increase the risk to the platform by providing additional attack vectors.
User namespaces are used primarily for Linux containers. The value 0
disallows the use of user namespaces. | ||||||
| Warnings | warning
This configuration baseline was created to deploy the base operating system for general purpose
workloads. When the operating system is configured for certain purposes, such as to host Linux Containers,
it is expected that user.max_user_namespaces will be enabled.
Note that this rule deliberately does not have remediations attached.
Use the sysctl_user_max_user_namespaces if you want to utilize remediation for this rule. |
Install policycoreutils-python-utils packagexccdf_org.ssgproject.content_rule_package_policycoreutils-python-utils_installed mediumCCE-84070-2
Install policycoreutils-python-utils package
| Rule ID | xccdf_org.ssgproject.content_rule_package_policycoreutils-python-utils_installed | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-84070-2 | ||||||
| References: |
| ||||||
| Description | The policycoreutils-python-utils package can be installed with the following command:
$ sudo dnf install policycoreutils-python-utils | ||||||
| Rationale | This package is required to operate and manage an SELinux environment and its policies.
It provides utilities such as semanage, audit2allow, audit2why, chcat and sandbox. |
Install policycoreutils Packagexccdf_org.ssgproject.content_rule_package_policycoreutils_installed lowCCE-84071-0
Install policycoreutils Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_policycoreutils_installed | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | low | ||||||
| Identifiers: | CCE-84071-0 | ||||||
| References: |
| ||||||
| Description | The policycoreutils package can be installed with the following command:
$ sudo dnf install policycoreutils | ||||||
| Rationale | Security-enhanced Linux is a feature of the Linux kernel and a number of utilities
with enhanced security functionality designed to add mandatory access controls to Linux.
The Security-enhanced Linux kernel contains new architectural components originally
developed to improve security of the Flask operating system. These architectural components
provide general support for the enforcement of many kinds of mandatory access control
policies, including those based on the concepts of Type Enforcement, Role-based Access
Control, and Multi-level Security.
policycoreutils contains the policy core utilities that are required for
basic operation of an SELinux-enabled system. These utilities include load_policy
to load SELinux policies, setfiles to label filesystems, newrole to
switch roles, and so on. |
Ensure No Device Files are Unlabeled by SELinuxxccdf_org.ssgproject.content_rule_selinux_all_devicefiles_labeled mediumCCE-85920-7
Ensure No Device Files are Unlabeled by SELinux
| Rule ID | xccdf_org.ssgproject.content_rule_selinux_all_devicefiles_labeled | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-85920-7 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Device files, which are used for communication with important system
resources, should be labeled with proper SELinux types. If any device files
carry the SELinux type device_t or unlabeled_t, report the
bug so that policy can be corrected. Supply information about what the
device is and what programs use it.
To check for incorrectly labeled device files, run following commands: $ sudo find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n" $ sudo find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"It should produce no output in a well-configured system. | ||||||||||||||||||||||
| Rationale | If a device file carries the SELinux type device_t or
unlabeled_t, then SELinux cannot properly restrict access to the
device file. | ||||||||||||||||||||||
| Warnings | warning
Automatic remediation of this control is not available. The remediation
can be achieved by amending SELinux policy. |
Elevate The SELinux Context When An Administrator Calls The Sudo Commandxccdf_org.ssgproject.content_rule_selinux_context_elevation_for_sudo mediumCCE-86576-6
Elevate The SELinux Context When An Administrator Calls The Sudo Command
| Rule ID | xccdf_org.ssgproject.content_rule_selinux_context_elevation_for_sudo | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86576-6 | ||||||||
| References: |
| ||||||||
| Description | Configure the operating system to elevate the SELinux context when an administrator calls
the sudo command.
Edit a file in the /etc/sudoers.d directory with the following command:
sudo visudo -f /etc/sudoers.d/CUSTOM_FILE
Use the following example to build the CUSTOM_FILE in the /etc/sudoers.d directory
to allow any administrator belonging to a designated sudoers admin group to elevate their
SELinux context with the use of the sudo command:
%wheel ALL=(ALL) TYPE=sysadm_t ROLE=sysadm_r ALL | ||||||||
| Rationale | Preventing non-privileged users from executing privileged functions mitigates
the risk that unauthorized individuals or processes may gain unnecessary access
to information or privileges.
Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. |
Configure SELinux Policyxccdf_org.ssgproject.content_rule_selinux_policytype mediumCCE-84074-4
Configure SELinux Policy
| Rule ID | xccdf_org.ssgproject.content_rule_selinux_policytype | ||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84074-4 | ||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||
| Description | The SELinux targeted policy is appropriate for
general-purpose desktops and servers, as well as systems in many other roles.
To configure the system to use this policy, add or correct the following line
in /etc/selinux/config:
SELINUXTYPE=targeted
Other policies, such as mls, provide additional security labeling
and greater confinement but are not compatible with many general-purpose
use cases. | ||||||||||||||||||||||||||||||||||||||||||
| Rationale | Setting the SELinux policy to targeted or a more specialized policy
ensures the system will confine processes that are likely to be
targeted for exploitation, such as network or system services.
Note: During the development or debugging of SELinux modules, it is common to temporarily place non-production systems in permissive mode. In such
temporary cases, SELinux policies should be developed, and once work
is completed, the system should be reconfigured to
targeted. |
Ensure SELinux State is Enforcingxccdf_org.ssgproject.content_rule_selinux_state highCCE-84079-3
Ensure SELinux State is Enforcing
| Rule ID | xccdf_org.ssgproject.content_rule_selinux_state | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84079-3 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | The SELinux state should be set to enforcing at
system boot time. In the file /etc/selinux/config, add or correct the
following line to configure the system to boot into enforcing mode:
SELINUX=enforcing
Ensure that all files have correct SELinux labels by running:
fixfiles onbootThen reboot the system. | ||||||||||||||||||||||||||||||||||||||||
| Rationale | Setting the SELinux state to enforcing ensures SELinux is able to confine
potentially compromised processes to the security policy, which is designed to
prevent them from causing damage to the system or further elevating their
privileges. |
Disable KDump Kernel Crash Analyzer (kdump)xccdf_org.ssgproject.content_rule_service_kdump_disabled mediumCCE-84232-8
Disable KDump Kernel Crash Analyzer (kdump)
| Rule ID | xccdf_org.ssgproject.content_rule_service_kdump_disabled | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-84232-8 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The kdump service provides a kernel crash dump analyzer. It uses the kexec
system call to boot a secondary kernel ("capture" kernel) following a system
crash, which can load information from the crashed kernel for analysis.
The kdump service can be disabled with the following command:
$ sudo systemctl mask --now kdump.service | ||||||||||||||||||||||||
| Rationale | Kernel core dumps may contain the full contents of system memory at the
time of the crash. Kernel core dumps consume a considerable amount of disk
space and may result in denial of service by exhausting the available space
on the target file system partition. Unless the system is used for kernel
development or testing, there is little need to run the kdump service. |
Install the cron servicexccdf_org.ssgproject.content_rule_package_cron_installed mediumCCE-86170-8
Install the cron service
| Rule ID | xccdf_org.ssgproject.content_rule_package_cron_installed | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-86170-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The Cron service should be installed. | ||||||||||||||||||||||||||||
| Rationale | The cron service allow periodic job execution, needed for almost all administrative tasks and services (software update, log rotating, etc.). Access to cron service should be restricted to administrative accounts only. |
Verify Group Who Owns cron.dxccdf_org.ssgproject.content_rule_file_groupowner_cron_d mediumCCE-84177-5
Verify Group Who Owns cron.d
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_d | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84177-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/cron.d, run the command:
$ sudo chgrp root /etc/cron.d | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns cron.dailyxccdf_org.ssgproject.content_rule_file_groupowner_cron_daily mediumCCE-84170-0
Verify Group Who Owns cron.daily
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_daily | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84170-0 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/cron.daily, run the command:
$ sudo chgrp root /etc/cron.daily | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns cron.denyxccdf_org.ssgproject.content_rule_file_groupowner_cron_deny mediumCCE-86537-8
Verify Group Who Owns cron.deny
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_deny | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86537-8 | ||||||||
| References: |
| ||||||||
| Description |
To properly set the group owner of /etc/cron.deny, run the command:
$ sudo chgrp root /etc/cron.deny | ||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns cron.hourlyxccdf_org.ssgproject.content_rule_file_groupowner_cron_hourly mediumCCE-84186-6
Verify Group Who Owns cron.hourly
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_hourly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84186-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/cron.hourly, run the command:
$ sudo chgrp root /etc/cron.hourly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns cron.monthlyxccdf_org.ssgproject.content_rule_file_groupowner_cron_monthly mediumCCE-84189-0
Verify Group Who Owns cron.monthly
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_monthly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84189-0 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/cron.monthly, run the command:
$ sudo chgrp root /etc/cron.monthly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns cron.weeklyxccdf_org.ssgproject.content_rule_file_groupowner_cron_weekly mediumCCE-84174-2
Verify Group Who Owns cron.weekly
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_cron_weekly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84174-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/cron.weekly, run the command:
$ sudo chgrp root /etc/cron.weekly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns Crontabxccdf_org.ssgproject.content_rule_file_groupowner_crontab mediumCCE-84171-8
Verify Group Who Owns Crontab
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_crontab | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84171-8 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/crontab, run the command:
$ sudo chgrp root /etc/crontab | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Owner on cron.dxccdf_org.ssgproject.content_rule_file_owner_cron_d mediumCCE-84169-2
Verify Owner on cron.d
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_d | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84169-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/cron.d, run the command:
$ sudo chown root /etc/cron.d | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on cron.dailyxccdf_org.ssgproject.content_rule_file_owner_cron_daily mediumCCE-84188-2
Verify Owner on cron.daily
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_daily | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84188-2 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/cron.daily, run the command:
$ sudo chown root /etc/cron.daily | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on cron.denyxccdf_org.ssgproject.content_rule_file_owner_cron_deny mediumCCE-86887-7
Verify Owner on cron.deny
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_deny | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86887-7 | ||||||||
| References: |
| ||||||||
| Description |
To properly set the owner of /etc/cron.deny, run the command:
$ sudo chown root /etc/cron.deny | ||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on cron.hourlyxccdf_org.ssgproject.content_rule_file_owner_cron_hourly mediumCCE-84168-4
Verify Owner on cron.hourly
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_hourly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84168-4 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/cron.hourly, run the command:
$ sudo chown root /etc/cron.hourly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on cron.monthlyxccdf_org.ssgproject.content_rule_file_owner_cron_monthly mediumCCE-84179-1
Verify Owner on cron.monthly
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_monthly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84179-1 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/cron.monthly, run the command:
$ sudo chown root /etc/cron.monthly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on cron.weeklyxccdf_org.ssgproject.content_rule_file_owner_cron_weekly mediumCCE-84190-8
Verify Owner on cron.weekly
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_cron_weekly | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84190-8 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/cron.weekly, run the command:
$ sudo chown root /etc/cron.weekly | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Verify Owner on crontabxccdf_org.ssgproject.content_rule_file_owner_crontab mediumCCE-84167-6
Verify Owner on crontab
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_crontab | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-84167-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/crontab, run the command:
$ sudo chown root /etc/crontab | ||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective services that if configured incorrectly
can lead to insecure and vulnerable configurations. Therefore, service configuration files should be owned by the
correct user to prevent unauthorized changes. |
Install fapolicyd Packagexccdf_org.ssgproject.content_rule_package_fapolicyd_installed mediumCCE-84224-5
Install fapolicyd Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_fapolicyd_installed | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-84224-5 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The fapolicyd package can be installed with the following command:
$ sudo dnf install fapolicyd | ||||||||||||||
| Rationale | fapolicyd (File Access Policy Daemon)
implements application whitelisting to decide file access rights. |
Enable the File Access Policy Servicexccdf_org.ssgproject.content_rule_service_fapolicyd_enabled mediumCCE-84227-8
Enable the File Access Policy Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_fapolicyd_enabled | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-84227-8 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | The File Access Policy service should be enabled.
The fapolicyd service can be enabled with the following command:
$ sudo systemctl enable fapolicyd.service | ||||||||||||||
| Rationale | The fapolicyd service (File Access Policy Daemon)
implements application whitelisting to decide file access rights. |
Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs.xccdf_org.ssgproject.content_rule_fapolicy_default_deny mediumCCE-86479-3
Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs.
| Rule ID | xccdf_org.ssgproject.content_rule_fapolicy_default_deny | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86479-3 | ||||||||||
| References: |
| ||||||||||
| Description | The Fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and to prevent unauthorized software from running. | ||||||||||
| Rationale | Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software.
Using only authorized software decreases risk by limiting the number of potential vulnerabilities. Verification of whitelisted software occurs prior to execution or at system startup.
Proceed with caution with enforcing the use of this daemon.
Improper configuration may render the system non-functional.
The "fapolicyd" API is not namespace aware and can cause issues when launching or running containers. |
Uninstall vsftpd Packagexccdf_org.ssgproject.content_rule_package_vsftpd_removed highCCE-84159-3
Uninstall vsftpd Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_vsftpd_removed | ||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-package_vsftpd_removed:def:1 | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||
| Identifiers: | CCE-84159-3 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | The vsftpd package can be removed with the following command: $ sudo dnf remove vsftpd | ||||||||||||||||||||||||
| Rationale | Removing the vsftpd package decreases the risk of its
accidental activation. |
OVAL test results details
package vsftpd is removed oval:ssg-test_package_vsftpd_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_vsftpd_removed:obj:1 of type rpminfo_object
| Name |
|---|
| vsftpd |
Configure System to Forward All Mail For The Root Accountxccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias mediumCCE-90826-9
Configure System to Forward All Mail For The Root Account
| Rule ID | xccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-90826-9 | ||||||||||
| References: |
| ||||||||||
| Description | Make sure that mails delivered to root user are forwarded to a monitored
email address. Make sure that the address
change_me@localhost is a valid email address
reachable from the system in question. Use the following command to
configure the alias:
$ sudo echo "root: change_me@localhost" >> /etc/aliases $ sudo newaliases | ||||||||||
| Rationale | A number of system services utilize email messages sent to the root user to
notify system administrators of active or impending issues. These messages must
be forwarded to at least one monitored email address. |
Configure System to Forward All Mail From Postmaster to The Root Accountxccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias_postmaster mediumCCE-89064-0
Configure System to Forward All Mail From Postmaster to The Root Account
| Rule ID | xccdf_org.ssgproject.content_rule_postfix_client_configure_mail_alias_postmaster | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89064-0 | ||||||||
| References: |
| ||||||||
| Description | Verify the administrators are notified in the event of an audit processing failure.
Check that the "/etc/aliases" file has a defined value for "root".
$ sudo grep "postmaster:\s*root$" /etc/aliases postmaster: root | ||||||||
| Rationale | It is critical for the appropriate personnel to be aware if a system is at risk of failing to
process audit logs as required. Without this notification, the security personnel may be
unaware of an impending failure of the audit capability, and system operation may be adversely
affected.
Audit processing failures include software/hardware errors, failures in the audit capturing
mechanisms, and audit storage capacity being reached or exceeded. |
Prevent Unrestricted Mail Relayingxccdf_org.ssgproject.content_rule_postfix_prevent_unrestricted_relay mediumCCE-87232-5
Prevent Unrestricted Mail Relaying
| Rule ID | xccdf_org.ssgproject.content_rule_postfix_prevent_unrestricted_relay | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-87232-5 | ||||||
| References: |
| ||||||
| Description | Modify the /etc/postfix/main.cffile to restrict client connections to the local network with the following command: $ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject' | ||||||
| Rationale | If unrestricted mail relaying is permitted, unauthorized senders could use this
host as a mail relay for the purpose of sending spam or other unauthorized
activity. |
The Postfix package is installedxccdf_org.ssgproject.content_rule_package_postfix_installed mediumCCE-85984-3
The Postfix package is installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_postfix_installed | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-85984-3 | ||||||
| References: |
| ||||||
| Description | A mail server is required for sending emails.
The postfix package can be installed with the following command:
$ sudo dnf install postfix | ||||||
| Rationale | Emails can be used to notify designated personnel about important
system events such as failures or warnings. |
The s-nail Package Is Installedxccdf_org.ssgproject.content_rule_package_s-nail_installed mediumCCE-86608-7
The s-nail Package Is Installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_s-nail_installed | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86608-7 | ||||||||
| References: |
| ||||||||
| Description | A mail server is required for sending emails.
The s-nail package can be installed with the following command:
$ sudo dnf install s-nail | ||||||||
| Rationale | Emails can be used to notify designated personnel about important
system events such as failures or warnings. |
Uninstall Sendmail Packagexccdf_org.ssgproject.content_rule_package_sendmail_removed mediumCCE-90830-1
Uninstall Sendmail Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_sendmail_removed | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-90830-1 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Sendmail is not the default mail transfer agent and is
not installed by default.
The sendmail package can be removed with the following command:
$ sudo dnf remove sendmail | ||||||||||||||||||||||
| Rationale | The sendmail software was not developed with security in mind and
its design prevents it from being effectively contained by SELinux. Postfix
should be used instead. |
Mount Remote Filesystems with nodevxccdf_org.ssgproject.content_rule_mount_option_nodev_remote_filesystems mediumCCE-90838-4
Mount Remote Filesystems with nodev
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_nodev_remote_filesystems | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-90838-4 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. | ||||||||||||||||||||
| Rationale | Legitimate device files should only exist in the /dev directory. NFS mounts
should not present device files to users. |
Mount Remote Filesystems with noexecxccdf_org.ssgproject.content_rule_mount_option_noexec_remote_filesystems mediumCCE-84246-8
Mount Remote Filesystems with noexec
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_noexec_remote_filesystems | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-84246-8 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. | ||||||||||||||||||||
| Rationale | The noexec mount option causes the system not to execute binary files. This option must be used
for mounting any file system not containing approved binary files as they may be incompatible. Executing
files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized
administrative access. |
Mount Remote Filesystems with nosuidxccdf_org.ssgproject.content_rule_mount_option_nosuid_remote_filesystems mediumCCE-84247-6
Mount Remote Filesystems with nosuid
| Rule ID | xccdf_org.ssgproject.content_rule_mount_option_nosuid_remote_filesystems | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-84247-6 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts. | ||||||||||||||||||||
| Rationale | NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables
should be installed to their default location on the local filesystem. |
Uninstall nfs-utils Packagexccdf_org.ssgproject.content_rule_package_nfs-utils_removed lowCCE-84243-5
Uninstall nfs-utils Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_nfs-utils_removed | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-package_nfs-utils_removed:def:1 | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | low | ||||||
| Identifiers: | CCE-84243-5 | ||||||
| References: |
| ||||||
| Description | The nfs-utils package can be removed with the following command:
$ sudo dnf remove nfs-utils | ||||||
| Rationale | nfs-utils provides a daemon for the kernel NFS server and related tools. This
package also contains the showmount program. showmount queries the mount
daemon on a remote host for information about the Network File System (NFS) server on the
remote host. For example, showmount can display the clients which are mounted on
that host. |
OVAL test results details
package nfs-utils is removed oval:ssg-test_package_nfs-utils_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_nfs-utils_removed:obj:1 of type rpminfo_object
| Name |
|---|
| nfs-utils |
The Chrony package is installedxccdf_org.ssgproject.content_rule_package_chrony_installed mediumCCE-84215-3
The Chrony package is installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_chrony_installed | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-84215-3 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | System time should be synchronized between all systems in an environment. This is
typically done by establishing an authoritative time server or set of servers and having all
systems synchronize their clocks to them.
The chrony package can be installed with the following command:
$ sudo dnf install chrony | ||||||||||||||||||||
| Rationale | Time synchronization is important to support time sensitive security mechanisms like
Kerberos and also ensures log files have consistent time records across the enterprise,
which aids in forensic investigations. |
The Chronyd service is enabledxccdf_org.ssgproject.content_rule_service_chronyd_enabled mediumCCE-84217-9
The Chronyd service is enabled
| Rule ID | xccdf_org.ssgproject.content_rule_service_chronyd_enabled | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-84217-9 | ||||||||||
| References: |
| ||||||||||
| Description | chrony is a daemon which implements the Network Time Protocol (NTP) is designed to
synchronize system clocks across a variety of systems and use a source that is highly
accurate. More information on chrony can be found at
https://chrony-project.org/.
Chrony can be configured to be a client and/or a server.
To enable Chronyd service, you can run:
# systemctl enable chronyd.service
This recommendation only applies if chrony is in use on the system. | ||||||||||
| Rationale | If chrony is in use on the system proper configuration is vital to ensuring time
synchronization is working properly. |
A remote time server for Chrony is configuredxccdf_org.ssgproject.content_rule_chronyd_specify_remote_server mediumCCE-84218-7
A remote time server for Chrony is configured
| Rule ID | xccdf_org.ssgproject.content_rule_chronyd_specify_remote_server | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-84218-7 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | Chrony is a daemon which implements the Network Time Protocol (NTP). It is designed
to synchronize system clocks across a variety of systems and use a source that is highly
accurate. More information on chrony can be found at
https://chrony-project.org/.
Chrony can be configured to be a client and/or a server.
Add or edit server or pool lines to /etc/chrony.conf as appropriate:
server <remote-server>Alternatively, server or pool directives can be specified in files included via sourcedir or confdir directives in /etc/chrony.conf.
When using sourcedir, create .sources files in the specified directory:
# In /etc/chrony.conf: sourcedir /etc/chrony/sources.d # In /etc/chrony/sources.d/ntp.sources: server 0.pool.ntp.orgWhen using confdir, create .conf files in the specified directory:
# In /etc/chrony.conf: confdir /etc/chrony/conf.d # In /etc/chrony/conf.d/ntp-servers.conf: pool 1.pool.ntp.orgMultiple servers may be configured. | ||||||||||||||||||||
| Rationale | If chrony is in use on the system proper configuration is vital to ensuring time
synchronization is working properly. |
Disable chrony daemon from acting as serverxccdf_org.ssgproject.content_rule_chronyd_client_only lowCCE-87543-5
Disable chrony daemon from acting as server
| Rule ID | xccdf_org.ssgproject.content_rule_chronyd_client_only | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | low | ||||||||||
| Identifiers: | CCE-87543-5 | ||||||||||
| References: |
| ||||||||||
| Description | The port option in /etc/chrony.conf can be set to
0 to make chrony daemon to never open any listening port
for server operation and to operate strictly in a client-only mode. | ||||||||||
| Rationale | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. |
Disable network management of chrony daemonxccdf_org.ssgproject.content_rule_chronyd_no_chronyc_network lowCCE-88876-8
Disable network management of chrony daemon
| Rule ID | xccdf_org.ssgproject.content_rule_chronyd_no_chronyc_network | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | low | ||||||||
| Identifiers: | CCE-88876-8 | ||||||||
| References: |
| ||||||||
| Description | The cmdport option in /etc/chrony.conf can be set to
0 to stop chrony daemon from listening on the UDP port 323
for management connections made by chronyc. | ||||||||
| Rationale | Minimizing the exposure of the server functionality of the chrony
daemon diminishes the attack surface. |
Configure Time Service Maxpoll Intervalxccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll mediumCCE-88648-1
Configure Time Service Maxpoll Interval
| Rule ID | xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-88648-1 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The maxpoll should be configured to
16 in /etc/ntp.conf or
/etc/chrony.conf (or /etc/chrony.d/) to continuously poll time servers. To configure
maxpoll in /etc/ntp.conf or /etc/chrony.conf (or /etc/chrony.d/)
add the following after each server, pool or peer entry:
maxpoll 16
to server directives. If using chrony, any pool directives
should be configured too. | ||||||||||||||||||||
| Rationale | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.
Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). |
Ensure Chrony is only configured with the server directivexccdf_org.ssgproject.content_rule_chronyd_server_directive mediumCCE-87077-4
Ensure Chrony is only configured with the server directive
| Rule ID | xccdf_org.ssgproject.content_rule_chronyd_server_directive | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-87077-4 | ||||||
| References: |
| ||||||
| Description | Check that Chrony only has time sources configured with the server directive. | ||||||
| Rationale | Depending on the infrastructure being used the pool directive may not be supported.
Using the server directive allows for better control of where the system gets time data from. | ||||||
| Warnings | warning
This rule doesn't come with a remediation, the time source needs to be added by the administrator. |
Remove Host-Based Authentication Filesxccdf_org.ssgproject.content_rule_no_host_based_files highCCE-90208-0
Remove Host-Based Authentication Files
| Rule ID | xccdf_org.ssgproject.content_rule_no_host_based_files | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-no_host_based_files:def:1 | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | high | ||||||
| Identifiers: | CCE-90208-0 | ||||||
| References: |
| ||||||
| Description | The shosts.equiv file lists remote hosts and users that are trusted by the local
system. To remove these files, run the following command to delete them from any location:
$ sudo rm /[path]/[to]/[file]/shosts.equiv | ||||||
| Rationale | The shosts.equiv files are used to configure host-based authentication for the system via SSH.
Host-based authentication is not sufficient for preventing unauthorized access to the system,
as it does not require interactive identification and authentication of a connection request,
or for the use of two-factor authentication. |
OVAL test results details
look for shosts.equiv in / oval:ssg-test_no_shosts_equiv:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_no_shosts_equiv_files_root:obj:1 of type file_object
| Behaviors | Path | Filename |
|---|---|---|
| / | shosts.equiv |
Remove User Host-Based Authentication Filesxccdf_org.ssgproject.content_rule_no_user_host_based_files highCCE-86532-9
Remove User Host-Based Authentication Files
| Rule ID | xccdf_org.ssgproject.content_rule_no_user_host_based_files | ||||||
| Result | pass | ||||||
| Multi-check rule | no | ||||||
| OVAL Definition ID | oval:ssg-no_user_host_based_files:def:1 | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | high | ||||||
| Identifiers: | CCE-86532-9 | ||||||
| References: |
| ||||||
| Description | The ~/.shosts (in each user's home directory) files
list remote hosts and users that are trusted by the
local system. To remove these files, run the following command
to delete them from any location:
$ sudo find / -name '.shosts' -type f -delete | ||||||
| Rationale | The .shosts files are used to configure host-based authentication for
individual users or the system via SSH. Host-based authentication is not
sufficient for preventing unauthorized access to the system, as it does not
require interactive identification and authentication of a connection request,
or for the use of two-factor authentication. |
OVAL test results details
look for .shosts in / oval:ssg-test_no_shosts:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-object_no_shosts_files_root:obj:1 of type file_object
| Behaviors | Path | Filename |
|---|---|---|
| / | .shosts |
Uninstall telnet-server Packagexccdf_org.ssgproject.content_rule_package_telnet-server_removed highCCE-84149-4
Uninstall telnet-server Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_telnet-server_removed | ||||||||||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-package_telnet-server_removed:def:1 | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-84149-4 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | The telnet-server package can be removed with the following command:
$ sudo dnf remove telnet-server | ||||||||||||||||||||||||||||||||||||
| Rationale | It is detrimental for operating systems to provide, or install by default,
functionality exceeding requirements or mission objectives. These
unnecessary capabilities are often overlooked and therefore may remain
insecure. They increase the risk to the platform by providing additional
attack vectors.
The telnet service provides an unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to login using this service, the privileged user password could be compromised. Removing the telnet-server package decreases the risk of the
telnet service's accidental (or intentional) activation. |
OVAL test results details
package telnet-server is removed oval:ssg-test_package_telnet-server_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_telnet-server_removed:obj:1 of type rpminfo_object
| Name |
|---|
| telnet-server |
Uninstall tftp-server Packagexccdf_org.ssgproject.content_rule_package_tftp-server_removed highCCE-84154-4
Uninstall tftp-server Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_tftp-server_removed | ||||||||||||||||||||||||||||
| Result | pass | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| OVAL Definition ID | oval:ssg-package_tftp-server_removed:def:1 | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||
| Identifiers: | CCE-84154-4 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | The tftp-server package can be removed with the following command: $ sudo dnf remove tftp-server | ||||||||||||||||||||||||||||
| Rationale | Removing the tftp-server package decreases the risk of the accidental
(or intentional) activation of tftp services.
If TFTP is required for operational support (such as transmission of router configurations), its use must be documented with the Information Systems Security Manager (ISSM), restricted to only authorized personnel, and have access control rules established. |
OVAL test results details
package tftp-server is removed oval:ssg-test_package_tftp-server_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_tftp-server_removed:obj:1 of type rpminfo_object
| Name |
|---|
| tftp-server |
Verify the SSH Private Key Files Have a Passcodexccdf_org.ssgproject.content_rule_ssh_keys_passphrase_protected mediumCCE-86553-5
Verify the SSH Private Key Files Have a Passcode
| Rule ID | xccdf_org.ssgproject.content_rule_ssh_keys_passphrase_protected | ||||||
| Result | notchecked | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86553-5 | ||||||
| References: |
| ||||||
| Description | When creating SSH key pairs, always use a passcode.
You can create such keys with the following command: $ sudo ssh-keygen -n [passphrase]Red Hat Enterprise Linux 9, for certificate-based authentication, must enforce authorized access to the corresponding private key. | ||||||
| Rationale | If an unauthorized user obtains access to a private key without a passcode,
that user would have unauthorized access to any system where the associated
public key has been installed. | ||||||
SSHD Must Include System Crypto Policy Config Filexccdf_org.ssgproject.content_rule_sshd_include_crypto_policy mediumCCE-90566-1
SSHD Must Include System Crypto Policy Config File
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_include_crypto_policy | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90566-1 | ||||||||
| References: |
| ||||||||
| Description | SSHD should follow the system cryptographic policy.
In order to accomplish this the SSHD configuration should include the configuration file provided by the system crypto policy.
The following line should be present in /etc/ssh/sshd_config or in a file included by this file (a file within the /etc/ssh/sshd_config.d directory):
Include /etc/crypto-policies/back-ends/opensshserver.config | ||||||||
| Rationale | Without cryptographic integrity protections, information can be altered by unauthorized users without detection. | ||||||||
| Warnings | warning
There is no automated remediation because recommended action could severely disrupt the system and might not be efficient in fixing the problem. |
Set SSH Client Alive Count Maxxccdf_org.ssgproject.content_rule_sshd_set_keepalive mediumCCE-90805-3
Set SSH Client Alive Count Max
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_set_keepalive | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90805-3 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | The SSH server sends at most ClientAliveCountMax messages
during a SSH session and waits for a response from the SSH client.
The option ClientAliveInterval configures timeout after
each ClientAliveCountMax message. If the SSH server does not
receive a response from the client, then the connection is considered unresponsive
and terminated.
For SSH earlier than v8.2, a ClientAliveCountMax value of 0
causes a timeout precisely when the ClientAliveInterval is set.
Starting with v8.2, a value of 0 disables the timeout functionality
completely. If the option is set to a number greater than 0, then
the session will be disconnected after
ClientAliveInterval * ClientAliveCountMax seconds without receiving
a keep alive message. | ||||||||||||||||||||||||||||||||||||
| Rationale | This ensures a user login will be terminated as soon as the ClientAliveInterval
is reached. |
Set SSH Client Alive Intervalxccdf_org.ssgproject.content_rule_sshd_set_idle_timeout mediumCCE-90811-1
Set SSH Client Alive Interval
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_set_idle_timeout | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90811-1 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | SSH allows administrators to set a network responsiveness timeout interval.
After this interval has passed, the unresponsive client will be automatically logged out.
To set this timeout interval, edit the following line in /etc/ssh/sshd_config as
follows:
ClientAliveInterval 600
The timeout interval is given in seconds. For example, have a timeout of 10 minutes, set interval to 600. If a shorter timeout has already been set for the login shell, that value will preempt any SSH setting made in /etc/ssh/sshd_config. Keep in mind that
some processes may stop SSH from correctly detecting that the user is idle. | ||||||||||||||||||||||||||||||||||
| Rationale | Terminating an idle ssh session within a short time period reduces the window of
opportunity for unauthorized personnel to take control of a management session
enabled on the console or console port that has been let unattended. | ||||||||||||||||||||||||||||||||||
| Warnings | warning
SSH disconnecting unresponsive clients will not have desired effect without also
configuring ClientAliveCountMax in the SSH service configuration. warning
Following conditions may prevent the SSH session to time out:
|
Disable Host-Based Authenticationxccdf_org.ssgproject.content_rule_disable_host_auth mediumCCE-90816-0
Disable Host-Based Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_disable_host_auth | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90816-0 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | SSH's cryptographic host-based authentication is
more secure than .rhosts authentication. However, it is
not recommended that hosts unilaterally trust one another, even
within an organization.
The default SSH configuration disables host-based authentication. The appropriate configuration is used if no value is set for HostbasedAuthentication.
To explicitly disable host-based authentication, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
HostbasedAuthentication no | ||||||||||||||||||||||||||||||||||||
| Rationale | SSH trust relationships mean a compromise on one host
can allow an attacker to move trivially to other hosts. |
Enable SSH Server firewalld Firewall Exceptionxccdf_org.ssgproject.content_rule_firewalld_sshd_port_enabled mediumCCE-89175-4
Enable SSH Server firewalld Firewall Exception
| Rule ID | xccdf_org.ssgproject.content_rule_firewalld_sshd_port_enabled | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-89175-4 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | If the SSH server is in use, inbound connections to SSH's port should be allowed to permit
remote access through SSH. In more restrictive firewalld settings, the SSH port should be
added to the proper firewalld zone in order to allow SSH remote access.
To configure firewalld to allow ssh access, run the following command(s):
firewall-cmd --permanent --add-service=sshThen run the following command to load the newly created rule(s): firewall-cmd --reload | ||||||||||||||
| Rationale | If inbound SSH connections are expected, adding the SSH port to the proper firewalld zone
will allow remote access through the SSH port. | ||||||||||||||
| Warnings | warning
The remediation for this rule uses firewall-cmd and nmcli tools.
Therefore, it will only be executed if firewalld and NetworkManager
services are running. Otherwise, the remediation will be aborted and a informative message
will be shown in the remediation report.
These respective services will not be started in order to preserve any intentional change
in network components related to firewall and network interfaces.warning
This rule also checks if the SSH port was modified by the administrator in the firewalld
services definitions and is reflecting the expected port number. Although this is checked,
fixing the custom ssh.xml file placed by the administrator at /etc/firewalld/services it
is not in the scope of the remediation since there is no reliable way to manually change
the respective file. If the default SSH port is modified, it is on the administrator
responsibility to ensure the firewalld customizations in the service port level are
properly configured. warning
Red Hat Enterprise Linux 9 prefers and recommends to use NetworkManager keyfiles instead of the
ifcfg files stored in /etc/sysconfig/network-scripts. Therefore, if the
system was upgraded from a previous release, make sure the NIC configuration files are
properly migrated from ifcfg format to NetworkManager keyfiles. Otherwise, this
rule won't be able to check the configuration. The migration can be accomplished by
nmcli connection migrate command. |
Disable Compression Or Set Compression to delayedxccdf_org.ssgproject.content_rule_sshd_disable_compression mediumCCE-90801-2
Disable Compression Or Set Compression to delayed
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_compression | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-90801-2 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | Compression is useful for slow network connections over long
distances but can cause performance issues on local LANs. If use of compression
is required, it should be enabled only after a user has authenticated; otherwise,
it should be disabled. To disable compression or delay compression until after
a user has successfully authenticated, add or correct the following line in the
/etc/ssh/sshd_config file:
Compression no
| ||||||||||||||||||||||||
| Rationale | If compression is allowed in an SSH connection prior to authentication,
vulnerabilities in the compression software could result in compromise of the
system from an unauthenticated connection, potentially with root privileges. |
Disable SSH Access via Empty Passwordsxccdf_org.ssgproject.content_rule_sshd_disable_empty_passwords highCCE-90799-8
Disable SSH Access via Empty Passwords
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_empty_passwords | ||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||
| Severity | high | ||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90799-8 | ||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||
| Description | Disallow SSH login with empty passwords.
The default SSH configuration disables logins with empty passwords. The appropriate
configuration is used if no value is set for PermitEmptyPasswords.
To explicitly disallow SSH login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
PermitEmptyPasswords noAny accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords. | ||||||||||||||||||||||||||||||||||||||
| Rationale | Configuring this setting for the SSH daemon provides additional assurance
that remote login via SSH will require a password, even in the event of
misconfiguration elsewhere. |
Disable GSSAPI Authenticationxccdf_org.ssgproject.content_rule_sshd_disable_gssapi_auth mediumCCE-90808-7
Disable GSSAPI Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_gssapi_auth | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-90808-7 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like GSSAPI.
The default SSH configuration disallows authentications based on GSSAPI. The appropriate configuration is used if no value is set for GSSAPIAuthentication.
To explicitly disable GSSAPI authentication, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
GSSAPIAuthentication no | ||||||||||||||||||||||||||||||
| Rationale | GSSAPI authentication is used to provide additional authentication mechanisms to
applications. Allowing GSSAPI authentication through SSH exposes the system's
GSSAPI to remote hosts, increasing the attack surface of the system. |
Disable Kerberos Authenticationxccdf_org.ssgproject.content_rule_sshd_disable_kerb_auth mediumCCE-90802-0
Disable Kerberos Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_kerb_auth | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90802-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like Kerberos.
The default SSH configuration disallows authentication validation through Kerberos. The appropriate configuration is used if no value is set for KerberosAuthentication.
To explicitly disable Kerberos authentication, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
KerberosAuthentication no | ||||||||||||||||||||||||||||
| Rationale | Kerberos authentication for SSH is often implemented using GSSAPI. If Kerberos
is enabled through SSH, the SSH daemon provides a means of access to the
system's Kerberos implementation.
Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use unused methods of authentication, even in the event of misconfiguration elsewhere. |
Disable SSH Support for .rhosts Filesxccdf_org.ssgproject.content_rule_sshd_disable_rhosts mediumCCE-90797-2
Disable SSH Support for .rhosts Files
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_rhosts | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-90797-2 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | SSH can emulate the behavior of the obsolete rsh
command in allowing users to enable insecure access to their
accounts via .rhosts files.
The default SSH configuration disables support for .rhosts. The appropriate
configuration is used if no value is set for IgnoreRhosts.
To explicitly disable support for .rhosts files, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
IgnoreRhosts yes | ||||||||||||||||||||||||||||||
| Rationale | SSH trust relationships mean a compromise on one host
can allow an attacker to move trivially to other hosts. |
Disable SSH Root Loginxccdf_org.ssgproject.content_rule_sshd_disable_root_login mediumCCE-90800-4
Disable SSH Root Login
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_root_login | ||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90800-4 | ||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||
| Description | The root user should never be allowed to login to a
system directly over a network.
To disable root login via SSH, add or correct the following line in
/etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
PermitRootLogin no | ||||||||||||||||||||||||||||||||||||||||||
| Rationale | Even though the communications channel may be encrypted, an additional layer of
security is gained by extending the policy of not logging directly on as root.
In addition, logging in with a user-specific account provides individual
accountability of actions performed on the system and also helps to minimize
direct attack attempts on root's password. |
Disable SSH Support for User Known Hostsxccdf_org.ssgproject.content_rule_sshd_disable_user_known_hosts mediumCCE-90796-4
Disable SSH Support for User Known Hosts
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_user_known_hosts | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-90796-4 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | SSH can allow system users to connect to systems if a cache of the remote
systems public keys is available. This should be disabled.
To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
IgnoreUserKnownHosts yes | ||||||||||||||||||||||||||
| Rationale | Configuring this setting for the SSH daemon provides additional
assurance that remote login via SSH will require a password, even
in the event of misconfiguration elsewhere. |
Disable X11 Forwardingxccdf_org.ssgproject.content_rule_sshd_disable_x11_forwarding mediumCCE-90798-0
Disable X11 Forwarding
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_disable_x11_forwarding | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-90798-0 | ||||||||||||
| References: |
| ||||||||||||
| Description | The X11Forwarding parameter provides the ability to tunnel X11 traffic
through the connection to enable remote graphic connections.
SSH has the capability to encrypt remote X11 connections when SSH's
X11Forwarding option is enabled.
The default SSH configuration disables X11Forwarding. The appropriate configuration is used if no value is set for X11Forwarding.
To explicitly disable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
X11Forwarding no | ||||||||||||
| Rationale | Disable X11 forwarding unless there is an operational requirement to use X11
applications directly. There is a small risk that the remote X11 servers of
users who are logged in via SSH with X11 forwarding could be compromised by
other users on the X11 server. Note that even if X11 forwarding is disabled,
users can always install their own forwarders. |
Do Not Allow SSH Environment Optionsxccdf_org.ssgproject.content_rule_sshd_do_not_permit_user_env mediumCCE-90803-8
Do Not Allow SSH Environment Options
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_do_not_permit_user_env | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90803-8 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | Ensure that users are not able to override environment variables of the SSH daemon.
The default SSH configuration disables environment processing. The appropriate configuration is used if no value is set for PermitUserEnvironment.
To explicitly disable Environment options, add or correct the following /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
PermitUserEnvironment no | ||||||||||||||||||||||||||||||||||
| Rationale | SSH environment options potentially allow users to bypass
access restriction in some configurations. |
Enable PAMxccdf_org.ssgproject.content_rule_sshd_enable_pam mediumCCE-86722-6
Enable PAM
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_enable_pam | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-86722-6 | ||||||||||
| References: |
| ||||||||||
| Description | UsePAM Enables the Pluggable Authentication Module interface. If set to “yes” this will
enable PAM authentication using ChallengeResponseAuthentication and
PasswordAuthentication in addition to PAM account and session module processing for all
authentication types.
To enable PAM authentication, add or correct the following line in
/etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
UsePAM yes | ||||||||||
| Rationale | When UsePAM is set to yes, PAM runs through account and session types properly. This is
important if you want to restrict access to services based off of IP, time or other factors of
the account. Additionally, you can make sure users inherit certain environment variables
on login or disallow access to the server. |
Enable Public Key Authenticationxccdf_org.ssgproject.content_rule_sshd_enable_pubkey_auth mediumCCE-86138-5
Enable Public Key Authentication
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_enable_pubkey_auth | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86138-5 | ||||||||
| References: |
| ||||||||
| Description | Enable SSH login with public keys.
The default SSH configuration enables authentication based on public keys. The appropriate configuration is used if no value is set for PubkeyAuthentication.
To explicitly enable Public Key Authentication, add or correct the following /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
PubkeyAuthentication yes | ||||||||
| Rationale | Without the use of multifactor authentication, the ease of access to
privileged functions is greatly increased. Multifactor authentication
requires using two or more factors to achieve authentication.
A privileged account is defined as an information system account with
authorizations of a privileged user.
Smart cards or hardware tokens paired with digital certificates are
common examples of multifactor implementations. |
Enable Use of Strict Mode Checkingxccdf_org.ssgproject.content_rule_sshd_enable_strictmodes mediumCCE-90809-5
Enable Use of Strict Mode Checking
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_enable_strictmodes | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90809-5 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description | SSHs StrictModes option checks file and ownership permissions in
the user's home directory .ssh folder before accepting login. If world-
writable permissions are found, logon is rejected.
The default SSH configuration has StrictModes enabled. The appropriate
configuration is used if no value is set for StrictModes.
To explicitly enable StrictModes in SSH, add or correct the following line in
/etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
StrictModes yes | ||||||||||||||||||||||||||||
| Rationale | If other users have access to modify user-specific SSH configuration files, they
may be able to log into the system as another user. |
Enable SSH Print Last Logxccdf_org.ssgproject.content_rule_sshd_print_last_log mediumCCE-90804-6
Enable SSH Print Last Log
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_print_last_log | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-90804-6 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Ensure that SSH will display the date and time of the last successful account logon.
The default SSH configuration enables print of the date and time of the last login. The appropriate configuration is used if no value is set for PrintLastLog.
To explicitly enable LastLog in SSH, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
PrintLastLog yes | ||||||||||||||||||||||
| Rationale | Providing users feedback on when account accesses last occurred facilitates user
recognition and reporting of unauthorized account use. |
Force frequent session key renegotiationxccdf_org.ssgproject.content_rule_sshd_rekey_limit mediumCCE-90815-2
Force frequent session key renegotiation
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_rekey_limit | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90815-2 | ||||||||
| References: |
| ||||||||
| Description | The RekeyLimit parameter specifies how often
the session key of the is renegotiated, both in terms of
amount of data that may be transmitted and the time
elapsed.To decrease the default limits, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
RekeyLimit 1G
1h
| ||||||||
| Rationale | By decreasing the limit based on the amount of data and enabling
time-based limit, effects of potential attacks against
encryption keys are limited. |
Set SSH Daemon LogLevel to VERBOSExccdf_org.ssgproject.content_rule_sshd_set_loglevel_verbose mediumCCE-86923-0
Set SSH Daemon LogLevel to VERBOSE
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_set_loglevel_verbose | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-86923-0 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The VERBOSE parameter configures the SSH daemon to record login and logout activity.
To specify the log level in
SSH, add or correct the following line in
/etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
LogLevel VERBOSE | ||||||||||||||||
| Rationale | SSH provides several logging levels with varying amounts of verbosity. DEBUG is specifically
not recommended other than strictly for debugging SSH communications since it provides
so much data that it is difficult to identify important security information. INFO or
VERBOSE level is the basic level that only records login activity of SSH users. In many
situations, such as Incident Response, it is important to determine when a particular user was active
on a system. The logout record can eliminate those users who disconnected, which helps narrow the
field. |
Prevent remote hosts from connecting to the proxy displayxccdf_org.ssgproject.content_rule_sshd_x11_use_localhost mediumCCE-89105-1
Prevent remote hosts from connecting to the proxy display
| Rule ID | xccdf_org.ssgproject.content_rule_sshd_x11_use_localhost | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89105-1 | ||||||||
| References: |
| ||||||||
| Description | The SSH daemon should prevent remote hosts from connecting to the proxy
display.
The default SSH configuration for X11UseLocalhost is yes,
which prevents remote hosts from connecting to the proxy display.
To explicitly prevent remote connections to the proxy display, add or correct the following line in /etc/ssh/sshd_config.d/00-complianceascode-hardening.conf:
X11UseLocalhost yes
| ||||||||
| Rationale | When X11 forwarding is enabled, there may be additional exposure to the
server and client displays if the sshd proxy display is configured to listen
on the wildcard address. By default, sshd binds the forwarding server to the
loopback address and sets the hostname part of the DISPLAY
environment variable to localhost. This prevents remote hosts from
connecting to the proxy display. |
Install OpenSSH client softwarexccdf_org.ssgproject.content_rule_package_openssh-clients_installed mediumCCE-90836-8
Install OpenSSH client software
| Rule ID | xccdf_org.ssgproject.content_rule_package_openssh-clients_installed | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-package_openssh-clients_installed:def:1 | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90836-8 | ||||||||
| References: |
| ||||||||
| Description | The openssh-clients package can be installed with the following command:
$ sudo dnf install openssh-clients | ||||||||
| Rationale | This package includes utilities to make encrypted connections and transfer
files securely to SSH servers. |
OVAL test results details
package openssh-clients is installed oval:ssg-test_package_openssh-clients_installed:tst:1 true
Following items have been found on the system:
| Result of item-state comparison | Name | Arch | Epoch | Release | Version | Evr | Signature keyid | Extended name |
|---|---|---|---|---|---|---|---|---|
| not evaluated | openssh-clients | x86_64 | (none) | 7.el9_8 | 9.9p1 | 0:9.9p1-7.el9_8 | 199e2f91fd431d51 | openssh-clients-0:9.9p1-7.el9_8.x86_64 |
Install the OpenSSH Server Packagexccdf_org.ssgproject.content_rule_package_openssh-server_installed mediumCCE-90823-6
Install the OpenSSH Server Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_openssh-server_installed | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-90823-6 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The openssh-server package should be installed.
The openssh-server package can be installed with the following command:
$ sudo dnf install openssh-server | ||||||||||||||||||||
| Rationale | Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered. |
Enable the OpenSSH Servicexccdf_org.ssgproject.content_rule_service_sshd_enabled mediumCCE-90822-8
Enable the OpenSSH Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_sshd_enabled | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-90822-8 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The SSH server service, sshd, is commonly needed.
The sshd service can be enabled with the following command:
$ sudo systemctl enable sshd.service | ||||||||||||||||||||||
| Rationale | Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.
This checklist item applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, etc). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. |
Verify Group Who Owns SSH Server Configuration Filesxccdf_org.ssgproject.content_rule_directory_groupowner_sshd_config_d mediumCCE-86179-9
Verify Group Who Owns SSH Server Configuration Files
| Rule ID | xccdf_org.ssgproject.content_rule_directory_groupowner_sshd_config_d | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-86179-9 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/ssh/sshd_config.d, run the command:
$ sudo chgrp root /etc/ssh/sshd_config.d | ||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Owner on SSH Server Configuration Filesxccdf_org.ssgproject.content_rule_directory_owner_sshd_config_d mediumCCE-86180-7
Verify Owner on SSH Server Configuration Files
| Rule ID | xccdf_org.ssgproject.content_rule_directory_owner_sshd_config_d | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-86180-7 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description |
To properly set the owner of /etc/ssh/sshd_config.d, run the command:
$ sudo chown root /etc/ssh/sshd_config.d | ||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns SSH Server config filexccdf_org.ssgproject.content_rule_file_groupowner_sshd_config mediumCCE-90817-8
Verify Group Who Owns SSH Server config file
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_sshd_config | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90817-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
To properly set the group owner of /etc/ssh/sshd_config, run the command:
$ sudo chgrp root /etc/ssh/sshd_config | ||||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Group Who Owns SSH Server Configuration Filesxccdf_org.ssgproject.content_rule_file_groupowner_sshd_drop_in_config mediumCCE-86253-2
Verify Group Who Owns SSH Server Configuration Files
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupowner_sshd_drop_in_config | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-86253-2 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description |
To properly set the group owner of files in /etc/ssh/sshd_config.d, run the command:
find -H /etc/ssh/sshd_config.d -type d -exec chgrp -L root {} \;
| ||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Owner on SSH Server config filexccdf_org.ssgproject.content_rule_file_owner_sshd_config mediumCCE-90821-0
Verify Owner on SSH Server config file
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_sshd_config | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-90821-0 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
To properly set the owner of /etc/ssh/sshd_config, run the command:
$ sudo chown root /etc/ssh/sshd_config | ||||||||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
Verify Owner on SSH Server Configuration Filesxccdf_org.ssgproject.content_rule_file_owner_sshd_drop_in_config mediumCCE-86217-7
Verify Owner on SSH Server Configuration Files
| Rule ID | xccdf_org.ssgproject.content_rule_file_owner_sshd_drop_in_config | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-86217-7 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description |
To properly set the owner of files in /etc/ssh/sshd_config.d, run the command:
find -H /etc/ssh/sshd_config.d -type d -exec chown -L root {} \;
| ||||||||||||||||||||||
| Rationale | Service configuration files enable or disable features of their respective
services that if configured incorrectly can lead to insecure and vulnerable
configurations. Therefore, service configuration files should be owned by the
correct group to prevent unauthorized changes. |
The File /etc/ssh/sshd_config.d/50-redhat.conf Must Existxccdf_org.ssgproject.content_rule_file_sshd_50_redhat_exists mediumCCE-88599-6
The File /etc/ssh/sshd_config.d/50-redhat.conf Must Exist
| Rule ID | xccdf_org.ssgproject.content_rule_file_sshd_50_redhat_exists | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-88599-6 | ||||||||
| References: |
| ||||||||
| Description | The /etc/ssh/sshd_config.d/50-redhat.conf file must exist as it contains important
settings to secure SSH. | ||||||||
| Rationale | The file must exist to configure SSH correctly. | ||||||||
| Warnings | warning
There is no remediation available for this rule since this file needs to have the correct content for the given system. |
Certificate status checking in SSSDxccdf_org.ssgproject.content_rule_sssd_certificate_verification mediumCCE-87088-1
Certificate status checking in SSSD
| Rule ID | xccdf_org.ssgproject.content_rule_sssd_certificate_verification | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87088-1 | ||||||||
| References: |
| ||||||||
| Description | Multifactor solutions that require devices separate from information systems gaining access include,
for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
Configuring certificate_verification to ocsp_dgst=sha512
ensures that certificates for
multifactor solutions are checked via Online Certificate Status Protocol (OCSP). | ||||||||
| Rationale | Ensuring that multifactor solutions certificates are checked via Online Certificate Status Protocol (OCSP)
ensures the security of the system. |
Enable Certmap in SSSDxccdf_org.ssgproject.content_rule_sssd_enable_certmap mediumCCE-89737-1
Enable Certmap in SSSD
| Rule ID | xccdf_org.ssgproject.content_rule_sssd_enable_certmap | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89737-1 | ||||||||
| References: |
| ||||||||
| Description | SSSD should be configured to verify the certificate of the user or group. To set this up
ensure that section like certmap/testing.test/rule_name is setup in
/etc/sssd/sssd.conf. For example
[certmap/testing.test/rule_name]
matchrule =<SAN>.*EDIPI@mil
maprule = (userCertificate;binary={cert!bin})
domains = testing.test
| ||||||||
| Rationale | Without mapping the certificate used to authenticate to the user account, the ability to
determine the identity of the individual user or group will not be available for forensic
analysis. | ||||||||
| Warnings | warning
Automatic remediation of this control is not available, since all of the settings in
in the certmap need to be customized. |
Enable Smartcards in SSSDxccdf_org.ssgproject.content_rule_sssd_enable_smartcards mediumCCE-89155-6
Enable Smartcards in SSSD
| Rule ID | xccdf_org.ssgproject.content_rule_sssd_enable_smartcards | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-89155-6 | ||||||||||
| References: |
| ||||||||||
| Description | SSSD should be configured to authenticate access to the system using smart cards.
To enable smart cards in SSSD, set pam_cert_auth to True under the
[pam] section in /etc/sssd/sssd.conf. For example:
[pam] pam_cert_auth = TrueAdd or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include "try_cert_auth" or "require_cert_auth" option, like in the following example: /etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_authAlso add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to include the "allow_missing_name" option, like in the following example: /etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name | ||||||||||
| Rationale | Using an authentication device, such as a CAC or token that is separate from
the information system, ensures that even if the information system is
compromised, that compromise will not affect credentials stored on the
authentication device.
Multi-Factor Authentication (MFA) solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards or similar secure authentication devices issued by an organization or identity provider. |
SSSD Has a Correct Trust Anchorxccdf_org.ssgproject.content_rule_sssd_has_trust_anchor mediumCCE-86321-7
SSSD Has a Correct Trust Anchor
| Rule ID | xccdf_org.ssgproject.content_rule_sssd_has_trust_anchor | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-86321-7 | ||||||||
| References: |
| ||||||||
| Description | SSSD must have acceptable trust anchor present. | ||||||||
| Rationale | Without path validation, an informed trust decision by the relying party cannot be made when
presented with any certificate not already explicitly trusted.
A trust anchor is an authoritative entity represented via a public key and associated data. It
is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.
When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor;
it can be, for example, a Certification Authority (CA). A certification path starts with the
subject certificate and proceeds through a number of intermediate certificates up to a trusted
root certificate, typically issued by a trusted CA.
This requirement verifies that a certification path to an accepted trust anchor is used for
certificate validation and that the path includes status information. Path validation is
necessary for a relying party to make an informed trust decision when presented with any
certificate not already explicitly trusted. Status information for certification paths includes
certificate revocation lists or online certificate status protocol responses.
Validation of the certificate status information is out of scope for this requirement. | ||||||||
| Warnings | warning
Automatic remediation of this control is not available. |
Configure SSSD to Expire Offline Credentialsxccdf_org.ssgproject.content_rule_sssd_offline_cred_expiration mediumCCE-87996-5
Configure SSSD to Expire Offline Credentials
| Rule ID | xccdf_org.ssgproject.content_rule_sssd_offline_cred_expiration | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-87996-5 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | SSSD should be configured to expire offline credentials after 1 day.
Check if SSSD allows cached authentications with the following command:
$ sudo grep cache_credentials /etc/sssd/sssd.conf cache_credentials = trueIf "cache_credentials" is set to "false" or is missing no further checks are required. To configure SSSD to expire offline credentials, set offline_credentials_expiration to 1 under the [pam]
section in /etc/sssd/sssd.conf. For example:
[pam] offline_credentials_expiration = 1 | ||||||||||||||||||||
| Rationale | If cached authentication information is out-of-date, the validity of the
authentication information may be questionable. |
Install usbguard Packagexccdf_org.ssgproject.content_rule_package_usbguard_installed mediumCCE-84203-9
Install usbguard Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_usbguard_installed | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-84203-9 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description |
The usbguard package can be installed with the following command:
$ sudo dnf install usbguard | ||||||||||||||||
| Rationale | usbguard is a software framework that helps to protect
against rogue USB devices by implementing basic whitelisting/blacklisting
capabilities based on USB device attributes. |
Enable the USBGuard Servicexccdf_org.ssgproject.content_rule_service_usbguard_enabled mediumCCE-84205-4
Enable the USBGuard Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_usbguard_enabled | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | medium | ||||||||||||||||
| Identifiers: | CCE-84205-4 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | The USBGuard service should be enabled.
The usbguard service can be enabled with the following command:
$ sudo systemctl enable usbguard.service | ||||||||||||||||
| Rationale | The usbguard service must be running in order to
enforce the USB device authorization policy for all USB devices. |
Log USBGuard daemon audit events using Linux Auditxccdf_org.ssgproject.content_rule_configure_usbguard_auditbackend lowCCE-84206-2
Log USBGuard daemon audit events using Linux Audit
| Rule ID | xccdf_org.ssgproject.content_rule_configure_usbguard_auditbackend | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | low | ||||||||||||
| Identifiers: | CCE-84206-2 | ||||||||||||
| References: |
| ||||||||||||
| Description | To configure USBGuard daemon to log via Linux Audit
(as opposed directly to a file),
AuditBackend option in /etc/usbguard/usbguard-daemon.conf
needs to be set to LinuxAudit. | ||||||||||||
| Rationale | Using the Linux Audit logging allows for centralized trace
of events. |
Generate USBGuard Policyxccdf_org.ssgproject.content_rule_usbguard_generate_policy mediumCCE-88882-6
Generate USBGuard Policy
| Rule ID | xccdf_org.ssgproject.content_rule_usbguard_generate_policy | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-88882-6 | ||||||||||
| References: |
| ||||||||||
| Description | By default USBGuard when enabled prevents access to all USB devices and this lead
to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
the initial policy configuration must be generated based on current connected USB
devices. | ||||||||||
| Rationale | The usbguard must be configured to allow connected USB devices to work
properly, avoiding the system to become inaccessible. |
Disable graphical user interfacexccdf_org.ssgproject.content_rule_xwindows_remove_packages mediumCCE-84106-4
Disable graphical user interface
| Rule ID | xccdf_org.ssgproject.content_rule_xwindows_remove_packages | ||||||||
| Result | pass | ||||||||
| Multi-check rule | no | ||||||||
| OVAL Definition ID | oval:ssg-xwindows_remove_packages:def:1 | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-84106-4 | ||||||||
| References: |
| ||||||||
| Description | By removing the following packages, the system no longer has X Windows installed.
xorg-x11-server-Xorg
xorg-x11-server-common
xorg-x11-server-utils
xorg-x11-server-Xwayland
If X Windows is not installed then the system cannot boot into graphical user mode.
This prevents the system from being accidentally or maliciously booted into a graphical.target
mode. To do so, run the following command:
sudo dnf remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland | ||||||||
| Rationale | Unnecessary service packages must not be installed to decrease the attack surface of the system.
X windows has a long history of security vulnerabilities and should not be installed unless approved and documented. | ||||||||
| Warnings | warning
The installation and use of a Graphical User Interface (GUI) increases your attack vector and decreases your
overall security posture. Removing the package xorg-x11-server-common package will remove the graphical target
which might bring your system to an inconsistent state requiring additional configuration to access the system
again.
The rule xwindows_runlevel_target can be used to configure the system to boot into the multi-user.target.
If a GUI is an operational requirement, a tailored profile that removes this rule should be used before
continuing installation. |
OVAL test results details
package xorg-x11-server-Xorg is removed oval:ssg-test_package_xorg-x11-server-Xorg_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_xorg-x11-server-Xorg_removed:obj:1 of type rpminfo_object
| Name |
|---|
| xorg-x11-server-Xorg |
package xorg-x11-server-common is removed oval:ssg-test_package_xorg-x11-server-common_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_xorg-x11-server-common_removed:obj:1 of type rpminfo_object
| Name |
|---|
| xorg-x11-server-common |
package xorg-x11-server-utils is removed oval:ssg-test_package_xorg-x11-server-utils_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_xorg-x11-server-utils_removed:obj:1 of type rpminfo_object
| Name |
|---|
| xorg-x11-server-utils |
package xorg-x11-server-Xwayland is removed oval:ssg-test_package_xorg-x11-server-Xwayland_removed:tst:1 true
No items have been found conforming to the following objects:
Object oval:ssg-obj_test_package_xorg-x11-server-Xwayland_removed:obj:1 of type rpminfo_object
| Name |
|---|
| xorg-x11-server-Xwayland |
Disable Graphical Environment Startup By Setting Default Targetxccdf_org.ssgproject.content_rule_xwindows_runlevel_target mediumCCE-84105-6
Disable Graphical Environment Startup By Setting Default Target
| Rule ID | xccdf_org.ssgproject.content_rule_xwindows_runlevel_target | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-84105-6 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | Systems that do not require a graphical user interface should only boot by
default into multi-user.target mode. This prevents accidental booting of the system
into a graphical.target mode. Setting the system's default target to
multi-user.target will prevent automatic startup of the graphical environment.
To do so, run:
$ systemctl set-default multi-user.targetYou should see the following output: Removed symlink /etc/systemd/system/default.target. Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target. | ||||||||||||||||||||||
| Rationale | Services that are not required for system and application processes
must not be active to decrease the attack surface of the system. |
Record Events that Modify the System's Discretionary Access Controls - chmodxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chmod mediumCCE-83830-0
Record Events that Modify the System's Discretionary Access Controls - chmod
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chmod | ||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83830-0 | ||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - chownxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chown mediumCCE-83812-8
Record Events that Modify the System's Discretionary Access Controls - chown
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_chown | ||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83812-8 | ||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fchmodxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmod mediumCCE-83832-6
Record Events that Modify the System's Discretionary Access Controls - fchmod
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmod | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83832-6 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fchmodatxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmodat mediumCCE-83822-7
Record Events that Modify the System's Discretionary Access Controls - fchmodat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchmodat | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83822-7 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fchownxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchown mediumCCE-83829-2
Record Events that Modify the System's Discretionary Access Controls - fchown
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchown | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83829-2 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fchownatxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchownat mediumCCE-83831-8
Record Events that Modify the System's Discretionary Access Controls - fchownat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fchownat | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83831-8 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fremovexattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fremovexattr mediumCCE-83821-9
Record Events that Modify the System's Discretionary Access Controls - fremovexattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fremovexattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83821-9 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fremovexattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - fsetxattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fsetxattr mediumCCE-83817-7
Record Events that Modify the System's Discretionary Access Controls - fsetxattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_fsetxattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83817-7 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S fsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S fsetxattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - lchownxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lchown mediumCCE-83833-4
Record Events that Modify the System's Discretionary Access Controls - lchown
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lchown | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83833-4 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - lremovexattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lremovexattr mediumCCE-83814-4
Record Events that Modify the System's Discretionary Access Controls - lremovexattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lremovexattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83814-4 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lremovexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lremovexattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - lsetxattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lsetxattr mediumCCE-83808-6
Record Events that Modify the System's Discretionary Access Controls - lsetxattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_lsetxattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83808-6 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S lsetxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S lsetxattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - removexattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_removexattr mediumCCE-83807-8
Record Events that Modify the System's Discretionary Access Controls - removexattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_removexattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83807-8 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following line to a file with suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod If the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - setxattrxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_setxattr mediumCCE-83811-0
Record Events that Modify the System's Discretionary Access Controls - setxattr
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_setxattr | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83811-0 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod -a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod | ||||||||||||||||||||||||||||||||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - umountxccdf_org.ssgproject.content_rule_audit_rules_dac_modification_umount mediumCCE-89272-9
Record Events that Modify the System's Discretionary Access Controls - umount
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_umount | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89272-9 | ||||||||
| References: |
| ||||||||
| Description | At a minimum, the audit system should collect file system umount
changes. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Events that Modify the System's Discretionary Access Controls - umount2xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_umount2 mediumCCE-88570-7
Record Events that Modify the System's Discretionary Access Controls - umount2
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_dac_modification_umount2 | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-88570-7 | ||||||||||
| References: |
| ||||||||||
| Description | At a minimum, the audit system should collect file system umount2
changes. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -F key=perm_mod | ||||||||||
| Rationale | The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users. | ||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Any Attempts to Run chaclxccdf_org.ssgproject.content_rule_audit_rules_execution_chacl mediumCCE-87685-4
Record Any Attempts to Run chacl
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_chacl | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-87685-4 | ||||||||||
| References: |
| ||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||
| Rationale | Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter). |
Record Any Attempts to Run setfaclxccdf_org.ssgproject.content_rule_audit_rules_execution_setfacl mediumCCE-90482-1
Record Any Attempts to Run setfacl
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_setfacl | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-90482-1 | ||||||||||||
| References: |
| ||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||
| Rationale | Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter). |
Record Any Attempts to Run chconxccdf_org.ssgproject.content_rule_audit_rules_execution_chcon mediumCCE-83748-4
Record Any Attempts to Run chcon
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_chcon | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83748-4 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Record Any Attempts to Run semanagexccdf_org.ssgproject.content_rule_audit_rules_execution_semanage mediumCCE-83750-0
Record Any Attempts to Run semanage
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_semanage | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83750-0 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Record Any Attempts to Run setfilesxccdf_org.ssgproject.content_rule_audit_rules_execution_setfiles mediumCCE-83736-9
Record Any Attempts to Run setfiles
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_setfiles | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83736-9 | ||||||||||||
| References: |
| ||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Record Any Attempts to Run setseboolxccdf_org.ssgproject.content_rule_audit_rules_execution_setsebool mediumCCE-83751-8
Record Any Attempts to Run setsebool
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_execution_setsebool | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83751-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects File Deletion Events by User - renamexccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rename mediumCCE-83754-2
Ensure auditd Collects File Deletion Events by User - rename
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rename | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83754-2 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S rename -F auid>=1000 -F auid!=unset -F key=delete | ||||||||||||||||||||||||||||||||||
| Rationale | Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence. |
Ensure auditd Collects File Deletion Events by User - renameatxccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_renameat mediumCCE-83756-7
Ensure auditd Collects File Deletion Events by User - renameat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_renameat | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83756-7 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S renameat -F auid>=1000 -F auid!=unset -F key=delete | ||||||||||||||||||||||||||||||||||
| Rationale | Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence. |
Ensure auditd Collects File Deletion Events by User - rmdirxccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rmdir mediumCCE-83758-3
Ensure auditd Collects File Deletion Events by User - rmdir
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_rmdir | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83758-3 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S rmdir -F auid>=1000 -F auid!=unset -F key=delete | ||||||||||||||||||||||||||||||||
| Rationale | Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence. |
Ensure auditd Collects File Deletion Events by User - unlinkxccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlink mediumCCE-83757-5
Ensure auditd Collects File Deletion Events by User - unlink
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlink | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83757-5 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S unlink -F auid>=1000 -F auid!=unset -F key=delete | ||||||||||||||||||||||||||||||||||
| Rationale | Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence. |
Ensure auditd Collects File Deletion Events by User - unlinkatxccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlinkat mediumCCE-83755-9
Ensure auditd Collects File Deletion Events by User - unlinkat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_file_deletion_events_unlinkat | ||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83755-9 | ||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 for 32-bit
system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete | ||||||||||||||||||||||||||||||||||
| Rationale | Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence. |
Record Unsuccessful Access Attempts to Files - creatxccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_creat mediumCCE-83786-4
Record Unsuccessful Access Attempts to Files - creat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_creat | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83786-4 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Unsuccessful Access Attempts to Files - ftruncatexccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_ftruncate mediumCCE-83800-3
Record Unsuccessful Access Attempts to Files - ftruncate
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_ftruncate | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83800-3 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Unsuccessful Access Attempts to Files - openxccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open mediumCCE-83801-1
Record Unsuccessful Access Attempts to Files - open
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83801-1 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Unsuccessful Access Attempts to Files - open_by_handle_atxccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open_by_handle_at mediumCCE-83796-3
Record Unsuccessful Access Attempts to Files - open_by_handle_at
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_open_by_handle_at | ||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||
| Identifiers: | CCE-83796-3 | ||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Unsuccessful Access Attempts to Files - openatxccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_openat mediumCCE-83794-8
Record Unsuccessful Access Attempts to Files - openat
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_openat | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83794-8 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Record Unsuccessful Access Attempts to Files - truncatexccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_truncate mediumCCE-83792-2
Record Unsuccessful Access Attempts to Files - truncate
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification_truncate | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83792-2 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=accessIf the system is 64 bit then also add the following lines: -a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access -a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access | ||||||||||||||||||||||||||||||||||||
| Rationale | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise. | ||||||||||||||||||||||||||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. Here the system calls
have been placed independent of other system calls. Grouping these system
calls with others as identifying earlier in this guide is more efficient. |
Ensure auditd Collects Information on Kernel Module Unloading - delete_modulexccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_delete mediumCCE-83802-9
Ensure auditd Collects Information on Kernel Module Unloading - delete_module
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_delete | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83802-9 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description |
To capture kernel module loading and unloading events, use the following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modulesPlace to add the line depends on a way auditd daemon is configured. If it is configured
to use the augenrules program (the default), add the line to a file with suffix
.rules in the directory /etc/audit/rules.d.
If the auditd daemon is configured to use the auditctl utility,
add the line to file /etc/audit/audit.rules. | ||||||||||||||||||||||||||||||||
| Rationale | The removal of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel. |
Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_modulexccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_finit mediumCCE-83803-7
Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_finit | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83803-7 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description |
To capture kernel module loading and unloading events, use the following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S finit_module -F auid>=1000 -F auid!=unset -F key=modulesPlace to add the line depends on a way auditd daemon is configured. If it is configured
to use the augenrules program (the default), add the line to a file with suffix
.rules in the directory /etc/audit/rules.d.
If the auditd daemon is configured to use the auditctl utility,
add the line to file /etc/audit/audit.rules. | ||||||||||||||||||||||||||||||||
| Rationale | The addition/removal of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel. |
Ensure auditd Collects Information on Kernel Module Loading - init_modulexccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_init mediumCCE-90835-0
Ensure auditd Collects Information on Kernel Module Loading - init_module
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_init | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90835-0 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description |
To capture kernel module loading and unloading events, use the following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:
-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modulesPlace to add the line depends on a way auditd daemon is configured. If it is configured
to use the augenrules program (the default), add the line to a file with suffix
.rules in the directory /etc/audit/rules.d.
If the auditd daemon is configured to use the auditctl utility,
add the line to file /etc/audit/audit.rules. | ||||||||||||||||||||||||||||||||
| Rationale | The addition of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel. |
Record Attempts to Alter Logon and Logout Events - faillockxccdf_org.ssgproject.content_rule_audit_rules_login_events_faillock mediumCCE-83783-1
Record Attempts to Alter Logon and Logout Events - faillock
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_login_events_faillock | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83783-1 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | The audit system already collects login information for all users
and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /var/log/faillock -p wa -k loginsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /var/log/faillock -p wa -k logins | ||||||||||||||||||||||||||||||||||||||||
| Rationale | Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion. |
Record Attempts to Alter Logon and Logout Events - lastlogxccdf_org.ssgproject.content_rule_audit_rules_login_events_lastlog mediumCCE-83785-6
Record Attempts to Alter Logon and Logout Events - lastlog
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_login_events_lastlog | ||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83785-6 | ||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||
| Description | The audit system already collects login information for all users
and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /var/log/lastlog -p wa -k loginsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /var/log/lastlog -p wa -k logins | ||||||||||||||||||||||||||||||||||||||||
| Rationale | Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion. |
Ensure auditd Collects Information on the Use of Privileged Commands - initxccdf_org.ssgproject.content_rule_audit_privileged_commands_init mediumCCE-85956-1
Ensure auditd Collects Information on the Use of Privileged Commands - init
| Rule ID | xccdf_org.ssgproject.content_rule_audit_privileged_commands_init | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-85956-1 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/init -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/init -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Misuse of the init command may cause availability issues for the system. |
Ensure auditd Collects Information on the Use of Privileged Commands - poweroffxccdf_org.ssgproject.content_rule_audit_privileged_commands_poweroff mediumCCE-85957-9
Ensure auditd Collects Information on the Use of Privileged Commands - poweroff
| Rule ID | xccdf_org.ssgproject.content_rule_audit_privileged_commands_poweroff | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-85957-9 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/poweroff -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/poweroff -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Misuse of the poweroff command may cause availability issues for the system. |
Ensure auditd Collects Information on the Use of Privileged Commands - rebootxccdf_org.ssgproject.content_rule_audit_privileged_commands_reboot mediumCCE-85958-7
Ensure auditd Collects Information on the Use of Privileged Commands - reboot
| Rule ID | xccdf_org.ssgproject.content_rule_audit_privileged_commands_reboot | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-85958-7 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/reboot -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/reboot -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Misuse of the reboot command may cause availability issues for the system. |
Ensure auditd Collects Information on the Use of Privileged Commands - shutdownxccdf_org.ssgproject.content_rule_audit_privileged_commands_shutdown mediumCCE-85959-5
Ensure auditd Collects Information on the Use of Privileged Commands - shutdown
| Rule ID | xccdf_org.ssgproject.content_rule_audit_privileged_commands_shutdown | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-85959-5 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/shutdown -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/shutdown -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Misuse of the shutdown command may cause availability issues for the system. |
Ensure auditd Collects Information on the Use of Privileged Commands - chagexccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chage mediumCCE-83765-8
Ensure auditd Collects Information on the Use of Privileged Commands - chage
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chage | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83765-8 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - chshxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chsh mediumCCE-83763-3
Ensure auditd Collects Information on the Use of Privileged Commands - chsh
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_chsh | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83763-3 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - crontabxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_crontab mediumCCE-83761-7
Ensure auditd Collects Information on the Use of Privileged Commands - crontab
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_crontab | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83761-7 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - gpasswdxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_gpasswd mediumCCE-83773-2
Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_gpasswd | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83773-2 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - kmodxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_kmod mediumCCE-90262-7
Ensure auditd Collects Information on the Use of Privileged Commands - kmod
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_kmod | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-90262-7 | ||||||||||||||
| References: |
| ||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||
| Rationale | Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter). |
Ensure auditd Collects Information on the Use of Privileged Commands - mountxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_mount mediumCCE-89564-9
Ensure auditd Collects Information on the Use of Privileged Commands - mount
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_mount | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-89564-9 | ||||||||||
| References: |
| ||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - newgrpxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_newgrp mediumCCE-83766-6
Ensure auditd Collects Information on the Use of Privileged Commands - newgrp
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_newgrp | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83766-6 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - passwdxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_passwd mediumCCE-83781-5
Ensure auditd Collects Information on the Use of Privileged Commands - passwd
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_passwd | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83781-5 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - postdropxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postdrop mediumCCE-83769-0
Ensure auditd Collects Information on the Use of Privileged Commands - postdrop
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postdrop | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83769-0 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - postqueuexccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postqueue mediumCCE-83770-8
Ensure auditd Collects Information on the Use of Privileged Commands - postqueue
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_postqueue | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83770-8 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Record Any Attempts to Run ssh-agentxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_agent mediumCCE-90388-0
Record Any Attempts to Run ssh-agent
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_agent | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90388-0 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter). |
Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysignxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_keysign mediumCCE-83776-5
Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysign
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_ssh_keysign | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83776-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - suxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_su mediumCCE-83771-6
Ensure auditd Collects Information on the Use of Privileged Commands - su
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_su | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83771-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - sudoxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_sudo mediumCCE-83780-7
Ensure auditd Collects Information on the Use of Privileged Commands - sudo
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_sudo | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83780-7 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - sudoeditxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_sudoedit mediumCCE-83764-1
Ensure auditd Collects Information on the Use of Privileged Commands - sudoedit
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_sudoedit | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83764-1 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - umountxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_umount mediumCCE-83762-5
Ensure auditd Collects Information on the Use of Privileged Commands - umount
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_umount | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83762-5 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwdxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_chkpwd mediumCCE-83768-2
Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_chkpwd | ||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||
| Identifiers: | CCE-83768-2 | ||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - unix_updatexccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_update mediumCCE-89481-6
Ensure auditd Collects Information on the Use of Privileged Commands - unix_update
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_unix_update | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89481-6 | ||||||||
| References: |
| ||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - userhelperxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_userhelper mediumCCE-83760-9
Ensure auditd Collects Information on the Use of Privileged Commands - userhelper
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_userhelper | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83760-9 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||||||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Information on the Use of Privileged Commands - usermodxccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_usermod mediumCCE-87212-7
Ensure auditd Collects Information on the Use of Privileged Commands - usermod
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands_usermod | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-87212-7 | ||||||||||||
| References: |
| ||||||||||||
| Description |
At a minimum, the audit system should collect the execution of privileged
commands for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add
a line of the following form to a file with suffix .rules
in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the
following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged | ||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.
Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity. |
Ensure auditd Collects Changes to Cron Jobs - /etc/cron.d/xccdf_org.ssgproject.content_rule_audit_rules_etc_cron_d mediumCCE-86613-7
Ensure auditd Collects Changes to Cron Jobs - /etc/cron.d/
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_etc_cron_d | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86613-7 | ||||||
| References: |
| ||||||
| Description | At a minimum, the audit system should collect administrator actions
for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/cron.d/ -p wa -k cronjobsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/cron.d/ -p wa -k cronjobs | ||||||
| Rationale | The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.
Editing the sudoers file may be sign of an attacker trying to
establish persistent methods to a system, auditing the editing of the sudoers
files mitigates this risk. |
Make the auditd Configuration Immutablexccdf_org.ssgproject.content_rule_audit_rules_immutable mediumCCE-83716-1
Make the auditd Configuration Immutable
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_immutable | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83716-1 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d in order to make the auditd configuration
immutable:
-e 2If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file in order to make the auditd configuration
immutable:
-e 2With this setting, a reboot will be required to change any audit rules. | ||||||||||||||||||||||||||||||||||||
| Rationale | Making the audit configuration immutable prevents accidental as
well as malicious modification of the audit rules, although it may be
problematic if legitimate changes are needed during system
operation. |
Ensure auditd Collects System Administrator Actions - /etc/sudoersxccdf_org.ssgproject.content_rule_audit_rules_sudoers mediumCCE-90176-9
Ensure auditd Collects System Administrator Actions - /etc/sudoers
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_sudoers | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-90176-9 | ||||||||
| References: |
| ||||||||
| Description | At a minimum, the audit system should collect administrator actions
for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/sudoers -p wa -k actionsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/sudoers -p wa -k actions | ||||||||
| Rationale | The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.
Editing the sudoers file may be sign of an attacker trying to
establish persistent methods to a system, auditing the editing of the sudoers
files mitigates this risk. |
Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/xccdf_org.ssgproject.content_rule_audit_rules_sudoers_d mediumCCE-89498-0
Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_sudoers_d | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-89498-0 | ||||||||
| References: |
| ||||||||
| Description | At a minimum, the audit system should collect administrator actions
for all users and root.
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/sudoers.d/ -p wa -k actionsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/sudoers.d/ -p wa -k actions | ||||||||
| Rationale | The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.
Editing the sudoers file may be sign of an attacker trying to
establish persistent methods to a system, auditing the editing of the sudoers
files mitigates this risk. |
Record Events When Privileged Executables Are Runxccdf_org.ssgproject.content_rule_audit_rules_suid_privilege_function mediumCCE-86402-5
Record Events When Privileged Executables Are Run
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_suid_privilege_function | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-86402-5 | ||||||||||||
| References: |
| ||||||||||||
| Description | Verify the system generates an audit record when privileged functions are executed.
If audit is using the "auditctl" tool to load the rules, run the following command:
$ sudo grep execve /etc/audit/audit.rulesIf audit is using the "augenrules" tool to load the rules, run the following command: $ sudo grep -r execve /etc/audit/rules.d -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgidIf both the "b32" and "b64" audit rules for "SUID" files are not defined, this is a finding. If both the "b32" and "b64" audit rules for "SGID" files are not defined, this is a finding. | ||||||||||||
| Rationale | Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have
compromised information system accounts, is a serious and ongoing concern
and can have significant adverse impacts on organizations. Auditing the use
of privileged functions is one way to detect such misuse and identify the
risk from insider threats and the advanced persistent threat. | ||||||||||||
| Warnings | warning
Note that these rules can be configured in a
number of ways while still achieving the desired effect. |
Shutdown System When Auditing Failures Occurxccdf_org.ssgproject.content_rule_audit_rules_system_shutdown mediumCCE-83709-6
Shutdown System When Auditing Failures Occur
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_system_shutdown | ||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||
| Identifiers: | CCE-83709-6 | ||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||
| Description | If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to to the bottom of a file with suffix
.rules in the directory /etc/audit/rules.d:
-f 2
If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to the
bottom of the /etc/audit/audit.rules file:
-f 2
| ||||||||||||||||||||||||
| Rationale | It is critical for the appropriate personnel to be aware if a system
is at risk of failing to process audit logs as required. Without this
notification, the security personnel may be unaware of an impending failure of
the audit capability, and system operation may be adversely affected.
Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. |
Record Events that Modify User/Group Information - /etc/groupxccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_group mediumCCE-83722-9
Record Events that Modify User/Group Information - /etc/group
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_group | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83722-9 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/group -p wa -k audit_rules_usergroup_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/group -p wa -k audit_rules_usergroup_modification | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
Record Events that Modify User/Group Information - /etc/gshadowxccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_gshadow mediumCCE-83723-7
Record Events that Modify User/Group Information - /etc/gshadow
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_gshadow | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83723-7 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/gshadow -p wa -k audit_rules_usergroup_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
Record Events that Modify User/Group Information - /etc/security/opasswdxccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_opasswd mediumCCE-83712-0
Record Events that Modify User/Group Information - /etc/security/opasswd
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_opasswd | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83712-0 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
Record Events that Modify User/Group Information - /etc/passwdxccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_passwd mediumCCE-83714-6
Record Events that Modify User/Group Information - /etc/passwd
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_passwd | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83714-6 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/passwd -p wa -k audit_rules_usergroup_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/passwd -p wa -k audit_rules_usergroup_modification | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
Record Events that Modify User/Group Information - /etc/shadowxccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_shadow mediumCCE-83725-2
Record Events that Modify User/Group Information - /etc/shadow
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_usergroup_modification_shadow | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83725-2 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /etc/shadow -p wa -k audit_rules_usergroup_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /etc/shadow -p wa -k audit_rules_usergroup_modification | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
Ensure auditd Collects Changes to Cron Jobs - /var/spool/cronxccdf_org.ssgproject.content_rule_audit_rules_var_spool_cron mediumCCE-86636-8
Ensure auditd Collects Changes to Cron Jobs - /var/spool/cron
| Rule ID | xccdf_org.ssgproject.content_rule_audit_rules_var_spool_cron | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-86636-8 | ||||||
| References: |
| ||||||
| Description |
If the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add the
following lines to a file with suffix .rules in the
directory /etc/audit/rules.d:
-w /var/spool/cron -p wa -k cronjobsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules:
-w /var/spool/cron -p wa -k cronjobs | ||||||
| Rationale | In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy. |
System Audit Directories Must Be Group Owned By Rootxccdf_org.ssgproject.content_rule_directory_group_ownership_var_log_audit mediumCCE-90516-6
System Audit Directories Must Be Group Owned By Root
| Rule ID | xccdf_org.ssgproject.content_rule_directory_group_ownership_var_log_audit | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-90516-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | All audit directories must be group owned by root user. By default, the path for audit log is /var/log/audit/. To properly set the group owner of /var/log/audit, run the command:
$ sudo chgrp root /var/log/auditIf log_group in /etc/audit/auditd.conf is set to a group other than the root
group account, change the group ownership of the audit directories to this specific group. | ||||||||||||||||||||||||||
| Rationale | Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality. |
System Audit Directories Must Be Owned By Rootxccdf_org.ssgproject.content_rule_directory_ownership_var_log_audit mediumCCE-85869-6
System Audit Directories Must Be Owned By Root
| Rule ID | xccdf_org.ssgproject.content_rule_directory_ownership_var_log_audit | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-85869-6 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | All audit directories must be owned by root user. By default, the path for audit log is /var/log/audit/. To properly set the owner of /var/log/audit, run the command:
$ sudo chown root /var/log/audit | ||||||||||||||||||||||||||
| Rationale | Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality. |
Audit Configuration Files Must Be Owned By Group rootxccdf_org.ssgproject.content_rule_file_groupownership_audit_configuration mediumCCE-86446-2
Audit Configuration Files Must Be Owned By Group root
| Rule ID | xccdf_org.ssgproject.content_rule_file_groupownership_audit_configuration | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-86446-2 | ||||||||||||
| References: |
| ||||||||||||
| Description | All audit configuration files must be owned by group root.
chown :root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*
| ||||||||||||
| Rationale | Without the capability to restrict which roles and individuals can
select which events are audited, unauthorized personnel may be able
to prevent the auditing of critical events.
Misconfigured audits may degrade the system's performance by
overwhelming the audit log. Misconfigured audits may also make it more
difficult to establish, correlate, and investigate the events relating
to an incident or identify those responsible for one. |
Audit Configuration Files Must Be Owned By Rootxccdf_org.ssgproject.content_rule_file_ownership_audit_configuration mediumCCE-86445-4
Audit Configuration Files Must Be Owned By Root
| Rule ID | xccdf_org.ssgproject.content_rule_file_ownership_audit_configuration | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-86445-4 | ||||||||||||
| References: |
| ||||||||||||
| Description | All audit configuration files must be owned by root user.
To properly set the owner of /etc/audit/, run the command:
$ sudo chown root /etc/audit/To properly set the owner of /etc/audit/rules.d/, run the command:
$ sudo chown root /etc/audit/rules.d/ | ||||||||||||
| Rationale | Without the capability to restrict which roles and individuals can
select which events are audited, unauthorized personnel may be able
to prevent the auditing of critical events.
Misconfigured audits may degrade the system's performance by
overwhelming the audit log. Misconfigured audits may also make it more
difficult to establish, correlate, and investigate the events relating
to an incident or identify those responsible for one. |
Configure a Sufficiently Large Partition for Audit Logsxccdf_org.ssgproject.content_rule_auditd_audispd_configure_sufficiently_large_partition mediumCCE-88173-0
Configure a Sufficiently Large Partition for Audit Logs
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_audispd_configure_sufficiently_large_partition | ||||||
| Result | notapplicable | ||||||
| Multi-check rule | no | ||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||
| Severity | medium | ||||||
| Identifiers: | CCE-88173-0 | ||||||
| References: |
| ||||||
| Description | The Red Hat Enterprise Linux 9 operating system must allocate audit record storage
capacity to store at least one weeks worth of audit records when audit
records are not immediately sent to a central audit record storage
facility.
The partition size needed to capture a week's worth of audit records is
based on the activity level of the system and the total storage capacity
available.
In normal circumstances, 10.0 GB of storage space for audit
records will be sufficient.
Determine which partition the audit records are being written to with the
following command:
$ sudo grep log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.logCheck the size of the partition that audit records are written to with the following command: $ sudo df -h /var/log/audit/ /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit | ||||||
| Rationale | Information stored in one location is vulnerable to accidental or incidental
deletion or alteration. Off-loading is a common process in information
systems with limited audit storage capacity. |
Configure auditd Disk Error Action on Disk Errorxccdf_org.ssgproject.content_rule_auditd_data_disk_error_action_stig mediumCCE-88303-3
Configure auditd Disk Error Action on Disk Error
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_disk_error_action_stig | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-88303-3 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when there is a disk error.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting ACTION appropriately:
disk_error_action = ACTION
Set this value to single to cause the system to switch to single-user
mode for corrective action. Acceptable values also include syslog,
exec, single, and halt. For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page. | ||||||||||||||||||||
| Rationale | Taking appropriate action in case of disk errors will minimize the possibility of
losing audit records. |
Configure auditd Disk Full Action when Disk Space Is Fullxccdf_org.ssgproject.content_rule_auditd_data_disk_full_action_stig mediumCCE-88336-3
Configure auditd Disk Full Action when Disk Space Is Full
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_disk_full_action_stig | ||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||
| Identifiers: | CCE-88336-3 | ||||||||||||||||||||
| References: |
| ||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting ACTION appropriately:
disk_full_action = ACTION
Set this value to single to cause the system to switch to single-user
mode for corrective action. Acceptable values also include syslog,
single, and halt. For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page. | ||||||||||||||||||||
| Rationale | Taking appropriate action in case of a filled audit storage volume will minimize
the possibility of losing audit records. |
Configure auditd mail_acct Action on Low Disk Spacexccdf_org.ssgproject.content_rule_auditd_data_retention_action_mail_acct mediumCCE-83698-1
Configure auditd mail_acct Action on Low Disk Space
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_action_mail_acct | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83698-1 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The auditd service can be configured to send email to
a designated account in certain situations. Add or correct the following line
in /etc/audit/auditd.conf to ensure that administrators are notified
via email for those situations:
action_mail_acct = root
| ||||||||||||||||||||||||||||||||
| Rationale | Email sent to the root account is typically aliased to the
administrators of the system, who can take appropriate action. |
Configure auditd admin_space_left Action on Low Disk Spacexccdf_org.ssgproject.content_rule_auditd_data_retention_admin_space_left_action mediumCCE-83700-5
Configure auditd admin_space_left Action on Low Disk Space
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_admin_space_left_action | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83700-5 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting ACTION appropriately:
admin_space_left_action = ACTION
Set this value to single to cause the system to switch to single user
mode for corrective action. Acceptable values also include suspend and
halt. For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page. | ||||||||||||||||||||||||||||||||
| Rationale | Administrators should be made aware of an inability to record
audit records. If a separate partition or logical volume of adequate size
is used, running low on space for audit records should never occur. |
Configure auditd admin_space_left on Low Disk Spacexccdf_org.ssgproject.content_rule_auditd_data_retention_admin_space_left_percentage mediumCCE-88816-4
Configure auditd admin_space_left on Low Disk Space
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_admin_space_left_percentage | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-88816-4 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting PERCENTAGE appropriately:
admin_space_left = PERCENTAGE%Set this value to 5 to cause the system to perform an action. | ||||||||||||||||||||||
| Rationale | Notifying administrators of an impending disk space problem may allow them to
take corrective action prior to any disruption. |
Configure auditd max_log_file_action Upon Reaching Maximum Log Sizexccdf_org.ssgproject.content_rule_auditd_data_retention_max_log_file_action_stig mediumCCE-88396-7
Configure auditd max_log_file_action Upon Reaching Maximum Log Size
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_max_log_file_action_stig | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-88396-7 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The default action to take when the logs reach their maximum size
is to rotate the log files, discarding the oldest one. To configure the action taken
by auditd, add or correct the line in /etc/audit/auditd.conf:
max_log_file_action = ACTION
Possible values for ACTION are described in the auditd.conf man
page. These include:
ACTION to rotate to ensure log rotation
occurs. This is the default. The setting is case-insensitive. | ||||||||||||||||||||||||||
| Rationale | Automatically rotating logs (by setting this to rotate)
minimizes the chances of the system unexpectedly running out of disk space by
being overwhelmed with log data. However, for systems that must never discard
log data, or which use external processes to transfer it and reclaim space,
keep_logs can be employed. |
Configure auditd space_left Action on Low Disk Spacexccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_action mediumCCE-83703-9
Configure auditd space_left Action on Low Disk Space
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_action | ||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83703-9 | ||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when disk space starts to run low.
Edit the file /etc/audit/auditd.conf. Modify the following line,
substituting ACTION appropriately:
space_left_action = ACTION
Possible values for ACTION are described in the auditd.conf man page.
These include:
email (instead of the default,
which is suspend) as it is more likely to get prompt attention. Acceptable values
also include suspend, single, and halt. | ||||||||||||||||||||||||||||||||
| Rationale | Notifying administrators of an impending disk space problem may
allow them to take corrective action prior to any disruption. |
Configure auditd space_left on Low Disk Spacexccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_percentage mediumCCE-87746-4
Configure auditd space_left on Low Disk Space
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_percentage | ||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||
| Identifiers: | CCE-87746-4 | ||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||
| Description | The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting PERCENTAGE appropriately:
space_left = PERCENTAGE%Set this value to at least 25 to cause the system to notify the user of an issue. | ||||||||||||||||||||||
| Rationale | Notifying administrators of an impending disk space problem may allow them to
take corrective action prior to any disruption. |
Set number of records to cause an explicit flush to audit logsxccdf_org.ssgproject.content_rule_auditd_freq mediumCCE-83704-7
Set number of records to cause an explicit flush to audit logs
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_freq | ||||||||||||
| Result | notapplicable | ||||||||||||
| Multi-check rule | no | ||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||
| Severity | medium | ||||||||||||
| Identifiers: | CCE-83704-7 | ||||||||||||
| References: |
| ||||||||||||
| Description | To configure Audit daemon to issue an explicit flush to disk command
after writing 100 records, set freq to 100
in /etc/audit/auditd.conf. | ||||||||||||
| Rationale | If option freq isn't set to 100, the flush to disk
may happen after higher number of records, increasing the danger
of audit loss. |
Include Local Events in Audit Logsxccdf_org.ssgproject.content_rule_auditd_local_events mediumCCE-83682-5
Include Local Events in Audit Logs
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_local_events | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83682-5 | ||||||||||
| References: |
| ||||||||||
| Description | To configure Audit daemon to include local events in Audit logs, set
local_events to yes in /etc/audit/auditd.conf.
This is the default setting. | ||||||||||
| Rationale | If option local_events isn't set to yes only events from
network will be aggregated. |
Resolve information before writing to audit logsxccdf_org.ssgproject.content_rule_auditd_log_format lowCCE-83696-5
Resolve information before writing to audit logs
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_log_format | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | low | ||||||||||||||
| Identifiers: | CCE-83696-5 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To configure Audit daemon to resolve all uid, gid, syscall,
architecture, and socket address information before writing the
events to disk, set log_format to ENRICHED
in /etc/audit/auditd.conf. | ||||||||||||||
| Rationale | If option log_format isn't set to ENRICHED, the
audit records will be stored in a format exactly as the kernel sends them. |
Set type of computer node name logging in audit logsxccdf_org.ssgproject.content_rule_auditd_name_format mediumCCE-83686-6
Set type of computer node name logging in audit logs
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_name_format | ||||||||||||||
| Result | notapplicable | ||||||||||||||
| Multi-check rule | no | ||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||
| Severity | medium | ||||||||||||||
| Identifiers: | CCE-83686-6 | ||||||||||||||
| References: |
| ||||||||||||||
| Description | To configure Audit daemon to use a unique identifier
as computer node name in the audit events,
set name_format to hostname|fqd|numeric
in /etc/audit/auditd.conf. | ||||||||||||||
| Rationale | If option name_format is left at its default value of
none, audit events from different computers may be hard
to distinguish. | ||||||||||||||
| Warnings | warning
Whenever the variable var_auditd_name_formatuses a multiple value option, for example A|B|C, the first value will be used when remediating this rule. |
Appropriate Action Must be Setup When the Internal Audit Event Queue is Fullxccdf_org.ssgproject.content_rule_auditd_overflow_action mediumCCE-87901-5
Appropriate Action Must be Setup When the Internal Audit Event Queue is Full
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_overflow_action | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-87901-5 | ||||||||
| References: |
| ||||||||
| Description | The audit system should have an action setup in the event the internal event queue becomes full.
To setup an overflow action edit /etc/audit/auditd.conf. Set overflow_action
to one of the following values: syslog, single, halt. | ||||||||
| Rationale | The audit system should have an action setup in the event the internal event queue becomes full
so that no data is lost. |
Write Audit Logs to the Diskxccdf_org.ssgproject.content_rule_auditd_write_logs mediumCCE-83705-4
Write Audit Logs to the Disk
| Rule ID | xccdf_org.ssgproject.content_rule_auditd_write_logs | ||||||||||
| Result | notapplicable | ||||||||||
| Multi-check rule | no | ||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||
| Severity | medium | ||||||||||
| Identifiers: | CCE-83705-4 | ||||||||||
| References: |
| ||||||||||
| Description | To configure Audit daemon to write Audit logs to the disk, set
write_logs to yes in /etc/audit/auditd.conf.
This is the default setting. | ||||||||||
| Rationale | If write_logs isn't set to yes, the Audit logs will
not be written to the disk. |
Install audispd-plugins Packagexccdf_org.ssgproject.content_rule_package_audispd-plugins_installed mediumCCE-83648-6
Install audispd-plugins Package
| Rule ID | xccdf_org.ssgproject.content_rule_package_audispd-plugins_installed | ||||||||
| Result | notapplicable | ||||||||
| Multi-check rule | no | ||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||
| Severity | medium | ||||||||
| Identifiers: | CCE-83648-6 | ||||||||
| References: |
| ||||||||
| Description | The audispd-plugins package can be installed with the following command:
$ sudo dnf install audispd-plugins | ||||||||
| Rationale | audispd-plugins provides plugins for the real-time interface to the
audit subsystem, audispd. These plugins can do things like relay events
to remote machines or analyze events for suspicious behavior. |
Ensure the audit Subsystem is Installedxccdf_org.ssgproject.content_rule_package_audit_installed mediumCCE-83649-4
Ensure the audit Subsystem is Installed
| Rule ID | xccdf_org.ssgproject.content_rule_package_audit_installed | ||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||
| Identifiers: | CCE-83649-4 | ||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||
| Description | The audit package should be installed. | ||||||||||||||||||||||||||
| Rationale | The auditd service is an access monitoring and accounting daemon, watching system calls to audit any access, in comparison with potential local access control policy such as SELinux policy. |
Enable auditd Servicexccdf_org.ssgproject.content_rule_service_auditd_enabled mediumCCE-90829-3
Enable auditd Service
| Rule ID | xccdf_org.ssgproject.content_rule_service_auditd_enabled | ||||||||||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||||||||||
| Severity | medium | ||||||||||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-90829-3 | ||||||||||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||||||||||
| Description | The auditd service is an essential userspace component of
the Linux Auditing System, as it is responsible for writing audit records to
disk.
The auditd service can be enabled with the following command:
$ sudo systemctl enable auditd.service | ||||||||||||||||||||||||||||||||||||||||||||
| Rationale | Without establishing what type of events occurred, it would be difficult
to establish, correlate, and investigate the events leading up to an outage or attack.
Ensuring the auditd service is active ensures audit records
generated by the kernel are appropriately recorded.
Additionally, a properly configured audit subsystem ensures that actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. |
Enable Auditing for Processes Which Start Prior to the Audit Daemonxccdf_org.ssgproject.content_rule_grub2_audit_argument lowCCE-83651-0
Enable Auditing for Processes Which Start Prior to the Audit Daemon
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_audit_argument | ||||||||||||||||||||||||||||||||||||
| Result | notapplicable | ||||||||||||||||||||||||||||||||||||
| Multi-check rule | no | ||||||||||||||||||||||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||||||||||||||||||||||
| Severity | low | ||||||||||||||||||||||||||||||||||||
| Identifiers: | CCE-83651-0 | ||||||||||||||||||||||||||||||||||||
| References: |
| ||||||||||||||||||||||||||||||||||||
| Description | To ensure all processes can be audited, even those which start
prior to the audit daemon, add the argument audit=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit=1 is added as a kernel command line
argument to newly installed kernels, add audit=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit=1 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="audit=1"If the system is distributed as a bootable container image, GRUB2 can't be configured using the method described above, but the following method needs to be used instead. The kernel arguments should be set in /usr/lib/bootc/kargs.d in a TOML file that has the following form:
# /usr/lib/bootc/kargs.d/10-example.toml kargs = ["audit=1"]For more details on configuring kernel arguments in bootable container images, please refer to Bootc documentation. | ||||||||||||||||||||||||||||||||||||
| Rationale | Each process on the system carries an "auditable" flag which indicates whether
its activities can be audited. Although auditd takes care of enabling
this for all processes which launch after it does, adding the kernel argument
ensures it is set for every process during boot. |
Extend Audit Backlog Limit for the Audit Daemonxccdf_org.ssgproject.content_rule_grub2_audit_backlog_limit_argument lowCCE-83652-8
Extend Audit Backlog Limit for the Audit Daemon
| Rule ID | xccdf_org.ssgproject.content_rule_grub2_audit_backlog_limit_argument | ||||||||||||||||
| Result | notapplicable | ||||||||||||||||
| Multi-check rule | no | ||||||||||||||||
| Time | 2026-06-11T16:45:09+00:00 | ||||||||||||||||
| Severity | low | ||||||||||||||||
| Identifiers: | CCE-83652-8 | ||||||||||||||||
| References: |
| ||||||||||||||||
| Description | To improve the kernel capacity to queue all log events, even those which occurred
prior to the audit daemon, add the argument audit_backlog_limit=8192
to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit_backlog_limit=8192
is added as a kernel command line
argument to newly installed kernels, add audit_backlog_limit=8192
to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."Run the following command to update command line for already installed kernels: # grubby --update-kernel=ALL --args="audit_backlog_limit=8192"If the system is distributed as a bootable container image, GRUB2 can't be configured using the method described above, but the following method needs to be used instead. The kernel arguments should be set in /usr/lib/bootc/kargs.d in a TOML file that has the following form:
# /usr/lib/bootc/kargs.d/10-example.toml kargs = ["audit_backlog_limit=8192"]For more details on configuring kernel arguments in bootable container images, please refer to Bootc documentation. | ||||||||||||||||
| Rationale | audit_backlog_limit sets the queue length for audit events awaiting transfer
to the audit daemon. Until the audit daemon is up and running, all log messages
are stored in this queue. If the queue is overrun during boot process, the action
defined by audit failure flag is taken. |
Red Hat and Red Hat Enterprise Linux are either registered
trademarks or trademarks of Red Hat, Inc. in the United States and other
countries. All other names are registered trademarks or trademarks of their
respective companies.