From c171f5d9ddb12b8dc762f92535b24a1d70367e88 Mon Sep 17 00:00:00 2001 From: Marcus Burghardt Date: Tue, 13 Feb 2024 13:11:57 +0100 Subject: [PATCH] Rebase to new upstream version 0.1.72 Resolves: RHEL-21425 Resolves: RHEL-14484 Resolves: RHEL-1484 Resolves: RHEL-17417 Resolves: RHEL-1489 Resolves: RHEL-16801 Resolves: RHEL-17418 --- .gitignore | 1 + ...add_package_smail_installed-PR_11144.patch | 91 - ...0.1.70-fix_enable_fips_mode-PR_10961.patch | 52 - ...eadability_enable_fips_mode-PR_10911.patch | 272 - ...0.1.70-name_format_variable-PR_11019.patch | 263 - ...move_openssh_hardening_stig-PR_10996.patch | 21 - ...ve_secure_mode_insmod_anssi-PR_11001.patch | 30 - ...-sshd_approved_ciphers_stig-PR_10966.patch | 104 - ....1.70-update_ssh_stig_algos-PR_10920.patch | 212 - ...-0.1.71-add_cron_deny_rules-PR_11185.patch | 158 - ...guide-0.1.71-add_rhel9_stig-PR_11193.patch | 18124 ---------------- ...srg_to_file_owner_grub2_cfg-PR_11261.patch | 26 - ...manager_dns_mode_rhel9_stig-PR_11242.patch | 26 - ...0.1.71-new_rule_dns_mode_nm-PR_11160.patch | 294 - ...uide-0.1.72-remove_stig_ids-PR_11327.patch | 67 - scap-security-guide.spec | 40 +- sources | 2 +- 17 files changed, 13 insertions(+), 19770 deletions(-) delete mode 100644 scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch delete mode 100644 scap-security-guide-0.1.70-fix_enable_fips_mode-PR_10961.patch delete mode 100644 scap-security-guide-0.1.70-improve_readability_enable_fips_mode-PR_10911.patch delete mode 100644 scap-security-guide-0.1.70-name_format_variable-PR_11019.patch delete mode 100644 scap-security-guide-0.1.70-remove_openssh_hardening_stig-PR_10996.patch delete mode 100644 scap-security-guide-0.1.70-remove_secure_mode_insmod_anssi-PR_11001.patch delete mode 100644 scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch delete mode 100644 scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch delete mode 100644 scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch delete mode 100644 scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch delete mode 100644 scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch delete mode 100644 scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch delete mode 100644 scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch delete mode 100644 scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch diff --git a/.gitignore b/.gitignore index ccc1903..8904f76 100644 --- a/.gitignore +++ b/.gitignore @@ -47,3 +47,4 @@ /scap-security-guide-0.1.63.tar.bz2 /scap-security-guide-0.1.66.tar.bz2 /scap-security-guide-0.1.69.tar.bz2 +/scap-security-guide-0.1.72.tar.bz2 diff --git a/scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch b/scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch deleted file mode 100644 index 81b2a80..0000000 --- a/scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch +++ /dev/null @@ -1,91 +0,0 @@ -From d98cffdc7ebd3c266e71ead933d401188ef0d66a Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:05:37 +0100 -Subject: [PATCH 07/14] Add rule `package_s-nail-installed` - -Patch-name: scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch -Patch-status: Add rule `package_s-nail-installed` ---- - components/s-nail.yml | 5 +++ - .../srg_gpos/SRG-OS-000363-GPOS-00150.yml | 1 + - .../mail/package_s-nail_installed/rule.yml | 33 +++++++++++++++++++ - shared/references/cce-redhat-avail.txt | 1 - - 4 files changed, 39 insertions(+), 1 deletion(-) - create mode 100644 components/s-nail.yml - create mode 100644 linux_os/guide/services/mail/package_s-nail_installed/rule.yml - -diff --git a/components/s-nail.yml b/components/s-nail.yml -new file mode 100644 -index 0000000000..d93f8c52dc ---- /dev/null -+++ b/components/s-nail.yml -@@ -0,0 +1,5 @@ -+name: s-nail -+packages: -+- s-nail -+rules: -+- package_s-nail_installed -diff --git a/controls/srg_gpos/SRG-OS-000363-GPOS-00150.yml b/controls/srg_gpos/SRG-OS-000363-GPOS-00150.yml -index 3ffba82f03..05a10a2304 100644 ---- a/controls/srg_gpos/SRG-OS-000363-GPOS-00150.yml -+++ b/controls/srg_gpos/SRG-OS-000363-GPOS-00150.yml -@@ -7,4 +7,5 @@ controls: - rules: - - aide_periodic_cron_checking - - package_aide_installed -+ - package_s-nail_installed - status: automated -diff --git a/linux_os/guide/services/mail/package_s-nail_installed/rule.yml b/linux_os/guide/services/mail/package_s-nail_installed/rule.yml -new file mode 100644 -index 0000000000..e14fbc9f35 ---- /dev/null -+++ b/linux_os/guide/services/mail/package_s-nail_installed/rule.yml -@@ -0,0 +1,33 @@ -+documentation_complete: true -+ -+prodtype: rhel9 -+ -+title: 'The s-nail Package Is Installed' -+ -+description: |- -+ A mail server is required for sending emails. -+ {{{ describe_package_install(package="s-nail") }}} -+ -+rationale: |- -+ Emails can be used to notify designated personnel about important -+ system events such as failures or warnings. -+ -+severity: medium -+ -+identifiers: -+ cce@rhel9: CCE-86608-7 -+ -+references: -+ disa: CCI-001744 -+ nist: CM-3(5) -+ srg: SRG-OS-000363-GPOS-00150 -+ -+ocil_clause: 'the package is not installed' -+ -+ocil: '{{{ ocil_package(package="s-nail") }}}' -+ -+template: -+ name: package_installed -+ vars: -+ pkgname: s-nail -+ -diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt -index ef6afd3fbe..538d9d488d 100644 ---- a/shared/references/cce-redhat-avail.txt -+++ b/shared/references/cce-redhat-avail.txt -@@ -315,7 +315,6 @@ CCE-86604-6 - CCE-86605-3 - CCE-86606-1 - CCE-86607-9 --CCE-86608-7 - CCE-86609-5 - CCE-86610-3 - CCE-86612-9 --- -2.43.0 - diff --git a/scap-security-guide-0.1.70-fix_enable_fips_mode-PR_10961.patch b/scap-security-guide-0.1.70-fix_enable_fips_mode-PR_10961.patch deleted file mode 100644 index af7d37e..0000000 --- a/scap-security-guide-0.1.70-fix_enable_fips_mode-PR_10961.patch +++ /dev/null @@ -1,52 +0,0 @@ -From 75dd0e76be957e5fd92c98f01f7d672b2549fd3d Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 8 Aug 2023 15:15:21 +0200 -Subject: [PATCH] Remove kernel cmdline check - -The OVAL in rule enable_fips_mode contains multiple checks. One -of these checks tests presence of `fips=1` in `/etc/kernel/cmdline`. -Although this is useful for latest RHEL versions, this file doesn't -exist on RHEL 8.6 and 9.0. This causes that the rule fails after -remediation on these RHEL versions. - -We want the same OVAL behavior on all minor RHEL releases, therefore -we will remove this test from the OVAL completely. - -Related to: https://github.com/ComplianceAsCode/content/pull/10897 ---- - .../fips/enable_fips_mode/oval/shared.xml | 15 --------------- - 1 file changed, 15 deletions(-) - -diff --git a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -index 88aae7aaab9..3b50e07060e 100644 ---- a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -+++ b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -@@ -12,8 +12,6 @@ - comment="system cryptography policy is configured"/> - -- - {{% if "ol" in product or "rhel" in product %}} - - -@@ -57,19 +55,6 @@ - ^(?:.*\s)?fips=1(?:\s.*)?$ - - -- -- -- -- -- -- -- ^/etc/kernel/cmdline -- ^(.*)$ -- 1 -- -- - - diff --git a/scap-security-guide-0.1.70-improve_readability_enable_fips_mode-PR_10911.patch b/scap-security-guide-0.1.70-improve_readability_enable_fips_mode-PR_10911.patch deleted file mode 100644 index fbc06d7..0000000 --- a/scap-security-guide-0.1.70-improve_readability_enable_fips_mode-PR_10911.patch +++ /dev/null @@ -1,272 +0,0 @@ -From 9d00e0d296ad4a5ce503b2dfe9647de6806b7b60 Mon Sep 17 00:00:00 2001 -From: Marcus Burghardt -Date: Thu, 27 Jul 2023 10:02:08 +0200 -Subject: [PATCH 1/2] Align the parameters ordering in OVAL objects - -This commit only improves readability without any technical impact in -the OVAL logic. ---- - .../fips/enable_fips_mode/oval/shared.xml | 81 ++++++++++++------- - 1 file changed, 50 insertions(+), 31 deletions(-) - -diff --git a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -index fe3f96f52a5..0ec076a5fb7 100644 ---- a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -+++ b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -@@ -1,32 +1,38 @@ - -- -+ - {{{ oval_metadata("Check if FIPS mode is enabled on the system") }}} - -- -- -- -- -- -- -+ -+ -+ -+ -+ -+ - {{% if "ol" in product or "rhel" in product %}} - - -- -- -+ -+ - - - -- -+ - - {{% if product in ["ol8", "rhel8"] %}} -- -+ - {{% else %}} -- -+ - {{% endif %}} - - -@@ -34,58 +40,71 @@ - - - -- -+ - - - -+ - - ^/boot/loader/entries/.*.conf - ^options (.*)$ - 1 - -+ - - ^(?:.*\s)?fips=1(?:\s.*)?$ - -- -+ -+ - - - -+ - - ^/etc/kernel/cmdline - ^(.*)$ - 1 - - -- -+ - - - -+ - - var_system_crypto_policy - -- -+ -+ - {{% if product in ["ol9","rhel9"] -%}} - ^FIPS(:OSPP)?$ - {{%- else %}} -- {{# Legacy and more relaxed list of crypto policies that were historically considered FIPS-compatible. More recent products should use the more restricted list of options #}} -+ {{# Legacy and more relaxed list of crypto policies that were historically considered -+ FIPS-compatible. More recent products should use the more restricted list of options #}} - ^FIPS(:(OSPP|NO-SHA1|NO-CAMELLIA))?$ - {{%- endif %}} - -+ - {{% if product in ["ol8","rhel8"] %}} -- -+ - - -- -+ -+ - /boot/grub2/grubenv - fips=1 - 1 - - {{% endif %}} -- -+ -+ - - -From 6a62a2f1b61e51326c7cadd2a0494200d98cc02e Mon Sep 17 00:00:00 2001 -From: Marcus Burghardt -Date: Thu, 27 Jul 2023 10:20:33 +0200 -Subject: [PATCH 2/2] Improve OVAL comments for better readability - -Simplified the comments and aligned the respective lines to the -project Style Guides. ---- - .../fips/enable_fips_mode/oval/shared.xml | 31 ++++++++++--------- - 1 file changed, 16 insertions(+), 15 deletions(-) - -diff --git a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -index 0ec076a5fb7..88aae7aaab9 100644 ---- a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -+++ b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/oval/shared.xml -@@ -3,36 +3,36 @@ - {{{ oval_metadata("Check if FIPS mode is enabled on the system") }}} - - -+ comment="check /etc/system-fips file existence"/> - -+ comment="check option crypto.fips_enabled = 1 in sysctl"/> - -+ comment="dracut FIPS module is enabled"/> - - -+ comment="check if var_system_crypto_policy variable selection is set to FIPS"/> - -+ comment="check if kernel option fips=1 is present in /etc/kernel/cmdline"/> - {{% if "ol" in product or "rhel" in product %}} - - - -+ comment="generic test for s390x architecture"/> - -+ comment="check if kernel option fips=1 is present in /boot/loader/entries/.*.conf"/> - - - - -+ comment="generic test for non-s390x architecture"/> - - {{% if product in ["ol8", "rhel8"] %}} - - {{% else %}} - -+ comment="check if kernel option fips=1 is present in /boot/loader/entries/.*.conf"/> - {{% endif %}} - - -@@ -42,7 +42,7 @@ - - -+ comment="check if kernel option fips=1 is present in options in /boot/loader/entries/.*.conf"> - - - -@@ -59,7 +59,7 @@ - - -+ comment="check if kernel option fips=1 is present in /etc/kernel/cmdline"> - - - -@@ -71,7 +71,7 @@ - - - -+ check="at least one" comment="test if var_system_crypto_policy selection is set to FIPS"> - - - -@@ -81,7 +81,8 @@ - - - -+ comment="variable value is set to 'FIPS' or 'FIPS:modifier', where the modifier corresponds -+to a crypto policy module that further restricts the modified crypto policy."> - {{% if product in ["ol9","rhel9"] -%}} - ^FIPS(:OSPP)?$ - {{%- else %}} -@@ -94,7 +95,7 @@ - {{% if product in ["ol8","rhel8"] %}} - -+ comment="FIPS mode is selected in running kernel options"> - - - -@@ -106,5 +107,5 @@ - {{% endif %}} - - -+ datatype="string" comment="variable which selects the crypto policy"/> - diff --git a/scap-security-guide-0.1.70-name_format_variable-PR_11019.patch b/scap-security-guide-0.1.70-name_format_variable-PR_11019.patch deleted file mode 100644 index e3370e0..0000000 --- a/scap-security-guide-0.1.70-name_format_variable-PR_11019.patch +++ /dev/null @@ -1,263 +0,0 @@ -From 09b4ceaba513e23ee933349f8a89b9c9b7dc1c26 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Wed, 6 Dec 2023 10:02:00 +0100 -Subject: [PATCH 14/14] Add variable support to `auditd_name_format` rule - -Patch-name: scap-security-guide-0.1.70-name_format_variable-PR_11019.patch -Patch-status: Add variable support to `auditd_name_format` rule ---- - controls/srg_gpos.yml | 1 + - .../auditd_name_format/ansible/shared.yml | 7 +- - .../auditd_name_format/bash/shared.sh | 7 +- - .../auditd_name_format/oval/shared.xml | 49 ++++- - .../auditd_name_format/rule.yml | 23 ++- - .../var_auditd_flush.var | 2 +- - .../var_auditd_name_format.var | 18 ++ - products/rhel7/profiles/stig.profile | 1 + - products/rhel8/profiles/stig.profile | 1 + - .../data/profile_stability/rhel8/stig.profile | 1 + - .../profile_stability/rhel8/stig_gui.profile | 1 + - 15 files changed, 289 insertions(+), 24 deletions(-) - create mode 100644 linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_name_format.var - -diff --git a/controls/srg_gpos.yml b/controls/srg_gpos.yml -index 1be70cf332..45fe8635c0 100644 ---- a/controls/srg_gpos.yml -+++ b/controls/srg_gpos.yml -@@ -29,3 +29,4 @@ controls: - - var_auditd_space_left_action=email - - login_banner_text=dod_banners - - var_authselect_profile=sssd -+ - var_auditd_name_format=stig -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/ansible/shared.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/ansible/shared.yml -index c933228357..015e9d6eff 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/ansible/shared.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/ansible/shared.yml -@@ -10,9 +10,14 @@ - {{%- set auditd_conf_path=audisp_conf_path + "/auditd.conf" %}} - {{%- endif %}} - -+{{{ ansible_instantiate_variables("var_auditd_name_format") }}} -+ -+- name: "{{{ rule_title }}} - Define Value to Be Used in the Remediation" -+ ansible.builtin.set_fact: auditd_name_format_split="{{ var_auditd_name_format.split('|')[0] }}" -+ - {{{ ansible_set_config_file(file=auditd_conf_path, - parameter="name_format", -- value="hostname", -+ value="{{ auditd_name_format_split }}", - create=true, - separator=" = ", - separator_regex="\s*=\s*", -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/bash/shared.sh b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/bash/shared.sh -index 67a1203dd5..a08fddc901 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/bash/shared.sh -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/bash/shared.sh -@@ -10,9 +10,14 @@ - {{%- set auditd_conf_path=audisp_conf_path + "/auditd.conf" %}} - {{%- endif %}} - -+ -+{{{ bash_instantiate_variables("var_auditd_name_format") }}} -+ -+var_auditd_name_format="$(echo $var_auditd_name_format | cut -d \| -f 1)" -+ - {{{set_config_file(path=auditd_conf_path, - parameter="name_format", -- value="hostname", -+ value="$var_auditd_name_format", - create=true, - insensitive=true, - separator=" = ", -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/oval/shared.xml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/oval/shared.xml -index 1bb86958fa..a98a46773b 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/oval/shared.xml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/oval/shared.xml -@@ -3,10 +3,47 @@ - {{% else %}} - {{% set audisp_conf_file = "/auditd.conf" %}} - {{% endif %}} -+ -+ -+ -+ Set type of computer node name logging in audit logs -+ -+ multi_platform_all -+ -+ Ensure 'name_format' is configured with value 'hostname|fdq|numeric' in {{{ audisp_conf_path + audisp_conf_file }}} -+ -+ -+ -+ - --{{{ oval_check_config_file( -- path=audisp_conf_path + audisp_conf_file, -- prefix_regex="^[ \\t]*(?i)", -- parameter="name_format", -- value="(?i)hostname(?-i)", -- separator_regex="(?-i)[ \\t]*=[ \\t]*") }}} -+ -+ -+ -+ -+ -+ -+ {{{ audisp_conf_path + audisp_conf_file }}} -+ ^[ \t]*(?i)name_format(?-i)[ \t]*=[ \t]*(.+?)[ \t]*(?:$|#) -+ 1 -+ -+ -+ -+ -+ -+ -+ -+ -+ (?i) -+ -+ -+ -+ -+ -+ -+ -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -index 76a908f28f..4ee80e3d07 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -@@ -1,11 +1,11 @@ - documentation_complete: true - --title: 'Set hostname as computer node name in audit logs' -+title: 'Set type of computer node name logging in audit logs' - - description: |- -- To configure Audit daemon to use value returned by gethostname -- syscall as computer node name in the audit events, -- set name_format to hostname -+ To configure Audit daemon to use a unique identifier -+ as computer node name in the audit events, -+ set name_format to {{{ xccdf_value("var_auditd_name_format") }}} - in /etc/audit/auditd.conf. - - rationale: |- -@@ -32,17 +32,22 @@ references: - stigid@rhel8: RHEL-08-030062 - stigid@rhel9: RHEL-09-653060 - --ocil_clause: name_format isn't set to hostname -+ocil_clause: name_format isn't set to {{{ xccdf_value("var_auditd_name_format") }}} - - ocil: |- -- To verify that Audit Daemon is configured to record the hostname -- in audit events, run the following command: -+ To verify that Audit Daemon is configured to record the computer node -+ name in the audit events, run the following command: - 
$ sudo grep name_format /etc/audit/auditd.conf
- The output should return the following: -- 
name_format = hostname
-+ 
name_format = {{{ xccdf_value("var_auditd_name_format") }}}
-+ -+warnings: -+ - general: |- -+ Whenever the variable 
var_auditd_name_format
uses a multiple value option, for example -+ 
A|B|C
, the first value will be used when remediating this rule. - - fixtext: |- -- {{{ fixtext_audit_configuration(param="name_format", value="hostname") | indent(4) }}} -+ {{{ fixtext_audit_configuration(param="name_format", value=xccdf_value("var_auditd_name_format")) | indent(4) }}} - - srg_requirement: |- - {{{ full_name }}} must label all off-loaded audit logs before sending them to the central log server. -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_flush.var b/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_flush.var -index 3ae67d484a..f7b0bc5b8f 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_flush.var -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_flush.var -@@ -13,5 +13,5 @@ options: - default: data - incremental: incremental - incremental_async: incremental_async -- none: none -+ none: "none" - sync: sync -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_name_format.var b/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_name_format.var -new file mode 100644 -index 0000000000..75cc597038 ---- /dev/null -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/var_auditd_name_format.var -@@ -0,0 +1,18 @@ -+documentation_complete: true -+ -+title: 'Type of hostname to record the audit event' -+ -+description: 'Type of hostname to record the audit event' -+ -+type: string -+ -+interactive: false -+ -+options: -+ default: hostname -+ hostname: hostname -+ fqd: fqd -+ numeric: numeric -+ user: user -+ none: "none" -+ stig: hostname|fqd|numeric -diff --git a/products/rhel7/profiles/stig.profile b/products/rhel7/profiles/stig.profile -index 6483dfe3da..1e1e50765a 100644 ---- a/products/rhel7/profiles/stig.profile -+++ b/products/rhel7/profiles/stig.profile -@@ -335,6 +335,7 @@ selections: - - accounts_authorized_local_users - - auditd_overflow_action - - auditd_name_format -+ - var_auditd_name_format=stig - - sebool_ssh_sysadm_login - - sudoers_default_includedir - - package_aide_installed -diff --git a/products/rhel8/profiles/stig.profile b/products/rhel8/profiles/stig.profile -index 0e136784a1..3914fae78f 100644 ---- a/products/rhel8/profiles/stig.profile -+++ b/products/rhel8/profiles/stig.profile -@@ -707,6 +707,7 @@ selections: - - # RHEL-08-030062 - - auditd_name_format -+ - var_auditd_name_format=stig - - # RHEL-08-030063 - - auditd_log_format -diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile -index 7aabec8694..60dc9d3a50 100644 ---- a/tests/data/profile_stability/rhel8/stig.profile -+++ b/tests/data/profile_stability/rhel8/stig.profile -@@ -473,6 +473,7 @@ selections: - - var_auditd_disk_error_action=rhel8 - - var_auditd_max_log_file_action=syslog - - var_auditd_disk_full_action=rhel8 -+- var_auditd_name_format=stig - - var_sssd_certificate_verification_digest_function=sha1 - - login_banner_text=dod_banners - - var_authselect_profile=sssd -diff --git a/tests/data/profile_stability/rhel8/stig_gui.profile b/tests/data/profile_stability/rhel8/stig_gui.profile -index bef1437536..b77c8eab2f 100644 ---- a/tests/data/profile_stability/rhel8/stig_gui.profile -+++ b/tests/data/profile_stability/rhel8/stig_gui.profile -@@ -481,6 +481,7 @@ selections: - - var_auditd_disk_error_action=rhel8 - - var_auditd_max_log_file_action=syslog - - var_auditd_disk_full_action=rhel8 -+- var_auditd_name_format=stig - - var_sssd_certificate_verification_digest_function=sha1 - - login_banner_text=dod_banners - - var_authselect_profile=sssd --- -2.43.0 - diff --git a/scap-security-guide-0.1.70-remove_openssh_hardening_stig-PR_10996.patch b/scap-security-guide-0.1.70-remove_openssh_hardening_stig-PR_10996.patch deleted file mode 100644 index a181eb5..0000000 --- a/scap-security-guide-0.1.70-remove_openssh_hardening_stig-PR_10996.patch +++ /dev/null @@ -1,21 +0,0 @@ -From 509c117acea0cc7a8457752cbdb4b8e7a6ca27d7 Mon Sep 17 00:00:00 2001 -From: Vojtech Polasek -Date: Tue, 15 Aug 2023 15:17:16 +0200 -Subject: [PATCH] remove rules not relevant to RHEL 9 from STIG profile - -rules have no remediation for RHEL 9, syntax for RHEL 9 is also different than RHEL 8 ---- - controls/srg_gpos/SRG-OS-000125-GPOS-00065.yml | 2 -- - 1 file changed, 2 deletions(-) - -diff --git a/controls/srg_gpos/SRG-OS-000125-GPOS-00065.yml b/controls/srg_gpos/SRG-OS-000125-GPOS-00065.yml -index d5fe6e1327b..9d9dc579fc4 100644 ---- a/controls/srg_gpos/SRG-OS-000125-GPOS-00065.yml -+++ b/controls/srg_gpos/SRG-OS-000125-GPOS-00065.yml -@@ -7,6 +7,4 @@ controls: - rules: - - sshd_enable_pam - - sysctl_crypto_fips_enabled -- - harden_sshd_ciphers_openssh_conf_crypto_policy -- - harden_sshd_macs_openssh_conf_crypto_policy - status: automated diff --git a/scap-security-guide-0.1.70-remove_secure_mode_insmod_anssi-PR_11001.patch b/scap-security-guide-0.1.70-remove_secure_mode_insmod_anssi-PR_11001.patch deleted file mode 100644 index bf45744..0000000 --- a/scap-security-guide-0.1.70-remove_secure_mode_insmod_anssi-PR_11001.patch +++ /dev/null @@ -1,30 +0,0 @@ -From 08b9f875630e119d90a5a1fc3694f6168ad19cb9 Mon Sep 17 00:00:00 2001 -From: Vojtech Polasek -Date: Thu, 17 Aug 2023 10:50:09 +0200 -Subject: [PATCH] remove sebool_secure_mode_insmod from RHEL ANSSI high - ---- - products/rhel8/profiles/anssi_bp28_high.profile | 2 ++ - products/rhel9/profiles/anssi_bp28_high.profile | 2 ++ - 2 files changed, 4 insertions(+) - -diff --git a/products/rhel8/profiles/anssi_bp28_high.profile b/products/rhel8/profiles/anssi_bp28_high.profile -index e2eeabbb78d..204e141b1f5 100644 ---- a/products/rhel8/profiles/anssi_bp28_high.profile -+++ b/products/rhel8/profiles/anssi_bp28_high.profile -@@ -17,3 +17,5 @@ description: |- - - selections: - - anssi:all:high -+ # the following rule renders UEFI systems unbootable -+ - '!sebool_secure_mode_insmod' -diff --git a/products/rhel9/profiles/anssi_bp28_high.profile b/products/rhel9/profiles/anssi_bp28_high.profile -index e2eeabbb78d..204e141b1f5 100644 ---- a/products/rhel9/profiles/anssi_bp28_high.profile -+++ b/products/rhel9/profiles/anssi_bp28_high.profile -@@ -17,3 +17,5 @@ description: |- - - selections: - - anssi:all:high -+ # the following rule renders UEFI systems unbootable -+ - '!sebool_secure_mode_insmod' diff --git a/scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch b/scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch deleted file mode 100644 index d602a60..0000000 --- a/scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch +++ /dev/null @@ -1,104 +0,0 @@ -From cfbc85e51f15d106dd3cf03ef2fc7cd4f3c5d251 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:05:37 +0100 -Subject: [PATCH 06/14] Update sshd_approved_ciphers value for RHEL in STIG - profile - -Patch-name: scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch -Patch-status: Update sshd_approved_ciphers value for RHEL in STIG profile ---- - controls/srg_gpos.yml | 2 +- - products/rhel8/profiles/stig.profile | 2 +- - tests/data/profile_stability/rhel8/stig.profile | 6 +++--- - tests/data/profile_stability/rhel8/stig_gui.profile | 6 +++--- - 4 files changed, 8 insertions(+), 8 deletions(-) - -diff --git a/controls/srg_gpos.yml b/controls/srg_gpos.yml -index 65d58d5291..1be70cf332 100644 ---- a/controls/srg_gpos.yml -+++ b/controls/srg_gpos.yml -@@ -20,7 +20,7 @@ controls: - - var_password_hashing_algorithm=SHA512 - - var_password_pam_dictcheck=1 - - sshd_approved_macs=stig_extended -- - sshd_approved_ciphers=stig -+ - sshd_approved_ciphers=stig_extended - - sshd_idle_timeout_value=10_minutes - - var_accounts_authorized_local_users_regex=rhel8 - - var_account_disable_post_pw_expiration=35 -diff --git a/products/rhel8/profiles/stig.profile b/products/rhel8/profiles/stig.profile -index 5be8fb8127..0e136784a1 100644 ---- a/products/rhel8/profiles/stig.profile -+++ b/products/rhel8/profiles/stig.profile -@@ -51,7 +51,7 @@ selections: - - var_password_pam_minlen=15 - - var_sshd_set_keepalive=1 - - sshd_approved_macs=stig_extended -- - sshd_approved_ciphers=stig -+ - sshd_approved_ciphers=stig_extended - - sshd_idle_timeout_value=10_minutes - - var_accounts_authorized_local_users_regex=rhel8 - - var_accounts_passwords_pam_faillock_deny=3 -diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile -index 3fe7cdf4ea..7aabec8694 100644 ---- a/tests/data/profile_stability/rhel8/stig.profile -+++ b/tests/data/profile_stability/rhel8/stig.profile -@@ -1,6 +1,6 @@ - description: 'This profile contains configuration checks that align to the - -- DISA STIG for Red Hat Enterprise Linux 8 V1R9. -+ DISA STIG for Red Hat Enterprise Linux 8 V1R11. - - - In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes -@@ -22,7 +22,7 @@ description: 'This profile contains configuration checks that align to the - - Red Hat Containers with a Red Hat Enterprise Linux 8 image' - extends: null - metadata: -- version: V1R10 -+ version: V1R11 - SMEs: - - mab879 - - ggbecker -@@ -455,7 +455,7 @@ selections: - - var_password_pam_retry=3 - - var_sshd_set_keepalive=1 - - sshd_approved_macs=stig_extended --- sshd_approved_ciphers=stig -+- sshd_approved_ciphers=stig_extended - - sshd_idle_timeout_value=10_minutes - - var_accounts_authorized_local_users_regex=rhel8 - - var_accounts_passwords_pam_faillock_deny=3 -diff --git a/tests/data/profile_stability/rhel8/stig_gui.profile b/tests/data/profile_stability/rhel8/stig_gui.profile -index 66ada8588f..bef1437536 100644 ---- a/tests/data/profile_stability/rhel8/stig_gui.profile -+++ b/tests/data/profile_stability/rhel8/stig_gui.profile -@@ -1,6 +1,6 @@ - description: 'This profile contains configuration checks that align to the - -- DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R9. -+ DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R11. - - - In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes -@@ -33,7 +33,7 @@ description: 'This profile contains configuration checks that align to the - standard DISA STIG for Red Hat Enterprise Linux 8 profile.' - extends: null - metadata: -- version: V1R10 -+ version: V1R11 - SMEs: - - mab879 - - ggbecker -@@ -463,7 +463,7 @@ selections: - - var_password_pam_retry=3 - - var_sshd_set_keepalive=1 - - sshd_approved_macs=stig_extended --- sshd_approved_ciphers=stig -+- sshd_approved_ciphers=stig_extended - - sshd_idle_timeout_value=10_minutes - - var_accounts_authorized_local_users_regex=rhel8 - - var_accounts_passwords_pam_faillock_deny=3 --- -2.43.0 - diff --git a/scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch b/scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch deleted file mode 100644 index 32df8ef..0000000 --- a/scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch +++ /dev/null @@ -1,212 +0,0 @@ -From f0998f93828e756111294eb4c733fad77febd493 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Wed, 6 Dec 2023 10:31:53 +0100 -Subject: [PATCH 15/15] Update ssh stig HMACS and Ciphers allowed in OL8 STIG - -Patch-name: scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch -Patch-status: Update ssh stig HMACS and Ciphers allowed in OL8 STIG ---- - linux_os/guide/services/ssh/sshd_approved_ciphers.var | 1 + - .../tests/rhel8_stig_correct.pass.sh | 5 +++-- - .../tests/rhel8_stig_empty_policy.fail.sh | 2 +- - .../tests/rhel8_stig_incorrect_policy.fail.sh | 2 +- - .../tests/rhel8_stig_missing_file.fail.sh | 2 +- - .../harden_sshd_macs_openssh_conf_crypto_policy/rule.yml | 4 ++-- - .../tests/stig_correct.pass.sh | 5 +++-- - .../tests/stig_correct_commented.fail.sh | 5 +++-- - .../stig_correct_followed_by_incorrect_commented.pass.sh | 5 +++-- - .../stig_incorrect_followed_by_correct_commented.fail.sh | 5 +++-- - .../rule.yml | 4 ++-- - products/ol8/profiles/stig.profile | 4 ++-- - 12 files changed, 25 insertions(+), 19 deletions(-) - -diff --git a/linux_os/guide/services/ssh/sshd_approved_ciphers.var b/linux_os/guide/services/ssh/sshd_approved_ciphers.var -index 65c3fde987..4ab4d36cef 100644 ---- a/linux_os/guide/services/ssh/sshd_approved_ciphers.var -+++ b/linux_os/guide/services/ssh/sshd_approved_ciphers.var -@@ -12,6 +12,7 @@ interactive: false - - options: - stig: aes256-ctr,aes192-ctr,aes128-ctr -+ stig_extended: aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com - default: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se - cis_rhel7: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc - cis_sle12: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_correct.pass.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_correct.pass.sh -index c84e0c1576..34b69406a3 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_correct.pass.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_correct.pass.sh -@@ -1,8 +1,9 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8 --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com -+ -+sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com - --sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr - configfile=/etc/crypto-policies/back-ends/opensshserver.config - correct_value="-oCiphers=${sshd_approved_ciphers}" - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_empty_policy.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_empty_policy.fail.sh -index 66483e898a..60b4616ce5 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_empty_policy.fail.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_empty_policy.fail.sh -@@ -1,6 +1,6 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8 --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com - - configfile=/etc/crypto-policies/back-ends/opensshserver.config - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_incorrect_policy.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_incorrect_policy.fail.sh -index e350ce5f0a..3eca150b3f 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_incorrect_policy.fail.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_incorrect_policy.fail.sh -@@ -1,6 +1,6 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8 --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com - - configfile=/etc/crypto-policies/back-ends/opensshserver.config - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_missing_file.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_missing_file.fail.sh -index 11b194db03..f8659efcf0 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_missing_file.fail.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/tests/rhel8_stig_missing_file.fail.sh -@@ -1,6 +1,6 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8 --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_ciphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com - - configfile=/etc/crypto-policies/back-ends/opensshserver.config - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/rule.yml -index 8736e39afc..547c31545e 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/rule.yml -@@ -12,7 +12,7 @@ description: |- - 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-512,hmac-sha2-256 -+ MACs {{{ xccdf_value("sshd_approved_macs") }}} - - rationale: |- - Overriding the system crypto policy makes the behavior of the OpenSSH -@@ -38,7 +38,7 @@ ocil: |- - To verify if the OpenSSH client uses defined MACs in the Crypto Policy, run: - 
$ grep -i macs /etc/crypto-policies/back-ends/openssh.config
- and verify that the line matches: -- 
MACs hmac-sha2-512,hmac-sha2-256
-+ 
MACs {{{ xccdf_value("sshd_approved_macs") }}}
- - warnings: - - general: |- -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct.pass.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct.pass.sh -index 6edae50924..49d18486f3 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct.pass.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct.pass.sh -@@ -1,8 +1,9 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8,multi_platform_fedora --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com -+ -+sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com - --sshd_approved_macs=hmac-sha2-512,hmac-sha2-256 - configfile=/etc/crypto-policies/back-ends/openssh.config - - # Ensure directory + file is there -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_commented.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_commented.fail.sh -index 0fec46a5c3..b068e2ea4d 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_commented.fail.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_commented.fail.sh -@@ -1,8 +1,9 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8,multi_platform_fedora --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com -+ -+sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com - --sshd_approved_macs=hmac-sha2-512,hmac-sha2-256 - configfile=/etc/crypto-policies/back-ends/openssh.config - - # Ensure directory + file is there -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_followed_by_incorrect_commented.pass.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_followed_by_incorrect_commented.pass.sh -index 95bf94331c..f57f422701 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_followed_by_incorrect_commented.pass.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_correct_followed_by_incorrect_commented.pass.sh -@@ -1,8 +1,9 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8,multi_platform_fedora --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com -+ -+sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com - --sshd_approved_macs=hmac-sha2-512,hmac-sha2-256 - configfile=/etc/crypto-policies/back-ends/openssh.config - - # Ensure directory + file is there -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_incorrect_followed_by_correct_commented.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_incorrect_followed_by_correct_commented.fail.sh -index 4af43d60e7..999463e1c2 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_incorrect_followed_by_correct_commented.fail.sh -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_openssh_conf_crypto_policy/tests/stig_incorrect_followed_by_correct_commented.fail.sh -@@ -1,8 +1,9 @@ - #!/bin/bash - # platform = Oracle Linux 8,Red Hat Enterprise Linux 8,multi_platform_fedora --# profiles = xccdf_org.ssgproject.content_profile_stig -+# variables = sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com -+ -+sshd_approved_macs=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com - --sshd_approved_macs=hmac-sha2-512,hmac-sha2-256 - incorrect_sshd_approved_macs=hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 - configfile=/etc/crypto-policies/back-ends/openssh.config - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_opensshserver_conf_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_opensshserver_conf_crypto_policy/rule.yml -index f08f120f9a..a76cee71d8 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_opensshserver_conf_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_macs_opensshserver_conf_crypto_policy/rule.yml -@@ -12,7 +12,7 @@ description: |- - 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-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com -+ -oMACS={{{ xccdf_value("sshd_approved_macs") }}} - - rationale: |- - Overriding the system crypto policy makes the behavior of the OpenSSH -@@ -38,7 +38,7 @@ ocil: |- - To verify if the OpenSSH server uses defined MACs in the Crypto Policy, run: - 
$ grep -Po '(-oMACs=\S+)' /etc/crypto-policies/back-ends/opensshserver.config
- and verify that the line matches: -- 
-oMACS=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com
-+ 
-oMACS={{{ xccdf_value("sshd_approved_macs") }}}
- - warnings: - - general: |- -diff --git a/products/ol8/profiles/stig.profile b/products/ol8/profiles/stig.profile -index ae2795c4fb..2be62c59ca 100644 ---- a/products/ol8/profiles/stig.profile -+++ b/products/ol8/profiles/stig.profile -@@ -38,8 +38,8 @@ selections: - - var_password_pam_retry=3 - - var_password_pam_minlen=15 - - var_sshd_set_keepalive=0 -- - sshd_approved_macs=stig -- - sshd_approved_ciphers=stig -+ - sshd_approved_macs=stig_extended -+ - sshd_approved_ciphers=stig_extended - - sshd_idle_timeout_value=10_minutes - - var_accounts_authorized_local_users_regex=ol8 - - var_accounts_passwords_pam_faillock_deny=3 --- -2.43.0 - diff --git a/scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch b/scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch deleted file mode 100644 index 4c12920..0000000 --- a/scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch +++ /dev/null @@ -1,158 +0,0 @@ -From 1927922065ba7cab8e389d6b2e4ec014be491bed Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:05:37 +0100 -Subject: [PATCH 09/14] Add cron.deny Owership Rules - -Patch-name: scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch -Patch-status: Add cron.deny Owership Rules ---- - components/cronie.yml | 2 + - .../srg_gpos/SRG-OS-000480-GPOS-00227.yml | 2 + - .../file_groupowner_cron_deny/rule.yml | 39 ++++++++++++++++++ - .../cron_and_at/file_owner_cron_deny/rule.yml | 41 +++++++++++++++++++ - shared/references/cce-redhat-avail.txt | 2 - - 5 files changed, 84 insertions(+), 2 deletions(-) - create mode 100644 linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml - create mode 100644 linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml - -diff --git a/components/cronie.yml b/components/cronie.yml -index c11edb518e..b8bf7f264a 100644 ---- a/components/cronie.yml -+++ b/components/cronie.yml -@@ -8,6 +8,8 @@ rules: - - disable_anacron - - file_at_deny_not_exist - - file_cron_deny_not_exist -+- file_owner_cron_deny -+- file_groupowner_cron_deny - - file_groupowner_at_allow - - file_groupowner_cron_allow - - file_groupowner_cron_d -diff --git a/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml b/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -index be60a154c1..d78256777c 100644 ---- a/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -+++ b/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -@@ -64,6 +64,8 @@ controls: - - file_permissions_ungroupowned - - dir_perms_world_writable_root_owned - - no_files_unowned_by_user -+ - file_owner_cron_deny -+ - file_groupowner_cron_deny - - # service disabled - # - service_rngd_enabled - this rule was removed because it does bring questionable value on modern systems -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml -new file mode 100644 -index 0000000000..7cacc3fc7b ---- /dev/null -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml -@@ -0,0 +1,39 @@ -+documentation_complete: true -+ -+prodtype: rhel9 -+ -+title: 'Verify Group Who Owns cron.deny' -+ -+description: |- -+ {{{ describe_file_group_owner(file="/etc/cron.deny", group="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. -+ -+severity: medium -+ -+identifiers: -+ cce@rhel9: CCE-86537-8 -+ -+ -+references: -+ disa: CCI-000366 -+ nist: CM-6 b -+ srg: SRG-OS-000480-GPOS-00227 -+ -+ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.deny", group="root") }}}' -+ -+ocil: |- -+ {{{ ocil_file_group_owner(file="/etc/cron.deny", group="root") }}} -+ -+fixtext: '{{{ fixtext_file_group_owner(file="/etc/cron.deny/", group="root") }}}' -+ -+srg_requirement: '{{{ srg_requirement_file_group_owner(file="/etc/cron.deny", group="root") }}}' -+ -+template: -+ name: file_groupowner -+ vars: -+ filepath: /etc/cron.deny -+ gid_or_name: '0' -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml -new file mode 100644 -index 0000000000..4297313a74 ---- /dev/null -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml -@@ -0,0 +1,41 @@ -+documentation_complete: true -+ -+prodtype: rhel9 -+ -+title: 'Verify Owner on cron.deny' -+ -+description: |- -+ {{{ describe_file_owner(file="/etc/cron.deny", owner="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 user to prevent unauthorized changes. -+ -+ -+severity: medium -+ -+identifiers: -+ cce@rhel9: CCE-86887-7 -+ -+references: -+ disa: CCI-000366 -+ nist: CM-6 b -+ srg: SRG-OS-000480-GPOS-00227 -+ -+ -+ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.deny", owner="root") }}}' -+ -+ocil: |- -+ {{{ ocil_file_owner(file="/etc/cron.deny", owner="root") }}} -+ -+fixtext: '{{{ fixtext_file_owner(file="/etc/cron.deny/", owner="root") }}}' -+ -+srg_requirement: '{{{ srg_requirement_file_owner(file="/etc/cron.deny", owner="root") }}}' -+ -+template: -+ name: file_owner -+ vars: -+ filepath: /etc/cron.deny -+ fileuid: '0' -+ -diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt -index 60663b117a..8ae1e4186f 100644 ---- a/shared/references/cce-redhat-avail.txt -+++ b/shared/references/cce-redhat-avail.txt -@@ -259,7 +259,6 @@ CCE-86528-7 - CCE-86530-3 - CCE-86535-2 - CCE-86536-0 --CCE-86537-8 - CCE-86538-6 - CCE-86539-4 - CCE-86540-2 -@@ -516,7 +515,6 @@ CCE-86880-2 - CCE-86881-0 - CCE-86882-8 - CCE-86886-9 --CCE-86887-7 - CCE-86888-5 - CCE-86889-3 - CCE-86890-1 --- -2.43.0 - diff --git a/scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch b/scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch deleted file mode 100644 index 2bb15ed..0000000 --- a/scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch +++ /dev/null @@ -1,18124 +0,0 @@ -From d70d9db129c4120f9f370d98ff52d8326c501c9f Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:22:08 +0100 -Subject: [PATCH 10/14] Add RHEL 9 STIG - -Patch-name: scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch -Patch-status: Add RHEL 9 STIG ---- - controls/stig_rhel9.yml | 4236 ++++++++++ - .../base/service_kdump_disabled/rule.yml | 1 + - .../file_groupowner_cron_d/rule.yml | 1 + - .../file_groupowner_cron_daily/rule.yml | 1 + - .../file_groupowner_cron_deny/rule.yml | 1 + - .../file_groupowner_cron_hourly/rule.yml | 1 + - .../file_groupowner_cron_monthly/rule.yml | 1 + - .../file_groupowner_cron_weekly/rule.yml | 1 + - .../file_groupowner_crontab/rule.yml | 1 + - .../cron_and_at/file_owner_cron_d/rule.yml | 1 + - .../file_owner_cron_daily/rule.yml | 1 + - .../cron_and_at/file_owner_cron_deny/rule.yml | 1 + - .../file_owner_cron_hourly/rule.yml | 1 + - .../file_owner_cron_monthly/rule.yml | 1 + - .../file_owner_cron_weekly/rule.yml | 1 + - .../cron_and_at/file_owner_crontab/rule.yml | 1 + - .../file_permissions_cron_d/rule.yml | 1 + - .../file_permissions_cron_daily/rule.yml | 1 + - .../file_permissions_cron_hourly/rule.yml | 1 + - .../file_permissions_cron_monthly/rule.yml | 1 + - .../file_permissions_cron_weekly/rule.yml | 1 + - .../file_permissions_crontab/rule.yml | 1 + - .../package_fapolicyd_installed/rule.yml | 1 + - .../service_fapolicyd_enabled/rule.yml | 1 + - .../package_vsftpd_removed/rule.yml | 1 + - .../kerberos_disable_no_keytab/rule.yml | 1 + - .../mail/package_s-nail_installed/rule.yml | 1 + - .../mail/package_sendmail_removed/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../package_nfs-utils_removed/rule.yml | 1 + - .../services/ntp/chronyd_client_only/rule.yml | 1 + - .../ntp/chronyd_no_chronyc_network/rule.yml | 1 + - .../ntp/chronyd_or_ntpd_set_maxpoll/rule.yml | 1 + - .../ntp/chronyd_server_directive/rule.yml | 1 + - .../ntp/package_chrony_installed/rule.yml | 1 + - .../ntp/service_chronyd_enabled/rule.yml | 1 + - .../nis/package_ypserv_removed/rule.yml | 1 + - .../r_services/no_host_based_files/rule.yml | 1 + - .../no_user_host_based_files/rule.yml | 1 + - .../package_rsh-server_removed/rule.yml | 1 + - .../package_telnet-server_removed/rule.yml | 1 + - .../tftp/package_tftp-server_removed/rule.yml | 1 + - .../tftp/tftpd_uses_secure_mode/rule.yml | 1 + - .../rng/service_rngd_enabled/rule.yml | 6 + - .../package_quagga_removed/rule.yml | 1 + - .../ssh/file_groupowner_sshd_config/rule.yml | 1 + - .../ssh/file_owner_sshd_config/rule.yml | 1 + - .../ssh/file_permissions_sshd_config/rule.yml | 1 + - .../rule.yml | 1 + - .../file_permissions_sshd_pub_key/rule.yml | 1 + - .../rule.yml | 1 + - .../package_openssh-server_installed/rule.yml | 1 + - .../ssh/service_sshd_enabled/rule.yml | 1 + - .../ssh_keys_passphrase_protected/rule.yml | 1 + - .../ssh/ssh_server/disable_host_auth/rule.yml | 1 + - .../firewalld_sshd_port_enabled/rule.yml | 1 + - .../sshd_disable_compression/rule.yml | 1 + - .../sshd_disable_empty_passwords/rule.yml | 1 + - .../sshd_disable_gssapi_auth/rule.yml | 1 + - .../sshd_disable_kerb_auth/rule.yml | 1 + - .../ssh_server/sshd_disable_rhosts/rule.yml | 1 + - .../sshd_disable_root_login/rule.yml | 1 + - .../sshd_disable_user_known_hosts/rule.yml | 1 + - .../sshd_disable_x11_forwarding/rule.yml | 1 + - .../sshd_do_not_permit_user_env/rule.yml | 1 + - .../ssh/ssh_server/sshd_enable_pam/rule.yml | 1 + - .../sshd_enable_pubkey_auth/rule.yml | 1 + - .../sshd_enable_strictmodes/rule.yml | 1 + - .../sshd_enable_warning_banner/rule.yml | 1 + - .../ssh_server/sshd_print_last_log/rule.yml | 1 + - .../ssh/ssh_server/sshd_rekey_limit/rule.yml | 1 + - .../ssh_server/sshd_set_idle_timeout/rule.yml | 1 + - .../ssh_server/sshd_set_keepalive/rule.yml | 1 + - .../sshd_set_loglevel_verbose/rule.yml | 1 + - .../sshd_use_priv_separation/rule.yml | 1 + - .../sshd_x11_use_localhost/rule.yml | 1 + - .../sssd_certificate_verification/rule.yml | 2 +- - .../sssd/sssd_enable_certmap/rule.yml | 1 + - .../sssd/sssd_enable_smartcards/rule.yml | 1 + - .../sssd/sssd_has_trust_anchor/rule.yml | 1 + - .../sssd_offline_cred_expiration/rule.yml | 1 + - .../configure_usbguard_auditbackend/rule.yml | 1 + - .../package_usbguard_installed/rule.yml | 1 + - .../service_usbguard_enabled/rule.yml | 1 + - .../usbguard_generate_policy/rule.yml | 1 + - .../xwindows_remove_packages/rule.yml | 1 + - .../xwindows_runlevel_target/rule.yml | 1 + - .../banner_etc_issue/rule.yml | 1 + - .../dconf_gnome_banner_enabled/rule.yml | 1 + - .../disallow_bypass_password_sudo/rule.yml | 1 + - .../display_login_attempts/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 5 +- - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../accounts_password_pam_dcredit/rule.yml | 1 + - .../accounts_password_pam_dictcheck/rule.yml | 1 + - .../accounts_password_pam_difok/rule.yml | 1 + - .../rule.yml | 1 + - .../accounts_password_pam_lcredit/rule.yml | 1 + - .../rule.yml | 1 + - .../accounts_password_pam_maxrepeat/rule.yml | 1 + - .../accounts_password_pam_minclass/rule.yml | 1 + - .../accounts_password_pam_minlen/rule.yml | 1 + - .../accounts_password_pam_ocredit/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../accounts_password_pam_retry/rule.yml | 1 + - .../accounts_password_pam_ucredit/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../disable_ctrlaltdel_burstaction/rule.yml | 1 + - .../disable_ctrlaltdel_reboot/rule.yml | 1 + - .../grub2_disable_interactive_boot/rule.yml | 1 + - .../logind_session_timeout/rule.yml | 1 + - .../require_emergency_target_auth/rule.yml | 1 + - .../require_singleuser_auth/rule.yml | 1 + - .../configure_bashrc_exec_tmux/rule.yml | 1 + - .../configure_tmux_lock_after_time/rule.yml | 1 + - .../configure_tmux_lock_command/rule.yml | 1 + - .../configure_tmux_lock_keybinding/rule.yml | 1 + - .../no_tmux_in_shells/rule.yml | 1 + - .../package_tmux_installed/rule.yml | 1 + - .../configure_opensc_card_drivers/rule.yml | 1 + - .../install_smartcard_packages/rule.yml | 1 + - .../package_opensc_installed/rule.yml | 1 + - .../package_pcsc-lite_installed/rule.yml | 1 + - .../service_pcscd_enabled/rule.yml | 1 + - .../service_debug-shell_disabled/rule.yml | 1 + - .../rule.yml | 1 + - .../account_temp_expire_date/rule.yml | 1 + - .../account_unique_id/rule.yml | 1 + - .../accounts_authorized_local_users/rule.yml | 1 + - .../group_unique_id/rule.yml | 1 + - .../accounts_maximum_age_login_defs/rule.yml | 2 +- - .../accounts_minimum_age_login_defs/rule.yml | 2 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 2 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../gid_passwd_group_same/rule.yml | 1 + - .../no_empty_passwords/rule.yml | 3 +- - .../no_empty_passwords_etc_shadow/rule.yml | 1 + - .../accounts_no_uid_except_zero/rule.yml | 1 + - .../no_shelllogin_for_systemaccounts/rule.yml | 1 + - .../root_logins/use_pam_wheel_for_su/rule.yml | 1 + - ..._accounts_authorized_local_users_regex.var | 1 + - .../accounts_have_homedir_login_defs/rule.yml | 1 + - .../accounts_logon_fail_delay/rule.yml | 1 + - .../rule.yml | 1 + - .../accounts-session/accounts_tmout/rule.yml | 1 + - .../rule.yml | 1 + - .../accounts_user_home_paths_only/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../file_permission_user_init_files/rule.yml | 1 + - .../rule.yml | 1 + - .../accounts_umask_etc_bashrc/rule.yml | 1 + - .../accounts_umask_etc_csh_cshrc/rule.yml | 1 + - .../accounts_umask_etc_login_defs/rule.yml | 1 + - .../accounts_umask_etc_profile/rule.yml | 1 + - .../accounts_umask_interactive_users/rule.yml | 1 + - .../authconfig_config_files_symlinks/rule.yml | 1 - - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 3 +- - .../audit_rules_execution_chacl/rule.yml | 1 + - .../audit_rules_execution_setfacl/rule.yml | 1 + - .../audit_rules_execution_chcon/rule.yml | 1 + - .../audit_rules_execution_semanage/rule.yml | 1 + - .../audit_rules_execution_setfiles/rule.yml | 1 + - .../audit_rules_execution_setsebool/rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 3 +- - .../rule.yml | 2 + - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../audit_rules_login_events_lastlog/rule.yml | 1 + - .../rule.yml | 1 + - .../audit_privileged_commands_init/rule.yml | 1 + - .../rule.yml | 1 + - .../audit_privileged_commands_reboot/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../audit_rules_immutable/rule.yml | 1 + - .../audit_rules_sudoers/rule.yml | 1 + - .../audit_rules_sudoers_d/rule.yml | 1 + - .../rule.yml | 1 + - .../audit_rules_system_shutdown/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../file_permissions_var_log_audit/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 2 +- - .../rule.yml | 3 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../auditd_freq/rule.yml | 1 + - .../auditd_local_events/rule.yml | 1 + - .../auditd_log_format/rule.yml | 1 + - .../auditd_name_format/rule.yml | 1 + - .../auditd_overflow_action/rule.yml | 1 + - .../auditd_write_logs/rule.yml | 1 + - .../auditing/grub2_audit_argument/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../auditing/package_audit_installed/rule.yml | 1 + - .../audit_immutable_login_uids/rule.yml | 1 + - .../auditing/service_auditd_enabled/rule.yml | 1 + - .../grub2_pti_argument/rule.yml | 1 + - .../grub2_vsyscall_argument/rule.yml | 2 +- - .../file_groupowner_grub2_cfg/rule.yml | 1 + - .../non-uefi/file_owner_grub2_cfg/rule.yml | 1 + - .../non-uefi/grub2_admin_username/rule.yml | 1 + - .../non-uefi/grub2_password/rule.yml | 1 + - .../kernel_config_page_poisoning/rule.yml | 1 - - .../rsyslog_cron_logging/rule.yml | 1 + - .../rule.yml | 2 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rsyslog_remote_access_monitoring/rule.yml | 1 + - .../service_systemd-journald_enabled/rule.yml | 2 +- - .../package_rsyslog-gnutls_installed/rule.yml | 1 + - .../package_rsyslog_installed/rule.yml | 1 + - .../rsyslog_nolisten/rule.yml | 1 + - .../rsyslog_remote_loghost/rule.yml | 1 + - .../logging/service_rsyslog_enabled/rule.yml | 1 + - .../firewalld-backend/rule.yml | 1 + - .../package_firewalld_installed/rule.yml | 1 + - .../service_firewalld_enabled/rule.yml | 1 + - .../configure_firewalld_ports/rule.yml | 1 + - .../rule.yml | 1 + - .../libreswan_approved_tunnels/rule.yml | 1 + - .../package_libreswan_installed/rule.yml | 5 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../sysctl_net_ipv4_tcp_syncookies/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../kernel_module_atm_disabled/rule.yml | 1 + - .../kernel_module_can_disabled/rule.yml | 1 + - .../rule.yml | 1 + - .../kernel_module_sctp_disabled/rule.yml | 1 + - .../kernel_module_tipc_disabled/rule.yml | 1 + - .../kernel_module_bluetooth_disabled/rule.yml | 5 +- - .../wireless_disable_interfaces/rule.yml | 1 + - .../rule.yml | 1 + - .../network/network_sniffer_disabled/rule.yml | 1 + - .../networkmanager_dns_mode/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../file_permissions_ungroupowned/rule.yml | 1 + - .../files/no_files_unowned_by_user/rule.yml | 1 + - .../file_groupowner_backup_etc_group/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../file_groupowner_etc_group/rule.yml | 1 + - .../file_groupowner_etc_gshadow/rule.yml | 1 + - .../file_groupowner_etc_passwd/rule.yml | 1 + - .../file_groupowner_etc_shadow/rule.yml | 1 + - .../file_owner_backup_etc_group/rule.yml | 1 + - .../file_owner_backup_etc_gshadow/rule.yml | 1 + - .../file_owner_backup_etc_passwd/rule.yml | 1 + - .../file_owner_backup_etc_shadow/rule.yml | 1 + - .../file_owner_etc_group/rule.yml | 1 + - .../file_owner_etc_gshadow/rule.yml | 1 + - .../file_owner_etc_passwd/rule.yml | 1 + - .../file_owner_etc_shadow/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../file_permissions_etc_group/rule.yml | 2 +- - .../file_permissions_etc_gshadow/rule.yml | 1 + - .../file_permissions_etc_passwd/rule.yml | 1 + - .../file_permissions_etc_shadow/rule.yml | 1 + - .../file_groupowner_var_log/rule.yml | 1 + - .../file_groupowner_var_log_messages/rule.yml | 1 + - .../file_owner_var_log/rule.yml | 1 + - .../file_owner_var_log_messages/rule.yml | 1 + - .../file_permissions_var_log/rule.yml | 1 + - .../rule.yml | 1 + - .../dir_group_ownership_library_dirs/rule.yml | 1 + - .../dir_ownership_library_dirs/rule.yml | 1 + - .../dir_permissions_library_dirs/rule.yml | 1 + - .../rule.yml | 1 + - .../file_ownership_binary_dirs/rule.yml | 3 +- - .../file_ownership_library_dirs/rule.yml | 1 + - .../file_permissions_binary_dirs/rule.yml | 1 + - .../file_permissions_library_dirs/rule.yml | 1 + - .../rule.yml | 1 + - .../sysctl_fs_protected_hardlinks/rule.yml | 1 + - .../sysctl_fs_protected_symlinks/rule.yml | 1 + - .../kernel_module_cramfs_disabled/rule.yml | 1 + - .../rule.yml | 1 + - .../mounting/service_autofs_disabled/rule.yml | 1 + - .../mount_option_boot_efi_nosuid/rule.yml | 1 + - .../mount_option_boot_nodev/rule.yml | 1 + - .../mount_option_boot_nosuid/rule.yml | 1 + - .../mount_option_dev_shm_nodev/rule.yml | 1 + - .../mount_option_dev_shm_noexec/rule.yml | 1 + - .../mount_option_dev_shm_nosuid/rule.yml | 1 + - .../mount_option_home_nodev/rule.yml | 1 + - .../mount_option_home_noexec/rule.yml | 1 + - .../mount_option_home_nosuid/rule.yml | 3 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 3 +- - .../rule.yml | 1 + - .../mount_option_tmp_nodev/rule.yml | 1 + - .../mount_option_tmp_noexec/rule.yml | 1 + - .../mount_option_tmp_nosuid/rule.yml | 1 + - .../mount_option_var_log_audit_nodev/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../mount_option_var_log_nodev/rule.yml | 1 + - .../mount_option_var_log_noexec/rule.yml | 1 + - .../mount_option_var_log_nosuid/rule.yml | 1 + - .../mount_option_var_nodev/rule.yml | 1 + - .../mount_option_var_tmp_nodev/rule.yml | 1 + - .../mount_option_var_tmp_noexec/rule.yml | 1 + - .../mount_option_var_tmp_nosuid/rule.yml | 1 + - .../coredump_disable_backtraces/rule.yml | 1 + - .../coredump_disable_storage/rule.yml | 1 + - .../disable_users_coredumps/rule.yml | 1 + - .../rule.yml | 1 + - .../sysctl_kernel_exec_shield/rule.yml | 1 + - .../sysctl_kernel_kptr_restrict/rule.yml | 1 + - .../sysctl_kernel_randomize_va_space/rule.yml | 1 + - .../grub2_page_poison_argument/rule.yml | 1 + - .../grub2_slub_debug_argument/rule.yml | 1 + - .../sysctl_kernel_core_pattern/rule.yml | 1 + - .../sysctl_kernel_dmesg_restrict/rule.yml | 1 + - .../rule.yml | 2 +- - .../rule.yml | 1 + - .../rule.yml | 1 + - .../sysctl_kernel_yama_ptrace_scope/rule.yml | 1 + - .../sysctl_net_core_bpf_jit_harden/rule.yml | 1 + - .../sysctl_user_max_user_namespaces/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../selinux_all_devicefiles_labeled/rule.yml | 1 + - .../selinux/selinux_policytype/rule.yml | 1 + - .../system/selinux/selinux_state/rule.yml | 1 + - .../encrypt_partitions/rule.yml | 1 + - .../partition_for_home/rule.yml | 1 + - .../partition_for_tmp/rule.yml | 1 + - .../partition_for_var/rule.yml | 1 + - .../partition_for_var_log/rule.yml | 1 + - .../partition_for_var_log_audit/rule.yml | 1 + - .../partition_for_var_tmp/rule.yml | 1 + - .../gnome/dconf_db_up_to_date/rule.yml | 3 + - .../rule.yml | 1 + - .../dconf_gnome_disable_user_list/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../dconf_gnome_disable_autorun/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 3 + - .../rule.yml | 1 + - .../installed_OS_is_vendor_supported/rule.yml | 1 + - .../configure_bind_crypto_policy/rule.yml | 1 + - .../crypto/configure_crypto_policy/rule.yml | 1 + - .../configure_kerberos_crypto_policy/rule.yml | 1 + - .../rule.yml | 1 + - .../configure_openssl_crypto_policy/rule.yml | 1 + - .../rule.yml | 1 + - .../configure_ssh_crypto_policy/rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../rule.yml | 1 + - .../agent_mfetpd_running/rule.yml | 1 + - .../package_mcafeetp_installed/rule.yml | 1 + - .../fips/enable_dracut_fips_module/rule.yml | 1 + - .../integrity/fips/enable_fips_mode/rule.yml | 1 + - .../fips/sysctl_crypto_fips_enabled/rule.yml | 1 + - .../aide/aide_check_audit_tools/rule.yml | 1 + - .../aide/aide_periodic_cron_checking/rule.yml | 1 + - .../aide/aide_scan_notification/rule.yml | 1 + - .../aide/aide_use_fips_hashes/rule.yml | 1 + - .../aide/aide_verify_acls/rule.yml | 1 + - .../aide/aide_verify_ext_attributes/rule.yml | 1 + - .../file_audit_tools_group_ownership/rule.yml | 1 + - .../aide/file_audit_tools_ownership/rule.yml | 1 + - .../file_audit_tools_permissions/rule.yml | 1 + - .../aide/package_aide_installed/rule.yml | 1 + - .../rpm_verify_hashes/rule.yml | 1 + - .../sudo/package_sudo_installed/rule.yml | 1 + - .../sudo/sudo_remove_no_authenticate/rule.yml | 1 + - .../sudo/sudo_remove_nopasswd/rule.yml | 1 + - .../sudo_require_reauthentication/rule.yml | 1 + - .../rule.yml | 1 + - .../sudo/sudoers_validate_passwd/rule.yml | 1 + - .../package_gnutls-utils_installed/rule.yml | 1 + - .../package_gssproxy_removed/rule.yml | 1 + - .../package_iprutils_removed/rule.yml | 1 + - .../package_nss-tools_installed/rule.yml | 1 + - .../package_rng-tools_installed/rule.yml | 1 + - .../rule.yml | 1 + - .../package_tuned_removed/rule.yml | 1 + - .../clean_components_post_updating/rule.yml | 1 + - .../rule.yml | 1 + - .../ensure_gpgcheck_local_packages/rule.yml | 1 + - .../ensure_gpgcheck_never_disabled/rule.yml | 1 + - .../ensure_redhat_gpgkey_installed/rule.yml | 1 + - .../security_patches_up_to_date/rule.yml | 2 +- - products/rhel9/profiles/stig.profile | 11 +- - products/rhel9/profiles/stig_gui.profile | 20 +- - .../disa-stig-rhel9-v1r1-xccdf-manual.xml | 7018 +++++++++++++++++ - tests/CMakeLists.txt | 27 +- - utils/controlrefcheck.py | 7 + - utils/refchecker.py | 39 +- - 506 files changed, 11855 insertions(+), 61 deletions(-) - create mode 100644 controls/stig_rhel9.yml - create mode 100644 shared/references/disa-stig-rhel9-v1r1-xccdf-manual.xml - -diff --git a/controls/stig_rhel9.yml b/controls/stig_rhel9.yml -new file mode 100644 -index 0000000000..0966ebb6fc ---- /dev/null -+++ b/controls/stig_rhel9.yml -@@ -0,0 +1,4236 @@ -+policy: 'Red Hat Enterprise Linux 9 Security Technical Implementation Guide' -+title: 'Red Hat Enterprise Linux 9 Security Technical Implementation Guide' -+id: stig_rhel9 -+source: https://public.cyber.mil/stigs/downloads/ -+version: V1R1 -+levels: -+ - id: high -+ - id: medium -+ - id: low -+controls: -+ - id: needed_rules -+ levels: -+ - medium -+ rules: -+ - enable_authselect -+ - var_authselect_profile=sssd -+ -+ - id: RHEL-09-211010 -+ levels: -+ - high -+ title: RHEL 9 must be a vendor-supported release. -+ rules: -+ - installed_OS_is_vendor_supported -+ status: automated -+ -+ - id: RHEL-09-211015 -+ levels: -+ - medium -+ title: -+ RHEL 9 vendor packaged system security patches and updates must be installed -+ and up to date. -+ rules: -+ - security_patches_up_to_date -+ status: automated -+ -+ - id: RHEL-09-211020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner -+ before granting local or remote access to the system via a command line user logon. -+ rules: -+ - banner_etc_issue -+ - login_banner_text=dod_banners -+ status: automated -+ -+ - id: RHEL-09-211025 -+ levels: -+ - medium -+ title: RHEL 9 must implement the Endpoint Security for Linux Threat Prevention tool. -+ rules: -+ - package_mcafeetp_installed -+ - agent_mfetpd_running -+ status: automated -+ -+ - id: RHEL-09-211030 -+ levels: -+ - medium -+ title: -+ The graphical display manager must not be the default target on RHEL 9 unless -+ approved. -+ rules: -+ - xwindows_runlevel_target -+ status: automated -+ -+ - id: RHEL-09-211035 -+ levels: -+ - low -+ title: -+ RHEL 9 must enable the hardware random number generator entropy gatherer -+ service. -+ related_rules: -+ - service_rngd_enabled # This rule is causing test failures, See https://github.com/ComplianceAsCode/content/pull/10153 -+ status: pending -+ -+ - id: RHEL-09-211040 -+ levels: -+ - medium -+ title: RHEL 9 systemd-journald service must be enabled. -+ rules: -+ - service_systemd-journald_enabled -+ status: automated -+ -+ - id: RHEL-09-211045 -+ levels: -+ - high -+ title: The systemd Ctrl-Alt-Delete burst key sequence in RHEL 9 must be disabled. -+ rules: -+ - disable_ctrlaltdel_burstaction -+ status: automated -+ -+ - id: RHEL-09-211050 -+ levels: -+ - high -+ title: The x86 Ctrl-Alt-Delete key sequence must be disabled on RHEL 9. -+ rules: -+ - disable_ctrlaltdel_reboot -+ status: automated -+ -+ - id: RHEL-09-211055 -+ levels: -+ - medium -+ title: RHEL 9 debug-shell systemd service must be disabled. -+ status: automated -+ rules: -+ - service_debug-shell_disabled -+ -+ - id: RHEL-09-212010 -+ levels: -+ - medium -+ title: RHEL 9 must require a boot loader superuser password. -+ rules: -+ - grub2_password -+ status: automated -+ -+ - id: RHEL-09-212015 -+ levels: -+ - medium -+ title: RHEL 9 must disable the ability of systemd to spawn an interactive boot process. -+ rules: -+ - grub2_disable_interactive_boot -+ status: automated -+ -+ - id: RHEL-09-212020 -+ levels: -+ - high -+ title: -+ RHEL 9 must require a unique superusers name upon booting into single-user -+ and maintenance modes. -+ rules: -+ - grub2_admin_username -+ status: automated -+ -+ - id: RHEL-09-212025 -+ levels: -+ - medium -+ title: RHEL 9 /boot/grub2/grub.cfg file must be group-owned by root. -+ rules: -+ - file_groupowner_grub2_cfg -+ status: automated -+ -+ - id: RHEL-09-212030 -+ levels: -+ - medium -+ title: RHEL 9 /boot/grub2/grub.cfg file must be owned by root. -+ rules: -+ - file_owner_grub2_cfg -+ status: automated -+ -+ - id: RHEL-09-212035 -+ levels: -+ - medium -+ title: RHEL 9 must disable virtual system calls. -+ rules: -+ - grub2_vsyscall_argument -+ status: automated -+ -+ - id: RHEL-09-212040 -+ levels: -+ - medium -+ title: RHEL 9 must clear the page allocator to prevent use-after-free attacks. -+ rules: -+ - grub2_page_poison_argument -+ status: automated -+ -+ - id: RHEL-09-212045 -+ levels: -+ - medium -+ title: RHEL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks. -+ rules: -+ - grub2_slub_debug_argument -+ status: automated -+ -+ - id: RHEL-09-212050 -+ levels: -+ - low -+ title: RHEL 9 must enable mitigations against processor-based vulnerabilities. -+ rules: -+ - grub2_pti_argument -+ status: automated -+ -+ - id: RHEL-09-212055 -+ levels: -+ - low -+ title: RHEL 9 must enable auditing of processes that start prior to the audit daemon. -+ rules: -+ - grub2_audit_argument -+ status: automated -+ -+ - id: RHEL-09-213010 -+ levels: -+ - medium -+ title: RHEL 9 must restrict access to the kernel message buffer. -+ rules: -+ - sysctl_kernel_dmesg_restrict -+ status: automated -+ -+ - id: RHEL-09-213015 -+ levels: -+ - medium -+ title: RHEL 9 must prevent kernel profiling by nonprivileged users. -+ rules: -+ - sysctl_kernel_perf_event_paranoid -+ status: automated -+ -+ - id: RHEL-09-213020 -+ levels: -+ - medium -+ title: RHEL 9 must prevent the loading of a new kernel for later execution. -+ rules: -+ - sysctl_kernel_kexec_load_disabled -+ status: automated -+ -+ - id: RHEL-09-213025 -+ levels: -+ - medium -+ title: RHEL 9 must restrict exposed kernel pointer addresses access. -+ rules: -+ - sysctl_kernel_kptr_restrict -+ status: automated -+ -+ - id: RHEL-09-213030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enable kernel parameters to enforce discretionary access control -+ on hardlinks. -+ rules: -+ - sysctl_fs_protected_hardlinks -+ status: automated -+ -+ - id: RHEL-09-213035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enable kernel parameters to enforce discretionary access control -+ on symlinks. -+ rules: -+ - sysctl_fs_protected_symlinks -+ status: automated -+ -+ - id: RHEL-09-213040 -+ levels: -+ - medium -+ title: RHEL 9 must disable the kernel.core_pattern. -+ rules: -+ - sysctl_kernel_core_pattern -+ status: automated -+ -+ - id: RHEL-09-213045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured to disable the Asynchronous Transfer Mode kernel -+ module. -+ rules: -+ - kernel_module_atm_disabled -+ status: automated -+ -+ - id: RHEL-09-213050 -+ levels: -+ - medium -+ title: RHEL 9 must be configured to disable the Controller Area Network kernel module. -+ rules: -+ - kernel_module_can_disabled -+ status: automated -+ -+ - id: RHEL-09-213055 -+ levels: -+ - medium -+ title: RHEL 9 must be configured to disable the FireWire kernel module. -+ rules: -+ - kernel_module_firewire-core_disabled -+ status: automated -+ -+ - id: RHEL-09-213060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the Stream Control Transmission Protocol (SCTP) kernel -+ module. -+ rules: -+ - kernel_module_sctp_disabled -+ status: automated -+ -+ - id: RHEL-09-213065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the Transparent Inter Process Communication (TIPC) kernel -+ module. -+ rules: -+ - kernel_module_tipc_disabled -+ status: automated -+ -+ - id: RHEL-09-213070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must implement address space layout randomization (ASLR) to protect -+ its memory from unauthorized code execution. -+ rules: -+ - sysctl_kernel_randomize_va_space -+ status: automated -+ -+ - id: RHEL-09-213075 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable access to network bpf system call from nonprivileged -+ processes. -+ rules: -+ - sysctl_kernel_unprivileged_bpf_disabled -+ status: automated -+ -+ - id: RHEL-09-213080 -+ levels: -+ - medium -+ title: RHEL 9 must restrict usage of ptrace to descendant processes. -+ rules: -+ - sysctl_kernel_yama_ptrace_scope -+ status: automated -+ -+ - id: RHEL-09-213085 -+ levels: -+ - medium -+ title: RHEL 9 must disable core dump backtraces. -+ rules: -+ - coredump_disable_backtraces -+ status: automated -+ -+ - id: RHEL-09-213090 -+ levels: -+ - medium -+ title: RHEL 9 must disable storing core dumps. -+ rules: -+ - coredump_disable_storage -+ status: automated -+ -+ - id: RHEL-09-213095 -+ levels: -+ - medium -+ title: RHEL 9 must disable core dumps for all users. -+ rules: -+ - disable_users_coredumps -+ status: automated -+ -+ - id: RHEL-09-213100 -+ levels: -+ - medium -+ title: RHEL 9 must disable acquiring, saving, and processing core dumps. -+ rules: -+ - service_systemd-coredump_disabled -+ status: automated -+ -+ - id: RHEL-09-213105 -+ levels: -+ - medium -+ title: RHEL 9 must disable the use of user namespaces. -+ rules: -+ - sysctl_user_max_user_namespaces -+ status: automated -+ -+ - id: RHEL-09-213110 -+ levels: -+ - medium -+ title: -+ RHEL 9 must implement nonexecutable data to protect its memory from unauthorized -+ code execution. -+ rules: -+ - sysctl_kernel_exec_shield -+ status: automated -+ -+ - id: RHEL-09-213115 -+ levels: -+ - medium -+ title: The kdump service on RHEL 9 must be disabled. -+ rules: -+ - service_kdump_disabled -+ status: automated -+ -+ - id: RHEL-09-214010 -+ levels: -+ - medium -+ title: RHEL 9 must ensure cryptographic verification of vendor software packages. -+ rules: -+ - ensure_redhat_gpgkey_installed -+ status: automated -+ -+ - id: RHEL-09-214015 -+ levels: -+ - high -+ title: -+ RHEL 9 must check the GPG signature of software packages originating from -+ external software repositories before installation. -+ rules: -+ - ensure_gpgcheck_globally_activated -+ status: automated -+ -+ - id: RHEL-09-214020 -+ levels: -+ - high -+ title: -+ RHEL 9 must check the GPG signature of locally installed software packages -+ before installation. -+ rules: -+ - ensure_gpgcheck_local_packages -+ status: automated -+ -+ - id: RHEL-09-214025 -+ levels: -+ - high -+ title: RHEL 9 must have GPG signature verification enabled for all software repositories. -+ rules: -+ - ensure_gpgcheck_never_disabled -+ status: automated -+ -+ - id: RHEL-09-214030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that the cryptographic hashes of system files -+ match vendor values. -+ related_rules: -+ - rpm_verify_hashes # Due to crypto policies this cannot be selected at this time -+ status: pending -+ -+ - id: RHEL-09-214035 -+ levels: -+ - low -+ title: -+ RHEL 9 must remove all software components after updated versions have been -+ installed. -+ rules: -+ - clean_components_post_updating -+ status: automated -+ -+ - id: RHEL-09-215010 -+ levels: -+ - medium -+ title: RHEL 9 subscription-manager package must be installed. -+ rules: -+ - package_subscription-manager_installed -+ status: automated -+ -+ - id: RHEL-09-215015 -+ levels: -+ - high -+ title: RHEL 9 must not have a File Transfer Protocol (FTP) server package installed. -+ rules: -+ - package_vsftpd_removed -+ status: automated -+ -+ - id: RHEL-09-215020 -+ levels: -+ - medium -+ title: RHEL 9 must not have the sendmail package installed. -+ rules: -+ - package_sendmail_removed -+ status: automated -+ -+ - id: RHEL-09-215025 -+ levels: -+ - medium -+ title: RHEL 9 must not have the nfs-utils package installed. -+ rules: -+ - package_nfs-utils_removed -+ status: automated -+ -+ - id: RHEL-09-215030 -+ levels: -+ - medium -+ title: RHEL 9 must not have the ypserv package installed. -+ rules: -+ - package_ypserv_removed -+ status: automated -+ -+ - id: RHEL-09-215035 -+ levels: -+ - medium -+ title: RHEL 9 must not have the rsh-server package installed. -+ rules: -+ - package_rsh-server_removed -+ status: automated -+ -+ - id: RHEL-09-215040 -+ levels: -+ - medium -+ title: RHEL 9 must not have the telnet-server package installed. -+ rules: -+ - package_telnet-server_removed -+ status: automated -+ -+ - id: RHEL-09-215045 -+ levels: -+ - medium -+ title: RHEL 9 must not have the gssproxy package installed. -+ rules: -+ - package_gssproxy_removed -+ status: automated -+ -+ - id: RHEL-09-215050 -+ levels: -+ - medium -+ title: RHEL 9 must not have the iprutils package installed. -+ rules: -+ - package_iprutils_removed -+ status: automated -+ -+ - id: RHEL-09-215055 -+ levels: -+ - medium -+ title: RHEL 9 must not have the tuned package installed. -+ rules: -+ - package_tuned_removed -+ status: automated -+ -+ - id: RHEL-09-215060 -+ levels: -+ - high -+ title: -+ RHEL 9 must not have a Trivial File Transfer Protocol (TFTP) server package -+ installed. -+ rules: -+ - package_tftp-server_removed -+ status: automated -+ -+ - id: RHEL-09-215065 -+ levels: -+ - medium -+ title: RHEL 9 must not have the quagga package installed. -+ rules: -+ - package_quagga_removed -+ status: automated -+ -+ - id: RHEL-09-215070 -+ levels: -+ - medium -+ title: A graphical display manager must not be installed on RHEL 9 unless approved. -+ rules: -+ - xwindows_remove_packages -+ status: automated -+ -+ - id: RHEL-09-215075 -+ levels: -+ - medium -+ title: RHEL 9 must have the openssl-pkcs11 package installed. -+ rules: -+ - install_smartcard_packages -+ status: automated -+ -+ - id: RHEL-09-215080 -+ levels: -+ - medium -+ title: RHEL 9 must have the gnutls-utils package installed. -+ rules: -+ - package_gnutls-utils_installed -+ status: automated -+ -+ - id: RHEL-09-215085 -+ levels: -+ - medium -+ title: RHEL 9 must have the nss-tools package installed. -+ rules: -+ - package_nss-tools_installed -+ status: automated -+ -+ - id: RHEL-09-215090 -+ levels: -+ - medium -+ title: RHEL 9 must have the rng-tools package installed. -+ rules: -+ - package_rng-tools_installed -+ status: automated -+ -+ - id: RHEL-09-215095 -+ levels: -+ - medium -+ title: RHEL 9 must have the s-nail package installed. -+ rules: -+ - package_s-nail_installed -+ status: automated -+ -+ - id: RHEL-09-231010 -+ levels: -+ - medium -+ title: -+ A separate RHEL 9 file system must be used for user home directories (such -+ as /home or an equivalent). -+ rules: -+ - partition_for_home -+ status: automated -+ -+ - id: RHEL-09-231015 -+ levels: -+ - medium -+ title: RHEL 9 must use a separate file system for /tmp. -+ rules: -+ - partition_for_tmp -+ status: automated -+ -+ - id: RHEL-09-231020 -+ levels: -+ - low -+ title: RHEL 9 must use a separate file system for /var. -+ rules: -+ - partition_for_var -+ status: automated -+ -+ - id: RHEL-09-231025 -+ levels: -+ - low -+ title: RHEL 9 must use a separate file system for /var/log. -+ rules: -+ - partition_for_var_log -+ status: automated -+ -+ - id: RHEL-09-231030 -+ levels: -+ - low -+ title: RHEL 9 must use a separate file system for the system audit data path. -+ rules: -+ - partition_for_var_log_audit -+ status: automated -+ -+ - id: RHEL-09-231035 -+ levels: -+ - medium -+ title: RHEL 9 must use a separate file system for /var/tmp. -+ rules: -+ - partition_for_var_tmp -+ status: automated -+ -+ - id: RHEL-09-231040 -+ levels: -+ - medium -+ title: RHEL 9 file system automount function must be disabled unless required. -+ rules: -+ - service_autofs_disabled -+ status: automated -+ -+ - id: RHEL-09-231045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent device files from being interpreted on file systems that -+ contain user home directories. -+ rules: -+ - mount_option_home_nodev -+ status: automated -+ -+ - id: RHEL-09-231050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent files with the setuid and setgid bit set from being executed -+ on file systems that contain user home directories. -+ rules: -+ - mount_option_home_nosuid -+ status: automated -+ -+ - id: RHEL-09-231055 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent code from being executed on file systems that contain -+ user home directories. -+ rules: -+ - mount_option_home_noexec -+ status: automated -+ -+ - id: RHEL-09-231060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that the Network File System (NFS) is configured -+ to use RPCSEC_GSS. -+ rules: -+ - mount_option_krb_sec_remote_filesystems -+ status: automated -+ -+ - id: RHEL-09-231065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent special devices on file systems that are imported via -+ Network File System (NFS). -+ rules: -+ - mount_option_nodev_remote_filesystems -+ status: automated -+ -+ - id: RHEL-09-231070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent code from being executed on file systems that are imported -+ via Network File System (NFS). -+ rules: -+ - mount_option_noexec_remote_filesystems -+ status: automated -+ -+ - id: RHEL-09-231075 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent files with the setuid and setgid bit set from being executed -+ on file systems that are imported via Network File System (NFS). -+ rules: -+ - mount_option_nosuid_remote_filesystems -+ status: automated -+ -+ - id: RHEL-09-231080 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent code from being executed on file systems that are used -+ with removable media. -+ rules: -+ - mount_option_noexec_removable_partitions -+ status: automated -+ -+ - id: RHEL-09-231085 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent special devices on file systems that are used with removable -+ media. -+ rules: -+ - mount_option_nodev_removable_partitions -+ status: automated -+ -+ - id: RHEL-09-231090 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent files with the setuid and setgid bit set from being executed -+ on file systems that are used with removable media. -+ rules: -+ - mount_option_nosuid_removable_partitions -+ status: automated -+ -+ - id: RHEL-09-231095 -+ levels: -+ - medium -+ title: RHEL 9 must mount /boot with the nodev option. -+ rules: -+ - mount_option_boot_nodev -+ status: automated -+ -+ - id: RHEL-09-231100 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent files with the setuid and setgid bit set from being executed -+ on the /boot directory. -+ rules: -+ - mount_option_boot_nosuid -+ status: automated -+ -+ - id: RHEL-09-231105 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent files with the setuid and setgid bit set from being executed -+ on the /boot/efi directory. -+ rules: -+ - mount_option_boot_efi_nosuid -+ status: automated -+ -+ - id: RHEL-09-231110 -+ levels: -+ - medium -+ title: RHEL 9 must mount /dev/shm with the nodev option. -+ rules: -+ - mount_option_dev_shm_nodev -+ status: automated -+ -+ - id: RHEL-09-231115 -+ levels: -+ - medium -+ title: RHEL 9 must mount /dev/shm with the noexec option. -+ rules: -+ - mount_option_dev_shm_noexec -+ status: automated -+ -+ - id: RHEL-09-231120 -+ levels: -+ - medium -+ title: RHEL 9 must mount /dev/shm with the nosuid option. -+ rules: -+ - mount_option_dev_shm_nosuid -+ status: automated -+ -+ - id: RHEL-09-231125 -+ levels: -+ - medium -+ title: RHEL 9 must mount /tmp with the nodev option. -+ rules: -+ - mount_option_tmp_nodev -+ status: automated -+ -+ - id: RHEL-09-231130 -+ levels: -+ - medium -+ title: RHEL 9 must mount /tmp with the noexec option. -+ rules: -+ - mount_option_tmp_noexec -+ status: automated -+ -+ - id: RHEL-09-231135 -+ levels: -+ - medium -+ title: RHEL 9 must mount /tmp with the nosuid option. -+ rules: -+ - mount_option_tmp_nosuid -+ status: automated -+ -+ - id: RHEL-09-231140 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var with the nodev option. -+ rules: -+ - mount_option_var_nodev -+ status: automated -+ -+ - id: RHEL-09-231145 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log with the nodev option. -+ rules: -+ - mount_option_var_log_nodev -+ status: automated -+ -+ - id: RHEL-09-231150 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log with the noexec option. -+ rules: -+ - mount_option_var_log_noexec -+ status: automated -+ -+ - id: RHEL-09-231155 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log with the nosuid option. -+ rules: -+ - mount_option_var_log_nosuid -+ status: automated -+ -+ - id: RHEL-09-231160 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log/audit with the nodev option. -+ rules: -+ - mount_option_var_log_audit_nodev -+ status: automated -+ -+ - id: RHEL-09-231165 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log/audit with the noexec option. -+ rules: -+ - mount_option_var_log_audit_noexec -+ status: automated -+ -+ - id: RHEL-09-231170 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/log/audit with the nosuid option. -+ rules: -+ - mount_option_var_log_audit_nosuid -+ status: automated -+ -+ - id: RHEL-09-231175 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/tmp with the nodev option. -+ rules: -+ - mount_option_var_tmp_nodev -+ status: automated -+ -+ - id: RHEL-09-231180 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/tmp with the noexec option. -+ rules: -+ - mount_option_var_tmp_noexec -+ status: automated -+ -+ - id: RHEL-09-231185 -+ levels: -+ - medium -+ title: RHEL 9 must mount /var/tmp with the nosuid option. -+ rules: -+ - mount_option_var_tmp_nosuid -+ status: automated -+ -+ - id: RHEL-09-231190 -+ levels: -+ - high -+ title: -+ RHEL 9 local disk partitions must implement cryptographic mechanisms to prevent -+ unauthorized disclosure or modification of all information that requires at rest -+ protection. -+ rules: -+ - encrypt_partitions -+ status: automated -+ -+ - id: RHEL-09-231195 -+ levels: -+ - low -+ title: RHEL 9 must disable mounting of cramfs. -+ rules: -+ - kernel_module_cramfs_disabled -+ status: automated -+ -+ - id: RHEL-09-231200 -+ levels: -+ - medium -+ title: RHEL 9 must prevent special devices on non-root local partitions. -+ rules: -+ - mount_option_nodev_nonroot_local_partitions -+ status: automated -+ -+ - id: RHEL-09-232010 -+ levels: -+ - medium -+ title: RHEL 9 system commands must have mode 755 or less permissive. -+ rules: -+ - file_permissions_binary_dirs -+ status: automated -+ -+ - id: RHEL-09-232015 -+ levels: -+ - medium -+ title: RHEL 9 library directories must have mode 755 or less permissive. -+ rules: -+ - dir_permissions_library_dirs -+ status: automated -+ -+ - id: RHEL-09-232020 -+ levels: -+ - medium -+ title: RHEL 9 library files must have mode 755 or less permissive. -+ rules: -+ - file_permissions_library_dirs -+ status: automated -+ -+ - id: RHEL-09-232025 -+ levels: -+ - medium -+ title: RHEL 9 /var/log directory must have mode 0755 or less permissive. -+ rules: -+ - file_permissions_var_log -+ status: automated -+ -+ - id: RHEL-09-232030 -+ levels: -+ - medium -+ title: RHEL 9 /var/log/messages file must have mode 0640 or less permissive. -+ rules: -+ - file_permissions_var_log_messages -+ status: automated -+ -+ - id: RHEL-09-232035 -+ levels: -+ - medium -+ title: RHEL 9 audit tools must have a mode of 0755 or less permissive. -+ rules: -+ - file_audit_tools_permissions -+ status: automated -+ -+ - id: RHEL-09-232040 -+ levels: -+ - medium -+ title: RHEL 9 cron configuration directories must have a mode of 0700 or less permissive. -+ rules: -+ - file_permissions_cron_d -+ - file_permissions_cron_daily -+ - file_permissions_cron_hourly -+ - file_permissions_cron_monthly -+ - file_permissions_cron_weekly -+ status: automated -+ -+ - id: RHEL-09-232045 -+ levels: -+ - medium -+ title: All RHEL 9 local initialization files must have mode 0740 or less permissive. -+ rules: -+ - file_permission_user_init_files -+ status: automated -+ -+ - id: RHEL-09-232050 -+ levels: -+ - medium -+ title: -+ All RHEL 9 local interactive user home directories must have mode 0750 or -+ less permissive. -+ rules: -+ - file_permissions_home_directories -+ status: automated -+ -+ - id: RHEL-09-232055 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/group file must have mode 0644 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_etc_group -+ status: automated -+ -+ - id: RHEL-09-232060 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/group- file must have mode 0644 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_backup_etc_group -+ status: automated -+ -+ - id: RHEL-09-232065 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/gshadow file must have mode 0000 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232070 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/gshadow- file must have mode 0000 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_backup_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232075 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/passwd file must have mode 0644 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232080 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/passwd- file must have mode 0644 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_backup_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232085 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/shadow- file must have mode 0000 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_backup_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-232090 -+ levels: -+ - medium -+ title: RHEL 9 /etc/group file must be owned by root. -+ rules: -+ - file_owner_etc_group -+ status: automated -+ -+ - id: RHEL-09-232095 -+ levels: -+ - medium -+ title: RHEL 9 /etc/group file must be group-owned by root. -+ rules: -+ - file_groupowner_etc_group -+ status: automated -+ -+ - id: RHEL-09-232100 -+ levels: -+ - medium -+ title: RHEL 9 /etc/group- file must be owned by root. -+ rules: -+ - file_owner_backup_etc_group -+ status: automated -+ -+ - id: RHEL-09-232105 -+ levels: -+ - medium -+ title: RHEL 9 /etc/group- file must be group-owned by root. -+ rules: -+ - file_groupowner_backup_etc_group -+ status: automated -+ -+ - id: RHEL-09-232110 -+ levels: -+ - medium -+ title: RHEL 9 /etc/gshadow file must be owned by root. -+ rules: -+ - file_owner_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232115 -+ levels: -+ - medium -+ title: RHEL 9 /etc/gshadow file must be group-owned by root. -+ rules: -+ - file_groupowner_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232120 -+ levels: -+ - medium -+ title: RHEL 9 /etc/gshadow- file must be owned by root. -+ rules: -+ - file_owner_backup_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232125 -+ levels: -+ - medium -+ title: RHEL 9 /etc/gshadow- file must be group-owned by root. -+ rules: -+ - file_groupowner_backup_etc_gshadow -+ status: automated -+ -+ - id: RHEL-09-232130 -+ levels: -+ - medium -+ title: RHEL 9 /etc/passwd file must be owned by root. -+ rules: -+ - file_owner_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232135 -+ levels: -+ - medium -+ title: RHEL 9 /etc/passwd file must be group-owned by root. -+ rules: -+ - file_groupowner_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232140 -+ levels: -+ - medium -+ title: RHEL 9 /etc/passwd- file must be owned by root. -+ rules: -+ - file_owner_backup_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232145 -+ levels: -+ - medium -+ title: RHEL 9 /etc/passwd- file must be group-owned by root. -+ rules: -+ - file_groupowner_backup_etc_passwd -+ status: automated -+ -+ - id: RHEL-09-232150 -+ levels: -+ - medium -+ title: RHEL 9 /etc/shadow file must be owned by root. -+ rules: -+ - file_owner_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-232155 -+ levels: -+ - medium -+ title: RHEL 9 /etc/shadow file must be group-owned by root. -+ rules: -+ - file_groupowner_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-232160 -+ levels: -+ - medium -+ title: RHEL 9 /etc/shadow- file must be owned by root. -+ rules: -+ - file_owner_backup_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-232165 -+ levels: -+ - medium -+ title: RHEL 9 /etc/shadow- file must be group-owned by root. -+ rules: -+ - file_groupowner_backup_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-232170 -+ levels: -+ - medium -+ title: RHEL 9 /var/log directory must be owned by root. -+ rules: -+ - file_owner_var_log -+ status: automated -+ -+ - id: RHEL-09-232175 -+ levels: -+ - medium -+ title: RHEL 9 /var/log directory must be group-owned by root. -+ rules: -+ - file_groupowner_var_log -+ status: automated -+ -+ - id: RHEL-09-232180 -+ levels: -+ - medium -+ title: RHEL 9 /var/log/messages file must be owned by root. -+ rules: -+ - file_owner_var_log_messages -+ status: automated -+ -+ - id: RHEL-09-232185 -+ levels: -+ - medium -+ title: RHEL 9 /var/log/messages file must be group-owned by root. -+ rules: -+ - file_groupowner_var_log_messages -+ status: automated -+ -+ - id: RHEL-09-232190 -+ levels: -+ - medium -+ title: RHEL 9 system commands must be owned by root. -+ rules: -+ - file_ownership_binary_dirs -+ status: automated -+ -+ - id: RHEL-09-232195 -+ levels: -+ - medium -+ title: RHEL 9 system commands must be group-owned by root or a system account. -+ rules: -+ - file_groupownership_system_commands_dirs -+ status: automated -+ -+ - id: RHEL-09-232200 -+ levels: -+ - medium -+ title: RHEL 9 library files must be owned by root. -+ rules: -+ - file_ownership_library_dirs -+ status: automated -+ -+ - id: RHEL-09-232205 -+ levels: -+ - medium -+ title: RHEL 9 library files must be group-owned by root or a system account. -+ rules: -+ - root_permissions_syslibrary_files -+ status: automated -+ -+ - id: RHEL-09-232210 -+ levels: -+ - medium -+ title: RHEL 9 library directories must be owned by root. -+ rules: -+ - dir_ownership_library_dirs -+ status: automated -+ -+ - id: RHEL-09-232215 -+ levels: -+ - medium -+ title: RHEL 9 library directories must be group-owned by root or a system account. -+ rules: -+ - dir_group_ownership_library_dirs -+ status: automated -+ -+ - id: RHEL-09-232220 -+ levels: -+ - medium -+ title: RHEL 9 audit tools must be owned by root. -+ rules: -+ - file_audit_tools_ownership -+ status: automated -+ -+ - id: RHEL-09-232225 -+ levels: -+ - medium -+ title: RHEL 9 audit tools must be group-owned by root. -+ rules: -+ - file_audit_tools_group_ownership -+ status: automated -+ -+ - id: RHEL-09-232230 -+ levels: -+ - medium -+ title: RHEL 9 cron configuration files directory must be owned by root. -+ rules: -+ - file_owner_cron_d -+ - file_owner_cron_daily -+ - file_owner_cron_hourly -+ - file_owner_cron_monthly -+ - file_owner_cron_weekly -+ - file_owner_crontab -+ - file_owner_cron_deny -+ status: automated -+ -+ - id: RHEL-09-232235 -+ levels: -+ - medium -+ title: RHEL 9 cron configuration files directory must be group-owned by root. -+ rules: -+ - file_groupowner_cron_d -+ - file_groupowner_cron_daily -+ - file_groupowner_cron_hourly -+ - file_groupowner_cron_monthly -+ - file_groupowner_cron_weekly -+ - file_groupowner_crontab -+ - file_groupowner_cron_deny -+ status: automated -+ -+ - id: RHEL-09-232240 -+ levels: -+ - medium -+ title: -+ All RHEL 9 world-writable directories must be owned by root, sys, bin, or -+ an application user. -+ rules: -+ - dir_perms_world_writable_root_owned -+ status: automated -+ -+ - id: RHEL-09-232245 -+ levels: -+ - medium -+ title: A sticky bit must be set on all RHEL 9 public directories. -+ rules: -+ - dir_perms_world_writable_sticky_bits -+ status: automated -+ -+ - id: RHEL-09-232250 -+ levels: -+ - medium -+ title: All RHEL 9 local files and directories must have a valid group owner. -+ rules: -+ - file_permissions_ungroupowned -+ status: automated -+ -+ - id: RHEL-09-232255 -+ levels: -+ - medium -+ title: All RHEL 9 local files and directories must have a valid owner. -+ rules: -+ - no_files_unowned_by_user -+ status: automated -+ -+ - id: RHEL-09-232260 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that all system device files are correctly labeled -+ to prevent unauthorized modification. -+ rules: -+ - selinux_all_devicefiles_labeled -+ status: automated -+ -+ - id: RHEL-09-232265 -+ levels: -+ - medium -+ title: RHEL 9 /etc/crontab file must have mode 0600. -+ rules: -+ - file_permissions_crontab -+ status: automated -+ -+ - id: RHEL-09-232270 -+ levels: -+ - medium -+ title: RHEL 9 /etc/shadow file must have mode 0000 to prevent unauthorized access. -+ rules: -+ - file_permissions_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-251010 -+ levels: -+ - medium -+ title: RHEL 9 must have the firewalld package installed. -+ rules: -+ - package_firewalld_installed -+ status: automated -+ -+ - id: RHEL-09-251015 -+ levels: -+ - medium -+ title: The firewalld service on RHEL 9 must be active. -+ rules: -+ - service_firewalld_enabled -+ status: automated -+ -+ - id: RHEL-09-251020 -+ levels: -+ - medium -+ title: -+ A RHEL 9 firewall must employ a deny-all, allow-by-exception policy for allowing -+ connections to other systems. -+ rules: -+ - configured_firewalld_default_deny -+ status: automated -+ -+ - id: RHEL-09-251025 -+ levels: -+ - medium -+ title: RHEL 9 must control remote access methods. -+ rules: -+ - configure_firewalld_ports -+ status: automated -+ -+ - id: RHEL-09-251030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must protect against or limit the effects of denial-of-service (DoS) -+ attacks by ensuring rate-limiting measures on impacted network interfaces are -+ implemented. -+ rules: -+ - firewalld-backend -+ status: automated -+ -+ - id: RHEL-09-251035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured to prohibit or restrict the use of functions, ports, -+ protocols, and/or services, as defined in the Ports, Protocols, and Services Management -+ (PPSM) Category Assignments List (CAL) and vulnerability assessments. -+ rules: -+ - firewalld_sshd_port_enabled -+ status: automated -+ -+ - id: RHEL-09-251040 -+ levels: -+ - medium -+ title: RHEL 9 network interfaces must not be in promiscuous mode. -+ rules: -+ - network_sniffer_disabled -+ status: automated -+ -+ - id: RHEL-09-251045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enable hardening for the Berkeley Packet Filter just-in-time -+ compiler. -+ rules: -+ - sysctl_net_core_bpf_jit_harden -+ status: automated -+ -+ - id: RHEL-09-252010 -+ levels: -+ - medium -+ title: RHEL 9 must have the chrony package installed. -+ rules: -+ - package_chrony_installed -+ status: automated -+ -+ - id: RHEL-09-252015 -+ levels: -+ - medium -+ title: RHEL 9 chronyd service must be enabled. -+ rules: -+ - service_chronyd_enabled -+ status: automated -+ -+ - id: RHEL-09-252020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must securely compare internal information system clocks at least -+ every 24 hours. -+ rules: -+ - chronyd_or_ntpd_set_maxpoll -+ - chronyd_server_directive -+ - var_time_service_set_maxpoll=18_hours -+ status: automated -+ -+ - id: RHEL-09-252025 -+ levels: -+ - low -+ title: RHEL 9 must disable the chrony daemon from acting as a server. -+ rules: -+ - chronyd_client_only -+ status: automated -+ -+ - id: RHEL-09-252030 -+ levels: -+ - low -+ title: RHEL 9 must disable network management of the chrony daemon. -+ rules: -+ - chronyd_no_chronyc_network -+ status: automated -+ -+ - id: RHEL-09-252035 -+ levels: -+ - medium -+ title: -+ RHEL 9 systems using Domain Name Servers (DNS) resolution must have at least -+ two name servers configured. -+ rules: -+ - network_configure_name_resolution -+ status: automated -+ -+ - id: RHEL-09-252040 -+ levels: -+ - medium -+ title: RHEL 9 must configure a DNS processing mode set be Network Manager. -+ rules: -+ - networkmanager_dns_mode -+ status: automated -+ -+ - id: RHEL-09-252045 -+ levels: -+ - medium -+ title: RHEL 9 must not have unauthorized IP tunnels configured. -+ rules: -+ - libreswan_approved_tunnels -+ status: automated -+ -+ - id: RHEL-09-252050 -+ levels: -+ - medium -+ title: RHEL 9 must be configured to prevent unrestricted mail relaying. -+ rules: -+ - postfix_prevent_unrestricted_relay -+ status: automated -+ -+ - id: RHEL-09-252055 -+ levels: -+ - medium -+ title: -+ If the Trivial File Transfer Protocol (TFTP) server is required, RHEL 9 TFTP -+ daemon must be configured to operate in secure mode. -+ rules: -+ - tftpd_uses_secure_mode -+ status: automated -+ -+ - id: RHEL-09-252060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must forward mail from postmaster to the root account using a postfix -+ alias. -+ rules: -+ - postfix_client_configure_mail_alias_postmaster -+ status: automated -+ -+ - id: RHEL-09-252065 -+ levels: -+ - medium -+ title: RHEL 9 libreswan package must be installed. -+ rules: -+ - package_libreswan_installed -+ status: automated -+ -+ - id: RHEL-09-252070 -+ levels: -+ - high -+ title: There must be no shosts.equiv files on RHEL 9. -+ rules: -+ - no_host_based_files -+ status: automated -+ -+ - id: RHEL-09-252075 -+ levels: -+ - high -+ title: There must be no .shosts files on RHEL 9. -+ rules: -+ - no_user_host_based_files -+ status: automated -+ -+ - id: RHEL-09-253010 -+ levels: -+ - medium -+ title: RHEL 9 must be configured to use TCP syncookies. -+ rules: -+ - sysctl_net_ipv4_tcp_syncookies -+ status: automated -+ -+ - id: RHEL-09-253015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must ignore Internet Protocol version 4 (IPv4) Internet Control Message -+ Protocol (ICMP) redirect messages. -+ rules: -+ - sysctl_net_ipv4_conf_all_accept_redirects -+ status: automated -+ -+ - id: RHEL-09-253020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must not forward Internet Protocol version 4 (IPv4) source-routed -+ packets. -+ rules: -+ - sysctl_net_ipv4_conf_all_accept_source_route -+ status: automated -+ -+ - id: RHEL-09-253025 -+ levels: -+ - medium -+ title: RHEL 9 must log IPv4 packets with impossible addresses. -+ rules: -+ - sysctl_net_ipv4_conf_all_log_martians -+ status: automated -+ -+ - id: RHEL-09-253030 -+ levels: -+ - medium -+ title: RHEL 9 must log IPv4 packets with impossible addresses by default. -+ rules: -+ - sysctl_net_ipv4_conf_default_log_martians -+ status: automated -+ -+ - id: RHEL-09-253035 -+ levels: -+ - medium -+ title: RHEL 9 must use reverse path filtering on all IPv4 interfaces. -+ rules: -+ - sysctl_net_ipv4_conf_all_rp_filter -+ status: automated -+ -+ - id: RHEL-09-253040 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect -+ messages from being accepted. -+ rules: -+ - sysctl_net_ipv4_conf_default_accept_redirects -+ status: automated -+ -+ - id: RHEL-09-253045 -+ levels: -+ - medium -+ title: RHEL 9 must not forward IPv4 source-routed packets by default. -+ rules: -+ - sysctl_net_ipv4_conf_default_accept_source_route -+ status: automated -+ -+ - id: RHEL-09-253050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must use a reverse-path filter for IPv4 network traffic when possible -+ by default. -+ rules: -+ - sysctl_net_ipv4_conf_default_rp_filter -+ status: automated -+ -+ - id: RHEL-09-253055 -+ levels: -+ - medium -+ title: -+ RHEL 9 must not respond to Internet Control Message Protocol (ICMP) echoes -+ sent to a broadcast address. -+ rules: -+ - sysctl_net_ipv4_icmp_echo_ignore_broadcasts -+ status: automated -+ -+ - id: RHEL-09-253060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must limit the number of bogus Internet Control Message Protocol (ICMP) -+ response errors logs. -+ rules: -+ - sysctl_net_ipv4_icmp_ignore_bogus_error_responses -+ status: automated -+ -+ - id: RHEL-09-253065 -+ levels: -+ - medium -+ title: RHEL 9 must not send Internet Control Message Protocol (ICMP) redirects. -+ rules: -+ - sysctl_net_ipv4_conf_all_send_redirects -+ status: automated -+ -+ - id: RHEL-09-253070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must not allow interfaces to perform Internet Control Message Protocol -+ (ICMP) redirects by default. -+ rules: -+ - sysctl_net_ipv4_conf_default_send_redirects -+ status: automated -+ -+ - id: RHEL-09-253075 -+ levels: -+ - medium -+ title: RHEL 9 must not enable IPv4 packet forwarding unless the system is a router. -+ rules: -+ - sysctl_net_ipv4_conf_all_forwarding -+ status: automated -+ -+ - id: RHEL-09-254010 -+ levels: -+ - medium -+ title: RHEL 9 must not accept router advertisements on all IPv6 interfaces. -+ rules: -+ - sysctl_net_ipv6_conf_all_accept_ra -+ status: automated -+ -+ - id: RHEL-09-254015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect -+ messages. -+ rules: -+ - sysctl_net_ipv6_conf_all_accept_redirects -+ status: automated -+ -+ - id: RHEL-09-254020 -+ levels: -+ - medium -+ title: RHEL 9 must not forward IPv6 source-routed packets. -+ rules: -+ - sysctl_net_ipv6_conf_all_accept_source_route -+ status: automated -+ -+ - id: RHEL-09-254025 -+ levels: -+ - medium -+ title: RHEL 9 must not enable IPv6 packet forwarding unless the system is a router. -+ rules: -+ - sysctl_net_ipv6_conf_all_forwarding -+ status: automated -+ -+ - id: RHEL-09-254030 -+ levels: -+ - medium -+ title: RHEL 9 must not accept router advertisements on all IPv6 interfaces by default. -+ rules: -+ - sysctl_net_ipv6_conf_default_accept_ra -+ status: automated -+ -+ - id: RHEL-09-254035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect -+ messages from being accepted. -+ rules: -+ - sysctl_net_ipv6_conf_default_accept_redirects -+ status: automated -+ -+ - id: RHEL-09-254040 -+ levels: -+ - medium -+ title: RHEL 9 must not forward IPv6 source-routed packets by default. -+ rules: -+ - sysctl_net_ipv6_conf_default_accept_source_route -+ status: automated -+ -+ - id: RHEL-09-255010 -+ levels: -+ - medium -+ title: All RHEL 9 networked systems must have SSH installed. -+ rules: -+ - package_openssh-server_installed -+ status: automated -+ -+ - id: RHEL-09-255015 -+ levels: -+ - medium -+ title: -+ All RHEL 9 networked systems must have and implement SSH to protect the confidentiality -+ and integrity of transmitted and received information, as well as information -+ during preparation for transmission. -+ rules: -+ - service_sshd_enabled -+ status: automated -+ -+ - id: RHEL-09-255020 -+ levels: -+ - medium -+ title: RHEL 9 must have the openssh-clients package installed. -+ rules: -+ - package_openssh-clients_installed -+ status: automated -+ -+ - id: RHEL-09-255025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner -+ before granting local or remote access to the system via a SSH logon. -+ rules: -+ - sshd_enable_warning_banner -+ status: automated -+ -+ - id: RHEL-09-255030 -+ levels: -+ - medium -+ title: RHEL 9 must log SSH connection attempts and failures to the server. -+ rules: -+ - sshd_set_loglevel_verbose -+ status: automated -+ -+ - id: RHEL-09-255035 -+ levels: -+ - medium -+ title: RHEL 9 SSHD must accept public key authentication. -+ rules: -+ - sshd_enable_pubkey_auth -+ status: automated -+ -+ - id: RHEL-09-255040 -+ levels: -+ - high -+ title: RHEL 9 SSHD must not allow blank passwords. -+ rules: -+ - sshd_disable_empty_passwords -+ status: automated -+ -+ - id: RHEL-09-255045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must not permit direct logons to the root account using remote access -+ via SSH. -+ rules: -+ - sshd_disable_root_login -+ status: automated -+ -+ - id: RHEL-09-255050 -+ levels: -+ - high -+ title: -+ RHEL 9 must enable the Pluggable Authentication Module (PAM) interface for -+ SSHD. -+ rules: -+ - sshd_enable_pam -+ status: automated -+ -+ - id: RHEL-09-255055 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must be configured to use system-wide crypto policies. -+ rules: -+ - configure_ssh_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-255060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality -+ of SSH client connections. -+ rules: -+ - harden_sshd_ciphers_openssh_conf_crypto_policy -+ - sshd_approved_ciphers=stig_extended -+ status: automated -+ -+ - id: RHEL-09-255065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality -+ of SSH server connections. -+ rules: -+ - harden_sshd_ciphers_opensshserver_conf_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-255070 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH client must be configured to use only Message Authentication Codes -+ (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. -+ status: pending -+ -+ - id: RHEL-09-255075 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH server must be configured to use only Message Authentication Codes -+ (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. -+ status: pending -+ -+ - id: RHEL-09-255080 -+ levels: -+ - medium -+ title: RHEL 9 must not allow a noncertificate trusted host SSH logon to the system. -+ rules: -+ - disable_host_auth -+ status: automated -+ -+ - id: RHEL-09-255085 -+ levels: -+ - medium -+ title: RHEL 9 must not allow users to override SSH environment variables. -+ rules: -+ - sshd_do_not_permit_user_env -+ status: automated -+ -+ - id: RHEL-09-255090 -+ levels: -+ - medium -+ title: -+ RHEL 9 must force a frequent session key renegotiation for SSH connections -+ to the server. -+ rules: -+ - sshd_rekey_limit -+ - var_rekey_limit_size=1G -+ - var_rekey_limit_time=1hour -+ status: automated -+ -+ - id: RHEL-09-255095 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that all network connections associated with -+ SSH traffic terminate after becoming unresponsive. -+ rules: -+ - sshd_set_keepalive -+ status: automated -+ -+ - id: RHEL-09-255100 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that all network connections associated with -+ SSH traffic are terminated after 10 minutes of becoming unresponsive. -+ rules: -+ - sshd_set_idle_timeout -+ - sshd_idle_timeout_value=10_minutes -+ status: automated -+ -+ - id: RHEL-09-255105 -+ levels: -+ - medium -+ title: RHEL 9 SSH server configuration file must be group-owned by root. -+ rules: -+ - file_groupowner_sshd_config -+ status: automated -+ -+ - id: RHEL-09-255110 -+ levels: -+ - medium -+ title: RHEL 9 SSH server configuration file must be owned by root. -+ rules: -+ - file_owner_sshd_config -+ status: automated -+ -+ - id: RHEL-09-255115 -+ levels: -+ - medium -+ title: RHEL 9 SSH server configuration file must have mode 0600 or less permissive. -+ rules: -+ - file_permissions_sshd_config -+ status: automated -+ -+ - id: RHEL-09-255120 -+ levels: -+ - medium -+ title: RHEL 9 SSH private host key files must have mode 0640 or less permissive. -+ rules: -+ - file_permissions_sshd_private_key -+ status: automated -+ -+ - id: RHEL-09-255125 -+ levels: -+ - medium -+ title: RHEL 9 SSH public host key files must have mode 0644 or less permissive. -+ rules: -+ - file_permissions_sshd_pub_key -+ status: automated -+ -+ - id: RHEL-09-255130 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH daemon must not allow compression or must only allow compression -+ after successful authentication. -+ rules: -+ - sshd_disable_compression -+ - var_sshd_disable_compression=no -+ status: automated -+ -+ - id: RHEL-09-255135 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must not allow GSSAPI authentication. -+ rules: -+ - sshd_disable_gssapi_auth -+ status: automated -+ -+ - id: RHEL-09-255140 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must not allow Kerberos authentication. -+ rules: -+ - sshd_disable_kerb_auth -+ status: automated -+ -+ - id: RHEL-09-255145 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must not allow rhosts authentication. -+ rules: -+ - sshd_disable_rhosts -+ status: automated -+ -+ - id: RHEL-09-255150 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must not allow known hosts authentication. -+ rules: -+ - sshd_disable_user_known_hosts -+ status: automated -+ -+ - id: RHEL-09-255155 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must disable remote X connections for interactive users. -+ rules: -+ - sshd_disable_x11_forwarding -+ status: automated -+ -+ - id: RHEL-09-255160 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH daemon must perform strict mode checking of home directory configuration -+ files. -+ rules: -+ - sshd_enable_strictmodes -+ status: automated -+ -+ - id: RHEL-09-255165 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH daemon must display the date and time of the last successful account -+ logon upon an SSH logon. -+ rules: -+ - sshd_print_last_log -+ status: automated -+ -+ - id: RHEL-09-255170 -+ levels: -+ - medium -+ title: RHEL 9 SSH daemon must be configured to use privilege separation. -+ rules: -+ - sshd_use_priv_separation -+ status: automated -+ -+ - id: RHEL-09-255175 -+ levels: -+ - medium -+ title: -+ RHEL 9 SSH daemon must prevent remote hosts from connecting to the proxy -+ display. -+ rules: -+ - sshd_x11_use_localhost -+ status: automated -+ -+ - id: RHEL-09-271010 -+ levels: -+ - medium -+ title: -+ RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner -+ before granting local or remote access to the system via a graphical user logon. -+ rules: -+ - dconf_gnome_banner_enabled -+ status: automated -+ -+ - id: RHEL-09-271015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the banner-message-enable setting -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_banner_enabled -+ status: automated -+ -+ - id: RHEL-09-271020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the graphical user interface automount function unless -+ required. -+ rules: -+ - dconf_gnome_disable_automount_open -+ status: automated -+ -+ - id: RHEL-09-271025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the disabling of the graphical -+ user interface automount function. -+ rules: -+ - dconf_gnome_disable_automount_open -+ status: automated -+ -+ - id: RHEL-09-271030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the graphical user interface autorun function unless -+ required. -+ rules: -+ - dconf_gnome_disable_autorun -+ status: automated -+ -+ - id: RHEL-09-271035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the disabling of the graphical -+ user interface autorun function. -+ rules: -+ - dconf_gnome_disable_autorun -+ status: automated -+ -+ - id: RHEL-09-271040 -+ levels: -+ - high -+ title: -+ RHEL 9 must not allow unattended or automatic logon via the graphical user -+ interface. -+ rules: -+ - gnome_gdm_disable_automatic_login -+ status: automated -+ -+ - id: RHEL-09-271045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be able to initiate directly a session lock for all connection -+ types using smart card when the smart card is removed. -+ rules: -+ - dconf_gnome_lock_screen_on_smartcard_removal -+ status: automated -+ -+ - id: RHEL-09-271050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the disabling of the graphical -+ user smart card removal action. -+ rules: -+ - dconf_gnome_lock_screen_on_smartcard_removal -+ status: automated -+ -+ - id: RHEL-09-271055 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enable a user session lock until that user re-establishes access -+ using established identification and authentication procedures for graphical user -+ sessions. -+ rules: -+ - dconf_gnome_screensaver_lock_enabled -+ status: automated -+ -+ - id: RHEL-09-271060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the screensaver lock-enabled setting -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_screensaver_lock_enabled -+ status: automated -+ -+ - id: RHEL-09-271065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically lock graphical user sessions after 15 minutes of -+ inactivity. -+ rules: -+ - dconf_gnome_screensaver_idle_delay -+ status: automated -+ -+ - id: RHEL-09-271070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the session idle-delay setting -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_session_idle_user_locks -+ status: automated -+ -+ - id: RHEL-09-271075 -+ levels: -+ - medium -+ title: -+ RHEL 9 must initiate a session lock for graphical user interfaces when the -+ screensaver is activated. -+ rules: -+ - dconf_gnome_screensaver_lock_delay -+ status: automated -+ -+ - id: RHEL-09-271080 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the session lock-delay setting -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_screensaver_user_locks -+ status: automated -+ -+ - id: RHEL-09-271085 -+ levels: -+ - medium -+ title: -+ RHEL 9 must conceal, via the session lock, information previously visible -+ on the display with a publicly viewable image. -+ rules: -+ - dconf_gnome_screensaver_mode_blank -+ status: automated -+ -+ - id: RHEL-09-271090 -+ levels: -+ - medium -+ title: RHEL 9 effective dconf policy must match the policy keyfiles. -+ rules: -+ - dconf_db_up_to_date -+ status: automated -+ -+ - id: RHEL-09-271095 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the ability of a user to restart the system from the -+ login screen. -+ rules: -+ - dconf_gnome_disable_restart_shutdown -+ status: automated -+ -+ - id: RHEL-09-271100 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the disable-restart-buttons setting -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_disable_restart_shutdown -+ status: automated -+ -+ - id: RHEL-09-271105 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable the ability of a user to accidentally press Ctrl-Alt-Del -+ and cause a system to shut down or reboot. -+ rules: -+ - dconf_gnome_disable_ctrlaltdel_reboot -+ status: automated -+ -+ - id: RHEL-09-271110 -+ levels: -+ - medium -+ title: -+ RHEL 9 must prevent a user from overriding the Ctrl-Alt-Del sequence settings -+ for the graphical user interface. -+ rules: -+ - dconf_gnome_disable_ctrlaltdel_reboot -+ status: automated -+ -+ - id: RHEL-09-271115 -+ levels: -+ - medium -+ title: RHEL 9 must disable the user list at logon for graphical user interfaces. -+ rules: -+ - dconf_gnome_disable_user_list -+ status: automated -+ -+ - id: RHEL-09-291010 -+ levels: -+ - medium -+ title: RHEL 9 must be configured to disable USB mass storage. -+ rules: -+ - kernel_module_usb-storage_disabled -+ status: automated -+ -+ - id: RHEL-09-291015 -+ levels: -+ - medium -+ title: RHEL 9 must have the USBGuard package installed. -+ rules: -+ - package_usbguard_installed -+ status: automated -+ -+ - id: RHEL-09-291020 -+ levels: -+ - medium -+ title: RHEL 9 must have the USBGuard package enabled. -+ rules: -+ - service_usbguard_enabled -+ status: automated -+ -+ - id: RHEL-09-291025 -+ levels: -+ - low -+ title: RHEL 9 must enable Linux audit logging for the USBGuard daemon. -+ rules: -+ - configure_usbguard_auditbackend -+ status: automated -+ -+ - id: RHEL-09-291030 -+ levels: -+ - medium -+ title: RHEL 9 must block unauthorized peripherals before establishing a connection. -+ rules: -+ - usbguard_generate_policy -+ status: automated -+ -+ - id: RHEL-09-291035 -+ levels: -+ - medium -+ title: RHEL 9 Bluetooth must be disabled. -+ rules: -+ - kernel_module_bluetooth_disabled -+ status: automated -+ -+ - id: RHEL-09-291040 -+ levels: -+ - medium -+ title: RHEL 9 wireless network adapters must be disabled. -+ rules: -+ - wireless_disable_interfaces -+ status: automated -+ -+ - id: RHEL-09-411010 -+ levels: -+ - medium -+ title: -+ RHEL 9 user account passwords for new users or password changes must have -+ a 60-day maximum password lifetime restriction in /etc/login.defs. -+ rules: -+ - accounts_maximum_age_login_defs -+ status: automated -+ -+ - id: RHEL-09-411015 -+ levels: -+ - medium -+ title: -+ RHEL 9 user account passwords must have a 60-day maximum password lifetime -+ restriction. -+ rules: -+ - accounts_password_set_max_life_existing -+ - var_accounts_maximum_age_login_defs=60 -+ status: automated -+ -+ - id: RHEL-09-411020 -+ levels: -+ - medium -+ title: -+ All RHEL 9 local interactive user accounts must be assigned a home directory -+ upon creation. -+ rules: -+ - accounts_have_homedir_login_defs -+ status: automated -+ -+ - id: RHEL-09-411025 -+ levels: -+ - medium -+ title: RHEL 9 must set the umask value to 077 for all local interactive user accounts. -+ rules: -+ - accounts_umask_interactive_users -+ - var_accounts_user_umask=077 -+ status: automated -+ -+ - id: RHEL-09-411030 -+ levels: -+ - medium -+ title: RHEL 9 duplicate User IDs (UIDs) must not exist for interactive users. -+ rules: -+ - account_unique_id -+ status: automated -+ -+ - id: RHEL-09-411035 -+ levels: -+ - medium -+ title: RHEL 9 system accounts must not have an interactive login shell. -+ rules: -+ - no_shelllogin_for_systemaccounts -+ status: automated -+ -+ - id: RHEL-09-411040 -+ levels: -+ - medium -+ title: RHEL 9 must automatically expire temporary accounts within 72 hours. -+ rules: -+ - account_temp_expire_date -+ status: automated -+ -+ - id: RHEL-09-411045 -+ levels: -+ - medium -+ title: All RHEL 9 interactive users must have a primary group that exists. -+ rules: -+ - gid_passwd_group_same -+ status: automated -+ -+ - id: RHEL-09-411050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must disable account identifiers (individuals, groups, roles, and -+ devices) after 35 days of inactivity. -+ rules: -+ - account_disable_post_pw_expiration -+ - var_account_disable_post_pw_expiration=35 -+ status: automated -+ -+ - id: RHEL-09-411055 -+ levels: -+ - medium -+ title: -+ Executable search paths within the initialization files of all local interactive -+ RHEL 9 users must only contain paths that resolve to the system default or the -+ users home directory. -+ rules: -+ - accounts_user_home_paths_only -+ status: automated -+ -+ - id: RHEL-09-411060 -+ levels: -+ - medium -+ title: -+ All RHEL 9 local interactive users must have a home directory assigned in -+ the /etc/passwd file. -+ rules: -+ - accounts_user_interactive_home_directory_defined -+ status: automated -+ -+ - id: RHEL-09-411065 -+ levels: -+ - medium -+ title: -+ All RHEL 9 local interactive user home directories defined in the /etc/passwd -+ file must exist. -+ rules: -+ - accounts_user_interactive_home_directory_exists -+ status: automated -+ -+ - id: RHEL-09-411070 -+ levels: -+ - medium -+ title: -+ All RHEL 9 local interactive user home directories must be group-owned by -+ the home directory owner's primary group. -+ rules: -+ - file_groupownership_home_directories -+ status: automated -+ -+ - id: RHEL-09-411075 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically lock an account when three unsuccessful logon attempts -+ occur. -+ rules: -+ - accounts_passwords_pam_faillock_deny -+ - var_accounts_passwords_pam_faillock_deny=3 -+ status: automated -+ -+ - id: RHEL-09-411080 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically lock the root account until the root account is -+ released by an administrator when three unsuccessful logon attempts occur during -+ a 15-minute time period. -+ rules: -+ - accounts_passwords_pam_faillock_deny_root -+ status: automated -+ -+ - id: RHEL-09-411085 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically lock an account when three unsuccessful logon attempts -+ occur during a 15-minute time period. -+ rules: -+ - accounts_passwords_pam_faillock_interval -+ - var_accounts_passwords_pam_faillock_fail_interval=900 -+ status: automated -+ -+ - id: RHEL-09-411090 -+ levels: -+ - medium -+ title: -+ RHEL 9 must maintain an account lock until the locked account is released -+ by an administrator. -+ rules: -+ - accounts_passwords_pam_faillock_unlock_time -+ - var_accounts_passwords_pam_faillock_unlock_time=never -+ status: automated -+ -+ - id: RHEL-09-411095 -+ levels: -+ - medium -+ title: RHEL 9 must not have unauthorized accounts. -+ rules: -+ - accounts_authorized_local_users -+ - var_accounts_authorized_local_users_regex=rhel9 -+ status: automated -+ -+ - id: RHEL-09-411100 -+ levels: -+ - high -+ title: -+ The root account must be the only account having unrestricted access to RHEL -+ 9 system. -+ rules: -+ - accounts_no_uid_except_zero -+ status: automated -+ -+ - id: RHEL-09-411105 -+ levels: -+ - medium -+ title: RHEL 9 must ensure account lockouts persist. -+ rules: -+ - accounts_passwords_pam_faillock_dir -+ status: automated -+ -+ - id: RHEL-09-411110 -+ levels: -+ - medium -+ title: RHEL 9 groups must have unique Group ID (GID). -+ rules: -+ - group_unique_id -+ status: automated -+ -+ - id: RHEL-09-411115 -+ levels: -+ - medium -+ title: Local RHEL 9 initialization files must not execute world-writable programs. -+ rules: -+ - accounts_user_dot_no_world_writable_programs -+ status: automated -+ -+ - id: RHEL-09-412010 -+ levels: -+ - medium -+ title: RHEL 9 must have the tmux package installed. -+ rules: -+ - package_tmux_installed -+ status: automated -+ -+ - id: RHEL-09-412015 -+ levels: -+ - medium -+ title: RHEL 9 must ensure session control is automatically started at shell initialization. -+ rules: -+ - configure_bashrc_exec_tmux -+ status: automated -+ -+ - id: RHEL-09-412020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enable a user session lock until that user re-establishes access -+ using established identification and authentication procedures for command line -+ sessions. -+ rules: -+ - configure_tmux_lock_command -+ - configure_tmux_lock_keybinding -+ status: automated -+ -+ - id: RHEL-09-412025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically lock command line user sessions after 15 minutes -+ of inactivity. -+ rules: -+ - configure_tmux_lock_after_time -+ status: automated -+ -+ - id: RHEL-09-412030 -+ levels: -+ - low -+ title: RHEL 9 must prevent users from disabling session control mechanisms. -+ rules: -+ - no_tmux_in_shells -+ status: automated -+ -+ - id: RHEL-09-412035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must automatically exit interactive command shell user sessions after -+ 15 minutes of inactivity. -+ rules: -+ - accounts_tmout -+ status: automated -+ -+ - id: RHEL-09-412040 -+ levels: -+ - low -+ title: -+ RHEL 9 must limit the number of concurrent sessions to ten for all accounts -+ and/or account types. -+ rules: -+ - accounts_max_concurrent_login_sessions -+ - var_accounts_max_concurrent_login_sessions=10 -+ status: automated -+ -+ - id: RHEL-09-412045 -+ levels: -+ - medium -+ title: RHEL 9 must log username information when unsuccessful logon attempts occur. -+ rules: -+ - accounts_passwords_pam_faillock_audit -+ status: automated -+ -+ - id: RHEL-09-412050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enforce a delay of at least four seconds between logon prompts -+ following a failed logon attempt. -+ rules: -+ - accounts_logon_fail_delay -+ - var_accounts_fail_delay=4 -+ status: automated -+ -+ - id: RHEL-09-412055 -+ levels: -+ - medium -+ title: RHEL 9 must define default permissions for the bash shell. -+ rules: -+ - accounts_umask_etc_bashrc -+ status: automated -+ -+ - id: RHEL-09-412060 -+ levels: -+ - medium -+ title: RHEL 9 must define default permissions for the c shell. -+ rules: -+ - accounts_umask_etc_csh_cshrc -+ status: automated -+ -+ - id: RHEL-09-412065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must define default permissions for all authenticated users in such -+ a way that the user can only read and modify their own files. -+ rules: -+ - accounts_umask_etc_login_defs -+ status: automated -+ -+ - id: RHEL-09-412070 -+ levels: -+ - medium -+ title: RHEL 9 must define default permissions for the system default profile. -+ rules: -+ - accounts_umask_etc_profile -+ status: automated -+ -+ - id: RHEL-09-412075 -+ levels: -+ - low -+ title: -+ RHEL 9 must display the date and time of the last successful account logon -+ upon logon. -+ rules: -+ - display_login_attempts -+ status: automated -+ -+ - id: RHEL-09-412080 -+ levels: -+ - medium -+ title: RHEL 9 must terminate idle user sessions. -+ rules: -+ - logind_session_timeout -+ status: automated -+ -+ - id: RHEL-09-431010 -+ levels: -+ - high -+ title: -+ RHEL 9 must use a Linux Security Module configured to enforce limits on system -+ services. -+ rules: -+ - selinux_state -+ - var_selinux_state=enforcing -+ status: automated -+ -+ - id: RHEL-09-431015 -+ levels: -+ - medium -+ title: RHEL 9 must enable the SELinux targeted policy. -+ rules: -+ - selinux_policytype -+ - var_selinux_policy_name=targeted -+ status: automated -+ -+ - id: RHEL-09-431020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must configure SELinux context type to allow the use of a nondefault -+ faillock tally directory. -+ rules: -+ - account_password_selinux_faillock_dir -+ status: automated -+ -+ - id: RHEL-09-431025 -+ levels: -+ - medium -+ title: RHEL 9 must have policycoreutils package installed. -+ rules: -+ - package_policycoreutils_installed -+ status: automated -+ -+ - id: RHEL-09-431030 -+ levels: -+ - medium -+ title: RHEL 9 policycoreutils-python-utils package must be installed. -+ rules: -+ - package_policycoreutils-python-utils_installed -+ status: automated -+ -+ - id: RHEL-09-432010 -+ levels: -+ - medium -+ title: RHEL 9 must have the sudo package installed. -+ rules: -+ - package_sudo_installed -+ status: automated -+ -+ - id: RHEL-09-432015 -+ levels: -+ - medium -+ title: RHEL 9 must require reauthentication when using the "sudo" command. -+ rules: -+ - sudo_require_reauthentication -+ status: automated -+ -+ - id: RHEL-09-432020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must use the invoking user's password for privilege escalation when -+ using "sudo". -+ rules: -+ - sudoers_validate_passwd -+ status: automated -+ -+ - id: RHEL-09-432025 -+ levels: -+ - medium -+ title: RHEL 9 must require users to reauthenticate for privilege escalation. -+ rules: -+ - sudo_remove_no_authenticate -+ status: automated -+ -+ - id: RHEL-09-432030 -+ levels: -+ - medium -+ title: RHEL 9 must restrict privilege elevation to authorized personnel. -+ rules: -+ - sudo_restrict_privilege_elevation_to_authorized -+ status: automated -+ -+ - id: RHEL-09-432035 -+ levels: -+ - medium -+ title: RHEL 9 must restrict the use of the "su" command. -+ rules: -+ - use_pam_wheel_for_su -+ status: automated -+ -+ - id: RHEL-09-433010 -+ levels: -+ - medium -+ title: RHEL 9 fapolicy module must be installed. -+ rules: -+ - package_fapolicyd_installed -+ status: automated -+ -+ - id: RHEL-09-433015 -+ levels: -+ - medium -+ title: RHEL 9 fapolicy module must be enabled. -+ rules: -+ - service_fapolicyd_enabled -+ status: automated -+ -+ - id: RHEL-09-611010 -+ levels: -+ - medium -+ title: -+ RHEL 9 must ensure the password complexity module in the system-auth file -+ is configured for three retries or less. -+ rules: -+ - accounts_password_pam_retry -+ - var_password_pam_retry=3 -+ status: automated -+ -+ - id: RHEL-09-611015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured in the password-auth file to prohibit password -+ reuse for a minimum of five generations. -+ rules: -+ - accounts_password_pam_pwhistory_remember_password_auth -+ - var_password_pam_remember=5 -+ - var_password_pam_remember_control_flag=requisite_or_required -+ status: automated -+ -+ - id: RHEL-09-611020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured in the system-auth file to prohibit password reuse -+ for a minimum of five generations. -+ rules: -+ - accounts_password_pam_pwhistory_remember_system_auth -+ status: automated -+ -+ - id: RHEL-09-611025 -+ levels: -+ - high -+ title: RHEL 9 must not allow blank or null passwords. -+ rules: -+ - no_empty_passwords -+ status: automated -+ -+ - id: RHEL-09-611030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth -+ file. -+ rules: -+ - account_password_pam_faillock_system_auth -+ status: automated -+ -+ - id: RHEL-09-611035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth -+ file. -+ rules: -+ - account_password_pam_faillock_password_auth -+ status: automated -+ -+ - id: RHEL-09-611040 -+ levels: -+ - medium -+ title: -+ RHEL 9 must ensure the password complexity module is enabled in the password-auth -+ file. -+ rules: -+ - accounts_password_pam_pwquality_password_auth -+ status: automated -+ -+ - id: RHEL-09-611045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must ensure the password complexity module is enabled in the system-auth -+ file. -+ rules: -+ - accounts_password_pam_pwquality_system_auth -+ status: automated -+ -+ - id: RHEL-09-611050 -+ levels: -+ - medium -+ title: -+ RHEL 9 password-auth must be configured to use a sufficient number of hashing -+ rounds. -+ rules: -+ - accounts_password_pam_unix_rounds_password_auth -+ - var_password_pam_unix_rounds=5000 -+ status: automated -+ -+ - id: RHEL-09-611055 -+ levels: -+ - medium -+ title: -+ RHEL 9 system-auth must be configured to use a sufficient number of hashing -+ rounds. -+ rules: -+ - accounts_password_pam_unix_rounds_system_auth -+ status: automated -+ -+ - id: RHEL-09-611060 -+ levels: -+ - medium -+ title: RHEL 9 must enforce password complexity rules for the root account. -+ rules: -+ - accounts_password_pam_enforce_root -+ status: automated -+ -+ - id: RHEL-09-611065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enforce password complexity by requiring that at least one lowercase -+ character be used. -+ rules: -+ - accounts_password_pam_lcredit -+ - var_password_pam_lcredit=1 -+ status: automated -+ -+ - id: RHEL-09-611070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enforce password complexity by requiring that at least one numeric -+ character be used. -+ rules: -+ - accounts_password_pam_dcredit -+ - var_password_pam_dcredit=1 -+ status: automated -+ -+ - id: RHEL-09-611075 -+ levels: -+ - medium -+ title: -+ RHEL 9 passwords for new users or password changes must have a 24 hours minimum -+ password lifetime restriction in /etc/login.defs. -+ rules: -+ - accounts_minimum_age_login_defs -+ status: automated -+ -+ - id: RHEL-09-611080 -+ levels: -+ - medium -+ title: -+ RHEL 9 passwords must have a 24 hours minimum password lifetime restriction -+ in /etc/shadow. -+ rules: -+ - accounts_password_set_min_life_existing -+ - var_accounts_minimum_age_login_defs=1 -+ status: automated -+ -+ - id: RHEL-09-611085 -+ levels: -+ - medium -+ title: RHEL 9 must require users to provide a password for privilege escalation. -+ rules: -+ - sudo_remove_nopasswd -+ status: automated -+ -+ - id: RHEL-09-611090 -+ levels: -+ - medium -+ title: RHEL 9 passwords must be created with a minimum of 15 characters. -+ rules: -+ - accounts_password_pam_minlen -+ - var_password_pam_minlen=15 -+ status: automated -+ -+ - id: RHEL-09-611095 -+ levels: -+ - medium -+ title: RHEL 9 passwords for new users must have a minimum of 15 characters. -+ rules: -+ - accounts_password_minlen_login_defs -+ status: automated -+ -+ - id: RHEL-09-611100 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enforce password complexity by requiring that at least one special -+ character be used. -+ rules: -+ - accounts_password_pam_ocredit -+ - var_password_pam_ocredit=1 -+ status: automated -+ -+ - id: RHEL-09-611105 -+ levels: -+ - medium -+ title: RHEL 9 must prevent the use of dictionary words for passwords. -+ rules: -+ - accounts_password_pam_dictcheck -+ - var_password_pam_dictcheck=1 -+ status: automated -+ -+ - id: RHEL-09-611110 -+ levels: -+ - medium -+ title: -+ RHEL 9 must enforce password complexity by requiring that at least one uppercase -+ character be used. -+ rules: -+ - accounts_password_pam_ucredit -+ - var_password_pam_ucredit=1 -+ status: automated -+ -+ - id: RHEL-09-611115 -+ levels: -+ - medium -+ title: -+ RHEL 9 must require the change of at least eight characters when passwords -+ are changed. -+ rules: -+ - accounts_password_pam_difok -+ - var_password_pam_difok=8 -+ status: automated -+ -+ - id: RHEL-09-611120 -+ levels: -+ - medium -+ title: -+ RHEL 9 must require the maximum number of repeating characters of the same -+ character class be limited to four when passwords are changed. -+ rules: -+ - accounts_password_pam_maxclassrepeat -+ - var_password_pam_maxclassrepeat=4 -+ status: automated -+ -+ - id: RHEL-09-611125 -+ levels: -+ - medium -+ title: -+ RHEL 9 must require the maximum number of repeating characters be limited -+ to three when passwords are changed. -+ rules: -+ - accounts_password_pam_maxrepeat -+ - var_password_pam_maxrepeat=3 -+ status: automated -+ -+ - id: RHEL-09-611130 -+ levels: -+ - medium -+ title: -+ RHEL 9 must require the change of at least four character classes when passwords -+ are changed. -+ rules: -+ - accounts_password_pam_minclass -+ - var_password_pam_minclass=4 -+ status: automated -+ -+ - id: RHEL-09-611135 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that user and group account administration utilities -+ are configured to store only encrypted representations of passwords. -+ rules: -+ - set_password_hashing_algorithm_libuserconf -+ status: automated -+ -+ - id: RHEL-09-611140 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured to use the shadow file to store only encrypted -+ representations of passwords. -+ rules: -+ - set_password_hashing_algorithm_logindefs -+ - var_password_hashing_algorithm=SHA512 -+ status: automated -+ -+ - id: RHEL-09-611145 -+ levels: -+ - medium -+ title: -+ RHEL 9 must not be configured to bypass password requirements for privilege -+ escalation. -+ rules: -+ - disallow_bypass_password_sudo -+ status: automated -+ -+ - id: RHEL-09-611150 -+ levels: -+ - medium -+ title: -+ RHEL 9 shadow password suite must be configured to use a sufficient number -+ of hashing rounds. -+ rules: -+ - set_password_hashing_min_rounds_logindefs -+ status: automated -+ -+ - id: RHEL-09-611155 -+ levels: -+ - medium -+ title: RHEL 9 must not have accounts configured with blank or null passwords. -+ rules: -+ - no_empty_passwords_etc_shadow -+ status: automated -+ -+ - id: RHEL-09-611160 -+ levels: -+ - medium -+ title: RHEL 9 must use the CAC smart card driver. -+ rules: -+ - configure_opensc_card_drivers -+ - var_smartcard_drivers=cac -+ status: automated -+ -+ - id: RHEL-09-611165 -+ levels: -+ - medium -+ title: RHEL 9 must enable certificate based smart card authentication. -+ rules: -+ - sssd_enable_smartcards -+ status: automated -+ -+ - id: RHEL-09-611170 -+ levels: -+ - medium -+ title: RHEL 9 must implement certificate status checking for multifactor authentication. -+ rules: -+ - sssd_certificate_verification -+ - var_sssd_certificate_verification_digest_function=sha512 -+ status: automated -+ -+ - id: RHEL-09-611175 -+ levels: -+ - medium -+ title: RHEL 9 must have the pcsc-lite package installed. -+ rules: -+ - package_pcsc-lite_installed -+ status: automated -+ -+ - id: RHEL-09-611180 -+ levels: -+ - medium -+ title: The pcscd service on RHEL 9 must be active. -+ rules: -+ - service_pcscd_enabled -+ status: automated -+ -+ - id: RHEL-09-611185 -+ levels: -+ - medium -+ title: RHEL 9 must have the opensc package installed. -+ rules: -+ - package_opensc_installed -+ status: automated -+ -+ - id: RHEL-09-611190 -+ levels: -+ - medium -+ title: -+ RHEL 9, for PKI-based authentication, must enforce authorized access to the -+ corresponding private key. -+ rules: -+ - ssh_keys_passphrase_protected -+ status: automated -+ -+ - id: RHEL-09-611195 -+ levels: -+ - medium -+ title: RHEL 9 must require authentication to access emergency mode. -+ rules: -+ - require_emergency_target_auth -+ status: automated -+ -+ - id: RHEL-09-611200 -+ levels: -+ - medium -+ title: RHEL 9 must require authentication to access single-user mode. -+ rules: -+ - require_singleuser_auth -+ status: automated -+ -+ - id: RHEL-09-611205 -+ levels: -+ - medium -+ title: RHEL 9 must prevent system daemons from using Kerberos for authentication. -+ rules: -+ - kerberos_disable_no_keytab -+ status: automated -+ -+ - id: RHEL-09-631010 -+ levels: -+ - medium -+ title: -+ RHEL 9, for PKI-based authentication, must validate certificates by constructing -+ a certification path (which includes status information) to an accepted trust -+ anchor. -+ rules: -+ - sssd_has_trust_anchor -+ status: automated -+ -+ - id: RHEL-09-631015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must map the authenticated identity to the user or group account for -+ PKI-based authentication. -+ rules: -+ - sssd_enable_certmap -+ status: automated -+ -+ - id: RHEL-09-631020 -+ levels: -+ - medium -+ title: RHEL 9 must prohibit the use of cached authenticators after one day. -+ rules: -+ - sssd_offline_cred_expiration -+ status: automated -+ -+ - id: RHEL-09-651010 -+ levels: -+ - medium -+ title: RHEL 9 must have the AIDE package installed. -+ rules: -+ - package_aide_installed -+ status: automated -+ -+ - id: RHEL-09-651015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must routinely check the baseline configuration for unauthorized changes -+ and notify the system administrator when anomalies in the operation of any security -+ functions are discovered. -+ rules: -+ - aide_periodic_cron_checking -+ - aide_scan_notification -+ status: automated -+ -+ - id: RHEL-09-651020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must use a file integrity tool that is configured to use FIPS 140-3-approved -+ cryptographic hashes for validating file contents and directories. -+ rules: -+ - aide_use_fips_hashes -+ status: automated -+ -+ - id: RHEL-09-651025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must use cryptographic mechanisms to protect the integrity of audit -+ tools. -+ rules: -+ - aide_check_audit_tools -+ status: automated -+ -+ - id: RHEL-09-651030 -+ levels: -+ - low -+ title: -+ RHEL 9 must be configured so that the file integrity tool verifies Access -+ Control Lists (ACLs). -+ rules: -+ - aide_verify_acls -+ status: automated -+ -+ - id: RHEL-09-651035 -+ levels: -+ - low -+ title: -+ RHEL 9 must be configured so that the file integrity tool verifies extended -+ attributes. -+ rules: -+ - aide_verify_ext_attributes -+ status: automated -+ -+ - id: RHEL-09-652010 -+ levels: -+ - medium -+ title: RHEL 9 must have the rsyslog package installed. -+ rules: -+ - package_rsyslog_installed -+ status: automated -+ -+ - id: RHEL-09-652015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must have the packages required for encrypting offloaded audit logs -+ installed. -+ rules: -+ - package_rsyslog-gnutls_installed -+ status: automated -+ -+ - id: RHEL-09-652020 -+ levels: -+ - medium -+ title: The rsyslog service on RHEL 9 must be active. -+ rules: -+ - service_rsyslog_enabled -+ status: automated -+ -+ - id: RHEL-09-652025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured so that the rsyslog daemon does not accept log -+ messages from other servers unless the server is being used for log aggregation. -+ rules: -+ - rsyslog_nolisten -+ status: automated -+ -+ - id: RHEL-09-652030 -+ levels: -+ - medium -+ title: All RHEL 9 remote access methods must be monitored. -+ rules: -+ - rsyslog_remote_access_monitoring -+ status: automated -+ -+ - id: RHEL-09-652035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured to offload audit records onto a different system -+ from the system being audited via syslog. -+ rules: -+ - auditd_audispd_syslog_plugin_activated -+ status: automated -+ -+ - id: RHEL-09-652040 -+ levels: -+ - medium -+ title: -+ RHEL 9 must authenticate the remote logging server for offloading audit logs -+ via rsyslog. -+ rules: -+ - rsyslog_encrypt_offload_actionsendstreamdriverauthmode -+ status: automated -+ -+ - id: RHEL-09-652045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must encrypt the transfer of audit records offloaded onto a different -+ system or media from the system being audited via rsyslog. -+ rules: -+ - rsyslog_encrypt_offload_actionsendstreamdrivermode -+ status: automated -+ -+ - id: RHEL-09-652050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must encrypt via the gtls driver the transfer of audit records offloaded -+ onto a different system or media from the system being audited via rsyslog. -+ rules: -+ - rsyslog_encrypt_offload_defaultnetstreamdriver -+ status: automated -+ -+ - id: RHEL-09-652055 -+ levels: -+ - medium -+ title: -+ RHEL 9 must be configured to forward audit records via TCP to a different -+ system or media from the system being audited via rsyslog. -+ rules: -+ - rsyslog_remote_loghost -+ status: automated -+ -+ - id: RHEL-09-652060 -+ levels: -+ - medium -+ title: RHEL 9 must use cron logging. -+ rules: -+ - rsyslog_cron_logging -+ status: automated -+ -+ - id: RHEL-09-653010 -+ levels: -+ - medium -+ title: RHEL 9 audit package must be installed. -+ rules: -+ - package_audit_installed -+ status: automated -+ -+ - id: RHEL-09-653015 -+ levels: -+ - medium -+ title: RHEL 9 audit service must be enabled. -+ rules: -+ - service_auditd_enabled -+ status: automated -+ -+ - id: RHEL-09-653020 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit system must take appropriate action when an error writing to -+ the audit storage volume occurs. -+ rules: -+ - auditd_data_disk_error_action_stig -+ - var_auditd_disk_error_action=halt -+ status: automated -+ -+ - id: RHEL-09-653025 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit system must take appropriate action when the audit storage volume -+ is full. -+ rules: -+ - auditd_data_disk_full_action_stig -+ - var_auditd_disk_full_action=halt -+ status: automated -+ -+ - id: RHEL-09-653030 -+ levels: -+ - medium -+ title: -+ RHEL 9 must allocate audit record storage capacity to store at least one -+ week's worth of audit records. -+ rules: -+ - auditd_audispd_configure_sufficiently_large_partition -+ status: automated -+ -+ - id: RHEL-09-653035 -+ levels: -+ - medium -+ title: -+ RHEL 9 must take action when allocated audit record storage volume reaches -+ 75 percent of the repository maximum audit record storage capacity. -+ rules: -+ - auditd_data_retention_space_left_percentage -+ - var_auditd_space_left_percentage=25pc -+ status: automated -+ -+ - id: RHEL-09-653040 -+ levels: -+ - medium -+ title: -+ RHEL 9 must notify the system administrator (SA) and information system security -+ officer (ISSO) (at a minimum) when allocated audit record storage volume 75 percent -+ utilization. -+ rules: -+ - auditd_data_retention_space_left_action -+ - var_auditd_space_left_action=email -+ status: automated -+ -+ - id: RHEL-09-653045 -+ levels: -+ - medium -+ title: -+ RHEL 9 must take action when allocated audit record storage volume reaches -+ 95 percent of the audit record storage capacity. -+ rules: -+ - auditd_data_retention_admin_space_left_percentage -+ - var_auditd_admin_space_left_percentage=5pc -+ status: automated -+ -+ - id: RHEL-09-653050 -+ levels: -+ - medium -+ title: -+ RHEL 9 must take action when allocated audit record storage volume reaches -+ 95 percent of the repository maximum audit record storage capacity. -+ rules: -+ - auditd_data_retention_admin_space_left_action -+ - var_auditd_admin_space_left_action=halt -+ status: automated -+ -+ - id: RHEL-09-653055 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit system must take appropriate action when the audit files have -+ reached maximum size. -+ rules: -+ - auditd_data_retention_max_log_file_action_stig -+ - var_auditd_max_log_file_action=rotate -+ status: automated -+ -+ - id: RHEL-09-653060 -+ levels: -+ - medium -+ title: -+ RHEL 9 must label all offloaded audit logs before sending them to the central -+ log server. -+ rules: -+ - auditd_name_format -+ - var_auditd_name_format=stig -+ status: automated -+ -+ - id: RHEL-09-653065 -+ levels: -+ - medium -+ title: RHEL 9 must take appropriate action when the internal event queue is full. -+ rules: -+ - auditd_overflow_action -+ status: automated -+ -+ - id: RHEL-09-653070 -+ levels: -+ - medium -+ title: -+ RHEL 9 System Administrator (SA) and/or information system security officer -+ (ISSO) (at a minimum) must be alerted of an audit processing failure event. -+ rules: -+ - auditd_data_retention_action_mail_acct -+ - var_auditd_action_mail_acct=root -+ status: automated -+ -+ - id: RHEL-09-653075 -+ levels: -+ - medium -+ title: RHEL 9 audit system must audit local events. -+ rules: -+ - auditd_local_events -+ status: automated -+ -+ - id: RHEL-09-653080 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit logs must be group-owned by root or by a restricted logging -+ group to prevent unauthorized read access. -+ rules: -+ - directory_group_ownership_var_log_audit -+ status: automated -+ -+ - id: RHEL-09-653085 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit log directory must be owned by root to prevent unauthorized -+ read access. -+ rules: -+ - directory_ownership_var_log_audit -+ status: automated -+ -+ - id: RHEL-09-653090 -+ levels: -+ - medium -+ title: -+ RHEL 9 audit logs file must have mode 0600 or less permissive to prevent -+ unauthorized access to the audit log. -+ rules: -+ - file_permissions_var_log_audit -+ status: automated -+ -+ - id: RHEL-09-653095 -+ levels: -+ - medium -+ title: -+ RHEL 9 must periodically flush audit records to disk to prevent the loss -+ of audit records. -+ rules: -+ - auditd_freq -+ - var_auditd_freq=100 -+ status: automated -+ -+ - id: RHEL-09-653100 -+ levels: -+ - medium -+ title: -+ RHEL 9 must produce audit records containing information to establish the -+ identity of any individual or process associated with the event. -+ rules: -+ - auditd_log_format -+ status: automated -+ -+ - id: RHEL-09-653105 -+ levels: -+ - medium -+ title: RHEL 9 must write audit records to disk. -+ rules: -+ - auditd_write_logs -+ status: automated -+ -+ - id: RHEL-09-653110 -+ levels: -+ - medium -+ title: -+ RHEL 9 must allow only the information system security manager (ISSM) (or -+ individuals or roles appointed by the ISSM) to select which auditable events are -+ to be audited. -+ rules: -+ - file_permissions_etc_audit_rulesd -+ status: automated -+ -+ - id: RHEL-09-653115 -+ levels: -+ - medium -+ title: -+ RHEL 9 /etc/audit/auditd.conf file must have 0640 or less permissive to prevent -+ unauthorized access. -+ rules: -+ - file_permissions_etc_audit_auditd -+ status: automated -+ -+ - id: RHEL-09-653120 -+ levels: -+ - low -+ title: -+ RHEL 9 must allocate an audit_backlog_limit of sufficient size to capture -+ processes that start prior to the audit daemon. -+ rules: -+ - grub2_audit_backlog_limit_argument -+ status: automated -+ -+ - id: RHEL-09-653125 -+ levels: -+ - medium -+ title: -+ RHEL 9 must have mail aliases to notify the information system security officer -+ (ISSO) and system administrator (SA) (at a minimum) in the event of an audit processing -+ failure. -+ rules: -+ - postfix_client_configure_mail_alias -+ status: automated -+ -+ - id: RHEL-09-653130 -+ levels: -+ - medium -+ title: RHEL 9 audispd-plugins package must be installed. -+ rules: -+ - package_audispd-plugins_installed -+ status: automated -+ -+ - id: RHEL-09-654010 -+ levels: -+ - medium -+ title: RHEL 9 must audit uses of the "execve" system call. -+ rules: -+ - audit_rules_suid_privilege_function -+ status: automated -+ -+ - id: RHEL-09-654015 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the chmod, fchmod, and fchmodat system calls. -+ rules: -+ - audit_rules_dac_modification_chmod -+ - audit_rules_dac_modification_fchmod -+ - audit_rules_dac_modification_fchmodat -+ status: automated -+ -+ - id: RHEL-09-654020 -+ levels: -+ - medium -+ title: -+ RHEL 9 must audit all uses of the chown, fchown, fchownat, and lchown system -+ calls. -+ rules: -+ - audit_rules_dac_modification_chown -+ - audit_rules_dac_modification_fchown -+ - audit_rules_dac_modification_fchownat -+ - audit_rules_dac_modification_lchown -+ status: automated -+ -+ - id: RHEL-09-654025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, -+ fremovexattr, and lremovexattr system calls. -+ rules: -+ - audit_rules_dac_modification_setxattr -+ - audit_rules_dac_modification_fsetxattr -+ - audit_rules_dac_modification_lsetxattr -+ - audit_rules_dac_modification_removexattr -+ - audit_rules_dac_modification_fremovexattr -+ - audit_rules_dac_modification_lremovexattr -+ status: automated -+ -+ - id: RHEL-09-654030 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of umount system calls. -+ rules: -+ - audit_rules_privileged_commands_umount -+ status: automated -+ -+ - id: RHEL-09-654035 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the chacl command. -+ rules: -+ - audit_rules_execution_chacl -+ status: automated -+ -+ - id: RHEL-09-654040 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the setfacl command. -+ rules: -+ - audit_rules_execution_setfacl -+ status: automated -+ -+ - id: RHEL-09-654045 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the chcon command. -+ rules: -+ - audit_rules_execution_chcon -+ status: automated -+ -+ - id: RHEL-09-654050 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the semanage command. -+ rules: -+ - audit_rules_execution_semanage -+ status: automated -+ -+ - id: RHEL-09-654055 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the setfiles command. -+ rules: -+ - audit_rules_execution_setfiles -+ status: automated -+ -+ - id: RHEL-09-654060 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the setsebool command. -+ rules: -+ - audit_rules_execution_setsebool -+ status: automated -+ -+ - id: RHEL-09-654065 -+ levels: -+ - medium -+ title: -+ RHEL 9 must audit all uses of the rename, unlink, rmdir, renameat, and unlinkat -+ system calls. -+ rules: -+ - audit_rules_file_deletion_events_rename -+ - audit_rules_file_deletion_events_unlink -+ - audit_rules_file_deletion_events_rmdir -+ - audit_rules_file_deletion_events_renameat -+ - audit_rules_file_deletion_events_unlinkat -+ status: automated -+ -+ - id: RHEL-09-654070 -+ levels: -+ - medium -+ title: -+ RHEL 9 must audit all uses of the truncate, ftruncate, creat, open, openat, -+ and open_by_handle_at system calls. -+ rules: -+ - audit_rules_unsuccessful_file_modification_creat -+ - audit_rules_unsuccessful_file_modification_truncate -+ - audit_rules_unsuccessful_file_modification_ftruncate -+ - audit_rules_unsuccessful_file_modification_open -+ - audit_rules_unsuccessful_file_modification_openat -+ - audit_rules_unsuccessful_file_modification_open_by_handle_at -+ status: automated -+ -+ - id: RHEL-09-654075 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the delete_module system call. -+ rules: -+ - audit_rules_kernel_module_loading_delete -+ status: automated -+ -+ - id: RHEL-09-654080 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the init_module and finit_module system calls. -+ rules: -+ - audit_rules_kernel_module_loading_finit -+ - audit_rules_kernel_module_loading_init -+ status: automated -+ -+ - id: RHEL-09-654085 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the chage command. -+ rules: -+ - audit_rules_privileged_commands_chage -+ status: automated -+ -+ - id: RHEL-09-654090 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the chsh command. -+ rules: -+ - audit_rules_privileged_commands_chsh -+ status: automated -+ -+ - id: RHEL-09-654095 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the crontab command. -+ rules: -+ - audit_rules_privileged_commands_crontab -+ status: automated -+ -+ - id: RHEL-09-654100 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the gpasswd command. -+ rules: -+ - audit_rules_privileged_commands_gpasswd -+ status: automated -+ -+ - id: RHEL-09-654105 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the kmod command. -+ rules: -+ - audit_rules_privileged_commands_kmod -+ status: automated -+ -+ - id: RHEL-09-654110 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the newgrp command. -+ rules: -+ - audit_rules_privileged_commands_newgrp -+ status: automated -+ -+ - id: RHEL-09-654115 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the pam_timestamp_check command. -+ rules: -+ - audit_rules_privileged_commands_pam_timestamp_check -+ status: automated -+ -+ - id: RHEL-09-654120 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the passwd command. -+ rules: -+ - audit_rules_privileged_commands_passwd -+ status: automated -+ -+ - id: RHEL-09-654125 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the postdrop command. -+ rules: -+ - audit_rules_privileged_commands_postdrop -+ status: automated -+ -+ - id: RHEL-09-654130 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the postqueue command. -+ rules: -+ - audit_rules_privileged_commands_postqueue -+ status: automated -+ -+ - id: RHEL-09-654135 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the ssh-agent command. -+ rules: -+ - audit_rules_privileged_commands_ssh_agent -+ status: automated -+ -+ - id: RHEL-09-654140 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the ssh-keysign command. -+ rules: -+ - audit_rules_privileged_commands_ssh_keysign -+ status: automated -+ -+ - id: RHEL-09-654145 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the su command. -+ rules: -+ - audit_rules_privileged_commands_su -+ status: automated -+ -+ - id: RHEL-09-654150 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the sudo command. -+ rules: -+ - audit_rules_privileged_commands_sudo -+ status: automated -+ -+ - id: RHEL-09-654155 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the sudoedit command. -+ rules: -+ - audit_rules_privileged_commands_sudoedit -+ status: automated -+ -+ - id: RHEL-09-654160 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the unix_chkpwd command. -+ rules: -+ - audit_rules_privileged_commands_unix_chkpwd -+ status: automated -+ -+ - id: RHEL-09-654165 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the unix_update command. -+ rules: -+ - audit_rules_privileged_commands_unix_update -+ status: automated -+ -+ - id: RHEL-09-654170 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the userhelper command. -+ rules: -+ - audit_rules_privileged_commands_userhelper -+ status: automated -+ -+ - id: RHEL-09-654175 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the usermod command. -+ rules: -+ - audit_rules_privileged_commands_usermod -+ status: automated -+ -+ - id: RHEL-09-654180 -+ levels: -+ - medium -+ title: RHEL 9 must audit all uses of the mount command. -+ rules: -+ - audit_rules_privileged_commands_mount -+ status: automated -+ -+ - id: RHEL-09-654185 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the init command in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_privileged_commands_init -+ status: automated -+ -+ - id: RHEL-09-654190 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the poweroff command in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_privileged_commands_poweroff -+ status: automated -+ -+ - id: RHEL-09-654195 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the reboot command in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_privileged_commands_reboot -+ status: automated -+ -+ - id: RHEL-09-654200 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the shutdown command in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_privileged_commands_shutdown -+ status: automated -+ -+ - id: RHEL-09-654205 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the umount system call in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_rules_dac_modification_umount -+ status: automated -+ -+ - id: RHEL-09-654210 -+ levels: -+ - medium -+ title: -+ Successful/unsuccessful uses of the umount2 system call in RHEL 9 must generate -+ an audit record. -+ rules: -+ - audit_rules_dac_modification_umount2 -+ status: automated -+ -+ - id: RHEL-09-654215 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/sudoers. -+ rules: -+ - audit_rules_sudoers -+ status: automated -+ -+ - id: RHEL-09-654220 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/sudoers.d/ directory. -+ rules: -+ - audit_rules_sudoers_d -+ status: automated -+ -+ - id: RHEL-09-654225 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/group. -+ rules: -+ - audit_rules_usergroup_modification_group -+ status: automated -+ -+ - id: RHEL-09-654230 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/gshadow. -+ rules: -+ - audit_rules_usergroup_modification_gshadow -+ status: automated -+ -+ - id: RHEL-09-654235 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/opasswd. -+ rules: -+ - audit_rules_usergroup_modification_opasswd -+ status: automated -+ -+ - id: RHEL-09-654240 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/passwd. -+ rules: -+ - audit_rules_usergroup_modification_passwd -+ status: automated -+ -+ - id: RHEL-09-654245 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /etc/shadow. -+ rules: -+ - audit_rules_usergroup_modification_shadow -+ status: automated -+ -+ - id: RHEL-09-654250 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /var/log/faillock. -+ rules: -+ - audit_rules_login_events_faillock -+ status: automated -+ -+ - id: RHEL-09-654255 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /var/log/lastlog. -+ rules: -+ - audit_rules_login_events_lastlog -+ status: automated -+ -+ - id: RHEL-09-654260 -+ levels: -+ - medium -+ title: -+ RHEL 9 must generate audit records for all account creations, modifications, -+ disabling, and termination events that affect /var/log/tallylog. -+ rules: -+ - audit_rules_login_events_tallylog -+ status: automated -+ -+ - id: RHEL-09-654265 -+ levels: -+ - medium -+ title: -+ RHEL 9 must take appropriate action when a critical audit processing failure -+ occurs. -+ rules: -+ - audit_rules_system_shutdown -+ status: automated -+ -+ - id: RHEL-09-654270 -+ levels: -+ - medium -+ title: RHEL 9 audit system must protect logon UIDs from unauthorized change. -+ rules: -+ - audit_immutable_login_uids -+ status: automated -+ -+ - id: RHEL-09-654275 -+ levels: -+ - medium -+ title: RHEL 9 audit system must protect auditing rules from unauthorized change. -+ rules: -+ - audit_rules_immutable -+ status: automated -+ -+ - id: RHEL-09-671010 -+ levels: -+ - high -+ title: RHEL 9 must enable FIPS mode. -+ rules: -+ - enable_fips_mode -+ - sysctl_crypto_fips_enabled -+ - var_system_crypto_policy=fips -+ - configure_crypto_policy -+ - enable_dracut_fips_module -+ status: automated -+ -+ - id: RHEL-09-671015 -+ levels: -+ - medium -+ title: -+ RHEL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for -+ all stored passwords. -+ rules: -+ - accounts_password_all_shadowed_sha512 -+ status: automated -+ -+ - id: RHEL-09-671020 -+ levels: -+ - medium -+ title: RHEL 9 IP tunnels must use FIPS 140-2/140-3 approved cryptographic algorithms. -+ rules: -+ - configure_libreswan_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-671025 -+ levels: -+ - medium -+ title: -+ RHEL 9 pam_unix.so module must be configured in the password-auth file to -+ use a FIPS 140-3 approved cryptographic hashing algorithm for system authentication. -+ rules: -+ - set_password_hashing_algorithm_passwordauth -+ status: automated -+ -+ - id: RHEL-09-672010 -+ levels: -+ - medium -+ title: RHEL 9 must have the crypto-policies package installed. -+ rules: -+ - package_crypto-policies_installed -+ status: automated -+ -+ - id: RHEL-09-672015 -+ levels: -+ - high -+ title: RHEL 9 crypto policy files must match files shipped with the operating system. -+ status: pending -+ -+ - id: RHEL-09-672020 -+ levels: -+ - medium -+ title: RHEL 9 crypto policy must not be overridden. -+ status: pending -+ -+ - id: RHEL-09-672025 -+ levels: -+ - medium -+ title: -+ RHEL 9 must use mechanisms meeting the requirements of applicable federal -+ laws, executive orders, directives, policies, regulations, standards, and guidance -+ for authentication to a cryptographic module. -+ rules: -+ - configure_kerberos_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-672030 -+ levels: -+ - high -+ title: RHEL 9 must implement DOD-approved TLS encryption in the GnuTLS package. -+ rules: -+ - configure_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-672035 -+ levels: -+ - medium -+ title: RHEL 9 must implement DOD-approved encryption in the OpenSSL package. -+ rules: -+ - configure_openssl_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-672040 -+ levels: -+ - medium -+ title: RHEL 9 must implement DOD-approved TLS encryption in the OpenSSL package. -+ rules: -+ - configure_openssl_tls_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-672045 -+ levels: -+ - medium -+ title: RHEL 9 must implement a system-wide encryption policy. -+ rules: -+ - configure_crypto_policy -+ status: automated -+ -+ - id: RHEL-09-672050 -+ levels: -+ - medium -+ title: RHEL 9 must implement DOD-approved encryption in the bind package. -+ rules: -+ - configure_bind_crypto_policy -+ status: automated -diff --git a/linux_os/guide/services/base/service_kdump_disabled/rule.yml b/linux_os/guide/services/base/service_kdump_disabled/rule.yml -index 80fe7b688b..446f84e048 100644 ---- a/linux_os/guide/services/base/service_kdump_disabled/rule.yml -+++ b/linux_os/guide/services/base/service_kdump_disabled/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-010670 - stigid@rhel7: RHEL-07-021300 - stigid@rhel8: RHEL-08-010670 -+ stigid@rhel9: RHEL-09-213115 - stigid@sle12: SLES-12-010840 - stigid@sle15: SLES-15-040190 - stigid@ubuntu2004: UBTU-20-010413 -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_d/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_d/rule.yml -index 77b163e600..00cd6c036a 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_d/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_d/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.d", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_daily/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_daily/rule.yml -index ff0443ac56..cf786d35d1 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_daily/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_daily/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.daily", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml -index 7cacc3fc7b..7801c5599c 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_deny/rule.yml -@@ -22,6 +22,7 @@ references: - disa: CCI-000366 - nist: CM-6 b - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.deny", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_hourly/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_hourly/rule.yml -index 63dd951d70..380e0e4ba7 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_hourly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_hourly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.hourly", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_monthly/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_monthly/rule.yml -index 6d4493560d..477b101013 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_monthly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_monthly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.monthly", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_cron_weekly/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_cron_weekly/rule.yml -index 687b846989..f1f60548c4 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_cron_weekly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_cron_weekly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/cron.weekly", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_groupowner_crontab/rule.yml b/linux_os/guide/services/cron_and_at/file_groupowner_crontab/rule.yml -index b980bc125c..c71eb204d1 100644 ---- a/linux_os/guide/services/cron_and_at/file_groupowner_crontab/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_groupowner_crontab/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232235 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/crontab", group="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_d/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_d/rule.yml -index c2d050d277..af8937794c 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_d/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_d/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.d", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_daily/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_daily/rule.yml -index 6024de5c66..fa83630fd5 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_daily/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_daily/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.daily", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml -index 4297313a74..9cf7aba1a9 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_deny/rule.yml -@@ -22,6 +22,7 @@ references: - disa: CCI-000366 - nist: CM-6 b - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.deny", owner="root") }}}' -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_hourly/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_hourly/rule.yml -index 46320b4626..98b900d12b 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_hourly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_hourly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.hourly", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_monthly/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_monthly/rule.yml -index 18afaf1da8..2c8a38094d 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_monthly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_monthly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.monthly", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_cron_weekly/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_cron_weekly/rule.yml -index d76c2031c3..bbdf867467 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_cron_weekly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_cron_weekly/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/cron.weekly", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_owner_crontab/rule.yml b/linux_os/guide/services/cron_and_at/file_owner_crontab/rule.yml -index b9c4bcce48..bb655e1837 100644 ---- a/linux_os/guide/services/cron_and_at/file_owner_crontab/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_owner_crontab/rule.yml -@@ -39,6 +39,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232230 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/crontab", owner="root") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_cron_d/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_cron_d/rule.yml -index bdc53cc7c0..daf1affa1d 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_cron_d/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_cron_d/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232040 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/cron.d", perms="-rwx------") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_cron_daily/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_cron_daily/rule.yml -index 24b4cf5e58..a72240104c 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_cron_daily/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_cron_daily/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232040 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/cron.daily", perms="-rwx------") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_cron_hourly/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_cron_hourly/rule.yml -index 6e0da2bacc..cfdd97a259 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_cron_hourly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_cron_hourly/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232040 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/cron.hourly", perms="-rwx------") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_cron_monthly/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_cron_monthly/rule.yml -index 5f5e5f6ecd..97ffef201d 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_cron_monthly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_cron_monthly/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232040 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/cron.monthly", perms="-rwx------") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_cron_weekly/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_cron_weekly/rule.yml -index c4ea836530..d1d9bbc766 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_cron_weekly/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_cron_weekly/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232040 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/cron.weekly", perms="-rwx------") }}}' - -diff --git a/linux_os/guide/services/cron_and_at/file_permissions_crontab/rule.yml b/linux_os/guide/services/cron_and_at/file_permissions_crontab/rule.yml -index e29f650239..1befe3b76a 100644 ---- a/linux_os/guide/services/cron_and_at/file_permissions_crontab/rule.yml -+++ b/linux_os/guide/services/cron_and_at/file_permissions_crontab/rule.yml -@@ -40,6 +40,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232265 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/crontab", perms="-rw-------") }}}' - -diff --git a/linux_os/guide/services/fapolicyd/package_fapolicyd_installed/rule.yml b/linux_os/guide/services/fapolicyd/package_fapolicyd_installed/rule.yml -index febad1cc87..1a37a12aca 100644 ---- a/linux_os/guide/services/fapolicyd/package_fapolicyd_installed/rule.yml -+++ b/linux_os/guide/services/fapolicyd/package_fapolicyd_installed/rule.yml -@@ -24,6 +24,7 @@ references: - srg: SRG-OS-000370-GPOS-00155,SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00230 - stigid@ol8: OL08-00-040135 - stigid@rhel8: RHEL-08-040135 -+ stigid@rhel9: RHEL-09-433010 - - ocil_clause: 'the fapolicyd package is not installed' - -diff --git a/linux_os/guide/services/fapolicyd/service_fapolicyd_enabled/rule.yml b/linux_os/guide/services/fapolicyd/service_fapolicyd_enabled/rule.yml -index 57e01f7231..95b90e426e 100644 ---- a/linux_os/guide/services/fapolicyd/service_fapolicyd_enabled/rule.yml -+++ b/linux_os/guide/services/fapolicyd/service_fapolicyd_enabled/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000370-GPOS-00155,SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00230 - stigid@ol8: OL08-00-040136 - stigid@rhel8: RHEL-08-040136 -+ stigid@rhel9: RHEL-09-433015 - - ocil_clause: 'the service is not enabled' - -diff --git a/linux_os/guide/services/ftp/disabling_vsftpd/package_vsftpd_removed/rule.yml b/linux_os/guide/services/ftp/disabling_vsftpd/package_vsftpd_removed/rule.yml -index f88eea4f05..28ba822927 100644 ---- a/linux_os/guide/services/ftp/disabling_vsftpd/package_vsftpd_removed/rule.yml -+++ b/linux_os/guide/services/ftp/disabling_vsftpd/package_vsftpd_removed/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-040360 - stigid@rhel7: RHEL-07-040690 - stigid@rhel8: RHEL-08-040360 -+ stigid@rhel9: RHEL-09-215015 - stigid@sle12: SLES-12-030011 - stigid@sle15: SLES-15-010030 - -diff --git a/linux_os/guide/services/kerberos/kerberos_disable_no_keytab/rule.yml b/linux_os/guide/services/kerberos/kerberos_disable_no_keytab/rule.yml -index 87375c0d9c..764d43d0e1 100644 ---- a/linux_os/guide/services/kerberos/kerberos_disable_no_keytab/rule.yml -+++ b/linux_os/guide/services/kerberos/kerberos_disable_no_keytab/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000120-GPOS-00061 - stigid@ol8: OL08-00-010161 - stigid@rhel8: RHEL-08-010161 -+ stigid@rhel9: RHEL-09-611205 - - platforms: - - krb5_server_older_than_1_17-18 and krb5_workstation_older_than_1_17-18 -diff --git a/linux_os/guide/services/mail/package_s-nail_installed/rule.yml b/linux_os/guide/services/mail/package_s-nail_installed/rule.yml -index e14fbc9f35..ef11e38638 100644 ---- a/linux_os/guide/services/mail/package_s-nail_installed/rule.yml -+++ b/linux_os/guide/services/mail/package_s-nail_installed/rule.yml -@@ -21,6 +21,7 @@ references: - disa: CCI-001744 - nist: CM-3(5) - srg: SRG-OS-000363-GPOS-00150 -+ stigid@rhel9: RHEL-09-215095 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/services/mail/package_sendmail_removed/rule.yml b/linux_os/guide/services/mail/package_sendmail_removed/rule.yml -index 3674a8609a..f92f05f493 100644 ---- a/linux_os/guide/services/mail/package_sendmail_removed/rule.yml -+++ b/linux_os/guide/services/mail/package_sendmail_removed/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-040002 - stigid@rhel8: RHEL-08-040002 -+ stigid@rhel9: RHEL-09-215020 - - {{{ complete_ocil_entry_package(package="sendmail") }}} - -diff --git a/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias/rule.yml b/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias/rule.yml -index 1754bee03f..d3108b262d 100644 ---- a/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias/rule.yml -+++ b/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias/rule.yml -@@ -31,6 +31,7 @@ references: - nist: CM-6(a) - nist@sle12: AU-5(a),AU-5.1(ii) - srg: SRG-OS-000046-GPOS-00022 -+ stigid@rhel9: RHEL-09-653125 - stigid@sle12: SLES-12-020050 - stigid@sle15: SLES-15-030580 - -diff --git a/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias_postmaster/rule.yml b/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias_postmaster/rule.yml -index 1f8ff58312..d81aa3e411 100644 ---- a/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias_postmaster/rule.yml -+++ b/linux_os/guide/services/mail/postfix_client/postfix_client_configure_mail_alias_postmaster/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000046-GPOS-00022 - stigid@ol8: OL08-00-030030 - stigid@rhel8: RHEL-08-030030 -+ stigid@rhel9: RHEL-09-252060 - - ocil_clause: 'the alias is not set or is not root' - -diff --git a/linux_os/guide/services/mail/postfix_harden_os/postfix_server_cfg/postfix_server_relay/postfix_prevent_unrestricted_relay/rule.yml b/linux_os/guide/services/mail/postfix_harden_os/postfix_server_cfg/postfix_server_relay/postfix_prevent_unrestricted_relay/rule.yml -index 379999e33a..3c756f8139 100644 ---- a/linux_os/guide/services/mail/postfix_harden_os/postfix_server_cfg/postfix_server_relay/postfix_prevent_unrestricted_relay/rule.yml -+++ b/linux_os/guide/services/mail/postfix_harden_os/postfix_server_cfg/postfix_server_relay/postfix_prevent_unrestricted_relay/rule.yml -@@ -28,6 +28,7 @@ references: - stigid@ol8: OL08-00-040290 - stigid@rhel7: RHEL-07-040680 - stigid@rhel8: RHEL-08-040290 -+ stigid@rhel9: RHEL-09-252050 - - ocil_clause: 'the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject"' - -diff --git a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_krb_sec_remote_filesystems/rule.yml b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_krb_sec_remote_filesystems/rule.yml -index a48edf7794..6f8ceede54 100644 ---- a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_krb_sec_remote_filesystems/rule.yml -+++ b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_krb_sec_remote_filesystems/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040750 - stigid@rhel7: RHEL-07-040750 -+ stigid@rhel9: RHEL-09-231060 - - ocil_clause: 'the setting is not configured, has the ''sys'' option added, or does not have all Kerberos options added' - -diff --git a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nodev_remote_filesystems/rule.yml b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nodev_remote_filesystems/rule.yml -index 6911a71631..21109c2282 100644 ---- a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nodev_remote_filesystems/rule.yml -+++ b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nodev_remote_filesystems/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010640 - stigid@rhel8: RHEL-08-010640 -+ stigid@rhel9: RHEL-09-231065 - - ocil_clause: 'the setting does not show' - -diff --git a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_noexec_remote_filesystems/rule.yml b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_noexec_remote_filesystems/rule.yml -index 95c9022460..2fe699c03f 100644 ---- a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_noexec_remote_filesystems/rule.yml -+++ b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_noexec_remote_filesystems/rule.yml -@@ -35,6 +35,7 @@ references: - stigid@ol8: OL08-00-010630 - stigid@rhel7: RHEL-07-021021 - stigid@rhel8: RHEL-08-010630 -+ stigid@rhel9: RHEL-09-231070 - stigid@sle12: SLES-12-010820 - stigid@sle15: SLES-15-040170 - -diff --git a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nosuid_remote_filesystems/rule.yml b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nosuid_remote_filesystems/rule.yml -index c2805a5cdb..6efe0d94b8 100644 ---- a/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nosuid_remote_filesystems/rule.yml -+++ b/linux_os/guide/services/nfs_and_rpc/nfs_configuring_clients/mounting_remote_filesystems/mount_option_nosuid_remote_filesystems/rule.yml -@@ -33,6 +33,7 @@ references: - stigid@ol8: OL08-00-010650 - stigid@rhel7: RHEL-07-021020 - stigid@rhel8: RHEL-08-010650 -+ stigid@rhel9: RHEL-09-231075 - stigid@sle12: SLES-12-010810 - stigid@sle15: SLES-15-040160 - -diff --git a/linux_os/guide/services/nfs_and_rpc/package_nfs-utils_removed/rule.yml b/linux_os/guide/services/nfs_and_rpc/package_nfs-utils_removed/rule.yml -index 3de7c8db0c..fedf500ac7 100644 ---- a/linux_os/guide/services/nfs_and_rpc/package_nfs-utils_removed/rule.yml -+++ b/linux_os/guide/services/nfs_and_rpc/package_nfs-utils_removed/rule.yml -@@ -31,6 +31,7 @@ references: - cis@sle15: 2.2.7 - pcidss4: "2.2.4" - srg: SRG-OS-000095-GPOS-00049 -+ stigid@rhel9: RHEL-09-215025 - - {{{ complete_ocil_entry_package(package="nfs-utils") }}} - -diff --git a/linux_os/guide/services/ntp/chronyd_client_only/rule.yml b/linux_os/guide/services/ntp/chronyd_client_only/rule.yml -index 0e9ab7fe9e..1b7d066a44 100644 ---- a/linux_os/guide/services/ntp/chronyd_client_only/rule.yml -+++ b/linux_os/guide/services/ntp/chronyd_client_only/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000096-GPOS-00050,SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-030741 - stigid@rhel8: RHEL-08-030741 -+ stigid@rhel9: RHEL-09-252025 - - ocil_clause: 'the "port" option is not set to "0", is commented out, or is missing' - -diff --git a/linux_os/guide/services/ntp/chronyd_no_chronyc_network/rule.yml b/linux_os/guide/services/ntp/chronyd_no_chronyc_network/rule.yml -index 7821067344..4d71f0aa15 100644 ---- a/linux_os/guide/services/ntp/chronyd_no_chronyc_network/rule.yml -+++ b/linux_os/guide/services/ntp/chronyd_no_chronyc_network/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000096-GPOS-00050,SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-030742 - stigid@rhel8: RHEL-08-030742 -+ stigid@rhel9: RHEL-09-252030 - - ocil_clause: 'the "cmdport" option is not set to "0", is commented out, or is missing' - -diff --git a/linux_os/guide/services/ntp/chronyd_or_ntpd_set_maxpoll/rule.yml b/linux_os/guide/services/ntp/chronyd_or_ntpd_set_maxpoll/rule.yml -index b7bef7d30e..8a95dbe3a3 100644 ---- a/linux_os/guide/services/ntp/chronyd_or_ntpd_set_maxpoll/rule.yml -+++ b/linux_os/guide/services/ntp/chronyd_or_ntpd_set_maxpoll/rule.yml -@@ -96,6 +96,7 @@ references: - stigid@ol8: OL08-00-030740 - stigid@rhel7: RHEL-07-040500 - stigid@rhel8: RHEL-08-030740 -+ stigid@rhel9: RHEL-09-252020 - stigid@sle12: SLES-12-030300 - stigid@sle15: SLES-15-010400 - stigid@ubuntu2004: UBTU-20-010435 -diff --git a/linux_os/guide/services/ntp/chronyd_server_directive/rule.yml b/linux_os/guide/services/ntp/chronyd_server_directive/rule.yml -index 0b386f6bcb..556495bccf 100644 ---- a/linux_os/guide/services/ntp/chronyd_server_directive/rule.yml -+++ b/linux_os/guide/services/ntp/chronyd_server_directive/rule.yml -@@ -24,6 +24,7 @@ references: - srg: SRG-OS-000355-GPOS-00143,SRG-OS-000356-GPOS-00144,SRG-OS-000359-GPOS-00146 - stigid@ol8: OL08-00-030740 - stigid@rhel8: RHEL-08-030740 -+ stigid@rhel9: RHEL-09-252020 - - ocil_clause: 'an authoritative remote time server is not configured or configured with pool directive' - -diff --git a/linux_os/guide/services/ntp/package_chrony_installed/rule.yml b/linux_os/guide/services/ntp/package_chrony_installed/rule.yml -index d384a57e09..745235cbff 100644 ---- a/linux_os/guide/services/ntp/package_chrony_installed/rule.yml -+++ b/linux_os/guide/services/ntp/package_chrony_installed/rule.yml -@@ -40,6 +40,7 @@ references: - pcidss: Req-10.4 - pcidss4: "10.6.1" - srg: SRG-OS-000355-GPOS-00143 -+ stigid@rhel9: RHEL-09-252010 - stigid@ubuntu2004: UBTU-20-010435 - - ocil_clause: 'the package is not installed' -diff --git a/linux_os/guide/services/ntp/service_chronyd_enabled/rule.yml b/linux_os/guide/services/ntp/service_chronyd_enabled/rule.yml -index 62292ba18d..c0d7d16ebe 100644 ---- a/linux_os/guide/services/ntp/service_chronyd_enabled/rule.yml -+++ b/linux_os/guide/services/ntp/service_chronyd_enabled/rule.yml -@@ -32,6 +32,7 @@ references: - cis@ubuntu2204: 2.1.2.3 - ism: 0988,1405 - srg: SRG-OS-000355-GPOS-00143 -+ stigid@rhel9: RHEL-09-252015 - - ocil_clause: 'the chronyd process is not running' - -diff --git a/linux_os/guide/services/obsolete/nis/package_ypserv_removed/rule.yml b/linux_os/guide/services/obsolete/nis/package_ypserv_removed/rule.yml -index b057fc5a89..c91b8af25a 100644 ---- a/linux_os/guide/services/obsolete/nis/package_ypserv_removed/rule.yml -+++ b/linux_os/guide/services/obsolete/nis/package_ypserv_removed/rule.yml -@@ -44,6 +44,7 @@ references: - srg: SRG-OS-000095-GPOS-00049 - stigid@ol7: OL07-00-020010 - stigid@rhel7: RHEL-07-020010 -+ stigid@rhel9: RHEL-09-215030 - - {{{ complete_ocil_entry_package(package="ypserv") }}} - -diff --git a/linux_os/guide/services/obsolete/r_services/no_host_based_files/rule.yml b/linux_os/guide/services/obsolete/r_services/no_host_based_files/rule.yml -index 7ba8c10081..d695c7f41a 100644 ---- a/linux_os/guide/services/obsolete/r_services/no_host_based_files/rule.yml -+++ b/linux_os/guide/services/obsolete/r_services/no_host_based_files/rule.yml -@@ -31,6 +31,7 @@ references: - stigid@ol8: OL08-00-010460 - stigid@rhel7: RHEL-07-040550 - stigid@rhel8: RHEL-08-010460 -+ stigid@rhel9: RHEL-09-252070 - stigid@sle12: SLES-12-010410 - stigid@sle15: SLES-15-040030 - -diff --git a/linux_os/guide/services/obsolete/r_services/no_user_host_based_files/rule.yml b/linux_os/guide/services/obsolete/r_services/no_user_host_based_files/rule.yml -index 8eb7f2db57..f8215f46cf 100644 ---- a/linux_os/guide/services/obsolete/r_services/no_user_host_based_files/rule.yml -+++ b/linux_os/guide/services/obsolete/r_services/no_user_host_based_files/rule.yml -@@ -34,6 +34,7 @@ references: - stigid@ol8: OL08-00-010470 - stigid@rhel7: RHEL-07-040540 - stigid@rhel8: RHEL-08-010470 -+ stigid@rhel9: RHEL-09-252075 - stigid@sle12: SLES-12-010400 - stigid@sle15: SLES-15-040020 - -diff --git a/linux_os/guide/services/obsolete/r_services/package_rsh-server_removed/rule.yml b/linux_os/guide/services/obsolete/r_services/package_rsh-server_removed/rule.yml -index ccfe39dee5..80e7dd7a88 100644 ---- a/linux_os/guide/services/obsolete/r_services/package_rsh-server_removed/rule.yml -+++ b/linux_os/guide/services/obsolete/r_services/package_rsh-server_removed/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-040010 - stigid@rhel7: RHEL-07-020000 - stigid@rhel8: RHEL-08-040010 -+ stigid@rhel9: RHEL-09-215035 - stigid@ubuntu2004: UBTU-20-010406 - - {{{ complete_ocil_entry_package(package="rsh-server") }}} -diff --git a/linux_os/guide/services/obsolete/telnet/package_telnet-server_removed/rule.yml b/linux_os/guide/services/obsolete/telnet/package_telnet-server_removed/rule.yml -index 080785dd8f..bba0c3e05c 100644 ---- a/linux_os/guide/services/obsolete/telnet/package_telnet-server_removed/rule.yml -+++ b/linux_os/guide/services/obsolete/telnet/package_telnet-server_removed/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-040000 - stigid@rhel7: RHEL-07-021710 - stigid@rhel8: RHEL-08-040000 -+ stigid@rhel9: RHEL-09-215040 - stigid@sle12: SLES-12-030000 - stigid@sle15: SLES-15-010180 - -diff --git a/linux_os/guide/services/obsolete/tftp/package_tftp-server_removed/rule.yml b/linux_os/guide/services/obsolete/tftp/package_tftp-server_removed/rule.yml -index 9268c850cf..98c32a775e 100644 ---- a/linux_os/guide/services/obsolete/tftp/package_tftp-server_removed/rule.yml -+++ b/linux_os/guide/services/obsolete/tftp/package_tftp-server_removed/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-040190 - stigid@rhel7: RHEL-07-040700 - stigid@rhel8: RHEL-08-040190 -+ stigid@rhel9: RHEL-09-215060 - - {{{ complete_ocil_entry_package(package="tftp-server") }}} - -diff --git a/linux_os/guide/services/obsolete/tftp/tftpd_uses_secure_mode/rule.yml b/linux_os/guide/services/obsolete/tftp/tftpd_uses_secure_mode/rule.yml -index 9dd7a8bdde..f9773efea4 100644 ---- a/linux_os/guide/services/obsolete/tftp/tftpd_uses_secure_mode/rule.yml -+++ b/linux_os/guide/services/obsolete/tftp/tftpd_uses_secure_mode/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-040350 - stigid@rhel7: RHEL-07-040720 - stigid@rhel8: RHEL-08-040350 -+ stigid@rhel9: RHEL-09-252055 - - ocil_clause: |- - {{%- if product in ["rhel7","ol7","rhel8","ol8","rhv4"] %}} -diff --git a/linux_os/guide/services/rng/service_rngd_enabled/rule.yml b/linux_os/guide/services/rng/service_rngd_enabled/rule.yml -index 4e39496fcc..0a9f13f77a 100644 ---- a/linux_os/guide/services/rng/service_rngd_enabled/rule.yml -+++ b/linux_os/guide/services/rng/service_rngd_enabled/rule.yml -@@ -24,6 +24,12 @@ references: - ospp: FCS_RBG_EXT.1 - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010471 -+ stigid@rhel8: RHEL-08-010471 -+ stigid@rhel9: RHEL-09-211035 -+ -+{{% if product == "ol8" %}} -+platform: os_linux[ol]<8.4 or not runtime_kernel_fips_enabled -+{{% endif %}} - - ocil_clause: '{{{ ocil_clause_service_enabled("rngd") }}}' - -diff --git a/linux_os/guide/services/routing/disabling_quagga/package_quagga_removed/rule.yml b/linux_os/guide/services/routing/disabling_quagga/package_quagga_removed/rule.yml -index 40f9fa887f..d35875cda8 100644 ---- a/linux_os/guide/services/routing/disabling_quagga/package_quagga_removed/rule.yml -+++ b/linux_os/guide/services/routing/disabling_quagga/package_quagga_removed/rule.yml -@@ -30,6 +30,7 @@ references: - nist: CM-7(a),CM-7(b),CM-6(a) - nist-csf: PR.PT-4 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-215065 - - {{{ complete_ocil_entry_package(package="quagga") }}} - -diff --git a/linux_os/guide/services/ssh/file_groupowner_sshd_config/rule.yml b/linux_os/guide/services/ssh/file_groupowner_sshd_config/rule.yml -index 2262fb3b8b..67e65e6e17 100644 ---- a/linux_os/guide/services/ssh/file_groupowner_sshd_config/rule.yml -+++ b/linux_os/guide/services/ssh/file_groupowner_sshd_config/rule.yml -@@ -41,6 +41,7 @@ references: - nist: AC-17(a),CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-255105 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/ssh/sshd_config", group="root") }}}' - -diff --git a/linux_os/guide/services/ssh/file_owner_sshd_config/rule.yml b/linux_os/guide/services/ssh/file_owner_sshd_config/rule.yml -index 8785509dcf..bb5690e7d5 100644 ---- a/linux_os/guide/services/ssh/file_owner_sshd_config/rule.yml -+++ b/linux_os/guide/services/ssh/file_owner_sshd_config/rule.yml -@@ -41,6 +41,7 @@ references: - nist: AC-17(a),CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-255110 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/ssh/sshd_config", owner="root") }}}' - -diff --git a/linux_os/guide/services/ssh/file_permissions_sshd_config/rule.yml b/linux_os/guide/services/ssh/file_permissions_sshd_config/rule.yml -index a69ba302e0..5f1d6ced1a 100644 ---- a/linux_os/guide/services/ssh/file_permissions_sshd_config/rule.yml -+++ b/linux_os/guide/services/ssh/file_permissions_sshd_config/rule.yml -@@ -42,6 +42,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-255115 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/ssh/sshd_config", perms="-rw-------") }}}' - -diff --git a/linux_os/guide/services/ssh/file_permissions_sshd_private_key/rule.yml b/linux_os/guide/services/ssh/file_permissions_sshd_private_key/rule.yml -index db40366db3..3cf5cbef5b 100644 ---- a/linux_os/guide/services/ssh/file_permissions_sshd_private_key/rule.yml -+++ b/linux_os/guide/services/ssh/file_permissions_sshd_private_key/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-010490 - stigid@rhel7: RHEL-07-040420 - stigid@rhel8: RHEL-08-010490 -+ stigid@rhel9: RHEL-09-255120 - stigid@sle12: SLES-12-030220 - stigid@sle15: SLES-15-040250 - -diff --git a/linux_os/guide/services/ssh/file_permissions_sshd_pub_key/rule.yml b/linux_os/guide/services/ssh/file_permissions_sshd_pub_key/rule.yml -index 00d4222c82..c26d859dd8 100644 ---- a/linux_os/guide/services/ssh/file_permissions_sshd_pub_key/rule.yml -+++ b/linux_os/guide/services/ssh/file_permissions_sshd_pub_key/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-010480 - stigid@rhel7: RHEL-07-040410 - stigid@rhel8: RHEL-08-010480 -+ stigid@rhel9: RHEL-09-255125 - stigid@sle12: SLES-12-030210 - stigid@sle15: SLES-15-040240 - -diff --git a/linux_os/guide/services/ssh/package_openssh-clients_installed/rule.yml b/linux_os/guide/services/ssh/package_openssh-clients_installed/rule.yml -index 36ac1f29dc..f32f1428f6 100644 ---- a/linux_os/guide/services/ssh/package_openssh-clients_installed/rule.yml -+++ b/linux_os/guide/services/ssh/package_openssh-clients_installed/rule.yml -@@ -20,6 +20,7 @@ identifiers: - references: - ospp: FIA_UAU.5,FTP_ITC_EXT.1,FCS_SSH_EXT.1,FCS_SSHC_EXT.1 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-255020 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/services/ssh/package_openssh-server_installed/rule.yml b/linux_os/guide/services/ssh/package_openssh-server_installed/rule.yml -index 9847733617..2a665e70ed 100644 ---- a/linux_os/guide/services/ssh/package_openssh-server_installed/rule.yml -+++ b/linux_os/guide/services/ssh/package_openssh-server_installed/rule.yml -@@ -32,6 +32,7 @@ references: - stigid@ol8: OL08-00-040159 - stigid@rhel7: RHEL-07-040300 - stigid@rhel8: RHEL-08-040159 -+ stigid@rhel9: RHEL-09-255010 - stigid@ubuntu2004: UBTU-20-010042 - - ocil_clause: 'the package is not installed' -diff --git a/linux_os/guide/services/ssh/service_sshd_enabled/rule.yml b/linux_os/guide/services/ssh/service_sshd_enabled/rule.yml -index 5d7fd206b9..e070bd2295 100644 ---- a/linux_os/guide/services/ssh/service_sshd_enabled/rule.yml -+++ b/linux_os/guide/services/ssh/service_sshd_enabled/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-040160 - stigid@rhel7: RHEL-07-040310 - stigid@rhel8: RHEL-08-040160 -+ stigid@rhel9: RHEL-09-255015 - stigid@sle12: SLES-12-030100 - stigid@sle15: SLES-15-010530 - stigid@ubuntu2004: UBTU-20-010042 -diff --git a/linux_os/guide/services/ssh/ssh_client/ssh_keys_passphrase_protected/rule.yml b/linux_os/guide/services/ssh/ssh_client/ssh_keys_passphrase_protected/rule.yml -index 70d9bc7ccc..79602a4d84 100644 ---- a/linux_os/guide/services/ssh/ssh_client/ssh_keys_passphrase_protected/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_client/ssh_keys_passphrase_protected/rule.yml -@@ -25,6 +25,7 @@ identifiers: - references: - srg: SRG-OS-000067-GPOS-00035 - stigid@rhel8: RHEL-08-010100 -+ stigid@rhel9: RHEL-09-611190 - - ocil_clause: 'no ssh private key is accessible without a passcode' - -diff --git a/linux_os/guide/services/ssh/ssh_server/disable_host_auth/rule.yml b/linux_os/guide/services/ssh/ssh_server/disable_host_auth/rule.yml -index 8ee1007117..875b8f67ea 100644 ---- a/linux_os/guide/services/ssh/ssh_server/disable_host_auth/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/disable_host_auth/rule.yml -@@ -57,6 +57,7 @@ references: - srg: SRG-OS-000480-GPOS-00229 - stigid@ol7: OL07-00-010470 - stigid@rhel7: RHEL-07-010470 -+ stigid@rhel9: RHEL-09-255080 - - {{{ complete_ocil_entry_sshd_option(default="yes", option="HostbasedAuthentication", value="no") }}} - -diff --git a/linux_os/guide/services/ssh/ssh_server/firewalld_sshd_port_enabled/rule.yml b/linux_os/guide/services/ssh/ssh_server/firewalld_sshd_port_enabled/rule.yml -index fb69561525..f2ea1d0df7 100644 ---- a/linux_os/guide/services/ssh/ssh_server/firewalld_sshd_port_enabled/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/firewalld_sshd_port_enabled/rule.yml -@@ -27,6 +27,7 @@ references: - ism: "1416" - nist: AC-17(a),CM-6(b),CM-7(a),CM-7(b) - srg: SRG-OS-000096-GPOS-00050 -+ stigid@rhel9: RHEL-09-251035 - - platform: machine - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_compression/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_compression/rule.yml -index 184502a043..c1d415513e 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_compression/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_compression/rule.yml -@@ -39,6 +39,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040470 - stigid@rhel7: RHEL-07-040470 -+ stigid@rhel9: RHEL-09-255130 - stigid@sle12: SLES-12-030250 - - ocil_clause: 'it is commented out, or is not set to no or delayed' -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_empty_passwords/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_empty_passwords/rule.yml -index 6d4760f4b5..479f2e9b03 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_empty_passwords/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_empty_passwords/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-020330 - stigid@rhel7: RHEL-07-010300 - stigid@rhel8: RHEL-08-020330 -+ stigid@rhel9: RHEL-09-255040 - stigid@sle12: SLES-12-030150 - stigid@sle15: SLES-15-040440 - stigid@ubuntu2004: UBTU-20-010047 -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_gssapi_auth/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_gssapi_auth/rule.yml -index 84e5d497fa..8fc2c97356 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_gssapi_auth/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_gssapi_auth/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-010522 - stigid@rhel7: RHEL-07-040430 - stigid@rhel8: RHEL-08-010522 -+ stigid@rhel9: RHEL-09-255135 - - {{{ complete_ocil_entry_sshd_option(default="yes", option="GSSAPIAuthentication", value="no") }}} - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_kerb_auth/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_kerb_auth/rule.yml -index 05de4709b6..969e5a708e 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_kerb_auth/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_kerb_auth/rule.yml -@@ -45,6 +45,7 @@ references: - stigid@ol8: OL08-00-010521 - stigid@rhel7: RHEL-07-040440 - stigid@rhel8: RHEL-08-010521 -+ stigid@rhel9: RHEL-09-255140 - - {{{ complete_ocil_entry_sshd_option(default="yes", option="KerberosAuthentication", value="no") }}} - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_rhosts/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_rhosts/rule.yml -index 65cc31f4e5..6fd6719384 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_rhosts/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_rhosts/rule.yml -@@ -53,6 +53,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040350 - stigid@rhel7: RHEL-07-040350 -+ stigid@rhel9: RHEL-09-255145 - - {{{ complete_ocil_entry_sshd_option(default="yes", option="IgnoreRhosts", value="yes") }}} - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_root_login/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_root_login/rule.yml -index b5ff1dad5d..78063601ec 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_root_login/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_root_login/rule.yml -@@ -57,6 +57,7 @@ references: - stigid@ol8: OL08-00-010550 - stigid@rhel7: RHEL-07-040370 - stigid@rhel8: RHEL-08-010550 -+ stigid@rhel9: RHEL-09-255045 - stigid@sle12: SLES-12-030140 - stigid@sle15: SLES-15-020040 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_user_known_hosts/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_user_known_hosts/rule.yml -index 0bb62b7c93..780b846b0a 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_user_known_hosts/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_user_known_hosts/rule.yml -@@ -41,6 +41,7 @@ references: - stigid@ol8: OL08-00-010520 - stigid@rhel7: RHEL-07-040380 - stigid@rhel8: RHEL-08-010520 -+ stigid@rhel9: RHEL-09-255150 - stigid@sle12: SLES-12-030200 - stigid@sle15: SLES-15-040230 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_disable_x11_forwarding/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_disable_x11_forwarding/rule.yml -index 32174a5e88..aa0185e365 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_disable_x11_forwarding/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_disable_x11_forwarding/rule.yml -@@ -50,6 +50,7 @@ references: - stigid@ol8: OL08-00-040340 - stigid@rhel7: RHEL-07-040710 - stigid@rhel8: RHEL-08-040340 -+ stigid@rhel9: RHEL-09-255155 - stigid@sle15: SLES-15-040290 - stigid@ubuntu2004: UBTU-20-010048 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_do_not_permit_user_env/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_do_not_permit_user_env/rule.yml -index 11a371a738..f39506d96b 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_do_not_permit_user_env/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_do_not_permit_user_env/rule.yml -@@ -54,6 +54,7 @@ references: - stigid@ol8: OL08-00-010830 - stigid@rhel7: RHEL-07-010460 - stigid@rhel8: RHEL-08-010830 -+ stigid@rhel9: RHEL-09-255085 - stigid@sle12: SLES-12-030151 - stigid@sle15: SLES-15-040440 - stigid@ubuntu2004: UBTU-20-010047 -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_enable_pam/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_enable_pam/rule.yml -index fac8b26d1f..6ee445589b 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_enable_pam/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_enable_pam/rule.yml -@@ -38,6 +38,7 @@ references: - disa: CCI-000877 - pcidss4: "2.2.4" - srg: SRG-OS-000125-GPOS-00065 -+ stigid@rhel9: RHEL-09-255050 - stigid@ubuntu2004: UBTU-20-010035 - - {{{ complete_ocil_entry_sshd_option(default="no", option="UsePAM", value="yes") }}} -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_enable_pubkey_auth/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_enable_pubkey_auth/rule.yml -index 23654a9d08..8aea15b7dc 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_enable_pubkey_auth/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_enable_pubkey_auth/rule.yml -@@ -29,6 +29,7 @@ identifiers: - references: - disa: CCI-000765,CCI-000766,CCI-000767,CCI-000768 - srg: SRG-OS-000105-GPOS-00052,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055 -+ stigid@rhel9: RHEL-09-255035 - stigid@ubuntu2004: UBTU-20-010033 - - {{{ complete_ocil_entry_sshd_option(default="no", option="PubkeyAuthentication", value="yes") }}} -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_enable_strictmodes/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_enable_strictmodes/rule.yml -index 3228901547..65cf32d3ce 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_enable_strictmodes/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_enable_strictmodes/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-010500 - stigid@rhel7: RHEL-07-040450 - stigid@rhel8: RHEL-08-010500 -+ stigid@rhel9: RHEL-09-255160 - stigid@sle12: SLES-12-030230 - stigid@sle15: SLES-15-040260 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_enable_warning_banner/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_enable_warning_banner/rule.yml -index 595170d702..90dce2bd17 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_enable_warning_banner/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_enable_warning_banner/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-010040 - stigid@rhel7: RHEL-07-040170 - stigid@rhel8: RHEL-08-010040 -+ stigid@rhel9: RHEL-09-255025 - stigid@sle12: SLES-12-030050 - stigid@sle15: SLES-15-010040 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_print_last_log/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_print_last_log/rule.yml -index 6855040612..59b6850a0c 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_print_last_log/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_print_last_log/rule.yml -@@ -39,6 +39,7 @@ references: - stigid@ol8: OL08-00-020350 - stigid@rhel7: RHEL-07-040360 - stigid@rhel8: RHEL-08-020350 -+ stigid@rhel9: RHEL-09-255165 - stigid@sle12: SLES-12-030130 - stigid@sle15: SLES-15-020120 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml -index 9b1f144d7e..8cb93257c7 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000033-GPOS-00014 - stigid@ol8: OL08-00-040161 - stigid@rhel8: RHEL-08-040161 -+ stigid@rhel9: RHEL-09-255090 - - ocil_clause: 'it is commented out or is not set' - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_idle_timeout/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_set_idle_timeout/rule.yml -index 3502842769..bfd2909e11 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_set_idle_timeout/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_idle_timeout/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-010201 - stigid@rhel7: RHEL-07-040320 - stigid@rhel8: RHEL-08-010201 -+ stigid@rhel9: RHEL-09-255100 - stigid@sle12: SLES-12-030190 - stigid@sle15: SLES-15-010280 - stigid@ubuntu2004: UBTU-20-010037 -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_keepalive/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_set_keepalive/rule.yml -index 7ef1b837fc..f72209448d 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_set_keepalive/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_keepalive/rule.yml -@@ -59,6 +59,7 @@ references: - pcidss4: "8.2.8" - srg: SRG-OS-000163-GPOS-00072,SRG-OS-000279-GPOS-00109 - stigid@rhel8: RHEL-08-010200 -+ stigid@rhel9: RHEL-09-255095 - stigid@sle12: SLES-12-030191 - stigid@sle15: SLES-15-010320 - stigid@ubuntu2004: UBTU-20-010036 -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_loglevel_verbose/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_set_loglevel_verbose/rule.yml -index ea6007d5ce..0e95dab371 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_set_loglevel_verbose/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_loglevel_verbose/rule.yml -@@ -41,6 +41,7 @@ references: - pcidss: Req-2.2.4 - pcidss4: "2.2.6" - srg: SRG-OS-000032-GPOS-00013 -+ stigid@rhel9: RHEL-09-255030 - stigid@sle12: SLES-12-030110 - stigid@sle15: SLES-15-010150 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_use_priv_separation/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_use_priv_separation/rule.yml -index 8fef777e75..50c5ef57ac 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_use_priv_separation/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_use_priv_separation/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040460 - stigid@rhel7: RHEL-07-040460 -+ stigid@rhel9: RHEL-09-255170 - stigid@sle12: SLES-12-030240 - stigid@sle15: SLES-15-040270 - -diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_x11_use_localhost/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_x11_use_localhost/rule.yml -index 3a58720dd8..9e6d00a685 100644 ---- a/linux_os/guide/services/ssh/ssh_server/sshd_x11_use_localhost/rule.yml -+++ b/linux_os/guide/services/ssh/ssh_server/sshd_x11_use_localhost/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-040341 - stigid@rhel7: RHEL-07-040711 - stigid@rhel8: RHEL-08-040341 -+ stigid@rhel9: RHEL-09-255175 - stigid@sle12: SLES-12-030261 - stigid@ubuntu2004: UBTU-20-010049 - -diff --git a/linux_os/guide/services/sssd/sssd_certificate_verification/rule.yml b/linux_os/guide/services/sssd/sssd_certificate_verification/rule.yml -index cd24ded03c..09286f60cd 100644 ---- a/linux_os/guide/services/sssd/sssd_certificate_verification/rule.yml -+++ b/linux_os/guide/services/sssd/sssd_certificate_verification/rule.yml -@@ -26,7 +26,7 @@ references: - srg: SRG-OS-000375-GPOS-00160,SRG-OS-000377-GPOS-00162 - stigid@ol8: OL08-00-010400 - stigid@rhel8: RHEL-08-010400 -- -+ stigid@rhel9: RHEL-09-611170 - - ocil_clause: 'certificate_verification in sssd is not configured' - -diff --git a/linux_os/guide/services/sssd/sssd_enable_certmap/rule.yml b/linux_os/guide/services/sssd/sssd_enable_certmap/rule.yml -index ed8b1c4e18..833e4d405d 100644 ---- a/linux_os/guide/services/sssd/sssd_enable_certmap/rule.yml -+++ b/linux_os/guide/services/sssd/sssd_enable_certmap/rule.yml -@@ -32,6 +32,7 @@ references: - srg: SRG-OS-000068-GPOS-00036 - stigid@ol8: OL08-00-020090 - stigid@rhel8: RHEL-08-020090 -+ stigid@rhel9: RHEL-09-631015 - - warnings: - - general: |- -diff --git a/linux_os/guide/services/sssd/sssd_enable_smartcards/rule.yml b/linux_os/guide/services/sssd/sssd_enable_smartcards/rule.yml -index 6ed233a709..f026bdb489 100644 ---- a/linux_os/guide/services/sssd/sssd_enable_smartcards/rule.yml -+++ b/linux_os/guide/services/sssd/sssd_enable_smartcards/rule.yml -@@ -53,6 +53,7 @@ references: - srg: SRG-OS-000375-GPOS-00160,SRG-OS-000105-GPOS-00052,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000108-GPOS-00055 - stigid@ol8: OL08-00-020250 - stigid@rhel8: RHEL-08-020250 -+ stigid@rhel9: RHEL-09-611165 - - ocil_clause: 'smart cards are not enabled in SSSD' - -diff --git a/linux_os/guide/services/sssd/sssd_has_trust_anchor/rule.yml b/linux_os/guide/services/sssd/sssd_has_trust_anchor/rule.yml -index d71208630e..2e8193420f 100644 ---- a/linux_os/guide/services/sssd/sssd_has_trust_anchor/rule.yml -+++ b/linux_os/guide/services/sssd/sssd_has_trust_anchor/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000066-GPOS-00034,SRG-OS-000384-GPOS-00167 - stigid@ol8: OL08-00-010090 - stigid@rhel8: RHEL-08-010090 -+ stigid@rhel9: RHEL-09-631010 - - warnings: - - general: |- -diff --git a/linux_os/guide/services/sssd/sssd_offline_cred_expiration/rule.yml b/linux_os/guide/services/sssd/sssd_offline_cred_expiration/rule.yml -index 15ef6aa83e..fabacb4e3b 100644 ---- a/linux_os/guide/services/sssd/sssd_offline_cred_expiration/rule.yml -+++ b/linux_os/guide/services/sssd/sssd_offline_cred_expiration/rule.yml -@@ -48,6 +48,7 @@ references: - srg: SRG-OS-000383-GPOS-00166 - stigid@ol8: OL08-00-020290 - stigid@rhel8: RHEL-08-020290 -+ stigid@rhel9: RHEL-09-631020 - stigid@sle12: SLES-12-010680 - stigid@sle15: SLES-15-010500 - stigid@ubuntu2004: UBTU-20-010441 -diff --git a/linux_os/guide/services/usbguard/configure_usbguard_auditbackend/rule.yml b/linux_os/guide/services/usbguard/configure_usbguard_auditbackend/rule.yml -index c20527bf10..ca6cb336ca 100644 ---- a/linux_os/guide/services/usbguard/configure_usbguard_auditbackend/rule.yml -+++ b/linux_os/guide/services/usbguard/configure_usbguard_auditbackend/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000062-GPOS-00031,SRG-OS-000471-GPOS-00215,SRG-APP-000141-CTR-000315 - stigid@ol8: OL08-00-030603 - stigid@rhel8: RHEL-08-030603 -+ stigid@rhel9: RHEL-09-291025 - - platform: package[usbguard] - -diff --git a/linux_os/guide/services/usbguard/package_usbguard_installed/rule.yml b/linux_os/guide/services/usbguard/package_usbguard_installed/rule.yml -index 47a65aeb67..3926b5efe5 100644 ---- a/linux_os/guide/services/usbguard/package_usbguard_installed/rule.yml -+++ b/linux_os/guide/services/usbguard/package_usbguard_installed/rule.yml -@@ -52,6 +52,7 @@ references: - srg: SRG-OS-000378-GPOS-00163 - stigid@ol8: OL08-00-040139 - stigid@rhel8: RHEL-08-040139 -+ stigid@rhel9: RHEL-09-291015 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/services/usbguard/service_usbguard_enabled/rule.yml b/linux_os/guide/services/usbguard/service_usbguard_enabled/rule.yml -index e382a886fd..17e4ffa3d0 100644 ---- a/linux_os/guide/services/usbguard/service_usbguard_enabled/rule.yml -+++ b/linux_os/guide/services/usbguard/service_usbguard_enabled/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000378-GPOS-00163 - stigid@ol8: OL08-00-040141 - stigid@rhel8: RHEL-08-040141 -+ stigid@rhel9: RHEL-09-291020 - - ocil_clause: 'the service is not enabled' - -diff --git a/linux_os/guide/services/usbguard/usbguard_generate_policy/rule.yml b/linux_os/guide/services/usbguard/usbguard_generate_policy/rule.yml -index 40d4e8fb3a..a679baea6a 100644 ---- a/linux_os/guide/services/usbguard/usbguard_generate_policy/rule.yml -+++ b/linux_os/guide/services/usbguard/usbguard_generate_policy/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000378-GPOS-00163 - stigid@ol8: OL08-00-040140 - stigid@rhel8: RHEL-08-040140 -+ stigid@rhel9: RHEL-09-291030 - - ocil_clause: 'there is no evidence that unauthorized peripherals are being blocked before establishing a connection' - -diff --git a/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_remove_packages/rule.yml b/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_remove_packages/rule.yml -index 607ed945c1..b7a5cea6d7 100644 ---- a/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_remove_packages/rule.yml -+++ b/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_remove_packages/rule.yml -@@ -46,6 +46,7 @@ references: - stigid@ol8: OL08-00-040320 - stigid@rhel7: RHEL-07-040730 - stigid@rhel8: RHEL-08-040320 -+ stigid@rhel9: RHEL-09-215070 - - ocil_clause: 'xorg related packages are not removed and run level is not correctly configured' - -diff --git a/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_runlevel_target/rule.yml b/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_runlevel_target/rule.yml -index ab3b7ccd5a..a61727fd0f 100644 ---- a/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_runlevel_target/rule.yml -+++ b/linux_os/guide/services/xwindows/disabling_xwindows/xwindows_runlevel_target/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040321 - stigid@rhel8: RHEL-08-040321 -+ stigid@rhel9: RHEL-09-211030 - - ocil_clause: 'the system default target is not set to "multi-user.target" and the Information System Security Officer (ISSO) lacks a documented requirement for a graphical user interface' - -diff --git a/linux_os/guide/system/accounts/accounts-banners/banner_etc_issue/rule.yml b/linux_os/guide/system/accounts/accounts-banners/banner_etc_issue/rule.yml -index dbae8dd3ad..4d159a35eb 100644 ---- a/linux_os/guide/system/accounts/accounts-banners/banner_etc_issue/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-banners/banner_etc_issue/rule.yml -@@ -121,6 +121,7 @@ references: - stigid@ol8: OL08-00-010060 - stigid@rhel7: RHEL-07-010050 - stigid@rhel8: RHEL-08-010060 -+ stigid@rhel9: RHEL-09-211020 - stigid@sle12: SLES-12-010030 - stigid@sle15: SLES-15-010020 - -diff --git a/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_banner_enabled/rule.yml b/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_banner_enabled/rule.yml -index b21996ff49..6bfe3b563b 100644 ---- a/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_banner_enabled/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-banners/gui_login_banner/dconf_gnome_banner_enabled/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-010049 - stigid@rhel7: RHEL-07-010030 - stigid@rhel8: RHEL-08-010049 -+ stigid@rhel9: RHEL-09-271010,RHEL-09-271015 - stigid@sle12: SLES-12-010040 - stigid@sle15: SLES-15-010080 - stigid@ubuntu2004: UBTU-20-010002 -diff --git a/linux_os/guide/system/accounts/accounts-pam/disallow_bypass_password_sudo/rule.yml b/linux_os/guide/system/accounts/accounts-pam/disallow_bypass_password_sudo/rule.yml -index 2c5fbef58f..0859ad2d59 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/disallow_bypass_password_sudo/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/disallow_bypass_password_sudo/rule.yml -@@ -31,6 +31,7 @@ references: - stigid@ol8: OL08-00-010385 - stigid@rhel7: RHEL-07-010344 - stigid@rhel8: RHEL-08-010385 -+ stigid@rhel9: RHEL-09-611145 - stigid@sle12: SLES-12-010114 - stigid@sle15: SLES-15-020104 - -diff --git a/linux_os/guide/system/accounts/accounts-pam/display_login_attempts/rule.yml b/linux_os/guide/system/accounts/accounts-pam/display_login_attempts/rule.yml -index 81cdfc2024..76271fa257 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/display_login_attempts/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/display_login_attempts/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-020340 - stigid@rhel7: RHEL-07-040530 - stigid@rhel8: RHEL-08-020340 -+ stigid@rhel9: RHEL-09-412075 - stigid@sle12: SLES-12-010390 - stigid@sle15: SLES-15-020080 - stigid@ubuntu2004: UBTU-20-010453 -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_password_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_password_auth/rule.yml -index 74448292b2..ab60cf4b79 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_password_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_password_auth/rule.yml -@@ -24,6 +24,7 @@ references: - nist: AC-7 (a) - srg: SRG-OS-000021-GPOS-00005 - stigid@rhel8: RHEL-08-020026 -+ stigid@rhel9: RHEL-09-611035 - - ocil_clause: 'the pam_faillock.so module is not present in the "/etc/pam.d/password-auth" file with the "preauth" line listed before pam_unix.so' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_system_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_system_auth/rule.yml -index 912cd8c16a..6922b958cc 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_system_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_pam_faillock_system_auth/rule.yml -@@ -22,6 +22,7 @@ references: - nist: AC-7 (a) - srg: SRG-OS-000021-GPOS-00005 - stigid@rhel8: RHEL-08-020025 -+ stigid@rhel9: RHEL-09-611030 - - ocil_clause: 'the pam_faillock.so module is not present in the "/etc/pam.d/system-auth" file with the "preauth" line listed before pam_unix.so' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_selinux_faillock_dir/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_selinux_faillock_dir/rule.yml -index 61e58c8a05..9cba882763 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_selinux_faillock_dir/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/account_password_selinux_faillock_dir/rule.yml -@@ -23,7 +23,8 @@ references: - nist: AC-7 (a) - srg: SRG-OS-000021-GPOS-00005 - stigid@ol8: OL08-00-020027 -- stigid@rhel8: RHEL-08-020027 -+ stigid@rhel8: RHEL-08-020027,RHEL-08-020028 -+ stigid@rhel9: RHEL-09-431020 - - platform: machine - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_password_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_password_auth/rule.yml -index 6aaf7bf37f..01fc1800ed 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_password_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_password_auth/rule.yml -@@ -64,6 +64,7 @@ references: - stigid@ol8: OL08-00-020220 - stigid@rhel7: RHEL-07-010270 - stigid@rhel8: RHEL-08-020220 -+ stigid@rhel9: RHEL-09-611015 - - ocil_clause: |- - the pam_pwhistory.so module is not used, the "remember" module option is not set in -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_system_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_system_auth/rule.yml -index aeb999b8d1..05e8a99009 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_system_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_password_pam_pwhistory_remember_system_auth/rule.yml -@@ -64,6 +64,7 @@ references: - stigid@ol8: OL08-00-020221 - stigid@rhel7: RHEL-07-010270 - stigid@rhel8: RHEL-08-020221 -+ stigid@rhel9: RHEL-09-611020 - - ocil_clause: |- - the pam_pwhistory.so module is not used, the "remember" module option is not set in -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_audit/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_audit/rule.yml -index 038f8486c4..85f090e52f 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_audit/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_audit/rule.yml -@@ -20,6 +20,7 @@ references: - srg: SRG-OS-000021-GPOS-00005 - stigid@ol8: OL08-00-020021 - stigid@rhel8: RHEL-08-020021 -+ stigid@rhel9: RHEL-09-412045 - - ocil_clause: 'the "audit" option is not set, is missing or commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml -index 0fa9fac37c..42e2d0f258 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-020010 - stigid@rhel7: RHEL-07-010320 - stigid@rhel8: RHEL-08-020011 -+ stigid@rhel9: RHEL-09-411075 - - platform: package[pam] - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny_root/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny_root/rule.yml -index 94892c9d0e..6fd9186bd9 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny_root/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny_root/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-020022 - stigid@rhel7: RHEL-07-010330 - stigid@rhel8: RHEL-08-020023 -+ stigid@rhel9: RHEL-09-411080 - - ocil_clause: 'the "even_deny_root" option is not set, is missing or commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_dir/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_dir/rule.yml -index 28753f735a..749f570ac9 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_dir/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_dir/rule.yml -@@ -33,8 +33,9 @@ references: - disa: CCI-000044,CCI-002238 - nist: AC-7(b),AC-7(a),AC-7.1(ii) - srg: SRG-OS-000021-GPOS-00005,SRG-OS-000329-GPOS-00128 -- stigid@ol8: OL08-00-020016 -- stigid@rhel8: RHEL-08-020017 -+ stigid@ol8: OL08-00-020016,OL08-00-020017 -+ stigid@rhel8: RHEL-08-020016,RHEL-08-020017 -+ stigid@rhel9: RHEL-09-411105 - - ocil_clause: 'the "dir" option is not set to a non-default documented tally log directory, is missing or commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml -index 6a3f5b1697..db746f7c63 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-020012 - stigid@rhel7: RHEL-07-010320 - stigid@rhel8: RHEL-08-020012,RHEL-08-020013 -+ stigid@rhel9: RHEL-09-411085 - - platform: package[pam] - -diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml -index f55ff2cef0..2b554ef257 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml -@@ -66,7 +66,8 @@ references: - stigid@ol7: OL07-00-010320 - stigid@ol8: OL08-00-020014 - stigid@rhel7: RHEL-07-010320 -- stigid@rhel8: RHEL-08-020015 -+ stigid@rhel8: RHEL-08-020014,RHEL-08-020015 -+ stigid@rhel9: RHEL-09-411090 - - platform: package[pam] - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dcredit/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dcredit/rule.yml -index e67cd88351..e720e7015e 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dcredit/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dcredit/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-020130 - stigid@rhel7: RHEL-07-010140 - stigid@rhel8: RHEL-08-020130 -+ stigid@rhel9: RHEL-09-611070 - stigid@ubuntu2004: UBTU-20-010052 - - ocil_clause: 'the value of "dcredit" is a positive number or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dictcheck/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dictcheck/rule.yml -index d41ca6c264..26640dcd75 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dictcheck/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_dictcheck/rule.yml -@@ -31,6 +31,7 @@ references: - srg: SRG-OS-000480-GPOS-00225 - stigid@ol8: OL08-00-020300 - stigid@rhel8: RHEL-08-020300 -+ stigid@rhel9: RHEL-09-611105 - stigid@ubuntu2004: UBTU-20-010056 - - ocil_clause: '"dictcheck" does not have a value other than "0", or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_difok/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_difok/rule.yml -index e7fdf2e8b0..686bf9dbe8 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_difok/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_difok/rule.yml -@@ -49,6 +49,7 @@ references: - stigid@ol8: OL08-00-020170 - stigid@rhel7: RHEL-07-010160 - stigid@rhel8: RHEL-08-020170 -+ stigid@rhel9: RHEL-09-611115 - stigid@ubuntu2004: UBTU-20-010053 - - ocil_clause: 'the value of "difok" is set to less than "{{{ xccdf_value("var_password_pam_difok") }}}", or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_enforce_root/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_enforce_root/rule.yml -index 198475c876..34f694013f 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_enforce_root/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_enforce_root/rule.yml -@@ -29,6 +29,7 @@ references: - disa: CCI-000194,CCI-000193,CCI-001619,CCI-000205,CCI-000195,CCI-000192,CCI-000366 - nist: IA-5(c),IA-5(1)(a),CM-6(a),IA-5(4) - srg: SRG-OS-000072-GPOS-00040,SRG-OS-000071-GPOS-00039,SRG-OS-000070-GPOS-00038,SRG-OS-000266-GPOS-00101,SRG-OS-000078-GPOS-00046,SRG-OS-000480-GPOS-00225,SRG-OS-000069-GPOS-00037 -+ stigid@rhel9: RHEL-09-611060 - - ocil_clause: '"enforce_for_root" is commented or missing' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_lcredit/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_lcredit/rule.yml -index 5799a7b12e..2bd337a070 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_lcredit/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_lcredit/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-020120 - stigid@rhel7: RHEL-07-010130 - stigid@rhel8: RHEL-08-020120 -+ stigid@rhel9: RHEL-09-611065 - stigid@ubuntu2004: UBTU-20-010051 - - ocil_clause: 'the value of "lcredit" is a positive number or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxclassrepeat/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxclassrepeat/rule.yml -index 5f812e16fd..f502211ca3 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxclassrepeat/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxclassrepeat/rule.yml -@@ -41,6 +41,7 @@ references: - stigid@ol8: OL08-00-020140 - stigid@rhel7: RHEL-07-010190 - stigid@rhel8: RHEL-08-020140 -+ stigid@rhel9: RHEL-09-611120 - - ocil_clause: the value of "maxclassrepeat" is set to "0", more than "{{{ xccdf_value("var_password_pam_maxclassrepeat") }}}" or is commented out - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxrepeat/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxrepeat/rule.yml -index 8984b63d9b..816d07b465 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxrepeat/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_maxrepeat/rule.yml -@@ -43,6 +43,7 @@ references: - stigid@ol8: OL08-00-020150 - stigid@rhel7: RHEL-07-010180 - stigid@rhel8: RHEL-08-020150 -+ stigid@rhel9: RHEL-09-611125 - - ocil_clause: the value of "maxrepeat" is set to more than "{{{ xccdf_value("var_password_pam_maxrepeat") }}}" or is commented out - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minclass/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minclass/rule.yml -index 64f0915049..bcf48e4201 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minclass/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minclass/rule.yml -@@ -64,6 +64,7 @@ references: - stigid@ol8: OL08-00-020160 - stigid@rhel7: RHEL-07-010170 - stigid@rhel8: RHEL-08-020160 -+ stigid@rhel9: RHEL-09-611130 - - ocil_clause: the value of "minclass" is set to less than "{{{ xccdf_value("var_password_pam_minclass") }}}" or is commented out - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minlen/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minlen/rule.yml -index f75a680779..28c9fcbe92 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minlen/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_minlen/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-020230 - stigid@rhel7: RHEL-07-010280 - stigid@rhel8: RHEL-08-020230 -+ stigid@rhel9: RHEL-09-611090 - stigid@ubuntu2004: UBTU-20-010054 - - ocil_clause: 'the command does not return a "minlen" value of "{{{ xccdf_value("var_password_pam_minlen") }}}" or greater, does not return a line, or the line is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ocredit/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ocredit/rule.yml -index 632aa24dc5..cd398e39f8 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ocredit/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ocredit/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-020280 - stigid@rhel7: RHEL-07-010150 - stigid@rhel8: RHEL-08-020280 -+ stigid@rhel9: RHEL-09-611100 - stigid@ubuntu2004: UBTU-20-010055 - - ocil_clause: 'value of "ocredit" is a positive number or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_password_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_password_auth/rule.yml -index 24b8bb7b8c..bd3e9194af 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_password_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_password_auth/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000069-GPOS-00037,SRG-OS-000070-GPOS-00038,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-020100 - stigid@rhel8: RHEL-08-020100 -+ stigid@rhel9: RHEL-09-611040 - - ocil_clause: 'pam_pwquality.so is not enabled in password-auth' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_system_auth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_system_auth/rule.yml -index 7d123e7360..cf12069225 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_system_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_pwquality_system_auth/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-020101 - stigid@rhel8: RHEL-08-020101 -+ stigid@rhel9: RHEL-09-611045 - - ocil_clause: 'pam_pwquality.so is not enabled in system-auth' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_retry/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_retry/rule.yml -index 73f5ec7a6a..7159ff14d4 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_retry/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_retry/rule.yml -@@ -56,6 +56,7 @@ references: - stigid@ol8: OL08-00-020104 - stigid@rhel7: RHEL-07-010119 - stigid@rhel8: RHEL-08-020104 -+ stigid@rhel9: RHEL-09-611010 - stigid@ubuntu2004: UBTU-20-010057 - - ocil_clause: 'the value of "retry" is set to "0" or greater than "{{{ xccdf_value("var_password_pam_retry") }}}", or is missing' -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ucredit/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ucredit/rule.yml -index 6c631ea379..9ab3c177c3 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ucredit/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/password_quality_pwquality/accounts_password_pam_ucredit/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-020110 - stigid@rhel7: RHEL-07-010120 - stigid@rhel8: RHEL-08-020110 -+ stigid@rhel9: RHEL-09-611110 - stigid@ubuntu2004: UBTU-20-010050 - - ocil_clause: 'the value of "ucredit" is a positive number or is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_libuserconf/rule.yml b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_libuserconf/rule.yml -index cadfa1905f..2634808712 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_libuserconf/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_libuserconf/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000073-GPOS-00041 - stigid@ol7: OL07-00-010220 - stigid@rhel7: RHEL-07-010220 -+ stigid@rhel9: RHEL-09-611135 - - ocil_clause: crypt_style is not set to sha512 - -diff --git a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_logindefs/rule.yml b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_logindefs/rule.yml -index e58180a1b8..c7c68899f7 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_logindefs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_logindefs/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-010110 - stigid@rhel7: RHEL-07-010210 - stigid@rhel8: RHEL-08-010110 -+ stigid@rhel9: RHEL-09-611140 - stigid@sle12: SLES-12-010210 - stigid@sle15: SLES-15-010260 - stigid@ubuntu2004: UBTU-20-010404 -diff --git a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_passwordauth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_passwordauth/rule.yml -index 8d7b14d4e9..44a2ad62eb 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_passwordauth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_passwordauth/rule.yml -@@ -63,6 +63,7 @@ references: - stigid@ol8: OL08-00-010160 - stigid@rhel7: RHEL-07-010200 - stigid@rhel8: RHEL-08-010160 -+ stigid@rhel9: RHEL-09-671025 - - ocil_clause: 'it does not' - -diff --git a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_min_rounds_logindefs/rule.yml b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_min_rounds_logindefs/rule.yml -index 9a490a8bea..add30938b4 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_min_rounds_logindefs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_min_rounds_logindefs/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000073-GPOS-00041,SRG-OS-000120-GPOS-00061 - stigid@ol8: OL08-00-010130 - stigid@rhel8: RHEL-08-010130 -+ stigid@rhel9: RHEL-09-611150 - stigid@sle12: SLES-12-010240 - stigid@sle15: SLES-15-020190 - -diff --git a/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_burstaction/rule.yml b/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_burstaction/rule.yml -index 9c18a0c268..b8c635ecc4 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_burstaction/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_burstaction/rule.yml -@@ -73,6 +73,7 @@ references: - srg: SRG-OS-000324-GPOS-00125,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040172 - stigid@rhel8: RHEL-08-040172 -+ stigid@rhel9: RHEL-09-211045 - stigid@sle15: SLES-15-040062 - stigid@ubuntu2004: UBTU-20-010460 - -diff --git a/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_reboot/rule.yml b/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_reboot/rule.yml -index cdb3cbf457..d6ab8abde9 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_reboot/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/disable_ctrlaltdel_reboot/rule.yml -@@ -78,6 +78,7 @@ references: - stigid@ol8: OL08-00-040170 - stigid@rhel7: RHEL-07-020230 - stigid@rhel8: RHEL-08-040170 -+ stigid@rhel9: RHEL-09-211050 - stigid@sle12: SLES-12-010610 - stigid@sle15: SLES-15-040060 - stigid@ubuntu2004: UBTU-20-010460 -diff --git a/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml b/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -index cf5da2ae13..e320cf4c1f 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -@@ -48,6 +48,7 @@ references: - nist-csf: PR.AC-4,PR.AC-6,PR.PT-3 - ospp: FIA_UAU.1 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-212015 - - ocil_clause: 'Interactive boot is enabled at boot time' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/logind_session_timeout/rule.yml b/linux_os/guide/system/accounts/accounts-physical/logind_session_timeout/rule.yml -index 00e31fc215..acf6d8964b 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/logind_session_timeout/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/logind_session_timeout/rule.yml -@@ -41,6 +41,7 @@ references: - pcidss: Req-8.1.8 - srg: SRG-OS-000163-GPOS-00072 - stigid@rhel8: RHEL-08-020035 -+ stigid@rhel9: RHEL-09-412080 - - ocil_clause: "the option is not configured" - -diff --git a/linux_os/guide/system/accounts/accounts-physical/require_emergency_target_auth/rule.yml b/linux_os/guide/system/accounts/accounts-physical/require_emergency_target_auth/rule.yml -index 534b5a093c..b501d19935 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/require_emergency_target_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/require_emergency_target_auth/rule.yml -@@ -49,6 +49,7 @@ references: - stigid@ol7: OL07-00-010481 - stigid@ol8: OL08-00-010152 - stigid@rhel8: RHEL-08-010152 -+ stigid@rhel9: RHEL-09-611195 - - ocil_clause: 'the output is different' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/require_singleuser_auth/rule.yml b/linux_os/guide/system/accounts/accounts-physical/require_singleuser_auth/rule.yml -index bd617f3e8e..1d23a329a8 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/require_singleuser_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/require_singleuser_auth/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-010151 - stigid@rhel7: RHEL-07-010481 - stigid@rhel8: RHEL-08-010151 -+ stigid@rhel9: RHEL-09-611200 - - ocil_clause: 'the output is different' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_bashrc_exec_tmux/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_bashrc_exec_tmux/rule.yml -index 2b2bf88713..df711a8aae 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_bashrc_exec_tmux/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_bashrc_exec_tmux/rule.yml -@@ -27,6 +27,7 @@ references: - disa: CCI-000056,CCI-000058 - ospp: FMT_SMF_EXT.1,FMT_MOF_EXT.1,FTA_SSL.1 - srg: SRG-OS-000031-GPOS-00012,SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 -+ stigid@rhel9: RHEL-09-412015 - - platform: package[tmux] - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_after_time/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_after_time/rule.yml -index de8fab7e5a..6bcc443af6 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_after_time/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_after_time/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000029-GPOS-00010,SRG-OS-000031-GPOS-00012 - stigid@ol8: OL08-00-020070 - stigid@rhel8: RHEL-08-020070 -+ stigid@rhel9: RHEL-09-412025 - - ocil_clause: '"lock-after-time" is not set to "900" or less in the global tmux configuration file to enforce session lock after inactivity' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_command/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_command/rule.yml -index 80856b34de..084fb39032 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_command/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_command/rule.yml -@@ -31,6 +31,7 @@ references: - srg: SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 - stigid@ol8: OL08-00-020040 - stigid@rhel8: RHEL-08-020040 -+ stigid@rhel9: RHEL-09-412020 - - ocil_clause: 'the "lock-command" is not set in the global settings to call "vlock"' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_keybinding/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_keybinding/rule.yml -index 584d578103..884ac3e3c5 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_keybinding/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/configure_tmux_lock_keybinding/rule.yml -@@ -27,6 +27,7 @@ references: - srg: SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 - stigid@ol8: OL08-00-020040 - stigid@rhel8: RHEL-08-020040 -+ stigid@rhel9: RHEL-09-412020 - - ocil_clause: 'the "lock-session" is not bound to a specific key' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/no_tmux_in_shells/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/no_tmux_in_shells/rule.yml -index ec8fee18b8..cdbc700083 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/no_tmux_in_shells/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/no_tmux_in_shells/rule.yml -@@ -27,6 +27,7 @@ references: - srg: SRG-OS-000324-GPOS-00125,SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 - stigid@ol8: OL08-00-020042 - stigid@rhel8: RHEL-08-020042 -+ stigid@rhel9: RHEL-09-412030 - - ocil_clause: 'tmux is listed in /etc/shells' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/package_tmux_installed/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/package_tmux_installed/rule.yml -index 14207a44c6..6a706f60de 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/package_tmux_installed/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/console_screen_locking/package_tmux_installed/rule.yml -@@ -44,6 +44,7 @@ references: - srg: SRG-OS-000030-GPOS-00011,SRG-OS-000028-GPOS-00009 - stigid@ol8: OL08-00-020039 - stigid@rhel8: RHEL-08-020039 -+ stigid@rhel9: RHEL-09-412010 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/configure_opensc_card_drivers/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/configure_opensc_card_drivers/rule.yml -index a1e6ae87e4..2a0f5121be 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/configure_opensc_card_drivers/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/configure_opensc_card_drivers/rule.yml -@@ -49,6 +49,7 @@ references: - pcidss: Req-8.3 - pcidss4: "8.4" - srg: SRG-OS-000104-GPOS-00051,SRG-OS-000106-GPOS-00053,SRG-OS-000107-GPOS-00054,SRG-OS-000109-GPOS-00056,SRG-OS-000108-GPOS-00055,SRG-OS-000108-GPOS-00057,SRG-OS-000108-GPOS-00058 -+ stigid@rhel9: RHEL-09-611160 - - ocil_clause: '"{{{ xccdf_value("var_smartcard_drivers") }}}" is not listed as a card driver, or there is no line returned for "card_drivers"' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml -index a75f509a36..e4e1a79dc7 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml -@@ -56,6 +56,7 @@ references: - stigid@ol8: OL08-00-010390 - stigid@rhel7: RHEL-07-041001 - stigid@rhel8: RHEL-08-010390 -+ stigid@rhel9: RHEL-09-215075 - stigid@sle12: SLES-12-030500 - stigid@sle15: SLES-15-010460 - stigid@ubuntu2004: UBTU-20-010063 -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_opensc_installed/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_opensc_installed/rule.yml -index 56570f5c64..41d6e55b2d 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_opensc_installed/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_opensc_installed/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000375-GPOS-00160,SRG-OS-000376-GPOS-00161 - stigid@ol8: OL08-00-010410 - stigid@rhel8: RHEL-08-010410 -+ stigid@rhel9: RHEL-09-611185 - stigid@ubuntu2004: UBTU-20-010064 - - ocil_clause: 'the package is not installed' -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_pcsc-lite_installed/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_pcsc-lite_installed/rule.yml -index f3b1ef07a4..b7a0b4cd85 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_pcsc-lite_installed/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/package_pcsc-lite_installed/rule.yml -@@ -23,6 +23,7 @@ references: - ism: 1382,1384,1386 - nist: CM-6(a) - srg: SRG-OS-000375-GPOS-00160 -+ stigid@rhel9: RHEL-09-611175 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/service_pcscd_enabled/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/service_pcscd_enabled/rule.yml -index dcad70a82d..2c5ed01fb3 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/service_pcscd_enabled/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/service_pcscd_enabled/rule.yml -@@ -35,6 +35,7 @@ references: - pcidss: Req-8.3 - pcidss4: "8.4" - srg: SRG-OS-000375-GPOS-00160 -+ stigid@rhel9: RHEL-09-611180 - - ocil_clause: 'the pcscd service is not enabled' - -diff --git a/linux_os/guide/system/accounts/accounts-physical/service_debug-shell_disabled/rule.yml b/linux_os/guide/system/accounts/accounts-physical/service_debug-shell_disabled/rule.yml -index aad6ad4b67..0a857bd748 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/service_debug-shell_disabled/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/service_debug-shell_disabled/rule.yml -@@ -39,6 +39,7 @@ references: - srg: SRG-OS-000324-GPOS-00125,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040180 - stigid@rhel8: RHEL-08-040180 -+ stigid@rhel9: RHEL-09-211055 - - ocil_clause: |- - {{{ ocil_clause_service_disabled(service="debug-shell") }}} -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_disable_post_pw_expiration/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_disable_post_pw_expiration/rule.yml -index da2a2d367b..526a15acc1 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_disable_post_pw_expiration/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_disable_post_pw_expiration/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-020260 - stigid@rhel7: RHEL-07-010310 - stigid@rhel8: RHEL-08-020260 -+ stigid@rhel9: RHEL-09-411050 - stigid@sle12: SLES-12-010340 - stigid@sle15: SLES-15-020050 - stigid@ubuntu2004: UBTU-20-010409 -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_temp_expire_date/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_temp_expire_date/rule.yml -index 90045204ca..45fb511983 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_temp_expire_date/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_temp_expire_date/rule.yml -@@ -47,6 +47,7 @@ references: - stigid@ol8: OL08-00-020000 - stigid@rhel7: RHEL-07-010271 - stigid@rhel8: RHEL-08-020000 -+ stigid@rhel9: RHEL-09-411040 - stigid@sle12: SLES-12-010360 - stigid@sle15: SLES-15-020000 - stigid@ubuntu2004: UBTU-20-010000 -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/account_unique_id/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/account_unique_id/rule.yml -index 487bfd63a3..2e376eee74 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/account_unique_id/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/account_unique_id/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000104-GPOS-00051,SRG-OS-000121-GPOS-00062,SRG-OS-000042-GPOS-00020 - stigid@ol8: OL08-00-020240 - stigid@rhel8: RHEL-08-020240 -+ stigid@rhel9: RHEL-09-411030 - stigid@sle12: SLES-12-010640 - stigid@sle15: SLES-15-010230 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/accounts_authorized_local_users/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/accounts_authorized_local_users/rule.yml -index 9bb4ecb9f5..374454f7b7 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/accounts_authorized_local_users/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/accounts_authorized_local_users/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-020320 - stigid@rhel7: RHEL-07-020270 - stigid@rhel8: RHEL-08-020320 -+ stigid@rhel9: RHEL-09-411095 - stigid@sle12: SLES-12-010630 - stigid@sle15: SLES-15-020090 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/group_unique_id/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/group_unique_id/rule.yml -index 1ba8ed1522..6193b3f806 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/group_unique_id/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/group_unique_id/rule.yml -@@ -30,6 +30,7 @@ references: - disa: CCI-000764 - pcidss4: "8.2.1" - srg: SRG-OS-000104-GPOS-00051 -+ stigid@rhel9: RHEL-09-411110 - - ocil_clause: 'the system has duplicate group ids' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml -index c9eacf55c9..f4bb104309 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml -@@ -61,6 +61,7 @@ references: - stigid@ol8: OL08-00-020200 - stigid@rhel7: RHEL-07-010250 - stigid@rhel8: RHEL-08-020200 -+ stigid@rhel9: RHEL-09-411010 - stigid@sle12: SLES-12-010280 - stigid@sle15: SLES-15-020220 - stigid@ubuntu2004: UBTU-20-010008 -@@ -85,4 +86,3 @@ srg_requirement: |- - {{{ full_name }}} user account passwords for new users or password changes must have a 60 day maximum password lifetime restriction in /etc/login.defs. - - platform: package[shadow-utils] -- -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml -index 541ad9eef2..e0c416bd05 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-020190 - stigid@rhel7: RHEL-07-010230 - stigid@rhel8: RHEL-08-020190 -+ stigid@rhel9: RHEL-09-611075 - stigid@sle12: SLES-12-010260 - stigid@sle15: SLES-15-020200 - stigid@ubuntu2004: UBTU-20-010007 -@@ -85,4 +86,3 @@ srg_requirement: |- - {{{ full_name }}} passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in /etc/login.defs. - - platform: package[shadow-utils] -- -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_minlen_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_minlen_login_defs/rule.yml -index d0365266ac..37a247f304 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_minlen_login_defs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_minlen_login_defs/rule.yml -@@ -48,6 +48,7 @@ references: - srg: SRG-OS-000078-GPOS-00046 - stigid@ol8: OL08-00-020231 - stigid@rhel8: RHEL-08-020231 -+ stigid@rhel9: RHEL-09-611095 - - ocil_clause: 'it is not set to the required value' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_max_life_existing/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_max_life_existing/rule.yml -index d56b4e8c06..e21c8282af 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_max_life_existing/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_max_life_existing/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-020210 - stigid@rhel7: RHEL-07-010260 - stigid@rhel8: RHEL-08-020210 -+ stigid@rhel9: RHEL-09-411015 - stigid@sle12: SLES-12-010290 - stigid@sle15: SLES-15-020230 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_min_life_existing/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_min_life_existing/rule.yml -index 5e1fe03a20..6955ddfd13 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_min_life_existing/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_set_min_life_existing/rule.yml -@@ -43,6 +43,7 @@ references: - stigid@ol8: OL08-00-020180 - stigid@rhel7: RHEL-07-010240 - stigid@rhel8: RHEL-08-020180 -+ stigid@rhel9: RHEL-09-611080 - stigid@sle12: SLES-12-010270 - stigid@sle15: SLES-15-020210 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_all_shadowed_sha512/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_all_shadowed_sha512/rule.yml -index 25ec7a9699..da7c934ecb 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_all_shadowed_sha512/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_all_shadowed_sha512/rule.yml -@@ -39,10 +39,10 @@ references: - srg: SRG-OS-000073-GPOS-00041,SRG-OS-000120-GPOS-00061 - stigid@ol8: OL08-00-010120 - stigid@rhel8: RHEL-08-010120 -+ stigid@rhel9: RHEL-09-671015 - stigid@sle12: SLES-12-010220 - stigid@sle15: SLES-15-020180 - -- - ocil_clause: 'any interactive user password hash does not begin with "$6"' - - ocil: |- -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_password_auth/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_password_auth/rule.yml -index f293207553..e0a37b4844 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_password_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_password_auth/rule.yml -@@ -40,6 +40,7 @@ references: - anssi: BP28(R68) - disa: CCI-000196 - srg: SRG-OS-000073-GPOS-00041 -+ stigid@rhel9: RHEL-09-611050 - - ocil_clause: 'rounds is not set to {{{ xccdf_value("var_password_pam_unix_rounds") }}} or is commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_system_auth/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_system_auth/rule.yml -index c2c92fd71a..914911dc75 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_system_auth/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/accounts_password_pam_unix_rounds_system_auth/rule.yml -@@ -34,6 +34,7 @@ references: - anssi: BP28(R68) - disa: CCI-000196 - srg: SRG-OS-000073-GPOS-00041 -+ stigid@rhel9: RHEL-09-611055 - - ocil_clause: 'rounds is not set to {{{ xccdf_value("var_password_pam_unix_rounds") }}} or is commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/gid_passwd_group_same/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/gid_passwd_group_same/rule.yml -index 5bad19fede..428f1eaef6 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/gid_passwd_group_same/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/gid_passwd_group_same/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000104-GPOS-00051 - stigid@ol7: OL07-00-020300 - stigid@rhel7: RHEL-07-020300 -+ stigid@rhel9: RHEL-09-411045 - - ocil_clause: 'GIDs referenced in /etc/passwd are returned as not defined in /etc/group' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords/rule.yml -index d00d784548..90f912b89c 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords/rule.yml -@@ -55,7 +55,8 @@ references: - stigid@ol7: OL07-00-010290 - stigid@ol8: OL08-00-020331 - stigid@rhel7: RHEL-07-010290 -- stigid@rhel8: RHEL-08-020331 -+ stigid@rhel8: RHEL-08-020331,RHEL-08-020332 -+ stigid@rhel9: RHEL-09-611025 - stigid@sle12: SLES-12-010231 - stigid@sle15: SLES-15-020300 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords_etc_shadow/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords_etc_shadow/rule.yml -index fce24fc7f9..8e2777bde0 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords_etc_shadow/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords_etc_shadow/rule.yml -@@ -43,6 +43,7 @@ references: - stigid@ol8: OL08-00-010121 - stigid@rhel7: RHEL-07-010291 - stigid@rhel8: RHEL-08-010121 -+ stigid@rhel9: RHEL-09-611155 - stigid@sle12: SLES-12-010221 - stigid@sle15: SLES-15-020181 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml -index 4d8c72582c..588dfe904d 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml -@@ -58,6 +58,7 @@ references: - stigid@ol8: OL08-00-040200 - stigid@rhel7: RHEL-07-020310 - stigid@rhel8: RHEL-08-040200 -+ stigid@rhel9: RHEL-09-411100 - stigid@sle12: SLES-12-010650 - stigid@sle15: SLES-15-020100 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/rule.yml -index 6a819ccd5f..f0b5cc7544 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/rule.yml -@@ -51,6 +51,7 @@ references: - nist-csf: DE.CM-1,DE.CM-3,PR.AC-1,PR.AC-4,PR.AC-6 - pcidss4: "8.6.1" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-411035 - stigid@sle12: SLES-12-010631 - stigid@sle15: SLES-15-020091 - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/use_pam_wheel_for_su/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/use_pam_wheel_for_su/rule.yml -index 3320b393c9..7f2dbc6487 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/use_pam_wheel_for_su/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/use_pam_wheel_for_su/rule.yml -@@ -34,6 +34,7 @@ references: - ospp: FMT_SMF_EXT.1.1 - pcidss4: "8.6.1" - srg: 'SRG-OS-000373-GPOS-00156,SRG-OS-000312-GPOS-00123' -+ stigid@rhel9: RHEL-09-432035 - - ocil_clause: 'the line is not in the file or it is commented' - -diff --git a/linux_os/guide/system/accounts/accounts-restrictions/var_accounts_authorized_local_users_regex.var b/linux_os/guide/system/accounts/accounts-restrictions/var_accounts_authorized_local_users_regex.var -index 5da5a9709d..01f660034a 100644 ---- a/linux_os/guide/system/accounts/accounts-restrictions/var_accounts_authorized_local_users_regex.var -+++ b/linux_os/guide/system/accounts/accounts-restrictions/var_accounts_authorized_local_users_regex.var -@@ -27,5 +27,6 @@ options: - ol7forsap: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|pegasus|systemd-bus-proxy|systemd-network|dbus|polkitd|abrt|unbound|tss|libstoragemgmt|rpc|colord|usbmuxd$|pcp|saslauth|geoclue|setroubleshoot|rtkit|chrony|qemu|radvd|rpcuser|nfsnobody|pulse|gdm|gnome-initial-setup|postfix|avahi|ntp|sshd|tcpdump|oprofile|uuidd)$" - rhel7: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|pegasus|systemd-bus-proxy|systemd-network|dbus|polkitd|abrt|unbound|tss|libstoragemgmt|rpc|colord|usbmuxd$|pcp|saslauth|geoclue|setroubleshoot|rtkit|chrony|qemu|radvd|rpcuser|nfsnobody|pulse|gdm|gnome-initial-setup|postfix|avahi|ntp|sshd|tcpdump|oprofile|uuidd|systemd-resolve|systemd-coredump|sssd|rngd)$" - rhel8: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|pegasus|systemd-bus-proxy|systemd-network|dbus|polkitd|abrt|unbound|tss|libstoragemgmt|rpc|colord|usbmuxd$|pcp|saslauth|geoclue|setroubleshoot|rtkit|chrony|qemu|radvd|rpcuser|nfsnobody|pulse|gdm|gnome-initial-setup|postfix|avahi|ntp|sshd|tcpdump|oprofile|uuidd|systemd-resolve|systemd-coredump|sssd|rngd)$" -+ rhel9: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|tss|systemd-coredump|dbus|polkitd|avahi|colord|rtkit|pipewire|clevis|sssd|geoclue|flatpak|setroubleshoot|libstoragemgmt|systemd-oom|gdm|cockpit-ws|cockpit-wsinstance|gnome-initial-setup|sshd|chrony|dnsmasq|tcpdump|admin)$" - sle12: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|pegasus|systemd-bus-proxy|systemd-network|dbus|polkitd|abrt|unbound|tss|libstoragemgmt|rpc|colord|usbmuxd$|pcp|saslauth|geoclue|setroubleshoot|rtkit|chrony|qemu|radvd|rpcuser|nfsnobody|pulse|gdm|gnome-initial-setup|postfix|avahi|ntp|sshd|tcpdump|oprofile|uuidd|systemd-resolve|systemd-coredump|sssd|rngd|man|systemd-timesync|scard|hacluster|statd|at|dockremap|vnc)$" - sle15: "^(root|bin|daemon|adm|lp|sync|shutdown|halt|mail|operator|games|ftp|nobody|pegasus|systemd-bus-proxy|systemd-network|dbus|polkitd|abrt|unbound|tss|libstoragemgmt|rpc|colord|usbmuxd$|pcp|saslauth|geoclue|setroubleshoot|rtkit|chrony|qemu|radvd|rpcuser|nfsnobody|pulse|gdm|gnome-initial-setup|postfix|avahi|ntp|sshd|tcpdump|oprofile|uuidd|systemd-resolve|systemd-coredump|sssd|rngd|man|systemd-timesync|scard|hacluster|statd|at|dockremap|vnc|messagebus|nscd)$" -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_have_homedir_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_have_homedir_login_defs/rule.yml -index 9a8332e386..3d6faac7ef 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_have_homedir_login_defs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_have_homedir_login_defs/rule.yml -@@ -32,6 +32,7 @@ references: - stigid@ol8: OL08-00-010760 - stigid@rhel7: RHEL-07-020610 - stigid@rhel8: RHEL-08-010760 -+ stigid@rhel9: RHEL-09-411020 - stigid@sle12: SLES-12-010720 - stigid@sle15: SLES-15-020110 - -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_logon_fail_delay/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_logon_fail_delay/rule.yml -index d224b894f8..ff6e6b0e0e 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_logon_fail_delay/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_logon_fail_delay/rule.yml -@@ -33,6 +33,7 @@ references: - stigid@ol8: OL08-00-020310 - stigid@rhel7: RHEL-07-010430 - stigid@rhel8: RHEL-08-020310 -+ stigid@rhel9: RHEL-09-412050 - stigid@sle12: SLES-12-010140 - - ocil_clause: 'the value of "FAIL_DELAY" is not set to "{{{ xccdf_value("var_accounts_fail_delay") }}}" or greater, or the line is commented out' -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_max_concurrent_login_sessions/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_max_concurrent_login_sessions/rule.yml -index 238a4c35bc..3242bb77ee 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_max_concurrent_login_sessions/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_max_concurrent_login_sessions/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-020024 - stigid@rhel7: RHEL-07-040000 - stigid@rhel8: RHEL-08-020024 -+ stigid@rhel9: RHEL-09-412040 - stigid@sle12: SLES-12-010120 - stigid@sle15: SLES-15-020020 - stigid@ubuntu2004: UBTU-20-010400 -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml -index e91ae04939..b392f7aa07 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml -@@ -70,6 +70,7 @@ references: - srg: SRG-OS-000163-GPOS-00072,SRG-OS-000029-GPOS-00010 - stigid@ol7: OL07-00-040160 - stigid@rhel7: RHEL-07-040160 -+ stigid@rhel9: RHEL-09-412035 - stigid@sle12: SLES-12-010090 - stigid@sle15: SLES-15-010130 - stigid@ubuntu2004: UBTU-20-010013 -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_dot_no_world_writable_programs/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_dot_no_world_writable_programs/rule.yml -index e56be2792c..11dc1815e7 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_dot_no_world_writable_programs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_dot_no_world_writable_programs/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-010660 - stigid@rhel7: RHEL-07-020730 - stigid@rhel8: RHEL-08-010660 -+ stigid@rhel9: RHEL-09-411115 - stigid@sle12: SLES-12-010780 - stigid@sle15: SLES-15-040130 - -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_home_paths_only/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_home_paths_only/rule.yml -index 56fc415f92..7a78dfc2b9 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_home_paths_only/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_home_paths_only/rule.yml -@@ -36,6 +36,7 @@ references: - stigid@ol8: OL08-00-010690 - stigid@rhel7: RHEL-07-020720 - stigid@rhel8: RHEL-08-010690 -+ stigid@rhel9: RHEL-09-411055 - stigid@sle12: SLES-12-010770 - stigid@sle15: SLES-15-040120 - -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_defined/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_defined/rule.yml -index b90ef5d7d2..1402fb0a04 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_defined/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_defined/rule.yml -@@ -32,6 +32,7 @@ references: - stigid@ol8: OL08-00-010720 - stigid@rhel7: RHEL-07-020600 - stigid@rhel8: RHEL-08-010720 -+ stigid@rhel9: RHEL-09-411060 - stigid@sle12: SLES-12-010710 - stigid@sle15: SLES-15-040070 - -diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml -index 6811bb1c26..575fdd0f9f 100644 ---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-010750 - stigid@rhel7: RHEL-07-020620 - stigid@rhel8: RHEL-08-010750 -+ stigid@rhel9: RHEL-09-411065 - stigid@sle12: SLES-12-010730 - stigid@sle15: SLES-15-040080 - -diff --git a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml -index 94c513327c..ee58cd30a0 100644 ---- a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-010740 - stigid@rhel7: RHEL-07-020650 - stigid@rhel8: RHEL-08-010740 -+ stigid@rhel9: RHEL-09-411070 - stigid@sle12: SLES-12-010750 - stigid@sle15: SLES-15-040100 - -diff --git a/linux_os/guide/system/accounts/accounts-session/file_permission_user_init_files/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_permission_user_init_files/rule.yml -index 5bfdd4a141..eed6623b4f 100644 ---- a/linux_os/guide/system/accounts/accounts-session/file_permission_user_init_files/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/file_permission_user_init_files/rule.yml -@@ -30,6 +30,7 @@ references: - stigid@ol8: OL08-00-010770 - stigid@rhel7: RHEL-07-020710 - stigid@rhel8: RHEL-08-010770 -+ stigid@rhel9: RHEL-09-232045 - stigid@sle12: SLES-12-010760 - stigid@sle15: SLES-15-040110 - -diff --git a/linux_os/guide/system/accounts/accounts-session/file_permissions_home_directories/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_permissions_home_directories/rule.yml -index bda4bfd363..72bef78d2d 100644 ---- a/linux_os/guide/system/accounts/accounts-session/file_permissions_home_directories/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/file_permissions_home_directories/rule.yml -@@ -39,6 +39,7 @@ references: - stigid@ol8: OL08-00-010730 - stigid@rhel7: RHEL-07-020630 - stigid@rhel8: RHEL-08-010730 -+ stigid@rhel9: RHEL-09-232050 - stigid@sle12: SLES-12-010740 - stigid@sle15: SLES-15-040090 - -diff --git a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_bashrc/rule.yml b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_bashrc/rule.yml -index 8293b72ade..200502c4bb 100644 ---- a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_bashrc/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_bashrc/rule.yml -@@ -55,6 +55,7 @@ references: - srg: SRG-OS-000480-GPOS-00228,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-020353 - stigid@rhel8: RHEL-08-020353 -+ stigid@rhel9: RHEL-09-412055 - - ocil_clause: 'the value for the "umask" parameter is not "{{{ xccdf_value("var_accounts_user_umask") }}}", or the "umask" parameter is missing or is commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_csh_cshrc/rule.yml b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_csh_cshrc/rule.yml -index 21238691a4..7eeee3879d 100644 ---- a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_csh_cshrc/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_csh_cshrc/rule.yml -@@ -35,6 +35,7 @@ references: - srg: SRG-OS-000480-GPOS-00228,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-020353 - stigid@rhel8: RHEL-08-020353 -+ stigid@rhel9: RHEL-09-412060 - - ocil_clause: 'the value for the "umask" parameter is not "{{{ xccdf_value("var_accounts_user_umask") }}}", or the "umask" parameter is missing or is commented out' - -diff --git a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_login_defs/rule.yml -index 91b4ff56cc..53c32eda05 100644 ---- a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_login_defs/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_login_defs/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-020351 - stigid@rhel7: RHEL-07-020240 - stigid@rhel8: RHEL-08-020351 -+ stigid@rhel9: RHEL-09-412065 - stigid@sle12: SLES-12-010620 - stigid@sle15: SLES-15-040420 - stigid@ubuntu2004: UBTU-20-010016 -diff --git a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_profile/rule.yml b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_profile/rule.yml -index 410c6af61e..1fb0b0a565 100644 ---- a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_profile/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_etc_profile/rule.yml -@@ -50,6 +50,7 @@ references: - srg: SRG-OS-000480-GPOS-00228,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-020353 - stigid@rhel8: RHEL-08-020353 -+ stigid@rhel9: RHEL-09-412070 - - ocil_clause: |- - the value for the "umask" parameter is not "{{{ xccdf_value("var_accounts_user_umask") }}}", -diff --git a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_interactive_users/rule.yml b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_interactive_users/rule.yml -index ded8284bef..313ac772a5 100644 ---- a/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_interactive_users/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-session/user_umask/accounts_umask_interactive_users/rule.yml -@@ -30,6 +30,7 @@ references: - stigid@ol8: OL08-00-020352 - stigid@rhel7: RHEL-07-021040 - stigid@rhel8: RHEL-08-020352 -+ stigid@rhel9: RHEL-09-411025 - - ocil_clause: 'any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077"' - -diff --git a/linux_os/guide/system/accounts/authconfig_config_files_symlinks/rule.yml b/linux_os/guide/system/accounts/authconfig_config_files_symlinks/rule.yml -index 179a7b8bda..6daa94e1d8 100644 ---- a/linux_os/guide/system/accounts/authconfig_config_files_symlinks/rule.yml -+++ b/linux_os/guide/system/accounts/authconfig_config_files_symlinks/rule.yml -@@ -72,4 +72,3 @@ fixtext: |- - /etc/pam.d/system-auth - /etc/pam.d/system-auth-ac - /etc/pam.d/system-auth-local -- -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chmod/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chmod/rule.yml -index f1d8dbc14a..6ba6b10931 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chmod/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chmod/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030490 - stigid@rhel7: RHEL-07-030410 - stigid@rhel8: RHEL-08-030490 -+ stigid@rhel9: RHEL-09-654015 - stigid@sle12: SLES-12-020460 - stigid@sle15: SLES-15-030290 - stigid@ubuntu2004: UBTU-20-010152 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chown/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chown/rule.yml -index 2896ec8452..3f077927c8 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chown/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_chown/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030480 - stigid@rhel7: RHEL-07-030370 - stigid@rhel8: RHEL-08-030480 -+ stigid@rhel9: RHEL-09-654020 - stigid@sle12: SLES-12-020420 - stigid@sle15: SLES-15-030250 - stigid@ubuntu2004: UBTU-20-010148 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmod/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmod/rule.yml -index 45a66b8c4c..405c88d260 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmod/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmod/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030490 - stigid@rhel7: RHEL-07-030410 - stigid@rhel8: RHEL-08-030490 -+ stigid@rhel9: RHEL-09-654015 - stigid@sle12: SLES-12-020460 - stigid@sle15: SLES-15-030290 - stigid@ubuntu2004: UBTU-20-010153 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmodat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmodat/rule.yml -index d68b7b4af2..5d658acb99 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmodat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchmodat/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030490 - stigid@rhel7: RHEL-07-030410 - stigid@rhel8: RHEL-08-030490 -+ stigid@rhel9: RHEL-09-654015 - stigid@sle12: SLES-12-020460 - stigid@sle15: SLES-15-030290 - stigid@ubuntu2004: UBTU-20-010154 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchown/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchown/rule.yml -index 146f89e8b6..4a41f68624 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchown/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchown/rule.yml -@@ -68,6 +68,7 @@ references: - stigid@ol8: OL08-00-030480 - stigid@rhel7: RHEL-07-030370 - stigid@rhel8: RHEL-08-030480 -+ stigid@rhel9: RHEL-09-654020 - stigid@sle12: SLES-12-020420 - stigid@sle15: SLES-15-030250 - stigid@ubuntu2004: UBTU-20-010149 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchownat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchownat/rule.yml -index 464500cd64..35419d3dbc 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchownat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fchownat/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030480 - stigid@rhel7: RHEL-07-030370 - stigid@rhel8: RHEL-08-030480 -+ stigid@rhel9: RHEL-09-654020 - stigid@sle12: SLES-12-020420 - stigid@sle15: SLES-15-030250 - stigid@ubuntu2004: UBTU-20-010150 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fremovexattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fremovexattr/rule.yml -index 1dc43e75f7..c20140fce9 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fremovexattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fremovexattr/rule.yml -@@ -82,6 +82,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010147 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fsetxattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fsetxattr/rule.yml -index 261433ef9f..0013304a84 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fsetxattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_fsetxattr/rule.yml -@@ -77,6 +77,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010144 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lchown/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lchown/rule.yml -index 1ce741da41..e2c3ff9ed8 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lchown/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lchown/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030480 - stigid@rhel7: RHEL-07-030370 - stigid@rhel8: RHEL-08-030480 -+ stigid@rhel9: RHEL-09-654020 - stigid@sle12: SLES-12-020420 - stigid@sle15: SLES-15-030250 - stigid@ubuntu2004: UBTU-20-010151 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lremovexattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lremovexattr/rule.yml -index abe8228aa0..85d2f6d051 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lremovexattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lremovexattr/rule.yml -@@ -82,6 +82,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010146 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lsetxattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lsetxattr/rule.yml -index f855dd32be..b36944ba43 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lsetxattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_lsetxattr/rule.yml -@@ -77,6 +77,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010143 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_removexattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_removexattr/rule.yml -index 63d3490a49..27e223fae8 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_removexattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_removexattr/rule.yml -@@ -81,6 +81,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010145 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_setxattr/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_setxattr/rule.yml -index ab4c0226e4..21610d36ba 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_setxattr/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_setxattr/rule.yml -@@ -77,6 +77,7 @@ references: - stigid@ol8: OL08-00-030200 - stigid@rhel7: RHEL-07-030440 - stigid@rhel8: RHEL-08-030200 -+ stigid@rhel9: RHEL-09-654025 - stigid@sle12: SLES-12-020370 - stigid@sle15: SLES-15-030190 - stigid@ubuntu2004: UBTU-20-010142 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount/rule.yml -index ee4a90773e..c78f88ad28 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount/rule.yml -@@ -30,7 +30,8 @@ identifiers: - references: - disa: CCI-000130,CCI-000169,CCI-000172,CCI-002884 - nist@sle12: AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) -- srg: SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 -+ srg: SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-APP-000495-CTR-001235 -+ stigid@rhel9: RHEL-09-654205 - stigid@sle12: SLES-12-020300 - stigid@sle15: SLES-15-030360 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount2/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount2/rule.yml -index d2d196ab8e..6376db4974 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount2/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_dac_actions/audit_rules_dac_modification_umount2/rule.yml -@@ -37,7 +37,8 @@ references: - anssi: BP28(R73) - disa: CCI-000130,CCI-000169,CCI-000172,CCI-002884 - nist@sle12: AU-3,AU-3.1,AU-12.1(ii),AU-12(a),AU-12.1(iv),AU-12(c),MA-4(1)(a) -- srg: SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 -+ srg: SRG-OS-000037-GPOS-00015,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-APP-000495-CTR-001235 -+ stigid@rhel9: RHEL-09-654210 - stigid@sle12: SLES-12-020300 - stigid@sle15: SLES-15-030360 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_chacl/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_chacl/rule.yml -index 2a15e8610e..f8e9a34d6f 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_chacl/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_chacl/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210 - stigid@ol8: OL08-00-030570 - stigid@rhel8: RHEL-08-030570 -+ stigid@rhel9: RHEL-09-654035 - stigid@sle12: SLES-12-020620 - stigid@sle15: SLES-15-030440 - stigid@ubuntu2004: UBTU-20-010168 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_setfacl/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_setfacl/rule.yml -index 8c1cec42e8..1a6802fc24 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_setfacl/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_acl_commands/audit_rules_execution_setfacl/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 - stigid@ol8: OL08-00-030330 - stigid@rhel8: RHEL-08-030330 -+ stigid@rhel9: RHEL-09-654040 - stigid@sle12: SLES-12-020610 - stigid@sle15: SLES-15-030430 - stigid@ubuntu2004: UBTU-20-010167 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_chcon/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_chcon/rule.yml -index 4f4194fe86..b2c8ab8f8d 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_chcon/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_chcon/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030260 - stigid@rhel7: RHEL-07-030580 - stigid@rhel8: RHEL-08-030260 -+ stigid@rhel9: RHEL-09-654045 - stigid@sle12: SLES-12-020630 - stigid@sle15: SLES-15-030450 - stigid@ubuntu2004: UBTU-20-010165 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_semanage/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_semanage/rule.yml -index 43a9ae1840..14a08e26b2 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_semanage/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_semanage/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-030313 - stigid@rhel7: RHEL-07-030560 - stigid@rhel8: RHEL-08-030313 -+ stigid@rhel9: RHEL-09-654050 - - {{{ ocil_fix_srg_privileged_command("semanage", "/usr/sbin/", "privileged-unix-update") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setfiles/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setfiles/rule.yml -index 3593267108..432403663a 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setfiles/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setfiles/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-030314 - stigid@rhel7: RHEL-07-030590 - stigid@rhel8: RHEL-08-030314 -+ stigid@rhel9: RHEL-09-654055 - - {{{ ocil_fix_srg_privileged_command("setfiles", "/usr/sbin/", "privileged-unix-update") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setsebool/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setsebool/rule.yml -index 810d628387..b1444ef8ff 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setsebool/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_execution_selinux_commands/audit_rules_execution_setsebool/rule.yml -@@ -58,6 +58,7 @@ references: - stigid@ol8: OL08-00-030316 - stigid@rhel7: RHEL-07-030570 - stigid@rhel8: RHEL-08-030316 -+ stigid@rhel9: RHEL-09-654060 - - {{{ ocil_fix_srg_privileged_command("setsebool", "/usr/sbin/", "privileged") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rename/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rename/rule.yml -index 5b6bb0424a..7609125f2d 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rename/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rename/rule.yml -@@ -60,7 +60,8 @@ references: - stigid@ol8: OL08-00-030361 - stigid@rhel7: RHEL-07-030910 - stigid@rhel8: RHEL-08-030361 -- stigid@ubuntu2004: UBTU-20-010269 -+ stigid@rhel9: RHEL-09-654065 -+ stigid@ubuntu2004: UBTU-20-010267 - - {{{ complete_ocil_entry_audit_syscall(syscall="rename") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_renameat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_renameat/rule.yml -index fd2e5b77fd..4880157a10 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_renameat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_renameat/rule.yml -@@ -59,7 +59,8 @@ references: - stigid@ol8: OL08-00-030361 - stigid@rhel7: RHEL-07-030910 - stigid@rhel8: RHEL-08-030361 -- stigid@ubuntu2004: UBTU-20-010270 -+ stigid@rhel9: RHEL-09-654065 -+ stigid@ubuntu2004: UBTU-20-010267 - - {{{ complete_ocil_entry_audit_syscall(syscall="renameat") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rmdir/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rmdir/rule.yml -index 7c42d57ec2..7f0283f315 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rmdir/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_rmdir/rule.yml -@@ -53,6 +53,8 @@ references: - stigid@ol8: OL08-00-030361 - stigid@rhel7: RHEL-07-030910 - stigid@rhel8: RHEL-08-030361 -+ stigid@rhel9: RHEL-09-654065 -+ stigid@ubuntu2004: UBTU-20-010267 - - {{{ complete_ocil_entry_audit_syscall(syscall="rmdir") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlink/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlink/rule.yml -index 432d5dee7b..89efb59a95 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlink/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlink/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-030361 - stigid@rhel7: RHEL-07-030910 - stigid@rhel8: RHEL-08-030361 -+ stigid@rhel9: RHEL-09-654065 - stigid@ubuntu2004: UBTU-20-010267 - - {{{ complete_ocil_entry_audit_syscall(syscall="unlink") }}} -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlinkat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlinkat/rule.yml -index 2d9dfec6f8..e8abd8958b 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlinkat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_deletion_events/audit_rules_file_deletion_events_unlinkat/rule.yml -@@ -59,7 +59,8 @@ references: - stigid@ol8: OL08-00-030361 - stigid@rhel7: RHEL-07-030910 - stigid@rhel8: RHEL-08-030361 -- stigid@ubuntu2004: UBTU-20-010268 -+ stigid@rhel9: RHEL-09-654065 -+ stigid@ubuntu2004: UBTU-20-010267 - - {{{ complete_ocil_entry_audit_syscall(syscall="unlinkat") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_creat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_creat/rule.yml -index a3e663e12a..2f1ad3f06e 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_creat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_creat/rule.yml -@@ -70,6 +70,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010158 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_ftruncate/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_ftruncate/rule.yml -index d088d91bc9..449faf04e3 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_ftruncate/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_ftruncate/rule.yml -@@ -73,6 +73,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010157 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open/rule.yml -index de8897a2cc..406589c5f3 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open/rule.yml -@@ -73,6 +73,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010155 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open_by_handle_at/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open_by_handle_at/rule.yml -index 7b303e092c..281886ca9e 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open_by_handle_at/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_open_by_handle_at/rule.yml -@@ -63,6 +63,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010160 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_openat/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_openat/rule.yml -index c85d6d55c2..99183a570f 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_openat/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_openat/rule.yml -@@ -73,6 +73,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010159 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_truncate/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_truncate/rule.yml -index b7e17951e6..02d9424fb0 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_truncate/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_file_modification/audit_rules_unsuccessful_file_modification_truncate/rule.yml -@@ -72,6 +72,7 @@ references: - stigid@ol8: OL08-00-030420 - stigid@rhel7: RHEL-07-030510 - stigid@rhel8: RHEL-08-030420 -+ stigid@rhel9: RHEL-09-654070 - stigid@sle12: SLES-12-020490 - stigid@sle15: SLES-15-030150 - stigid@ubuntu2004: UBTU-20-010156 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_delete/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_delete/rule.yml -index d7973aed92..b2fd7022a4 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_delete/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_delete/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-030390 - stigid@rhel7: RHEL-07-030830 - stigid@rhel8: RHEL-08-030390 -+ stigid@rhel9: RHEL-09-654075 - stigid@sle12: SLES-12-020730 - stigid@sle15: SLES-15-030520 - stigid@ubuntu2004: UBTU-20-010302 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_finit/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_finit/rule.yml -index 57bf26f067..e5fd9bcdf2 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_finit/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_finit/rule.yml -@@ -63,6 +63,7 @@ references: - stigid@ol8: OL08-00-030360 - stigid@rhel7: RHEL-07-030820 - stigid@rhel8: RHEL-08-030360 -+ stigid@rhel9: RHEL-09-654080 - stigid@sle12: SLES-12-020740 - stigid@sle15: SLES-15-030530 - stigid@ubuntu2004: UBTU-20-010180 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_init/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_init/rule.yml -index 4392f855f4..b52273362b 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_init/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_init/rule.yml -@@ -64,6 +64,7 @@ references: - stigid@ol8: OL08-00-030360 - stigid@rhel7: RHEL-07-030820 - stigid@rhel8: RHEL-08-030360 -+ stigid@rhel9: RHEL-09-654080 - stigid@sle12: SLES-12-020740 - stigid@sle15: SLES-15-030530 - stigid@ubuntu2004: UBTU-20-010179 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_faillock/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_faillock/rule.yml -index 4dcd32e2c0..a8d92255a8 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_faillock/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_faillock/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-030590 - stigid@rhel7: RHEL-07-030610 - stigid@rhel8: RHEL-08-030590 -+ stigid@rhel9: RHEL-09-654250 - - ocil_clause: 'the command does not return a line, or the line is commented out' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_lastlog/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_lastlog/rule.yml -index 45c08e4c43..e323b64c21 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_lastlog/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_lastlog/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030600 - stigid@rhel7: RHEL-07-030620 - stigid@rhel8: RHEL-08-030600 -+ stigid@rhel9: RHEL-09-654255 - stigid@sle12: SLES-12-020660 - stigid@sle15: SLES-15-030480 - stigid@ubuntu2004: UBTU-20-010171 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_tallylog/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_tallylog/rule.yml -index 96f6e645fd..8ebbe44c05 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_tallylog/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_login_events/audit_rules_login_events_tallylog/rule.yml -@@ -52,6 +52,7 @@ references: - pcidss4: "10.2.1.3" - srg: SRG-OS-000392-GPOS-00172,SRG-OS-000470-GPOS-00214,SRG-OS-000473-GPOS-00218 - stigid@rhel7: RHEL-07-030600 -+ stigid@rhel9: RHEL-09-654260 - stigid@sle12: SLES-12-020650 - stigid@sle15: SLES-15-030470 - stigid@ubuntu2004: UBTU-20-010169 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_init/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_init/rule.yml -index c66ed5fcd6..0630c7201a 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_init/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_init/rule.yml -@@ -32,6 +32,7 @@ references: - disa: CCI-000172 - nist: AU-12(c) - srg: SRG-OS-000477-GPOS-00222 -+ stigid@rhel9: RHEL-09-654185 - - {{{ ocil_fix_srg_privileged_command("init","{{{ path }}}/") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_poweroff/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_poweroff/rule.yml -index 3a4f1fead9..edb63d1f46 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_poweroff/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_poweroff/rule.yml -@@ -32,6 +32,7 @@ references: - disa: CCI-000172 - nist: AU-12(c) - srg: SRG-OS-000477-GPOS-00222 -+ stigid@rhel9: RHEL-09-654190 - - {{{ ocil_fix_srg_privileged_command("poweroff","{{{ path }}}/") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_reboot/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_reboot/rule.yml -index deb4f602c8..19419ece48 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_reboot/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_reboot/rule.yml -@@ -32,6 +32,7 @@ references: - disa: CCI-000172 - nist: AU-12(c) - srg: SRG-OS-000477-GPOS-00222 -+ stigid@rhel9: RHEL-09-654195 - - {{{ ocil_fix_srg_privileged_command("reboot","{{{ path }}}/") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_shutdown/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_shutdown/rule.yml -index a144848165..7f62af5ecb 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_shutdown/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_privileged_commands_shutdown/rule.yml -@@ -32,6 +32,7 @@ references: - disa: CCI-000172 - nist: AU-12(c) - srg: SRG-OS-000477-GPOS-00222 -+ stigid@rhel9: RHEL-09-654200 - - {{{ ocil_fix_srg_privileged_command("shutdown","{{{ path }}}/") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chage/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chage/rule.yml -index bc240650ee..40531f2032 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chage/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chage/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030250 - stigid@rhel7: RHEL-07-030660 - stigid@rhel8: RHEL-08-030250 -+ stigid@rhel9: RHEL-09-654085 - stigid@sle12: SLES-12-020690 - stigid@sle15: SLES-15-030120 - stigid@ubuntu2004: UBTU-20-010175 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chsh/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chsh/rule.yml -index 8603087c31..a48a300989 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chsh/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_chsh/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030410 - stigid@rhel7: RHEL-07-030720 - stigid@rhel8: RHEL-08-030410 -+ stigid@rhel9: RHEL-09-654090 - stigid@sle12: SLES-12-020580 - stigid@sle15: SLES-15-030100 - stigid@ubuntu2004: UBTU-20-010163 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_crontab/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_crontab/rule.yml -index 0846706f2d..6c81b180d9 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_crontab/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_crontab/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-030400 - stigid@rhel7: RHEL-07-030800 - stigid@rhel8: RHEL-08-030400 -+ stigid@rhel9: RHEL-09-654095 - stigid@sle12: SLES-12-020710 - stigid@sle15: SLES-15-030130 - stigid@ubuntu2004: UBTU-20-010177 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_gpasswd/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_gpasswd/rule.yml -index 347eaee25d..c1865a24b7 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_gpasswd/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_gpasswd/rule.yml -@@ -63,6 +63,7 @@ references: - stigid@ol8: OL08-00-030370 - stigid@rhel7: RHEL-07-030650 - stigid@rhel8: RHEL-08-030370 -+ stigid@rhel9: RHEL-09-654100 - stigid@sle12: SLES-12-020560 - stigid@sle15: SLES-15-030080 - stigid@ubuntu2004: UBTU-20-010174 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_kmod/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_kmod/rule.yml -index 1f40fde770..efc6edf3ee 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_kmod/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_kmod/rule.yml -@@ -54,6 +54,7 @@ references: - stigid@ol8: OL08-00-030580 - stigid@rhel7: RHEL-07-030840 - stigid@rhel8: RHEL-08-030580 -+ stigid@rhel9: RHEL-09-654105 - stigid@sle12: SLES-12-020360 - stigid@sle15: SLES-15-030410 - stigid@ubuntu2004: UBTU-20-010297 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_mount/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_mount/rule.yml -index 602518ad82..c8b3db1173 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_mount/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_mount/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-030300 - stigid@rhel7: RHEL-07-030740 - stigid@rhel8: RHEL-08-030300 -+ stigid@rhel9: RHEL-09-654180 - stigid@sle12: SLES-12-020290 - stigid@ubuntu2004: UBTU-20-010138 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_newgrp/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_newgrp/rule.yml -index 59b4dcfbba..0057a2ea6a 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_newgrp/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_newgrp/rule.yml -@@ -63,6 +63,7 @@ references: - stigid@ol8: OL08-00-030350 - stigid@rhel7: RHEL-07-030710 - stigid@rhel8: RHEL-08-030350 -+ stigid@rhel9: RHEL-09-654110 - stigid@sle12: SLES-12-020570 - stigid@sle15: SLES-15-030090 - stigid@ubuntu2004: UBTU-20-010164 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_pam_timestamp_check/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_pam_timestamp_check/rule.yml -index 0bda87b7d5..f5209ef8d6 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_pam_timestamp_check/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_pam_timestamp_check/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030340 - stigid@rhel7: RHEL-07-030810 - stigid@rhel8: RHEL-08-030340 -+ stigid@rhel9: RHEL-09-654115 - stigid@sle12: SLES-12-020720 - stigid@sle15: SLES-15-030510 - stigid@ubuntu2004: UBTU-20-010178 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_passwd/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_passwd/rule.yml -index 19b6623a7a..36e693f8c3 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_passwd/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_passwd/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-030290 - stigid@rhel7: RHEL-07-030630 - stigid@rhel8: RHEL-08-030290 -+ stigid@rhel9: RHEL-09-654120 - stigid@sle12: SLES-12-020550 - stigid@sle15: SLES-15-030070 - stigid@ubuntu2004: UBTU-20-010172 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postdrop/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postdrop/rule.yml -index 8408a93d07..efba85f00b 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postdrop/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postdrop/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-030311 - stigid@rhel7: RHEL-07-030760 - stigid@rhel8: RHEL-08-030311 -+ stigid@rhel9: RHEL-09-654125 - - {{{ ocil_fix_srg_privileged_command("postdrop") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postqueue/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postqueue/rule.yml -index bbeabeb8d1..f8809fd836 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postqueue/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_postqueue/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-030312 - stigid@rhel7: RHEL-07-030770 - stigid@rhel8: RHEL-08-030312 -+ stigid@rhel9: RHEL-09-654130 - - {{{ ocil_fix_srg_privileged_command("postqueue") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_agent/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_agent/rule.yml -index e1d848144b..e8ad41133d 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_agent/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_agent/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 - stigid@ol8: OL08-00-030280 - stigid@rhel8: RHEL-08-030280 -+ stigid@rhel9: RHEL-09-654135 - stigid@sle12: SLES-12-020310 - stigid@sle15: SLES-15-030370 - stigid@ubuntu2004: UBTU-20-010140 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_keysign/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_keysign/rule.yml -index fd3983b539..f8e2f71a49 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_keysign/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_ssh_keysign/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030320 - stigid@rhel7: RHEL-07-030780 - stigid@rhel8: RHEL-08-030320 -+ stigid@rhel9: RHEL-09-654140 - stigid@sle12: SLES-12-020320 - stigid@sle15: SLES-15-030060 - stigid@ubuntu2004: UBTU-20-010141 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_su/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_su/rule.yml -index 7a02e62206..53c04e298b 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_su/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_su/rule.yml -@@ -61,6 +61,7 @@ references: - stigid@ol8: OL08-00-030190 - stigid@rhel7: RHEL-07-030680 - stigid@rhel8: RHEL-08-030190 -+ stigid@rhel9: RHEL-09-654145 - stigid@sle12: SLES-12-020250 - stigid@sle15: SLES-15-030550 - stigid@ubuntu2004: UBTU-20-010136 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudo/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudo/rule.yml -index 55e5e24bda..e552728561 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudo/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudo/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030550 - stigid@rhel7: RHEL-07-030690 - stigid@rhel8: RHEL-08-030550 -+ stigid@rhel9: RHEL-09-654150 - stigid@sle12: SLES-12-020260 - stigid@sle15: SLES-15-030560 - stigid@ubuntu2004: UBTU-20-010161 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudoedit/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudoedit/rule.yml -index ed40c3d03d..2dfd45f5f9 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudoedit/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_sudoedit/rule.yml -@@ -56,7 +56,8 @@ references: - nist-csf: DE.CM-1,DE.CM-3,DE.CM-7,ID.SC-4,PR.PT-1 - nist@sle15: AU-3,AU-3.1,AU-12(a),AU-12.1(ii),AU-12.1(iv) - ospp: FAU_GEN.1.1.c -- srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 -+ srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-APP-000495-CTR-001235 -+ stigid@rhel9: RHEL-09-654155 - stigid@sle15: SLES-15-030330 - stigid@ubuntu2004: UBTU-20-010162 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_umount/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_umount/rule.yml -index 4ba40efd09..379e854a71 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_umount/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_umount/rule.yml -@@ -60,6 +60,7 @@ references: - stigid@ol8: OL08-00-030301 - stigid@rhel7: RHEL-07-030750 - stigid@rhel8: RHEL-08-030301 -+ stigid@rhel9: RHEL-09-654030 - stigid@sle12: SLES-12-020300 - stigid@ubuntu2004: UBTU-20-010139 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_chkpwd/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_chkpwd/rule.yml -index 53d21d2c89..8cdc38b7d3 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_chkpwd/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_chkpwd/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030317 - stigid@rhel7: RHEL-07-030640 - stigid@rhel8: RHEL-08-030317 -+ stigid@rhel9: RHEL-09-654160 - stigid@sle12: SLES-12-020680 - stigid@sle15: SLES-15-030110 - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_update/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_update/rule.yml -index 6ad48696d8..77dfe37300 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_update/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_unix_update/rule.yml -@@ -39,6 +39,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000064-GPOS-00033,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 - stigid@ol8: OL08-00-030310 - stigid@rhel8: RHEL-08-030310 -+ stigid@rhel9: RHEL-09-654165 - stigid@ubuntu2004: UBTU-20-010173 - - {{{ ocil_fix_srg_privileged_command("unix_update") }}} -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_userhelper/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_userhelper/rule.yml -index b1994fa98b..9befc0b051 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_userhelper/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_userhelper/rule.yml -@@ -58,6 +58,7 @@ references: - stigid@ol8: OL08-00-030315 - stigid@rhel7: RHEL-07-030670 - stigid@rhel8: RHEL-08-030315 -+ stigid@rhel9: RHEL-09-654170 - - {{{ ocil_fix_srg_privileged_command("userhelper") }}} - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_usermod/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_usermod/rule.yml -index 8af4359877..d7379274b8 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_usermod/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_privileged_commands/audit_rules_privileged_commands_usermod/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000466-GPOS-00210 - stigid@ol8: OL08-00-030560 - stigid@rhel8: RHEL-08-030560 -+ stigid@rhel9: RHEL-09-654175 - stigid@sle12: SLES-12-020700 - stigid@sle15: SLES-15-030500 - stigid@ubuntu2004: UBTU-20-010176 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/rule.yml -index 81e0bc11e3..35eb000f24 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/rule.yml -@@ -59,6 +59,7 @@ references: - srg: SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029 - stigid@ol8: OL08-00-030121 - stigid@rhel8: RHEL-08-030121 -+ stigid@rhel9: RHEL-09-654275 - - ocil_clause: 'the audit system is not set to be immutable by adding the "-e 2" option to the end of "/etc/audit/audit.rules"' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers/rule.yml -index 628dc4fd83..71f7914762 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221 - stigid@ol8: OL08-00-030171 - stigid@rhel8: RHEL-08-030171 -+ stigid@rhel9: RHEL-09-654215 - - ocil_clause: 'the command does not return a line, or the line is commented out' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers_d/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers_d/rule.yml -index a8b33956b7..c85eef910a 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers_d/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_sudoers_d/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000004-GPOS-00004,SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000304-GPOS-00121,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000470-GPOS-00214,SRG-OS-000471-GPOS-00215,SRG-OS-000239-GPOS-00089,SRG-OS-000240-GPOS-00090,SRG-OS-000241-GPOS-00091,SRG-OS-000303-GPOS-00120,SRG-OS-000466-GPOS-00210,SRG-OS-000476-GPOS-00221 - stigid@ol8: OL08-00-030172 - stigid@rhel8: RHEL-08-030172 -+ stigid@rhel9: RHEL-09-654220 - - ocil_clause: 'the command does not return a line, or the line is commented out' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_suid_privilege_function/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_suid_privilege_function/rule.yml -index 49a665ded0..4802646e88 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_suid_privilege_function/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_suid_privilege_function/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-030000 - stigid@rhel7: RHEL-07-030360 - stigid@rhel8: RHEL-08-030000 -+ stigid@rhel9: RHEL-09-654010 - stigid@sle12: SLES-12-020240 - stigid@sle15: SLES-15-030640 - stigid@ubuntu2004: UBTU-20-010211 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/rule.yml -index 339a4846fb..724b11dc9d 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/rule.yml -@@ -47,6 +47,7 @@ references: - srg: SRG-OS-000046-GPOS-00022,SRG-OS-000047-GPOS-00023 - stigid@ol7: OL07-00-030010 - stigid@rhel7: RHEL-07-030010 -+ stigid@rhel9: RHEL-09-654265 - - ocil_clause: 'the system is not configured to shutdown on auditd failures' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_group/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_group/rule.yml -index b213979b4e..b8a3aea141 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_group/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_group/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030170 - stigid@rhel7: RHEL-07-030871 - stigid@rhel8: RHEL-08-030170 -+ stigid@rhel9: RHEL-09-654225 - stigid@sle12: SLES-12-020210 - stigid@sle15: SLES-15-030010 - stigid@ubuntu2004: UBTU-20-010101 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_gshadow/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_gshadow/rule.yml -index 0bb5e2238d..e857ced4de 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_gshadow/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_gshadow/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030160 - stigid@rhel7: RHEL-07-030872 - stigid@rhel8: RHEL-08-030160 -+ stigid@rhel9: RHEL-09-654230 - stigid@sle12: SLES-12-020590 - stigid@sle15: SLES-15-030040 - stigid@ubuntu2004: UBTU-20-010103 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_opasswd/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_opasswd/rule.yml -index 946cd6104f..1891114f38 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_opasswd/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_opasswd/rule.yml -@@ -68,6 +68,7 @@ references: - stigid@ol8: OL08-00-030140 - stigid@rhel7: RHEL-07-030874 - stigid@rhel8: RHEL-08-030140 -+ stigid@rhel9: RHEL-09-654235 - stigid@sle12: SLES-12-020230 - stigid@sle15: SLES-15-030030 - stigid@ubuntu2004: UBTU-20-010104 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_passwd/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_passwd/rule.yml -index 46cf595dd7..7372fe52a0 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_passwd/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_passwd/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030150 - stigid@rhel7: RHEL-07-030870 - stigid@rhel8: RHEL-08-030150 -+ stigid@rhel9: RHEL-09-654240 - stigid@sle12: SLES-12-020200 - stigid@sle15: SLES-15-030000 - stigid@ubuntu2004: UBTU-20-010100 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_shadow/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_shadow/rule.yml -index a4e780a392..5fc5fda83d 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_shadow/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_usergroup_modification_shadow/rule.yml -@@ -67,6 +67,7 @@ references: - stigid@ol8: OL08-00-030130 - stigid@rhel7: RHEL-07-030873 - stigid@rhel8: RHEL-08-030130 -+ stigid@rhel9: RHEL-09-654245 - stigid@sle12: SLES-12-020220 - stigid@sle15: SLES-15-030020 - stigid@ubuntu2004: UBTU-20-010102 -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/directory_group_ownership_var_log_audit/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/directory_group_ownership_var_log_audit/rule.yml -index dfff55bd3b..6b09bc56ef 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/directory_group_ownership_var_log_audit/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/directory_group_ownership_var_log_audit/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029,SRG-OS-000206-GPOS-00084 - stigid@ol8: OL08-00-030110 - stigid@rhel8: RHEL-08-030110 -+ stigid@rhel9: RHEL-09-653080 - - ocil: |- - {{% if product =="ol8" %}} -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/directory_ownership_var_log_audit/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/directory_ownership_var_log_audit/rule.yml -index 6a95e9f13b..de7b97c758 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/directory_ownership_var_log_audit/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/directory_ownership_var_log_audit/rule.yml -@@ -33,6 +33,7 @@ references: - srg: SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029,SRG-OS-000206-GPOS-00084 - stigid@ol8: OL08-00-030100 - stigid@rhel8: RHEL-08-030100 -+ stigid@rhel9: RHEL-09-653085 - - ocil_clause: the directory is not owned by root - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/file_permissions_var_log_audit/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/file_permissions_var_log_audit/rule.yml -index a7aa67de49..e73322c961 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/file_permissions_var_log_audit/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/file_permissions_var_log_audit/rule.yml -@@ -56,6 +56,7 @@ references: - stigid@ol8: OL08-00-030070 - stigid@rhel7: RHEL-07-910055 - stigid@rhel8: RHEL-08-030070 -+ stigid@rhel9: RHEL-09-653090 - stigid@ubuntu2004: UBTU-20-010122 - - ocil_clause: 'any permissions are more permissive' -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_configure_sufficiently_large_partition/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_configure_sufficiently_large_partition/rule.yml -index 5edbb9df94..849847ad75 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_configure_sufficiently_large_partition/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_configure_sufficiently_large_partition/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000341-GPOS-00132,SRG-OS-000342-GPOS-00133 - stigid@ol8: OL08-00-030660 - stigid@rhel8: RHEL-08-030660 -+ stigid@rhel9: RHEL-09-653030 - stigid@sle12: SLES-12-020020 - stigid@sle15: SLES-15-030660 - stigid@ubuntu2004: UBTU-20-010215 -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_syslog_plugin_activated/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_syslog_plugin_activated/rule.yml -index 95f7e5f44a..d58488fe8d 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_syslog_plugin_activated/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_audispd_syslog_plugin_activated/rule.yml -@@ -40,6 +40,7 @@ references: - pcidss: Req-10.5.3 - pcidss4: "10.3.3" - srg: SRG-OS-000479-GPOS-00224,SRG-OS-000342-GPOS-00133 -+ stigid@rhel9: RHEL-09-652035 - - ocil_clause: 'it is not activated' - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_error_action_stig/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_error_action_stig/rule.yml -index 6fb1ec38e9..5452ddf4de 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_error_action_stig/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_error_action_stig/rule.yml -@@ -34,6 +34,7 @@ references: - nist: AU-5(b),AU-5(2),AU-5(1),AU-5(4),CM-6(a) - nist-csf: DE.AE-3,DE.AE-5,PR.DS-4,PR.PT-1,RS.AN-1,RS.AN-4 - srg: SRG-OS-000047-GPOS-00023 -+ stigid@rhel9: RHEL-09-653020 - - ocil_clause: 'there is no evidence of appropriate action' - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_full_action_stig/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_full_action_stig/rule.yml -index 966797ef18..8183e13212 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_full_action_stig/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_disk_full_action_stig/rule.yml -@@ -34,6 +34,7 @@ references: - nist: AU-5(b),AU-5(2),AU-5(1),AU-5(4),CM-6(a) - nist-csf: DE.AE-3,DE.AE-5,PR.DS-4,PR.PT-1,RS.AN-1,RS.AN-4 - srg: SRG-OS-000047-GPOS-00023 -+ stigid@rhel9: RHEL-09-653025 - - ocil_clause: there is no evidence of appropriate action - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_action_mail_acct/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_action_mail_acct/rule.yml -index f04a42850e..03a41d58b7 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_action_mail_acct/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_action_mail_acct/rule.yml -@@ -53,6 +53,7 @@ references: - stigid@ol8: OL08-00-030020 - stigid@rhel7: RHEL-07-030350 - stigid@rhel8: RHEL-08-030020 -+ stigid@rhel9: RHEL-09-653070 - stigid@sle12: SLES-12-020040 - stigid@sle15: SLES-15-030570 - stigid@ubuntu2004: UBTU-20-010117 -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_action/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_action/rule.yml -index d2fb8df431..a3bfaf9fe7 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_action/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_action/rule.yml -@@ -54,6 +54,7 @@ references: - pcidss: Req-10.7 - pcidss4: "10.5.1" - srg: SRG-OS-000343-GPOS-00134 -+ stigid@rhel9: RHEL-09-653050 - - ocil_clause: 'there is no evidence that real-time alerts are configured on the system' - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_percentage/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_percentage/rule.yml -index 01c5df5d62..d986d448f3 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_percentage/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_admin_space_left_percentage/rule.yml -@@ -33,6 +33,7 @@ references: - nist-csf: DE.AE-3,DE.AE-5,PR.DS-4,PR.PT-1,RS.AN-1,RS.AN-4 - pcidss: Req-10.7 - srg: SRG-OS-000343-GPOS-00134 -+ stigid@rhel9: RHEL-09-653045 - - ocil_clause: 'the "admin_space_left" value is not configured to the correct value' - -@@ -52,4 +53,3 @@ fixtext: |- - - srg_requirement: |- - {{{ full_name }}} must take action when allocated audit record storage volume reaches 95 percent of the audit record storage capacity. -- -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_max_log_file_action_stig/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_max_log_file_action_stig/rule.yml -index f4e1e6d67b..6b4910f634 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_max_log_file_action_stig/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_max_log_file_action_stig/rule.yml -@@ -45,7 +45,8 @@ references: - nist-csf: DE.AE-3,DE.AE-5,PR.DS-4,PR.PT-1,RS.AN-1,RS.AN-4 - pcidss: Req-10.7 - pcidss4: "10.5.1" -- srg: SRG-OS-000047-GPOS-00023 -+ srg: SRG-OS-000047-GPOS-00023,SRG-APP-000098-CTR-000185,SRG-APP-000099-CTR-000190,SRG-APP-000100-CTR-000195,SRG-APP-000100-CTR-000200,SRG-APP-000109-CTR-000215,SRG-APP-000290-CTR-000670,SRG-APP-000357-CTR-000800 -+ stigid@rhel9: RHEL-09-653055 - - ocil_clause: 'the value of the "max_log_file_action" option is not "ROTATE", "SINGLE", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit storage volume is full. If there is no evidence of appropriate action' - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_action/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_action/rule.yml -index bea9a7805b..0d4dd64b9d 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_action/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_action/rule.yml -@@ -64,6 +64,7 @@ references: - stigid@ol8: OL08-00-030731 - stigid@rhel7: RHEL-07-030340 - stigid@rhel8: RHEL-08-030731 -+ stigid@rhel9: RHEL-09-653040 - stigid@ubuntu2004: UBTU-20-010217 - - ocil_clause: 'there is no evidence that real-time alerts are configured on the system' -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_percentage/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_percentage/rule.yml -index c82d0d3701..de0e08d46b 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_percentage/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_data_retention_space_left_percentage/rule.yml -@@ -39,6 +39,7 @@ references: - stigid@ol8: OL08-00-030730 - stigid@rhel7: RHEL-07-030330 - stigid@rhel8: RHEL-08-030730 -+ stigid@rhel9: RHEL-09-653035 - stigid@ubuntu2004: UBTU-20-010217 - - ocil_clause: 'the value of the "space_left" keyword is not set to {{{ xccdf_value("var_auditd_space_left_percentage") }}}% of the storage volume allocated to audit logs, or if the line is commented out, ask the System Administrator to indicate how the system is providing real-time alerts to the SA and ISSO. If the "space_left" value is not configured to the correct value' -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_freq/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_freq/rule.yml -index e21dfbacf2..21d9b8d5f8 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_freq/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_freq/rule.yml -@@ -24,6 +24,7 @@ references: - nist: CM-6 - ospp: FAU_GEN.1 - srg: SRG-OS-000051-GPOS-00024 -+ stigid@rhel9: RHEL-09-653095 - - ocil_clause: freq isn't set to {{{ xccdf_value("var_auditd_freq") }}} - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_local_events/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_local_events/rule.yml -index 75590e720e..e3a34e25b1 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_local_events/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_local_events/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000062-GPOS-00031,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-030061 - stigid@rhel8: RHEL-08-030061 -+ stigid@rhel9: RHEL-09-653075 - - ocil_clause: local_events isn't set to yes - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_log_format/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_log_format/rule.yml -index 475689e526..bb13c77924 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_log_format/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_log_format/rule.yml -@@ -27,6 +27,7 @@ references: - srg: SRG-OS-000255-GPOS-00096,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-030063 - stigid@rhel8: RHEL-08-030063 -+ stigid@rhel9: RHEL-09-653100 - - ocil_clause: log_format isn't set to ENRICHED - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -index 1d32aaf925..76a908f28f 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_name_format/rule.yml -@@ -30,6 +30,7 @@ references: - stigid@ol8: OL08-00-030062 - stigid@rhel7: RHEL-07-030211 - stigid@rhel8: RHEL-08-030062 -+ stigid@rhel9: RHEL-09-653060 - - ocil_clause: name_format isn't set to hostname - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_overflow_action/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_overflow_action/rule.yml -index a058b881c1..bd0205d1fd 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_overflow_action/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_overflow_action/rule.yml -@@ -33,6 +33,7 @@ references: - stigid@ol8: OL08-00-030700 - stigid@rhel7: RHEL-07-030210 - stigid@rhel8: RHEL-08-030700 -+ stigid@rhel9: RHEL-09-653065 - - ocil_clause: 'auditd overflow action is not set correctly' - -diff --git a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_write_logs/rule.yml b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_write_logs/rule.yml -index a095a5ae4f..064e9ff3e3 100644 ---- a/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_write_logs/rule.yml -+++ b/linux_os/guide/system/auditing/configure_auditd_data_retention/auditd_write_logs/rule.yml -@@ -23,6 +23,7 @@ references: - nist: CM-6 - ospp: FAU_STG.1 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-653105 - - ocil_clause: write_logs isn't set to yes - -diff --git a/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml b/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml -index e81a90bc65..2cb1b00282 100644 ---- a/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml -+++ b/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml -@@ -52,6 +52,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215,SRG-OS-000473-GPOS-00218,SRG-OS-000254-GPOS-00095 - stigid@ol8: OL08-00-030601 - stigid@rhel8: RHEL-08-030601 -+ stigid@rhel9: RHEL-09-212055 - stigid@ubuntu2004: UBTU-20-010198 - - ocil_clause: 'auditing is not enabled at boot time' -diff --git a/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml -index 65132d8ee8..80bb222932 100644 ---- a/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml -+++ b/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml -@@ -40,6 +40,7 @@ references: - srg: SRG-OS-000037-GPOS-00015,SRG-OS-000042-GPOS-00020,SRG-OS-000062-GPOS-00031,SRG-OS-000254-GPOS-00095,SRG-OS-000341-GPOS-00132,SRG-OS-000392-GPOS-00172,SRG-OS-000462-GPOS-00206,SRG-OS-000471-GPOS-00215 - stigid@ol8: OL08-00-030602 - stigid@rhel8: RHEL-08-030602 -+ stigid@rhel9: RHEL-09-653120 - - ocil_clause: 'audit backlog limit is not configured' - -diff --git a/linux_os/guide/system/auditing/package_audispd-plugins_installed/rule.yml b/linux_os/guide/system/auditing/package_audispd-plugins_installed/rule.yml -index e2d2b7fdb5..785c649715 100644 ---- a/linux_os/guide/system/auditing/package_audispd-plugins_installed/rule.yml -+++ b/linux_os/guide/system/auditing/package_audispd-plugins_installed/rule.yml -@@ -22,6 +22,7 @@ identifiers: - references: - ospp: FMT_SMF_EXT.1 - srg: SRG-OS-000342-GPOS-00133 -+ stigid@rhel9: RHEL-09-653130 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/auditing/package_audit_installed/rule.yml b/linux_os/guide/system/auditing/package_audit_installed/rule.yml -index b71d4e054a..d8378a0572 100644 ---- a/linux_os/guide/system/auditing/package_audit_installed/rule.yml -+++ b/linux_os/guide/system/auditing/package_audit_installed/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000062-GPOS-00031,SRG-OS-000037-GPOS-00015,SRG-OS-000038-GPOS-00016,SRG-OS-000039-GPOS-00017,SRG-OS-000040-GPOS-00018,SRG-OS-000041-GPOS-00019,SRG-OS-000042-GPOS-00021,SRG-OS-000051-GPOS-00024,SRG-OS-000054-GPOS-00025,SRG-OS-000122-GPOS-00063,SRG-OS-000254-GPOS-00095,SRG-OS-000255-GPOS-00096,SRG-OS-000337-GPOS-00129,SRG-OS-000348-GPOS-00136,SRG-OS-000349-GPOS-00137,SRG-OS-000350-GPOS-00138,SRG-OS-000351-GPOS-00139,SRG-OS-000352-GPOS-00140,SRG-OS-000353-GPOS-00141,SRG-OS-000354-GPOS-00142,SRG-OS-000358-GPOS-00145,SRG-OS-000365-GPOS-00152,SRG-OS-000392-GPOS-00172,SRG-OS-000475-GPOS-00220 - stigid@ol8: OL08-00-030180 - stigid@rhel8: RHEL-08-030180 -+ stigid@rhel9: RHEL-09-653010 - stigid@sle12: SLES-12-020000 - stigid@sle15: SLES-15-030650 - stigid@ubuntu2004: UBTU-20-010182 -diff --git a/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml b/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -index c5295afebb..9f2f7dbc11 100644 ---- a/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -+++ b/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000462-GPOS-00206,SRG-OS-000475-GPOS-00220,SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029 - stigid@ol8: OL08-00-030122 - stigid@rhel8: RHEL-08-030122 -+ stigid@rhel9: RHEL-09-654270 - - ocil_clause: 'the file does not exist or the content differs' - -diff --git a/linux_os/guide/system/auditing/service_auditd_enabled/rule.yml b/linux_os/guide/system/auditing/service_auditd_enabled/rule.yml -index ffcdae2492..c8592b5101 100644 ---- a/linux_os/guide/system/auditing/service_auditd_enabled/rule.yml -+++ b/linux_os/guide/system/auditing/service_auditd_enabled/rule.yml -@@ -62,6 +62,7 @@ references: - stigid@ol8: OL08-00-030181 - stigid@rhel7: RHEL-07-030000 - stigid@rhel8: RHEL-08-030181 -+ stigid@rhel9: RHEL-09-653015 - stigid@sle12: SLES-12-020010 - stigid@sle15: SLES-15-030050 - -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_pti_argument/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_pti_argument/rule.yml -index 70251f709c..f855edebd5 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_pti_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_pti_argument/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000433-GPOS-00193,SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-040004 - stigid@rhel8: RHEL-08-040004 -+ stigid@rhel9: RHEL-09-212050 - - ocil_clause: 'Kernel page-table isolation is not enabled' - -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml -index 9a0f0d2122..3e81a8aed8 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000134-GPOS-00068 - stigid@ol8: OL08-00-010422 - stigid@rhel8: RHEL-08-010422 -+ stigid@rhel9: RHEL-09-212035 - - ocil_clause: 'vsyscalls are enabled' - -@@ -47,4 +48,3 @@ fixtext: |- - - srg_requirement: - {{{ full_name }}} must disable virtual syscalls. -- -diff --git a/linux_os/guide/system/bootloader-grub2/non-uefi/file_groupowner_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/non-uefi/file_groupowner_grub2_cfg/rule.yml -index d0bdf25237..b157d9b449 100644 ---- a/linux_os/guide/system/bootloader-grub2/non-uefi/file_groupowner_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/non-uefi/file_groupowner_grub2_cfg/rule.yml -@@ -46,6 +46,7 @@ references: - pcidss: Req-7.1 - pcidss4: "2.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-212025 - - ocil_clause: '{{{ ocil_clause_file_group_owner(grub2_boot_path ~ "/grub.cfg", "root") }}}' - -diff --git a/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -index 2ef41b1c5d..fef91a47df 100644 ---- a/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -@@ -45,6 +45,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss: Req-7.1 - pcidss4: "2.2.6" -+ stigid@rhel9: RHEL-09-212030 - - ocil_clause: '{{{ ocil_clause_file_owner(file=grub2_boot_path ~ "/grub.cfg", owner="root") }}}' - -diff --git a/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_admin_username/rule.yml b/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_admin_username/rule.yml -index 05e2deae07..49a7f8d5e1 100644 ---- a/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_admin_username/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_admin_username/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-010149 - stigid@rhel7: RHEL-07-010483 - stigid@rhel8: RHEL-08-010149 -+ stigid@rhel9: RHEL-09-212020 - - ocil_clause: 'superuser account is not set or is set to root, admin, administrator or any other existing user name' - -diff --git a/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_password/rule.yml b/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_password/rule.yml -index 03031cd112..bde98a410e 100644 ---- a/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_password/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/non-uefi/grub2_password/rule.yml -@@ -73,6 +73,7 @@ references: - stigid@ol8: OL08-00-010150 - stigid@rhel7: RHEL-07-010482 - stigid@rhel8: RHEL-08-010150 -+ stigid@rhel9: RHEL-09-212010 - stigid@sle12: SLES-12-010430 - stigid@sle15: SLES-15-010190 - stigid@ubuntu2004: UBTU-20-010009 -diff --git a/linux_os/guide/system/kernel_build_config/kernel_config_page_poisoning/rule.yml b/linux_os/guide/system/kernel_build_config/kernel_config_page_poisoning/rule.yml -index db25759741..3591e41c03 100644 ---- a/linux_os/guide/system/kernel_build_config/kernel_config_page_poisoning/rule.yml -+++ b/linux_os/guide/system/kernel_build_config/kernel_config_page_poisoning/rule.yml -@@ -37,4 +37,3 @@ template: - vars: - config: CONFIG_PAGE_POISONING - value: 'y' -- -diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_cron_logging/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_cron_logging/rule.yml -index 8a7b722b9c..546ae325a0 100644 ---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_cron_logging/rule.yml -+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_cron_logging/rule.yml -@@ -39,6 +39,7 @@ references: - stigid@ol8: OL08-00-030010 - stigid@rhel7: RHEL-07-021100 - stigid@rhel8: RHEL-08-030010 -+ stigid@rhel9: RHEL-09-652060 - - ocil_clause: 'cron is not logging to rsyslog' - -diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdriverauthmode/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdriverauthmode/rule.yml -index 452294e3a7..fe5623311f 100644 ---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdriverauthmode/rule.yml -+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdriverauthmode/rule.yml -@@ -28,7 +28,7 @@ references: - srg: SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 - stigid@ol8: OL08-00-030720 - stigid@rhel8: RHEL-08-030720 -- -+ stigid@rhel9: RHEL-09-652040 - - ocil_clause: '$ActionSendStreamDriverAuthMode in /etc/rsyslog.conf is not set to x509/name' - -diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdrivermode/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdrivermode/rule.yml -index d15f2d7924..7fb97b65f3 100644 ---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdrivermode/rule.yml -+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_actionsendstreamdrivermode/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 - stigid@ol8: OL08-00-030710 - stigid@rhel8: RHEL-08-030710 -+ stigid@rhel9: RHEL-09-652045 - - ocil_clause: 'rsyslogd ActionSendStreamDriverMode is not set to 1' - -diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_defaultnetstreamdriver/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_defaultnetstreamdriver/rule.yml -index ba1095929b..12c43f3dbc 100644 ---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_defaultnetstreamdriver/rule.yml -+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_encrypt_offload_defaultnetstreamdriver/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000342-GPOS-00133,SRG-OS-000479-GPOS-00224 - stigid@ol8: OL08-00-030710 - stigid@rhel8: RHEL-08-030710 -+ stigid@rhel9: RHEL-09-652050 - - ocil_clause: 'rsyslogd DefaultNetstreamDriver not set to gtls' - -diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_remote_access_monitoring/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_remote_access_monitoring/rule.yml -index bea5ed4707..e541c0a704 100644 ---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_remote_access_monitoring/rule.yml -+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_remote_access_monitoring/rule.yml -@@ -33,6 +33,7 @@ references: - srg: SRG-OS-000032-GPOS-00013 - stigid@ol8: OL08-00-010070 - stigid@rhel8: RHEL-08-010070 -+ stigid@rhel9: RHEL-09-652030 - stigid@ubuntu2004: UBTU-20-010403 - - ocil_clause: 'remote access methods are not logging to rsyslog' -diff --git a/linux_os/guide/system/logging/journald/service_systemd-journald_enabled/rule.yml b/linux_os/guide/system/logging/journald/service_systemd-journald_enabled/rule.yml -index e43407bf6a..d07b9ff205 100644 ---- a/linux_os/guide/system/logging/journald/service_systemd-journald_enabled/rule.yml -+++ b/linux_os/guide/system/logging/journald/service_systemd-journald_enabled/rule.yml -@@ -23,6 +23,7 @@ references: - disa: CCI-001665 - nist: SC-24 - srg: SRG-OS-000269-GPOS-00103 -+ stigid@rhel9: RHEL-09-211040 - - ocil_clause: 'the systemd-journald service is not running' - -@@ -41,4 +42,3 @@ template: - vars: - servicename: systemd-journald - packagename: systemd -- -diff --git a/linux_os/guide/system/logging/package_rsyslog-gnutls_installed/rule.yml b/linux_os/guide/system/logging/package_rsyslog-gnutls_installed/rule.yml -index 0abe60b2df..5e94cfdef5 100644 ---- a/linux_os/guide/system/logging/package_rsyslog-gnutls_installed/rule.yml -+++ b/linux_os/guide/system/logging/package_rsyslog-gnutls_installed/rule.yml -@@ -32,6 +32,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000120-GPOS-00061 - stigid@ol8: OL08-00-030680 - stigid@rhel8: RHEL-08-030680 -+ stigid@rhel9: RHEL-09-652015 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml b/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml -index 70b97b107c..6b4dd08449 100644 ---- a/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml -+++ b/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml -@@ -40,6 +40,7 @@ references: - srg: SRG-OS-000479-GPOS-00224,SRG-OS-000051-GPOS-00024,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-030670 - stigid@rhel8: RHEL-08-030670 -+ stigid@rhel9: RHEL-09-652010 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml b/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml -index 1ff4d159cb..cf6f3069ee 100644 ---- a/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml -+++ b/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml -@@ -58,6 +58,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-031010 - stigid@rhel7: RHEL-07-031010 -+ stigid@rhel9: RHEL-09-652025 - - ocil_clause: "rsyslog accepts remote messages and is not documented as a log aggregation system" - -diff --git a/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml b/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml -index 99af538e94..879a629045 100644 ---- a/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml -+++ b/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml -@@ -70,6 +70,7 @@ references: - stigid@ol8: OL08-00-030690 - stigid@rhel7: RHEL-07-031000 - stigid@rhel8: RHEL-08-030690 -+ stigid@rhel9: RHEL-09-652055 - stigid@sle12: SLES-12-030340 - stigid@sle15: SLES-15-010580 - -diff --git a/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml b/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml -index 5dcdc7fb51..f2e7194968 100644 ---- a/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml -+++ b/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010561 - stigid@rhel8: RHEL-08-010561 -+ stigid@rhel9: RHEL-09-652020 - stigid@ubuntu2004: UBTU-20-010432 - - ocil_clause: '{{{ ocil_clause_service_enabled(service="rsyslog") }}}' -diff --git a/linux_os/guide/system/network/network-firewalld/firewalld-backend/rule.yml b/linux_os/guide/system/network/network-firewalld/firewalld-backend/rule.yml -index cdf4f0eff6..f9a95d2f82 100644 ---- a/linux_os/guide/system/network/network-firewalld/firewalld-backend/rule.yml -+++ b/linux_os/guide/system/network/network-firewalld/firewalld-backend/rule.yml -@@ -27,6 +27,7 @@ references: - srg: SRG-OS-000420-GPOS-00186 - stigid@ol8: OL08-00-040150 - stigid@rhel8: RHEL-08-040150 -+ stigid@rhel9: RHEL-09-251030 - - ocil_clause: 'the "nftables" is not set as the "firewallbackend"' - -diff --git a/linux_os/guide/system/network/network-firewalld/firewalld_activation/package_firewalld_installed/rule.yml b/linux_os/guide/system/network/network-firewalld/firewalld_activation/package_firewalld_installed/rule.yml -index fd1fe14943..02a06babe6 100644 ---- a/linux_os/guide/system/network/network-firewalld/firewalld_activation/package_firewalld_installed/rule.yml -+++ b/linux_os/guide/system/network/network-firewalld/firewalld_activation/package_firewalld_installed/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol7: OL07-00-040520 - stigid@ol8: OL08-00-040100 - stigid@rhel8: RHEL-08-040100 -+ stigid@rhel9: RHEL-09-251010 - stigid@sle15: SLES-15-010220 - - ocil_clause: 'the package is not installed' -diff --git a/linux_os/guide/system/network/network-firewalld/firewalld_activation/service_firewalld_enabled/rule.yml b/linux_os/guide/system/network/network-firewalld/firewalld_activation/service_firewalld_enabled/rule.yml -index 52bc3288f5..fc30d75740 100644 ---- a/linux_os/guide/system/network/network-firewalld/firewalld_activation/service_firewalld_enabled/rule.yml -+++ b/linux_os/guide/system/network/network-firewalld/firewalld_activation/service_firewalld_enabled/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-040101 - stigid@rhel7: RHEL-07-040520 - stigid@rhel8: RHEL-08-040101 -+ stigid@rhel9: RHEL-09-251015 - stigid@sle15: SLES-15-010220 - - ocil_clause: '{{{ ocil_clause_service_enabled("firewalld") }}}' -diff --git a/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml b/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml -index 18e51cc420..056c07d88a 100644 ---- a/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml -+++ b/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configure_firewalld_ports/rule.yml -@@ -53,6 +53,7 @@ references: - stigid@ol8: OL08-00-040030 - stigid@rhel7: RHEL-07-040100 - stigid@rhel8: RHEL-08-040030 -+ stigid@rhel9: RHEL-09-251025 - - ocil_clause: 'there are additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), or there are no firewall rules configured' - -diff --git a/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configured_firewalld_default_deny/rule.yml b/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configured_firewalld_default_deny/rule.yml -index 2c0820d666..6a498a6902 100644 ---- a/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configured_firewalld_default_deny/rule.yml -+++ b/linux_os/guide/system/network/network-firewalld/ruleset_modifications/configured_firewalld_default_deny/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000297-GPOS-00115 - stigid@ol8: OL08-00-040090 - stigid@rhel8: RHEL-08-040090 -+ stigid@rhel9: RHEL-09-251020 - - ocil_clause: 'no zones are active on the interfaces or if the target is set to a different option other than "DROP"' - -diff --git a/linux_os/guide/system/network/network-ipsec/libreswan_approved_tunnels/rule.yml b/linux_os/guide/system/network/network-ipsec/libreswan_approved_tunnels/rule.yml -index 995b046df4..567c7ff948 100644 ---- a/linux_os/guide/system/network/network-ipsec/libreswan_approved_tunnels/rule.yml -+++ b/linux_os/guide/system/network/network-ipsec/libreswan_approved_tunnels/rule.yml -@@ -35,6 +35,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040820 - stigid@rhel7: RHEL-07-040820 -+ stigid@rhel9: RHEL-09-252045 - - ocil_clause: 'the IPSec tunnels are not approved' - -diff --git a/linux_os/guide/system/network/network-ipsec/package_libreswan_installed/rule.yml b/linux_os/guide/system/network/network-ipsec/package_libreswan_installed/rule.yml -index 9427aee635..4b9c9121ec 100644 ---- a/linux_os/guide/system/network/network-ipsec/package_libreswan_installed/rule.yml -+++ b/linux_os/guide/system/network/network-ipsec/package_libreswan_installed/rule.yml -@@ -8,7 +8,7 @@ description: |- - The libreswan package provides an implementation of IPsec - and IKE, which permits the creation of secure tunnels over - untrusted networks. {{{ describe_package_install(package="libreswan") }}} -- -+ - - rationale: |- - Providing the ability for remote users or systems -@@ -37,7 +37,8 @@ references: - pcidss: Req-4.1 - pcidss4: "4.2.1" - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000120-GPOS-00061 -- -+ stigid@rhel9: RHEL-09-252065 -+ - ocil_clause: 'the package is not installed' - - ocil: '{{{ ocil_package(package="libreswan") }}}' -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_ra/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_ra/rule.yml -index f9728d7dcd..7cb30d194f 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_ra/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_ra/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040261 - stigid@rhel8: RHEL-08-040261 -+ stigid@rhel9: RHEL-09-254010 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv6.conf.all.accept_ra", value="0") }}} - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_redirects/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_redirects/rule.yml -index 2d8036595b..d986698c6d 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_redirects/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040280 - stigid@rhel8: RHEL-08-040280 -+ stigid@rhel9: RHEL-09-254015 - stigid@sle12: SLES-12-030363 - stigid@sle15: SLES-15-040341 - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_source_route/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_source_route/rule.yml -index 834c8c2c1c..27add44823 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_source_route/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_accept_source_route/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-040240 - stigid@rhel7: RHEL-07-040830 - stigid@rhel8: RHEL-08-040240 -+ stigid@rhel9: RHEL-09-254020 - stigid@sle12: SLES-12-030361 - stigid@sle15: SLES-15-040310 - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_forwarding/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_forwarding/rule.yml -index 7373f9a7d9..ccc429d5b6 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_forwarding/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_all_forwarding/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040260 - stigid@rhel8: RHEL-08-040260 -+ stigid@rhel9: RHEL-09-254025 - stigid@sle12: SLES-12-030364 - stigid@sle15: SLES-15-040381 - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_ra/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_ra/rule.yml -index 68083fac12..07374bdb8a 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_ra/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_ra/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040262 - stigid@rhel8: RHEL-08-040262 -+ stigid@rhel9: RHEL-09-254030 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv6.conf.default.accept_ra", value="0") }}} - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_redirects/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_redirects/rule.yml -index 1fa3ff0389..7769ce20ec 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_redirects/rule.yml -@@ -44,6 +44,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040210 - stigid@rhel8: RHEL-08-040210 -+ stigid@rhel9: RHEL-09-254035 - stigid@sle12: SLES-12-030401 - stigid@sle15: SLES-15-040350 - -diff --git a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_source_route/rule.yml b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_source_route/rule.yml -index 6f29e358d9..ba833372aa 100644 ---- a/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_source_route/rule.yml -+++ b/linux_os/guide/system/network/network-ipv6/configuring_ipv6/sysctl_net_ipv6_conf_default_accept_source_route/rule.yml -@@ -51,6 +51,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040250 - stigid@rhel8: RHEL-08-040250 -+ stigid@rhel9: RHEL-09-254040 - stigid@sle12: SLES-12-030362 - stigid@sle15: SLES-15-040321 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_redirects/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_redirects/rule.yml -index 6434038562..9f047ea906 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_redirects/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-040279 - stigid@rhel7: RHEL-07-040641 - stigid@rhel8: RHEL-08-040279 -+ stigid@rhel9: RHEL-09-253015 - stigid@sle12: SLES-12-030390 - stigid@sle15: SLES-15-040330 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_source_route/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_source_route/rule.yml -index 2620e42881..88bfe6d7d4 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_source_route/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_accept_source_route/rule.yml -@@ -53,6 +53,7 @@ references: - stigid@ol8: OL08-00-040239 - stigid@rhel7: RHEL-07-040610 - stigid@rhel8: RHEL-08-040239 -+ stigid@rhel9: RHEL-09-253020 - stigid@sle12: SLES-12-030360 - stigid@sle15: SLES-15-040300 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_forwarding/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_forwarding/rule.yml -index a75bcc616d..9a36d23899 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_forwarding/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_forwarding/rule.yml -@@ -23,6 +23,7 @@ references: - nist: CM-6(b) - srg: SRG-OS-000480-GPOS-00227 - stigid@rhel8: RHEL-08-040259 -+ stigid@rhel9: RHEL-09-253075 - - ocil_clause: 'IP forwarding value is "1" and the system is not router' - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_log_martians/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_log_martians/rule.yml -index 11dc1ce813..b1df46e254 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_log_martians/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_log_martians/rule.yml -@@ -43,6 +43,7 @@ references: - nist: CM-7(a),CM-7(b),SC-5(3)(a) - nist-csf: DE.CM-1,PR.AC-3,PR.DS-4,PR.IP-1,PR.PT-3,PR.PT-4 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-253025 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv4.conf.all.log_martians", value="1") }}} - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_rp_filter/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_rp_filter/rule.yml -index 3a4507eff7..832ea91edf 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_rp_filter/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_all_rp_filter/rule.yml -@@ -50,6 +50,7 @@ references: - stigid@ol8: OL08-00-040285 - stigid@rhel7: RHEL-07-040611 - stigid@rhel8: RHEL-08-040285 -+ stigid@rhel9: RHEL-09-253035 - - ocil: |- - The runtime status of the net.ipv4.conf.all.rp_filter parameter can be queried -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_redirects/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_redirects/rule.yml -index 4184bfc833..9303e24ccc 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_redirects/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-040209 - stigid@rhel7: RHEL-07-040640 - stigid@rhel8: RHEL-08-040209 -+ stigid@rhel9: RHEL-09-253040 - stigid@sle12: SLES-12-030400 - stigid@sle15: SLES-15-040340 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_source_route/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_source_route/rule.yml -index 0de834a155..d43d147ceb 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_source_route/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_accept_source_route/rule.yml -@@ -54,6 +54,7 @@ references: - stigid@ol8: OL08-00-040249 - stigid@rhel7: RHEL-07-040620 - stigid@rhel8: RHEL-08-040249 -+ stigid@rhel9: RHEL-09-253045 - stigid@sle12: SLES-12-030370 - stigid@sle15: SLES-15-040320 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_log_martians/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_log_martians/rule.yml -index 84b4b78e7d..be9262e372 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_log_martians/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_log_martians/rule.yml -@@ -43,6 +43,7 @@ references: - nist: CM-7(a),CM-7(b),SC-5(3)(a) - nist-csf: DE.CM-1,PR.AC-3,PR.DS-4,PR.IP-1,PR.PT-3,PR.PT-4 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-253030 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv4.conf.default.log_martians", value="1") }}} - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_rp_filter/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_rp_filter/rule.yml -index 2de023866c..e7a2772354 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_rp_filter/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_conf_default_rp_filter/rule.yml -@@ -47,6 +47,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-040612 - stigid@rhel7: RHEL-07-040612 -+ stigid@rhel9: RHEL-09-253050 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv4.conf.default.rp_filter", value="1") }}} - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_echo_ignore_broadcasts/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_echo_ignore_broadcasts/rule.yml -index 6aa5a30a5c..8512b96428 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_echo_ignore_broadcasts/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_echo_ignore_broadcasts/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-040230 - stigid@rhel7: RHEL-07-040630 - stigid@rhel8: RHEL-08-040230 -+ stigid@rhel9: RHEL-09-253055 - stigid@sle12: SLES-12-030380 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv4.icmp_echo_ignore_broadcasts", value="1") }}} -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_ignore_bogus_error_responses/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_ignore_bogus_error_responses/rule.yml -index 5e9c18bcb8..58fef11d13 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_ignore_bogus_error_responses/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_icmp_ignore_bogus_error_responses/rule.yml -@@ -43,6 +43,7 @@ references: - nist-csf: DE.CM-1,PR.DS-4,PR.IP-1,PR.PT-3 - pcidss: Req-1.4.3 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-253060 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.ipv4.icmp_ignore_bogus_error_responses", value="1") }}} - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_tcp_syncookies/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_tcp_syncookies/rule.yml -index 0b4f362725..984c7ff81e 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_tcp_syncookies/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_and_router_parameters/sysctl_net_ipv4_tcp_syncookies/rule.yml -@@ -48,6 +48,7 @@ references: - nist-csf: DE.AE-1,DE.CM-1,ID.AM-3,PR.AC-5,PR.DS-4,PR.DS-5,PR.PT-4 - pcidss: Req-1.4.1 - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000420-GPOS-00186,SRG-OS-000142-GPOS-00071 -+ stigid@rhel9: RHEL-09-253010 - stigid@sle12: SLES-12-030350 - stigid@sle15: SLES-15-010310 - stigid@ubuntu2004: UBTU-20-010412 -diff --git a/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_all_send_redirects/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_all_send_redirects/rule.yml -index 3bdc1dfea7..969fe698dc 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_all_send_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_all_send_redirects/rule.yml -@@ -52,6 +52,7 @@ references: - stigid@ol8: OL08-00-040220 - stigid@rhel7: RHEL-07-040660 - stigid@rhel8: RHEL-08-040220 -+ stigid@rhel9: RHEL-09-253065 - stigid@sle12: SLES-12-030420 - stigid@sle15: SLES-15-040370 - -diff --git a/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_default_send_redirects/rule.yml b/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_default_send_redirects/rule.yml -index d456a9de6e..136847aa52 100644 ---- a/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_default_send_redirects/rule.yml -+++ b/linux_os/guide/system/network/network-kernel/network_host_parameters/sysctl_net_ipv4_conf_default_send_redirects/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-040270 - stigid@rhel7: RHEL-07-040650 - stigid@rhel8: RHEL-08-040270 -+ stigid@rhel9: RHEL-09-253070 - stigid@sle12: SLES-12-030410 - stigid@sle15: SLES-15-040360 - -diff --git a/linux_os/guide/system/network/network-uncommon/kernel_module_atm_disabled/rule.yml b/linux_os/guide/system/network/network-uncommon/kernel_module_atm_disabled/rule.yml -index f995e27951..26b93bf78e 100644 ---- a/linux_os/guide/system/network/network-uncommon/kernel_module_atm_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-uncommon/kernel_module_atm_disabled/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040021 - stigid@rhel8: RHEL-08-040021 -+ stigid@rhel9: RHEL-09-213045 - - {{{ complete_ocil_entry_module_disable(module="atm") }}} - -diff --git a/linux_os/guide/system/network/network-uncommon/kernel_module_can_disabled/rule.yml b/linux_os/guide/system/network/network-uncommon/kernel_module_can_disabled/rule.yml -index 420485c11a..61febfa322 100644 ---- a/linux_os/guide/system/network/network-uncommon/kernel_module_can_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-uncommon/kernel_module_can_disabled/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040022 - stigid@rhel8: RHEL-08-040022 -+ stigid@rhel9: RHEL-09-213050 - - {{{ complete_ocil_entry_module_disable(module="can") }}} - -diff --git a/linux_os/guide/system/network/network-uncommon/kernel_module_firewire-core_disabled/rule.yml b/linux_os/guide/system/network/network-uncommon/kernel_module_firewire-core_disabled/rule.yml -index 0522abc152..919326417d 100644 ---- a/linux_os/guide/system/network/network-uncommon/kernel_module_firewire-core_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-uncommon/kernel_module_firewire-core_disabled/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-040026 - stigid@rhel8: RHEL-08-040026 -+ stigid@rhel9: RHEL-09-213055 - - {{{ complete_ocil_entry_module_disable(module="firewire-core") }}} - -diff --git a/linux_os/guide/system/network/network-uncommon/kernel_module_sctp_disabled/rule.yml b/linux_os/guide/system/network/network-uncommon/kernel_module_sctp_disabled/rule.yml -index 0da8cd9fe4..c4739b912b 100644 ---- a/linux_os/guide/system/network/network-uncommon/kernel_module_sctp_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-uncommon/kernel_module_sctp_disabled/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040023 - stigid@rhel8: RHEL-08-040023 -+ stigid@rhel9: RHEL-09-213060 - - {{{ complete_ocil_entry_module_disable(module="sctp") }}} - -diff --git a/linux_os/guide/system/network/network-uncommon/kernel_module_tipc_disabled/rule.yml b/linux_os/guide/system/network/network-uncommon/kernel_module_tipc_disabled/rule.yml -index 075d86c275..c59cdc395e 100644 ---- a/linux_os/guide/system/network/network-uncommon/kernel_module_tipc_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-uncommon/kernel_module_tipc_disabled/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-040024 - stigid@rhel8: RHEL-08-040024 -+ stigid@rhel9: RHEL-09-213065 - - {{{ complete_ocil_entry_module_disable(module="tipc") }}} - -diff --git a/linux_os/guide/system/network/network-wireless/wireless_software/kernel_module_bluetooth_disabled/rule.yml b/linux_os/guide/system/network/network-wireless/wireless_software/kernel_module_bluetooth_disabled/rule.yml -index 847d212368..1172e7dbd1 100644 ---- a/linux_os/guide/system/network/network-wireless/wireless_software/kernel_module_bluetooth_disabled/rule.yml -+++ b/linux_os/guide/system/network/network-wireless/wireless_software/kernel_module_bluetooth_disabled/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000300-GPOS-00118 - stigid@ol8: OL08-00-040111 - stigid@rhel8: RHEL-08-040111 -+ stigid@rhel9: RHEL-09-291035 - - {{{ complete_ocil_entry_module_disable(module="bluetooth") }}} - -@@ -45,9 +46,9 @@ fixtext: |- - Configure {{{ full_name }}} to disable the Bluetooth adapter when not in use. - - Create or modify the "/etc/modprobe.d/bluetooth.conf" file with the following line: -- -+ - install bluetooth /bin/true -- -+ - Reboot the system for the settings to take effect. - - srg_requirement: '{{{ srg_requirement_kernel_module_disable('bluetooth') }}}' -diff --git a/linux_os/guide/system/network/network-wireless/wireless_software/wireless_disable_interfaces/rule.yml b/linux_os/guide/system/network/network-wireless/wireless_software/wireless_disable_interfaces/rule.yml -index cb57496539..dfec17a79c 100644 ---- a/linux_os/guide/system/network/network-wireless/wireless_software/wireless_disable_interfaces/rule.yml -+++ b/linux_os/guide/system/network/network-wireless/wireless_software/wireless_disable_interfaces/rule.yml -@@ -66,6 +66,7 @@ references: - stigid@ol8: OL08-00-040110 - stigid@rhel7: RHEL-07-041010 - stigid@rhel8: RHEL-08-040110 -+ stigid@rhel9: RHEL-09-291040 - stigid@sle12: SLES-12-030450 - stigid@sle15: SLES-15-010380 - stigid@ubuntu2004: UBTU-20-010455 -diff --git a/linux_os/guide/system/network/network_configure_name_resolution/rule.yml b/linux_os/guide/system/network/network_configure_name_resolution/rule.yml -index bf2339bbde..019542b6dd 100644 ---- a/linux_os/guide/system/network/network_configure_name_resolution/rule.yml -+++ b/linux_os/guide/system/network/network_configure_name_resolution/rule.yml -@@ -55,6 +55,7 @@ references: - stigid@ol8: OL08-00-010680 - stigid@rhel7: RHEL-07-040600 - stigid@rhel8: RHEL-08-010680 -+ stigid@rhel9: RHEL-09-252035 - - ocil_clause: 'less than two lines are returned that are not commented out' - -diff --git a/linux_os/guide/system/network/network_sniffer_disabled/rule.yml b/linux_os/guide/system/network/network_sniffer_disabled/rule.yml -index 6970bbdba0..072b433944 100644 ---- a/linux_os/guide/system/network/network_sniffer_disabled/rule.yml -+++ b/linux_os/guide/system/network/network_sniffer_disabled/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-040330 - stigid@rhel7: RHEL-07-040670 - stigid@rhel8: RHEL-08-040330 -+ stigid@rhel9: RHEL-09-251040 - stigid@sle12: SLES-12-030440 - stigid@sle15: SLES-15-040390 - -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml -index 8b703cb2f1..210746188c 100644 ---- a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml -@@ -20,6 +20,7 @@ references: - disa: CCI-000366 - nist: CM-6(b) - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-252040 - - ocil_clause: 'the dns key under main does not exist or is not set to "none" or "default"' - -diff --git a/linux_os/guide/system/permissions/files/dir_perms_world_writable_root_owned/rule.yml b/linux_os/guide/system/permissions/files/dir_perms_world_writable_root_owned/rule.yml -index 678b06d338..0654db0ad0 100644 ---- a/linux_os/guide/system/permissions/files/dir_perms_world_writable_root_owned/rule.yml -+++ b/linux_os/guide/system/permissions/files/dir_perms_world_writable_root_owned/rule.yml -@@ -28,6 +28,7 @@ references: - disa: CCI-000366 - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000138-GPOS-00069 - stigid@rhel8: RHEL-08-010700 -+ stigid@rhel9: RHEL-09-232240 - - ocil_clause: 'there are world-writable directories not owned by root' - -diff --git a/linux_os/guide/system/permissions/files/dir_perms_world_writable_sticky_bits/rule.yml b/linux_os/guide/system/permissions/files/dir_perms_world_writable_sticky_bits/rule.yml -index be74f698ec..048360b7be 100644 ---- a/linux_os/guide/system/permissions/files/dir_perms_world_writable_sticky_bits/rule.yml -+++ b/linux_os/guide/system/permissions/files/dir_perms_world_writable_sticky_bits/rule.yml -@@ -62,6 +62,7 @@ references: - srg: SRG-OS-000138-GPOS-00069 - stigid@ol8: OL08-00-010190 - stigid@rhel8: RHEL-08-010190 -+ stigid@rhel9: RHEL-09-232245 - stigid@sle12: SLES-12-010460 - stigid@sle15: SLES-15-010300 - stigid@ubuntu2004: UBTU-20-010411 -diff --git a/linux_os/guide/system/permissions/files/file_permissions_etc_audit_auditd/rule.yml b/linux_os/guide/system/permissions/files/file_permissions_etc_audit_auditd/rule.yml -index c9ed36852e..13356b344a 100644 ---- a/linux_os/guide/system/permissions/files/file_permissions_etc_audit_auditd/rule.yml -+++ b/linux_os/guide/system/permissions/files/file_permissions_etc_audit_auditd/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000063-GPOS-00032 - stigid@ol8: OL08-00-030610 - stigid@rhel8: RHEL-08-030610 -+ stigid@rhel9: RHEL-09-653115 - stigid@ubuntu2004: UBTU-20-010133 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/audit/auditd.conf", perms="-rw-r-----") }}}' -diff --git a/linux_os/guide/system/permissions/files/file_permissions_etc_audit_rulesd/rule.yml b/linux_os/guide/system/permissions/files/file_permissions_etc_audit_rulesd/rule.yml -index ec3bba5b8a..0e592304a8 100644 ---- a/linux_os/guide/system/permissions/files/file_permissions_etc_audit_rulesd/rule.yml -+++ b/linux_os/guide/system/permissions/files/file_permissions_etc_audit_rulesd/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000063-GPOS-00032 - stigid@ol8: OL08-00-030610 - stigid@rhel8: RHEL-08-030610 -+ stigid@rhel9: RHEL-09-653110 - stigid@ubuntu2004: UBTU-20-010133 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/audit/rules.d/*.rules", perms="-rw-r-----") }}}' -diff --git a/linux_os/guide/system/permissions/files/file_permissions_ungroupowned/rule.yml b/linux_os/guide/system/permissions/files/file_permissions_ungroupowned/rule.yml -index d2aa53a986..b366421864 100644 ---- a/linux_os/guide/system/permissions/files/file_permissions_ungroupowned/rule.yml -+++ b/linux_os/guide/system/permissions/files/file_permissions_ungroupowned/rule.yml -@@ -58,6 +58,7 @@ references: - stigid@ol8: OL08-00-010790 - stigid@rhel7: RHEL-07-020330 - stigid@rhel8: RHEL-08-010790 -+ stigid@rhel9: RHEL-09-232250 - stigid@sle12: SLES-12-010700 - stigid@sle15: SLES-15-040410 - -diff --git a/linux_os/guide/system/permissions/files/no_files_unowned_by_user/rule.yml b/linux_os/guide/system/permissions/files/no_files_unowned_by_user/rule.yml -index 13650fcea5..11ed3b37e7 100644 ---- a/linux_os/guide/system/permissions/files/no_files_unowned_by_user/rule.yml -+++ b/linux_os/guide/system/permissions/files/no_files_unowned_by_user/rule.yml -@@ -57,6 +57,7 @@ references: - stigid@ol8: OL08-00-010780 - stigid@rhel7: RHEL-07-020320 - stigid@rhel8: RHEL-08-010780 -+ stigid@rhel9: RHEL-09-232255 - stigid@sle12: SLES-12-010690 - stigid@sle15: SLES-15-040400 - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_group/rule.yml -index 7e5c5ebaed..29556b82bd 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_group/rule.yml -@@ -33,6 +33,7 @@ references: - pcidss: Req-8.7 - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232105 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/group-", group="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml -index 8c7c1b0fea..2738e23377 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml -@@ -38,6 +38,7 @@ references: - pcidss: Req-8.7 - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232125 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/gshadow-", group=target_group) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_passwd/rule.yml -index e1a5b1023a..3370599f03 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_passwd/rule.yml -@@ -33,6 +33,7 @@ references: - pcidss: Req-8.7 - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232145 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/passwd-", group="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml -index 6031702990..290ab5e719 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml -@@ -37,6 +37,7 @@ references: - pcidss: Req-8.7 - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232165 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/shadow-", group=target_group) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_group/rule.yml -index 8861983fb1..ef80fd7168 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_group/rule.yml -@@ -39,6 +39,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232095 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/group", group="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_gshadow/rule.yml -index 701a7e0096..08e7210b53 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_gshadow/rule.yml -@@ -42,6 +42,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232115 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/gshadow", group=target_group) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_passwd/rule.yml -index d1e4a79ebc..b04ec48a0e 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_passwd/rule.yml -@@ -38,6 +38,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232135 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/passwd", group="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_shadow/rule.yml -index 3ee4090438..97fe416c9a 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_etc_shadow/rule.yml -@@ -45,6 +45,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232155 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/etc/shadow", group=target_group) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_group/rule.yml -index d9a20c008e..791f259b92 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_group/rule.yml -@@ -33,6 +33,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232100 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/group-", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_gshadow/rule.yml -index f5abc26569..2c65eccd5a 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_gshadow/rule.yml -@@ -32,6 +32,7 @@ references: - pcidss: Req-8.7 - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232120 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/gshadow-", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_passwd/rule.yml -index 166df2a0c4..a0bf253905 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_passwd/rule.yml -@@ -33,6 +33,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232140 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/passwd-", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_shadow/rule.yml -index 49261333e2..7f17d2bead 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_backup_etc_shadow/rule.yml -@@ -33,6 +33,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232160 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/shadow-", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_group/rule.yml -index 4924396804..dd69b3b3c5 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_group/rule.yml -@@ -40,6 +40,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232090 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/group", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_gshadow/rule.yml -index fdf6869b5c..db292c000d 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_gshadow/rule.yml -@@ -38,6 +38,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232110 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/gshadow", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_passwd/rule.yml -index 7cbb326f98..6e8276d93f 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_passwd/rule.yml -@@ -39,6 +39,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232130 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/passwd", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_shadow/rule.yml -index eb96ee32cb..0a610fa5fc 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_owner_etc_shadow/rule.yml -@@ -44,6 +44,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232150 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/etc/shadow", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_group/rule.yml -index a69e06ae90..b9e8f5da5c 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_group/rule.yml -@@ -34,6 +34,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232060 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/group-", perms="-rw-r--r--") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_gshadow/rule.yml -index 1664e496eb..fdc7bed884 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_gshadow/rule.yml -@@ -39,6 +39,7 @@ references: - disa: CCI-002223 - nist: AC-6 (1) - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232070 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/gshadow-", perms=target_perms) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_passwd/rule.yml -index faf7d5b038..cc27002c83 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_passwd/rule.yml -@@ -34,6 +34,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232080 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/passwd-", perms="-rw-r--r--") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_shadow/rule.yml -index c47c89ea80..a6a50a9576 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_backup_etc_shadow/rule.yml -@@ -42,6 +42,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232085 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/shadow-", perms=target_perms) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_group/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_group/rule.yml -index d23d3f0f93..c7e74e7788 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_group/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_group/rule.yml -@@ -42,7 +42,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -- -+ stigid@rhel9: RHEL-09-232055 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/group", perms="-rw-r--r--") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_gshadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_gshadow/rule.yml -index 826e5e92f0..3d117149a1 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_gshadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_gshadow/rule.yml -@@ -47,6 +47,7 @@ references: - nist: CM-6(a),AC-6(1) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232065 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/gshadow", perms=target_perms) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_passwd/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_passwd/rule.yml -index 9cfa9c7ac4..705f0dbcd4 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_passwd/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_passwd/rule.yml -@@ -43,6 +43,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232075 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/passwd", perms="-rw-r--r--") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_shadow/rule.yml b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_shadow/rule.yml -index 531d3e3df2..25f28e7f7b 100644 ---- a/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_shadow/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_important_account_files/file_permissions_etc_shadow/rule.yml -@@ -53,6 +53,7 @@ references: - pcidss: Req-8.7.c - pcidss4: "7.2.6" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-232270 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/etc/shadow", perms=target_perms) }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log/rule.yml -index aff9b4912e..8c52048066 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000206-GPOS-00084,SRG-APP-000118-CTR-000240 - stigid@ol8: OL08-00-010260 - stigid@rhel8: RHEL-08-010260 -+ stigid@rhel9: RHEL-09-232175 - stigid@ubuntu2004: UBTU-20-010417 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/var/log", group=gid) }}}' -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log_messages/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log_messages/rule.yml -index 797bfafc39..8e4b7d00c5 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log_messages/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_groupowner_var_log_messages/rule.yml -@@ -19,6 +19,7 @@ references: - srg: SRG-OS-000206-GPOS-00084 - stigid@ol8: OL08-00-010230 - stigid@rhel8: RHEL-08-010230 -+ stigid@rhel9: RHEL-09-232185 - - ocil_clause: '{{{ ocil_clause_file_group_owner(file="/var/log/messages", group="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log/rule.yml -index f81fce93ec..5870e7e270 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log/rule.yml -@@ -21,6 +21,7 @@ references: - srg: SRG-OS-000206-GPOS-00084,SRG-APP-000118-CTR-000240 - stigid@ol8: OL08-00-010250 - stigid@rhel8: RHEL-08-010250 -+ stigid@rhel9: RHEL-09-232170 - stigid@ubuntu2004: UBTU-20-010418 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/var/log", owner="root") }}}' -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log_messages/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log_messages/rule.yml -index f0d63e3617..a286eff798 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log_messages/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_owner_var_log_messages/rule.yml -@@ -19,6 +19,7 @@ references: - srg: SRG-OS-000206-GPOS-00084 - stigid@ol8: OL08-00-010220 - stigid@rhel8: RHEL-08-010220 -+ stigid@rhel9: RHEL-09-232180 - - ocil_clause: '{{{ ocil_clause_file_owner(file="/var/log/messages", owner="root") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log/rule.yml -index fa83358bff..528f86713a 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log/rule.yml -@@ -23,6 +23,7 @@ references: - srg: SRG-OS-000206-GPOS-00084,SRG-APP-000118-CTR-000240 - stigid@ol8: OL08-00-010240 - stigid@rhel8: RHEL-08-010240 -+ stigid@rhel9: RHEL-09-232025 - stigid@ubuntu2004: UBTU-20-010419 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/var/log", perms="drwxr-xr-x") }}}' -diff --git a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log_messages/rule.yml b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log_messages/rule.yml -index d0cded9af7..b92a282820 100644 ---- a/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log_messages/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_var_log_dir/file_permissions_var_log_messages/rule.yml -@@ -20,6 +20,7 @@ references: - srg: SRG-OS-000206-GPOS-00084 - stigid@ol8: OL08-00-010210 - stigid@rhel8: RHEL-08-010210 -+ stigid@rhel9: RHEL-09-232030 - - ocil_clause: '{{{ ocil_clause_file_permissions(file="/var/log/messages", perms="-rw-r-----") }}}' - -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_group_ownership_library_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_group_ownership_library_dirs/rule.yml -index 8f41e6219d..5e84759ab0 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_group_ownership_library_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_group_ownership_library_dirs/rule.yml -@@ -40,6 +40,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010351 - stigid@rhel8: RHEL-08-010351 -+ stigid@rhel9: RHEL-09-232215 - stigid@sle12: SLES-12-010876 - stigid@sle15: SLES-15-010356 - stigid@ubuntu2004: UBTU-20-010431 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_ownership_library_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_ownership_library_dirs/rule.yml -index c5d67497f8..d69dcf07e9 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_ownership_library_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_ownership_library_dirs/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010341 - stigid@rhel8: RHEL-08-010341 -+ stigid@rhel9: RHEL-09-232210 - stigid@sle12: SLES-12-010874 - stigid@sle15: SLES-15-010354 - stigid@ubuntu2004: UBTU-20-010429 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_permissions_library_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_permissions_library_dirs/rule.yml -index 68230eb4b0..5e9aeae2b8 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_permissions_library_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/dir_permissions_library_dirs/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010331 - stigid@rhel8: RHEL-08-010331 -+ stigid@rhel9: RHEL-09-232015 - stigid@sle12: SLES-12-010872 - stigid@sle15: SLES-15-010352 - stigid@ubuntu2004: UBTU-20-010427 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_groupownership_system_commands_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_groupownership_system_commands_dirs/rule.yml -index d50a7162e2..f4e81b24ce 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_groupownership_system_commands_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_groupownership_system_commands_dirs/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010320 - stigid@rhel8: RHEL-08-010320 -+ stigid@rhel9: RHEL-09-232195 - stigid@sle12: SLES-12-010882 - stigid@sle15: SLES-15-010361 - stigid@ubuntu2004: UBTU-20-010458 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_binary_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_binary_dirs/rule.yml -index 32b2d523db..7350927874 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_binary_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_binary_dirs/rule.yml -@@ -44,7 +44,8 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010310 - stigid@rhel8: RHEL-08-010310 -- stigid@sle12: SLES-15-010879 -+ stigid@rhel9: RHEL-09-232190 -+ stigid@sle12: SLES-12-010879 - stigid@sle15: SLES-15-010359 - stigid@ubuntu2004: UBTU-20-010457 - -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_library_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_library_dirs/rule.yml -index bc1f3caff0..c02b4c8964 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_library_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_ownership_library_dirs/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010340 - stigid@rhel8: RHEL-08-010340 -+ stigid@rhel9: RHEL-09-232200 - stigid@sle12: SLES-12-010873 - stigid@sle15: SLES-15-010353 - stigid@ubuntu2004: UBTU-20-010428 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_binary_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_binary_dirs/rule.yml -index aed33a4940..2a3e521fa7 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_binary_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_binary_dirs/rule.yml -@@ -44,6 +44,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010300 - stigid@rhel8: RHEL-08-010300 -+ stigid@rhel9: RHEL-09-232010 - stigid@sle12: SLES-12-010878 - stigid@sle15: SLES-15-010358 - stigid@ubuntu2004: UBTU-20-010456 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_library_dirs/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_library_dirs/rule.yml -index f497a602af..12d8448a77 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_library_dirs/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/file_permissions_library_dirs/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010330 - stigid@rhel8: RHEL-08-010330 -+ stigid@rhel9: RHEL-09-232020 - stigid@sle12: SLES-12-010871 - stigid@sle15: SLES-15-010351 - stigid@ubuntu2004: UBTU-20-010426 -diff --git a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/root_permissions_syslibrary_files/rule.yml b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/root_permissions_syslibrary_files/rule.yml -index 662778c70e..2d4f70bbda 100644 ---- a/linux_os/guide/system/permissions/files/permissions_within_important_dirs/root_permissions_syslibrary_files/rule.yml -+++ b/linux_os/guide/system/permissions/files/permissions_within_important_dirs/root_permissions_syslibrary_files/rule.yml -@@ -44,6 +44,7 @@ references: - srg: SRG-OS-000259-GPOS-00100 - stigid@ol8: OL08-00-010350 - stigid@rhel8: RHEL-08-010350 -+ stigid@rhel9: RHEL-09-232205 - stigid@sle12: SLES-12-010875 - stigid@sle15: SLES-15-010355 - stigid@ubuntu2004: UBTU-20-01430 -diff --git a/linux_os/guide/system/permissions/files/sysctl_fs_protected_hardlinks/rule.yml b/linux_os/guide/system/permissions/files/sysctl_fs_protected_hardlinks/rule.yml -index 710fc0bf69..ccb1b8ea45 100644 ---- a/linux_os/guide/system/permissions/files/sysctl_fs_protected_hardlinks/rule.yml -+++ b/linux_os/guide/system/permissions/files/sysctl_fs_protected_hardlinks/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000312-GPOS-00122,SRG-OS-000312-GPOS-00123,SRG-OS-000324-GPOS-00125 - stigid@ol8: OL08-00-010374 - stigid@rhel8: RHEL-08-010374 -+ stigid@rhel9: RHEL-09-213030 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="fs.protected_hardlinks", value="1") }}} - -diff --git a/linux_os/guide/system/permissions/files/sysctl_fs_protected_symlinks/rule.yml b/linux_os/guide/system/permissions/files/sysctl_fs_protected_symlinks/rule.yml -index 3b66b3c9b4..34ed37a004 100644 ---- a/linux_os/guide/system/permissions/files/sysctl_fs_protected_symlinks/rule.yml -+++ b/linux_os/guide/system/permissions/files/sysctl_fs_protected_symlinks/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000312-GPOS-00122,SRG-OS-000312-GPOS-00123,SRG-OS-000324-GPOS-00125 - stigid@ol8: OL08-00-010373 - stigid@rhel8: RHEL-08-010373 -+ stigid@rhel9: RHEL-09-213035 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="fs.protected_symlinks", value="1") }}} - -diff --git a/linux_os/guide/system/permissions/mounting/kernel_module_cramfs_disabled/rule.yml b/linux_os/guide/system/permissions/mounting/kernel_module_cramfs_disabled/rule.yml -index 664c7364e1..eab9bce8ce 100644 ---- a/linux_os/guide/system/permissions/mounting/kernel_module_cramfs_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/mounting/kernel_module_cramfs_disabled/rule.yml -@@ -50,6 +50,7 @@ references: - srg: SRG-OS-000095-GPOS-00049 - stigid@ol8: OL08-00-040025 - stigid@rhel8: RHEL-08-040025 -+ stigid@rhel9: RHEL-09-231195 - - {{{ complete_ocil_entry_module_disable(module="cramfs") }}} - -diff --git a/linux_os/guide/system/permissions/mounting/kernel_module_usb-storage_disabled/rule.yml b/linux_os/guide/system/permissions/mounting/kernel_module_usb-storage_disabled/rule.yml -index 144d855a0c..a517d2fa95 100644 ---- a/linux_os/guide/system/permissions/mounting/kernel_module_usb-storage_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/mounting/kernel_module_usb-storage_disabled/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-040080 - stigid@rhel7: RHEL-07-020100 - stigid@rhel8: RHEL-08-040080 -+ stigid@rhel9: RHEL-09-291010 - stigid@sle12: SLES-12-010580 - stigid@sle15: SLES-15-010480 - -diff --git a/linux_os/guide/system/permissions/mounting/service_autofs_disabled/rule.yml b/linux_os/guide/system/permissions/mounting/service_autofs_disabled/rule.yml -index 27f23dd297..f433c1f887 100644 ---- a/linux_os/guide/system/permissions/mounting/service_autofs_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/mounting/service_autofs_disabled/rule.yml -@@ -57,6 +57,7 @@ references: - stigid@ol8: OL08-00-040070 - stigid@rhel7: RHEL-07-020110 - stigid@rhel8: RHEL-08-040070 -+ stigid@rhel9: RHEL-09-231040 - stigid@sle12: SLES-12-010590 - stigid@sle15: SLES-15-010240 - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_boot_efi_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_boot_efi_nosuid/rule.yml -index c6901e86d8..6c33c8b27e 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_boot_efi_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_boot_efi_nosuid/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010572 - stigid@rhel8: RHEL-08-010572 -+ stigid@rhel9: RHEL-09-231105 - - platform: machine and uefi - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_boot_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_boot_nodev/rule.yml -index 9ac722d0ed..dd10c989ad 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_boot_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_boot_nodev/rule.yml -@@ -30,6 +30,7 @@ references: - nist: CM-7(a),CM-7(b),CM-6(a),AC-6,AC-6(1),MP-7 - nist-csf: PR.IP-1,PR.PT-2,PR.PT-3 - srg: SRG-OS-000368-GPOS-00154 -+ stigid@rhel9: RHEL-09-231095 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_boot_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_boot_nosuid/rule.yml -index 583dd2b60c..a9b24acb98 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_boot_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_boot_nosuid/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010571 - stigid@rhel8: RHEL-08-010571 -+ stigid@rhel9: RHEL-09-231100 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml -index 17d1273f92..0c28efb145 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml -@@ -49,6 +49,7 @@ references: - stigid@ol8: OL08-00-040120 - stigid@rhel7: RHEL-07-021024 - stigid@rhel8: RHEL-08-040120 -+ stigid@rhel9: RHEL-09-231110 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_noexec/rule.yml -index ea5701f9b3..7debed33da 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_noexec/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-040122 - stigid@rhel7: RHEL-07-021024 - stigid@rhel8: RHEL-08-040122 -+ stigid@rhel9: RHEL-09-231115 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml -index 808035e3a6..f8bf73b56b 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml -@@ -49,6 +49,7 @@ references: - stigid@ol8: OL08-00-040121 - stigid@rhel7: RHEL-07-021024 - stigid@rhel8: RHEL-08-040121 -+ stigid@rhel9: RHEL-09-231120 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_home_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_home_nodev/rule.yml -index d454139b42..ba5959a42b 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_home_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_home_nodev/rule.yml -@@ -41,6 +41,7 @@ references: - cis@ubuntu2004: 1.1.18 - cis@ubuntu2204: 1.1.7.2 - srg: SRG-OS-000368-GPOS-00154 -+ stigid@rhel9: RHEL-09-231045 - - platform: machine and mount[home] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_home_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_home_noexec/rule.yml -index bee3a60e87..d77f85065e 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_home_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_home_noexec/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010590 - stigid@rhel8: RHEL-08-010590 -+ stigid@rhel9: RHEL-09-231055 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_home_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_home_nosuid/rule.yml -index 5e42ac0a7e..85ec3a89bb 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_home_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_home_nosuid/rule.yml -@@ -43,10 +43,10 @@ references: - stigid@ol8: OL08-00-010570 - stigid@rhel7: RHEL-07-021000 - stigid@rhel8: RHEL-08-010570 -+ stigid@rhel9: RHEL-09-231050 - stigid@sle12: SLES-12-010790 - stigid@sle15: SLES-15-040140 - -- - {{{ complete_ocil_entry_mount_option("/home", "nosuid") }}} - - fixtext: |- -@@ -79,4 +79,3 @@ template: - vars: - mountoption: nosuid - {{% endif %}} -- -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_nodev_nonroot_local_partitions/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_nodev_nonroot_local_partitions/rule.yml -index a22d24b1a5..2a7213e901 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_nodev_nonroot_local_partitions/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_nodev_nonroot_local_partitions/rule.yml -@@ -48,6 +48,7 @@ references: - srg: SRG-OS-000368-GPOS-00154,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010580 - stigid@rhel8: RHEL-08-010580 -+ stigid@rhel9: RHEL-09-231200 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_nodev_removable_partitions/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_nodev_removable_partitions/rule.yml -index d06852da93..1ce7103350 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_nodev_removable_partitions/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_nodev_removable_partitions/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010600 - stigid@rhel8: RHEL-08-010600 -+ stigid@rhel9: RHEL-09-231085 - - platform: machine - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_noexec_removable_partitions/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_noexec_removable_partitions/rule.yml -index 75934b9d75..e6494f4870 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_noexec_removable_partitions/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_noexec_removable_partitions/rule.yml -@@ -43,6 +43,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010610 - stigid@rhel8: RHEL-08-010610 -+ stigid@rhel9: RHEL-09-231080 - - ocil_clause: 'removable media partitions are present' - -@@ -53,7 +54,7 @@ ocil: |- - in the output are not removable media. - - fixtext: |- -- Configure the "/etc/fstab" to use the "noexec" option on file systems that are associated with removable media. -+ Configure the "/etc/fstab" to use the "noexec" option on file systems that are associated with removable media. - - srg_requirement: '{{{ full_name }}} must prevent code from being executed on file systems that are used with removable media.' - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_nosuid_removable_partitions/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_nosuid_removable_partitions/rule.yml -index 2ae9f064c3..db9c65f36a 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_nosuid_removable_partitions/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_nosuid_removable_partitions/rule.yml -@@ -47,6 +47,7 @@ references: - stigid@ol8: OL08-00-010620 - stigid@rhel7: RHEL-07-021010 - stigid@rhel8: RHEL-08-010620 -+ stigid@rhel9: RHEL-09-231090 - stigid@sle12: SLES-12-010800 - stigid@sle15: SLES-15-040150 - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_tmp_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_tmp_nodev/rule.yml -index 105a4549dc..06a7dc18f3 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_tmp_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_tmp_nodev/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040123 - stigid@rhel8: RHEL-08-040123 -+ stigid@rhel9: RHEL-09-231125 - - platform: machine and mount[tmp] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_tmp_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_tmp_noexec/rule.yml -index d4105fd2be..5d8d9710fb 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_tmp_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_tmp_noexec/rule.yml -@@ -48,6 +48,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040125 - stigid@rhel8: RHEL-08-040125 -+ stigid@rhel9: RHEL-09-231130 - - platform: machine and mount[tmp] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_tmp_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_tmp_nosuid/rule.yml -index e8f8b86b68..b7b9fec923 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_tmp_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_tmp_nosuid/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040124 - stigid@rhel8: RHEL-08-040124 -+ stigid@rhel9: RHEL-09-231135 - - platform: machine and mount[tmp] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nodev/rule.yml -index 844f31d187..c89966261a 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nodev/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040129 - stigid@rhel8: RHEL-08-040129 -+ stigid@rhel9: RHEL-09-231160 - - platform: machine and mount[var-log-audit] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_noexec/rule.yml -index f5c55f7d49..98a7e9ad02 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_noexec/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040131 - stigid@rhel8: RHEL-08-040131 -+ stigid@rhel9: RHEL-09-231165 - - platform: machine and mount[var-log-audit] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nosuid/rule.yml -index 38c807ee5e..833e994701 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_audit_nosuid/rule.yml -@@ -35,6 +35,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040130 - stigid@rhel8: RHEL-08-040130 -+ stigid@rhel9: RHEL-09-231170 - - platform: machine and mount[var-log-audit] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_nodev/rule.yml -index b59aeba7f8..aae251d622 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_nodev/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040126 - stigid@rhel8: RHEL-08-040126 -+ stigid@rhel9: RHEL-09-231145 - - platform: machine and mount[var-log] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_noexec/rule.yml -index e3885b4974..132b09fd29 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_noexec/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040128 - stigid@rhel8: RHEL-08-040128 -+ stigid@rhel9: RHEL-09-231150 - - platform: machine and mount[var-log] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_log_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_log_nosuid/rule.yml -index c463963115..0744827b99 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_log_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_log_nosuid/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040127 - stigid@rhel8: RHEL-08-040127 -+ stigid@rhel9: RHEL-09-231155 - - platform: machine and mount[var-log] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_nodev/rule.yml -index d2723fd05f..eb57b5c017 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_nodev/rule.yml -@@ -33,6 +33,7 @@ references: - nist: CM-7(a),CM-7(b),CM-6(a),AC-6,AC-6(1),MP-7 - nist-csf: PR.IP-1,PR.PT-2,PR.PT-3 - srg: SRG-OS-000368-GPOS-00154 -+ stigid@rhel9: RHEL-09-231140 - - platform: machine and mount[var] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nodev/rule.yml -index 0496b5523c..b21666373b 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nodev/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nodev/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040132 - stigid@rhel8: RHEL-08-040132 -+ stigid@rhel9: RHEL-09-231175 - - platforms: - - machine and mount[var-tmp] -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_noexec/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_noexec/rule.yml -index 355ed84dde..3240796eb4 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_noexec/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_noexec/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040134 - stigid@rhel8: RHEL-08-040134 -+ stigid@rhel9: RHEL-09-231180 - - platform: machine and mount[var-tmp] - -diff --git a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nosuid/rule.yml -index 6a58626503..49b39bc061 100644 ---- a/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nosuid/rule.yml -+++ b/linux_os/guide/system/permissions/partitions/mount_option_var_tmp_nosuid/rule.yml -@@ -42,6 +42,7 @@ references: - srg: SRG-OS-000368-GPOS-00154 - stigid@ol8: OL08-00-040133 - stigid@rhel8: RHEL-08-040133 -+ stigid@rhel9: RHEL-09-231185 - - platform: machine and mount[var-tmp] - -diff --git a/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_backtraces/rule.yml b/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_backtraces/rule.yml -index a806796736..e8106e8366 100644 ---- a/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_backtraces/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_backtraces/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010675 - stigid@rhel8: RHEL-08-010675 -+ stigid@rhel9: RHEL-09-213085 - - ocil_clause: 'the "ProcessSizeMax" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned' - -diff --git a/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_storage/rule.yml b/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_storage/rule.yml -index 4206d067c7..c18c6eda96 100644 ---- a/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_storage/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/coredumps/coredump_disable_storage/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010674 - stigid@rhel8: RHEL-08-010674 -+ stigid@rhel9: RHEL-09-213090 - - ocil_clause: Storage is not set to none or is commented out and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned - -diff --git a/linux_os/guide/system/permissions/restrictions/coredumps/disable_users_coredumps/rule.yml b/linux_os/guide/system/permissions/restrictions/coredumps/disable_users_coredumps/rule.yml -index 4de1534fbc..2eca5e2037 100644 ---- a/linux_os/guide/system/permissions/restrictions/coredumps/disable_users_coredumps/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/coredumps/disable_users_coredumps/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010673 - stigid@rhel8: RHEL-08-010673 -+ stigid@rhel9: RHEL-09-213095 - - ocil_clause: 'the "core" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core"' - -diff --git a/linux_os/guide/system/permissions/restrictions/coredumps/service_systemd-coredump_disabled/rule.yml b/linux_os/guide/system/permissions/restrictions/coredumps/service_systemd-coredump_disabled/rule.yml -index 6d62d139a4..0072545f30 100644 ---- a/linux_os/guide/system/permissions/restrictions/coredumps/service_systemd-coredump_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/coredumps/service_systemd-coredump_disabled/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010672 - stigid@rhel8: RHEL-08-010672 -+ stigid@rhel9: RHEL-09-213100 - - ocil_clause: unit systemd-coredump.socket is not masked or running - -diff --git a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_exec_shield/rule.yml b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_exec_shield/rule.yml -index 4614843372..ab45d968b7 100644 ---- a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_exec_shield/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_exec_shield/rule.yml -@@ -47,6 +47,7 @@ references: - nist: SC-39,CM-6(a) - nist-csf: PR.PT-4 - srg: SRG-OS-000433-GPOS-00192 -+ stigid@rhel9: RHEL-09-213110 - - ocil_clause: 'ExecShield is not supported by the hardware, is not enabled, or has been disabled by the kernel configuration.' - -diff --git a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_kptr_restrict/rule.yml b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_kptr_restrict/rule.yml -index 367934b567..8f7a99d5ea 100644 ---- a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_kptr_restrict/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_kptr_restrict/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000132-GPOS-00067,SRG-OS-000433-GPOS-00192,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040283 - stigid@rhel8: RHEL-08-040283 -+ stigid@rhel9: RHEL-09-213025 - stigid@sle12: SLES-12-030320 - stigid@sle15: SLES-15-010540 - -diff --git a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_randomize_va_space/rule.yml b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_randomize_va_space/rule.yml -index 444d7b11c3..bc1cc99b78 100644 ---- a/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_randomize_va_space/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/enable_execshield_settings/sysctl_kernel_randomize_va_space/rule.yml -@@ -45,6 +45,7 @@ references: - stigid@ol8: OL08-00-010430 - stigid@rhel7: RHEL-07-040201 - stigid@rhel8: RHEL-08-010430 -+ stigid@rhel9: RHEL-09-213070 - stigid@sle12: SLES-12-030330 - stigid@sle15: SLES-15-010550 - stigid@ubuntu2004: UBTU-20-010448 -diff --git a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml -index 78c982211e..6a0befd506 100644 ---- a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml -@@ -31,6 +31,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000134-GPOS-00068 - stigid@ol8: OL08-00-010421 - stigid@rhel8: RHEL-08-010421 -+ stigid@rhel9: RHEL-09-212040 - - ocil_clause: 'page allocator poisoning is not enabled' - -diff --git a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml -index ea3560cecb..59c4c94ff5 100644 ---- a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml -@@ -31,6 +31,7 @@ references: - srg: SRG-OS-000433-GPOS-00192,SRG-OS-000134-GPOS-00068 - stigid@ol8: OL08-00-010423 - stigid@rhel8: RHEL-08-010423 -+ stigid@rhel9: RHEL-09-212045 - - ocil_clause: 'SLUB/SLAB poisoning is not enabled' - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_core_pattern/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_core_pattern/rule.yml -index e369854060..a4d5e4a191 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_core_pattern/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_core_pattern/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010671 - stigid@rhel8: RHEL-08-010671 -+ stigid@rhel9: RHEL-09-213040 - - ocil_clause: |- - the returned line does not have a value of "|/bin/false", or a line is not -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_dmesg_restrict/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_dmesg_restrict/rule.yml -index b7acaf1281..0000c38de4 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_dmesg_restrict/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_dmesg_restrict/rule.yml -@@ -31,6 +31,7 @@ references: - stigid@ol8: OL08-00-010375 - stigid@rhel7: RHEL-07-010375 - stigid@rhel8: RHEL-08-010375 -+ stigid@rhel9: RHEL-09-213010 - stigid@sle12: SLES-12-010375 - stigid@sle15: SLES-15-010375 - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_kexec_load_disabled/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_kexec_load_disabled/rule.yml -index 4e68361c2b..fa70fcd5c8 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_kexec_load_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_kexec_load_disabled/rule.yml -@@ -24,7 +24,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000366-GPOS-00153 - stigid@ol8: OL08-00-010372 - stigid@rhel8: RHEL-08-010372 -- -+ stigid@rhel9: RHEL-09-213020 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="kernel.kexec_load_disabled", value="1") }}} - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_perf_event_paranoid/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_perf_event_paranoid/rule.yml -index a39ff72eeb..ee2c1333d0 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_perf_event_paranoid/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_perf_event_paranoid/rule.yml -@@ -27,6 +27,7 @@ references: - srg: SRG-OS-000132-GPOS-00067,SRG-OS-000138-GPOS-00069,SRG-APP-000243-CTR-000600 - stigid@ol8: OL08-00-010376 - stigid@rhel8: RHEL-08-010376 -+ stigid@rhel9: RHEL-09-213015 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="kernel.perf_event_paranoid", value="2") }}} - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_unprivileged_bpf_disabled/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_unprivileged_bpf_disabled/rule.yml -index ca51c5534e..549caac664 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_unprivileged_bpf_disabled/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_unprivileged_bpf_disabled/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000132-GPOS-00067,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040281 - stigid@rhel8: RHEL-08-040281 -+ stigid@rhel9: RHEL-09-213075 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="kernel.unprivileged_bpf_disabled", value="1") }}} - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_yama_ptrace_scope/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_yama_ptrace_scope/rule.yml -index e03106c01d..1a9c419a0c 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_kernel_yama_ptrace_scope/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_kernel_yama_ptrace_scope/rule.yml -@@ -29,6 +29,7 @@ references: - srg: SRG-OS-000132-GPOS-00067,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040282 - stigid@rhel8: RHEL-08-040282 -+ stigid@rhel9: RHEL-09-213080 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="kernel.yama.ptrace_scope", value="1") }}} - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_net_core_bpf_jit_harden/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_net_core_bpf_jit_harden/rule.yml -index 323fef1e6e..791f714516 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_net_core_bpf_jit_harden/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_net_core_bpf_jit_harden/rule.yml -@@ -26,6 +26,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040286 - stigid@rhel8: RHEL-08-040286 -+ stigid@rhel9: RHEL-09-251045 - - {{{ complete_ocil_entry_sysctl_option_value(sysctl="net.core.bpf_jit_harden", value="2") }}} - -diff --git a/linux_os/guide/system/permissions/restrictions/sysctl_user_max_user_namespaces/rule.yml b/linux_os/guide/system/permissions/restrictions/sysctl_user_max_user_namespaces/rule.yml -index 2932ebe235..9713bd0cbd 100644 ---- a/linux_os/guide/system/permissions/restrictions/sysctl_user_max_user_namespaces/rule.yml -+++ b/linux_os/guide/system/permissions/restrictions/sysctl_user_max_user_namespaces/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040284 - stigid@rhel8: RHEL-08-040284 -+ stigid@rhel9: RHEL-09-213105 - - ocil: | - Verify that {{{ full_name }}} disables the use of user namespaces with the following commands: -diff --git a/linux_os/guide/system/selinux/package_policycoreutils-python-utils_installed/rule.yml b/linux_os/guide/system/selinux/package_policycoreutils-python-utils_installed/rule.yml -index eb5f39b451..308655d120 100644 ---- a/linux_os/guide/system/selinux/package_policycoreutils-python-utils_installed/rule.yml -+++ b/linux_os/guide/system/selinux/package_policycoreutils-python-utils_installed/rule.yml -@@ -19,6 +19,7 @@ identifiers: - - references: - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-431030 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/selinux/package_policycoreutils_installed/rule.yml b/linux_os/guide/system/selinux/package_policycoreutils_installed/rule.yml -index 71e5c70a68..f5b0cf4ed2 100644 ---- a/linux_os/guide/system/selinux/package_policycoreutils_installed/rule.yml -+++ b/linux_os/guide/system/selinux/package_policycoreutils_installed/rule.yml -@@ -33,6 +33,7 @@ references: - srg: SRG-OS-000480-GPOS-00227,SRG-OS-000134-GPOS-00068 - stigid@ol8: OL08-00-010171 - stigid@rhel8: RHEL-08-010171 -+ stigid@rhel9: RHEL-09-431025 - - ocil_clause: 'the policycoreutils package is not installed' - -diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml -index 7065c1eb9f..36b3f79aba 100644 ---- a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml -+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml -@@ -41,6 +41,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-020900 - stigid@rhel7: RHEL-07-020900 -+ stigid@rhel9: RHEL-09-232260 - - ocil_clause: 'there is output' - -diff --git a/linux_os/guide/system/selinux/selinux_policytype/rule.yml b/linux_os/guide/system/selinux/selinux_policytype/rule.yml -index d84bae70e4..f6a2e5dd8c 100644 ---- a/linux_os/guide/system/selinux/selinux_policytype/rule.yml -+++ b/linux_os/guide/system/selinux/selinux_policytype/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-010450 - stigid@rhel7: RHEL-07-020220 - stigid@rhel8: RHEL-08-010450 -+ stigid@rhel9: RHEL-09-431015 - - ocil_clause: 'the loaded policy name is not "{{{ xccdf_value("var_selinux_policy_name") }}}"' - -diff --git a/linux_os/guide/system/selinux/selinux_state/rule.yml b/linux_os/guide/system/selinux/selinux_state/rule.yml -index 8a67f6cae9..fdef693b8c 100644 ---- a/linux_os/guide/system/selinux/selinux_state/rule.yml -+++ b/linux_os/guide/system/selinux/selinux_state/rule.yml -@@ -51,6 +51,7 @@ references: - stigid@ol8: OL08-00-010170 - stigid@rhel7: RHEL-07-020210 - stigid@rhel8: RHEL-08-010170 -+ stigid@rhel9: RHEL-09-431010 - - ocil_clause: 'SELINUX is not set to enforcing' - -diff --git a/linux_os/guide/system/software/disk_partitioning/encrypt_partitions/rule.yml b/linux_os/guide/system/software/disk_partitioning/encrypt_partitions/rule.yml -index a7b2c5bcc0..34dc1b0c8c 100644 ---- a/linux_os/guide/system/software/disk_partitioning/encrypt_partitions/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/encrypt_partitions/rule.yml -@@ -78,6 +78,7 @@ references: - srg: SRG-OS-000405-GPOS-00184,SRG-OS-000185-GPOS-00079,SRG-OS-000404-GPOS-00183 - stigid@ol8: OL08-00-010030 - stigid@rhel8: RHEL-08-010030 -+ stigid@rhel9: RHEL-09-231190 - stigid@sle12: SLES-12-010450 - stigid@sle15: SLES-15-010330 - stigid@ubuntu2004: UBTU-20-010414 -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_home/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_home/rule.yml -index 92fb555537..39cf4ae4fe 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_home/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_home/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-010800 - stigid@rhel7: RHEL-07-021310 - stigid@rhel8: RHEL-08-010800 -+ stigid@rhel9: RHEL-09-231010 - stigid@sle12: SLES-12-010850 - stigid@sle15: SLES-15-040200 - -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_tmp/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_tmp/rule.yml -index 1fd3af83a1..43b1c12e2f 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_tmp/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_tmp/rule.yml -@@ -45,6 +45,7 @@ references: - stigid@ol8: OL08-00-010543 - stigid@rhel7: RHEL-07-021340 - stigid@rhel8: RHEL-08-010543 -+ stigid@rhel9: RHEL-09-231015 - - {{{ complete_ocil_entry_separate_partition(part="/tmp") }}} - -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_var/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_var/rule.yml -index 9f87a00281..753c2d0021 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_var/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_var/rule.yml -@@ -47,6 +47,7 @@ references: - stigid@ol8: OL08-00-010540 - stigid@rhel7: RHEL-07-021320 - stigid@rhel8: RHEL-08-010540 -+ stigid@rhel9: RHEL-09-231020 - stigid@sle12: SLES-12-010860 - stigid@sle15: SLES-15-040210 - -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_var_log/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_var_log/rule.yml -index e2f69fef81..c5790aab1d 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_var_log/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_var_log/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010541 - stigid@rhel8: RHEL-08-010541 -+ stigid@rhel9: RHEL-09-231025 - - {{{ complete_ocil_entry_separate_partition(part="/var/log") }}} - -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_var_log_audit/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_var_log_audit/rule.yml -index 9758b06251..a7c19fca3f 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_var_log_audit/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_var_log_audit/rule.yml -@@ -53,6 +53,7 @@ references: - stigid@ol8: OL08-00-010542 - stigid@rhel7: RHEL-07-021330 - stigid@rhel8: RHEL-08-010542 -+ stigid@rhel9: RHEL-09-231030 - stigid@sle12: SLES-12-010870 - stigid@sle15: SLES-15-030810 - -diff --git a/linux_os/guide/system/software/disk_partitioning/partition_for_var_tmp/rule.yml b/linux_os/guide/system/software/disk_partitioning/partition_for_var_tmp/rule.yml -index 65cde9418e..a5f203a1ac 100644 ---- a/linux_os/guide/system/software/disk_partitioning/partition_for_var_tmp/rule.yml -+++ b/linux_os/guide/system/software/disk_partitioning/partition_for_var_tmp/rule.yml -@@ -39,6 +39,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010544 - stigid@rhel8: RHEL-08-010544 -+ stigid@rhel9: RHEL-09-231035 - - {{{ complete_ocil_entry_separate_partition(part="/var/tmp") }}} - -diff --git a/linux_os/guide/system/software/gnome/dconf_db_up_to_date/rule.yml b/linux_os/guide/system/software/gnome/dconf_db_up_to_date/rule.yml -index 814a0103c5..2c59561849 100644 ---- a/linux_os/guide/system/software/gnome/dconf_db_up_to_date/rule.yml -+++ b/linux_os/guide/system/software/gnome/dconf_db_up_to_date/rule.yml -@@ -36,6 +36,9 @@ references: - pcidss: Req-6.2 - pcidss4: "6.3.3" - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-271090 -+ stigid@sle12: SLES-12-010040 -+ stigid@sle15: SLES-15-010090 - - ocil_clause: 'The system-wide dconf databases are up-to-date with regards to respective keyfiles' - -diff --git a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_restart_shutdown/rule.yml b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_restart_shutdown/rule.yml -index b5bf2b9984..420150667d 100644 ---- a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_restart_shutdown/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_restart_shutdown/rule.yml -@@ -43,6 +43,7 @@ references: - nist: CM-6(a),AC-6(1),CM-7(b) - nist-csf: PR.AC-4,PR.DS-5 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-271095,RHEL-09-271100 - - ocil_clause: 'disable-restart-buttons has not been configured or is not disabled' - -diff --git a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_user_list/rule.yml b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_user_list/rule.yml -index 50a8651abe..5957ae82f4 100644 ---- a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_user_list/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_disable_user_list/rule.yml -@@ -49,6 +49,7 @@ references: - stigid@ol8: OL08-00-020032 - stigid@rhel7: RHEL-07-010063 - stigid@rhel8: RHEL-08-020032 -+ stigid@rhel9: RHEL-09-271115 - - ocil_clause: 'disable-user-list has not been configured or is not disabled' - -diff --git a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_lock_screen_on_smartcard_removal/rule.yml b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_lock_screen_on_smartcard_removal/rule.yml -index 3bdd2128d9..fe8fa9d689 100644 ---- a/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_lock_screen_on_smartcard_removal/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_login_screen/dconf_gnome_lock_screen_on_smartcard_removal/rule.yml -@@ -34,6 +34,7 @@ references: - srg: SRG-OS-000028-GPOS-00009,SRG-OS-000030-GPOS-00011 - stigid@ol8: OL08-00-020050 - stigid@rhel8: RHEL-08-020050 -+ stigid@rhel9: RHEL-09-271045,RHEL-09-271050 - - ocil_clause: 'removal-action has not been configured' - -diff --git a/linux_os/guide/system/software/gnome/gnome_login_screen/gnome_gdm_disable_automatic_login/rule.yml b/linux_os/guide/system/software/gnome/gnome_login_screen/gnome_gdm_disable_automatic_login/rule.yml -index cbfcb9c18a..9efe162f9d 100644 ---- a/linux_os/guide/system/software/gnome/gnome_login_screen/gnome_gdm_disable_automatic_login/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_login_screen/gnome_gdm_disable_automatic_login/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-010820 - stigid@rhel7: RHEL-07-010440 - stigid@rhel8: RHEL-08-010820 -+ stigid@rhel9: RHEL-09-271040 - - ocil_clause: 'GDM allows users to automatically login' - -diff --git a/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_automount_open/rule.yml b/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_automount_open/rule.yml -index 429314038a..4f9addce4b 100644 ---- a/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_automount_open/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_automount_open/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-020111 - stigid@rhel7: RHEL-07-020111 -+ stigid@rhel9: RHEL-09-271020,RHEL-09-271025 - - ocil_clause: 'GNOME automounting is not disabled' - -diff --git a/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_autorun/rule.yml b/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_autorun/rule.yml -index b7662be6f8..74ee302023 100644 ---- a/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_autorun/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_media_settings/dconf_gnome_disable_autorun/rule.yml -@@ -48,6 +48,7 @@ references: - srg: SRG-OS-000114-GPOS-00059,SRG-OS-000378-GPOS-00163,SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-020111 - stigid@rhel7: RHEL-07-020111 -+ stigid@rhel9: RHEL-09-271030,RHEL-09-271035 - - ocil_clause: 'GNOME autorun is not disabled' - -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_idle_delay/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_idle_delay/rule.yml -index 58488e8aa1..eeb849c86c 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_idle_delay/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_idle_delay/rule.yml -@@ -53,6 +53,7 @@ references: - stigid@ol8: OL08-00-020060 - stigid@rhel7: RHEL-07-010070 - stigid@rhel8: RHEL-08-020060 -+ stigid@rhel9: RHEL-09-271065 - stigid@sle12: SLES-12-010080 - stigid@sle15: SLES-15-010120 - -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_delay/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_delay/rule.yml -index 99c897f17f..f8b2a08de9 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_delay/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_delay/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-020031 - stigid@rhel7: RHEL-07-010110 - stigid@rhel8: RHEL-08-020031 -+ stigid@rhel9: RHEL-09-271075 - - ocil_clause: 'the screensaver lock delay is missing, or is set to a value greater than {{{ xccdf_value("var_screensaver_lock_delay") }}}' - -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_enabled/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_enabled/rule.yml -index 8a86e38061..43b8a1c19f 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_enabled/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_lock_enabled/rule.yml -@@ -59,6 +59,7 @@ references: - stigid@ol8: OL08-00-020030 - stigid@rhel7: RHEL-07-010060 - stigid@rhel8: RHEL-08-020030 -+ stigid@rhel9: RHEL-09-271060,RHEL-09-271055 - stigid@sle12: SLES-12-010060 - stigid@sle15: SLES-15-010100 - stigid@ubuntu2004: UBTU-20-010004 -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_mode_blank/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_mode_blank/rule.yml -index 48735e16a9..7b305f37bb 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_mode_blank/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_mode_blank/rule.yml -@@ -68,6 +68,7 @@ references: - pcidss: Req-8.1.8 - pcidss4: "8.2.8" - srg: SRG-OS-000031-GPOS-00012 -+ stigid@rhel9: RHEL-09-271085 - stigid@sle12: SLES-12-010100 - stigid@sle15: SLES-15-010140 - -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_user_locks/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_user_locks/rule.yml -index a1169934fd..723dfb0967 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_user_locks/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_screensaver_user_locks/rule.yml -@@ -43,6 +43,7 @@ references: - stigid@ol8: OL08-00-020080 - stigid@rhel7: RHEL-07-010081 - stigid@rhel8: RHEL-08-020080 -+ stigid@rhel9: RHEL-09-271080 - - ocil_clause: 'GNOME3 session settings are not locked or configured properly' - -diff --git a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_session_idle_user_locks/rule.yml b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_session_idle_user_locks/rule.yml -index 762e8c789c..7f0a52f333 100644 ---- a/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_session_idle_user_locks/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_screen_locking/dconf_gnome_session_idle_user_locks/rule.yml -@@ -47,6 +47,9 @@ references: - stigid@ol8: OL08-00-020081 - stigid@rhel7: RHEL-07-010082 - stigid@rhel8: RHEL-08-020081 -+ stigid@rhel9: RHEL-09-271070 -+ stigid@sle12: SLES-12-010080 -+ stigid@sle15: SLES-15-010120 - - ocil_clause: 'idle-delay is not locked' - -diff --git a/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml b/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml -index 1f04e0af05..8889ac6c0d 100644 ---- a/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml -+++ b/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-040171 - stigid@rhel7: RHEL-07-020231 - stigid@rhel8: RHEL-08-040171 -+ stigid@rhel9: RHEL-09-271105,RHEL-09-271110 - stigid@ubuntu2004: UBTU-20-010459 - - ocil_clause: 'GNOME3 is configured to reboot when Ctrl-Alt-Del is pressed' -diff --git a/linux_os/guide/system/software/integrity/certified-vendor/installed_OS_is_vendor_supported/rule.yml b/linux_os/guide/system/software/integrity/certified-vendor/installed_OS_is_vendor_supported/rule.yml -index 234eb42b84..53d18dbef2 100644 ---- a/linux_os/guide/system/software/integrity/certified-vendor/installed_OS_is_vendor_supported/rule.yml -+++ b/linux_os/guide/system/software/integrity/certified-vendor/installed_OS_is_vendor_supported/rule.yml -@@ -50,6 +50,7 @@ references: - stigid@ol8: OL08-00-010000 - stigid@rhel7: RHEL-07-020250 - stigid@rhel8: RHEL-08-010000 -+ stigid@rhel9: RHEL-09-211010 - stigid@sle12: SLES-12-010000 - stigid@sle15: SLES-15-010000 - -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_bind_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_bind_crypto_policy/rule.yml -index cafd1940a6..0f9b14f044 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_bind_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_bind_crypto_policy/rule.yml -@@ -32,6 +32,7 @@ references: - srg: SRG-OS-000423-GPOS-00187,SRG-OS-000426-GPOS-00190 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-672050 - - ocil_clause: |- - BIND is installed and the BIND config file doesn't contain the -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_crypto_policy/rule.yml -index d1aec77447..c592a41fbb 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_crypto_policy/rule.yml -@@ -72,6 +72,7 @@ references: - srg: SRG-OS-000396-GPOS-00176,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-671010,RHEL-09-672030,RHEL-09-672045 - - ocil_clause: 'cryptographic policy is not configured or is configured incorrectly' - -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_kerberos_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_kerberos_crypto_policy/rule.yml -index 094beadb3a..5d761430b2 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_kerberos_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_kerberos_crypto_policy/rule.yml -@@ -30,6 +30,7 @@ references: - srg: SRG-OS-000120-GPOS-00061 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-672025 - - ocil_clause: 'the symlink does not exist or points to a different target' - -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_libreswan_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_libreswan_crypto_policy/rule.yml -index 5c8655c921..84d2e1dc01 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_libreswan_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_libreswan_crypto_policy/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000033-GPOS-00014 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-671020 - - ocil_clause: |- - the "IPsec" service is active and the ipsec configuration file does not contain does not contain include /etc/crypto-policies/back-ends/libreswan.config -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml -index 8cf86b7390..37d5ff6d1c 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml -@@ -47,6 +47,7 @@ references: - srg: SRG-OS-000250-GPOS-00093 - stigid@ol8: OL08-00-010293 - stigid@rhel8: RHEL-08-010293 -+ stigid@rhel9: RHEL-09-672035 - - ocil_clause: |- - the OpenSSL config file doesn't contain the whole section, -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_tls_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_tls_crypto_policy/rule.yml -index 767481d1eb..e937e9f12f 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_tls_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_tls_crypto_policy/rule.yml -@@ -46,6 +46,7 @@ references: - srg: SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174 - stigid@ol8: OL08-00-010294 - stigid@rhel8: RHEL-08-010294 -+ stigid@rhel9: RHEL-09-672040 - - ocil_clause: 'cryptographic policy for openssl is not configured or is configured incorrectly' - -diff --git a/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml -index 2373c03c3a..d87e647cfe 100644 ---- a/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml -@@ -38,6 +38,7 @@ references: - srg: SRG-OS-000250-GPOS-00093 - stigid@ol8: OL08-00-010287 - stigid@rhel8: RHEL-08-010287 -+ stigid@rhel9: RHEL-09-255055 - - ocil_clause: 'the CRYPTO_POLICY variable is set or is not commented out in the /etc/sysconfig/sshd' - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_openssh_conf_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_openssh_conf_crypto_policy/rule.yml -index 00bbcf955a..d25cadb02d 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_openssh_conf_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_openssh_conf_crypto_policy/rule.yml -@@ -33,6 +33,7 @@ references: - srg: SRG-OS-000033-GPOS-00014,SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174,SRG-OS-000423-GPOS-00187 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-255060 - - ocil_clause: 'Crypto Policy for OpenSSH client is not configured correctly' - -diff --git a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/rule.yml -index c4edc79bff..9f9fb9f2ce 100644 ---- a/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/harden_sshd_ciphers_opensshserver_conf_crypto_policy/rule.yml -@@ -33,6 +33,7 @@ references: - srg: SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093 - stigid@ol8: OL08-00-010291 - stigid@rhel8: RHEL-08-010291 -+ stigid@rhel9: RHEL-09-255065 - - ocil_clause: 'Crypto Policy for OpenSSH Server is not configured correctly' - -diff --git a/linux_os/guide/system/software/integrity/crypto/package_crypto-policies_installed/rule.yml b/linux_os/guide/system/software/integrity/crypto/package_crypto-policies_installed/rule.yml -index 68dc260a8d..75fa8730d0 100644 ---- a/linux_os/guide/system/software/integrity/crypto/package_crypto-policies_installed/rule.yml -+++ b/linux_os/guide/system/software/integrity/crypto/package_crypto-policies_installed/rule.yml -@@ -21,6 +21,7 @@ identifiers: - references: - ospp: FCS_COP.1(1),FCS_COP.1(2),FCS_COP.1(3),FCS_COP.1(4),FCS_CKM.1,FCS_CKM.2,FCS_TLSC_EXT.1 - srg: SRG-OS-000396-GPOS-00176,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174 -+ stigid@rhel9: RHEL-09-672010 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/agent_mfetpd_running/rule.yml b/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/agent_mfetpd_running/rule.yml -index c0e75cb0b4..c0613116d4 100644 ---- a/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/agent_mfetpd_running/rule.yml -+++ b/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/agent_mfetpd_running/rule.yml -@@ -28,6 +28,7 @@ references: - stigid@ol8: OL08-00-010001 - stigid@rhel7: RHEL-07-020019 - stigid@rhel8: RHEL-08-010001 -+ stigid@rhel9: RHEL-09-211025 - - ocil_clause: 'virus scanning software is not running' - -diff --git a/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/package_mcafeetp_installed/rule.yml b/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/package_mcafeetp_installed/rule.yml -index ef172b86b7..85a3c55835 100644 ---- a/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/package_mcafeetp_installed/rule.yml -+++ b/linux_os/guide/system/software/integrity/endpoint_security_software/mcafee_security_software/mcafee_endpoint_security_software/package_mcafeetp_installed/rule.yml -@@ -36,6 +36,7 @@ references: - stigid@ol8: OL08-00-010001 - stigid@rhel7: RHEL-07-020019 - stigid@rhel8: RHEL-08-010001 -+ stigid@rhel9: RHEL-09-211025 - stigid@ubuntu2004: UBTU-20-010415 - - ocil_clause: 'the package is not installed' -diff --git a/linux_os/guide/system/software/integrity/fips/enable_dracut_fips_module/rule.yml b/linux_os/guide/system/software/integrity/fips/enable_dracut_fips_module/rule.yml -index 62cfc0d6a6..d6a17c21f1 100644 ---- a/linux_os/guide/system/software/integrity/fips/enable_dracut_fips_module/rule.yml -+++ b/linux_os/guide/system/software/integrity/fips/enable_dracut_fips_module/rule.yml -@@ -32,6 +32,7 @@ references: - srg: SRG-OS-000478-GPOS-00223 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-671010 - - ocil_clause: 'the Dracut FIPS module is not enabled' - -diff --git a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/rule.yml b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/rule.yml -index c6e9662022..e8abdf67d6 100644 ---- a/linux_os/guide/system/software/integrity/fips/enable_fips_mode/rule.yml -+++ b/linux_os/guide/system/software/integrity/fips/enable_fips_mode/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000478-GPOS-00223,SRG-OS-000396-GPOS-00176 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-671010 - - ocil_clause: 'FIPS mode is not enabled' - -diff --git a/linux_os/guide/system/software/integrity/fips/sysctl_crypto_fips_enabled/rule.yml b/linux_os/guide/system/software/integrity/fips/sysctl_crypto_fips_enabled/rule.yml -index 2aafe35d7e..2c42b62630 100644 ---- a/linux_os/guide/system/software/integrity/fips/sysctl_crypto_fips_enabled/rule.yml -+++ b/linux_os/guide/system/software/integrity/fips/sysctl_crypto_fips_enabled/rule.yml -@@ -36,6 +36,7 @@ references: - srg: SRG-OS-000033-GPOS-00014,SRG-OS-000125-GPOS-00065,SRG-OS-000250-GPOS-00093,SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174,SRG-OS-000396-GPOS-00176,SRG-OS-000423-GPOS-00187,SRG-OS-000478-GPOS-00223 - stigid@ol8: OL08-00-010020 - stigid@rhel8: RHEL-08-010020 -+ stigid@rhel9: RHEL-09-671010 - - ocil_clause: 'crypto.fips_enabled is not 1' - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_check_audit_tools/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_check_audit_tools/rule.yml -index 4d786f01b3..79a0cdeffd 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_check_audit_tools/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_check_audit_tools/rule.yml -@@ -45,6 +45,7 @@ references: - srg: SRG-OS-000278-GPOS-00108 - stigid@ol8: OL08-00-030650 - stigid@rhel8: RHEL-08-030650 -+ stigid@rhel9: RHEL-09-651025 - stigid@sle12: SLES-12-010540 - stigid@sle15: SLES-15-030630 - stigid@ubuntu2004: UBTU-20-010205 -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_periodic_cron_checking/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_periodic_cron_checking/rule.yml -index 123e0ebf23..8135d0bb13 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_periodic_cron_checking/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_periodic_cron_checking/rule.yml -@@ -68,6 +68,7 @@ references: - srg: SRG-OS-000363-GPOS-00150,SRG-OS-000446-GPOS-00200,SRG-OS-000447-GPOS-00201 - stigid@ol7: OL07-00-020030 - stigid@rhel7: RHEL-07-020030 -+ stigid@rhel9: RHEL-09-651015 - stigid@sle12: SLES-12-010500 - stigid@sle15: SLES-15-010420 - stigid@ubuntu2004: UBTU-20-010074 -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_scan_notification/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_scan_notification/rule.yml -index 8ba2e20674..ac1f1452b6 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_scan_notification/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_scan_notification/rule.yml -@@ -50,6 +50,7 @@ references: - stigid@ol8: OL08-00-010360 - stigid@rhel7: RHEL-07-020040 - stigid@rhel8: RHEL-08-010360 -+ stigid@rhel9: RHEL-09-651015 - stigid@sle12: SLES-12-010510 - stigid@sle15: SLES-15-010570 - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_use_fips_hashes/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_use_fips_hashes/rule.yml -index b6b7b17b2f..8b880c9f2f 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_use_fips_hashes/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_use_fips_hashes/rule.yml -@@ -37,6 +37,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-021620 - stigid@rhel7: RHEL-07-021620 -+ stigid@rhel9: RHEL-09-651020 - - ocil_clause: 'the sha512 option is missing or not added to the correct ruleset' - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_acls/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_acls/rule.yml -index acf5996244..6e2a50eb89 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_acls/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_acls/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-040310 - stigid@rhel7: RHEL-07-021600 - stigid@rhel8: RHEL-08-040310 -+ stigid@rhel9: RHEL-09-651030 - stigid@sle12: SLES-12-010520 - stigid@sle15: SLES-15-040040 - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_ext_attributes/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_ext_attributes/rule.yml -index 1617182762..ab1435f534 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_ext_attributes/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/aide_verify_ext_attributes/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-040300 - stigid@rhel7: RHEL-07-021610 - stigid@rhel8: RHEL-08-040300 -+ stigid@rhel9: RHEL-09-651035 - stigid@sle12: SLES-12-010530 - stigid@sle15: SLES-15-040050 - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_group_ownership/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_group_ownership/rule.yml -index 7cb7eb36d4..d8e5c16528 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_group_ownership/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_group_ownership/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000258-GPOS-00099 - stigid@ol8: OL08-00-030640 - stigid@rhel8: RHEL-08-030640 -+ stigid@rhel9: RHEL-09-232225 - - ocil_clause: 'any audit tools are not group-owned by root' - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_ownership/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_ownership/rule.yml -index 077a39e0e4..04f3e40e9d 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_ownership/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_ownership/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000258-GPOS-00099 - stigid@ol8: OL08-00-030630 - stigid@rhel8: RHEL-08-030630 -+ stigid@rhel9: RHEL-09-232220 - - ocil_clause: 'any audit tools are not owned by root' - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_permissions/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_permissions/rule.yml -index d31eb6e936..460ee52d75 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_permissions/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/file_audit_tools_permissions/rule.yml -@@ -28,6 +28,7 @@ references: - srg: SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000258-GPOS-00099 - stigid@ol8: OL08-00-030620 - stigid@rhel8: RHEL-08-030620 -+ stigid@rhel9: RHEL-09-232035 - - ocil_clause: 'any of these files have more permissive permissions than 0755' - -diff --git a/linux_os/guide/system/software/integrity/software-integrity/aide/package_aide_installed/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/aide/package_aide_installed/rule.yml -index 6e9b2554a7..eb09388de6 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/aide/package_aide_installed/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/aide/package_aide_installed/rule.yml -@@ -46,6 +46,7 @@ references: - stigid@ol8: OL08-00-010359 - stigid@rhel7: RHEL-07-020029 - stigid@rhel8: RHEL-08-010359 -+ stigid@rhel9: RHEL-09-651010 - stigid@sle12: SLES-12-010499 - stigid@sle15: SLES-15-010419 - stigid@ubuntu2004: UBTU-20-010450 -diff --git a/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_hashes/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_hashes/rule.yml -index 1706d789ad..3472f117b5 100644 ---- a/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_hashes/rule.yml -+++ b/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_hashes/rule.yml -@@ -59,6 +59,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol7: OL07-00-010020 - stigid@rhel7: RHEL-07-010020 -+ stigid@rhel9: RHEL-09-214030 - - ocil_clause: 'there is output' - -diff --git a/linux_os/guide/system/software/sudo/package_sudo_installed/rule.yml b/linux_os/guide/system/software/sudo/package_sudo_installed/rule.yml -index 4652a0922d..86335e8723 100644 ---- a/linux_os/guide/system/software/sudo/package_sudo_installed/rule.yml -+++ b/linux_os/guide/system/software/sudo/package_sudo_installed/rule.yml -@@ -38,6 +38,7 @@ references: - ospp: FMT_MOF_EXT.1 - pcidss4: "10.2.1.5" - srg: SRG-OS-000324-GPOS-00125 -+ stigid@rhel9: RHEL-09-432010 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml b/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml -index 4408d610eb..553370c115 100644 ---- a/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml -+++ b/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-010381 - stigid@rhel7: RHEL-07-010350 - stigid@rhel8: RHEL-08-010381 -+ stigid@rhel9: RHEL-09-432025 - stigid@sle12: SLES-12-010110 - stigid@sle15: SLES-15-010450 - -diff --git a/linux_os/guide/system/software/sudo/sudo_remove_nopasswd/rule.yml b/linux_os/guide/system/software/sudo/sudo_remove_nopasswd/rule.yml -index 32e8a1bef5..1f1aba0f49 100644 ---- a/linux_os/guide/system/software/sudo/sudo_remove_nopasswd/rule.yml -+++ b/linux_os/guide/system/software/sudo/sudo_remove_nopasswd/rule.yml -@@ -40,6 +40,7 @@ references: - stigid@ol8: OL08-00-010380 - stigid@rhel7: RHEL-07-010340 - stigid@rhel8: RHEL-08-010380 -+ stigid@rhel9: RHEL-09-611085 - stigid@sle12: SLES-12-010110 - stigid@sle15: SLES-15-010450 - -diff --git a/linux_os/guide/system/software/sudo/sudo_require_reauthentication/rule.yml b/linux_os/guide/system/software/sudo/sudo_require_reauthentication/rule.yml -index 78ee258689..5de52cbedb 100644 ---- a/linux_os/guide/system/software/sudo/sudo_require_reauthentication/rule.yml -+++ b/linux_os/guide/system/software/sudo/sudo_require_reauthentication/rule.yml -@@ -42,6 +42,7 @@ references: - stigid@ol8: OL08-00-010384 - stigid@rhel7: RHEL-07-010343 - stigid@rhel8: RHEL-08-010384 -+ stigid@rhel9: RHEL-09-432015 - stigid@sle12: SLES-12-010113 - stigid@sle15: SLES-15-020102 - -diff --git a/linux_os/guide/system/software/sudo/sudo_restrict_privilege_elevation_to_authorized/rule.yml b/linux_os/guide/system/software/sudo/sudo_restrict_privilege_elevation_to_authorized/rule.yml -index b90f566abd..4999f30d76 100644 ---- a/linux_os/guide/system/software/sudo/sudo_restrict_privilege_elevation_to_authorized/rule.yml -+++ b/linux_os/guide/system/software/sudo/sudo_restrict_privilege_elevation_to_authorized/rule.yml -@@ -35,6 +35,7 @@ references: - stigid@ol8: OL08-00-010382 - stigid@rhel7: RHEL-07-010341 - stigid@rhel8: RHEL-08-010382 -+ stigid@rhel9: RHEL-09-432030 - stigid@sle12: SLES-12-010111 - stigid@sle15: SLES-15-020101 - -diff --git a/linux_os/guide/system/software/sudo/sudoers_validate_passwd/rule.yml b/linux_os/guide/system/software/sudo/sudoers_validate_passwd/rule.yml -index bd9d939471..ef6bef6a44 100644 ---- a/linux_os/guide/system/software/sudo/sudoers_validate_passwd/rule.yml -+++ b/linux_os/guide/system/software/sudo/sudoers_validate_passwd/rule.yml -@@ -39,6 +39,7 @@ references: - stigid@ol8: OL08-00-010383 - stigid@rhel7: RHEL-07-010342 - stigid@rhel8: RHEL-08-010383 -+ stigid@rhel9: RHEL-09-432020 - stigid@sle12: SLES-12-010112 - stigid@sle15: SLES-15-020103 - -diff --git a/linux_os/guide/system/software/system-tools/package_gnutls-utils_installed/rule.yml b/linux_os/guide/system/software/system-tools/package_gnutls-utils_installed/rule.yml -index 7b43f345fe..72322dc724 100644 ---- a/linux_os/guide/system/software/system-tools/package_gnutls-utils_installed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_gnutls-utils_installed/rule.yml -@@ -23,6 +23,7 @@ identifiers: - references: - ospp: FIA_X509_EXT.1,FIA_X509_EXT.2 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-215080 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/system-tools/package_gssproxy_removed/rule.yml b/linux_os/guide/system/software/system-tools/package_gssproxy_removed/rule.yml -index 4a5481118c..a7e8d3b523 100644 ---- a/linux_os/guide/system/software/system-tools/package_gssproxy_removed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_gssproxy_removed/rule.yml -@@ -22,6 +22,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040370 - stigid@rhel8: RHEL-08-040370 -+ stigid@rhel9: RHEL-09-215045 - - {{{ complete_ocil_entry_package(package="gssproxy") }}} - -diff --git a/linux_os/guide/system/software/system-tools/package_iprutils_removed/rule.yml b/linux_os/guide/system/software/system-tools/package_iprutils_removed/rule.yml -index 8986513f28..01e401020a 100644 ---- a/linux_os/guide/system/software/system-tools/package_iprutils_removed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_iprutils_removed/rule.yml -@@ -23,6 +23,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040380 - stigid@rhel8: RHEL-08-040380 -+ stigid@rhel9: RHEL-09-215050 - - {{{ complete_ocil_entry_package(package="iprutils") }}} - -diff --git a/linux_os/guide/system/software/system-tools/package_nss-tools_installed/rule.yml b/linux_os/guide/system/software/system-tools/package_nss-tools_installed/rule.yml -index a6bed84a66..82c45c0b9e 100644 ---- a/linux_os/guide/system/software/system-tools/package_nss-tools_installed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_nss-tools_installed/rule.yml -@@ -21,6 +21,7 @@ identifiers: - references: - ospp: FMT_SMF_EXT.1 - srg: SRG-OS-000480-GPOS-00227 -+ stigid@rhel9: RHEL-09-215085 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/system-tools/package_rng-tools_installed/rule.yml b/linux_os/guide/system/software/system-tools/package_rng-tools_installed/rule.yml -index 41a484f26f..53a5367fe5 100644 ---- a/linux_os/guide/system/software/system-tools/package_rng-tools_installed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_rng-tools_installed/rule.yml -@@ -23,6 +23,7 @@ references: - srg: SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-010472 - stigid@rhel8: RHEL-08-010472 -+ stigid@rhel9: RHEL-09-215090 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/system-tools/package_subscription-manager_installed/rule.yml b/linux_os/guide/system/software/system-tools/package_subscription-manager_installed/rule.yml -index f8b8011817..a6e47f2efb 100644 ---- a/linux_os/guide/system/software/system-tools/package_subscription-manager_installed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_subscription-manager_installed/rule.yml -@@ -32,6 +32,7 @@ references: - ism: 0940,1144,1467,1472,1483,1493,1494,1495 - ospp: FPT_TUD_EXT.1,FPT_TUD_EXT.2 - srg: SRG-OS-000366-GPOS-00153 -+ stigid@rhel9: RHEL-09-215010 - - ocil_clause: 'the package is not installed' - -diff --git a/linux_os/guide/system/software/system-tools/package_tuned_removed/rule.yml b/linux_os/guide/system/software/system-tools/package_tuned_removed/rule.yml -index 48443defda..3828dc0be2 100644 ---- a/linux_os/guide/system/software/system-tools/package_tuned_removed/rule.yml -+++ b/linux_os/guide/system/software/system-tools/package_tuned_removed/rule.yml -@@ -25,6 +25,7 @@ references: - srg: SRG-OS-000095-GPOS-00049,SRG-OS-000480-GPOS-00227 - stigid@ol8: OL08-00-040390 - stigid@rhel8: RHEL-08-040390 -+ stigid@rhel9: RHEL-09-215055 - - {{{ complete_ocil_entry_package(package="tuned") }}} - -diff --git a/linux_os/guide/system/software/updating/clean_components_post_updating/rule.yml b/linux_os/guide/system/software/updating/clean_components_post_updating/rule.yml -index ee66181ab6..d839d9e528 100644 ---- a/linux_os/guide/system/software/updating/clean_components_post_updating/rule.yml -+++ b/linux_os/guide/system/software/updating/clean_components_post_updating/rule.yml -@@ -48,6 +48,7 @@ references: - stigid@ol8: OL08-00-010440 - stigid@rhel7: RHEL-07-020200 - stigid@rhel8: RHEL-08-010440 -+ stigid@rhel9: RHEL-09-214035 - stigid@sle12: SLES-12-010570 - stigid@sle15: SLES-15-010560 - stigid@ubuntu2004: UBTU-20-010449 -diff --git a/linux_os/guide/system/software/updating/ensure_gpgcheck_globally_activated/rule.yml b/linux_os/guide/system/software/updating/ensure_gpgcheck_globally_activated/rule.yml -index 91cd19e265..83eaf8f2e2 100644 ---- a/linux_os/guide/system/software/updating/ensure_gpgcheck_globally_activated/rule.yml -+++ b/linux_os/guide/system/software/updating/ensure_gpgcheck_globally_activated/rule.yml -@@ -65,6 +65,7 @@ references: - stigid@ol8: OL08-00-010370 - stigid@rhel7: RHEL-07-020050 - stigid@rhel8: RHEL-08-010370 -+ stigid@rhel9: RHEL-09-214015 - stigid@sle12: SLES-12-010550 - stigid@sle15: SLES-15-010430 - -diff --git a/linux_os/guide/system/software/updating/ensure_gpgcheck_local_packages/rule.yml b/linux_os/guide/system/software/updating/ensure_gpgcheck_local_packages/rule.yml -index d02e8df1a4..812b64d6e3 100644 ---- a/linux_os/guide/system/software/updating/ensure_gpgcheck_local_packages/rule.yml -+++ b/linux_os/guide/system/software/updating/ensure_gpgcheck_local_packages/rule.yml -@@ -44,6 +44,7 @@ references: - stigid@ol8: OL08-00-010371 - stigid@rhel7: RHEL-07-020060 - stigid@rhel8: RHEL-08-010371 -+ stigid@rhel9: RHEL-09-214020 - - ocil_clause: 'there is no process to validate certificates for local packages that is approved by the organization' - -diff --git a/linux_os/guide/system/software/updating/ensure_gpgcheck_never_disabled/rule.yml b/linux_os/guide/system/software/updating/ensure_gpgcheck_never_disabled/rule.yml -index 64287817b9..dca8a55308 100644 ---- a/linux_os/guide/system/software/updating/ensure_gpgcheck_never_disabled/rule.yml -+++ b/linux_os/guide/system/software/updating/ensure_gpgcheck_never_disabled/rule.yml -@@ -49,6 +49,7 @@ references: - srg: SRG-OS-000366-GPOS-00153 - stigid@ol8: OL08-00-010370 - stigid@rhel8: RHEL-08-010370 -+ stigid@rhel9: RHEL-09-214025 - - ocil_clause: 'GPG checking is disabled' - -diff --git a/linux_os/guide/system/software/updating/ensure_redhat_gpgkey_installed/rule.yml b/linux_os/guide/system/software/updating/ensure_redhat_gpgkey_installed/rule.yml -index 5ecaae27c5..74fd2e21c6 100644 ---- a/linux_os/guide/system/software/updating/ensure_redhat_gpgkey_installed/rule.yml -+++ b/linux_os/guide/system/software/updating/ensure_redhat_gpgkey_installed/rule.yml -@@ -60,6 +60,7 @@ references: - srg: SRG-OS-000366-GPOS-00153 - stigid@rhel7: RHEL-07-010019 - stigid@rhel8: RHEL-08-010019 -+ stigid@rhel9: RHEL-09-214010 - - ocil_clause: 'the Red Hat GPG Key is not installed' - -diff --git a/linux_os/guide/system/software/updating/security_patches_up_to_date/rule.yml b/linux_os/guide/system/software/updating/security_patches_up_to_date/rule.yml -index 99aa0518a2..f0ef023320 100644 ---- a/linux_os/guide/system/software/updating/security_patches_up_to_date/rule.yml -+++ b/linux_os/guide/system/software/updating/security_patches_up_to_date/rule.yml -@@ -69,10 +69,10 @@ references: - stigid@ol8: OL08-00-010010 - stigid@rhel7: RHEL-07-020260 - stigid@rhel8: RHEL-08-010010 -+ stigid@rhel9: RHEL-09-211015 - stigid@sle12: SLES-12-010010 - stigid@sle15: SLES-15-010010 - -- - # SCAP 1.3 content should reference flat non compressed xml files - {{% if oval_feed_url %}} - oval_external_content: {{{ oval_feed_url }}} -diff --git a/products/rhel9/profiles/stig.profile b/products/rhel9/profiles/stig.profile -index c88cc4629e..c461e7cd29 100644 ---- a/products/rhel9/profiles/stig.profile -+++ b/products/rhel9/profiles/stig.profile -@@ -1,19 +1,18 @@ - documentation_complete: true - - metadata: -- version: TBD -+ version: V1R1 - SMEs: - - mab879 - - ggbecker - - reference: https://public.cyber.mil/stigs/downloads/?_dl_facet_stigs=operating-systems%2Cunix-linux - --title: '[DRAFT] DISA STIG for Red Hat Enterprise Linux 9' -+title: 'DISA STIG for Red Hat Enterprise Linux 9' - - description: |- -- This is a draft profile based on its RHEL8 version for experimental purposes. -- It is not based on the DISA STIG for RHEL9, because this one was not available at time of -- the release. -+ This profile contains configuration checks that align to the -+ DISA STIG for Red Hat Enterprise Linux 9 V1R1. - - In addition to being applicable to Red Hat Enterprise Linux 9, DISA recognizes this - configuration baseline as applicable to the operating system tier of -@@ -26,4 +25,4 @@ description: |- - - Red Hat Containers with a Red Hat Enterprise Linux 9 image - - selections: -- - srg_gpos:all -+ - stig_rhel9:all -diff --git a/products/rhel9/profiles/stig_gui.profile b/products/rhel9/profiles/stig_gui.profile -index a754a8787d..ca869ccde8 100644 ---- a/products/rhel9/profiles/stig_gui.profile -+++ b/products/rhel9/profiles/stig_gui.profile -@@ -1,19 +1,19 @@ - documentation_complete: true - - metadata: -- version: TBD -+ version: V1R1 - SMEs: - - mab879 - - ggbecker - - reference: https://public.cyber.mil/stigs/downloads/?_dl_facet_stigs=operating-systems%2Cunix-linux - --title: '[DRAFT] DISA STIG with GUI for Red Hat Enterprise Linux 9' -+title: 'DISA STIG with GUI for Red Hat Enterprise Linux 9' - - description: |- -- This is a draft profile based on its RHEL8 version for experimental purposes. -- It is not based on the DISA STIG for RHEL9, because this one was not available at time of -- the release. -+ This profile contains configuration checks that align to the -+ DISA STIG for Red Hat Enterprise Linux 9 V1R1. -+ - - In addition to being applicable to Red Hat Enterprise Linux 9, DISA recognizes this - configuration baseline as applicable to the operating system tier of -@@ -34,15 +34,11 @@ description: |- - extends: stig - - selections: -- # RHEL-08-040320 -+ # RHEL-09-215070 - - '!xwindows_remove_packages' - -- # RHEL-08-040321 -+ # RHEL-09-211030 - - '!xwindows_runlevel_target' - -- # SRG-OS-000480-GPOS-00227 -- - '!package_gdm_removed' -- - '!package_xorg-x11-server-common_removed' -- -- # SRG-OS-000095-GPOS-00049 -+ # RHEL-09-215025 - - '!package_nfs-utils_removed' -diff --git a/shared/references/disa-stig-rhel9-v1r1-xccdf-manual.xml b/shared/references/disa-stig-rhel9-v1r1-xccdf-manual.xml -new file mode 100644 -index 0000000000..8a824f0d47 ---- /dev/null -+++ b/shared/references/disa-stig-rhel9-v1r1-xccdf-manual.xml -@@ -0,0 +1,7018 @@ -+acceptedRed Hat Enterprise Linux 9 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 22 Sep 20233.4.1.229161.10.01I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-211010RHEL 9 must be a vendor-supported release.<VulnDiscussion>An operating system release 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 security issues discovered in the system software. -+ -+Red Hat offers the Extended Update Support (EUS) add-on to a Red Hat Enterprise Linux subscription, for a fee, for those customers who wish to standardize on a specific minor release for an extended period.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Upgrade to a supported version of RHEL 9.Verify that the version or RHEL 9 is vendor supported with the following command: -+ -+$ cat /etc/redhat-release -+ -+Red Hat Enterprise Linux release 9.2 (Plow) -+ -+If the installed version of RHEL 9 is not supported, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-211015RHEL 9 vendor packaged system security patches and updates must be installed and up to date.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Install RHEL 9 security patches and updates at the organizationally defined frequency. If system updates are installed via a centralized repository that is configured on the system, all updates can be installed with the following command: -+ -+$ sudo dnf updateVerify RHEL 9 security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by organizational policy. -+ -+Obtain the list of available package security updates from Red Hat. The URL for updates is https://access.redhat.com/errata-search/. It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed. -+ -+Check that the available package security updates have been installed on the system with the following command: -+ -+$ dnf history list | more -+ -+ ID | Command line | Date and time | Action(s) | Altered -+------------------------------------------------------------------------------- -+ 70 | install aide | 2023-03-05 10:58 | Install | 1 -+ 69 | update -y | 2023-03-04 14:34 | Update | 18 EE -+ 68 | install vlc | 2023-02-21 17:12 | Install | 21 -+ 67 | update -y | 2023-02-21 17:04 | Update | 7 EE -+ -+Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM. -+ -+If the system is in noncompliance with the organizational patching policy, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>RHEL-09-211020RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a command line user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. -+ -+System use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist. -+ -+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure RHEL 9 to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via command line logon. -+ -+Edit the "/etc/issue" file to replace the default text with the Standard Mandatory DOD Notice and Consent Banner. The DOD-required text is: -+ -+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -+ -+By using this IS (which includes any device attached to this IS), you consent to the following conditions: -+ -+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -+ -+-At any time, the USG may inspect and seize data stored on this IS. -+ -+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -+ -+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests -- not for your personal benefit or privacy. -+ -+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."Verify RHEL 9 displays the Standard Mandatory DOD Notice and Consent Banner before granting access to the operating system via a command line user logon. -+ -+Check that a banner is displayed at the command line login screen with the following command: -+ -+$ sudo cat /etc/issue -+ -+If the banner is set correctly it will return the following text: -+ -+"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -+ -+By using this IS (which includes any device attached to this IS), you consent to the following conditions: -+ -+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -+ -+-At any time, the USG may inspect and seize data stored on this IS. -+ -+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -+ -+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -+ -+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." -+ -+If the banner text does not match the Standard Mandatory DOD Notice and Consent Banner exactly, or the line is commented out, this is a finding.SRG-OS-000191-GPOS-00080<GroupDescription></GroupDescription>RHEL-09-211025RHEL 9 must implement the Endpoint Security for Linux Threat Prevention tool.<VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. -+ -+To support this requirement, the operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other tools, as specified in the requirement.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001233Install and enable the latest McAfee ENSLTP package.Verify that RHEL 9 has implemented the Endpoint Security for Linux Threat Prevention tool. -+ -+Check that the following package has been installed: -+ -+$ sudo rpm -qa | grep -i mcafeetp -+ -+If the "mcafeetp" package is not installed, this is a finding. -+ -+Verify that the daemon is running: -+ -+$ sudo ps -ef | grep -i mfetpd -+ -+If the daemon is not running, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-211030The graphical display manager must not be the default target on RHEL 9 unless approved.<VulnDiscussion>Unnecessary service packages must not be installed to decrease the attack surface of the system. Graphical display managers have a long history of security vulnerabilities and must not be used, unless approved and documented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Document the requirement for a graphical user interface with the ISSO or set the default target to multi-user with the following command: -+ -+$ sudo systemctl set-default multi-user.targetVerify that RHEL 9 is configured to boot to the command line: -+ -+$ systemctl get-default -+ -+multi-user.target -+ -+If the system default target is not set to "multi-user.target" and the information system security officer (ISSO) lacks a documented requirement for a graphical user interface, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-211035RHEL 9 must enable the hardware random number generator entropy gatherer service.<VulnDiscussion>The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution of random values. Random number generators are one of the most important building blocks of cryptosystems. -+ -+The rngd service feeds random data from hardware device to kernel random device. Quality (nonpredictable) random number generation is important for several security functions (i.e., ciphers).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Install the rng-tools package with the following command: -+ -+$ sudo dnf install rng-tools -+ -+Then enable the rngd service run the following command: -+ -+$ sudo systemctl enable --now rngdVerify that RHEL 9 has enabled the hardware random number generator entropy gatherer service with the following command: -+ -+$ systemctl is-active rngd -+ -+active -+ -+If the "rngd" service is not active, this is a finding.SRG-OS-000269-GPOS-00103<GroupDescription></GroupDescription>RHEL-09-211040RHEL 9 systemd-journald service must be enabled.<VulnDiscussion>In the event of a system failure, RHEL 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001665To enable the systemd-journald service, run the following command: -+ -+$ sudo systemctl enable --now systemd-journaldVerify that "systemd-journald" is active with the following command: -+ -+$ systemctl is-active systemd-journald -+ -+active -+ -+If the systemd-journald service is not active, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>RHEL-09-211045The systemd Ctrl-Alt-Delete burst key sequence in RHEL 9 must be disabled.<VulnDiscussion>A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken. -+ -+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-002235Configure the system to disable the CtrlAltDelBurstAction by added or modifying the following line in the "/etc/systemd/system.conf" configuration file: -+ -+CtrlAltDelBurstAction=none -+ -+Reload the daemon for this change to take effect. -+ -+$ sudo systemctl daemon-reloadVerify RHEL 9 is configured to not reboot the system when Ctrl-Alt-Delete is pressed seven times within two seconds with the following command: -+ -+$ grep -i ctrl /etc/systemd/system.conf -+ -+CtrlAltDelBurstAction=none -+ -+If the "CtrlAltDelBurstAction" is not set to "none", commented out, or is missing, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>RHEL-09-211050The x86 Ctrl-Alt-Delete key sequence must be disabled on RHEL 9.<VulnDiscussion>A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken. -+ -+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-002235Configure RHEL 9 to disable the ctrl-alt-del.target with the following command: -+ -+$ sudo systemctl disable --now ctrl-alt-del.target -+$ sudo systemctl mask --now ctrl-alt-del.targetVerify RHEL 9 is not configured to reboot the system when Ctrl-Alt-Delete is pressed with the following command: -+ -+$ sudo systemctl status ctrl-alt-del.target -+ -+ctrl-alt-del.target -+Loaded: masked (Reason: Unit ctrl-alt-del.target is masked.) -+Active: inactive (dead) -+ -+If the "ctrl-alt-del.target" is loaded and not masked, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>RHEL-09-211055RHEL 9 debug-shell systemd service must be disabled.<VulnDiscussion>The debug-shell requires no authentication and provides root privileges to anyone who has physical access to the machine. While this feature is disabled by default, masking it adds an additional layer of assurance that it will not be enabled via a dependency in systemd. This also 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. -+ -+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-002235Configure RHEL 9 to mask the debug-shell systemd service with the following command: -+ -+$ sudo systemctl disable --now debug-shell.target -+$ sudo systemctl mask --now debug-shell.targetVerify RHEL 9 is configured to mask the debug-shell systemd service with the following command: -+ -+$ sudo systemctl status debug-shell.service -+ -+debug-shell.service -+Loaded: masked (Reason: Unit debug-shell.service is masked.) -+Active: inactive (dead) -+ -+If the "debug-shell.service" is loaded and not masked, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>RHEL-09-212010RHEL 9 must require a boot loader superuser password.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. -+ -+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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000213Configure RHEL 9 to require a grub bootloader password for the grub superuser account. -+ -+Generate an encrypted grub2 password for the grub superuser account with the following command: -+ -+$ sudo grub2-setpassword -+Enter password: -+Confirm password:Verify the boot loader superuser password has been set and run the following command: -+ -+$ sudo grep "superusers" /etc/grub2.cfg -+ -+password_pbkdf2 superusers-account ${GRUB2_PASSWORD} -+ -+To verify the boot loader superuser account password has been set, and the password encrypted, run the following command: -+ -+$ sudo cat /boot/grub2/user.cfg -+ -+GRUB2_PASSWORD=grub.pbkdf2.sha512.10000.C4E08AC72FBFF7E837FD267BFAD7AEB3D42DDC -+2C99F2A94DD5E2E75C2DC331B719FE55D9411745F82D1B6CFD9E927D61925F9BBDD1CFAA0080E0 -+916F7AB46E0D.1302284FCCC52CD73BA3671C6C12C26FF50BA873293B24EE2A96EE3B57963E6D7 -+0C83964B473EC8F93B07FE749AA6710269E904A9B08A6BBACB00A2D242AD828 -+ -+If a "GRUB2_PASSWORD" is not set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-212015RHEL 9 must disable the ability of systemd to spawn an interactive boot process.<VulnDiscussion>Using interactive or recovery boot, the console user could disable auditing, firewalls, or other services, weakening system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to allocate sufficient audit_backlog_limit to disable the ability of systemd to spawn an interactive boot process with the following command: -+ -+$ sudo grubby --update-kernel=ALL --remove-args="systemd.confirm_spawn"Verify that GRUB 2 is configured to disable interactive boot. -+ -+Check that the current GRUB 2 configuration disables the ability of systemd to spawn an interactive boot process with the following command: -+ -+$ sudo grubby --info=ALL | grep args | grep 'systemd.confirm_spawn' -+ -+If any output is returned, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>RHEL-09-212020RHEL 9 must require a unique superusers name upon booting into single-user and maintenance modes.<VulnDiscussion>Having a nondefault grub superuser username makes password-guessing attacks less effective.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000213Configure RHEL 9 to have a unique username for the grub superuser account. -+ -+Edit the "/etc/grub.d/01_users" file and add or modify the following lines in the "### BEGIN /etc/grub.d/01_users ###" section: -+ -+set superusers="superusers-account" -+export superusers -+ -+Once the superuser account has been added, update the grub.cfg file by running: -+ -+$ sudo grubby --update-kernel=ALL'Verify the boot loader superuser account has been set with the following command: -+ -+$ sudo grep -A1 "superusers" /etc/grub2.cfg -+ -+ set superusers="<superusers-account>" -+export superusers -+ -+The <superusers-account> is the actual account name different from common names like root, admin, or administrator. -+ -+If superusers contains easily guessable usernames, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-212025RHEL 9 /boot/grub2/grub.cfg file must be group-owned by root.<VulnDiscussion>The "root" group is a highly privileged group. Furthermore, the group-owner of this file should not have any access privileges anyway.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /boot/grub2/grub.cfg to root by running the following command: -+ -+$ sudo chgrp root /boot/grub2/grub.cfgVerify the group ownership of the "/boot/grub2/grub.cfg" file with the following command: -+ -+$ sudo stat -c "%G %n" /boot/grub2/grub.cfg -+ -+root /boot/grub2/grub.cfg -+ -+If "/boot/grub2/grub.cfg" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-212030RHEL 9 /boot/grub2/grub.cfg file must be owned by root.<VulnDiscussion>The " /boot/grub2/grub.cfg" file stores sensitive system configuration. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /boot/grub2/grub.cfg to root by running the following command: -+ -+$ sudo chown root /boot/grub2/grub.cfgVerify the ownership of the "/boot/grub2/grub.cfg" file with the following command: -+ -+$ sudo stat -c "%U %n" /boot/grub2/grub.cfg -+ -+root /boot/grub2/grub.cfg -+ -+If "/boot/grub2/grub.cfg" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-212035RHEL 9 must disable virtual system calls.<VulnDiscussion>System calls are special routines in the Linux kernel, which userspace applications ask to do privileged tasks. Invoking a system call is an expensive operation because the processor must interrupt the currently executing task and switch context to kernel mode and then back to userspace after the system call completes. Virtual system calls map into user space a page that contains some variables and the implementation of some system calls. This allows the system calls to be executed in userspace to alleviate the context switching expense. -+ -+Virtual system calls provide an opportunity of attack for a user who has control of the return instruction pointer. Disabling virtual system calls help to prevent return oriented programming (ROP) attacks via buffer overflows and overruns. If the system intends to run containers based on RHEL 6 components, then virtual system calls will need enabled so the components function properly. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000134-GPOS-00068</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001084Document the use of virtual system calls with the ISSO as an operational requirement or disable them with the following command: -+ -+$ sudo grubby --update-kernel=ALL --args="vsyscall=none" -+ -+Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: -+ -+GRUB_CMDLINE_LINUX="vsyscall=none"Verify the current GRUB 2 configuration disables virtual system calls with the following command: -+ -+$ sudo grubby --info=ALL | grep args | grep -v 'vsyscall=none' -+ -+If any output is returned, this is a finding. -+ -+Check that virtual system calls are disabled by default to persist in kernel updates with the following command: -+ -+$ sudo grep vsyscall /etc/default/grub -+ -+GRUB_CMDLINE_LINUX="vsyscall=none" -+ -+If "vsyscall" is not set to "none", is missing or commented out, and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-212040RHEL 9 must clear the page allocator to prevent use-after-free attacks.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000134-GPOS-00068</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001084Configure RHEL 9 to enable page poisoning with the following commands: -+ -+$ sudo grubby --update-kernel=ALL --args="page_poison=1" -+ -+Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: -+ -+GRUB_CMDLINE_LINUX="page_poison=1"Verify that GRUB 2 is configured to enable page poisoning to mitigate use-after-free vulnerabilities. -+ -+Check that the current GRUB 2 configuration has page poisoning enabled with the following command: -+ -+$ sudo grubby --info=ALL | grep args | grep -v 'page_poison=1' -+ -+If any output is returned, this is a finding. -+ -+Check that page poisoning is enabled by default to persist in kernel updates with the following command: -+ -+$ sudo grep page_poison /etc/default/grub -+ -+GRUB_CMDLINE_LINUX="page_poison=1" -+ -+If "page_poison" is not set to "1", is missing or commented out, this is a finding.SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>RHEL-09-212045RHEL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks.<VulnDiscussion>Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can be either hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. -+ -+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. -+ -+SLAB objects are blocks of physically contiguous memory. SLUB is the unqueued SLAB allocator. -+ -+Satisfies: SRG-OS-000433-GPOS-00192, SRG-OS-000134-GPOS-00068</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001084CCI-002824Configure RHEL to enable poisoning of SLUB/SLAB objects with the following commands: -+ -+$ sudo grubby --update-kernel=ALL --args="slub_debug=P" -+ -+Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: -+ -+GRUB_CMDLINE_LINUX="slub_debug=P"Verify that GRUB 2 is configured to enable poisoning of SLUB/SLAB objects to mitigate use-after-free vulnerabilities with the following commands: -+ -+Check that the current GRUB 2 configuration has poisoning of SLUB/SLAB objects enabled: -+ -+$ sudo grubby --info=ALL | grep args | grep -v 'slub_debug=P' -+ -+If any output is returned, this is a finding. -+ -+Check that poisoning of SLUB/SLAB objects is enabled by default to persist in kernel updates: -+ -+$ sudo grep slub_debug /etc/default/grub -+ -+GRUB_CMDLINE_LINUX="slub_debug=P" -+ -+If "slub_debug" is not set to "P", is missing or commented out, this is a finding.SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>RHEL-09-212050RHEL 9 must enable mitigations against processor-based vulnerabilities.<VulnDiscussion>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). -+ -+Satisfies: SRG-OS-000433-GPOS-00193, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381CCI-002824Configure RHEL 9 to enable kernel page-table isolation with the following command: -+ -+$ sudo grubby --update-kernel=ALL --args="pti=on" -+ -+Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: -+ -+GRUB_CMDLINE_LINUX="pti=on"Verify RHEL 9 enables kernel page-table isolation with the following command: -+ -+$ sudo grubby --info=ALL | grep pti -+ -+args="ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet fips=1 audit=1 audit_backlog_limit=8192 pti=on -+ -+If the "pti" entry does not equal "on", or is missing, this is a finding. -+ -+Check that kernel page-table isolation is enabled by default to persist in kernel updates: -+ -+$ sudo grep pti /etc/default/grub -+ -+GRUB_CMDLINE_LINUX="pti=on" -+ -+If "pti" is not set to "on", is missing or commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-212055RHEL 9 must enable auditing of processes that start prior to the audit daemon.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. -+ -+If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218, SRG-OS-000254-GPOS-00095</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-001464CCI-002884Enable auditing of processes that start prior to the audit daemon with the following command: -+ -+$ sudo grubby --update-kernel=ALL --args="audit=1" -+ -+Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: -+ -+GRUB_CMDLINE_LINUX="audit=1"Verify that GRUB 2 is configured to enable auditing of processes that start prior to the audit daemon with the following commands: -+ -+Check that the current GRUB 2 configuration enabled auditing: -+ -+$ sudo grubby --info=ALL | grep audit -+ -+args="ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet fips=1 audit=1 audit_backlog_limit=8192 pti=on -+ -+If "audit" is not set to "1" or is missing, this is a finding. -+ -+Check that auditing is enabled by default to persist in kernel updates: -+ -+$ sudo grep audit /etc/default/grub -+ -+GRUB_CMDLINE_LINUX="audit=1" -+ -+If "audit" is not set to "1", is missing, or is commented out, this is a finding.SRG-OS-000132-GPOS-00067<GroupDescription></GroupDescription>RHEL-09-213010RHEL 9 must restrict access to the kernel message buffer.<VulnDiscussion>Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. -+ -+This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DOD or other government agencies. -+ -+There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components. -+ -+Restricting access to the kernel message buffer limits access to only root. This prevents attackers from gaining additional system information as a nonprivileged user. -+ -+Satisfies: SRG-OS-000132-GPOS-00067, SRG-OS-000138-GPOS-00069</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001082CCI-001090Configure RHEL 9 to restrict access to the kernel message buffer. -+ -+Add or edit the following line in a system configuration file, in the "/etc/sysctl.d/" directory: -+ -+kernel.dmesg_restrict = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to restrict access to the kernel message buffer with the following commands: -+ -+Check the status of the kernel.dmesg_restrict kernel parameter. -+ -+$ sysctl kernel.dmesg_restrict -+ -+kernel.dmesg_restrict = 1 -+ -+If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.dmesg_restrict | tail -1 -+ -+kernel.dmesg_restrict = 1 -+ -+If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding.SRG-OS-000132-GPOS-00067<GroupDescription></GroupDescription>RHEL-09-213015RHEL 9 must prevent kernel profiling by nonprivileged users.<VulnDiscussion>Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. -+ -+This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DOD or other government agencies. -+ -+There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components. -+ -+Setting the kernel.perf_event_paranoid kernel parameter to "2" prevents attackers from gaining additional system information as a nonprivileged user. -+ -+Satisfies: SRG-OS-000132-GPOS-00067, SRG-OS-000138-GPOS-00069</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001082CCI-001090Configure RHEL 9 to prevent kernel profiling by nonprivileged users. -+ -+Add or edit the following line in a system configuration file, in the "/etc/sysctl.d/" directory: -+ -+kernel.perf_event_paranoid = 2 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to prevent kernel profiling by nonprivileged users with the following commands: -+ -+Check the status of the kernel.perf_event_paranoid kernel parameter. -+ -+$sysctl kernel.perf_event_paranoid -+ -+kernel.perf_event_paranoid = 2 -+ -+If "kernel.perf_event_paranoid" is not set to "2" or is missing, this is a finding. -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.perf_event_paranoid | tail -1 -+ -+kernel.perf_event_paranoid = 2 -+ -+If "kernel.perf_event_paranoid" is not set to "2" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213020RHEL 9 must prevent the loading of a new kernel for later execution.<VulnDiscussion>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. -+ -+Disabling kexec_load prevents an unsigned kernel image (that could be a windows kernel or modified vulnerable kernel) from being loaded. Kexec can be used subvert the entire secureboot process and should be avoided at all costs especially since it can load unsigned kernel images. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000366-GPOS-00153</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001749Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ -+kernel.kexec_load_disabled = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to disable kernel image loading. -+ -+Check the status of the kernel.kexec_load_disabled kernel parameter with the following command: -+ -+$ sysctl kernel.kexec_load_disabled -+ -+kernel.kexec_load_disabled = 1 -+ -+If "kernel.kexec_load_disabled" is not set to "1" or is missing, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter with the following command: -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.kexec_load_disabled | tail -1 -+ -+kernel.kexec_load_disabled = 1 -+ -+If "kernel.kexec_load_disabled" is not set to "1" or is missing, this is a finding.SRG-OS-000132-GPOS-00067<GroupDescription></GroupDescription>RHEL-09-213025RHEL 9 must restrict exposed kernel pointer addresses access.<VulnDiscussion>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 disallows any program without the CAP_SYSLOG capability to get the addresses of kernel pointers by replacing them with "0". -+ -+Satisfies: SRG-OS-000132-GPOS-00067, SRG-OS-000433-GPOS-00192, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001082CCI-002824Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ -+kernel.kptr_restrict = 1 -+ -+Reload settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify the runtime status of the kernel.kptr_restrict kernel parameter with the following command: -+ -+$ sysctl kernel.kptr_restrict -+ -+kernel.kptr_restrict = 1 -+ -+Verify the configuration of the kernel.kptr_restrict kernel parameter with the following command: -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.kptr_restrict | tail -1 -+ -+kernel.kptr_restrict =1 -+ -+If "kernel.kptr_restrict" is not set to "1" or is missing, this is a finding.SRG-OS-000312-GPOS-00123<GroupDescription></GroupDescription>RHEL-09-213030RHEL 9 must enable kernel parameters to enforce discretionary access control on hardlinks.<VulnDiscussion>By enabling the fs.protected_hardlinks kernel parameter, users can no longer create soft or hard links to files they do not own. Disallowing such hardlinks mitigates vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat(). -+ -+Satisfies: SRG-OS-000312-GPOS-00123, SRG-OS-000324-GPOS-00125</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002165CCI-002235Configure RHEL 9 to enable DAC on hardlinks with the following: -+ -+Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ -+fs.protected_hardlinks = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to enable DAC on hardlinks. -+ -+Check the status of the fs.protected_hardlinks kernel parameter with the following command: -+ -+$ sudo sysctl fs.protected_hardlinks -+ -+fs.protected_hardlinks = 1 -+ -+If "fs.protected_hardlinks" is not set to "1" or is missing, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F fs.protected_hardlinks | tail -1 -+ -+fs.protected_hardlinks = 1 -+ -+If "fs.protected_hardlinks" is not set to "1" or is missing, this is a finding.SRG-OS-000312-GPOS-00123<GroupDescription></GroupDescription>RHEL-09-213035RHEL 9 must enable kernel parameters to enforce discretionary access control on symlinks.<VulnDiscussion>By enabling the fs.protected_symlinks kernel parameter, symbolic links are permitted to be followed only when outside a sticky world-writable directory, or when the user identifier (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(). -+ -+Satisfies: SRG-OS-000312-GPOS-00123, SRG-OS-000324-GPOS-00125</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002165CCI-002235Configure RHEL 9 to enable DAC on symlinks with the following: -+ -+Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ -+fs.protected_symlinks = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to enable DAC on symlinks. -+ -+Check the status of the fs.protected_symlinks kernel parameter with the following command: -+ -+$ sudo sysctl fs.protected_symlinks -+ -+fs.protected_symlinks = 1 -+ -+If "fs.protected_symlinks " is not set to "1" or is missing, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F fs.protected_symlinks | tail -1 -+ -+fs.protected_symlinks = 1 -+ -+If "fs.protected_symlinks" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213040RHEL 9 must disable the kernel.core_pattern.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to disable storing core dumps. -+ -+Add or edit the following line in a system configuration file, in the "/etc/sysctl.d/" directory: -+ -+kernel.core_pattern = |/bin/false -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 disables storing core dumps with the following commands: -+ -+$ sysctl kernel.core_pattern -+ -+kernel.core_pattern = |/bin/false -+ -+If the returned line does not have a value of "|/bin/false", or a line is not returned and the need for core dumps is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding. -+ -+Check that the configuration files are present to disable core dump storage. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.core_pattern | tail -1 -+ -+kernel.core_pattern = |/bin/false -+ -+If "kernel.core_pattern" is not set to "|/bin/false" and is not documented with the ISSO as an operational requirement, or is missing, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-213045RHEL 9 must be configured to disable the Asynchronous Transfer Mode kernel module.<VulnDiscussion>Disabling Asynchronous Transfer Mode (ATM) protects the system against exploitation of any flaws in its implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To configure the system to prevent the atm kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf (or create atm.conf if it does not exist): -+ -+install atm /bin/false -+blacklist atmVerify that RHEL 9 disables the ability to load the ATM kernel module with the following command: -+ -+$ sudo grep -r atm /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist atm -+ -+If the command does not return any output, or the line is commented out, and use of ATM is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-213050RHEL 9 must be configured to disable the Controller Area Network kernel module.<VulnDiscussion>Disabling Controller Area Network (CAN) protects the system against exploitation of any flaws in its implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To configure the system to prevent the can kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf (or create atm.conf if it does not exist): -+ -+install can /bin/false -+blacklist canVerify that RHEL 9 disables the ability to load the CAN kernel module with the following command: -+ -+$ sudo grep -r can /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist can -+ -+If the command does not return any output, or the line is commented out, and use of CAN is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-213055RHEL 9 must be configured to disable the FireWire kernel module.<VulnDiscussion>Disabling firewire protects the system against exploitation of any flaws in its implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To 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 (or create firewire-core.conf if it does not exist): -+ -+install firewire-core /bin/true -+blacklist firewire-coreVerify that RHEL 9 disables the ability to load the firewire-core kernel module with the following command: -+ -+$ sudo grep -r firewire-core /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist firewire-core -+ -+If the command does not return any output, or the line is commented out, and use of firewire-core is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-213060RHEL 9 must disable the Stream Control Transmission Protocol (SCTP) kernel module.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+Failing to disconnect unused protocols can result in a system compromise. -+ -+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. Disabling SCTP protects the system against exploitation of any flaws in its implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To configure the system to prevent the sctp kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf (or create sctp.conf if it does not exist): -+ -+install sctp/bin/false -+blacklist sctpVerify that RHEL 9 disables the ability to load the sctp kernel module with the following command: -+ -+$ sudo grep -r sctp /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist sctp -+ -+If the command does not return any output, or the line is commented out, and use of sctp is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-213065RHEL 9 must disable the Transparent Inter Process Communication (TIPC) kernel module.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+Failing to disconnect unused protocols can result in a system compromise. -+ -+The Transparent Inter Process Communication (TIPC) is a protocol that is specially designed for intra-cluster communication. It can be configured to transmit messages either on UDP or directly across Ethernet. Message delivery is sequence guaranteed, loss free and flow controlled. Disabling TIPC protects the system against exploitation of any flaws in its implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To configure the system to prevent the tipc kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf (or create tipc.conf if it does not exist): -+ -+install tipc /bin/false -+blacklist tipcVerify that RHEL 9 disables the ability to load the tipc kernel module with the following command: -+ -+$ sudo grep -r tipc /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist tipc -+ -+If the command does not return any output, or the line is commented out, and use of tipc is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>RHEL-09-213070RHEL 9 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution.<VulnDiscussion>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' 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 repurpose it using return oriented programming (ROP) techniques. -+ -+Satisfies: SRG-OS-000433-GPOS-00193, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-002824Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ -+kernel.randomize_va_space = 2 -+ -+Reload settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is implementing ASLR with the following command: -+ -+$ sysctl kernel.randomize_va_space -+ -+kernel.randomize_va_space = 2 -+ -+Check that the configuration files are present to enable this kernel parameter. -+Verify the configuration of the kernel.kptr_restrict kernel parameter with the following command: -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.randomize_va_space | tail -1 -+ -+kernel.randomize_va_space = 2 -+ -+If "kernel.randomize_va_space" is not set to "2" or is missing, this is a finding.SRG-OS-000132-GPOS-00067<GroupDescription></GroupDescription>RHEL-09-213075RHEL 9 must disable access to network bpf system call from nonprivileged processes.<VulnDiscussion>Loading and accessing the packet filters programs and maps using the bpf() system call has the potential of revealing sensitive information about the kernel state. -+ -+Satisfies: SRG-OS-000132-GPOS-00067, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001082Configure RHEL 9 to prevent privilege escalation thru the kernel by disabling access to the bpf syscall by adding the following line to a file, in the "/etc/sysctl.d" directory: -+ -+kernel.unprivileged_bpf_disabled = 1 -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 prevents privilege escalation thru the kernel by disabling access to the bpf system call with the following commands: -+ -+$ sysctl kernel.unprivileged_bpf_disabled -+ -+kernel.unprivileged_bpf_disabled = 1 -+ -+If the returned line does not have a value of "1", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.unprivileged_bpf_disabled | tail -1 -+kernel.unprivileged_bpf_disabled = 1 -+ -+If the network parameter "ipv4.tcp_syncookies" is not equal to "1", or nothing is returned, this is a finding.SRG-OS-000132-GPOS-00067<GroupDescription></GroupDescription>RHEL-09-213080RHEL 9 must restrict usage of ptrace to descendant processes.<VulnDiscussion>Unrestricted usage of ptrace allows compromised binaries to run ptrace on other processes of the user. Like this, the attacker can steal sensitive information from the target processes (e.g., SSH sessions, web browser, etc.) without any additional assistance from the user (i.e., without resorting to phishing). -+ -+Satisfies: SRG-OS-000132-GPOS-00067, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001082Configure RHEL 9 to restrict usage of ptrace to descendant processes by adding the following line to a file, in the "/etc/sysctl.d" directory: -+ -+kernel.yama.ptrace_scope = 1 -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 restricts usage of ptrace to descendant processes with the following commands: -+ -+$ sysctl kernel.yama.ptrace_scope -+ -+kernel.yama.ptrace_scope = 1 -+ -+If the returned line does not have a value of "1", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F kernel.yama.ptrace_scope| tail -1 -+kernel.yama.ptrace_scope = 1 -+ -+If the network parameter "kernel.yama.ptrace_scope" is not equal to "1", or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213085RHEL 9 must disable core dump backtraces.<VulnDiscussion>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 or system operators trying to debug problems. -+ -+Enabling core dumps on production systems is not recommended; however, there may be overriding operational requirements to enable advanced debugging. Permitting temporary enablement of core dumps during such situations must be reviewed through local needs and policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the operating system to disable core dump backtraces. -+ -+Add or modify the following line in /etc/systemd/coredump.conf: -+ -+ProcessSizeMax=0Verify RHEL 9 disables core dump backtraces by issuing the following command: -+ -+$ grep -i process /etc/systemd/coredump.conf -+ -+ProcessSizeMax=0 -+ -+If the "ProcessSizeMax" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the information system security officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213090RHEL 9 must disable storing core dumps.<VulnDiscussion>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 or system operators trying to debug problems. Enabling core dumps on production systems is not recommended; however, there may be overriding operational requirements to enable advanced debugging. Permitting temporary enablement of core dumps during such situations must be reviewed through local needs and policy.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the operating system to disable storing core dumps for all users. -+ -+Add or modify the following line in /etc/systemd/coredump.conf: -+ -+Storage=noneVerify RHEL 9 disables storing core dumps for all users by issuing the following command: -+ -+$ grep -i storage /etc/systemd/coredump.conf -+ -+Storage=none -+ -+If the "Storage" item is missing, commented out, or the value is anything other than "none" and the need for core dumps is not documented with the information system security officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213095RHEL 9 must disable core dumps for all users.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the operating system to disable core dumps for all users. -+ -+Add the following line to the top of the /etc/security/limits.conf or in a single ".conf" file defined in /etc/security/limits.d/: -+ -+* hard core 0Verify RHEL 9 disables core dumps for all users by issuing the following command: -+ -+$ grep -r -s core /etc/security/limits.conf /etc/security/limits.d/*.conf -+ -+/etc/security/limits.conf:* hard core 0 -+ -+This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. -+ -+If the "core" item is missing, commented out, or the value is anything other than "0" and the need for core dumps is not documented with the information system security officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213100RHEL 9 must disable acquiring, saving, and processing core dumps.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the system to disable the systemd-coredump.socket with the following command: -+ -+$ sudo systemctl mask --now systemd-coredump.socket -+ -+Created symlink /etc/systemd/system/systemd-coredump.socket -> /dev/null -+ -+Reload the daemon for this change to take effect. -+ -+$ sudo systemctl daemon-reloadVerify RHEL 9 is not configured to acquire, save, or process core dumps with the following command: -+ -+$ sudo systemctl status systemd-coredump.socket -+ -+systemd-coredump.socket -+Loaded: masked (Reason: Unit systemd-coredump.socket is masked.) -+Active: inactive (dead) -+ -+If the "systemd-coredump.socket" is loaded and not masked and the need for core dumps is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213105RHEL 9 must disable the use of user namespaces.<VulnDiscussion>User namespaces are used primarily for Linux containers. The value "0" disallows the use of user namespaces.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to disable the use of user namespaces by adding the following line to a file, in the "/etc/sysctl.d" directory: -+ -+Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is Not Applicable. -+ -+user.max_user_namespaces = 0 -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 disables the use of user namespaces with the following commands: -+ -+Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is Not Applicable. -+ -+$ sysctl user.max_user_namespaces -+ -+user.max_user_namespaces = 0 -+ -+If the returned line does not have a value of "0", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F user.max_user_namespaces | tail -1 -+user.max_user_namespaces = 0 -+ -+If the network parameter "user.max_user_namespaces" is not equal to "0", or nothing is returned, this is a finding.SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>RHEL-09-213110RHEL 9 must implement nonexecutable data to protect its memory from unauthorized code execution.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002824Update the GRUB 2 bootloader configuration. -+ -+Run the following command: -+ -+$ sudo grubby --update-kernel=ALL --remove-args=noexecVerify ExecShield is enabled on 64-bit RHEL 9 systems with the following command: -+ -+$ sudo dmesg | grep '[NX|DX]*protection' -+ -+[ 0.000000] NX (Execute Disable) protection: active -+ -+If "dmesg" does not show "NX (Execute Disable) protection" active, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-213115The kdump service on RHEL 9 must be disabled.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Disable and mask the kdump service on RHEL 9. -+ -+To disable the kdump service run the following command: -+ -+$ sudo systemctl disable --now kdump -+ -+To mask the kdump service run the following command: -+ -+$ sudo systemctl mask --now kdumpVerify that the kdump service is disabled in system boot configuration with the following command: -+ -+$ systemctl is-enabled kdump -+ -+disabled -+ -+Verify that the kdump service is not active (i.e., not running) through current runtime configuration with the following command: -+ -+$ systemctl is-active kdump -+ -+inactive -+ -+Verify that the kdump service is masked with the following command: -+ -+$ sudo systemctl show kdump | grep "LoadState\|UnitFileState" -+ -+LoadState=masked -+ -+UnitFileState=masked -+ -+If the "kdump" service is loaded or active, and is not masked, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>RHEL-09-214010RHEL 9 must ensure cryptographic verification of vendor software packages.<VulnDiscussion>Cryptographic verification of vendor software packages ensures that all software packages are obtained from a valid source and protects against spoofing that could lead to installation of malware on the system. Red Hat cryptographically signs all software packages, which includes updates, with a GPG key to verify that they are valid.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001749Install Red Hat package-signing keys on the system and verify their fingerprints match vendor values. -+ -+Insert RHEL 9 installation disc or attach RHEL 9 installation image to the system. Mount the disc or image to make the contents accessible inside the system. -+ -+Assuming the mounted location is "/media/cdrom", use the following command to copy Red Hat GPG key file onto the system: -+ -+$ sudo cp /media/cdrom/RPM-GPG-KEY-redhat-release /etc/pki/rpm-gpg/ -+ -+Import Red Hat GPG keys from key file into system keyring: -+ -+$ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release -+ -+Using the steps listed in the Check Text, confirm the newly imported keys show as installed on the system and verify their fingerprints match vendor values.Confirm Red Hat package-signing keys are installed on the system and verify their fingerprints match vendor values. -+ -+Note: For RHEL 9 software packages, Red Hat uses GPG keys labeled "release key 2" and "auxiliary key 3". The keys are defined in key file "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release" by default. -+ -+List Red Hat GPG keys installed on the system: -+ -+$ sudo rpm -q --queryformat "%{SUMMARY}\n" gpg-pubkey | grep -i "red hat" -+ -+Red Hat, Inc. (release key 2) <security@redhat.com> public key -+Red Hat, Inc. (auxiliary key 3) <security@redhat.com> public key -+ -+If Red Hat GPG keys "release key 2" and "auxiliary key 3" are not installed, this is a finding. -+ -+List key fingerprints of installed Red Hat GPG keys: -+ -+$ sudo gpg -q --keyid-format short --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release -+ -+If key file "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release" is missing, this is a finding. -+ -+Example output: -+ -+pub rsa4096/FD431D51 2009-10-22 [SC] -+ Key fingerprint = 567E 347A D004 4ADE 55BA 8A5F 199E 2F91 FD43 1D51 -+uid Red Hat, Inc. (release key 2) <security@redhat.com> -+pub rsa4096/5A6340B3 2022-03-09 [SC] -+ Key fingerprint = 7E46 2425 8C40 6535 D56D 6F13 5054 E4A4 5A63 40B3 -+uid Red Hat, Inc. (auxiliary key 3) <security@redhat.com> -+ -+Compare key fingerprints of installed Red Hat GPG keys with fingerprints listed for RHEL 9 on Red Hat "Product Signing Keys" webpage at https://access.redhat.com/security/team/key. -+ -+If key fingerprints do not match, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>RHEL-09-214015RHEL 9 must check the GPG signature of software packages originating from external software repositories before installation.<VulnDiscussion>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. -+ -+All software packages must be signed with a cryptographic key recognized and approved by the organization. -+ -+Verifying the authenticity of software prior to installation validates the integrity of the software package received from a vendor. This verifies the software has not been tampered with and that it has been provided by a trusted vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001749Configure dnf to always check the GPG signature of software packages originating from external software repositories before installation. -+ -+Add or update the following line in the [main] section of the /etc/dnf/dnf.conf file: -+ -+gpgcheck=1Verify that dnf always checks the GPG signature of software packages originating from external software repositories before installation: -+ -+$ grep gpgcheck /etc/dnf/dnf.conf -+ -+gpgcheck=1 -+ -+If "gpgcheck" is not set to "1", or if the option is missing or commented out, ask the system administrator how the GPG signatures of software packages are being verified. -+ -+If there is no process to verify GPG signatures that is approved by the organization, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>RHEL-09-214020RHEL 9 must check the GPG signature of locally installed software packages before installation.<VulnDiscussion>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. -+ -+All software packages must be signed with a cryptographic key recognized and approved by the organization. -+ -+Verifying the authenticity of software prior to installation validates the integrity of the software package received from a vendor. This verifies the software has not been tampered with and that it has been provided by a trusted vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001749Configure dnf to always check the GPG signature of local software packages before installation. -+ -+Add or update the following line in the [main] section of the /etc/dnf/dnf.conf file: -+ -+localpkg_gpgcheck=1Verify that dnf always checks the GPG signature of locally installed software packages before installation: -+ -+$ grep localpkg_gpgcheck /etc/dnf/dnf.conf -+ -+localpkg_gpgcheck=1 -+ -+If "localpkg_gpgcheck" is not set to "1", or if the option is missing or commented out, ask the system administrator how the GPG signatures of local software packages are being verified. -+ -+If there is no process to verify GPG signatures that is approved by the organization, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>RHEL-09-214025RHEL 9 must have GPG signature verification enabled for all software repositories.<VulnDiscussion>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. -+ -+All software packages must be signed with a cryptographic key recognized and approved by the organization. -+ -+Verifying the authenticity of software prior to installation validates the integrity of the software package received from a vendor. This verifies the software has not been tampered with and that it has been provided by a trusted vendor.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001749Configure all software repositories defined in "/etc/yum.repos.d/" to have "gpgcheck" enabled: -+ -+$ sudo sed -i 's/gpgcheck\s*=.*/gpgcheck=1/g' /etc/yum.repos.d/*Verify that all software repositories defined in "/etc/yum.repos.d/" have been configured with "gpgcheck" enabled: -+ -+$ grep gpgcheck /etc/yum.repos.d/*.repo | more -+ -+gpgcheck = 1 -+ -+If "gpgcheck" is not set to "1" for all returned lines, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-214030RHEL 9 must be configured so that the cryptographic hashes of system files match vendor values.<VulnDiscussion>The hashes of important files like system executables should match the information given by the RPM database. Executables with erroneous hashes could be a sign of nefarious activity on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Given output from the check command, identify the package that provides the output and reinstall it. The following trimmed example output shows a package that has failed verification, been identified, and been reinstalled: -+ -+$ rpm -Va --noconfig | awk '$1 ~ /..5/ && $2 != "c"' -+S.5....T. /usr/bin/znew -+$ sudo dnf provides /usr/bin/znew -+[...] -+gzip-1.10-8.el9.x86_64 : The GNU data compression program -+[...] -+$ sudo dnf reinstall gzip -+[...] -+$ rpm -Va --noconfig | awk '$1 ~ /..5/ && $2 != "c"' -+[no output]The following command will list which files on the system have file hashes different from what is expected by the RPM database: -+ -+ $ rpm -Va --noconfig | awk '$1 ~ /..5/ && $2 != "c"' -+ -+If there is output, this is a finding.SRG-OS-000437-GPOS-00194<GroupDescription></GroupDescription>RHEL-09-214035RHEL 9 must remove all software components after updated versions have been installed.<VulnDiscussion>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some adversaries.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002617Configure RHEL 9 to remove all software components after updated versions have been installed. -+ -+Edit the file /etc/dnf/dnf.conf by adding or editing the following line: -+ -+ clean_requirements_on_remove=1Verify RHEL 9 removes all software components after updated versions have been installed with the following command: -+ -+$ grep clean /etc/dnf/dnf.conf -+ -+clean_requirements_on_remove=1 -+ -+If "clean_requirements_on_remove" is not set to "1", this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>RHEL-09-215010RHEL 9 subscription-manager package must be installed.<VulnDiscussion>The Red Hat Subscription Manager application manages software subscriptions and software repositories for installed software products on the local system. It communicates with backend servers, such as the Red Hat Customer Portal or an on-premise instance of Subscription Asset Manager, to register the local system and grant access to software resources determined by the subscription entitlement.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001749The subscription-manager package can be installed with the following command: -+ -+$ sudo dnf install subscription-managerVerify that RHEL 9 subscription-manager package is installed with the following command: -+ -+$ sudo dnf list --installed subscription-manager -+ -+Example output: -+ -+subscription-manager.x86_64 1.29.26-3.el9_0 -+ -+If the "subscription-manager" package is not installed, this is a finding.SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>RHEL-09-215015RHEL 9 must not have a File Transfer Protocol (FTP) server package installed.<VulnDiscussion>The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service. -+ -+Removing the "vsftpd" package decreases the risk of accidental activation. -+ -+Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000095-GPOS-00049, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000197CCI-000366CCI-000381The ftp package can be removed with the following command (using vsftpd as an example): -+ -+$ sudo dnf remove vsftpdVerify that RHEL 9 does not have a File Transfer Protocol (FTP) server package installed with the following command: -+ -+$ sudo dnf list --installed | grep ftp -+ -+If the "ftp" package is installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215020RHEL 9 must not have the sendmail package installed.<VulnDiscussion>The sendmail software was not developed with security in mind, and its design prevents it from being effectively contained by SELinux. Postfix must be used instead. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000381Remove the sendmail package with the following command: -+ -+$ sudo dnf remove sendmailVerify that the sendmail package is not installed with the following command: -+ -+$ sudo dnf list --installed sendmail -+ -+Error: No matching Packages to list -+ -+If the "sendmail" package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215025RHEL 9 must not have the nfs-utils package installed.<VulnDiscussion>"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 that are mounted on that host.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381Remove the nfs-utils package with the following command: -+ -+$ sudo dnf remove nfs-utilsVerify that the nfs-utils package is not installed with the following command: -+ -+$ sudo dnf list --installed nfs-utils -+ -+Error: No matching Packages to list -+ -+If the "nfs-utils" package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215030RHEL 9 must not have the ypserv package installed.<VulnDiscussion>The NIS service provides an unencrypted authentication service, which does not provide for the confidentiality and integrity of user passwords or the remote session. -+ -+Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381Remove the ypserv package with the following command: -+ -+$ sudo dnf remove ypservVerify that the ypserv package is not installed with the following command: -+ -+$ sudo dnf list --installed ypserv -+ -+Error: No matching Packages to list -+ -+If the "ypserv" package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215035RHEL 9 must not have the rsh-server package installed.<VulnDiscussion>The "rsh-server" service provides unencrypted remote access service, which does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication. If a privileged user were to login using this service, the privileged user password could be compromised. The "rsh-server" package provides several obsolete and insecure network services. Removing it decreases the risk of accidental (or intentional) activation of those services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381Remove the rsh-server package with the following command: -+ -+$ sudo dnf remove rsh-serverVerify that the rsh-server package is not installed with the following command: -+ -+$ sudo dnf list --installed rsh-server -+ -+Error: No matching Packages to list -+ -+If the "rsh-server" package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215040RHEL 9 must not have the telnet-server package installed.<VulnDiscussion>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 unsecure. 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 accidental (or intentional) activation of the telnet service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381Remove the telnet-server package with the following command: -+ -+$ sudo dnf remove telnet-serverVerify that the telnet-server package is not installed with the following command: -+ -+$ sudo dnf list --installed telnet-server -+ -+Error: No matching Packages to list -+ -+If the "telnet-server" package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215045RHEL 9 must not have the gssproxy package installed.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+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 (e.g., key missions, functions). -+ -+The gssproxy package is a proxy for GSS API credential handling and could expose secrets on some networks. It is not needed for normal function of the OS. -+ -+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000381Remove the gssproxy package with the following command: -+ -+$ sudo dnf remove gssproxyVerify that the gssproxy package is not installed with the following command: -+ -+$ sudo dnf list --installed gssproxy -+ -+Error: No matching Packages to list -+ -+If the "gssproxy" package is installed and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215050RHEL 9 must not have the iprutils package installed.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+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 (e.g., key missions, functions). -+ -+The iprutils package provides a suite of utilities to manage and configure SCSI devices supported by the ipr SCSI storage device driver. -+ -+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000381Remove the iprutils package with the following command: -+ -+$ sudo dnf remove iprutilsVerify that the iprutils package is not installed with the following command: -+ -+$ sudo dnf list --installed iprutils -+ -+Error: No matching Packages to list -+ -+If the "iprutils" package is installed and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-215055RHEL 9 must not have the tuned package installed.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+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 (e.g., key missions, functions). -+ -+The tuned package 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. The tuned package is not needed for normal OS operations. -+ -+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000381Remove the tuned package with the following command: -+ -+$ sudo dnf remove tunedVerify that the tuned package is not installed with the following command: -+ -+$ sudo dnf list --installed tuned -+ -+Error: No matching Packages to list -+ -+If the "tuned" package is installed and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215060RHEL 9 must not have a Trivial File Transfer Protocol (TFTP) server package installed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366The tftp package can be removed with the following command: -+ -+$ sudo dnf remove tftpVerify that RHEL 9 does not have a tftp server package installed with the following command: -+ -+$ sudo dnf list --installed | grep tftp -+ -+If the "tftp" package is installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215065RHEL 9 must not have the quagga package installed.<VulnDiscussion>Quagga is a network routing software suite providing implementations of Open Shortest Path First (OSPF), Routing Information Protocol (RIP), Border Gateway Protocol (BGP) for Unix and Linux platforms. -+ -+If there is no need to make the router software available, removing it provides a safeguard against its activation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove the quagga package with the following command: -+ -+$ sudo dnf remove quaggaVerify that the quagga package is not installed with the following command: -+ -+$ sudo dnf list --installed quagga -+ -+Error: No matching Packages to list -+ -+If the "quagga" package is installed, and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215070A graphical display manager must not be installed on RHEL 9 unless approved.<VulnDiscussion>Unnecessary service packages must not be installed to decrease the attack surface of the system. Graphical display managers have a long history of security vulnerabilities and must not be used, unless approved and documented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Document the requirement for a graphical user interface with the ISSO or remove all xorg packages with the following command: -+ -+Warning: If you are accessing the system through the graphical user interface, change to the multi-user.target with the following command: -+ -+$ sudo systemctl isolate multi-user.target -+ -+Warning: Removal of the graphical user interface will immediately render it useless. The following commands must not be run from a virtual terminal emulator in the graphical interface. -+ -+$ sudo dnf remove "xorg*" -+$ sudo systemctl set-default multi-user.targetVerify that a graphical user interface is not installed with the following command: -+ -+$ sudo dnf list --installed "xorg*common" -+ -+Error: No matching Packages to list -+ -+If the "x11-server-common" package is installed, and the use of a graphical user interface has not been documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>RHEL-09-215075RHEL 9 must have the openssl-pkcs11 package installed.<VulnDiscussion>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. The DOD CAC with DOD-approved PKI is an example of multifactor authentication. -+ -+Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000375-GPOS-00160, SRG-OS-000376-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000765CCI-001948CCI-001953CCI-001954The openssl-pkcs11 package can be installed with the following command: -+ -+$ sudo dnf install openssl-pkcs11Verify that RHEL 9 has the openssl-pkcs11 package installed with the following command: -+ -+$ sudo dnf list --installed openssl-pkcs11 -+ -+Example output: -+ -+openssl-pkcs.i686 0.4.11-7.el9 -+openssl-pkcs.x86_64 0.4.11-7.el9 -+ -+If the "openssl-pkcs11" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215080RHEL 9 must have the gnutls-utils package installed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366The gnutls-utils package can be installed with the following command: -+ -+$ sudo dnf install gnutls-utilsVerify that RHEL 9 has the gnutls-utils package installed with the following command: -+ -+$ dnf list --installed gnutls-utils -+ -+Example output: -+ -+gnutls-utils.x86_64 3.7.3-9.el9 -+ -+If the "gnutls-utils" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215085RHEL 9 must have the nss-tools package installed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366The nss-tools package can be installed with the following command: -+ -+$ sudo dnf install nss-toolsVerify that RHEL 9 has the nss-tools package installed with the following command: -+ -+$ dnf list --installed nss-tools -+ -+Example output: -+ -+nss-tools.x86_64 3.71.0-7.el9 -+ -+If the "nss-tools" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-215090RHEL 9 must have the rng-tools package installed.<VulnDiscussion>"rng-tools" provides hardware random number generator tools, such as those used in the formation of x509/PKI certificates.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366The rng-tools package can be installed with the following command: -+ -+$ sudo dnf install rng-toolsVerify that RHEL 9 has the rng-tools package installed with the following command: -+ -+$ sudo dnf list --installed rng-tools -+ -+Example output: -+ -+rng-tools.x86_64 6.14-2.git.b2b7934e.el9 -+ -+If the "rng-tools" package is not installed, this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>RHEL-09-215095RHEL 9 must have the s-nail package installed.<VulnDiscussion>The "s-nail" package provides the mail command required to allow sending email notifications of unauthorized configuration changes to designated personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001744The s-nail package can be installed with the following command: -+ -+$ sudo dnf install s-nailVerify that RHEL 9 is configured to allow sending email notifications. -+ -+Note: The "s-nail" package provides the "mail" command that is used to send email messages. -+ -+Verify that the "s-nail" package is installed on the system: -+ -+$ sudo dnf list --installed mailx -+ -+s-nail.x86_64 14.9.22-6.el9 -+ -+If "s-nail" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231010A separate RHEL 9 file system must be used for user home directories (such as /home or an equivalent).<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Migrate the "/home" directory onto a separate file system/partition.Verify that a separate file system/partition has been created for "/home" with the following command: -+ -+$ mount | grep /home -+ -+UUID=fba5000f-2ffa-4417-90eb-8c54ae74a32f on /home type ext4 (rw,nodev,nosuid,noexec,seclabel) -+ -+If a separate entry for "/home" is not in use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231015RHEL 9 must use a separate file system for /tmp.<VulnDiscussion>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 that use it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Migrate the "/tmp" path onto a separate file system.Verify that a separate file system/partition has been created for "/tmp" with the following command: -+ -+$ mount | grep /tmp -+ -+tmpfs /tmp tmpfs noatime,mode=1777 0 0 -+ -+If a separate entry for "/tmp" is not in use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231020RHEL 9 must use a separate file system for /var.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Migrate the "/var" path onto a separate file system.Verify that a separate file system/partition has been created for "/var" with the following command: -+ -+$ mount | grep /var -+ -+UUID=c274f65f-c5b5-4481-b007-bee96feb8b05 /var xfs noatime 1 2 -+ -+If a separate entry for "/var" is not in use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231025RHEL 9 must use a separate file system for /var/log.<VulnDiscussion>Placing "/var/log" in its own partition enables better separation between log files and other files in "/var/".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Migrate the "/var/log" path onto a separate file system.Verify that a separate file system/partition has been created for "/var/log" with the following command: -+ -+$ mount | grep /var/log -+ -+UUID=c274f65f-c5b5-4486-b021-bee96feb8b21 /var/log xfs noatime 1 2 -+ -+If a separate entry for "/var/log" is not in use, this is a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>RHEL-09-231030RHEL 9 must use a separate file system for the system audit data path.<VulnDiscussion>Placing "/var/log/audit" in its own partition enables better separation between audit files and other system files, and helps ensure that auditing cannot be halted due to the partition running out of space. -+ -+Satisfies: SRG-OS-000341-GPOS-00132, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001849Migrate the system audit data path onto a separate file system.Verify that a separate file system/partition has been created for the system audit data path with the following command: -+ -+Note: /var/log/audit is used as the example as it is a common location. -+ -+$ mount | grep /var/log/audit -+ -+UUID=2efb2979-45ac-82d7-0ae632d11f51 on /var/log/home type xfs (rw,realtime,seclabel,attr2,inode64) -+ -+If no line is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231035RHEL 9 must use a separate file system for /var/tmp.<VulnDiscussion>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 that use it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Migrate the "/var/tmp" path onto a separate file system.Verify that a separate file system/partition has been created for "/var/tmp" with the following command: -+ -+$ mount | grep /var/tmp -+ -+UUID=c274f65f-c5b5-4379-b017-bee96feb7a34 /var/log xfs noatime 1 2 -+ -+If a separate entry for "/var/tmp" is not in use, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>RHEL-09-231040RHEL 9 file system automount function must be disabled unless required.<VulnDiscussion>An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. -+ -+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000778CCI-001958Configure RHEL 9 to disable the ability to automount devices. -+ -+The autofs service can be disabled with the following command: -+ -+$ sudo systemctl mask --now autofs.serviceVerify that RHEL 9 file system automount function has been disabled with the following command: -+ -+$ sudo systemctl is-enabled autofs -+ -+masked -+ -+If the returned value is not "masked", "disabled", "Failed to get unit file state for autofs.service for autofs", or "enabled", and is not documented as operational requirement with the information system security officer ISSO, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231045RHEL 9 must prevent device files from being interpreted on file systems that contain user home directories.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/home" directory.Verify "/home" is mounted with the "nodev" option with the following command: -+ -+Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is automatically a finding, as the "nodev" option cannot be used on the "/" system. -+ -+$ mount | grep /home -+ -+tmpfs on /home type tmpfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/home" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231050RHEL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that contain user home directories.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/home" directory.Verify "/home" is mounted with the "nosuid" option with the following command: -+ -+Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is automatically a finding, as the "nosuid" option cannot be used on the "/" system. -+ -+$ mount | grep /home -+ -+tmpfs on /home type tmpfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/home" file system is mounted without the "nosuid" option, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231055RHEL 9 must prevent code from being executed on file systems that contain user home directories.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Modify "/etc/fstab" to use the "noexec" option on the "/home" directory.Verify "/home" is mounted with the "noexec" option with the following command: -+ -+Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is automatically a finding, as the "noexec" option cannot be used on the "/" system. -+ -+$ mount | grep /home -+ -+tmpfs on /home type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/home" file system is mounted without the "noexec" option, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231060RHEL 9 must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS.<VulnDiscussion>When an NFS server is configured to use RPCSEC_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Update the "/etc/fstab" file so the option "sec" is defined for each NFS mounted file system and the "sec" option does not have the "sys" setting. -+ -+Ensure the "sec" option is defined as "krb5p:krb5i:krb5".Verify RHEL 9 has the "sec" option configured for all NFS mounts with the following command: -+ -+Note: If no NFS mounts are configured, this requirement is Not Applicable. -+ -+$ cat /etc/fstab | grep nfs -+ -+192.168.22.2:/mnt/export /data nfs4 rw,nosuid,nodev,noexec,sync,soft,sec=krb5p:krb5i:krb5 -+ -+If the system is mounting file systems via NFS and has the sec option without the "krb5:krb5i:krb5p" settings, the "sec" option has the "sys" setting, or the "sec" option is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231065RHEL 9 must prevent special devices on file systems that are imported via Network File System (NFS).<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Update each NFS mounted file system to use the "nodev" option on file systems that are being imported via NFS.Verify RHEL 9 has the "nodev" option configured for all NFS mounts with the following command: -+ -+$ cat /etc/fstab | grep nfs -+ -+192.168.22.2:/mnt/export /data nfs4 rw,nosuid,nodev,noexec,sync,soft,sec=krb5:krb5i:krb5p -+ -+Note: If no NFS mounts are configured, this requirement is Not Applicable. -+ -+If the system is mounting file systems via NFS and the "nodev" option is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231070RHEL 9 must prevent code from being executed on file systems that are imported via Network File System (NFS).<VulnDiscussion>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 as they may be incompatible. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Update each NFS mounted file system to use the "noexec" option on file systems that are being imported via NFS.Verify RHEL 9 has the "noexec" option configured for all NFS mounts with the following command: -+ -+$ cat /etc/fstab | grep nfs -+ -+192.168.22.2:/mnt/export /data nfs4 rw,nosuid,nodev,noexec,sync,soft,sec=krb5:krb5i:krb5p -+ -+If no NFS mounts are configured, this requirement is Not Applicable. -+ -+If the system is mounting file systems via NFS and the "noexec" option is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231075RHEL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that are imported via Network File System (NFS).<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Update each NFS mounted file system to use the "nosuid" option on file systems that are being imported via NFS.Verify RHEL 9 has the "nosuid" option configured for all NFS mounts with the following command: -+ -+Note: If no NFS mounts are configured, this requirement is Not Applicable. -+ -+$ cat /etc/fstab | grep nfs -+ -+192.168.22.2:/mnt/export /data nfs4 rw,nosuid,nodev,noexec,sync,soft,sec=krb5:krb5i:krb5p -+ -+If the system is mounting file systems via NFS and the "nosuid" option is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231080RHEL 9 must prevent code from being executed on file systems that are used with removable media.<VulnDiscussion>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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/fstab" to use the "noexec" option on file systems that are associated with removable media.Verify file systems that are used for removable media are mounted with the "noexec" option with the following command: -+ -+$ more /etc/fstab -+ -+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 -+ -+If a file system found in "/etc/fstab" refers to removable media and it does not have the "noexec" option set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231085RHEL 9 must prevent special devices on file systems that are used with removable media.<VulnDiscussion>The "nodev" mount option causes the system not to interpret character or block special devices. Executing character or blocking special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/fstab" to use the "nodev" option on file systems that are associated with removable media.Verify file systems that are used for removable media are mounted with the "nodev" option with the following command: -+ -+$ more /etc/fstab -+ -+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 -+ -+If a file system found in "/etc/fstab" refers to removable media and it does not have the "nodev" option set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231090RHEL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media.<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/fstab" to use the "nosuid" option on file systems that are associated with removable media.Verify file systems that are used for removable media are mounted with the "nosuid" option with the following command: -+ -+$ more /etc/fstab -+ -+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 -+ -+If a file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231095RHEL 9 must mount /boot with the nodev option.<VulnDiscussion>The only legitimate location for device files is the "/dev" directory located on the root partition. The only exception to this is chroot jails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/boot" directory.Verify that the "/boot" mount point has the "nodev" option is with the following command: -+ -+Note: This control is not applicable to RHEL 9 system booted UEFI. -+ -+$ sudo mount | grep '\s/boot\s' -+ -+/dev/sda1 on /boot type xfs (rw,nodev,relatime,seclabel,attr2) -+ -+If the "/boot" file system does not have the "nodev" option set, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231100RHEL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot directory.<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/boot" directory.Note: For systems that use UEFI, this requirement is Not Applicable. -+ -+Verify the /boot directory is mounted with the "nosuid" option with the following command: -+ -+$ mount | grep '\s/boot\s' -+ -+/dev/sda1 on /boot type xfs (rw,nosuid,relatime,seclabe,attr2,inode64,noquota) -+ -+If the /boot file system does not have the "nosuid" option set, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231105RHEL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory.<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/boot/efi" directory.Note: For systems that use BIOS, this requirement is Not Applicable. -+ -+Verify the /boot/efi directory is mounted with the "nosuid" option with the following command: -+ -+$ mount | grep '\s/boot/efi\s' -+ -+/dev/sda1 on /boot/efi type vfat (rw,nosuid,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) -+ -+If the /boot/efi file system does not have the "nosuid" option set, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231110RHEL 9 must mount /dev/shm with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/dev/shm" file system.Verify "/dev/shm" is mounted with the "nodev" option with the following command: -+ -+$ mount | grep /dev/shm -+ -+tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the /dev/shm file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231115RHEL 9 must mount /dev/shm with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "noexec" option on the "/dev/shm" file system.Verify "/dev/shm" is mounted with the "noexec" option with the following command: -+ -+$ mount | grep /dev/shm -+ -+tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the /dev/shm file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231120RHEL 9 must mount /dev/shm with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/dev/shm" file system.Verify "/dev/shm" is mounted with the "nosuid" option with the following command: -+ -+$ mount | grep /dev/shm -+ -+tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the /dev/shm file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231125RHEL 9 must mount /tmp with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/tmp" directory.Verify "/tmp" is mounted with the "nodev" option: -+ -+$ mount | grep /tmp -+ -+/dev/mapper/rhel-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/tmp" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231130RHEL 9 must mount /tmp with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "noexec" option on the "/tmp" directory.Verify "/tmp" is mounted with the "noexec" option: -+ -+$ mount | grep /tmp -+ -+/dev/mapper/rhel-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/tmp" file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231135RHEL 9 must mount /tmp with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/tmp" directory.Verify "/tmp" is mounted with the "nosuid" option: -+ -+$ mount | grep /tmp -+ -+/dev/mapper/rhel-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/tmp" file system is mounted without the "nosuid" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231140RHEL 9 must mount /var with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/var" directory.Verify "/var" is mounted with the "nodev" option: -+ -+$ mount | grep /var -+ -+/dev/mapper/rhel-var on /var type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231145RHEL 9 must mount /var/log with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/var/log" directory.Verify "/var/log" is mounted with the "nodev" option: -+ -+$ mount | grep /var/log -+ -+/dev/mapper/rhel-var-log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231150RHEL 9 must mount /var/log with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "noexec" option on the "/var/log" directory.Verify "/var/log" is mounted with the "noexec" option: -+ -+$ mount | grep /var/log -+ -+/dev/mapper/rhel-var-log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log" file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231155RHEL 9 must mount /var/log with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/var/log" directory.Verify "/var/log" is mounted with the "nosuid" option: -+ -+$ mount | grep /var/log -+ -+/dev/mapper/rhel-var-log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log" file system is mounted without the "nosuid" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231160RHEL 9 must mount /var/log/audit with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/var/log/audit" directory.Verify "/var/log/audit" is mounted with the "nodev" option: -+ -+$ mount | grep /var/log/audit -+ -+/dev/mapper/rhel-var-log-audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log/audit" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231165RHEL 9 must mount /var/log/audit with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "noexec" option on the "/var/log/audit" directory.Verify "/var/log/audit" is mounted with the "noexec" option: -+ -+$ mount | grep /var/log/audit -+ -+/dev/mapper/rhel-var-log-audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log/audit" file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231170RHEL 9 must mount /var/log/audit with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/var/log/audit" directory.Verify "/var/log/audit" is mounted with the "nosuid" option: -+ -+$ mount | grep /var/log/audit -+ -+/dev/mapper/rhel-var-log-audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/log/audit" file system is mounted without the "nosuid" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231175RHEL 9 must mount /var/tmp with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nodev" option on the "/var/tmp" directory.Verify "/var/tmp" is mounted with the "nodev" option: -+ -+$ mount | grep /var/tmp -+ -+/dev/mapper/rhel-var-tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/tmp" file system is mounted without the "nodev" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231180RHEL 9 must mount /var/tmp with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system to not 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 nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "noexec" option on the "/var/tmp" directory.Verify "/var/tmp" is mounted with the "noexec" option: -+ -+$ mount | grep /var/tmp -+ -+/dev/mapper/rhel-var-tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/tmp" file system is mounted without the "noexec" option, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-231185RHEL 9 must mount /var/tmp with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Modify "/etc/fstab" to use the "nosuid" option on the "/var/tmp" directory.Verify "/var/tmp" is mounted with the "nosuid" option: -+ -+$ mount | grep /var/tmp -+ -+/dev/mapper/rhel-var-tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) -+ -+If the "/var/tmp" file system is mounted without the "nosuid" option, this is a finding.SRG-OS-000405-GPOS-00184<GroupDescription></GroupDescription>RHEL-09-231190RHEL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection.<VulnDiscussion>RHEL 9 systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. -+ -+Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). -+ -+Satisfies: SRG-OS-000405-GPOS-00184, SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001199CCI-002475CCI-002476Configure RHEL 9 to prevent unauthorized modification of all information at rest by using disk encryption. -+ -+Encrypting a partition in an already installed system is more difficult, because existing partitions will need to be resized and changed. -+ -+To encrypt an entire partition, dedicate a partition for encryption in the partition layout.Verify RHEL 9 prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption. -+ -+Note: If there is a documented and approved reason for not having data-at-rest encryption, this requirement is Not Applicable. -+ -+Verify all system partitions are encrypted with the following command: -+ -+$ blkid -+ -+/dev/map per/rhel-root: UUID="67b7d7fe-de60-6fd0-befb-e6748cf97743" TYPE="crypto_LUKS" -+ -+Every persistent disk partition present must be of type "crypto_LUKS". If any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) or temporary file systems (that are tmpfs) are not type "crypto_LUKS", ask the administrator to indicate how the partitions are encrypted. If there is no evidence that these partitions are encrypted, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-231195RHEL 9 must disable mounting of cramfs.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission 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. -+ -+Removing support for unneeded filesystem types reduces the local attack surface of the server. -+ -+Compressed ROM/RAM file system (or cramfs) is a read-only file system designed for simplicity and space-efficiency. It is mainly used in embedded and small-footprint systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381To configure the system to prevent the cramfs kernel module from being loaded, add the following line to the file /etc/modprobe.d/blacklist.conf (or create blacklist.conf if it does not exist): -+ -+install tipc /bin/false -+blacklist cramfsVerify that RHEL 9 disables the ability to load the cramfs kernel module with the following command: -+ -+$ sudo grep -r cramfs /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist cramfs -+ -+If the command does not return any output, or the line is commented out, and use of cramfs is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-231200RHEL 9 must prevent special devices on non-root local partitions.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access. -+ -+The only legitimate location for device files is the "/dev" directory located on the root partition, with the exception of chroot jails if implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/fstab" to use the "nodev" option on all non-root local partitions.Verify all non-root local partitions are mounted with the "nodev" option with the following command: -+ -+$ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev' -+ -+If any output is produced, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232010RHEL 9 system commands must have mode 755 or less permissive.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system commands to be protected from unauthorized access. -+ -+Run the following command, replacing "[FILE]" with any system command with a mode more permissive than "755". -+ -+$ sudo chmod 755 [FILE]Verify the system commands contained in the following directories have mode "755" or less permissive with the following command: -+ -+$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/libexec /usr/local/bin /usr/local/sbin -perm /022 -exec ls -l {} \; -+ -+If any system commands are found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232015RHEL 9 library directories must have mode 755 or less permissive.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system-wide shared library directories (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. -+ -+Run the following command, replacing "[DIRECTORY]" with any library directory with a mode more permissive than 755. -+ -+$ sudo chmod 755 [DIRECTORY]Verify the system-wide shared library directories have mode "755" or less permissive with the following command: -+ -+$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type d -exec ls -l {} \; -+ -+If any system-wide shared library file is found to be group-writable or world-writable, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232020RHEL 9 library files must have mode 755 or less permissive.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the library files to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any library file with a mode more permissive than 755. -+ -+$ sudo chmod 755 [FILE]Verify the system-wide shared library files contained in the following directories have mode "755" or less permissive with the following command: -+ -+$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec ls -l {} \; -+ -+If any system-wide shared library file is found to be group-writable or world-writable, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232025RHEL 9 /var/log directory must have mode 0755 or less permissive.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Configure the "/var/log" directory to a mode of "0755" by running the following command: -+ -+$ sudo chmod 0755 /var/logVerify that the "/var/log" directory has a mode of "0755" or less permissive with the following command: -+ -+$ ls -ld /var/log -+ -+drwxr-xr-x. 16 root root 4096 July 11 11:34 /var/log -+ -+If "/var/log" does not have a mode of "0755" or less permissive, this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232030RHEL 9 /var/log/messages file must have mode 0640 or less permissive.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Configure the "/var/log/messages" file to have a mode of "0640" by running the following command: -+ -+$ sudo chmod 0640 /var/log/messagesVerify the "/var/log/messages" file has a mode of "0640" or less permissive with the following command: -+ -+$ ls -la /var/log/messages -+ -+rw-------. 1 root root 564223 July 11 11:34 /var/log/messages -+ -+If "/var/log/messages" does not have a mode of "0640" or less permissive, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>RHEL-09-232035RHEL 9 audit tools must have a mode of 0755 or less permissive.<VulnDiscussion>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 operation on audit information. -+ -+RHEL 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001493Configure the audit tools to have a mode of "0755" by running the following command: -+ -+$ sudo chmod 0755 [audit_tool] -+ -+Replace "[audit_tool]" with each audit tool that has a more permissive mode than 0755.Verify the audit tools have a mode of "0755" or less with the following command: -+ -+$ stat -c "%a %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules -+ -+755 /sbin/auditctl -+755 /sbin/aureport -+755 /sbin/ausearch -+750 /sbin/autrace -+755 /sbin/auditd -+755 /sbin/rsyslogd -+755 /sbin/augenrules -+ -+If any of the audit tool files have a mode more permissive than "0755", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232040RHEL 9 cron configuration directories must have a mode of 0700 or less permissive.<VulnDiscussion>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 have the correct access rights to prevent unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure any RHEL 9 cron configuration directory with a mode more permissive than "0700" as follows: -+ -+chmod 0700 [cron configuration directory]Verify the permissions of the cron directories with the following command: -+ -+$ find /etc/cron* -type d | xargs stat -c "%a %n" -+ -+700 /etc/cron.d -+700 /etc/cron.daily -+700 /etc/cron.hourly -+700 /etc/cron.monthly -+700 /etc/cron.weekly -+ -+If any cron configuration directory is more permissive than "700", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232045All RHEL 9 local initialization files must have mode 0740 or less permissive.<VulnDiscussion>Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Set the mode of the local initialization files to "0740" with the following command: -+ -+Note: The example will be for the wadea user, who has a home directory of "/home/wadea". -+ -+$ sudo chmod 0740 /home/wadea/.<INIT_FILE>Verify that all local initialization files have a mode of "0740" or less permissive with the following command: -+ -+Note: The example will be for the "wadea" user, who has a home directory of "/home/wadea". -+ -+$ sudo ls -al /home/wadea/.[^.]* | more -+ -+-rwxr-xr-x 1 wadea users 896 Mar 10 2011 .profile -+-rwxr-xr-x 1 wadea users 497 Jan 6 2007 .login -+-rwxr-xr-x 1 wadea users 886 Jan 6 2007 .something -+ -+If any local initialization files have a mode more permissive than "0740", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232050All RHEL 9 local interactive user home directories must have mode 0750 or less permissive.<VulnDiscussion>Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of interactive user's home directories to "0750". To change the mode of a local interactive user's home directory, use the following command: -+ -+Note: The example will be for the user "wadea". -+ -+$ sudo chmod 0750 /home/wadeaVerify the assigned home directory of all local interactive users has a mode of "0750" or less permissive with the following command: -+ -+Note: This may miss interactive users that have been assigned a privileged user identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. -+ -+$ sudo ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) -+ -+drwxr-x--- 2 wadea admin 4096 Jun 5 12:41 wadea -+ -+If home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232055RHEL 9 /etc/group file must have mode 0644 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/group" to "0644" by running the following command: -+ -+$ sudo chmod 0644 /etc/groupVerify that the "/etc/group" file has mode "0644" or less permissive with the following command: -+ -+$ sudo stat -c "%a %n" /etc/group -+ -+644 /etc/group -+ -+If a value of "0644" or less permissive is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232060RHEL 9 /etc/group- file must have mode 0644 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/group-" to "0644" by running the following command: -+ -+$ sudo chmod 0644 /etc/group-Verify that the "/etc/group-" file has mode "0644" or less permissive with the following command: -+ -+$ sudo stat -c "%a %n" /etc/group- -+ -+644 /etc/group- -+ -+If a value of "0644" or less permissive is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232065RHEL 9 /etc/gshadow file must have mode 0000 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/gshadow" to "0000" by running the following command: -+ -+$ sudo chmod 0000 /etc/gshadowVerify that the "/etc/gshadow" file has mode "0000" with the following command: -+ -+$ sudo stat -c "%a %n" /etc/gshadow -+ -+0 /etc/gshadow -+ -+If a value of "0" is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232070RHEL 9 /etc/gshadow- file must have mode 0000 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/gshadow-" to "0000" by running the following command: -+ -+$ sudo chmod 0000 /etc/gshadow-Verify that the "/etc/gshadow-" file has mode "0000" with the following command: -+ -+$ sudo stat -c "%a %n" /etc/gshadow- -+ -+0 /etc/gshadow- -+ -+If a value of "0" is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232075RHEL 9 /etc/passwd file must have mode 0644 or less permissive to prevent unauthorized access.<VulnDiscussion>If the "/etc/passwd" file is writable by a group-owner or the world the risk of its compromise is increased. The file contains the list of accounts on the system and associated information, and protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/passwd" to "0644" by running the following command: -+ -+$ sudo chmod 0644 /etc/passwdVerify that the "/etc/passwd" file has mode "0644" or less permissive with the following command: -+ -+$ sudo stat -c "%a %n" /etc/passwd -+ -+644 /etc/passwd -+ -+If a value of "0644" or less permissive is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232080RHEL 9 /etc/passwd- file must have mode 0644 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/passwd-" to "0644" by running the following command: -+ -+$ sudo chmod 0644 /etc/passwd-Verify that the "/etc/passwd-" file has mode "0644" or less permissive with the following command: -+ -+$ sudo stat -c "%a %n" /etc/passwd- -+ -+644 /etc/passwd- -+ -+If a value of "0644" or less permissive is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232085RHEL 9 /etc/shadow- file must have mode 0000 or less permissive to prevent unauthorized access.<VulnDiscussion>The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/shadow-" to "0000" by running the following command: -+ -+$ sudo chmod 0000 /etc/shadow-Verify that the "/etc/shadow-" file has mode "0000" with the following command: -+ -+$ sudo stat -c "%a %n" /etc/shadow- -+ -+0 /etc/shadow- -+ -+If a value of "0" is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232090RHEL 9 /etc/group file must be owned by root.<VulnDiscussion>The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/group to root by running the following command: -+ -+$ sudo chown root /etc/groupVerify the ownership of the "/etc/group" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/group -+ -+root /etc/group -+ -+If "/etc/group" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232095RHEL 9 /etc/group file must be group-owned by root.<VulnDiscussion>The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/group to root by running the following command: -+ -+$ sudo chgrp root /etc/groupVerify the group ownership of the "/etc/group" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/group -+ -+root /etc/group -+ -+If "/etc/group" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232100RHEL 9 /etc/group- file must be owned by root.<VulnDiscussion>The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/group- to root by running the following command: -+ -+$ sudo chown root /etc/group-Verify the ownership of the "/etc/group-" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/group- -+ -+root /etc/group- -+ -+If "/etc/group-" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232105RHEL 9 /etc/group- file must be group-owned by root.<VulnDiscussion>The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protection of this file is important for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/group- to root by running the following command: -+ -+$ sudo chgrp root /etc/group-Verify the group ownership of the "/etc/group-" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/group- -+ -+root /etc/group- -+ -+If "/etc/group-" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232110RHEL 9 /etc/gshadow file must be owned by root.<VulnDiscussion>The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/gshadow to root by running the following command: -+ -+$ sudo chown root /etc/gshadowVerify the ownership of the "/etc/gshadow" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/gshadow -+ -+root /etc/gshadow -+ -+If "/etc/gshadow" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232115RHEL 9 /etc/gshadow file must be group-owned by root.<VulnDiscussion>The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/gshadow to root by running the following command: -+ -+$ sudo chgrp root /etc/gshadowVerify the group ownership of the "/etc/gshadow" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/gshadow -+ -+root /etc/gshadow -+ -+If "/etc/gshadow" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232120RHEL 9 /etc/gshadow- file must be owned by root.<VulnDiscussion>The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/gshadow- to root by running the following command: -+ -+$ sudo chown root /etc/gshadow-Verify the ownership of the "/etc/gshadow-" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/gshadow- -+ -+root /etc/gshadow- -+ -+If "/etc/gshadow-" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232125RHEL 9 /etc/gshadow- file must be group-owned by root.<VulnDiscussion>The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/gshadow- to root by running the following command: -+ -+$ sudo chgrp root /etc/gshadow-Verify the group ownership of the "/etc/gshadow-" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/gshadow- -+ -+root /etc/gshadow- -+ -+If "/etc/gshadow-" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232130RHEL 9 /etc/passwd file must be owned by root.<VulnDiscussion>The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/passwd to root by running the following command: -+ -+$ sudo chown root /etc/passwdVerify the ownership of the "/etc/passwd" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/passwd -+ -+root /etc/passwd -+ -+If "/etc/passwd" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232135RHEL 9 /etc/passwd file must be group-owned by root.<VulnDiscussion>The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/passwd to root by running the following command: -+ -+$ sudo chgrp root /etc/passwdVerify the group ownership of the "/etc/passwd" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/passwd -+ -+root /etc/passwd -+ -+If "/etc/passwd" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232140RHEL 9 /etc/passwd- file must be owned by root.<VulnDiscussion>The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/passwd- to root by running the following command: -+ -+$ sudo chown root /etc/passwd-Verify the ownership of the "/etc/passwd-" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/passwd- -+ -+root /etc/passwd- -+ -+If "/etc/passwd-" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232145RHEL 9 /etc/passwd- file must be group-owned by root.<VulnDiscussion>The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/passwd- to root by running the following command: -+ -+$ sudo chgrp root /etc/passwd-Verify the group ownership of the "/etc/passwd-" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/passwd- -+ -+root /etc/passwd- -+ -+If "/etc/passwd-" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232150RHEL 9 /etc/shadow file must be owned by root.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/shadow to root by running the following command: -+ -+$ sudo chown root /etc/shadowVerify the ownership of the "/etc/shadow" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/shadow -+ -+root /etc/shadow -+ -+If "/etc/shadow" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232155RHEL 9 /etc/shadow file must be group-owned by root.<VulnDiscussion>The "/etc/shadow" file stores password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/shadow to root by running the following command: -+ -+$ sudo chgrp root /etc/shadowVerify the group ownership of the "/etc/shadow" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/shadow -+ -+root /etc/shadow -+ -+If "/etc/shadow" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232160RHEL 9 /etc/shadow- file must be owned by root.<VulnDiscussion>The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the owner of the file /etc/shadow- to root by running the following command: -+ -+$ sudo chown root /etc/shadow-Verify the ownership of the "/etc/shadow-" file with the following command: -+ -+$ sudo stat -c "%U %n" /etc/shadow- -+ -+root /etc/shadow- -+ -+If "/etc/shadow-" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232165RHEL 9 /etc/shadow- file must be group-owned by root.<VulnDiscussion>The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of this file is critical for system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group of the file /etc/shadow- to root by running the following command: -+ -+$ sudo chgrp root /etc/shadow-Verify the group ownership of the "/etc/shadow-" file with the following command: -+ -+$ sudo stat -c "%G %n" /etc/shadow- -+ -+root /etc/shadow- -+ -+If "/etc/shadow-" file does not have a group owner of "root", this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232170RHEL 9 /var/log directory must be owned by root.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Configure the owner of the directory "/var/log" to "root" by running the following command: -+ -+$ sudo chown root /var/logVerify the "/var/log" directory is owned by root with the following command: -+ -+$ ls -ld /var/log -+ -+drwxr-xr-x. 16 root root 4096 July 11 11:34 /var/log -+ -+If "/var/log" does not have an owner of "root", this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232175RHEL 9 /var/log directory must be group-owned by root.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Configure the group owner of the directory "/var/log" to "root" by running the following command: -+ -+$ sudo chgrp root /var/logVerify the "/var/log" directory is group-owned by root with the following command: -+ -+$ ls -ld /var/log -+ -+drwxr-xr-x. 16 root root 4096 July 11 11:34 /var/log -+ -+If "/var/log" does not have a group owner of "root", this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232180RHEL 9 /var/log/messages file must be owned by root.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Change the owner of the "/var/log/messages" file to "root" by running the following command: -+ -+$ sudo chown root /var/log/messagesVerify the "/var/log/messages" file is owned by root with the following command: -+ -+$ ls -la /var/log/messages -+ -+rw-------. 1 root root 564223 July 11 11:34 /var/log/messages -+ -+If "/var/log/messages" does not have an owner of "root", this is a finding.SRG-OS-000206-GPOS-00084<GroupDescription></GroupDescription>RHEL-09-232185RHEL 9 /var/log/messages file must be group-owned by root.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001314Change the group owner of the "/var/log/messages" file to "root" by running the following command: -+ -+$ sudo chgrp root /var/log/messagesVerify the "/var/log/messages" file is group-owned by root with the following command: -+ -+$ ls -la /var/log/messages -+ -+rw-------. 1 root root 564223 July 11 11:34 /var/log/messages -+ -+If "/var/log/messages" does not have a group owner of "root", this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232190RHEL 9 system commands must be owned by root.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system commands to be protected from unauthorized access. -+ -+Run the following command, replacing "[FILE]" with any system command file not owned by "root". -+ -+$ sudo chown root [FILE]Verify the system commands contained in the following directories are owned by "root" with the following command: -+ -+$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/libexec /usr/local/bin /usr/local/sbin ! -user root -exec ls -l {} \; -+ -+If any system commands are found to not be owned by root, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232195RHEL 9 system commands must be group-owned by root or a system account.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system commands to be protected from unauthorized access. -+ -+Run the following command, replacing "[FILE]" with any system command file not group-owned by "root" or a required system account. -+ -+$ sudo chgrp root [FILE]Verify the system commands contained in the following directories are group-owned by "root", or a required system account, with the following command: -+ -+$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -exec ls -l {} \; -+ -+If any system commands are returned and is not group-owned by a required system account, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232200RHEL 9 library files must be owned by root.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system-wide shared library files (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. -+ -+Run the following command, replacing "[FILE]" with any library file not owned by "root". -+ -+$ sudo chown root [FILE]Verify the system-wide shared library files are owned by "root" with the following command: -+ -+$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -user root -exec ls -l {} \; -+ -+If any system-wide shared library file is not owned by root, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232205RHEL 9 library files must be group-owned by root or a system account.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system-wide shared library files (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. -+ -+Run the following command, replacing "[FILE]" with any library file not group-owned by "root". -+ -+$ sudo chgrp root [FILE]Verify the system-wide shared library files are group-owned by "root" with the following command: -+ -+$ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -group root -exec ls -l {} \; -+ -+If any system-wide shared library file is returned and is not group-owned by a required system account, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232210RHEL 9 library directories must be owned by root.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system-wide shared library directories within (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. -+ -+Run the following command, replacing "[DIRECTORY]" with any library directory not owned by "root". -+ -+$ sudo chown root [DIRECTORY]Verify the system-wide shared library directories are owned by "root" with the following command: -+ -+$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; -+ -+If any system-wide shared library directory is not owned by root, this is a finding.SRG-OS-000259-GPOS-00100<GroupDescription></GroupDescription>RHEL-09-232215RHEL 9 library directories must be group-owned by root or a system account.<VulnDiscussion>If RHEL 9 allowed 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 RHEL 9 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001499Configure the system-wide shared library directories (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. -+ -+Run the following command, replacing "[DIRECTORY]" with any library directory not group-owned by "root". -+ -+$ sudo chgrp root [DIRECTORY]Verify the system-wide shared library directories are group-owned by "root" with the following command: -+ -+$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; -+ -+If any system-wide shared library directory is returned and is not group-owned by a required system account, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>RHEL-09-232220RHEL 9 audit tools must be owned by root.<VulnDiscussion>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 operation on audit information. -+ -+RHEL 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001493Configure the audit tools to be owned by "root" by running the following command: -+ -+$ sudo chown root [audit_tool] -+ -+Replace "[audit_tool]" with each audit tool not owned by "root".Verify the audit tools are owned by "root" with the following command: -+ -+$ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules -+ -+root /sbin/auditctl -+root /sbin/aureport -+root /sbin/ausearch -+root /sbin/autrace -+root /sbin/auditd -+root /sbin/rsyslogd -+root /sbin/augenrules -+ -+If any audit tools do not have an owner of "root", this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>RHEL-09-232225RHEL 9 audit tools must be group-owned by root.<VulnDiscussion>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 operation on audit information. -+ -+RHEL 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001493Configure the audit tools to be group-owned by "root" by running the following command: -+ -+$ sudo chgrp root [audit_tool] -+ -+Replace "[audit_tool]" with each audit tool not group-owned by "root".Verify the audit tools are group owned by "root" with the following command: -+ -+$ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules -+ -+root /sbin/auditctl -+root /sbin/aureport -+root /sbin/ausearch -+root /sbin/autrace -+root /sbin/auditd -+root /sbin/rsyslogd -+root /sbin/augenrules -+ -+If any audit tools do not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232230RHEL 9 cron configuration files directory must be owned by root.<VulnDiscussion>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 must be owned by the correct group to prevent unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure any cron configuration not owned by root with the following command: -+ -+$ sudo chown root [cron config file]Verify the ownership of all cron configuration files with the command: -+ -+$ stat -c "%U %n" /etc/cron* -+ -+root /etc/cron.d -+root /etc/cron.daily -+root /etc/cron.deny -+root /etc/cron.hourly -+root /etc/cron.monthly -+root /etc/crontab -+root /etc/cron.weekly -+ -+If any crontab is not owned by root, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232235RHEL 9 cron configuration files directory must be group-owned by root.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure any cron configuration not group-owned by root with the following command: -+ -+$ sudo chgrp root [cron config file]Verify the group ownership of all cron configuration files with the following command: -+ -+$ stat -c "%G %n" /etc/cron* -+ -+root /etc/cron.d -+root /etc/cron.daily -+root /etc/cron.deny -+root /etc/cron.hourly -+root /etc/cron.monthly -+root /etc/crontab -+root /etc/cron.weekly -+ -+If any crontab is not group owned by root, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232240All RHEL 9 world-writable directories must be owned by root, sys, bin, or an application user.<VulnDiscussion>If a world-writable directory is not owned by root, sys, bin, or an application user identifier (UID), unauthorized users may be able to modify files created by others. -+ -+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 and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000138-GPOS-00069</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001090Configure all public directories to be owned by root or a system account to prevent unauthorized and unintended information transferred via shared system resources. -+ -+Set the owner of all public directories as root or a system account using the command, replace "[Public Directory]" with any directory path not owned by root or a system account: -+ -+$ sudo chown root [Public Directory]Verify that world writable directories are owned by root, a system account, or an application account with the following command. It will discover and print world-writable directories that are not owned by root. Run it once for each local partition [PART]: -+ -+$ sudo find PART -xdev -type d -perm -0002 -uid +0 -print -+ -+If there is output, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>RHEL-09-232245A sticky bit must be set on all RHEL 9 public directories.<VulnDiscussion>Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. -+ -+This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DOD or other government agencies.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001090Configure all world-writable directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources. -+ -+Set the sticky bit on all world-writable directories using the command, replace "[World-Writable Directory]" with any directory path missing the sticky bit: -+ -+$ chmod a+t [World-Writable Directory]Verify that all world-writable directories have the sticky bit set. -+ -+Determine if all world-writable directories have the sticky bit set by running the following command: -+ -+$ sudo find / -type d \( -perm -0002 -a ! -perm -1000 \) -print 2>/dev/null -+ -+drwxrwxrwt 7 root root 4096 Jul 26 11:19 /tmp -+ -+If any of the returned directories are world-writable and do not have the sticky bit set, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232250All RHEL 9 local files and directories must have a valid group owner.<VulnDiscussion>Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Either remove all files and directories from RHEL 9 that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command: -+ -+$ sudo chgrp <group> <file>Verify all local files and directories on RHEL 9 have a valid group with the following command: -+ -+$ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nogroup -+ -+If any files on the system do not have an assigned group, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232255All RHEL 9 local files and directories must have a valid owner.<VulnDiscussion>Unowned files and directories may be unintentionally inherited if a user is assigned the same user identifier "UID" as the UID of the unowned files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on RHEL 9 with the "chown" command: -+ -+$ sudo chown <user> <file>Verify all local files and directories on RHEL 9 have a valid owner with the following command: -+ -+$ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nouser -+ -+If any files on the system do not have an assigned owner, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232260RHEL 9 must be configured so that all system device files are correctly labeled to prevent unauthorized modification.<VulnDiscussion>If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Restore the SELinux policy for the affected device file from the system policy database using the following command: -+ -+$ sudo restorecon -v <device_path> -+ -+Substituting "<device_path>" with the path to the affected device file (from the output of the previous commands). An example device file path would be "/dev/ttyUSB0". If the output of the above command does not indicate that the device was relabeled to a more specific SELinux type label, then the SELinux policy of the system must be updated with more specific policy for the device class specified. If a package was used to install support for a device class, that package could be reinstalled using the following command: -+ -+$ sudo dnf reinstall <package_name> -+ -+If a package was not used to install the SELinux policy for a given device class, then it must be generated manually and provide specific type labels.Verify that all system device files are correctly labeled to prevent unauthorized modification. -+ -+List all device files on the system that are incorrectly labeled with the following commands: -+ -+Note: Device files are normally found under "/dev", but applications may place device files in other directories and may necessitate a search of the entire system. -+ -+# find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n" -+ -+# find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n" -+ -+Note: There are device files, such as "/dev/vmci", that are used when the operating system is a host virtual machine. They will not be owned by a user on the system and require the "device_t" label to operate. These device files are not a finding. -+ -+If there is output from either of these commands, other than already noted, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232265RHEL 9 /etc/crontab file must have mode 0600.<VulnDiscussion>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 must have the correct access rights to prevent unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the RHEL 9 file /etc/crontab with mode 600. -+ -+$ sudo chmod 0600 /etc/crontabVerify the permissions of /etc/crontab with the following command: -+ -+$ stat -c "%a %n" /etc/crontab -+ -+0600 -+ -+If /etc/crontab does not have a mode of "0600", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-232270RHEL 9 /etc/shadow file must have mode 0000 to prevent unauthorized access.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of the file "/etc/shadow" to "0000" by running the following command: -+ -+$ sudo chmod 0000 /etc/shadowVerify that the "/etc/shadow" file has mode "0000" with the following command: -+ -+$ sudo stat -c "%a %n" /etc/shadow -+ -+0 /etc/shadow -+ -+If a value of "0" is not returned, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-251010RHEL 9 must have the firewalld package installed.<VulnDiscussion>"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 DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+RHEL 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). -+ -+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115, SRG-OS-000298-GPOS-00116, SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000382CCI-002314CCI-002322To install the "firewalld" package run the following command: -+ -+$ sudo dnf install firewalldRun the following command to determine if the firewalld package is installed with the following command: -+ -+$ sudo dnf list --installed firewalld -+ -+Example output: -+ -+firewalld.noarch 1.0.0-4.el9 -+ -+If the "firewall" package is not installed, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-251015The firewalld service on RHEL 9 must be active.<VulnDiscussion>"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 DOD 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. -+ -+RHEL 9 functionality (e.g., RDP) 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). -+ -+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115, SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000382CCI-002314To enable the firewalld service run the following command: -+ -+$ sudo systemctl enable --now firewalldVerify that "firewalld" is active with the following command: -+ -+$ systemctl is-active firewalld -+ -+active -+ -+If the firewalld service is not active, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-251020A RHEL 9 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems.<VulnDiscussion>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 DOD data. -+ -+RHEL 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "firewalld" daemon to employ a deny-all, allow-by-exception with the following commands: -+ -+Start by adding the exceptions that are required for mission functionality to the "drop" zone. If SSH access on port 22 is needed, for example, run the following: "sudo firewall-cmd --permanent --add-service=ssh --zone=drop" -+ -+Reload the firewall rules to update the runtime configuration from the "--permanent" changes made above: -+$ sudo firewall-cmd --reload -+ -+Set the default zone to the drop zone: -+$ sudo firewall-cmd --set-default-zone=drop -+Note: This is a runtime and permanent change. -+ -+Add any interfaces to the newly modified "drop" zone: -+$ sudo firewall-cmd --permanent --zone=drop --change-interface=ens33 -+ -+Reload the firewall rules for changes to take effect: -+$ sudo firewall-cmd --reloadVerify the RHEL 9 "firewalld" is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems with the following commands: -+ -+$ sudo firewall-cmd --state -+ -+running -+ -+$ sudo firewall-cmd --get-active-zones -+ -+public -+ interfaces: ens33 -+ -+$ sudo firewall-cmd --info-zone=public | grep target -+ -+ target: DROP -+ -+$ sudo firewall-cmd --permanent --info-zone=public | grep target -+ -+ target: DROP -+ -+If no zones are active on the RHEL 9 interfaces or if runtime and permanent targets are set to a different option other than "DROP", this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-251025RHEL 9 must control remote access methods.<VulnDiscussion>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 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. -+ -+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000382CCI-002314Configure RHEL 9 to allow approved settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL. -+ -+To open a port for a service, configure firewalld using the following command: -+ -+$ sudo firewall-cmd --permanent --add-port=port_number/tcp -+or -+$ sudo firewall-cmd --permanent --add-service=service_nameInspect the list of enabled firewall ports and verify they are configured correctly by running the following command: -+ -+$ sudo firewall-cmd --list-all -+ -+Ask the system administrator for the site or program Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA). Verify the services allowed by the firewall match the PPSM CLSA. -+ -+If there are additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), or there are no firewall rules configured, this is a finding.SRG-OS-000420-GPOS-00186<GroupDescription></GroupDescription>RHEL-09-251030RHEL 9 must protect against or limit the effects of denial-of-service (DoS) attacks by ensuring rate-limiting measures on impacted network interfaces are implemented.<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. -+ -+This requirement addresses the configuration of RHEL 9 to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exists to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002385Configure "nftables" to be the default "firewallbackend" for "firewalld" by adding or editing the following line in "etc/firewalld/firewalld.conf": -+ -+FirewallBackend=nftables -+ -+Establish rate-limiting rules based on organization-defined types of DoS attacks on impacted network interfaces.Verify "nftables" is configured to allow rate limits on any connection to the system with the following command: -+ -+$ sudo grep -i firewallbackend /etc/firewalld/firewalld.conf -+ -+# FirewallBackend -+FirewallBackend=nftables -+ -+If the "nftables" is not set as the "FirewallBackend" default, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-251035RHEL 9 must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments.<VulnDiscussion>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 ports, protocols, and services on information systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000382Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL. -+ -+Then run the following command to load the newly created rule(s): -+ -+$ sudo firewall-cmd --reloadInspect the firewall configuration and running services to verify it is configured to prohibit or restrict the use of functions, ports, protocols, and/or services that are unnecessary or prohibited. -+ -+Check which services are currently active with the following command: -+ -+$ sudo firewall-cmd --list-all-zones -+ -+custom (active) -+target: DROP -+icmp-block-inversion: no -+interfaces: ens33 -+sources: -+services: dhcpv6-client dns http https ldaps rpc-bind ssh -+ports: -+masquerade: no -+forward-ports: -+icmp-blocks: -+rich rules: -+ -+Ask the system administrator for the site or program Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA). Verify the services allowed by the firewall match the PPSM CLSA. -+ -+If there are additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-251040RHEL 9 network interfaces must not be in promiscuous mode.<VulnDiscussion>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 officer (ISSO) and restricted to only authorized personnel.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure network interfaces to turn off promiscuous mode unless approved by the ISSO and documented. -+ -+Set the promiscuous mode of an interface to off with the following command: -+ -+$ sudo ip link set dev <devicename> multicast off promisc offVerify network interfaces are not in promiscuous mode with the following command: -+ -+$ ip link | grep -i promisc -+ -+If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSO and documented, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-251045RHEL 9 must enable hardening for the Berkeley Packet Filter just-in-time compiler.<VulnDiscussion>When hardened, the extended Berkeley Packet Filter (BPF) just-in-time (JIT) compiler will randomize any kernel addresses in the BPF programs and maps, and will not expose the JIT addresses in "/proc/kallsyms".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to enable hardening for the BPF JIT compiler by adding the following line to a file, in the "/etc/sysctl.d" directory: -+ -+net.core.bpf_jit_harden = 2 -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 enables hardening for the BPF JIT with the following commands: -+ -+$ sudo sysctl net.core.bpf_jit_harden -+ -+net.core.bpf_jit_harden = 2 -+ -+If the returned line does not have a value of "2", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.core.bpf_jit_harden | tail -1 -+net.core.bpf_jit_harden = 2 -+ -+If the network parameter "net.core.bpf_jit_harden" is not equal to "2" or nothing is returned, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>RHEL-09-252010RHEL 9 must have the chrony package installed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001891The chrony package can be installed with the following command: -+ -+$ sudo dnf install chronyVerify that RHEL 9 has the chrony package installed with the following command: -+ -+$ sudo dnf list --installed chrony -+ -+Example output: -+ -+chrony.x86_64 4.1-3.el9 -+ -+If the "chrony" package is not installed, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>RHEL-09-252015RHEL 9 chronyd service must be enabled.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001891To enable the chronyd service run the following command: -+ -+$ sudo systemctl enable --now chronydVerify the chronyd service is active with the following command: -+ -+$ systemctl is-active chronyd -+ -+active -+ -+If the chronyd service is not active, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>RHEL-09-252020RHEL 9 must securely compare internal information system clocks at least every 24 hours.<VulnDiscussion>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. -+ -+Depending on the infrastructure being used the "pool" directive may not be supported. -+ -+Authoritative time sources include the United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). -+ -+Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000356-GPOS-00144, SRG-OS-000359-GPOS-00146</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001890CCI-001891CCI-002046Configure RHEL 9 to securely compare internal information system clocks at least every 24 hours with an NTP server by adding/modifying the following line in the /etc/chrony.conf file. -+ -+server [ntp.server.name] iburst maxpoll 16Verify RHEL 9 is securely comparing internal information system clocks at least every 24 hours with an NTP server with the following commands: -+ -+$ sudo grep maxpoll /etc/chrony.conf -+ -+server 0.us.pool.ntp.mil iburst maxpoll 16 -+ -+If the "maxpoll" option is set to a number greater than 16 or the line is commented out, this is a finding. -+ -+Verify the "chrony.conf" file is configured to an authoritative DOD time source by running the following command: -+ -+$ sudo grep -i server /etc/chrony.conf -+server 0.us.pool.ntp.mil -+ -+If the parameter "server" is not set or is not set to an authoritative DOD time source, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-252025RHEL 9 must disable the chrony daemon from acting as a server.<VulnDiscussion>Minimizing the exposure of the server functionality of the chrony daemon diminishes the attack surface. -+ -+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381CCI-000382Configure RHEL 9 to disable the chrony daemon from acting as a server by adding/modifying the following line in the /etc/chrony.conf file: -+ -+port 0Verify RHEL 9 disables the chrony daemon from acting as a server with the following command: -+ -+$ grep -w port /etc/chrony.conf -+ -+port 0 -+ -+If the "port" option is not set to "0", is commented out, or is missing, this is a finding.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>RHEL-09-252030RHEL 9 must disable network management of the chrony daemon.<VulnDiscussion>Not exposing the management interface of the chrony daemon on the network diminishes the attack space. -+ -+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000095-GPOS-00049</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381CCI-000382Configure RHEL 9 to disable network management of the chrony daemon by adding/modifying the following line in the /etc/chrony.conf file: -+ -+cmdport 0Verify RHEL 9 disables network management of the chrony daemon with the following command: -+ -+$ grep -w cmdport /etc/chrony.conf -+ -+cmdport 0 -+ -+If the "cmdport" option is not set to "0", is commented out, or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252035RHEL 9 systems using Domain Name Servers (DNS) resolution must have at least two name servers configured.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the operating system to use two or more name servers for DNS resolution based on the DNS mode of the system. -+ -+If the NetworkManager DNS mode is set to "none", then add the following lines to "/etc/resolv.conf": -+ -+nameserver [name server 1] -+nameserver [name server 2] -+ -+Replace [name server 1] and [name server 2] with the IPs of two different DNS resolvers. -+ -+If the NetworkManager DNS mode is set to "default" then add two DNS servers to a NetworkManager connection. Using the following commands: -+ -+$ sudo nmcli connection modify [connection name] ipv4.dns [name server 1] -+$ sudo nmcli connection modify [connection name] ipv4.dns [name server 2] -+ -+Replace [name server 1] and [name server 2] with the IPs of two different DNS resolvers. Replace [connection name] with a valid NetworkManager connection name on the system. Replace ipv4 with ipv6 if IPv6 DNS servers are used.Verify the name servers used by the system with the following command: -+ -+$ grep nameserver /etc/resolv.conf -+ -+nameserver 192.168.1.2 -+nameserver 192.168.1.3 -+ -+If less than two lines are returned that are not commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252040RHEL 9 must configure a DNS processing mode set be Network Manager.<VulnDiscussion>In order to ensure that DNS resolver settings are respected, a DNS mode in Network Manager must be configured.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure NetworkManager in RHEL 9 to use a DNS mode. -+ -+In "/etc/NetworkManager/NetworkManager.conf" add the following line in the "[main]" section: -+ -+dns = none -+ -+NetworkManager must be reloaded for the change to take effect. -+ -+$ sudo systemctl reload NetworkManagerVerify that RHEL 9 has a DNS mode configured in Network Manager. -+ -+$ NetworkManager --print-config -+[main] -+dns=none -+ -+If the dns key under main does not exist or is not set to "none" or "default", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252045RHEL 9 must not have unauthorized IP tunnels configured.<VulnDiscussion>IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the information system security officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove all unapproved tunnels from the system, or document them with the ISSO.Verify that RHEL 9 does not have unauthorized IP tunnels configured. -+ -+Determine if the "IPsec" service is active with the following command: -+ -+$ systemctl status ipsec -+ -+ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec -+Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled) -+Active: inactive (dead) -+ -+If the "IPsec" service is active, check for configured IPsec connections ("conn"), with the following command: -+ -+$ grep -rni conn /etc/ipsec.conf /etc/ipsec.d/ -+ -+Verify any returned results are documented with the ISSO. -+ -+If the IPsec tunnels are active and not approved, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252050RHEL 9 must be configured to prevent unrestricted mail relaying.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Modify the postfix configuration file to restrict client connections to the local network with the following command: -+ -+$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'Verify RHEL 9 is configured to prevent unrestricted mail relaying with the following command: -+ -+$ postconf -n smtpd_client_restrictions -+ -+smtpd_client_restrictions = permit_mynetworks,reject -+ -+If the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject", and the additional entries have not been documented with the information system security officer (ISSO), this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252055If the Trivial File Transfer Protocol (TFTP) server is required, RHEL 9 TFTP daemon must be configured to operate in secure mode.<VulnDiscussion>Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files. Using the "-s" option causes the TFTP service to only serve files from the given directory.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the TFTP daemon to operate in secure mode. -+ -+1. Find the path for the systemd service. -+ -+$ sudo systemctl show tftp | grep FragmentPath= -+FragmentPath=/etc/systemd/system/tftp.service -+ -+2. Edit the ExecStart line on that file to add the -s option with a subdirectory. -+ -+ExecStart=/usr/sbin/in.tftpd -s /var/lib/tftpbootVerify the TFTP daemon is configured to operate in secure mode. -+ -+Check if a TFTP server is installed with the following command: -+ -+$ sudo dnf list --installed tftp-server -+ -+Example output: -+ -+tftp-server.x86_64 5.2-35.el9.x86_64 -+ -+Note: If a TFTP server is not installed, this requirement is Not Applicable. -+ -+If a TFTP server is installed, check for the server arguments with the following command: -+ -+$ systemctl cat tftp | grep ExecStart -+ExecStart=/usr/sbin/in.tftpd -s /var/lib/tftpboot -+ -+If the "ExecStart" line does not have a "-s" option, and a subdirectory is not assigned, this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>RHEL-09-252060RHEL 9 must forward mail from postmaster to the root account using a postfix alias.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000139Configure a valid email address as an alias for the root account. -+ -+Append the following line to "/etc/aliases": -+ -+postmaster: root -+ -+Then, run the following command: -+ -+$ sudo newaliasesVerify that 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 -+ -+If the command does not return a line, or the line is commented out, ask the system administrator to indicate how they and the information systems security officer (ISSO) are notified of an audit process failure. If there is no evidence of the proper personnel being notified of an audit processing failure, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252065RHEL 9 libreswan package must be installed.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000803Install the libreswan service (if it is not already installed) with the following command: -+ -+$ sudo dnf install libreswanVerify that RHEL 9 libreswan service package is installed. -+ -+Check that the libreswan service package is installed with the following command: -+ -+$ sudo dnf list --installed libreswan -+ -+Example output: -+ -+libreswan.x86_64 4.6-3.el9 -+ -+If the "libreswan" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252070There must be no shosts.equiv files on RHEL 9.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove any found "shosts.equiv" files from the system. -+ -+$ sudo rm /[path]/[to]/[file]/shosts.equivVerify there are no "shosts.equiv" files on RHEL 9 with the following command: -+ -+$ sudo find / -name shosts.equiv -+ -+If a "shosts.equiv" file is found, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-252075There must be no .shosts files on RHEL 9.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove any found ".shosts" files from the system. -+ -+$ sudo rm /[path]/[to]/[file]/.shostsVerify there are no ".shosts" files on RHEL 9 with the following command: -+ -+$ sudo find / -name .shosts -+ -+If a ".shosts" file is found, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253010RHEL 9 must be configured to use TCP syncookies.<VulnDiscussion>Denial of service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. -+ -+Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000420-GPOS-00186, SRG-OS-000142-GPOS-00071</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001095CCI-002385Configure RHEL 9 to use TCP syncookies. -+ -+Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: -+ net.ipv4.tcp_syncookies = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is configured to use IPv4 TCP syncookies. -+ -+Determine if syncookies are used with the following command: -+ -+Check the status of the kernel.perf_event_paranoid kernel parameter. -+ -+$ sysctl net.ipv4.tcp_syncookies -+ -+net.ipv4.tcp_syncookies = 1 -+ -+Check that the configuration files are present to enable this kernel parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.tcp_syncookies | tail -1 -+ -+net.ipv4.tcp_syncookies = 1 -+ -+If the network parameter "ipv4.tcp_syncookies" is not equal to "1" or nothing is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253015RHEL 9 must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to ignore IPv4 ICMP redirect messages. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.accept_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 will not accept IPv4 ICMP redirect messages. -+ -+Check the value of the all "accept_redirects" variables with the following command: -+ -+$ sysctl net.ipv4.conf.all.accept_redirects -+ -+net.ipv4.conf.all.accept_redirects = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.all.accept_redirects | tail -1 -+ -+net.ipv4.conf.all.accept_redirects = 0 -+ -+If "net.ipv4.conf.all.accept_redirects" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253020RHEL 9 must not forward Internet Protocol version 4 (IPv4) source-routed packets.<VulnDiscussion>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 must be disabled unless it is absolutely required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to ignore IPv4 source-routed packets. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.accept_source_route = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 will not accept IPv4 source-routed packets. -+ -+Check the value of the all "accept_source_route" variables with the following command: -+ -+$ sysctl net.ipv4.conf.all.accept_source_route -+ -+net.ipv4.conf.all.accept_source_route = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.all.accept_source_route | tail -1 -+ -+net.ipv4.conf.all.accept_source_route = 0 -+ -+If "net.ipv4.conf.all.accept_source_route" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253025RHEL 9 must log IPv4 packets with impossible addresses.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to log martian packets on IPv4 interfaces. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.log_martians=1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 logs IPv4 martian packets. -+ -+Check the value of the accept source route variable with the following command: -+ -+$ sudo sysctl net.ipv4.conf.all.log_martians -+ -+net.ipv4.conf.all.log_martians = 1 -+ -+If the returned line does not have a value of "1", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.all.log_martians | tail -1 -+ -+net.ipv4.conf.all.log_martians = 1 -+ -+If "net.ipv4.conf.all.log_martians" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253030RHEL 9 must log IPv4 packets with impossible addresses by default.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to log martian packets on IPv4 interfaces by default. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.default.log_martians=1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 logs IPv4 martian packets by default. -+ -+Check the value of the accept source route variable with the following command: -+ -+$ sudo sysctl net.ipv4.conf.default.log_martians -+ -+net.ipv4.conf.default.log_martians = 1 -+ -+If the returned line does not have a value of "1", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.default.log_martians | tail -1 -+ -+net.ipv4.conf.default.log_martians = 1 -+ -+If "net.ipv4.conf.default.log_martians" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253035RHEL 9 must use reverse path filtering on all IPv4 interfaces.<VulnDiscussion>Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface on which they were received. It must not be used on systems that are routers for complicated networks, but is helpful for end hosts and routers serving small networks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to use reverse path filtering on all IPv4 interfaces. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.rp_filter = 1 -+ -+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 uses reverse path filtering on all IPv4 interfaces with the following commands: -+ -+$ sysctl net.ipv4.conf.all.rp_filter -+ -+net.ipv4.conf.all.rp_filter = 1 -+ -+If the returned line does not have a value of "1", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.all.rp_filter | tail -1 -+ -+net.ipv4.conf.all.rp_filter = 1 -+ -+If "net.ipv4.conf.all.rp_filter" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253040RHEL 9 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect messages from being accepted.<VulnDiscussion>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 must be disabled unless absolutely required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to prevent IPv4 ICMP redirect messages from being accepted. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.default.accept_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 will not accept IPv4 ICMP redirect messages. -+ -+Check the value of the default "accept_redirects" variables with the following command: -+ -+$ sysctl net.ipv4.conf.default.accept_redirects -+ -+net.ipv4.conf.default.accept_redirects = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.default.accept_redirects | tail -1 -+ -+net.ipv4.conf.default.accept_redirects = 0 -+ -+If "net.ipv4.conf.default.accept_redirects" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253045RHEL 9 must not forward IPv4 source-routed packets by default.<VulnDiscussion>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 must be disabled unless it is absolutely required, such as when IPv4 forwarding is enabled and the system is legitimately functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not forward IPv4 source-routed packets by default. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.default.accept_source_route = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not accept IPv4 source-routed packets by default. -+ -+Check the value of the accept source route variable with the following command: -+ -+$ sysctl net.ipv4.conf.default.accept_source_route -+ -+net.ipv4.conf.default.accept_source_route = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.default.accept_source_route | tail -1 -+ -+net.ipv4.conf.default.accept_source_route = 0 -+ -+If "net.ipv4.conf.default.accept_source_route" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253050RHEL 9 must use a reverse-path filter for IPv4 network traffic when possible by default.<VulnDiscussion>Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface on which they were received. It must not be used on systems that are routers for complicated networks, but is helpful for end hosts and routers serving small networks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to use reverse path filtering on IPv4 interfaces by default. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.default.rp_filter = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 uses reverse path filtering on IPv4 interfaces with the following commands: -+ -+$ sudo sysctl net.ipv4.conf.default.rp_filter -+ -+net.ipv4.conf.default.rp_filter = 1 -+ -+If the returned line does not have a value of "1", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.default.rp_filter | tail -1 -+ -+net.ipv4.conf.default.rp_filter = 1 -+ -+If "net.ipv4.conf.default.rp_filter" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253055RHEL 9 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not respond to IPv4 ICMP echoes sent to a broadcast address. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.icmp_echo_ignore_broadcasts = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not respond to ICMP echoes sent to a broadcast address. -+ -+Check the value of the "icmp_echo_ignore_broadcasts" variable with the following command: -+ -+$ sysctl net.ipv4.icmp_echo_ignore_broadcasts -+ -+net.ipv4.icmp_echo_ignore_broadcasts = 1 -+ -+If the returned line does not have a value of "1", a line is not returned, or the retuned line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|$)' | grep -F net.ipv4.icmp_echo_ignore_broadcasts | tail -1 -+ -+net.ipv4.icmp_echo_ignore_broadcasts = 1 -+ -+If "net.ipv4.icmp_echo_ignore_broadcasts" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253060RHEL 9 must limit the number of bogus Internet Control Message Protocol (ICMP) response errors logs.<VulnDiscussion>Some routers will send responses to broadcast frames that violate RFC-1122, which fills up a log file system with many useless error messages. An attacker may take advantage of this and attempt to flood the logs with bogus error logs. Ignoring bogus ICMP error responses reduces log size, although some activity would not be logged.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not log bogus ICMP errors: -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.icmp_ignore_bogus_error_responses = 1 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemThe runtime status of the net.ipv4.icmp_ignore_bogus_error_responses kernel parameter can be queried by running the following command: -+ -+$ sudo sysctl net.ipv4.icmp_ignore_bogus_error_responses -+ -+net.ipv4.icmp_ignore_bogus_error_responses = 1 -+ -+If "net.ipv4.icmp_ignore_bogus_error_responses" is not set to "1", this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.icmp_ignore_bogus_error_response | tail -1 -+ -+net.ipv4.icmp_ignore_bogus_error_response = 1 -+ -+If "net.ipv4.icmp_ignore_bogus_error_response" is not set to "1" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253065RHEL 9 must not send Internet Control Message Protocol (ICMP) redirects.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not allow interfaces to perform IPv4 ICMP redirects. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.send_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not IPv4 ICMP redirect messages. -+ -+Check the value of the "all send_redirects" variables with the following command: -+ -+$ sysctl net.ipv4.conf.all.send_redirects -+ -+net.ipv4.conf.all.send_redirects = 0 -+ -+If the returned line does not have a value of "0", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.all.send_redirects | tail -1 -+ -+net.ipv4.conf.all.send_redirects = 0 -+ -+If "net.ipv4.conf.all.send_redirects" is not set to "0" and is not documented with the information system security officer (ISSO) as an operational requirement or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253070RHEL 9 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.default.send_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default. -+ -+Check the value of the "default send_redirects" variables with the following command: -+ -+$ sysctl net.ipv4.conf.default.send_redirects -+ -+net.ipv4.conf.default.send_redirects=0 -+ -+If the returned line does not have a value of "0", or a line is not returned, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv4.conf.default.send_redirects | tail -1 -+ -+net.ipv4.conf.default.send_redirects = 0 -+ -+If "net.ipv4.conf.default.send_redirects" is not set to "0" and is not documented with the information system security officer (ISSO) as an operational requirement or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-253075RHEL 9 must not enable IPv4 packet forwarding unless the system is a router.<VulnDiscussion>Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this capability is used when not required, system network information may be unnecessarily transmitted across the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not allow IPv4 packet forwarding, unless the system is a router. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv4.conf.all.forwarding = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is not performing IPv4 packet forwarding, unless the system is a router. -+ -+Check that IPv4 forwarding is disabled using the following command: -+ -+$ sysctl net.ipv4.conf.all.forwarding -+ -+net.ipv4.conf.all.forwarding = 0 -+ -+If the IPv4 forwarding value is not "0" and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ { /usr/lib/systemd/systemd-sysctl --cat-config; cat /etc/sysctl.conf; } | egrep -v '^(#|$)' | grep -F net.ipv4.conf.all.forwarding | tail -1 -+ -+net.ipv4.conf.all.forwarding = 0 -+ -+If "net.ipv4.conf.all.forwarding" is not set to "0" and is not documented with the ISSO as an operational requirement or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254010RHEL 9 must not accept router advertisements on all IPv6 interfaces.<VulnDiscussion>An illicit router advertisement message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not accept router advertisements on all IPv6 interfaces unless the system is a router. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.all.accept_ra = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not accept router advertisements on all IPv6 interfaces, unless the system is a router. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Determine if router advertisements are not accepted by using the following command: -+ -+$ sudo sysctl net.ipv6.conf.all.accept_ra -+ -+net.ipv6.conf.all.accept_ra = 0 -+ -+If the "accept_ra" value is not "0" and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.all.accept_ra | tail -1 -+ -+net.ipv6.conf.all.accept_ra = 0 -+ -+If "net.ipv6.conf.all.accept_ra" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254015RHEL 9 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages.<VulnDiscussion>An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to ignore IPv6 ICMP redirect messages. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.all.accept_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 ignores IPv6 ICMP redirect messages. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Check the value of the "accept_redirects" variables with the following command: -+ -+$ sysctl net.ipv6.conf.all.accept_redirects -+ -+net.ipv6.conf.all.accept_redirects = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.all.accept_redirects | tail -1 -+ -+net.ipv6.conf.all.accept_redirects = 0 -+ -+If "net.ipv6.conf.all.accept_redirects" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254020RHEL 9 must not forward IPv6 source-routed packets.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that 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-routed traffic, such as when forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not forward IPv6 source-routed packets. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.all.accept_source_route = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not accept IPv6 source-routed packets. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Check the value of the accept source route variable with the following command: -+ -+$ sysctl net.ipv6.conf.all.accept_source_route -+ -+net.ipv6.conf.all.accept_source_route = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.all.accept_source_route | tail -1 -+ -+net.ipv6.conf.all.accept_source_route = 0 -+ -+If "net.ipv6.conf.all.accept_source_route" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254025RHEL 9 must not enable IPv6 packet forwarding unless the system is a router.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not allow IPv6 packet forwarding, unless the system is a router. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.all.forwarding = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 is not performing IPv6 packet forwarding, unless the system is a router. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Check that IPv6 forwarding is disabled using the following commands: -+ -+$ sysctl net.ipv6.conf.all.forwarding -+ -+net.ipv6.conf.all.forwarding = 0 -+ -+If the IPv6 forwarding value is not "0" and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.all.forwarding | tail -1 -+ -+net.ipv6.conf.all.forwarding = 0 -+ -+If "net.ipv6.conf.all.forwarding" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254030RHEL 9 must not accept router advertisements on all IPv6 interfaces by default.<VulnDiscussion>An illicit router advertisement message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not accept router advertisements on all IPv6 interfaces by default unless the system is a router. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.default.accept_ra = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not accept router advertisements on all IPv6 interfaces by default, unless the system is a router. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Determine if router advertisements are not accepted by default by using the following command: -+ -+$ sysctl net.ipv6.conf.default.accept_ra -+ -+net.ipv6.conf.default.accept_ra = 0 -+ -+If the "accept_ra" value is not "0" and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.default.accept_ra | tail -1 -+ -+net.ipv6.conf.default.accept_ra = 0 -+ -+If "net.ipv6.conf.default.accept_ra" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254035RHEL 9 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to prevent IPv6 ICMP redirect messages from being accepted. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.default.accept_redirects = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 will not accept IPv6 ICMP redirect messages. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Check the value of the default "accept_redirects" variables with the following command: -+ -+$ sysctl net.ipv6.conf.default.accept_redirects -+ -+net.ipv6.conf.default.accept_redirects = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.default.accept_redirects | tail -1 -+ -+net.ipv6.conf.default.accept_redirects = 0 -+ -+If "net.ipv6.conf.default.accept_redirects" is not set to "0" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-254040RHEL 9 must not forward IPv6 source-routed packets by default.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that 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-routed traffic, such as when forwarding is enabled and the system is functioning as a router. -+ -+Accepting source-routed packets in the IPv6 protocol has few legitimate uses. It must be disabled unless it is absolutely required.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not forward IPv6 source-routed packets by default. -+ -+Add or edit the following line in a single system configuration file, in the "/etc/sysctl.d/" directory: -+ -+net.ipv6.conf.default.accept_source_route = 0 -+ -+Load settings from all system configuration files with the following command: -+ -+$ sudo sysctl --systemVerify RHEL 9 does not accept IPv6 source-routed packets by default. -+ -+Note: If IPv6 is disabled on the system, this requirement is Not Applicable. -+ -+Check the value of the accept source route variable with the following command: -+ -+$ sysctl net.ipv6.conf.default.accept_source_route -+ -+net.ipv6.conf.default.accept_source_route = 0 -+ -+If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. -+ -+Check that the configuration files are present to enable this network parameter. -+ -+$ sudo /usr/lib/systemd/systemd-sysctl --cat-config | egrep -v '^(#|;)' | grep -F net.ipv6.conf.default.accept_source_route | tail -1 -+ -+net.ipv6.conf.default.accept_source_route = 0 -+ -+If "net.ipv6.conf.default.accept_source_route" is not set to "0" or is missing, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>RHEL-09-255010All RHEL 9 networked systems must have SSH installed.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. -+ -+This requirement 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, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. -+ -+Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. -+ -+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002418CCI-002420CCI-002421CCI-002422The openssh-server package can be installed with the following command: -+ -+$ sudo dnf install openssh-serverVerify that RHEL 9 has the openssh-server package installed with the following command: -+ -+$ sudo dnf list --installed openssh-server -+ -+Example output: -+ -+openssh-server.x86_64 8.7p1-8.el9 -+ -+If the "openssh-server" package is not installed, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>RHEL-09-255015All RHEL 9 networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. -+ -+This requirement 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, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. -+ -+Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. -+ -+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002418CCI-002420CCI-002421CCI-002422To enable the sshd service run the following command: -+ -+$ systemctl enable --now sshdVerify that "sshd" is active with the following command: -+ -+$ systemctl is-active sshd -+ -+active -+ -+If the "sshd" service is not active, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255020RHEL 9 must have the openssh-clients package installed.<VulnDiscussion>This package includes utilities to make encrypted connections and transfer files securely to SSH servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366The openssh-clients package can be installed with the following command: -+ -+$ sudo dnf install openssh-clientsVerify that RHEL 9 has the openssh-clients package installed with the following command: -+ -+$ sudo dnf list --installed openssh-clients -+ -+Example output: -+ -+openssh-clients.x86_64 8.7p1-8.el9 -+ -+If the "openssh-clients" package is not installed, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>RHEL-09-255025RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a SSH logon.<VulnDiscussion>The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, systems whose ownership should not be obvious should ensure usage of a banner that does not provide easy attribution. -+ -+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure RHEL 9 to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via ssh. -+ -+Edit the "/etc/ssh/sshd_config" file to uncomment the banner keyword and configure it to point to a file that will contain the logon banner (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). -+ -+An example configuration line is: -+ -+Banner /etc/issueVerify any SSH connection to the operating system displays the Standard Mandatory DOD Notice and Consent Banner before granting access to the system. -+ -+Check for the location of the banner file being used with the following command: -+ -+$ sudo grep -i banner /etc/ssh/sshd_config -+ -+banner /etc/issue -+ -+This command will return the banner keyword and the name of the file that contains the SSH banner (in this case "/etc/issue"). -+ -+If the line is commented out, this is a finding.SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>RHEL-09-255030RHEL 9 must log SSH connection attempts and failures to the server.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000067Configure RHEL 9 to log connection attempts add or modify the following line in "/etc/ssh/sshd_config". -+ -+LogLevel VERBOSE -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify RHEL 9 logs SSH connection attempts and failures to the server. -+ -+Check what the SSH daemon's "LogLevel" option is set to with the following command: -+ -+$ sudo grep -i LogLevel /etc/ssh/sshd_config -+ -+LogLevel VERBOSE -+ -+If a value of "VERBOSE" is not returned, the line is commented out, or is missing, this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>RHEL-09-255035RHEL 9 SSHD must accept public key authentication.<VulnDiscussion>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. A DOD CAC with DOD-approved PKI is an example of multifactor authentication. -+ -+Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000765CCI-000766CCI-000767CCI-000768To configure the system add or modify the following line in "/etc/ssh/sshd_config". -+ -+PubkeyAuthentication yes -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify that RHEL 9 SSH daemon accepts public key encryption with the following command: -+ -+$ sudo grep -i PubkeyAuthentication /etc/ssh/sshd_config -+ -+PubkeyAuthentication yes -+ -+If "PubkeyAuthentication" is set to no, the line is commented out, or the line is missing, this is a finding.SRG-OS-000106-GPOS-00053<GroupDescription></GroupDescription>RHEL-09-255040RHEL 9 SSHD must not allow blank passwords.<VulnDiscussion>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments. -+ -+Satisfies: SRG-OS-000106-GPOS-00053, SRG-OS-000480-GPOS-00229, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000766To configure the system to prevent SSH users from logging on with blank passwords edit the following line in "etc/ssh/sshd_config": -+ -+PermitEmptyPasswords no -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify RHEL 9 remote access using SSH prevents logging on with a blank password with the following command: -+ -+$ sudo grep -i PermitEmptyPasswords /etc/ssh/sshd_config -+ -+PermitEmptyPassword no -+ -+If the "PermitEmptyPassword" keyword is set to "yes", is missing, or is commented out, this is a finding.SRG-OS-000109-GPOS-00056<GroupDescription></GroupDescription>RHEL-09-255045RHEL 9 must not permit direct logons to the root account using remote access via SSH.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000109-GPOS-00056, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000770To configure the system to prevent SSH users from logging on directly as root add or modify the following line in "/etc/ssh/sshd_config". -+ -+ PermitRootLogin no -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify RHEL 9 remote access using SSH prevents users from logging on directly as "root" with the following command: -+ -+$ sudo grep -i PermitRootLogin /etc/ssh/sshd_config -+ -+PermitRootLogin no -+ -+If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>RHEL-09-255050RHEL 9 must enable the Pluggable Authentication Module (PAM) interface for SSHD.<VulnDiscussion>When UsePAM is set to "yes", PAM runs through account and session types properly. This is important when restricted access to services based off of IP, time, or other factors of the account is needed. Additionally, this ensures users can inherit certain environment variables on login or disallow access to the server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000877Configure the RHEL 9 SSHD to use the UsePAM interface add or modify the following line in "/etc/ssh/sshd_config". -+ -+UsePAM yes -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the RHEL 9 SSHD is configured to allow for the UsePAM interface with the following command: -+ -+$ sudo grep -i usepam /etc/ssh/sshd_config -+ -+UsePAM yes -+ -+If the "UsePAM" keyword is set to "no", is missing, or is commented out, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-255055RHEL 9 SSH daemon must be configured to use system-wide crypto policies.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 SSH daemon to use system-wide crypto policies by running the following commands: -+ -+$ sudo dnf reinstall openssh-serverVerify that system-wide crypto policies are in effect with the following command: -+ -+$ sudo grep Include /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+/etc/ssh/sshd_config:Include /etc/ssh/sshd_config.d/*.conf -+/etc/ssh/sshd_config.d/50-redhat.conf:Include /etc/crypto-policies/back-ends/opensshserver.config -+ -+If "Include /etc/ssh/sshd_config.d/*.conf" or "Include /etc/crypto-policies/back-ends/opensshserver.config" are not included in the system sshd config or the file /etc/ssh/sshd_config.d/50-redhat.conf is missing, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-255060RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH client connections.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD 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. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+RHEL 9 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/opensshserver.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 SSH daemon to use system-wide crypto policies by running the following commands: -+ -+$ sudo dnf reinstall openssh-clientsVerify that system-wide crypto policies are in effect with the following command: -+ -+$ sudo grep Include /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+/etc/ssh/sshd_config:Include /etc/ssh/sshd_config.d/*.conf -+/etc/ssh/sshd_config.d/50-redhat.conf:Include /etc/crypto-policies/back-ends/opensshserver.config -+ -+If "Include /etc/ssh/sshd_config.d/*.conf" or "Include /etc/crypto-policies/back-ends/opensshserver.config" are not included in the system sshd config or the file "/etc/ssh/sshd_config.d/50-redhat.conf" is missing, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-255065RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH server connections.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+RHEL 9 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/opensshserver.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 SSH client to use only ciphers employing FIPS 140-3 approved algorithms by updating the "/etc/crypto-policies/back-ends/openssh.config" file with the following line: -+ -+Ciphers aes-256-gcm@openssh.com, chacha20-poly1305@openssh.com, aes256-ctr,aes128-gcm@openssh.com,aes128-ctr -+ -+A reboot is required for the changes to take effect.Verify the SSH client is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command: -+ -+$ sudo grep -i ciphers /etc/crypto-policies/back-ends/openssh.config -+ -+Ciphers aes-256-gcm@openssh.com, chacha20-poly1305@openssh.com, aes256-ctr,aes128-gcm@openssh.com,aes128-ctr -+ -+If the cipher entries in the "openssh.config" file have any ciphers other than "aes-256-gcm@openssh.com, chacha20-poly1305@openssh.com, aes256-ctr,aes128-gcm@openssh.com,aes128-ctr", the order differs from the example above, they are missing, or commented out, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-255070RHEL 9 SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD 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. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+RHEL 9 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/opensshserver.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 SSH client to use only MACs employing FIPS 140-3 approved algorithms by updating the "/etc/crypto-policies/back-ends/openssh.config" file with the following line: -+ -+MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-512,hmac-sha2-256-etm@openssh.com,hmac-sha2-256 -+ -+A reboot is required for the changes to take effect.Verify SSH client is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command: -+ -+$ sudo grep -i macs /etc/crypto-policies/back-ends/openssh.config -+MACs hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-512 -+ -+If the MACs entries in the "openssh.config" file have any hashes other than "hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-512", the order differs from the example above, they are missing, or commented out, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-255075RHEL 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+RHEL 9 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/opensshserver.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 SSH client to use only MACs employing FIPS 140-3 approved algorithms by updating the "/etc/crypto-policies/back-ends/openssh.config" file with the following line: -+ -+MACs hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 -+ -+A reboot is required for the changes to take effect.Verify SSH client is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command: -+ -+$ sudo grep -i macs /etc/crypto-policies/back-ends/openssh.config -+MACs hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 -+ -+If the MACs entries in the "openssh.config" file have any hashes other than "hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-512", the order differs from the example above, they are missing, or commented out, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>RHEL-09-255080RHEL 9 must not allow a noncertificate trusted host SSH logon to the system.<VulnDiscussion>SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366To configure RHEL 9 to not allow a noncertificate trusted host SSH logon to the system add or modify the following line in "/etc/ssh/sshd_config". -+ -+HostbasedAuthentication no -+ -+Restart the SSH daemon for the settings to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the operating system does not allow a noncertificate trusted host SSH logon to the system with the following command: -+ -+$ sudo grep -i hostbasedauthentication /etc/ssh/sshd_config -+ -+HostbasedAuthentication no -+ -+If the "HostbasedAuthentication" keyword is not set to "no", is missing, or is commented out, this is a finding. -+ -+If the required value is not set, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>RHEL-09-255085RHEL 9 must not allow users to override SSH environment variables.<VulnDiscussion>SSH environment options potentially allow users to bypass access restriction in some configurations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the RHEL 9 SSH daemon to not allow unattended or automatic logon to the system. -+ -+Add or edit the following line in the "/etc/ssh/sshd_config" file: -+ -+PermitUserEnvironment no -+ -+Restart the SSH daemon for the setting to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify that unattended or automatic logon via SSH is disabled with the following command: -+ -+$ sudo grep -i permituserenvironment /etc/ssh/sshd_config -+ -+PermitUserEnvironment no -+ -+If "PermitUserEnvironment" is set to "yes", is missing completely, or is commented out, this is a finding. -+ -+If the required value is not set, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>RHEL-09-255090RHEL 9 must force a frequent session key renegotiation for SSH connections to the server.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. -+ -+This requirement 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, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. -+ -+Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. -+ -+Session key regeneration limits the chances of a session key becoming compromised. -+ -+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000033-GPOS-00014, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000068CCI-002418CCI-002421Configure RHEL 9 to force a frequent session key renegotiation for SSH connections to the server by adding or modifying the following line in the "/etc/ssh/sshd_config" file: -+ -+RekeyLimit 1G 1h -+ -+Restart the SSH daemon for the settings to take effect. -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH server is configured to force frequent session key renegotiation with the following command: -+ -+$ sudo grep -i rekeyLimit /etc/ssh/sshd_config -+ -+RekeyLimit 1G 1h -+ -+If "RekeyLimit" does not have a maximum data amount and maximum time defined, is missing or commented out, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>RHEL-09-255095RHEL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive.<VulnDiscussion>Terminating an unresponsive 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 left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element. -+ -+Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean the operating system terminates all sessions or network access; it only ends the unresponsive session and releases the resources associated with that session. -+ -+RHEL 9 utilizes /etc/ssh/sshd_config for configurations of OpenSSH. Within the sshd_config, the product of the values of "ClientAliveInterval" and "ClientAliveCountMax" are used to establish the inactivity threshold. The "ClientAliveInterval" is a timeout interval in seconds, after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The "ClientAliveCountMax" is the number of client alive messages that may be sent without sshd receiving any messages back from the client. If this threshold is met, sshd will disconnect the client. For more information on these settings and others, refer to the sshd_config man pages. -+ -+Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001133CCI-002361Note: This setting must be applied in conjunction with RHEL-09-255100 to function correctly. -+ -+Configure the SSH server to terminate a user session automatically after the SSH client has become unresponsive. -+ -+Modify or append the following lines in the "/etc/ssh/sshd_config" file: -+ -+ClientAliveCountMax 1 -+ -+In order for the changes to take effect, the SSH daemon must be restarted. -+ -+$ sudo systemctl restart sshd.serviceVerify that the "ClientAliveCountMax" is set to "1" by performing the following command: -+ -+$ sudo grep -i countmax /etc/ssh/sshd_config -+ -+ClientAliveCountMax 1 -+ -+If "ClientAliveCountMax" do not exist, is not set to a value of "0" in "/etc/ssh/sshd_config", or is commented out, this is a finding.SRG-OS-000126-GPOS-00066<GroupDescription></GroupDescription>RHEL-09-255100RHEL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive.<VulnDiscussion>Terminating an unresponsive 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 left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element. -+ -+Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean the operating system terminates all sessions or network access; it only ends the unresponsive session and releases the resources associated with that session. -+ -+RHEL 9 utilizes /etc/ssh/sshd_config for configurations of OpenSSH. Within the sshd_config, the product of the values of "ClientAliveInterval" and "ClientAliveCountMax" are used to establish the inactivity threshold. The "ClientAliveInterval" is a timeout interval in seconds, after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The "ClientAliveCountMax" is the number of client alive messages that may be sent without sshd receiving any messages back from the client. If this threshold is met, sshd will disconnect the client. For more information on these settings and others, refer to the sshd_config man pages. -+ -+Satisfies: SRG-OS-000126-GPOS-00066, SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109, SRG-OS-000395-GPOS-00175</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000879CCI-001133CCI-002361CCI-002891Note: This setting must be applied in conjunction with RHEL-09-255095 to function correctly. -+ -+Configure the SSH server to terminate a user session automatically after the SSH client has been unresponsive for 10 minutes. -+ -+Modify or append the following lines in the "/etc/ssh/sshd_config" file: -+ -+ClientAliveInterval 600 -+ -+In order for the changes to take effect, the SSH daemon must be restarted. -+ -+$ sudo systemctl restart sshd.serviceVerify that the "ClientAliveInterval" variable is set to a value of "600" or less by performing the following command: -+ -+$ sudo grep -i interval /etc/ssh/sshd_config -+ -+ClientAliveInterval 600 -+ -+If "ClientAliveInterval" does not exist, does not have a value of "600" or less in "/etc/ssh/sshd_config", or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255105RHEL 9 SSH server configuration file must be group-owned by root.<VulnDiscussion>Service configuration files enable or disable features of their respective services, which if configured incorrectly, can lead to insecure and vulnerable configurations. Therefore, service configuration files must be owned by the correct group to prevent unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/ssh/sshd_config" file to be group-owned by root with the following command: -+ -+$ sudo chgrp root /etc/ssh/sshd_configVerify the group ownership of the "/etc/ssh/sshd_config" file with the following command: -+ -+$ ls -al /etc/ssh/sshd_config -+ -+rw-------. 1 root root 3669 Feb 22 11:34 /etc/ssh/sshd_config -+ -+If the "/etc/ssh/sshd_config" file does not have a group owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255110RHEL 9 SSH server configuration file must be owned by root.<VulnDiscussion>Service configuration files enable or disable features of their respective services, which if configured incorrectly, can lead to insecure and vulnerable configurations. Therefore, service configuration files must be owned by the correct group to prevent unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/ssh/sshd_config" file to be owned by root with the following command: -+ -+$ sudo chown root /etc/ssh/sshd_configVerify the ownership of the "/etc/ssh/sshd_config" file with the following command: -+ -+$ ls -al /etc/ssh/sshd_config -+ -+rw-------. 1 root root 3669 Feb 22 11:34 /etc/ssh/sshd_config -+ -+If the "/etc/ssh/sshd_config" file does not have an owner of "root", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255115RHEL 9 SSH server configuration file must have mode 0600 or less permissive.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the "/etc/ssh/sshd_config" permissions to be "0600" with the following command: -+ -+$ sudo chmod 0600 /etc/ssh/sshd_configVerify the permissions of the "/etc/ssh/sshd_config" file with the following command: -+ -+$ ls -al /etc/ssh/sshd_config -+ -+rw-------. 1 root root 3669 Feb 22 11:34 /etc/ssh/sshd_config -+ -+If the "/etc/ssh/sshd_config" permissions are not "0600", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255120RHEL 9 SSH private host key files must have mode 0640 or less permissive.<VulnDiscussion>If an unauthorized user obtains the private SSH host key file, the host could be impersonated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the mode of SSH private host key files under "/etc/ssh" to "0640" with the following command: -+ -+$ sudo chmod 0640 /etc/ssh/ssh_host*key -+ -+Restart the SSH daemon for the changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH private host key files have a mode of "0640" or less permissive with the following command: -+ -+$ ls -l /etc/ssh/*_key -+ -+640 /etc/ssh/ssh_host_dsa_key -+640 /etc/ssh/ssh_host_ecdsa_key -+640 /etc/ssh/ssh_host_ed25519_key -+640 /etc/ssh/ssh_host_rsa_key -+ -+If any private host key file has a mode more permissive than "0640", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255125RHEL 9 SSH public host key files must have mode 0644 or less permissive.<VulnDiscussion>If a public host key file is modified by an unauthorized user, the SSH service may be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the mode of public host key files under "/etc/ssh" to "0644" with the following command: -+ -+$ sudo chmod 0644 /etc/ssh/*key.pub -+ -+Restart the SSH daemon for the changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH public host key files have a mode of "0644" or less permissive with the following command: -+ -+Note: SSH public key files may be found in other directories on the system depending on the installation. -+ -+$ sudo stat -c "%a %n" /etc/ssh/*.pub -+ -+644 /etc/ssh/ssh_host_dsa_key.pub -+644 /etc/ssh/ssh_host_ecdsa_key.pub -+644 /etc/ssh/ssh_host_ed25519_key.pub -+644 /etc/ssh/ssh_host_rsa_key.pub -+ -+If any key.pub file has a mode more permissive than "0644", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255130RHEL 9 SSH daemon must not allow compression or must only allow compression after successful authentication.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to not allow compression. -+ -+Uncomment the "Compression" keyword in "/etc/ssh/sshd_config" on the system and set the value to "delayed" or "no": -+ -+Compression no -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon performs compression after a user successfully authenticates with the following command: -+ -+$ sudo grep -ir compression /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+Compression delayed -+ -+If the "Compression" keyword is set to "yes", is missing, or the returned line is commented out, this is a finding.SRG-OS-000364-GPOS-00151<GroupDescription></GroupDescription>RHEL-09-255135RHEL 9 SSH daemon must not allow GSSAPI authentication.<VulnDiscussion>Generic Security Service Application Program Interface (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. -+ -+Satisfies: SRG-OS-000364-GPOS-00151, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001813Configure the SSH daemon to not allow GSSAPI authentication. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "no": -+ -+GSSAPIAuthentication no -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon does not allow GSSAPI authentication with the following command: -+ -+$ sudo grep -ir gssapiauth /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+GSSAPIAuthentication no -+ -+If the value is returned as "yes", the returned line is commented out, no output is returned, and the use of GSSAPI authentication has not been documented with the information system security officer (ISSO), this is a finding. -+ -+If the required value is not set, this is a finding.SRG-OS-000364-GPOS-00151<GroupDescription></GroupDescription>RHEL-09-255140RHEL 9 SSH daemon must not allow Kerberos authentication.<VulnDiscussion>Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Vulnerabilities in the system's Kerberos implementations may be subject to exploitation. -+ -+Satisfies: SRG-OS-000364-GPOS-00151, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001813Configure the SSH daemon to not allow Kerberos authentication. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "no": -+ -+KerberosAuthentication no -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon does not allow Kerberos authentication with the following command: -+ -+$ sudo grep -i kerberosauth /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+KerberosAuthentication no -+ -+If the value is returned as "yes", the returned line is commented out, no output is returned, and the use of Kerberos authentication has not been documented with the information system security officer (ISSO), this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255145RHEL 9 SSH daemon must not allow rhosts authentication.<VulnDiscussion>SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to not allow rhosts authentication. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+IgnoreRhosts yes -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon does not allow rhosts authentication with the following command: -+ -+$ sudo grep -ir ignorerhosts /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+IgnoreRhosts yes -+ -+If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255150RHEL 9 SSH daemon must not allow known hosts authentication.<VulnDiscussion>Configuring the IgnoreUserKnownHosts setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to not allow known hosts authentication. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+IgnoreUserKnownHosts yes -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon does not allow known hosts authentication with the following command: -+ -+$ sudo grep -ir ignoreuser /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+IgnoreUserKnownHosts yes -+ -+If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255155RHEL 9 SSH daemon must disable remote X connections for interactive users.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to not allow X11 forwarding. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+X11forwarding no -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon does not allow X11Forwarding with the following command: -+ -+$ sudo grep -ir x11for /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+X11forwarding no -+ -+If the value is returned as "yes", the returned line is commented out, or no output is returned, and X11 forwarding is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255160RHEL 9 SSH daemon must perform strict mode checking of home directory configuration files.<VulnDiscussion>If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to perform strict mode checking of home directory configuration files. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+StrictModes yes -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon performs strict mode checking of home directory configuration files with the following command: -+ -+$ sudo grep -ir strictmodes /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+StrictModes yes -+ -+If the "StrictModes" keyword is set to "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255165RHEL 9 SSH daemon must display the date and time of the last successful account logon upon an SSH logon.<VulnDiscussion>Providing users feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to provide users with feedback on when account accesses last occurred. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+PrintLastLog yes -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon provides users with feedback on when account accesses last occurred with the following command: -+ -+$ sudo grep -ir printlast /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+PrintLastLog yes -+ -+If the "PrintLastLog" keyword is set to "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255170RHEL 9 SSH daemon must be configured to use privilege separation.<VulnDiscussion>SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabilities in the nonprivileged section.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to perform privilege separation. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes" or "sandbox": -+ -+UsePrivilegeSeparation sandbox -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon performs privilege separation with the following command: -+ -+$ sudo grep -ir usepriv /etc/ssh/sshd_config /etc/ssh/sshd_config.d/* -+ -+UsePrivilegeSeparation sandbox -+ -+If the "UsePrivilegeSeparation" keyword is set to "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-255175RHEL 9 SSH daemon must prevent remote hosts from connecting to the proxy display.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the SSH daemon to prevent remote hosts from connecting to the proxy display. -+ -+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": -+ -+X11UseLocalhost yes -+ -+The SSH service must be restarted for changes to take effect: -+ -+$ sudo systemctl restart sshd.serviceVerify the SSH daemon prevents remote hosts from connecting to the proxy display with the following command: -+ -+$ sudo grep -i x11uselocal /etc/ssh/sshd_config -+ -+X11UseLocalhost yes -+ -+If the "X11UseLocalhost" keyword is set to "no", is missing, or is commented out, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>RHEL-09-271010RHEL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. -+ -+For U.S. Government systems, system use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist. -+ -+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure RHEL 9 to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the system via a graphical user logon. -+ -+Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: -+ -+$ sudo touch /etc/dconf/db/local.d/01-banner-message -+ -+Add the following lines to the [org/gnome/login-screen] section of the "/etc/dconf/db/local.d/01-banner-message": -+ -+[org/gnome/login-screen] -+ -+banner-message-enable=true -+ -+Run the following command to update the database: -+ -+$ sudo dconf updateVerify RHEL 9 displays a banner before granting access to the operating system via a graphical user logon. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine if the operating system displays a banner at the logon screen with the following command: -+ -+$ sudo grep banner-message-enable /etc/dconf/db/local.d/* -+ -+banner-message-enable=true -+ -+If "banner-message-enable" is set to "false", is commented out, or is missing, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>RHEL-09-271015RHEL 9 must prevent a user from overriding the banner-message-enable setting for the graphical user interface.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. -+ -+For U.S. Government systems, system use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist. -+ -+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000048CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure RHEL 9 to prevent a user from overriding the banner setting for graphical user interfaces. -+ -+Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following setting to prevent nonprivileged users from modifying it: -+ -+banner-message-enable -+ -+Run the following command to update the database: -+ -+$ sudo dconf updateVerify RHEL 9 prevents a user from overriding settings for graphical user interfaces. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that graphical settings are locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ sudo grep banner-message-enable /etc/dconf/db/local.d/* -+ -+/org/gnome/login-screen/banner-message-enable -+ -+If the output is not "/org/gnome/login-screen/banner-message-enable", the line is commented out, or the line is missing, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>RHEL-09-271020RHEL 9 must disable the graphical user interface automount function unless required.<VulnDiscussion>Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity. -+ -+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000778CCI-001958Configure the GNOME desktop to disable automated mounting of removable media. -+ -+The dconf settings can be edited in the /etc/dconf/db/* location. -+ -+Update the [org/gnome/desktop/media-handling] section of the "/etc/dconf/db/local.d/00-security-settings" database file and add or update the following lines: -+ -+[org/gnome/desktop/media-handling] -+automount-open=false -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables the graphical user interface automount function with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.desktop.media-handling automount-open -+ -+false -+ -+If "automount-open" is set to "true", and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>RHEL-09-271025RHEL 9 must prevent a user from overriding the disabling of the graphical user interface automount function.<VulnDiscussion>A nonprivileged account is any operating system account with authorizations of a nonprivileged user. -+ -+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000778CCI-001958Configure the GNOME desktop to not allow a user to change the setting that disables automated mounting of removable media. -+ -+Add the following line to "/etc/dconf/db/local.d/locks/00-security-settings-lock" to prevent user modification: -+ -+/org/gnome/desktop/media-handling/automount-open -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables ability of the user to override the graphical user interface automount setting. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that the automount setting is locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ grep 'automount-open' /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/desktop/media-handling/automount-open -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>RHEL-09-271030RHEL 9 must disable the graphical user interface autorun function unless required.<VulnDiscussion>Allowing autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents autorun commands from executing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764Configure the GNOME desktop to disable the autorun function on removable media. -+ -+The dconf settings can be edited in the /etc/dconf/db/* location. -+ -+Update the [org/gnome/desktop/media-handling] section of the "/etc/dconf/db/local.d/00-security-settings" database file and add or update the following lines: -+ -+[org/gnome/desktop/media-handling] -+autorun-never=true -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables the graphical user interface autorun function with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.desktop.media-handling autorun-never -+ -+true -+ -+If "autorun-never" is set to "false", and is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>RHEL-09-271035RHEL 9 must prevent a user from overriding the disabling of the graphical user interface autorun function.<VulnDiscussion>Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators. -+ -+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000778CCI-001958Configure the GNOME desktop to not allow a user to change the setting that disables autorun on removable media. -+ -+Add the following line to "/etc/dconf/db/local.d/locks/00-security-settings-lock" to prevent user modification: -+ -+/org/gnome/desktop/media-handling/autorun-never -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables ability of the user to override the graphical user interface autorun setting. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that the automount setting is locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ grep 'autorun-never' /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/desktop/media-handling/autorun-never -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>RHEL-09-271040RHEL 9 must not allow unattended or automatic logon via the graphical user interface.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the GNOME desktop display manager to disable automatic login. -+ -+Set AutomaticLoginEnable to false in the [daemon] section in /etc/gdm/custom.conf. For example: -+ -+[daemon] -+AutomaticLoginEnable=falseVerify RHEL 9 does not allow an unattended or automatic logon to the system via a graphical user interface. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Check for the value of the "AutomaticLoginEnable" in the "/etc/gdm/custom.conf" file with the following command: -+ -+$ grep -i automaticlogin /etc/gdm/custom.conf -+ -+[daemon] -+AutomaticLoginEnable=false -+ -+If the value of "AutomaticLoginEnable" is not set to "false", this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>RHEL-09-271045RHEL 9 must be able to initiate directly a session lock for all connection types using smart card when the smart card is removed.<VulnDiscussion>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 log out because of the temporary nature of the absence. -+ -+The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, RHEL 9 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity. -+ -+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000058Configure RHEL 9 to enable a user's session lock until that user re-establishes access using established identification and authentication procedures. -+ -+Select or create an authselect profile and incorporate the "with-smartcard-lock-on-removal" feature with the following example: -+ -+$ sudo authselect select sssd with-smartcard with-smartcard-lock-on-removal -+ -+Alternatively, the dconf settings can be edited in the /etc/dconf/db/* location. -+ -+Add or update the [org/gnome/settings-daemon/peripherals/smartcard] section of the /etc/dconf/db/local.d/00-security-settings" database file and add or update the following lines: -+ -+[org/gnome/settings-daemon/peripherals/smartcard] -+removal-action='lock-screen' -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 enables a user's session lock until that user re-establishes access using established identification and authentication procedures with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ grep -R removal-action /etc/dconf/db/* -+ -+/etc/dconf/db/distro.d/20-authselect:removal-action='lock-screen' -+ -+If the "removal-action='lock-screen'" setting is missing or commented out from the dconf database files, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>RHEL-09-271050RHEL 9 must prevent a user from overriding the disabling of the graphical user smart card removal action.<VulnDiscussion>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 log out because of the temporary nature of the absence. -+ -+The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, RHEL 9 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity. -+ -+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000058Add the following line to "/etc/dconf/db/local.d/locks/00-security-settings-lock" to prevent user override of the smart card removal action: -+ -+/org/gnome/settings-daemon/peripherals/smartcard/removal-action -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables ability of the user to override the smart card removal action setting. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that the removal action setting is locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ grep 'removal-action' /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/settings-daemon/peripherals/smartcard/removal-action -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>RHEL-09-271055RHEL 9 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for graphical user sessions.<VulnDiscussion>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 log out because of the temporary nature of the absence. -+ -+The session lock is implemented at the point where session activity can be determined. -+ -+Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. -+ -+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000058Configure RHEL 9 to enable a user's session lock until that user re-establishes access using established identification and authentication procedures. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following example: -+ -+$ sudo vi /etc/dconf/db/local.d/00-screensaver -+ -+Edit the "[org/gnome/desktop/screensaver]" section of the database file and add or update the following lines: -+ -+# Set this to true to lock the screen when the screensaver activates -+lock-enabled=true -+ -+Update the system databases: -+ -+$ sudo dconf updateVerify RHEL 9 enables a user's session lock until that user re-establishes access using established identification and authentication procedures with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.desktop.screensaver lock-enabled -+ -+true -+ -+If the setting is "false", this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>RHEL-09-271060RHEL 9 must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface.<VulnDiscussion>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 log out 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, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock. -+ -+The session lock is implemented at the point where session activity can be determined and/or controlled. -+ -+Implementing session settings will have little value if a user is able to manipulate these settings from the defaults prescribed in the other requirements of this implementation guide. -+ -+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000058Configure RHEL 9 to prevent a user from overriding settings for graphical user interfaces. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+ -+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following setting to prevent nonprivileged users from modifying it: -+ -+/org/gnome/desktop/screensaver/lock-enabledVerify RHEL 9 prevents a user from overriding settings for graphical user interfaces. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that graphical settings are locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ sudo grep -i lock-enabled /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/desktop/screensaver/lock-enabled -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>RHEL-09-271065RHEL 9 must automatically lock graphical user sessions after 15 minutes of inactivity.<VulnDiscussion>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, the GNOME desktop can be configured to identify when a user's session has idled and take action to initiate a session lock. -+ -+Satisfies: SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057CCI-000060Configure RHEL 9 to initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+ -+$ sudo touch /etc/dconf/db/local.d/00-screensaver -+ -+Edit /etc/dconf/db/local.d/00-screensaver and add or update the following lines: -+ -+[org/gnome/desktop/session] -+# Set the lock time out to 900 seconds before the session is considered idle -+idle-delay=uint32 900 -+ -+Update the system databases: -+ -+$ sudo dconf updateVerify RHEL 9 initiates a session lock after a 15-minute period of inactivity for graphical user interfaces with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ sudo gsettings get org.gnome.desktop.session idle-delay -+ -+uint32 900 -+ -+If "idle-delay" is set to "0" or a value greater than "900", this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>RHEL-09-271070RHEL 9 must prevent a user from overriding the session idle-delay setting for the graphical user interface.<VulnDiscussion>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, the GNOME desktop 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. -+ -+Satisfies: SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057CCI-000060Configure RHEL 9 to prevent a user from overriding settings for graphical user interfaces. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+ -+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following setting to prevent nonprivileged users from modifying it: -+ -+/org/gnome/desktop/session/idle-delayVerify RHEL 9 prevents a user from overriding settings for graphical user interfaces. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that graphical settings are locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ sudo grep -i idle /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/desktop/session/idle-delay -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>RHEL-09-271075RHEL 9 must initiate a session lock for graphical user interfaces when the screensaver is activated.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057Configure RHEL 9 to initiate a session lock for graphical user interfaces when a screensaver is activated. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+ -+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. -+ -+$ sudo touch /etc/dconf/db/local.d/00-screensaver -+ -+[org/gnome/desktop/screensaver] -+lock-delay=uint32 5 -+ -+The "uint32" must be included along with the integer key values as shown. -+ -+Update the system databases: -+ -+$ sudo dconf updateVerify RHEL 9 initiates a session lock for graphical user interfaces when the screensaver is activated with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.desktop.screensaver lock-delay -+ -+uint32 5 -+ -+If the "uint32" setting is not set to "5" or less, or is missing, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>RHEL-09-271080RHEL 9 must prevent a user from overriding the session lock-delay setting for the graphical user interface.<VulnDiscussion>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, the GNOME desktop 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057Configure RHEL 9 to prevent a user from overriding settings for graphical user interfaces. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+ -+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following setting to prevent nonprivileged users from modifying it: -+ -+/org/gnome/desktop/screensaver/lock-delayVerify RHEL 9 prevents a user from overriding settings for graphical user interfaces. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that graphical settings are locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ sudo grep -i lock-delay /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/desktop/screensaver/lock-delay -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000031-GPOS-00012<GroupDescription></GroupDescription>RHEL-09-271085RHEL 9 must conceal, via the session lock, information previously visible on the display with a publicly viewable image.<VulnDiscussion>Setting the screensaver mode to blank-only conceals the contents of the display from passersby.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000060The dconf settings can be edited in the /etc/dconf/db/* location. -+ -+First, add or update the [org/gnome/desktop/screensaver] section of the "/etc/dconf/db/local.d/00-security-settings" database file and add or update the following lines: -+ -+[org/gnome/desktop/screensaver] -+picture-uri='' -+ -+Then, add the following line to "/etc/dconf/db/local.d/locks/00-security-settings-lock" to prevent user modification: -+ -+/org/gnome/desktop/screensaver/picture-uri -+ -+Finally, update the dconf system databases: -+ -+$ sudo dconf updateTo ensure the screensaver is configured to be blank, run the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.desktop.screensaver picture-uri -+ -+If properly configured, the output should be "''". -+ -+To ensure that users cannot set the screensaver background, run the following: -+ -+$ grep picture-uri /etc/dconf/db/local.d/locks/* -+ -+If properly configured, the output should be "/org/gnome/desktop/screensaver/picture-uri". -+ -+If it is not set or configured properly, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271090RHEL 9 effective dconf policy must match the policy keyfiles.<VulnDiscussion>Unlike text-based keyfiles, the binary database is impossible to check through most automated and all manual means; 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Update the dconf databases by running the following command: -+ -+$ sudo dconf updateCheck the last modification time of the local databases, comparing it to the last modification time of the related keyfiles. The following command will check every dconf database and compare its modification time to the related system keyfiles: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ function dconf_needs_update { for db in $(find /etc/dconf/db -maxdepth 1 -type f); do db_mtime=$(stat -c %Y "$db"); keyfile_mtime=$(stat -c %Y "$db".d/* | sort -n | tail -1); if [ -n "$db_mtime" ] && [ -n "$keyfile_mtime" ] && [ "$db_mtime" -lt "$keyfile_mtime" ]; then echo "$db needs update"; return 1; fi; done; }; dconf_needs_update -+ -+If the command has any output, then a dconf database needs to be updated, and this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271095RHEL 9 must disable the ability of a user to restart the system from the login screen.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to disable a user's ability to restart the system. -+ -+Add or update the [org/gnome/settings-daemon/] section of the /etc/dconf/db/local.d/00-security-settings" database file and add or update the following lines: -+ -+[org/gnome/settings-daemon/peripherals/smartcard] -+disable-restart-buttons='true' -+ -+Then update the dconf system databases: -+ -+$ sudo dconf updateVerify RHEL 9 disables a user's ability to restart the system with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ grep -R disable-restart-buttons /etc/dconf/db/* -+ -+/etc/dconf/db/distro.d/20-authselect:disable-restart-buttons='true' -+ -+If the "disable-restart-button" setting is not set to "true", is missing or commented out from the dconf database files, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271100RHEL 9 must prevent a user from overriding the disable-restart-buttons setting for the graphical user interface.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to prevent a user from overriding the disable-restart-buttons setting for graphical user interfaces. -+ -+Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following line to prevent nonprivileged users from modifying it: -+ -+/org/gnome/login-screen/disable-restart-buttons -+ -+Run the following command to update the database: -+ -+$ sudo dconf updateVerify RHEL 9 prevents a user from overriding the disable-restart-buttons setting for graphical user interfaces. -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+Determine which profile the system database is using with the following command: -+ -+$ sudo grep system-db /etc/dconf/profile/user -+ -+system-db:local -+ -+Check that graphical settings are locked from nonprivileged user modification with the following command: -+ -+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. -+ -+$ grep disable-restart-buttons /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/login-screen/disable-restart-buttons -+ -+If the command does not return at least the example result, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271105RHEL 9 must disable the ability of a user to accidentally press Ctrl-Alt-Del and cause a system to shut down or reboot.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to ignore the Ctrl-Alt-Del sequence in the GNOME desktop. -+ -+Add or update the [org/gnome/settings-daemon/plugins/media-keys] section of the /etc/dconf/db/local.d/00-security-settings database file and add or update the following lines: -+ -+[org/gnome/settings-daemon/plugins/media-keys] -+logout=[''] -+ -+Run the following command to update the database: -+ -+$ sudo dconf updateVerify RHEL 9 is configured to ignore the Ctrl-Alt-Del sequence in the GNOME desktop with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ gsettings get org.gnome.settings-daemon.plugins.media-keys logout -+ -+"['']" -+ -+If the GNOME desktop is configured to shut down when Ctrl-Alt-Del is pressed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271110RHEL 9 must prevent a user from overriding the Ctrl-Alt-Del sequence settings for the graphical user interface.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to disallow the user changing the Ctrl-Alt-Del sequence in the GNOME desktop. -+ -+Create a database to container system-wide graphical user logon settings (if it does not already exist) with the following command: -+ -+$ sudo touch /etc/dconf/db/local.d/locks/session -+ -+Add the following line to the session locks file to prevent nonprivileged users from modifying the Ctrl-Alt-Del setting: -+ -+/org/gnome/settings-daemon/plugins/media-keys/logout -+ -+Run the following command to update the database: -+ -+$ sudo dconf updateVerify that users cannot enable the Ctrl-Alt-Del sequence in the GNOME desktop with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ grep logout /etc/dconf/db/local.d/locks/* -+ -+/org/gnome/settings-daemon/plugins/media-keys/logout -+ -+If the output is not "/org/gnome/settings-daemon/plugins/media-keys/logout", the line is commented out, or the line is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-271115RHEL 9 must disable the user list at logon for graphical user interfaces.<VulnDiscussion>Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to enumerate known user accounts without authenticated access to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to disable the user list at logon for graphical user interfaces. -+ -+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: -+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. -+ -+$ sudo touch /etc/dconf/db/local.d/02-login-screen -+ -+[org/gnome/login-screen] -+disable-user-list=true -+ -+Update the system databases: -+ -+$ sudo dconf updateVerify that RHEL 9 disables the user logon list for graphical user interfaces with the following command: -+ -+Note: This requirement assumes the use of the RHEL 9 default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable. -+ -+$ sudo gsettings get org.gnome.login-screen disable-user-list -+true -+ -+If the setting is "false", this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>RHEL-09-291010RHEL 9 must be configured to disable USB mass storage.<VulnDiscussion>USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity. -+ -+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000778CCI-001958To 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 (or create usb-storage.conf if it does not exist): -+ -+install usb-storage /bin/false -+blacklist usb-storageVerify that RHEL 9 disables the ability to load the USB Storage kernel module with the following command: -+ -+$ sudo grep -r usb-storage /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist usb-storage -+ -+If the command does not return any output, or the line is commented out, and use of USB Storage is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000378-GPOS-00163<GroupDescription></GroupDescription>RHEL-09-291015RHEL 9 must have the USBGuard package installed.<VulnDiscussion>The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device authorization policy for all USB devices. The policy is defined by a set of rules using a rule language described in the usbguard-rules.conf file. The policy and the authorization state of USB devices can be modified during runtime using the usbguard tool. -+ -+The system administrator (SA) must work with the site information system security officer (ISSO) to determine a list of authorized peripherals and establish rules within the USBGuard software framework to allow only authorized devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001958Install the usbguard package with the following command: -+ -+$ sudo dnf install usbguardVerify USBGuard is installed on the operating system with the following command: -+ -+$ sudo dnf list installed usbguard -+ -+Example output: -+ -+Installed Packages -+usbguard.x86_64 1.0.0-10.el9_1.2 @rhel-9-for-x86_64-appstream-rpms -+ -+If the USBGuard package is not installed, ask the SA to indicate how unauthorized peripherals are being blocked. -+ -+If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.SRG-OS-000378-GPOS-00163<GroupDescription></GroupDescription>RHEL-09-291020RHEL 9 must have the USBGuard package enabled.<VulnDiscussion>The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device authorization policy for all USB devices. The policy is defined by a set of rules using a rule language described in the usbguard-rules.conf file. The policy and the authorization state of USB devices can be modified during runtime using the usbguard tool. -+ -+The system administrator (SA) must work with the site information system security officer (ISSO) to determine a list of authorized peripherals and establish rules within the USBGuard software framework to allow only authorized devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001958To enable the USBGuard service run the following command: -+ -+$ sudo systemctl enable --now usbguardVerify RHEL 9 has USBGuard enabled with the following command: -+ -+$ systemctl is-active usbguard -+ -+active -+ -+If usbguard is not active, ask the SA to indicate how unauthorized peripherals are being blocked. -+ -+If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>RHEL-09-291025RHEL 9 must enable Linux audit logging for the USBGuard daemon.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. -+ -+If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. -+ -+Audit records can be generated from various components within the information system (e.g., module or policy filter). -+ -+The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. -+ -+DOD has defined the list of events for which RHEL 9 will provide an audit record generation capability as the following: -+ -+1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); -+ -+2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; -+ -+3) All account creations, modifications, disabling, and terminations; and -+ -+4) All kernel module load, unload, and restart actions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000169Configure RHEL 9 USBGuard AuditBackend to use the audit system. -+ -+Add or edit the following line in /etc/usbguard/usbguard-daemon.conf -+ -+AuditBackend=LinuxAuditTo verify that Linux Audit logging is enabled for the USBGuard daemon with the following command: -+ -+$ sudo grep AuditBackend /etc/usbguard/usbguard-daemon.conf -+ -+AuditBackend=LinuxAudit -+ -+If "AuditBackend" is not set to "LinuxAudit", this is a finding.SRG-OS-000378-GPOS-00163<GroupDescription></GroupDescription>RHEL-09-291030RHEL 9 must block unauthorized peripherals before establishing a connection.<VulnDiscussion>The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device authorization policy for all USB devices. The policy is defined by a set of rules using a rule language described in the usbguard-rules.conf file. The policy and the authorization state of USB devices can be modified during runtime using the usbguard tool. -+ -+The system administrator (SA) must work with the site information system security officer (ISSO) to determine a list of authorized peripherals and establish rules within the USBGuard software framework to allow only authorized devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001958Configure the operating system to enable the blocking of unauthorized peripherals with the following command: -+ -+Note: This command must be run from a root shell and will create an allow list for any usb devices currently connect to the system. -+ -+# usbguard generate-policy --no-hash > /etc/usbguard/rules.conf -+ -+Note: Enabling and starting usbguard without properly configuring it for an individual system will immediately prevent any access over a usb device such as a keyboard or mouse.Verify the USBGuard has a policy configured with the following command: -+ -+$ usbguard list-rules -+ -+allow id 1d6b:0001 serial -+ -+If the command does not return results or an error is returned, ask the SA to indicate how unauthorized peripherals are being blocked. -+ -+If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>RHEL-09-291035RHEL 9 Bluetooth must be disabled.<VulnDiscussion>This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 9 systems. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR keyboards, mice and pointing devices, and near field communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DOD requirements for wireless data transmission and be approved for use by the Authorizing Official (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the RHEL 9 operating system. -+ -+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000300-GPOS-00118</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000381CCI-001443Configure RHEL 9 to disable the Bluetooth adapter when not in use. -+ -+Create or modify the "/etc/modprobe.d/bluetooth.conf" file with the following line: -+ -+install bluetooth /bin/false -+blacklist bluetooth -+ -+Reboot the system for the settings to take effect.Verify that RHEL 9 disables the ability to load the Bluetooth kernel module with the following command: -+ -+$ sudo grep -r bluetooth /etc/modprobe.conf /etc/modprobe.d/* -+ -+blacklist bluetooth -+ -+If the command does not return any output, or the line is commented out, and use of Bluetooth is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000299-GPOS-00117<GroupDescription></GroupDescription>RHEL-09-291040RHEL 9 wireless network adapters must be disabled.<VulnDiscussion>This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 9 systems. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR keyboards, mice and pointing devices, and near field communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DOD requirements for wireless data transmission and be approved for use by the Authorizing Official (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the RHEL 9 operating system. -+ -+Satisfies: SRG-OS-000299-GPOS-00117, SRG-OS-000300-GPOS-00118, SRG-OS-000424-GPOS-00188, SRG-OS-000481-GPOS-00481</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001443CCI-001444CCI-002418CCI-002421Configure the system to disable all wireless network interfaces with the following command: -+ -+$ nmcli radio all offVerify there are no wireless interfaces configured on the system with the following command: -+ -+Note: This requirement is Not Applicable for systems that do not have physical wireless network radios. -+ -+$ nmcli device status -+ -+DEVICE TYPE STATE CONNECTION -+virbr0 bridge connected virbr0 -+wlp7s0 wifi connected wifiSSID -+enp6s0 ethernet disconnected -- -+p2p-dev-wlp7s0 wifi-p2p disconnected -- -+lo loopback unmanaged -- -+virbr0-nic tun unmanaged -- -+ -+If a wireless interface is configured and has not been documented and approved by the information system security officer (ISSO), this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>RHEL-09-411010RHEL 9 user account passwords for new users or password changes must have a 60-day maximum password lifetime restriction in /etc/login.defs.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000199Configure RHEL 9 to enforce a 60-day maximum password lifetime. -+ -+Add or modify the following line in the "/etc/login.defs" file: -+ -+PASS_MAX_DAYS 60Verify that RHEL 9 enforces a 60-day maximum password lifetime for new user accounts by running the following command: -+ -+$ grep -i pass_max_days /etc/login.defs -+ -+PASS_MAX_DAYS 60 -+ -+If the "PASS_MAX_DAYS" parameter value is greater than "60", or commented out, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>RHEL-09-411015RHEL 9 user account passwords must have a 60-day maximum password lifetime restriction.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked; therefore, passwords need to be changed periodically. If RHEL 9 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 9 passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000199Configure noncompliant accounts to enforce a 60-day maximum password lifetime restriction. -+ -+passwd -x 60 [user]Check whether the maximum time period for existing passwords is restricted to 60 days with the following commands: -+ -+$ sudo awk -F: '$5 > 60 {print $1 "" "" $5}' /etc/shadow -+ -+$ sudo awk -F: '$5 <= 0 {print $1 "" "" $5}' /etc/shadow -+ -+If any results are returned that are not associated with a system account, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411020All RHEL 9 local interactive user accounts must be assigned a home directory upon creation.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 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 yesVerify all local interactive users on RHEL 9 are assigned a home directory upon creation with the following command: -+ -+$ grep -i create_home /etc/login.defs -+ -+CREATE_HOME yes -+ -+If the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411025RHEL 9 must set the umask value to 077 for all local interactive user accounts.<VulnDiscussion>The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove the umask statement from all local interactive user's initialization files. -+ -+If the account is for an application, the requirement for a umask less restrictive than "077" can be documented with the information system security officer, but the user agreement for access to the account must specify that the local interactive user must log on to their account first and then switch the user to the application account with the correct option to gain the account's environment variables.Verify that the default umask for all local interactive users is "077". -+ -+Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file. -+ -+Check all local interactive user initialization files for interactive users with the following command: -+ -+Note: The example is for a system that is configured to create users home directories in the "/home" directory. -+ -+# grep -ri umask /home/ -+ -+/home/wadea/.bash_history:grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile -+/home/wadea/.bash_history:grep -i umask /etc/login.defs -+ -+If any local interactive user initialization files are found to have a umask statement that sets a value less restrictive than "077", this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>RHEL-09-411030RHEL 9 duplicate User IDs (UIDs) must not exist for interactive users.<VulnDiscussion>To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system. -+ -+Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062, SRG-OS-000042-GPOS-00020</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000135CCI-000764CCI-000804Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate UID with a unique UID.Verify that RHEL 9 contains no duplicate UIDs for interactive users with the following command: -+ -+$ sudo awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd -+ -+If output is produced and the accounts listed are interactive user accounts, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411035RHEL 9 system accounts must not have an interactive login shell.<VulnDiscussion>Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 so that all noninteractive accounts on the system do not have an interactive shell assigned to them. -+ -+If the system account needs a shell assigned for mission operations, document the need with the information system security officer (ISSO). -+ -+Run the following command to disable the interactive shell for a specific noninteractive user account: -+ -+Replace <user> with the user that has a login shell. -+ -+$ sudo usermod --shell /sbin/nologin <user> -+ -+Do not perform the steps in this section on the root account. Doing so will cause the system to become inaccessible.Verify that system accounts must not have an interactive login shell with the following command: -+ -+$ awk -F: '($3<1000){print $1 ":" $3 ":" $7}' /etc/passwd -+ -+root:0:/bin/bash -+bin:1:/sbin/nologin -+daemon:2:/sbin/nologin -+adm:3:/sbin/nologin -+lp:4:/sbin/nologin -+ -+Identify the system accounts from this listing that do not have a nologin shell. -+ -+If any system account (other than the root account) has a login shell and it is not documented with the information system security officer (ISSO), this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>RHEL-09-411040RHEL 9 must automatically expire temporary accounts within 72 hours.<VulnDiscussion>Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors. -+ -+Temporary accounts are different from emergency accounts. Emergency accounts, also known as "last resort" or "break glass" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements. -+ -+The automatic expiration of temporary accounts may be extended as needed by the circumstances but it must not be extended indefinitely. A documented permanent account should be established for privileged users who need long-term maintenance accounts. -+ -+Satisfies: SRG-OS-000123-GPOS-00064, SRG-OS-000002-GPOS-00002</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000016CCI-001682Configure the operating system to expire temporary accounts after 72 hours with the following command: -+ -+$ sudo chage -E $(date -d +3days +%Y-%m-%d) <temporary_account_name>Verify temporary accounts have been provisioned with an expiration date of 72 hours. -+ -+For every existing temporary account, run the following command to obtain its account expiration information: -+ -+$ sudo chage -l <temporary_account_name> | grep -i "account expires" -+ -+Verify each of these accounts has an expiration date set within 72 hours. -+ -+If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>RHEL-09-411045All RHEL 9 interactive users must have a primary group that exists.<VulnDiscussion>If a user is assigned the Group Identifier (GID) of a group that does not exist on the system, and a group with the GID is subsequently created, the user may have unintended rights to any files associated with the group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000764Configure the system so that all GIDs are referenced in "/etc/passwd" are defined in "/etc/group". -+ -+Edit the file "/etc/passwd" and ensure that every user's GID is a valid GID.Verify that all RHEL 9 interactive users have a valid GID. -+ -+Check that the interactive users have a valid GID with the following command: -+ -+$ sudo pwck -qr -+ -+If the system has any interactive users with duplicate GIDs, this is a finding.SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>RHEL-09-411050RHEL 9 must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000795Configure RHEL 9 to disable account identifiers after 35 days of inactivity after the password expiration. -+ -+Run the following command to change the configuration for useradd: -+ -+$ sudo useradd -D -f 35 -+ -+The recommendation is 35 days, but a lower value is acceptable.Verify that RHEL 9 account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity with the following command: -+ -+Check the account inactivity value by performing the following command: -+ -+$ sudo grep -i inactive /etc/default/useradd -+ -+INACTIVE=35 -+ -+If "INACTIVE" is set to "-1", a value greater than "35", or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411055Executable search paths within the initialization files of all local interactive RHEL 9 users must only contain paths that resolve to the system default or the users home directory.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Edit the local interactive user initialization files to change any PATH variable statements that reference directories other than their home directory. -+ -+If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the ISSO.Verify that all local interactive user initialization file executable search path statements do not contain statements that will reference a working directory other than user home directories with the following commands: -+ -+$ sudo grep -i path= /home/*/.* -+ -+/home/[localinteractiveuser]/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin -+ -+If any local interactive user initialization files have executable search path statements that include directories outside of their home directory and is not documented with the ISSO as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411060All RHEL 9 local interactive users must have a home directory assigned in the /etc/passwd file.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Create and assign home directories to all local interactive users on RHEL 9 that currently do not have a home directory assigned.Verify that interactive users on the system have a home directory assigned with the following command: -+ -+$ sudo awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6}' /etc/passwd -+ -+smithk:x:1000:1000:smithk:/home/smithk:/bin/bash -+scsaustin:x:1001:1001:scsaustin:/home/scsaustin:/bin/bash -+djohnson:x:1002:1002:djohnson:/home/djohnson:/bin/bash -+ -+Inspect the output and verify that all interactive users (normally users with a user identifier (UID) greater that 1000) have a home directory defined. -+ -+If users home directory is not defined, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411065All RHEL 9 local interactive user home directories defined in the /etc/passwd file must exist.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Create 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": -+ -+Note: The example will be for the user wadea, who has a home directory of "/home/wadea", a user identifier (UID) of "wadea", and a Group Identifier (GID) of "users assigned" in "/etc/passwd". -+ -+$ sudo mkdir /home/wadea -+$ sudo chown wadea /home/wadea -+$ sudo chgrp users /home/wadea -+$ sudo chmod 0750 /home/wadeaVerify the assigned home directories of all interactive users on the system exist with the following command: -+ -+$ sudo pwck -r -+ -+user 'mailnull': directory 'var/spool/mqueue' does not exist -+ -+The output should not return any interactive users. -+ -+If users home directory does not exist, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411070All RHEL 9 local interactive user home directories must be group-owned by the home directory owner's primary group.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the group owner of a local interactive user's home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user's home directory, use the following command: -+ -+Note: The example will be for the user "wadea", who has a home directory of "/home/wadea", and has a primary group of users. -+ -+$ sudo chgrp users /home/wadeaVerify the assigned home directory of all local interactive users is group-owned by that user's primary GID with the following command: -+ -+Note: This may miss local interactive users that have been assigned a privileged user identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. The returned directory "/home/wadea" is used as an example. -+ -+$ sudo ls -ld $(awk -F: '($3>=1000)&&($7 !~ /nologin/){print $6}' /etc/passwd) -+ -+drwxr-x--- 2 wadea admin 4096 Jun 5 12:41 wadea -+ -+Check the user's primary group with the following command: -+ -+$ sudo grep $(grep wadea /etc/passwd | awk -F: ‘{print $4}') /etc/group -+ -+admin:x:250:wadea,jonesj,jacksons -+ -+If the user home directory referenced in "/etc/passwd" is not group-owned by that user's primary GID, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>RHEL-09-411075RHEL 9 must automatically lock an account when three unsuccessful logon attempts occur.<VulnDiscussion>By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. -+ -+Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044CCI-002238Configure RHEL 9 to lock an account when three unsuccessful logon attempts occur. -+ -+Add/modify the "/etc/security/faillock.conf" file to match the following line: -+ -+deny = 3Verify RHEL 9 is configured to lock an account after three unsuccessful logon attempts with the command: -+ -+$ grep 'deny =' /etc/security/faillock.conf -+ -+deny = 3 -+ -+If the "deny" option is not set to "3" or less (but not "0"), is missing or commented out, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>RHEL-09-411080RHEL 9 must automatically lock the root account until the root account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044CCI-002238Configure RHEL 9 to lock out the "root" account after a number of incorrect login attempts using "pam_faillock.so", first enable the feature using the following command: -+ -+$ sudo authselect enable-feature with-faillock -+ -+ Then edit the "/etc/security/faillock.conf" file as follows: -+ -+ add or uncomment the following line: -+ even_deny_rootVerify RHEL 9 is configured to lock the root account after three unsuccessful logon attempts with the command: -+ -+$ grep even_deny_root /etc/security/faillock.conf -+ -+even_deny_root -+ -+If the "even_deny_root" option is not set, is missing or commented out, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>RHEL-09-411085RHEL 9 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044CCI-002238To configure RHEL 9 to lock out the "root" account after a number of incorrect login attempts within 15 minutes using "pam_faillock.so", enable the feature using the following command: -+ -+$ authselect enable-feature with-faillock -+ -+Then edit the "/etc/security/faillock.conf" file as follows: -+ -+fail_interval = 900Verify RHEL 9 locks an account after three unsuccessful logon attempts within a period of 15 minutes with the following command: -+ -+Note: If the system administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is Not Applicable. -+ -+$ grep fail_interval /etc/security/faillock.conf -+ -+fail_interval = 900 -+ -+If the "fail_interval" option is not set to "900" or less (but not "0"), the line is commented out, or the line is missing, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>RHEL-09-411090RHEL 9 must maintain an account lock until the locked account is released by an administrator.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044CCI-002238Configure RHEL 9 to lock an account until released by an administrator after three unsuccessful logon attempts with the command: -+ -+$ authselect enable-feature with-faillock -+ -+Then edit the "/etc/security/faillock.conf" file as follows: -+ -+unlock_time = 0Verify RHEL 9 is configured to lock an account until released by an administrator after three unsuccessful logon attempts with the command: -+ -+$ grep 'unlock_time =' /etc/security/faillock.conf -+ -+unlock_time = 0 -+ -+If the "unlock_time" option is not set to "0", the line is missing, or commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411095RHEL 9 must not have unauthorized accounts.<VulnDiscussion>Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove unauthorized local interactive user accounts with the following command where <unauthorized_user> is the unauthorized account: -+ -+$ sudo userdel <unauthorized_user>Verify that there are no unauthorized interactive user accounts with the following command: -+ -+$ less /etc/passwd -+ -+root:x:0:0:root:/root:/bin/bash -+... -+games:x:12:100:games:/usr/games:/sbin/nologin -+scsaustin:x:1001:1001:scsaustin:/home/scsaustin:/bin/bash -+djohnson:x:1002:1002:djohnson:/home/djohnson:/bin/bash -+ -+Interactive user account, generally will have a user identifier (UID) of 1000 or greater, a home directory in a specific partition, and an interactive shell. -+ -+Obtain the list of interactive user accounts authorized to be on the system from the system administrator or information system security officer (ISSO) and compare it to the list of local interactive user accounts on the system. -+ -+If there are unauthorized local user accounts on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411100The root account must be the only account having unrestricted access to RHEL 9 system.<VulnDiscussion>An account has root authority if it has a user identifier (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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Change the UID of any account on the system, other than root, that has a UID of "0". -+ -+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 of greater than "1000" that has not already been assigned.Verify that only the "root" account has a UID "0" assignment with the following command: -+ -+$ awk -F: '$3 == 0 {print $1}' /etc/passwd -+ -+root -+ -+If any accounts other than "root" have a UID of "0", this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>RHEL-09-411105RHEL 9 must ensure account lockouts persist.<VulnDiscussion>Having lockouts persist across reboots ensures that account is only unlocked by an administrator. If the lockouts did not persist across reboots, an attacker could simply reboot the system to continue brute force attacks against the accounts on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044Configure RHEL 9 maintain the contents of the faillock directory after a reboot. -+ -+Add/modify the "/etc/security/faillock.conf" file to match the following line: -+ -+dir = /var/log/faillockVerify the "/etc/security/faillock.conf" file is configured use a nondefault faillock directory to ensure contents persist after reboot with the following command: -+ -+$ grep 'dir =' /etc/security/faillock.conf -+ -+dir = /var/log/faillock -+ -+If the "dir" option is not set to a nondefault documented tally log directory, is missing or commented out, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>RHEL-09-411110RHEL 9 groups must have unique Group ID (GID).<VulnDiscussion>To ensure accountability and prevent unauthenticated access, groups must be identified uniquely to prevent potential misuse and compromise of the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000764Edit the file "/etc/group" and provide each group that has a duplicate GID with a unique GID.Verify that RHEL 9 contains no duplicate GIDs for interactive users with the following command: -+ -+ $ cut -d : -f 3 /etc/group | uniq -d -+ -+If the system has duplicate GIDs, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-411115Local RHEL 9 initialization files must not execute world-writable programs.<VulnDiscussion>If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Set the mode on files being executed by the local initialization files with the following command: -+ -+$ sudo chmod 0755 <file>Verify that local initialization files do not execute world-writable programs with the following command: -+ -+Note: The example will be for a system that is configured to create user home directories in the "/home" directory. -+ -+$ sudo find /home -perm -002 -type f -name ".[^.]*" -exec ls -ld {} \; -+ -+If any local initialization files are found to reference world-writable files, this is a finding.SRG-OS-000030-GPOS-00011<GroupDescription></GroupDescription>RHEL-09-412010RHEL 9 must have the tmux package installed.<VulnDiscussion>Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package. -+ -+Satisfies: SRG-OS-000030-GPOS-00011, SRG-OS-000028-GPOS-00009</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000058The tmux package can be installed with the following command: -+ -+$ sudo dnf install tmuxVerify that RHEL 9 has the tmux package installed with the following command: -+ -+$ sudo dnf list --installed tmux -+ -+Example output: -+ -+tmux.x86_64 3.2a-4.el9 -+ -+If the "tmux" package is not installed, this is a finding.SRG-OS-000031-GPOS-00012<GroupDescription></GroupDescription>RHEL-09-412015RHEL 9 must ensure session control is automatically started at shell initialization.<VulnDiscussion>Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package. -+ -+Satisfies: SRG-OS-000031-GPOS-00012, SRG-OS-000028-GPOS-00009</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-000060Configure RHEL 9 to initialize the tmux terminal multiplexer as each shell is called by adding the following to file "/etc/profile.d/tmux.sh": -+ -+if [ "$PS1" ]; then -+ parent=$(ps -o ppid= -p $$) -+ name=$(ps -o comm= -p $parent) -+ case "$name" in sshd|login) tmux ;; esac -+fiVerify RHEL 9 shell initialization file is configured to start each shell with the tmux terminal multiplexer. -+ -+Determine the location of the tmux script with the following command: -+ -+$ sudo grep tmux /etc/bashrc /etc/profile.d/* -+ -+/etc/profile.d/tmux.sh: case "$name" in (sshd|login) exec tmux ;; esac -+ -+Review the tmux script by using the following example: -+ -+$ cat /etc/profile.d/tmux.sh -+ -+If [ "$PS1" ]; then -+parent=$(ps -o ppid= -p $$) -+name=$(ps -o comm= -p $parent) -+case "$name" in (sshd|login) tmux ;; esac -+fi -+ -+If the shell file is not configured as the example above, is commented out, or is missing, this is a finding. -+ -+Determine if tmux is currently running with the following command: -+ -+$ sudo ps all | grep tmux | grep -v grep -+ -+If the command does not produce output, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>RHEL-09-412020RHEL 9 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for command line sessions.<VulnDiscussion>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 log out because of the temporary nature of the absence. -+ -+The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, RHEL 9 must provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056Configure RHEL 9 to enable a user to manually initiate a session lock via tmux. This configuration binds the uppercase letter "X" to manually initiate a session lock after the prefix key "Ctrl + b" has been sent. The complete key sequence is thus "Ctrl + b" then "Shift + x" to lock tmux. -+ -+Create a global configuration file "/etc/tmux.conf" and add the following lines: -+ -+set -g lock-command vlock -+bind X lock-session -+ -+Reload tmux configuration to take effect. This can be performed in tmux while it is running: -+ -+$ tmux source-file /etc/tmux.confVerify RHEL 9 enables the user to initiate a session lock with the following command: -+ -+$ sudo grep -Ei 'lock-command|lock-session' /etc/tmux.conf -+ -+set -g lock-command vlock -+bind X lock-session -+ -+If the "lock-command" is not set and "lock-session" is not bound to a specific keyboard key in the global settings, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>RHEL-09-412025RHEL 9 must automatically lock command line user sessions after 15 minutes of inactivity.<VulnDiscussion>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, tmux can be configured to identify when a user's session has idled and take action to initiate a session lock. -+ -+Satisfies: SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057CCI-000060Configure RHEL 9 to enforce session lock after a period of 15 minutes of inactivity by adding the following line to the "/etc/tmux.conf" global configuration file: -+ -+set -g lock-after-time 900Verify RHEL 9 initiates a session lock after 15 minutes of inactivity. -+ -+Check the value of the system inactivity timeout with the following command: -+ -+$ grep -i lock-after-time /etc/tmux.conf -+ -+set -g lock-after-time 900 -+ -+If "lock-after-time" is not set to "900" or less in the global tmux configuration file to enforce session lock after inactivity, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>RHEL-09-412030RHEL 9 must prevent users from disabling session control mechanisms.<VulnDiscussion>The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, RHEL 9 must provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity. -+ -+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000028-GPOS-00009</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000056CCI-002235Configure RHEL 9 to prevent users from disabling the tmux terminal multiplexer by editing the "/etc/shells" configuration file to remove any instances of tmux.Verify RHEL 9 prevents users from disabling the tmux terminal multiplexer with the following command: -+ -+$ grep -i tmux /etc/shells -+ -+If any output is produced, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>RHEL-09-412035RHEL 9 must automatically exit interactive command shell user sessions after 15 minutes of inactivity.<VulnDiscussion>Terminating an idle interactive command shell user session within a short time period reduces the window of opportunity for unauthorized personnel to take control of it when left unattended in a virtual terminal or physical console. -+ -+Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000029-GPOS-00010</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000057CCI-001133Configure RHEL 9 to exit interactive command shell user sessions after 15 minutes of inactivity. -+ -+Add or edit the following line in "/etc/profile.d/tmout.sh": -+ -+#!/bin/bash -+ -+declare -xr TMOUT=900Verify RHEL 9 is configured to exit interactive command shell user sessions after 15 minutes of inactivity or less with the following command: -+ -+$ sudo grep -i tmout /etc/profile /etc/profile.d/*.sh -+ -+/etc/profile.d/tmout.sh:declare -xr TMOUT=900 -+ -+If "TMOUT" is not set to "900" or less in a script located in the "/etc/'profile.d/ directory, is missing or is commented out, this is a finding.SRG-OS-000027-GPOS-00008<GroupDescription></GroupDescription>RHEL-09-412040RHEL 9 must limit the number of concurrent sessions to ten for all accounts and/or account types.<VulnDiscussion>Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to denial-of-service (DoS) attacks. -+ -+This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions must be defined based on mission needs and the operational environment for each system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000054Configure RHEL 9 to limit the number of concurrent sessions to "10" for all accounts and/or account types. -+ -+Add the following line to the top of the /etc/security/limits.conf or in a ".conf" file defined in /etc/security/limits.d/: -+ -+* hard maxlogins 10Verify RHEL 9 limits the number of concurrent sessions to "10" for all accounts and/or account types with the following command: -+ -+$ grep -r -s maxlogins /etc/security/limits.conf /etc/security/limits.d/*.conf -+ -+/etc/security/limits.conf:* hard maxlogins 10 -+ -+This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. -+ -+If the "maxlogins" item is missing, commented out, or the value is set greater than "10" and is not documented with the information system security officer (ISSO) as an operational requirement for all domains that have the "maxlogins" item assigned, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>RHEL-09-412045RHEL 9 must log username information when unsuccessful logon attempts occur.<VulnDiscussion>Without auditing of these events, it may be harder or impossible to identify what an attacker did after an attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044Configure RHEL 9 to log username information when unsuccessful logon attempts occur. -+ -+Add/modify the "/etc/security/faillock.conf" file to match the following line: -+ -+auditVerify the "/etc/security/faillock.conf" file is configured to log username information when unsuccessful logon attempts occur with the following command: -+ -+$ grep audit /etc/security/faillock.conf -+ -+audit -+ -+If the "audit" option is not set, is missing, or is commented out, this is a finding.SRG-OS-000480-GPOS-00226<GroupDescription></GroupDescription>RHEL-09-412050RHEL 9 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.<VulnDiscussion>Increasing the time between a failed authentication attempt and reprompting to enter credentials helps to slow a single-threaded brute force attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the RHEL 9 to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt. -+ -+Modify the "/etc/login.defs" file to set the "FAIL_DELAY" parameter to 4 or greater: -+ -+FAIL_DELAY 4Verify RHEL 9 enforces a delay of at least four seconds between console logon prompts following a failed logon attempt with the following command: -+ -+$ grep -i fail_delay /etc/login.defs -+ -+FAIL_DELAY 4 -+ -+If the value of "FAIL_DELAY" is not set to "4" or greater, or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>RHEL-09-412055RHEL 9 must define default permissions for the bash shell.<VulnDiscussion>The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 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. -+ -+Satisfies: SRG-OS-000480-GPOS-00228, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to define default permissions for all authenticated users using the bash shell. -+ -+Add or edit the lines for the "umask" parameter in the "/etc/bashrc" file to "077": -+ -+umask 077Verify the "umask" setting is configured correctly in the "/etc/bashrc" file with the following command: -+ -+Note: If the value of the "umask" parameter is set to "000" "/etc/bashrc" file, the Severity is raised to a CAT I. -+ -+$ grep umask /etc/bashrc -+ -+umask 077 -+umask 077 -+ -+If the value for the "umask" parameter is not "077", or the "umask" parameter is missing or is commented out, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>RHEL-09-412060RHEL 9 must define default permissions for the c shell.<VulnDiscussion>The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 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. -+ -+Satisfies: SRG-OS-000480-GPOS-00228, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to define default permissions for all authenticated users using the c shell. -+ -+Add or edit the lines for the "umask" parameter in the "/etc/csh.cshrc" file to "077": -+ -+umask 077Verify the "umask" setting is configured correctly in the "/etc/csh.cshrc" file with the following command: -+ -+Note: If the value of the "umask" parameter is set to "000" "/etc/csh.cshrc" file, the Severity is raised to a CAT I. -+ -+$ grep umask /etc/csh.cshrc -+ -+umask 077 -+umask 077 -+ -+If the value for the "umask" parameter is not "077", or the "umask" parameter is missing or is commented out, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>RHEL-09-412065RHEL 9 must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.<VulnDiscussion>Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. -+ -+Add or edit the lines for the "UMASK" parameter in the "/etc/login.defs" file to "077": -+ -+UMASK 077Verify RHEL 9 defines default permissions for all authenticated users in such a way that the user can only read and modify their own files with the following command: -+ -+Note: If the value of the "UMASK" parameter is set to "000" in "/etc/login.defs" file, the Severity is raised to a CAT I. -+ -+# grep -i umask /etc/login.defs -+ -+UMASK 077 -+ -+If the value for the "UMASK" parameter is not "077", or the "UMASK" parameter is missing or is commented out, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>RHEL-09-412070RHEL 9 must define default permissions for the system default profile.<VulnDiscussion>The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 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. -+ -+Satisfies: SRG-OS-000480-GPOS-00228, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. -+ -+Add or edit the lines for the "umask" parameter in the "/etc/profile" file to "077": -+ -+umask 077Verify the "umask" setting is configured correctly in the "/etc/profile" file with the following command: -+ -+Note: If the value of the "umask" parameter is set to "000" "/etc/profile" file, the Severity is raised to a CAT I. -+ -+$ grep umask /etc/profile -+ -+umask 077 -+ -+If the value for the "umask" parameter is not "077", or the "umask" parameter is missing or is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-412075RHEL 9 must display the date and time of the last successful account logon upon logon.<VulnDiscussion>Users need to be aware of activity that occurs regarding their account. Providing users with information regarding the number of unsuccessful attempts that were made to login to their account allows the user to determine if any unauthorized activity has occurred and gives them an opportunity to notify administrators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/postlogin". -+ -+Add the following line to the top of "/etc/pam.d/postlogin": -+ -+session required pam_lastlog.so showfailedVerify users are provided with feedback on when account accesses last occurred with the following command: -+ -+$ sudo grep pam_lastlog /etc/pam.d/postlogin -+ -+session required pam_lastlog.so showfailed -+ -+If "pam_lastlog" is missing from "/etc/pam.d/postlogin" file, or the silent option is present, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>RHEL-09-412080RHEL 9 must terminate idle user sessions.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001133Configure RHEL 9 to log out idle sessions by editing the /etc/systemd/logind.conf file with the following line: -+ -+StopIdleSessionSec=900 -+ -+The "logind" service must be restarted for the changes to take effect. To restart the "logind" service, run the following command: -+ -+$ sudo systemctl restart systemd-logind -+ -+Note: To preserve running user programs such as tmux, uncomment and/or edit "KillUserProccesses=no" in "/etc/systemd/logind.conf".Verify that RHEL 9 logs out sessions that are idle for 15 minutes with the following command: -+ -+$ sudo grep -i ^StopIdleSessionSec /etc/systemd/logind.conf -+ -+StopIdleSessionSec=900 -+ -+If "StopIdleSessionSec" is not configured to "900" seconds, this is a finding.SRG-OS-000445-GPOS-00199<GroupDescription></GroupDescription>RHEL-09-431010RHEL 9 must use a Linux Security Module configured to enforce limits on system services.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. -+ -+This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality. -+ -+Satisfies: SRG-OS-000445-GPOS-00199, SRG-OS-000134-GPOS-00068</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001084CCI-002696Configure RHEL 9 to verify correct operation of security functions. -+ -+Edit the file "/etc/selinux/config" and add or modify the following line: -+ -+ SELINUX=enforcing -+ -+A reboot is required for the changes to take effect.Ensure that RHEL 9 verifies correct operation of security functions through the use of SELinux with the following command: -+ -+$ getenforce -+ -+Enforcing -+ -+If SELINUX is not set to "Enforcing", this is a finding. -+ -+Verify that SELinux is configured to be enforcing at boot. -+ -+grep "SELINUX=" /etc/selinux/config -+# SELINUX= can take one of these three values: -+# NOTE: In earlier Fedora kernel builds, SELINUX=disabled would also -+SELINUX=enforcing -+ -+If SELINUX line is missing, commented out, or not set to "enforcing", this is a finding.SRG-OS-000445-GPOS-00199<GroupDescription></GroupDescription>RHEL-09-431015RHEL 9 must enable the SELinux targeted policy.<VulnDiscussion>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 nonproduction 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".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002696Configure RHEL 9 to use the targetd SELINUX policy. -+ -+Edit the file "/etc/selinux/config" and add or modify the following line: -+ -+ SELINUXTYPE=targeted -+ -+A reboot is required for the changes to take effect.Verify the SELINUX on RHEL 9 is using the targeted policy with the following command: -+ -+$ sestatus | grep policy -+ -+Loaded policy name: targeted -+ -+If the loaded policy name is not "targeted", this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>RHEL-09-431020RHEL 9 must configure SELinux context type to allow the use of a nondefault faillock tally directory.<VulnDiscussion>Not having the correct SELinux context on the faillock directory may lead to unauthorized access to the directory.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044Configure RHEL 9 to allow the use of a nondefault faillock tally directory while SELinux enforces a targeted policy. -+ -+Create a nondefault faillock tally directory (if it does not already exist) with the following example: -+ -+$ sudo mkdir /var/log/faillock -+ -+Update the /etc/selinux/targeted/contexts/files/file_contexts.local with "faillog_t" context type for the nondefault faillock tally directory with the following command: -+ -+$ sudo semanage fcontext -a -t faillog_t "/var/log/faillock(/.*)?" -+ -+Next, update the context type of the nondefault faillock directory/subdirectories and files with the following command: -+ -+$ sudo restorecon -R -v /var/log/faillockVerify the location of the nondefault tally directory for the pam_faillock module with the following command: -+ -+Note: If the system does not have SELinux enabled and enforcing a targeted policy, or if the pam_faillock module is not configured for use, this requirement is Not Applicable. -+ -+$ grep 'dir =' /etc/security/faillock.conf -+ -+dir = /var/log/faillock -+ -+Check the security context type of the nondefault tally directory with the following command: -+ -+$ ls -Zd /var/log/faillock -+ -+unconfined_u:object_r:faillog_t:s0 /var/log/faillock -+ -+If the security context type of the nondefault tally directory is not "faillog_t", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-431025RHEL 9 must have policycoreutils package installed.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. -+ -+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, setfile to label filesystems, newrole to switch roles, and run_init to run /etc/init.d scripts in the proper context. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000134-GPOS-00068</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001084The policycoreutils package can be installed with the following command: -+ -+$ sudo dnf install policycoreutilsVerify RHEL 9 has the policycoreutils package installed with the following command: -+ -+$ sudo dnf list --installed policycoreutils -+ -+Example output: -+ -+policycoreutils.x86_64 3.3-6.el9_0 -+ -+If the "policycoreutils" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-431030RHEL 9 policycoreutils-python-utils package must be installed.<VulnDiscussion>The policycoreutils-python-utils package is required to operate and manage an SELinux environment and its policies. It provides utilities such as semanage, audit2allow, audit2why, chcat, and sandbox.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Install the policycoreutils-python-utils service package (if the policycoreutils-python-utils service is not already installed) with the following command: -+ -+$ sudo dnf install policycoreutils-python-utilsVerify that RHEL 9 policycoreutils-python-utils service package is installed with the following command: -+ -+$ sudo dnf list --installed policycoreutils-python-utils -+ -+Example output: -+ -+policycoreutils-python-utils.noarch 3.3-6.el9_0 -+ -+If the "policycoreutils-python-utils" package is not installed, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>RHEL-09-432010RHEL 9 must have the sudo package installed.<VulnDiscussion>"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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002235The sudo package can be installed with the following command: -+ -+$ sudo dnf install sudoVerify that RHEL 9 sudo package is installed with the following command: -+ -+$ sudo dnf list --installed sudo -+ -+Example output: -+ -+sudo.x86_64 1.9.5p2-7.el9 -+ -+If the "sudo" package is not installed, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>RHEL-09-432015RHEL 9 must require reauthentication when using the "sudo" command.<VulnDiscussion>Without reauthentication, 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 organization requires the user to reauthenticate when using the "sudo" command. -+ -+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 reauthenticate for privileged actions until the user's session is terminated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002038Configure RHEL 9 to reauthenticate "sudo" commands after the specified timeout: -+ -+Add the following line to "/etc/sudoers": -+ -+Defaults timestamp_timeout=0Verify RHEL 9 requires reauthentication when using the "sudo" command to elevate privileges with the following command: -+ -+$ sudo grep -i 'timestamp_timeout' /etc/sudoers /etc/sudoers.d/* -+ -+/etc/sudoers:Defaults timestamp_timeout=0 -+ -+If results are returned from more than one file location, this is a finding. -+ -+If "timestamp_timeout" is set to a negative number, is commented out, or no results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-432020RHEL 9 must use the invoking user's password for privilege escalation when using "sudo".<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Define the following in the Defaults section of the /etc/sudoers file or a single configuration file in the /etc/sudoers.d/ directory: -+ -+Defaults !targetpw -+Defaults !rootpw -+Defaults !runaspwVerify that the sudoers security policy is configured to use the invoking user's password for privilege escalation with the following command: -+ -+$ sudo egrep -i '(!rootpw|!targetpw|!runaspw)' /etc/sudoers /etc/sudoers.d/* | grep -v '#' -+ -+/etc/sudoers:Defaults !targetpw -+/etc/sudoers:Defaults !rootpw -+/etc/sudoers:Defaults !runaspw -+ -+If no results are returned, this is a finding. -+ -+If results are returned from more than one file location, this is a finding. -+ -+If "Defaults !targetpw" is not defined, this is a finding. -+ -+If "Defaults !rootpw" is not defined, this is a finding. -+ -+If "Defaults !runaspw" is not defined, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>RHEL-09-432025RHEL 9 must require users to reauthenticate for privilege escalation.<VulnDiscussion>Without reauthentication, 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 reauthenticate. -+ -+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002038Configure RHEL 9 to not allow users to execute privileged actions without authenticating. -+ -+Remove any occurrence of "!authenticate" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory. -+ -+$ sudo sed -i '/\!authenticate/ s/^/# /g' /etc/sudoers /etc/sudoers.d/*Verify that "/etc/sudoers" has no occurrences of "!authenticate" with the following command: -+ -+$ sudo grep -i '!authenticate' /etc/sudoers /etc/sudoers.d/* -+ -+If any occurrences of "!authenticate" are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-432030RHEL 9 must restrict privilege elevation to authorized personnel.<VulnDiscussion>If the "sudoers" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove the following entries from the /etc/sudoers file or configuration file under /etc/sudoers.d/: -+ -+ALL ALL=(ALL) ALL -+ALL ALL=(ALL:ALL) ALLVerify RHEL 9 restricts privilege elevation to authorized personnel with the following command: -+ -+$ sudo sh -c 'grep -iw ALL /etc/sudoers /etc/sudoers.d/*' -+ -+If the either of the following entries are returned, this is a finding: -+ALL ALL=(ALL) ALL -+ALL ALL=(ALL:ALL) ALLSRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>RHEL-09-432035RHEL 9 must restrict the use of the "su" command.<VulnDiscussion>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 commands is considered a good security practice. -+ -+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000312-GPOS-00123</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002038CCI-002165Configure RHEL 9 to require users to be in the "wheel" group to run "su" command. -+ -+In file "/etc/pam.d/su", uncomment the following line: -+ -+"#auth required pam_wheel.so use_uid" -+ -+$ sed '/^[[:space:]]*#[[:space:]]*auth[[:space:]]\+required[[:space:]]\+pam_wheel\.so[[:space:]]\+use_uid$/s/^[[:space:]]*#//' -i /etc/pam.d/su -+ -+If necessary, create a "wheel" group and add administrative users to the group.Verify that RHEL 9 requires uses to be members of the "wheel" group with the following command: -+ -+$ grep pam_wheel /etc/pam.d/su -+ -+auth required pam_wheel.so use_uid -+ -+If a line for "pam_wheel.so" does not exist, or is commented out, this is a finding.SRG-OS-000370-GPOS-00155<GroupDescription></GroupDescription>RHEL-09-433010RHEL 9 fapolicy module must be installed.<VulnDiscussion>The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as allowlisting. -+ -+Utilizing an allowlist 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 allowlisted software occurs prior to execution or at system startup. -+ -+User home directories/folders may contain information of a sensitive nature. Nonprivileged users should coordinate any sharing of information with an SA through shared resources. -+ -+RHEL 9 ships with many optional packages. One such package is a file access policy daemon called "fapolicyd". "fapolicyd" is a userspace daemon that determines access rights to files based on attributes of the process and file. It can be used to either blocklist or allowlist processes or file access. -+ -+Proceed with caution with enforcing the use of this daemon. Improper configuration may render the system nonfunctional. The "fapolicyd" API is not namespace aware and can cause issues when launching or running containers. -+ -+Satisfies: SRG-OS-000370-GPOS-00155, SRG-OS-000368-GPOS-00154</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764CCI-001774The fapolicyd package can be installed with the following command: -+ -+$ sudo dnf install fapolicydVerify that RHEL 9 fapolicyd package is installed with the following command: -+ -+$ sudo dnf list --installed fapolicyd -+ -+Example output: -+ -+fapolicyd.x86_64 1.1-103.el9_0 -+ -+If the "fapolicyd" package is not installed, this is a finding.SRG-OS-000370-GPOS-00155<GroupDescription></GroupDescription>RHEL-09-433015RHEL 9 fapolicy module must be enabled.<VulnDiscussion>The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as allowlisting. -+ -+Utilizing an allowlist 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 allowlisted software occurs prior to execution or at system startup. -+ -+User home directories/folders may contain information of a sensitive nature. Nonprivileged users should coordinate any sharing of information with an SA through shared resources. -+ -+RHEL 9 ships with many optional packages. One such package is a file access policy daemon called "fapolicyd". "fapolicyd" is a userspace daemon that determines access rights to files based on attributes of the process and file. It can be used to either blocklist or allowlist processes or file access. -+ -+Proceed with caution with enforcing the use of this daemon. Improper configuration may render the system nonfunctional. The "fapolicyd" API is not namespace aware and can cause issues when launching or running containers. -+ -+Satisfies: SRG-OS-000370-GPOS-00155, SRG-OS-000368-GPOS-00154</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001764CCI-001774Enable the fapolicyd with the following command: -+ -+$ systemctl enable --now fapolicydVerify that RHEL 9 fapolicyd is active with the following command: -+ -+$ systemctl is-active fapolicyd -+ -+active -+ -+If fapolicyd module is not active, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>RHEL-09-611010RHEL 9 must ensure the password complexity module in the system-auth file is configured for three retries or less.<VulnDiscussion>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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system. -+ -+RHEL 9 uses "pwquality" as a mechanism to enforce password complexity. This is set in both: -+/etc/pam.d/password-auth -+/etc/pam.d/system-auth -+ -+By limiting the number of attempts to meet the pwquality module complexity requirements before returning with an error, the system will audit abnormal attempts at password changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000192Configure RHEL 9 to limit the "pwquality" retry option to "3". -+ -+Add the following line to the "/etc/pam.d/system-auth" file (or modify the line to have the required value): -+ -+password required pam_pwquality.so retry=3Verify RHEL 9 is configured to limit the "pwquality" retry option to "3". -+ -+Check for the use of the "pwquality" retry option in the system-auth file with the following command: -+ -+$ cat /etc/pam.d/system-auth | grep pam_pwquality -+ -+password required pam_pwquality.so retry=3 -+ -+If the value of "retry" is set to "0" or greater than "3", or is missing, this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>RHEL-09-611015RHEL 9 must be configured in the password-auth file to prohibit password reuse for a minimum of five generations.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements. -+ -+RHEL 9 uses "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both: -+/etc/pam.d/password-auth -+/etc/pam.d/system-auth -+ -+Note that manual changes to the listed files may be overwritten by the "authselect" program.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000200Configure the RHEL 9 password-auth file to prohibit password reuse for a minimum of five generations. -+ -+Add the following line in "/etc/pam.d/password-auth" (or modify the line to have the required value): -+ -+password required pam_pwhistory.so use_authtok remember=5 retry=3Verify RHEL 9 is configured in the password-auth file to prohibit password reuse for a minimum of five generations with the following command: -+ -+$ grep -i remember /etc/pam.d/password-auth -+ -+password required pam_pwhistory.so use_authtok remember=5 retry=3 -+ -+If the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "5", this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>RHEL-09-611020RHEL 9 must be configured in the system-auth file to prohibit password reuse for a minimum of five generations.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements. -+ -+RHEL 9 uses "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both: -+/etc/pam.d/password-auth -+/etc/pam.d/system-auth -+ -+Note that manual changes to the listed files may be overwritten by the "authselect" program.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000200Configure the RHEL 9 system-auth file to prohibit password reuse for a minimum of five generations. -+ -+Add the following line in "/etc/pam.d/system-auth" (or modify the line to have the required value): -+ -+password required pam_pwhistory.so use_authtok remember=5 retry=3Verify RHEL 9 is configured in the system-auth file to prohibit password reuse for a minimum of five generations with the following command: -+ -+$ grep -i remember /etc/pam.d/system-auth -+ -+password required pam_pwhistory.so use_authtok remember=5 retry=3 -+ -+If the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "5", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-611025RHEL 9 must not allow blank or null passwords.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Remove any instances of the "nullok" option in the "/etc/pam.d/password-auth" and "/etc/pam.d/system-auth" files to prevent logons with empty passwords. -+ -+Note: Manual changes to the listed file may be overwritten by the "authselect" program.Verify that null passwords cannot be used with the following command: -+ -+$ sudo grep -i nullok /etc/pam.d/system-auth /etc/pam.d/password-auth -+ -+If output is produced, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>RHEL-09-611030RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file.<VulnDiscussion>If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044Configure RHEL 9 to include the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. -+ -+Add/modify the appropriate sections of the "/etc/pam.d/system-auth" file to match the following lines: -+Note: The "preauth" line must be listed before pam_unix.so. -+ -+auth required pam_faillock.so preauth -+auth required pam_faillock.so authfail -+account required pam_faillock.soVerify the pam_faillock.so module is present in the "/etc/pam.d/system-auth" file: -+ -+$ grep pam_faillock.so /etc/pam.d/system-auth -+ -+auth required pam_faillock.so preauth -+auth required pam_faillock.so authfail -+account required pam_faillock.so -+ -+If the pam_faillock.so module is not present in the "/etc/pam.d/system-auth" file with the "preauth" line listed before pam_unix.so, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>RHEL-09-611035RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file.<VulnDiscussion>If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000044Configure RHEL 9 to include the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. -+ -+Add/modify the appropriate sections of the "/etc/pam.d/password-auth" file to match the following lines: -+Note: The "preauth" line must be listed before pam_unix.so. -+ -+auth required pam_faillock.so preauth -+auth required pam_faillock.so authfail -+account required pam_faillock.soVerify the pam_faillock.so module is present in the "/etc/pam.d/password-auth" file: -+ -+$ grep pam_faillock.so /etc/pam.d/password-auth -+ -+auth required pam_faillock.so preauth -+auth required pam_faillock.so authfail -+account required pam_faillock.so -+ -+If the pam_faillock.so module is not present in the "/etc/pam.d/password-auth" file with the "preauth" line listed before pam_unix.so, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>RHEL-09-611040RHEL 9 must ensure the password complexity module is enabled in the password-auth file.<VulnDiscussion>Enabling PAM password complexity permits enforcement of strong passwords and consequently makes the system less prone to dictionary attacks. -+ -+Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000192CCI-000193CCI-000366Configure RHEL 9 to use "pwquality" to enforce password complexity rules. -+ -+Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value): -+ -+password required pam_pwquality.soVerify RHEL 9 uses "pwquality" to enforce the password complexity rules in the password-auth file with the following command: -+ -+$ cat /etc/pam.d/password-auth | grep pam_pwquality -+ -+password required pam_pwquality.so -+ -+If the command does not return a line containing the value "pam_pwquality.so", or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-611045RHEL 9 must ensure the password complexity module is enabled in the system-auth file.<VulnDiscussion>Enabling PAM password complexity permits enforcement of strong passwords and consequently makes the system less prone to dictionary attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to use "pwquality" to enforce password complexity rules. -+ -+Add the following line to the "/etc/pam.d/system-auth" file(or modify the line to have the required value): -+ -+password required pam_pwquality.soVerify RHEL 9 uses "pwquality" to enforce the password complexity rules in the system-auth file with the following command: -+ -+$ cat /etc/pam.d/system-auth | grep pam_pwquality -+ -+password required pam_pwquality.so -+ -+If the command does not return a line containing the value "pam_pwquality.so", or the line is commented out, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-611050RHEL 9 password-auth must be configured to use a sufficient number of hashing rounds.<VulnDiscussion>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 more hashing rounds makes password cracking attacks more difficult. -+ -+Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196CCI-000803Configure Red Hat Enterprise Linux 9 to use 5000 hashing rounds for hashing passwords. -+ -+Add or modify the following line in "/etc/pam.d/password-auth" and set "rounds" to "5000". -+ -+password sufficient pam_unix.so sha512 rounds=5000Verify the number of rounds for the password hashing algorithm is configured with the following command: -+ -+$ sudo grep rounds /etc/pam.d/password-auth -+ -+password sufficient pam_unix.so sha512 rounds=5000 -+ -+If a matching line is not returned or "rounds" is less than "5000", this a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-611055RHEL 9 system-auth must be configured to use a sufficient number of hashing rounds.<VulnDiscussion>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 more hashing rounds makes password cracking attacks more difficult. -+ -+Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196CCI-000803Configure Red Hat Enterprise Linux 9 to use 5000 hashing rounds for hashing passwords. -+ -+Add or modify the following line in "/etc/pam.d/system-auth" and set "rounds" to 5000. -+ -+password sufficient pam_unix.so sha512 rounds=5000'Verify the number of rounds for the password hashing algorithm is configured with the following command: -+ -+$ sudo grep rounds /etc/pam.d/system-auth -+ -+password sufficient pam_unix.so sha512 rounds=5000 -+ -+If a matching line is not returned or "rounds" is less than 5000, this a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>RHEL-09-611060RHEL 9 must enforce password complexity rules for the root account.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000072-GPOS-00040, SRG-OS-000071-GPOS-00039, SRG-OS-000070-GPOS-00038, SRG-OS-000266-GPOS-00101, SRG-OS-000078-GPOS-00046, SRG-OS-000480-GPOS-00225, SRG-OS-000069-GPOS-00037</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000192CCI-000193CCI-000194CCI-000195CCI-000205CCI-000366CCI-001619Configure RHEL 9 to enforce password complexity on the root account. -+ -+Add or update the following line in /etc/security/pwquality.conf: -+ -+enforce_for_rootVerify that RHEL 9 enforces password complexity rules for the root account. -+ -+Check if root user is required to use complex passwords with the following command: -+ -+$ grep enforce_for_root /etc/security/pwquality.conf /etc/security/pwquality.conf/*.conf -+ -+/etc/security/pwquality.conf:enforce_for_root -+ -+If "enforce_for_root" is commented or missing, this is a finding.SRG-OS-000070-GPOS-00038<GroupDescription></GroupDescription>RHEL-09-611065RHEL 9 must enforce password complexity by requiring that at least one lowercase character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000193Configure RHEL 9 to enforce password complexity by requiring at least one lowercase character be used by setting the "lcredit" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+lcredit = -1Verify that RHEL 9 enforces password complexity by requiring at least one lowercase character. -+ -+Check the value for "lcredit" with the following command: -+ -+$ sudo grep lcredit /etc/security/pwquality.conf /etc/security/pwquality.conf/*.conf -+ -+/etc/security/pwquality.conf:lcredit = -1 -+ -+If the value of "lcredit" is a positive number or is commented out, this is a finding.SRG-OS-000071-GPOS-00039<GroupDescription></GroupDescription>RHEL-09-611070RHEL 9 must enforce password complexity by requiring that at least one numeric character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000194Configure RHEL 9 to enforce password complexity by requiring at least one numeric character be used by setting the "dcredit" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+dcredit = -1Verify that RHEL 9 enforces password complexity by requiring at least one numeric character. -+ -+Check the value for "dcredit" with the following command: -+ -+$ sudo grep dcredit /etc/security/pwquality.conf /etc/security/pwquality.conf/*.conf -+ -+/etc/security/pwquality.conf:dcredit = -1 -+ -+If the value of "dcredit" is a positive number or is commented out, this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>RHEL-09-611075RHEL 9 passwords for new users or password changes must have a 24 hours minimum password lifetime restriction in /etc/login.defs.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000198Configure RHEL 9 to enforce 24 hours as the minimum password lifetime. -+ -+Add the following line in "/etc/login.defs" (or modify the line to have the required value): -+ -+PASS_MIN_DAYS 1Verify RHEL 9 enforces 24 hours as the minimum password lifetime for new user accounts. -+ -+Check for the value of "PASS_MIN_DAYS" in "/etc/login.defs" with the following command: -+ -+$ grep -i pass_min_days /etc/login.defs -+ -+PASS_MIN_DAYS 1 -+ -+If the "PASS_MIN_DAYS" parameter value is not "1" or greater, or is commented out, this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>RHEL-09-611080RHEL 9 passwords must have a 24 hours minimum password lifetime restriction in /etc/shadow.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000198Configure noncompliant accounts to enforce a 24 hour minimum password lifetime: -+ -+$ sudo passwd -n 1 [user]Verify that RHEL 9 has configured the minimum time period between password changes for each user account as one day or greater with the following command: -+ -+$ sudo awk -F: '$4 < 1 {print $1 " " $4}' /etc/shadow -+ -+If any results are returned that are not associated with a system account, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>RHEL-09-611085RHEL 9 must require users to provide a password for privilege escalation.<VulnDiscussion>Without reauthentication, 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 reauthenticate. -+ -+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002038Configure RHEL 9 to not allow users to execute privileged actions without authenticating with a password. -+ -+Remove any occurrence of "NOPASSWD" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory. -+ -+$ sudo sed -i '/NOPASSWD/ s/^/# /g' /etc/sudoers /etc/sudoers.d/*Verify that "/etc/sudoers" has no occurrences of "NOPASSWD" with the following command: -+ -+$ sudo grep -ri nopasswd /etc/sudoers /etc/sudoers.d/* -+ -+If any occurrences of "NOPASSWD" are returned, this is a finding.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>RHEL-09-611090RHEL 9 passwords must be created with a minimum of 15 characters.<VulnDiscussion>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 increase exponentially the time and/or resources required to compromise the password. -+ -+RHEL 9 uses "pwquality" as a mechanism to enforce password complexity. Configurations are set in the "etc/security/pwquality.conf" file. -+ -+The "minlen", sometimes noted as minimum length, acts as a "score" of complexity based on the credit components of the "pwquality" module. By setting the credit components to a negative value, not only will those components be required, but they will not count toward the total "score" of "minlen". This will enable "minlen" to require a 15-character minimum. -+ -+The DOD minimum password requirement is 15 characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000205Configure RHEL 9 to enforce a minimum 15-character password length. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+minlen = 15Verify that RHEL 9 enforces a minimum 15-character password length with the following command: -+ -+$ grep minlen /etc/security/pwquality.conf -+ -+minlen = 15 -+ -+If the command does not return a "minlen" value of "15" or greater, does not return a line, or the line is commented out, this is a finding.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>RHEL-09-611095RHEL 9 passwords for new users must have a minimum of 15 characters.<VulnDiscussion>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 increase exponentially the time and/or resources required to compromise the password. -+ -+The DOD minimum password requirement is 15 characters.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000205Configure RHEL 9 to enforce a minimum 15-character password length for new user accounts. -+ -+Add or modify the following line in the "/etc/login.defs" file: -+ -+PASS_MIN_LEN 15Verify that RHEL 9 enforces a minimum 15-character password length for new user accounts by running the following command: -+ -+$ sudo grep -i pass_min_len /etc/login.defs -+ -+PASS_MIN_LEN 15 -+ -+If the command does not return a "PASS_MIN_LEN" value of "15" or greater, does not return a line, or the line is commented out, this is a finding.SRG-OS-000266-GPOS-00101<GroupDescription></GroupDescription>RHEL-09-611100RHEL 9 must enforce password complexity by requiring that at least one special character be used.<VulnDiscussion>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. RHEL 9 utilizes "pwquality" as a mechanism to enforce password complexity. Note that to require special characters without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001619Configure RHEL 9 to enforce password complexity by requiring at least one special character be used by setting the "ocredit" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+ocredit = -1Verify that RHEL 9 enforces password complexity by requiring at least one special character with the following command: -+ -+$ sudo grep ocredit /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf -+ -+ocredit = -1 -+ -+If the value of "ocredit" is a positive number or is commented out, this is a finding.SRG-OS-000480-GPOS-00225<GroupDescription></GroupDescription>RHEL-09-611105RHEL 9 must prevent the use of dictionary words for passwords.<VulnDiscussion>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. If RHEL 9 allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to prevent the use of dictionary words for passwords. -+ -+Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "dictcheck" parameter: -+ -+dictcheck=1Verify RHEL 9 prevents the use of dictionary words for passwords with the following command: -+ -+$ sudo grep dictcheck /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf -+ -+/etc/security/pwquality.conf:dictcheck=1 -+ -+If "dictcheck" does not have a value other than "0", or is commented out, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>RHEL-09-611110RHEL 9 must enforce password complexity by requiring that at least one uppercase character be used.<VulnDiscussion>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 uppercase characters makes password guessing attacks more difficult by ensuring a larger search space.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000192Configure RHEL 9 to enforce password complexity by requiring that at least one uppercase character be used by setting the "ucredit" option. -+ -+Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value): -+ -+ucredit = -1Verify that RHEL 9 enforces password complexity by requiring that at least one uppercase character. -+ -+Check the value for "ucredit" with the following command: -+ -+$ sudo grep ucredit /etc/security/pwquality.conf /etc/security/pwquality.conf/*.conf -+ -+ucredit = -1 -+ -+If the value of "ucredit" is a positive number or is commented out, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>RHEL-09-611115RHEL 9 must require the change of at least eight characters when passwords are changed.<VulnDiscussion>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 will not resemble previously compromised ones. Note that passwords changed on compromised systems will still be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000195Configure RHEL 9 to require the change of at least eight of the total number of characters when passwords are changed by setting the "difok" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+difok = 8Verify the value of the "difok" option in "/etc/security/pwquality.conf" with the following command: -+ -+$ sudo grep difok /etc/security/pwquality.conf -+ -+difok = 8 -+ -+If the value of "difok" is set to less than "8", or is commented out, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>RHEL-09-611120RHEL 9 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000195Configure RHEL 9 to require the change of the number of repeating characters of the same character class when passwords are changed by setting the "maxclassrepeat" option. -+ -+Add the following line to "/etc/security/pwquality.conf" conf (or modify the line to have the required value): -+ -+maxclassrepeat = 4Verify the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command: -+ -+$ grep maxclassrepeat /etc/security/pwquality.conf -+ -+maxclassrepeat = 4 -+ -+If the value of "maxclassrepeat" is set to "0", more than "4", or is commented out, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>RHEL-09-611125RHEL 9 must require the maximum number of repeating characters be limited to three when passwords are changed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000195Configure RHEL 9 to require the change of the number of repeating consecutive characters when passwords are changed by setting the "maxrepeat" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+maxrepeat = 3Verify the value of the "maxrepeat" option in "/etc/security/pwquality.conf" with the following command: -+ -+$ grep maxrepeat /etc/security/pwquality.conf -+ -+maxrepeat = 3 -+ -+If the value of "maxrepeat" is set to more than "3", or is commented out, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>RHEL-09-611130RHEL 9 must require the change of at least four character classes when passwords are changed.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000195Configure RHEL 9 to require the change of at least four character classes when passwords are changed by setting the "minclass" option. -+ -+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value): -+ -+minclass = 4Verify the value of the "minclass" option in "/etc/security/pwquality.conf" with the following command: -+ -+$ grep minclass /etc/security/pwquality.conf -+ -+minclass = 4 -+ -+If the value of "minclass" is set to less than "4", or is commented out, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-611135RHEL 9 must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords.<VulnDiscussion>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 ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196Configure RHEL 9 to use the SHA-512 algorithm for password hashing. -+ -+Add or change the following line in the "[default]" section of "/etc/libuser.conf" file: -+ -+crypt_style = sha512Verify the user and group account administration utilities are configured to store only encrypted representations of passwords with the following command: -+ -+# grep crypt /etc/libuser.conf -+ -+crypt_style = sha512 -+ -+If the "crypt_style" variable is not set to "sha512", is not in the defaults section, is commented out, or does not exist, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-611140RHEL 9 must be configured to use the shadow file to store only encrypted representations of passwords.<VulnDiscussion>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 ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196Configure RHEL 9 to store only SHA512 encrypted representations of passwords. -+ -+Add or update the following line in the "/etc/login.defs" file: -+ -+ENCRYPT_METHOD SHA512Verify the system's shadow file is configured to store only encrypted representations of passwords with a hash value of SHA512 with the following command: -+ -+# grep -i encrypt_method /etc/login.defs -+ -+ENCRYPT_METHOD SHA512 -+ -+If "ENCRYPT_METHOD" does not have a value of "SHA512", or the line is commented out, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>RHEL-09-611145RHEL 9 must not be configured to bypass password requirements for privilege escalation.<VulnDiscussion>Without reauthentication, 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 reauthenticate. -+ -+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002038Configure the operating system to require users to supply a password for privilege escalation. -+ -+Remove any occurrences of " pam_succeed_if " in the "/etc/pam.d/sudo" file.Verify the operating system is not configured to bypass password requirements for privilege escalation with the following command: -+ -+$ sudo grep pam_succeed_if /etc/pam.d/sudo -+ -+If any occurrences of "pam_succeed_if" are returned, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-611150RHEL 9 shadow password suite must be configured to use a sufficient number of hashing rounds.<VulnDiscussion>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 more hashing rounds makes password cracking attacks more difficult. -+ -+Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196CCI-000803Configure RHEL 9 to encrypt all stored passwords with a strong cryptographic hash. -+ -+Edit/modify the following line in the "/etc/login.defs" file and set "SHA_CRYPT_MIN_ROUNDS" to a value no lower than "5000": -+ -+SHA_CRYPT_MIN_ROUNDS 5000Verify that RHEL 9 has a minimum number of hash rounds configured with the following command: -+ -+$ grep -i sha_crypt /etc/login.defs -+ -+If "SHA_CRYPT_MIN_ROUNDS" or "SHA_CRYPT_MAX_ROUNDS" is less than "5000", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-611155RHEL 9 must not have accounts configured with blank or null passwords.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure all accounts on RHEL 9 to have a password or lock the account with the following commands: -+ -+Perform a password reset: -+ -+$ sudo passwd [username] -+ -+To lock an account: -+ -+$ sudo passwd -l [username]Verify that null or blank passwords cannot be used with the following command: -+ -+$ sudo awk -F: '!$2 {print $1}' /etc/shadow -+ -+If the command returns any results, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>RHEL-09-611160RHEL 9 must use the CAC smart card driver.<VulnDiscussion>Smart card login provides two-factor authentication stronger than that provided by a username and password combination. Smart cards leverage public key infrastructure to provide and verify credentials. Configuring the smart card driver in use by the organization helps to prevent users from using unauthorized smart cards. -+ -+Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000109-GPOS-00056, SRG-OS-000108-GPOS-00055, SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000764CCI-000766CCI-000767CCI-000768CCI-000770CCI-001941CCI-001942Configure RHEL 9 to load the CAC driver. -+ -+Add or modify the following line in the "/etc/opensc.conf" file: -+ -+card_drivers = cac;Verify that RHEL loads the CAC driver with the following command: -+ -+$ grep card_drivers /etc/opensc.conf -+ -+card_drivers = cac; -+ -+If "cac" is not listed as a card driver, or there is no line returned for "card_drivers", this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>RHEL-09-611165RHEL 9 must enable certificate based smart card authentication.<VulnDiscussion>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. The DOD Common Access Card (CAC) with DOD-approved PKI is an example of multifactor authentication. -+ -+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000105-GPOS-00052</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000765CCI-001948Edit the file "/etc/sssd/sssd.conf" and add or edit the following line: -+ -+pam_cert_auth = TrueVerify that RHEL 9 has smart cards are enabled in System Security Services Daemon (SSSD), run the following command: -+ -+$ sudo grep pam_cert_auth /etc/sssd/sssd.conf -+ -+pam_cert_auth = True -+ -+If "pam_cert_auth" is not set to "True", the line is commented out, or the line is missing, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>RHEL-09-611170RHEL 9 must implement certificate status checking for multifactor authentication.<VulnDiscussion>Using an authentication device, such as a DOD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, credentials stored on the authentication device will not be affected. -+ -+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 such as the U.S. Government Personal Identity Verification (PIV) card and the DOD CAC. -+ -+RHEL 9 includes multiple options for configuring certificate status checking, but for this requirement focuses on the System Security Services Daemon (SSSD). By default, SSSD performs Online Certificate Status Protocol (OCSP) checking and certificate verification using a sha256 digest function. -+ -+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001948CCI-001954Configure RHEL 9 to implement certificate status checking for multifactor authentication. -+ -+Review the "/etc/sssd/conf.d/certificate_verification.conf" file to determine if the system is configured to prevent OCSP or certificate verification. -+ -+Add the following line to the "/etc/sssd/conf.d/certificate_verification.conf" file: -+ -+certificate_verification = ocsp_dgst=sha512 -+ -+Set the correct ownership and permissions on the "/etc/sssd/conf.d/certificate_verification.conf" file by running these commands: -+ -+$ sudo chown root:root "/etc/sssd/conf.d/certificate_verification.conf" -+$ sudo chmod 600 "/etc/sssd/conf.d/certificate_verification.conf" -+ -+The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: -+ -+$ sudo systemctl restart sssd.serviceVerify the operating system implements Online Certificate Status Protocol (OCSP) and is using the proper digest value on the system with the following command: -+ -+$ sudo grep certificate_verification /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf | grep -v "^#" -+ -+certificate_verification = ocsp_dgst=sha512 -+ -+If the certificate_verification line is missing from the [sssd] section, or is missing "ocsp_dgst=sha512", ask the administrator to indicate what type of multifactor authentication is being utilized and how the system implements certificate status checking. If there is no evidence of certificate status checking being used, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>RHEL-09-611175RHEL 9 must have the pcsc-lite package installed.<VulnDiscussion>The pcsc-lite package must be installed if it is to be available for multifactor authentication using smart cards.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001948The pcsc-lite package can be installed with the following command: -+ -+$ sudo dnf install pcsc-liteVerify that RHEL 9 has the pcsc-lite package installed with the following command: -+ -+$ sudo dnf list --installed pcsc-lite -+ -+Example output: -+ -+pcsc-lite.x86_64 1.9.4-1.el9 -+ -+If the "pcsc-lite" package is not installed, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>RHEL-09-611180The pcscd service on RHEL 9 must be active.<VulnDiscussion>The information system ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. -+ -+The daemon program for pcsc-lite and the MuscleCard framework is pcscd. It is a resource manager that coordinates communications with smart card readers and smart cards and cryptographic tokens that are connected to the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001948To enable the pcscd service run the following command: -+ -+$ sudo systemctl enable --now pcscdVerify that the "pcscd" service is active with the following command: -+ -+$ systemctl is-active pcscd -+ -+active -+ -+If the pcscdservice is not active, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>RHEL-09-611185RHEL 9 must have the opensc package installed.<VulnDiscussion>The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. -+ -+The DOD has mandated the use of the Common Access Card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems. -+ -+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000376-GPOS-00161</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001948CCI-001953The opensc package can be installed with the following command: -+ -+$ sudo dnf install openscVerify that RHEL 9 has the opensc package installed with the following command: -+ -+$ sudo dnf list --installed opensc -+ -+Example output: -+ -+opensc.x86_64 0.22.0-2.el9 -+ -+If the "opensc" package is not installed, this is a finding.SRG-OS-000067-GPOS-00035<GroupDescription></GroupDescription>RHEL-09-611190RHEL 9, for PKI-based authentication, must enforce authorized access to the corresponding private key.<VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. -+ -+The cornerstone of the PKI is the private key used to encrypt or digitally sign information. -+ -+If the private key is stolen, this will lead to the compromise of the authentication and nonrepudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. -+ -+Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000186Create a new private and public key pair that utilizes a passcode with the following command: -+ -+$ sudo ssh-keygen -n [passphrase]Verify the SSH private key files have a passcode. -+ -+For each private key stored on the system, use the following command: -+ -+$ sudo ssh-keygen -y -f /path/to/file -+ -+If the contents of the key are displayed, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>RHEL-09-611195RHEL 9 must require authentication to access emergency mode.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. -+ -+This requirement 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000213Configure RHEL 9 to require authentication for emergency mode. -+ -+Add or modify the following line in the "/usr/lib/systemd/system/emergency.service" file: -+ -+ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergencyVerify that RHEL 9 requires authentication for emergency mode with the following command: -+ -+$ grep sulogin /usr/lib/systemd/system/emergency.service -+ -+ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency -+ -+If this line is not returned, or is commented out, this is a finding. If the output is different, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>RHEL-09-611200RHEL 9 must require authentication to access single-user mode.<VulnDiscussion>To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. -+ -+This requirement 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000213Configure RHEL 9 to require authentication for single-user mode. -+ -+Add or modify the following line in the "/usr/lib/systemd/system/rescue.service" file: -+ -+ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescueVerify that RHEL 9 requires authentication for single-user mode with the following command: -+ -+$ grep sulogin /usr/lib/systemd/system/rescue.service -+ -+ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue -+ -+If this line is not returned, or is commented out, this is a finding.SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>RHEL-09-611205RHEL 9 must prevent system daemons from using Kerberos for authentication.<VulnDiscussion>Unapproved mechanisms used for authentication to the cryptographic module are not verified; therefore, cannot be relied upon to provide confidentiality or integrity and DOD data may be compromised. -+ -+RHEL 9 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. -+ -+The key derivation function (KDF) in Kerberos is not FIPS compatible. Ensuring the system does not have any keytab files present prevents system daemons from using Kerberos for authentication. A keytab is a file containing pairs of Kerberos principals and encrypted keys. -+ -+FIPS 140-3 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DOD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general-purpose computing system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000803Configure RHEL 9 to prevent system daemons from using Kerberos for authentication. -+ -+Remove any files with the .keytab extension from the operating system. -+ -+rm -f /etc/*.keytabVerify that RHEL 9 prevents system daemons from using Kerberos for authentication with the following command: -+ -+$ sudo ls -al /etc/*.keytab -+ -+ls: cannot access '/etc/*.keytab': No such file or directory -+ -+If this command produces any "keytab" file(s), this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>RHEL-09-631010RHEL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000384-GPOS-00167</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000185CCI-001991Configure RHEL 9, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. -+ -+Obtain a valid copy of the DoD root CA file from the PKI CA certificate bundle from cyber.mil and copy the DoD_PKE_CA_chain.pem into the following file: -+/etc/sssd/pki/sssd_auth_ca_db.pemVerify RHEL 9 for PKI-based authentication has valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor. -+ -+Check that the system has a valid DoD root CA installed with the following command: -+ -+$ sudo openssl x509 -text -in /etc/sssd/pki/sssd_auth_ca_db.pem -+ -+Example output: -+ -+Certificate: -+ Data: -+ Version: 3 (0x2) -+ Serial Number: 1 (0x1) -+ Signature Algorithm: sha256WithRSAEncryption -+ Issuer: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 -+ Validity -+ Not Before: Mar 20 18:46:41 2012 GMT -+ Not After: Dec 30 18:46:41 2029 GMT -+ Subject: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 -+ Subject Public Key Info: -+ Public Key Algorithm: rsaEncryption -+ -+If the root CA file is not a DoD-issued certificate with a valid date and installed in the "/etc/sssd/pki/sssd_auth_ca_db.pem" location, this is a finding.SRG-OS-000068-GPOS-00036<GroupDescription></GroupDescription>RHEL-09-631015RHEL 9 must map the authenticated identity to the user or group account for PKI-based authentication.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000187Configure RHEL 9 to map the authenticated identity to the user or group account by adding or modifying the certmap section of the "/etc/sssd/sssd.conf" file based on the following example: -+ -+[certmap/testing.test/rule_name] -+matchrule = .*EDIPI@mil -+maprule = (userCertificate;binary={cert!bin}) -+dmains = testing.test -+ -+The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: -+ -+$ sudo systemctl restart sssd.serviceVerify the certificate of the user or group is mapped to the corresponding user or group in the "sssd.conf" file with the following command: -+ -+$ sudo cat /etc/sssd/sssd.conf -+ -+[certmap/testing.test/rule_name] -+matchrule =<SAN>.*EDIPI@mil -+maprule = (userCertificate;binary={cert!bin}) -+domains = testing.test -+ -+If the certmap section does not exist, ask the system administrator (SA) to indicate how certificates are mapped to accounts. If there is no evidence of certificate mapping, this is a finding.SRG-OS-000383-GPOS-00166<GroupDescription></GroupDescription>RHEL-09-631020RHEL 9 must prohibit the use of cached authenticators after one day.<VulnDiscussion>If cached authentication information is out-of-date, the validity of the authentication information may be questionable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002007Configure the SSSD to prohibit the use of cached authentications after one day. -+ -+Add or change the following line in "/etc/sssd/sssd.conf" just below the line [pam]: -+ -+offline_credentials_expiration = 1Verify that the System Security Services Daemon (SSSD) prohibits the use of cached authentications after one day. -+ -+Note: If smart card authentication is not being used on the system, this requirement is Not Applicable. -+ -+Check that SSSD allows cached authentications with the following command: -+ -+$ sudo grep cache_credentials /etc/sssd/sssd.conf -+ -+cache_credentials = true -+ -+If "cache_credentials" is set to "false" or missing from the configuration file, this is not a finding and no further checks are required. -+ -+If "cache_credentials" is set to "true", check that SSSD prohibits the use of cached authentications after one day with the following command: -+ -+$ sudo grep offline_credentials_expiration /etc/sssd/sssd.conf -+ -+offline_credentials_expiration = 1 -+ -+If "offline_credentials_expiration" is not set to a value of "1", this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>RHEL-09-651010RHEL 9 must have the AIDE package installed.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. -+ -+Satisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000445-GPOS-00199</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001744CCI-002696Install AIDE, initialize it, and perform a manual check. -+ -+Install AIDE: -+ -+$ sudo dnf install aide -+ -+Initialize AIDE: -+ -+$ sudo /usr/sbin/aide --init -+ -+Example output: -+ -+Start timestamp: 2023-06-05 10:09:04 -0600 (AIDE 0.16) -+AIDE initialized database at /var/lib/aide/aide.db.new.gz -+ -+Number of entries: 86833 -+ -+--------------------------------------------------- -+The attributes of the (uncompressed) database(s): -+--------------------------------------------------- -+ -+/var/lib/aide/aide.db.new.gz -+ MD5 : coZUtPHhoFoeD7+k54fUvQ== -+ SHA1 : DVpOEMWJwo0uPgrKZAygIUgSxeM= -+ SHA256 : EQiZH0XNEk001tcDmJa+5STFEjDb4MPE -+ TGdBJ/uvZKc= -+ SHA512 : 86KUqw++PZhoPK0SZvT3zuFq9yu9nnPP -+ toei0nENVELJ1LPurjoMlRig6q69VR8l -+ +44EwO9eYyy9nnbzQsfG1g== -+ -+End timestamp: 2023-06-05 10:09:57 -0600 (run time: 0m 53s) -+ -+The new database will need to be renamed to be read by AIDE: -+ -+$ sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz -+ -+Perform a manual check: -+ -+$ sudo /usr/sbin/aide --check -+ -+Example output: -+ -+2023-06-05 10:16:08 -0600 (AIDE 0.16) -+AIDE found NO differences between database and filesystem. Looks okay!! -+ -+...Verify that RHEL 9 has the Advanced Intrusion Detection Environment (AIDE) package installed with the following command: -+ -+$ sudo dnf list --installed aide -+ -+Example output: -+ -+aide.x86_64 0.16.100.el9 -+ -+If AIDE is not installed, ask the system administrator (SA) how file integrity checks are performed on the system. -+ -+If there is no application installed to perform integrity checks, this is a finding. -+ -+If AIDE is installed, check if it has been initialized with the following command: -+ -+$ sudo /usr/sbin/aide --check -+ -+If the output is "Couldn't open file /var/lib/aide/aide.db.gz for reading", this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>RHEL-09-651015RHEL 9 must routinely check the baseline configuration for unauthorized changes and notify the system administrator when anomalies in the operation of any security functions are discovered.<VulnDiscussion>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. -+ -+Notifications provided by information systems include messages to local computer consoles, and/or hardware indications, such as lights. -+ -+This capability must take into account operational requirements for availability for selecting an appropriate response. The organization may choose to shut down or restart the information system upon security function anomaly detection. -+ -+Satisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000446-GPOS-00200, SRG-OS-000447-GPOS-00201</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001744CCI-002699CCI-002702Configure the file integrity tool to run automatically on the system at least weekly and to notify designated personnel if baseline configurations are changed in an unauthorized manner. The AIDE tool can be configured to email designated personnel with the use of the cron system. -+ -+The following example output is generic. It will set cron to run AIDE daily and to send email at the completion of the analysis -+ -+$ sudo more /etc/cron.daily/aide -+ -+#!/bin/bash -+/usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.milVerify that RHEL 9 routinely executes a file integrity scan for changes to the system baseline. The command used in the example will use a daily occurrence. -+ -+Check the cron directories for scripts controlling the execution and notification of results of the file integrity application. For example, if AIDE is installed on the system, use the following commands: -+ -+$ ls -al /etc/cron.* | grep aide -+ -+-rwxr-xr-x 1 root root 29 Nov 22 2015 aide -+ -+$ grep aide /etc/crontab /var/spool/cron/root -+ -+/etc/crontab: 30 04 * * * root usr/sbin/aide -+/var/spool/cron/root: 30 04 * * * root usr/sbin/aide -+ -+$ sudo more /etc/cron.daily/aide -+ -+#!/bin/bash -+/usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil -+ -+If the file integrity application does not exist, or a script file controlling the execution of the file integrity application does not exist, or the file integrity application does not notify designated personnel of changes, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-651020RHEL 9 must use a file integrity tool that is configured to use FIPS 140-3-approved cryptographic hashes for validating file contents and directories.<VulnDiscussion>RHEL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable at install time. This requirement assumes the "aide.conf" file is under the "/etc" directory. -+ -+File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2/140-3-approved cryptographic hashes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the file integrity tool to use FIPS 140-2/140-3 cryptographic hashes for validating file and directory contents. -+ -+If AIDE is installed, ensure the "sha512" rule is present on all uncommented file and directory selection lists. Exclude any log files, or files expected to change frequently, to reduce unnecessary notifications.Verify that AIDE is configured to use FIPS 140-2/140-3 file hashing with the following command: -+ -+$ grep sha512 /etc/aide.conf -+ -+All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux -+ -+If the "sha512" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using FIPS 140-2/140-3-approved cryptographic hashes for validating file contents and directories, this is a finding.SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>RHEL-09-651025RHEL 9 must use cryptographic mechanisms to protect the integrity of audit tools.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099, SRG-OS-000278-GPOS-00108</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001493CCI-001494CCI-001495CCI-001496Add or update the following lines to "/etc/aide.conf", to protect the integrity of the audit tools. -+ -+/usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512Check that AIDE is properly configured to protect the integrity of the audit tools with the following command: -+ -+$ sudo cat /etc/aide.conf | grep /usr/sbin/au -+ -+/usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 -+/usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 -+ -+If AIDE is not installed, ask the system administrator (SA) how file integrity checks are performed on the system. -+ -+If any of the audit tools listed above do not have a corresponding line, ask the SA to indicate what cryptographic mechanisms are being used to protect the integrity of the audit tools. If there is no evidence of integrity protection, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-651030RHEL 9 must be configured so that the file integrity tool verifies Access Control Lists (ACLs).<VulnDiscussion>RHEL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable at install time. This requirement assumes the "aide.conf" file is under the "/etc" directory. -+ -+ACLs can provide permissions beyond those permitted through the file mode and must be verified by the file integrity tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the file integrity tool to check file and directory ACLs. -+ -+If AIDE is installed, ensure the "acl" rule is present on all uncommented file and directory selection lists.Verify that that AIDE is verifying ACLs with the following command: -+ -+$ grep acl /etc/aide.conf -+ -+All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux -+ -+If the "acl" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or ACLs are not being checked by another file integrity tool, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-651035RHEL 9 must be configured so that the file integrity tool verifies extended attributes.<VulnDiscussion>RHEL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable at install time. This requirement assumes the "aide.conf" file is under the "/etc" directory. -+ -+Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the file integrity tool to check file and directory extended attributes. -+ -+If AIDE is installed, ensure the "xattrs" rule is present on all uncommented file and directory selection lists.Verify that AIDE is configured to verify extended attributes with the following command: -+ -+$ grep xattrs /etc/aide.conf -+ -+All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux -+ -+If the "xattrs" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>RHEL-09-652010RHEL 9 must have the rsyslog package installed.<VulnDiscussion>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), to create a method to securely encrypt and offload auditing. -+ -+Satisfies: SRG-OS-000479-GPOS-00224, SRG-OS-000051-GPOS-00024, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000154CCI-000366CCI-001851The rsyslogd package can be installed with the following command: -+ -+$ sudo dnf install rsyslogdVerify that RHEL 9 has the rsyslogd package installed with the following command: -+ -+$ sudo dnf list --installed rsyslog -+ -+Example output: -+ -+rsyslog.x86_64 8.2102.0-101.el9_0.1 -+ -+If the "rsyslogd" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-652015RHEL 9 must have the packages required for encrypting offloaded audit logs installed.<VulnDiscussion>The rsyslog-gnutls package provides Transport Layer Security (TLS) support for the rsyslog daemon, which enables secure remote logging. -+ -+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-000803The rsyslog-gnutls package can be installed with the following command: -+ -+$ sudo dnf install rsyslog-gnutlsVerify that RHEL 9 has the rsyslog-gnutls package installed with the following command: -+ -+$ sudo dnf list --installed rsyslog-gnutls -+ -+Example output: -+ -+rsyslog-gnutls.x86_64 8.2102.0-101.el9_0.1 -+ -+If the "rsyslog-gnutls" package is not installed, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-652020The rsyslog service on RHEL 9 must be active.<VulnDiscussion>The "rsyslog" service must be running to provide logging services, which are essential to system administration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366To enable the rsyslog service, run the following command: -+ -+$ sudo systemctl enable --now rsyslogVerify that "rsyslog" is active with the following command: -+ -+$ systemctl is-active rsyslog -+ -+active -+ -+If the rsyslog service is not active, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-652025RHEL 9 must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation.<VulnDiscussion>Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information into the system's logs, or could fill the system's storage leading to a denial of service. -+ -+If the system is intended to be a log aggregation server, its use must be documented with the information system security officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure RHEL 9 to not receive remote logs using rsyslog. -+ -+Remove the lines in /etc/rsyslog.conf and any files in the /etc/rsyslog.d directory that match any of the following: -+ -+$ModLoad imtcp -+$ModLoad imudp -+$ModLoad imrelp -+$InputTCPServerRun [0-9]* -+$UDPServerRun [0-9]* -+$InputRELPServerRun [0-9]* -+ -+The rsyslog daemon must be restarted for the changes to take effect: -+ -+$ sudo systemctl restart rsyslog.serviceVerify that RHEL 9 is not configured to receive remote logs using rsyslog with the following commands: -+ -+$ grep -i modload /etc/rsyslog.conf /etc/rsyslog.d/* -+$ModLoad imtcp -+$ModLoad imrelp -+ -+$ grep -i serverrun /etc/rsyslog.conf /etc/rsyslog.d/* -+$InputTCPServerRun 514 -+$InputRELPServerRun 514 -+ -+Note: An error about no files or directories may be returned. This is not a finding. -+ -+If any lines are returned by the command, then rsyslog is configured to receive remote messages, and this is a finding.SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>RHEL-09-652030All RHEL 9 remote access methods must be monitored.<VulnDiscussion>Logging remote access methods can be used to trace the decrease in the risks associated with remote user access management. It can also be used to spot cyberattacks and ensure ongoing compliance with organizational policies surrounding the use of remote access methods.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000067Add or update the following lines to the "/etc/rsyslog.conf" file: -+ -+auth.*;authpriv.*;daemon.* /var/log/secure -+ -+The "rsyslog" service must be restarted for the changes to take effect with the following command: -+ -+$ sudo systemctl restart rsyslog.serviceVerify that RHEL 9 monitors all remote access methods. -+ -+Check that remote access methods are being logged by running the following command: -+ -+$ grep -rE '(auth.\*|authpriv.\*|daemon.\*)' /etc/rsyslog.conf -+ -+/etc/rsyslog.conf:authpriv.* -+ -+If "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-652035RHEL 9 must be configured to offload audit records onto a different system from the system being audited via syslog.<VulnDiscussion>The auditd service does not include the ability to send audit records to a centralized server for management directly. However, it can use a plug-in for audit event multiplexor (audispd) to pass audit records to the local syslog server. -+ -+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851Edit the /etc/audit/plugins.d/syslog.conf file and add or update the "active" option: -+ -+active = yes -+ -+The audit daemon must be restarted for changes to take effect.Verify RHEL 9 is configured use the audisp-remote syslog service with the following command: -+ -+$ sudo grep active /etc/audit/plugins.d/syslog.conf -+ -+active = yes -+ -+If the "active" keyword does not have a value of "yes", the line is commented out, or the line is missing, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-652040RHEL 9 must authenticate the remote logging server for offloading audit logs via rsyslog.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. -+ -+Offloading is a common process in information systems with limited audit storage capacity. -+ -+RHEL 9 installation media provides "rsyslogd", 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. Coupling this utility with "gnutls" (a secure communications library implementing the SSL, TLS and DTLS protocols) creates a method to securely encrypt and offload auditing. -+ -+"Rsyslog" supported authentication modes include: -+anon - anonymous authentication -+x509/fingerprint - certificate fingerprint authentication -+x509/certvalid - certificate validation only -+x509/name - certificate validation and subject name authentication -+ -+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851Configure RHEL 9 to authenticate the remote logging server for offloading audit logs by setting the following option in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf": -+ -+$ActionSendStreamDriverAuthMode x509/nameVerify RHEL 9 authenticates the remote logging server for offloading audit logs with the following command: -+ -+$ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+ /etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name -+ -+If the value of the "$ActionSendStreamDriverAuthMode" option is not set to "x509/name" or the line is commented out, ask the system administrator (SA) to indicate how the audit logs are offloaded to a different system or media. -+ -+If there is no evidence that the transfer of the audit logs being offloaded to another system or media is encrypted, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-652045RHEL 9 must encrypt the transfer of audit records offloaded onto a different system or media from the system being audited via rsyslog.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. -+ -+Offloading is a common process in information systems with limited audit storage capacity. -+ -+RHEL 9 installation media provides "rsyslogd", 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. Coupling this utility with "gnutls" (a secure communications library implementing the SSL, TLS and DTLS protocols) creates a method to securely encrypt and offload auditing. -+ -+"Rsyslog" supported authentication modes include: -+anon - anonymous authentication -+x509/fingerprint - certificate fingerprint authentication -+x509/certvalid - certificate validation only -+x509/name - certificate validation and subject name authentication -+ -+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851Configure RHEL 9 to encrypt offloaded audit records via rsyslog by setting the following options in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf": -+ -+$ActionSendStreamDriverMode 1Verify RHEL 9 encrypts audit records offloaded onto a different system or media from the system being audited via rsyslog with the following command: -+ -+$ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+/etc/rsyslog.conf:$ActionSendStreamDriverMode 1 -+ -+If the value of the "$ActionSendStreamDriverMode" option is not set to "1" or the line is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-652050RHEL 9 must encrypt via the gtls driver the transfer of audit records offloaded onto a different system or media from the system being audited via rsyslog.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. -+ -+Offloading is a common process in information systems with limited audit storage capacity. -+ -+RHEL 9 installation media provides "rsyslogd", 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. Coupling this utility with "gnutls" (a secure communications library implementing the SSL, TLS and DTLS protocols) creates a method to securely encrypt and offload auditing. -+ -+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851Configure RHEL 9 to use the gtls driver to encrypt offloaded audit records by setting the following options in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf": -+ -+$DefaultNetstreamDriver gtlsVerify RHEL 9 uses the gtls driver to encrypt audit records offloaded onto a different system or media from the system being audited with the following command: -+ -+$ sudo grep -i '$DefaultNetstreamDriver' /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+/etc/rsyslog.conf:$DefaultNetstreamDriver gtls -+ -+If the value of the "$DefaultNetstreamDriver" option is not set to "gtls" or the line is commented out, this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>RHEL-09-652055RHEL 9 must be configured to forward audit records via TCP to a different system or media from the system being audited via rsyslog.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. -+ -+Offloading is a common process in information systems with limited audit storage capacity. -+ -+RHEL 9 installation media provides "rsyslogd", 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. Coupling this utility with "gnutls" (a secure communications library implementing the SSL, TLS and DTLS protocols) creates a method to securely encrypt and offload auditing. -+ -+Rsyslog provides three ways to forward message: the traditional UDP transport, which is extremely lossy but standard; the plain TCP based transport, which loses messages only during certain situations but is widely available; and the RELP transport, which does not lose messages but is currently available only as part of the rsyslogd 3.15.0 and above. -+ -+Examples of each configuration: -+UDP *.* @remotesystemname -+TCP *.* @@remotesystemname -+RELP *.* :omrelp:remotesystemname:2514 -+Note that a port number was given as there is no standard port for RELP. -+ -+Satisfies: SRG-OS-000479-GPOS-00224, SRG-OS-000480-GPOS-00227, SRG-OS-000342-GPOS-00133</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001851Configure RHEL 9 to offload audit records onto a different system or media from the system being audited via TCP using rsyslog by specifying the remote logging server in "/etc/rsyslog.conf"" or "/etc/rsyslog.d/[customfile].conf" with the name or IP address of the log aggregation server. -+ -+*.* @@[remoteloggingserver]:[port]"Verify that RHEL 9 audit system offloads audit records onto a different system or media from the system being audited via rsyslog using TCP with the following command: -+ -+$ sudo grep @@ /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+/etc/rsyslog.conf:*.* @@[remoteloggingserver]:[port] -+ -+If a remote server is not configured, or the line is commented out, ask the system administrator (SA) to indicate how the audit logs are offloaded to a different system or media. -+ -+If there is no evidence that the audit logs are being offloaded to another system or media, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-652060RHEL 9 must use cron logging.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure "rsyslog" to log all cron messages by adding or updating the following line to "/etc/rsyslog.conf" or a configuration file in the /etc/rsyslog.d/ directory: -+ -+cron.* /var/log/cron -+ -+The rsyslog daemon must be restarted for the changes to take effect: -+ -+$ sudo systemctl restart rsyslog.serviceVerify that "rsyslog" is configured to log cron events with the following command: -+ -+Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files. -+ -+$ sudo grep -s cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+/etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages -+/etc/rsyslog.conf:cron.* /var/log/cron -+ -+If the command does not return a response, check for cron logging all facilities with the following command: -+ -+$ sudo grep -s /var/log/messages /etc/rsyslog.conf /etc/rsyslog.d/*.conf -+ -+/etc/rsyslog.conf:*.info;mail.none;authpriv.none;cron.none /var/log/messages -+ -+If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>RHEL-09-653010RHEL 9 audit package must be installed.<VulnDiscussion>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. -+ -+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. -+ -+Associating event types with detected events in audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured RHEL 9 system. -+ -+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000358-GPOS-00145, SRG-OS-000365-GPOS-00152, SRG-OS-000392-GPOS-00172, SRG-OS-000475-GPOS-00220, SRG-OS-000055-GPOS-00026</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000131CCI-000132CCI-000133CCI-000134CCI-000135CCI-000154CCI-000158CCI-000159CCI-000169CCI-000172CCI-001464CCI-001487CCI-001814CCI-001875CCI-001876CCI-001877CCI-001878CCI-001879CCI-001880CCI-001881CCI-001882CCI-001889CCI-001914CCI-002884Install the audit service package (if the audit service is not already installed) with the following command: -+ -+$ sudo dnf install auditVerify that RHEL 9 audit service package is installed. -+ -+Check that the audit service package is installed with the following command: -+ -+$ sudo dnf list --installed audit -+ -+Example output: -+ -+audit-3.0.7-101.el9_0.2.x86_64 -+ -+If the "audit" package is not installed, this is a finding.SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>RHEL-09-653015RHEL 9 audit service must be enabled.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000358-GPOS-00145, SRG-OS-000365-GPOS-00152, SRG-OS-000392-GPOS-00172, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000131CCI-000132CCI-000133CCI-000134CCI-000135CCI-000154CCI-000158CCI-000169CCI-000172CCI-001464CCI-001487CCI-001814CCI-001875CCI-001876CCI-001877CCI-001878CCI-001879CCI-001880CCI-001881CCI-001882CCI-001889CCI-001914CCI-002884To enable the auditd service run the following command: -+ -+$ sudo systemctl enable --now auditdVerify the audit service is configured to produce audit records with the following command: -+ -+$ systemctl status auditd.service -+ -+auditd.service - Security Auditing Service -+Loaded:loaded (/usr/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) -+Active: active (running) since Tues 2022-05-24 12:56:56 EST; 4 weeks 0 days ago -+ -+If the audit service is not "active" and "running", this is a finding.SRG-OS-000047-GPOS-00023<GroupDescription></GroupDescription>RHEL-09-653020RHEL 9 audit system must take appropriate action when an error writing to the audit storage volume occurs.<VulnDiscussion>It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000140Configure RHEL 9 to shut down by default upon audit failure (unless availability is an overriding concern). -+ -+Add or update the following line (depending on configuration "disk_error_action" can be set to "SYSLOG" or "SINGLE" depending on configuration) in "/etc/audit/auditd.conf" file: -+ -+disk_error_action = HALT -+ -+If availability has been determined to be more important, and this decision is documented with the information system security officer (ISSO), configure the operating system to notify SA staff and ISSO staff in the event of an audit processing failure by setting the "disk_error_action" to "SYSLOG".Verify RHEL 9 takes the appropriate action when an audit processing failure occurs. -+ -+Check that RHEL 9 takes the appropriate action when an audit processing failure occurs with the following command: -+ -+$ sudo grep disk_error_action /etc/audit/auditd.conf -+ -+disk_error_action = HALT -+ -+If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator (SA) to indicate how the system takes appropriate action when an audit process failure occurs. If there is no evidence of appropriate action, this is a finding.SRG-OS-000047-GPOS-00023<GroupDescription></GroupDescription>RHEL-09-653025RHEL 9 audit system must take appropriate action when the audit storage volume is full.<VulnDiscussion>It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000140Configure RHEL 9 to shut down by default upon audit failure (unless availability is an overriding concern). -+ -+Add or update the following line (depending on configuration "disk_full_action" can be set to "SYSLOG" or "SINGLE" depending on configuration) in "/etc/audit/auditd.conf" file: -+ -+disk_full_action = HALT -+ -+If availability has been determined to be more important, and this decision is documented with the information system security officer (ISSO), configure the operating system to notify SA staff and ISSO staff in the event of an audit processing failure by setting the "disk_full_action" to "SYSLOG".Verify RHEL 9 takes the appropriate action when the audit storage volume is full. -+ -+Check that RHEL 9 takes the appropriate action when the audit storage volume is full with the following command: -+ -+$ sudo grep disk_full_action /etc/audit/auditd.conf -+ -+disk_full_action = HALT -+ -+If the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator (SA) to indicate how the system takes appropriate action when an audit storage volume is full. If there is no evidence of appropriate action, this is a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>RHEL-09-653030RHEL 9 must allocate audit record storage capacity to store at least one week's worth of audit records.<VulnDiscussion>To ensure RHEL 9 systems have a sufficient storage capacity in which to write the audit logs, RHEL 9 needs to be able to allocate audit record storage capacity. -+ -+The task of allocating audit record storage capacity is usually performed during initial installation of RHEL 9. -+ -+Satisfies: SRG-OS-000341-GPOS-00132, SRG-OS-000342-GPOS-00133</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001849CCI-001851Allocate enough storage capacity for at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. -+ -+If audit records are stored on a partition made specifically for audit records, resize the partition with sufficient space to contain one week of audit records. -+ -+If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.Verify RHEL 9 allocates audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. -+ -+Note: The partition size needed to capture a week of audit records is based on the activity level of the system and the total storage capacity available. Typically 10.0 GB of storage space for audit records should 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.log -+ -+Check the size of the partition that audit records are written to with the following command and verify whether it is sufficiently large: -+ -+ # df -h /var/log/audit/ -+/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit -+ -+If the audit record partition is not allocated for sufficient storage capacity, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>RHEL-09-653035RHEL 9 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.<VulnDiscussion>If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001855Configure RHEL 9 to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file. -+ -+space_left = 25%Verify RHEL 9 takes action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command: -+ -+$ sudo grep -w space_left /etc/audit/auditd.conf -+ -+space_left = 25% -+ -+If the value of the "space_left" keyword is not set to 25 percent of the storage volume allocated to audit logs, or if the line is commented out, ask the system administrator (SA) to indicate how the system is providing real-time alerts to the SA and information system security officer (ISSO). If the "space_left" value is not configured to the correct value, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>RHEL-09-653040RHEL 9 must notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume 75 percent utilization.<VulnDiscussion>If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001855Configure RHEL 9 to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file. -+ -+space_left_action = emailVerify RHEL 9 notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command: -+ -+$ sudo grep -w space_left_action /etc/audit/auditd.conf -+ -+space_left_action = email -+ -+If the value of the "space_left_action" is not set to "email", or if the line is commented out, ask the SA to indicate how the system is providing real-time alerts to the SA and ISSO. -+ -+If there is no evidence that real-time alerts are configured on the system, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>RHEL-09-653045RHEL 9 must take action when allocated audit record storage volume reaches 95 percent of the audit record storage capacity.<VulnDiscussion>If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001855Configure RHEL 9 to initiate an action when allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file. -+ -+admin_space_left = 5%Verify RHEL 9 takes action when allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity with the following command: -+ -+$ sudo grep -w admin_space_left /etc/audit/auditd.conf -+ -+admin_space_left = 5% -+ -+If the value of the "admin_space_left" keyword is not set to 5 percent of the storage volume allocated to audit logs, or if the line is commented out, ask the system administrator (SA) to indicate how the system is taking action if the allocated storage is about to reach capacity. If the "space_left" value is not configured to the correct value, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>RHEL-09-653050RHEL 9 must take action when allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity.<VulnDiscussion>If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001855Configure "auditd" service to take action in the event of allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity. -+ -+Edit the following line in "/etc/audit/auditd.conf" to ensure that the system is forced into single user mode in the event the audit record storage volume is about to reach maximum capacity: -+ -+admin_space_left_action = single -+ -+The audit daemon must be restarted for changes to take effect.Verify that RHEL 9 is configured to take action in the event of allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity with the following command: -+ -+$ sudo grep admin_space_left_action /etc/audit/auditd.conf -+ -+admin_space_left_action = single -+ -+If the value of the "admin_space_left_action" is not set to "single", or if the line is commented out, ask the system administrator (SA) to indicate how the system is providing real-time alerts to the SA and information system security officer (ISSO). -+ -+If there is no evidence that real-time alerts are configured on the system, this is a finding.SRG-OS-000047-GPOS-00023<GroupDescription></GroupDescription>RHEL-09-653055RHEL 9 audit system must take appropriate action when the audit files have reached maximum size.<VulnDiscussion>It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000140Configure RHEL 9 to rotate the audit log when it reaches maximum size. -+ -+Add or update the following line in "/etc/audit/auditd.conf" file: -+ -+max_log_file_action = ROTATEVerify that RHEL 9 takes the appropriate action when the audit files have reached maximum size with the following command: -+ -+$ sudo grep max_log_file_action /etc/audit/auditd.conf -+ -+max_log_file_action = ROTATE -+ -+If the value of the "max_log_file_action" option is not "ROTATE", "SINGLE", or the line is commented out, ask the system administrator (SA)to indicate how the system takes appropriate action when an audit storage volume is full. If there is no evidence of appropriate action, this is a finding.SRG-OS-000039-GPOS-00017<GroupDescription></GroupDescription>RHEL-09-653060RHEL 9 must label all offloaded audit logs before sending them to the central log server.<VulnDiscussion>Enriched logging is needed to determine who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult. -+ -+When audit logs are not labeled before they are sent to a central log server, the audit data will not be able to be analyzed and tied back to the correct system. -+ -+Satisfies: SRG-OS-000039-GPOS-00017, SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000132CCI-001851Edit the /etc/audit/auditd.conf file and add or update the "name_format" option: -+ -+name_format = hostname -+ -+The audit daemon must be restarted for changes to take effect.Verify that RHEL 9 Audit Daemon is configured to label all offloaded audit logs, with the following command: -+ -+$ sudo grep name_format /etc/audit/auditd.conf -+ -+name_format = hostname -+ -+If the "name_format" option is not "hostname", "fqd", or "numeric", or the line is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-653065RHEL 9 must take appropriate action when the internal event queue is full.<VulnDiscussion>The audit system should have an action setup in the event the internal event queue becomes full so that no data is lost. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. -+ -+Offloading is a common process in information systems with limited audit storage capacity. -+ -+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851Edit the /etc/audit/auditd.conf file and add or update the "overflow_action" option: -+ -+overflow_action = syslog -+ -+The audit daemon must be restarted for changes to take effect.Verify that RHEL 9 audit system is configured to take an appropriate action when the internal event queue is full: -+ -+$ sudo grep -i overflow_action /etc/audit/auditd.conf -+ -+overflow_action = syslog -+ -+If the value of the "overflow_action" option is not set to "syslog", "single", "halt" or the line is commented out, ask the system administrator (SA) to indicate how the audit logs are offloaded to a different system or media. -+ -+If there is no evidence that the transfer of the audit logs being offloaded to another system or media takes appropriate action if the internal event queue becomes full, this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>RHEL-09-653070RHEL 9 System Administrator (SA) and/or information system security officer (ISSO) (at a minimum) must be alerted of an audit processing failure event.<VulnDiscussion>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. -+ -+This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both. -+ -+Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000343-GPOS-00134</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000139CCI-001855Configure "auditd" service to notify the SA and ISSO in the event of an audit processing failure. -+ -+Edit the following line in "/etc/audit/auditd.conf" to ensure that administrators are notified via email for those situations: -+ -+action_mail_acct = root -+ -+The audit daemon must be restarted for changes to take effect.Verify that RHEL 9 is configured to notify the SA and/or ISSO (at a minimum) in the event of an audit processing failure with the following command: -+ -+$ sudo grep action_mail_acct /etc/audit/auditd.conf -+ -+action_mail_acct = root -+ -+If the value of the "action_mail_acct" keyword is not set to "root" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the retuned line is commented out, ask the SA to indicate how they and the ISSO are notified of an audit process failure. If there is no evidence of the proper personnel being notified of an audit processing failure, this is a finding.SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>RHEL-09-653075RHEL 9 audit system must audit local events.<VulnDiscussion>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. -+ -+If option "local_events" isn't set to "yes" only events from network will be aggregated. -+ -+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000169CCI-000366Configure RHEL 9 to generate audit records for local events by adding or updating the following line in "/etc/audit/auditd.conf": -+ -+local_events = yes -+ -+The audit daemon must be restarted for the changes to take effect.Verify that the RHEL 9 audit system is configured to audit local events with the following command: -+ -+$ sudo grep local_events /etc/audit/auditd.conf -+ -+local_events = yes -+ -+If "local_events" isn't set to "yes", if the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>RHEL-09-653080RHEL 9 audit logs must be group-owned by root or by a restricted logging group to prevent unauthorized read access.<VulnDiscussion>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. -+ -+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000206-GPOS-00084</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000162CCI-000163CCI-000164CCI-001314Change the group of the directory of "/var/log/audit" to be owned by a correct group. -+ -+Identify the group that is configured to own audit log: -+ -+$ sudo grep -P '^[ ]*log_group[ ]+=.*$' /etc/audit/auditd.conf -+ -+Change the ownership to that group: -+ -+$ sudo chgrp ${GROUP} /var/log/auditVerify the audit logs are group-owned by "root" or a restricted logging group. -+ -+First determine if a group other than "root" has been assigned to the audit logs with the following command: -+ -+$ sudo grep log_group /etc/audit/auditd.conf -+ -+Then determine where the audit logs are stored with the following command: -+ -+$ sudo grep -iw log_file /etc/audit/auditd.conf -+ -+log_file = /var/log/audit/audit.log -+ -+Then using the location of the audit log file, determine if the audit log is group-owned by "root" using the following command: -+ -+$ sudo stat -c "%G %n" /var/log/audit/audit.log -+ -+root /var/log/audit/audit.log -+ -+If the audit log is not group-owned by "root" or the configured alternative logging group, this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>RHEL-09-653085RHEL 9 audit log directory must be owned by root to prevent unauthorized read access.<VulnDiscussion>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. -+ -+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000206-GPOS-00084</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000162CCI-000163CCI-000164CCI-001314Configure the audit log to be protected from unauthorized read access by setting the correct owner as "root" with the following command: -+ -+$ sudo chown root /var/log/auditVerify the audit logs directory is owned by "root". -+ -+First determine where the audit logs are stored with the following command: -+ -+$ sudo grep -iw log_file /etc/audit/auditd.conf -+ -+log_file = /var/log/audit/audit.log -+ -+Then using the location of the audit log file, determine if the audit log directory is owned by "root" using the following command: -+ -+$ sudo ls -ld /var/log/audit -+ -+drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit -+ -+If the audit log directory is not owned by "root", this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>RHEL-09-653090RHEL 9 audit logs file must have mode 0600 or less permissive to prevent unauthorized access to the audit log.<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the RHEL 9 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. -+ -+The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. -+ -+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000206-GPOS-00084</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000162CCI-000163CCI-000164CCI-001314Configure the audit logs to have a mode of "0600" with the following command: -+ -+Replace "[audit_log_file]" to the correct audit log path, by default this location is "/var/log/audit/audit.log". -+ -+$ sudo chmod 0600 /var/log/audit/[audit_log_file] -+ -+Check the group that owns the system audit logs: -+ -+$ sudo grep -m 1 -q ^log_group /etc/audit/auditd.conf -+ -+If the log_group is not defined or it is set to root, configure the permissions the following way: -+ -+$ sudo chmod 0640 $log_file -+$ sudo chmod 0440 $log_file.* -+ -+Otherwise, configure the permissions the following way: -+ -+$ sudo chmod 0600 $log_file -+$ sudo chmod 0400 $log_file.*Verify the audit logs have a mode of "0600". -+ -+First determine where the audit logs are stored with the following command: -+ -+$ sudo grep -iw log_file /etc/audit/auditd.conf -+ -+log_file = /var/log/audit/audit.log -+ -+Then using the location of the audit log file, determine if the audit log files as a mode of "0640" with the following command: -+ -+$ sudo ls -la /var/log/audit/*.log -+ -+rw-------. 2 root root 237923 Jun 11 11:56 /var/log/audit/audit.log -+ -+If the audit logs have a mode more permissive than "0600", this is a finding.SRG-OS-000051-GPOS-00024<GroupDescription></GroupDescription>RHEL-09-653095RHEL 9 must periodically flush audit records to disk to prevent the loss of audit records.<VulnDiscussion>If option "freq" is not set to a value that requires audit records being written to disk after a threshold number is reached, then audit records may be lost.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000154Configure RHEL 9 to flush audit to disk by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+freq = 100 -+ -+The audit daemon must be restarted for the changes to take effect.Verify that audit system is configured to flush to disk after every 100 records with the following command: -+ -+$ sudo grep freq /etc/audit/auditd.conf -+ -+freq = 100 -+ -+If "freq" isn't set to a value of "100" or greater, the value is missing, or the line is commented out, this is a finding.SRG-OS-000255-GPOS-00096<GroupDescription></GroupDescription>RHEL-09-653100RHEL 9 must produce audit records containing information to establish the identity of any individual or process associated with the event.<VulnDiscussion>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. -+ -+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. -+ -+Enriched logging aids in making sense of who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult. -+ -+Satisfies: SRG-OS-000255-GPOS-00096, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366CCI-001487Edit the /etc/audit/auditd.conf file and add or update the "log_format" option: -+ -+log_format = ENRICHED -+ -+The audit daemon must be restarted for changes to take effect.Verify that RHEL 9 audit system is configured to resolve audit information before writing to disk, with the following command: -+ -+$ sudo grep log_format /etc/audit/auditd.conf -+ -+log_format = ENRICHED -+ -+If the "log_format" option is not "ENRICHED", or the line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>RHEL-09-653105RHEL 9 must write audit records to disk.<VulnDiscussion>Audit data should be synchronously written to disk to ensure log integrity. This setting assures that all audit event data is written disk.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000366Configure the audit system to write log files to the disk. -+ -+Edit the /etc/audit/auditd.conf file and add or update the "write_logs" option to "yes": -+ -+write_logs = yes -+ -+The audit daemon must be restarted for changes to take effect.Verify that the audit system is configured to write logs to the disk with the following command: -+ -+$ sudo grep write_logs /etc/audit/auditd.conf -+ -+write_logs = yes -+ -+If "write_logs" does not have a value of "yes", the line is commented out, or the line is missing, this is a finding.SRG-OS-000063-GPOS-00032<GroupDescription></GroupDescription>RHEL-09-653110RHEL 9 must allow only the information system security manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.<VulnDiscussion>Without the capability to restrict the roles and individuals that 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000171Configure the files in directory "/etc/audit/rules.d/" and the "/etc/audit/auditd.conf" file to have a mode of "0640" with the following commands: -+ -+$ sudo chmod 0640 /etc/audit/rules.d/audit.rules -+$ sudo chmod 0640 /etc/audit/rules.d/[customrulesfile].rules -+$ sudo chmod 0640 /etc/audit/auditd.confVerify that the files in directory "/etc/audit/rules.d/" and "/etc/audit/auditd.conf" file have a mode of "0640" or less permissive with the following command: -+ -+$ sudo stat -c "%a %n" /etc/audit/rules.d/*.rules -+ -+640 /etc/audit/rules.d/audit.rules -+ -+If the files in the "/etc/audit/rules.d/" directory or the "/etc/audit/auditd.conf" file have a mode more permissive than "0640", this is a finding.SRG-OS-000063-GPOS-00032<GroupDescription></GroupDescription>RHEL-09-653115RHEL 9 /etc/audit/auditd.conf file must have 0640 or less permissive to prevent unauthorized access.<VulnDiscussion>Without the capability to restrict the roles and individuals that 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000171Set the mode of /etc/audit/auditd.conf file to 0640 with the command: -+ -+$ sudo chmod 0640 /etc/audit/auditd.confVerify the mode of /etc/audit/auditd.conf with the command: -+ -+$ sudo stat -c "%a %n" /etc/audit/auditd.conf -+ -+640 /etc/audit/auditd.conf -+ -+If "/etc/audit/auditd.conf" does not have a mode of "0640", this is a finding.SRG-OS-000254-GPOS-00095<GroupDescription></GroupDescription>RHEL-09-653120RHEL 9 must allocate an audit_backlog_limit of sufficient size to capture processes that start prior to the audit daemon.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. -+ -+If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created. -+ -+Audit records can be generated from various components within the information system (e.g., module or policy filter). -+ -+Allocating an audit_backlog_limit of sufficient size is critical in maintaining a stable boot process. With an insufficient limit allocated, the system is susceptible to boot failures and crashes. -+ -+Satisfies: SRG-OS-000254-GPOS-00095, SRG-OS-000341-GPOS-00132</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001464CCI-001849Configure RHEL 9 to allocate sufficient audit_backlog_limit to capture processes that start prior to the audit daemon with the following command: -+ -+$ sudo grubby --update-kernel=ALL --args=audit_backlog_limit=8192Verify RHEL 9 allocates a sufficient audit_backlog_limit to capture processes that start prior to the audit daemon with the following command: -+ -+$ sudo grubby --info=ALL | grep args | grep -v 'audit_backlog_limit=8192' -+ -+If the command returns any outputs, and audit_backlog_limit is less than "8192", this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>RHEL-09-653125RHEL 9 must have mail aliases to notify the information system security officer (ISSO) and system administrator (SA) (at a minimum) in the event of an audit processing failure.<VulnDiscussion>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. -+ -+This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000139Edit the aliases map file (by default /etc/aliases) used by Postfix and configure a root alias (using the user ISSO as an example): -+ -+root: ISSO -+ -+and then update the aliases database with the command: -+ -+$ sudo newaliasesVerify that RHEL 9 is configured to notify the appropriate interactive users in the event of an audit processing failure. -+ -+Find the alias maps that are being used with the following command: -+ -+$ postconf alias_maps -+ -+alias_maps = hash:/etc/aliases -+ -+Query the Postfix alias maps for an alias for the root user with the following command: -+ -+$ postmap -q root hash:/etc/aliases -+isso -+ -+If an alias is not set, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>RHEL-09-653130RHEL 9 audispd-plugins package must be installed.<VulnDiscussion>"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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001851The audispd-plugins package can be installed with the following command: -+ -+$ sudo dnf install audispd-pluginsVerify that RHEL 9 has the audispd-plugins package for installed with the following command: -+ -+$ sudo dnf list --installed audispd-plugins -+ -+Example output: -+ -+audispd-plugins.x86_64 3.0.7-101.el9_0.2 -+ -+If the "audispd-plugins" package is not installed, this is a finding.SRG-OS-000326-GPOS-00126<GroupDescription></GroupDescription>RHEL-09-654010RHEL 9 must audit uses of the "execve" system call.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000326-GPOS-00126, SRG-OS-000327-GPOS-00127</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002233CCI-002234Configure RHEL 9 to audit the execution of the "execve" system call. -+ -+Add or update the following file system rules to "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k execpriv -+-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k execpriv -+-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k execpriv -+-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k execpriv -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "execve" system call with the following command: -+ -+$ sudo auditctl -l | grep execve -+ -+-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k execpriv -+-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k execpriv -+-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k execpriv -+-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k execpriv -+ -+If the command does not return all lines, or the lines are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654015RHEL 9 must audit all uses of the chmod, fchmod, and fchmodat system calls.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210, SRG-OS-000458-GPOS-00203</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chmod", "fchmod", and "fchmodat" syscalls. -+ -+Add or update the following rules in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_mod -+ -+-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chmod", "fchmod", and "fchmodat" system calls with the following command: -+ -+$ sudo auditctl -l | grep chmod -+ -+-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_mod -+ -+If both the "b32" and "b64" audit rules are not defined for the "chmod", "fchmod", and "fchmodat" system calls, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654020RHEL 9 must audit all uses of the chown, fchown, fchownat, and lchown system calls.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chown", "fchown", "fchownat", and "lchown"" system calls. -+ -+Add or update the following rules in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chown", "fchown", "fchownat", and "lchown" system calls with the following command: -+ -+$ sudo auditctl -l | grep chown -+ -+-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_mod -+ -+If both the "b32" and "b64" audit rules are not defined for the "chown", "fchown", "fchownat", and "lchown" system calls, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654025RHEL 9 must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -+ -+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls with the following command: -+ -+$ sudo auditctl -l | grep xattr -+ -+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -+ -+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -+ -+If both the "b32" and "b64" audit rules are not defined for the "chmod", "fchmod", and "fchmodat" system calls "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls, or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654030RHEL 9 must audit all uses of umount system calls.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "umount" command by adding or updating the following rules in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "umount" command with the following command: -+ -+$ sudo auditctl -l | grep umount -+ -+-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount -+ -+If the command does not return an audit rule for "umount" or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654035RHEL 9 must audit all uses of the chacl command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chacl" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chacl" command with the following command: -+ -+$ sudo auditctl -l | grep chacl -+ -+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654040RHEL 9 must audit all uses of the setfacl command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "setfacl" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "setfacl" command with the following command: -+ -+$ sudo auditctl -l | grep setfacl -+ -+-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654045RHEL 9 must audit all uses of the chcon command.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chcon" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chcon" command with the following command: -+ -+$ sudo auditctl -l | grep chcon -+ -+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_mod -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654050RHEL 9 must audit all uses of the semanage command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "semanage" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "semanage" command with the following command: -+ -+$ sudo auditctl -l | grep semanage -+ -+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654055RHEL 9 must audit all uses of the setfiles command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "setfiles" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "setfiles" command with the following command: -+ -+$ sudo auditctl -l | grep setfiles -+ -+-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654060RHEL 9 must audit all uses of the setsebool command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate an audit event for any successful/unsuccessful use of the "setsebool " command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "setsebool" command with the following command: -+ -+$ sudo auditctl -l | grep setsebool -+ -+ -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654065RHEL 9 must audit all uses of the rename, unlink, rmdir, renameat, and unlinkat system calls.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00211, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate an audit event for any successful/unsuccessful use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete -+-a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit successful/unsuccessful attempts to use the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls with the following command: -+ -+$ sudo auditctl -l | grep 'rename\|unlink\|rmdir' -+ -+-a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete -+-a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete -+ -+If the command does not return an audit rule for "rename", "unlink", "rmdir", "renameat", and "unlinkat" or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654070RHEL 9 must audit all uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate an audit event for any successful/unsuccessful use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -+ -+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit successful/unsuccessful attempts to use the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls with the following command: -+ -+$ sudo auditctl -l | grep 'open\|truncate\|creat' -+ -+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -+ -+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -+ -+If the output does not produce rules containing "-F exit=-EPERM", this is a finding. -+ -+If the output does not produce rules containing "-F exit=-EACCES", this is a finding. -+ -+If the command does not return an audit rule for "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654075RHEL 9 must audit all uses of the delete_module system call.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate an audit event for any successful/unsuccessful use of the "delete_module" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -+-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "delete_module" system call with the following command: -+ -+$ sudo auditctl -l | grep delete_module -+ -+-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -+-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -+ -+If both the "b32" and "b64" audit rules are not defined for the "delete_module" system call, or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654080RHEL 9 must audit all uses of the init_module and finit_module system calls.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate an audit event for any successful/unsuccessful use of the "init_module" and "finit_module" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -+-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "init_module" and "finit_module" system calls with the following command: -+ -+$ sudo auditctl -l | grep init_module -+ -+-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -+-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -+ -+If both the "b32" and "b64" audit rules are not defined for the "delete_module" system call, or any of the lines returned are commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654085RHEL 9 must audit all uses of the chage command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chage" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chage" command with the following command: -+ -+$ sudo auditctl -l | grep chage -+ -+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654090RHEL 9 must audit all uses of the chsh command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "chsh" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "chsh" command with the following command: -+ -+$ sudo auditctl -l | grep chsh -+ -+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654095RHEL 9 must audit all uses of the crontab command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "crontab" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "crontab" command with the following command: -+ -+$ sudo auditctl -l | grep crontab -+ -+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654100RHEL 9 must audit all uses of the gpasswd command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "gpasswd" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "gpasswd" command with the following command: -+ -+$ sudo auditctl -l | grep gpasswd -+ -+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654105RHEL 9 must audit all uses of the kmod command.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "kmod" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k modules -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "kmod" command with the following command: -+ -+$ sudo auditctl -l | grep kmod -+ -+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k modules -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654110RHEL 9 must audit all uses of the newgrp command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "newgrp" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "newgrp" command with the following command: -+ -+$ sudo auditctl -l | grep newgrp -+ -+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654115RHEL 9 must audit all uses of the pam_timestamp_check command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "pam_timestamp_check" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "pam_timestamp_check" command with the following command: -+ -+$ sudo auditctl -l | grep timestamp -+ -+-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654120RHEL 9 must audit all uses of the passwd command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "passwd" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command: -+ -+$ sudo auditctl -l | egrep '(/usr/bin/passwd)' -+ -+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654125RHEL 9 must audit all uses of the postdrop command.<VulnDiscussion>Without generating audit records 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "postdrop" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "postdrop" command with the following command: -+ -+$ sudo auditctl -l | grep postdrop -+ -+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654130RHEL 9 must audit all uses of the postqueue command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "postqueue" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "postqueue" command with the following command: -+ -+$ sudo auditctl -l | grep postqueue -+ -+-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654135RHEL 9 must audit all uses of the ssh-agent command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "ssh-agent" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "ssh-agent" command with the following command: -+ -+$ sudo auditctl -l | grep ssh-agent -+ -+-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654140RHEL 9 must audit all uses of the ssh-keysign command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "ssh-keysign" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "ssh-keysign" command with the following command: -+ -+$ sudo auditctl -l | grep ssh-keysign -+ -+-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654145RHEL 9 must audit all uses of the su command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "su" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "su" command with the following command: -+ -+$ sudo auditctl -l | grep /usr/bin/su -+ -+-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654150RHEL 9 must audit all uses of the sudo command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "sudo" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "sudo" command with the following command: -+ -+$ sudo auditctl -l | grep /usr/bin/sudo -+ -+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654155RHEL 9 must audit all uses of the sudoedit command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "sudoedit" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "sudoedit" command with the following command: -+ -+$ sudo auditctl -l | grep /usr/bin/sudoedit -+ -+-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654160RHEL 9 must audit all uses of the unix_chkpwd command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "unix_chkpwd" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "unix_chkpwd" command with the following command: -+ -+$ sudo auditctl -l | grep unix_chkpwd -+ -+-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654165RHEL 9 must audit all uses of the unix_update command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "unix_update" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "unix_update" command with the following command: -+ -+$ sudo auditctl -l | grep unix_update -+ -+-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654170RHEL 9 must audit all uses of the userhelper command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "userhelper" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "userhelper" command with the following command: -+ -+$ sudo auditctl -l | grep userhelper -+ -+-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654175RHEL 9 must audit all uses of the usermod command.<VulnDiscussion>Without generating audit record 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). -+ -+When a user logs on, the auid is set to the uid of the account being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "usermod " command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "usermod" command with the following command: -+ -+$ sudo auditctl -l | grep usermod -+ -+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654180RHEL 9 must audit all uses of the mount command.<VulnDiscussion>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). -+ -+When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way. -+ -+The system call rules are loaded into a matching engine that intercepts each system call made by all programs on the system. Therefore, it is very important to use system call rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining system calls into one rule whenever possible. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records upon successful/unsuccessful attempts to use the "mount" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -+ -+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "mount" command with the following command: -+ -+$ sudo auditctl -l | grep /usr/bin/mount -+ -+-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>RHEL-09-654185Successful/unsuccessful uses of the init command in RHEL 9 must generate an audit record.<VulnDiscussion>Misuse of the init command may cause availability issues for the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "init" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F path=/usr/sbin/init -F perm=x -F auid>=1000 -F auid!=unset -k privileged-init -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "init" command with the following command: -+ -+$ sudo auditctl -l | grep init -+ -+-a always,exit -F path=/usr/sbin/init -F perm=x -F auid>=1000 -F auid!=unset -k privileged-init -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>RHEL-09-654190Successful/unsuccessful uses of the poweroff command in RHEL 9 must generate an audit record.<VulnDiscussion>Misuse of the poweroff command may cause availability issues for the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "poweroff" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F path=/usr/sbin/poweroff -F perm=x -F auid>=1000 -F auid!=unset -k privileged-poweroff -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "poweroff" command with the following command: -+ -+$ sudo auditctl -l | grep poweroff -+ -+-a always,exit -F path=/usr/sbin/poweroff -F perm=x -F auid>=1000 -F auid!=unset -k privileged-poweroff -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>RHEL-09-654195Successful/unsuccessful uses of the reboot command in RHEL 9 must generate an audit record.<VulnDiscussion>Misuse of the reboot command may cause availability issues for the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "reboot" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F path=/usr/sbin/reboot -F perm=x -F auid>=1000 -F auid!=unset -k privileged-reboot -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "reboot" command with the following command: -+ -+$ sudo auditctl -l | grep reboot -+ -+-a always,exit -F path=/usr/sbin/reboot -F perm=x -F auid>=1000 -F auid!=unset -k privileged-reboot -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000477-GPOS-00222<GroupDescription></GroupDescription>RHEL-09-654200Successful/unsuccessful uses of the shutdown command in RHEL 9 must generate an audit record.<VulnDiscussion>Misuse of the shutdown command may cause availability issues for the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "shutdown" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -+ -+-a always,exit -F path=/usr/sbin/shutdown -F perm=x -F auid>=1000 -F auid!=unset -k privileged-shutdown -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 is configured to audit the execution of the "shutdown" command with the following command: -+ -+$ sudo auditctl -l | grep shutdown -+ -+-a always,exit -F path=/usr/sbin/shutdown -F perm=x -F auid>=1000 -F auid!=unset -k privileged-shutdown -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654205Successful/unsuccessful uses of the umount system call in RHEL 9 must generate an audit record.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000169CCI-000172CCI-002884Configure the audit system to generate an audit event for any successful/unsuccessful use of the "umount" system call by adding or updating the following rules in "/etc/audit/audit.rules" and adding the following rules to "/etc/audit/rules.d/perm_mod.rules" or updating the existing rules in files in the "/etc/audit/rules.d/" directory: -+ -+-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b64 -S umount -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.Verify that RHEL 9 generates an audit record for all uses of the "umount" and system call with the following command: -+ -+$ sudo grep "umount" /etc/audit/audit.* -+ -+If the system is configured to audit this activity, it will return a line like the following: -+ -+-a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -k privileged-umount -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654210Successful/unsuccessful uses of the umount2 system call in RHEL 9 must generate an audit record.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000169CCI-000172CCI-002884Configure the audit system to generate an audit event for any successful/unsuccessful use of the "umount2" system call by adding or updating the following rules in "/etc/audit/audit.rules" and adding the following rules to "/etc/audit/rules.d/perm_mod.rules" or updating the existing rules in files in the "/etc/audit/rules.d/" directory: -+ -+-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -k perm_mod -+-a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -k perm_mod -+ -+The audit daemon must be restarted for the changes to take effect.To determine if the system is configured to audit calls to the umount2 system call, run the following command: -+ -+$ sudo grep "umount2" /etc/audit/audit.* -+ -+If the system is configured to audit this activity, it will return a line. -+ -+If no line is returned, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654215RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.<VulnDiscussion>The actions taken by system administrators must 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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/sudoers -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers" with the following command: -+ -+$ sudo auditctl -l | grep /etc/sudoers -+ -+-w /etc/sudoers -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654220RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/ directory.<VulnDiscussion>The actions taken by system administrators must 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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/sudoers.d/ -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/" with the following command: -+ -+$ sudo auditctl -l | grep /etc/sudoers.d -+ -+-w /etc/sudoers.d/ -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654225RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.<VulnDiscussion>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 must be investigated for legitimacy. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/group -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" with the following command: -+ -+$ sudo auditctl -l | egrep '(/etc/group)' -+ -+-w /etc/group -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654230RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/gshadow -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" with the following command: -+ -+$ sudo auditctl -l | egrep '(/etc/gshadow)' -+ -+-w /etc/gshadow -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654235RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/security/opasswd -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" with the following command: -+ -+$ sudo auditctl -l | egrep '(/etc/security/opasswd)' -+ -+-w /etc/security/opasswd -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654240RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221, SRG-OS-000274-GPOS-00104, SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-001683CCI-001684CCI-001685CCI-001686CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/passwd -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" with the following command: -+ -+$ sudo auditctl -l | egrep '(/etc/passwd)' -+ -+-w /etc/passwd -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>RHEL-09-654245RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000304-GPOS-00121, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000470-GPOS-00214, SRG-OS-000471-GPOS-00215, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000018CCI-000130CCI-000135CCI-000169CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130CCI-002132CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /etc/shadow -p wa -k identity -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd with the following command: -+ -+$ sudo auditctl -l | egrep '(/etc/shadow)' -+ -+-w /etc/shadow -p wa -k identity -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>RHEL-09-654250RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/faillock.<VulnDiscussion>Without generating audit records 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. -+ -+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/faillock". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /var/log/faillock -p wa -k logins -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/faillock" with the following command: -+ -+$ sudo auditctl -l | grep /var/log/faillock -+ -+-w /var/log/faillock -p wa -k logins -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>RHEL-09-654255RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/lastlog.<VulnDiscussion>Without generating audit records 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. -+ -+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000130CCI-000135CCI-000169CCI-000172CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /var/log/lastlog -p wa -k logins -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/lastlog" with the following command: -+ -+$ sudo auditctl -l | grep /var/log/lastlog -+ -+-w /var/log/lastlog -p wa -k logins -+ -+If the command does not return a line, or the line is commented out, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>RHEL-09-654260RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/tallylog.<VulnDiscussion>Without generating audit records 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. -+ -+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000172CCI-002884Configure RHEL 9 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/tallylog". -+ -+Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -+ -+-w /var/log/tallylog -p wa -k logins -+ -+The audit daemon must be restarted for the changes to take effect.Verify RHEL 9 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/tallylog" with the following command: -+ -+$ sudo auditctl -l | grep /var/log/tallylog -+ -+-w /var/log/tallylog -p wa -k logins -+ -+If the command does not return a line, or the line is commented out, is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>RHEL-09-654265RHEL 9 must take appropriate action when a critical audit processing failure occurs.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000047-GPOS-00023</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000139CCI-000140Configure RHEL 9 to shut down when auditing failures occur. -+ -+Add the following line to the bottom of the /etc/audit/audit.rules file: -+ -+-f 2Verify the audit service is configured to panic on a critical error with the following command: -+ -+$ sudo grep "\-f" /etc/audit/audit.rules -+ -+-f 2 -+ -+If the value for "-f" is not "2", and availability is not documented as an overriding concern, this is a finding.SRG-OS-000462-GPOS-00206<GroupDescription></GroupDescription>RHEL-09-654270RHEL 9 audit system must protect logon UIDs from unauthorized change.<VulnDiscussion>If modification of login user identifiers (UIDs) is not prevented, they can be changed by nonprivileged users and make auditing complicated or impossible. -+ -+Satisfies: SRG-OS-000462-GPOS-00206, SRG-OS-000475-GPOS-00220, SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000162CCI-000163CCI-000164CCI-000172Configure RHEL 9 auditing to prevent modification of login UIDs once they are set by adding the following line to /etc/audit/rules.d/audit.rules: -+ -+--loginuid-immutable -+ -+The audit daemon must be restarted for the changes to take effect.Verify the audit system prevents unauthorized changes to logon UIDs with the following command: -+ -+$ sudo grep -i immutable /etc/audit/audit.rules -+ -+--loginuid-immutable -+ -+If the "--loginuid-immutable" option is not returned in the "/etc/audit/audit.rules", or the line is commented out, this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>RHEL-09-654275RHEL 9 audit system must protect auditing rules from unauthorized change.<VulnDiscussion>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. -+ -+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 9 system activity. -+ -+In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable, and a system administrator could then investigate the unauthorized changes. -+ -+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000162CCI-000163CCI-000164Configure the audit system to set the audit rules to be immutable by adding the following line to end of "/etc/audit/rules.d/audit.rules" -+ -+-e 2 -+ -+The audit daemon must be restarted for the changes to take effect.Verify the audit system prevents unauthorized changes with the following command: -+ -+$ sudo grep "^\s*[^#]" /etc/audit/audit.rules | tail -1 -+ -+-e 2 -+ -+If the audit system is not set to be immutable by adding the "-e 2" option to the end of "/etc/audit/audit.rules", this is a finding.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>RHEL-09-671010RHEL 9 must enable FIPS mode.<VulnDiscussion>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. This includes NIST FIPS-validated cryptography for the following: Provisioning digital signatures, generating cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. -+ -+Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000125-GPOS-00065, SRG-OS-000396-GPOS-00176, SRG-OS-000423-GPOS-00187, SRG-OS-000478-GPOS-00223</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000068CCI-000877CCI-002418CCI-002450Configure the operating system to implement FIPS mode with the following command -+ -+$ sudo fips-mode-setup --enable -+ -+Reboot the system for the changes to take effect.Verify that RHEL 9 is in FIPS mode with the following command: -+ -+$ sudo fips-mode-setup --check -+ -+FIPS mode is enabled. -+ -+If FIPS mode is not enabled, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-671015RHEL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords.<VulnDiscussion>The system must use a strong hashing algorithm to store the password. -+ -+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. -+ -+Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000120-GPOS-00061</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196CCI-000803Lock all interactive user accounts not using SHA-512 hashing until the passwords can be regenerated with SHA-512.Verify 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.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>RHEL-09-671020RHEL 9 IP tunnels must use FIPS 140-2/140-3 approved cryptographic algorithms.<VulnDiscussion>Overriding the system crypto policy makes the behavior of the Libreswan service violate expectations, and makes system configuration more fragmented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000068Configure Libreswan to use the system cryptographic policy. -+ -+Add the following line to "/etc/ipsec.conf": -+ -+include /etc/crypto-policies/back-ends/libreswan.configVerify that the IPsec service uses the system crypto policy with the following command: -+ -+Note: If the ipsec service is not installed, this requirement is Not Applicable. -+ -+$ sudo grep include /etc/ipsec.conf /etc/ipsec.d/*.conf -+ -+/etc/ipsec.conf:include /etc/crypto-policies/back-ends/libreswan.config -+ -+If the ipsec configuration file does not contain "include /etc/crypto-policies/back-ends/libreswan.config", this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>RHEL-09-671025RHEL 9 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-3 approved cryptographic hashing algorithm for system authentication.<VulnDiscussion>Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and; therefore, cannot be relied upon to provide confidentiality or integrity, and DOD data may be compromised. -+ -+RHEL 9 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. -+ -+FIPS 140-3 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DOD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general-purpose computing system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000196Configure RHEL 9 to use a FIPS 140-3 approved cryptographic hashing algorithm for system authentication. -+ -+Edit/modify the following line in the "/etc/pam.d/password-auth" file to include the sha512 option for pam_unix.so: -+ -+password sufficient pam_unix.so sha512Verify that the pam_unix.so module is configured to use sha512 in /etc/pam.d/password-auth with the following command: -+ -+$ grep "^password.*pam_unix.so.*sha512" /etc/pam.d/password-auth -+ -+password sufficient pam_unix.so sha512 -+ -+If "sha512" is missing, or the line is commented out, this is a finding.SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>RHEL-09-672010RHEL 9 must have the crypto-policies package installed.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002450CCI-002890CCI-003123Install the crypto-policies package (if the package is not already installed) with the following command: -+ -+$ sudo dnf install crypto-policiesVerify that RHEL 9 crypto-policies package is installed with the following command: -+ -+$ sudo dnf list --installed crypto-policies -+ -+Example output: -+ -+crypto-policies.noarch 20220223-1.git5203b41.el9_0.1 -+ -+If the "crypto-policies" package is not installed, this is a finding.SRG-OS-000478-GPOS-00223<GroupDescription></GroupDescription>RHEL-09-672015RHEL 9 crypto policy files must match files shipped with the operating system.<VulnDiscussion>The RHEL 9 package "crypto-policies" defines the cryptography policies for the system. -+ -+If the files are changed from those shipped with the operating system, it may be possible for RHEL 9 to use cryptographic functions that are not FIPS 140-3 approved. -+ -+Satisfies: SRG-OS-000478-GPOS-00223, SRG-OS-000396-GPOS-00176</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002450Reinstall the crypto-policies package to remove any modifications. -+ -+$ sudo dnf reinstall crypto-policiesVerify that the RHEL 9 package "crypto-policies" has not been modified with the following command: -+ -+$ rpm -V crypto-policies -+ -+If the command has any output, this is a finding.SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>RHEL-09-672020RHEL 9 crypto policy must not be overridden.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002450CCI-002890CCI-003123Configure RHEL 9 to FIPS crypto policy. -+ -+$ sudo ln -s /usr/share/crypto-policies/FIPS/<service>.txt /etc/crypto-policies/back-ends/<service>.conf -+ -+Replace <service> with every service that is not set to FIPS. -+ -+The system must be rebooted to make the changes to take effect.Verify that RHEL 9 custom crypto policies are loaded correctly. -+ -+List all of the crypto backends configured on the system. -+ -+$ ls -l /etc/crypto-policies/back-ends/ -+lrwxrwxrwx. 1 root root 40 Oct 7 08:44 bind.config -> /usr/share/crypto-policies/FIPS/bind.txt -+lrwxrwxrwx. 1 root root 42 Oct 7 08:44 gnutls.config -> /usr/share/crypto-policies/FIPS/gnutls.txt -+lrwxrwxrwx. 1 root root 40 Oct 7 08:44 java.config -> /usr/share/crypto-policies/FIPS/java.txt -+lrwxrwxrwx. 1 root root 46 Oct 7 08:44 javasystem.config -> /usr/share/crypto-policies/FIPS/javasystem.txt -+lrwxrwxrwx. 1 root root 40 Oct 7 08:44 krb5.config -> /usr/share/crypto-policies/FIPS/krb5.txt -+lrwxrwxrwx. 1 root root 45 Oct 7 08:44 libreswan.config -> /usr/share/crypto-policies/FIPS/libreswan.txt -+lrwxrwxrwx. 1 root root 42 Oct 7 08:44 libssh.config -> /usr/share/crypto-policies/FIPS/libssh.txt -+lrwxrwxrwx. 1 root root 39 Oct 7 08:44 nss.config -> /usr/share/crypto-policies/FIPS/nss.txt -+lrwxrwxrwx. 1 root root 43 Oct 7 08:44 openssh.config -> /usr/share/crypto-policies/FIPS/openssh.txt -+lrwxrwxrwx. 1 root root 49 Oct 7 08:44 opensshserver.config -> /usr/share/crypto-policies/FIPS/opensshserver.txt -+lrwxrwxrwx. 1 root root 46 Oct 7 08:44 opensslcnf.config -> /usr/share/crypto-policies/FIPS/opensslcnf.txt -+lrwxrwxrwx. 1 root root 43 Oct 7 08:44 openssl.config -> /usr/share/crypto-policies/FIPS/openssl.txt -+ -+If the paths do not point the respective files under /usr/share/crypto-policies/FIPS path, this is a finding.SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>RHEL-09-672025RHEL 9 must use mechanisms meeting the requirements of applicable federal laws, executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.<VulnDiscussion>Overriding the system crypto policy makes the behavior of Kerberos violate expectations, and makes system configuration more fragmented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-000803Configure Kerberos to use system crypto policy. -+ -+Create a symlink pointing to system crypto policy in the Kerberos configuration using the following command: -+ -+$ sudo ln -s /etc/crypto-policies/back-ends/krb5.config /usr/share/crypto-policies/FIPS/krb5.txtVerify that the symlink exists and targets the correct Kerberos crypto policy, with the following command: -+ -+file /etc/crypto-policies/back-ends/krb5.config -+ -+If command output shows the following line, Kerberos is configured to use the system-wide crypto policy: -+ -+/etc/crypto-policies/back-ends/krb5.config: symbolic link to /usr/share/crypto-policies/FIPS/krb5.txt -+ -+If the symlink does not exist or points to a different target, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-672030RHEL 9 must implement DOD-approved TLS encryption in the GnuTLS package.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Transport Layer Security (TLS) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. SQL Server must use a minimum of FIPS 140-3 approved TLS version 1.2, and all non-FIPS-approved SSL and TLS versions must be disabled. NIST 800-53 specifies the preferred configurations for government systems. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000423-GPOS-00187</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453CCI-002418Configure the RHEL 9 GnuTLS library to use only NIST-approved encryption with the following steps to enable FIPS mode: -+ -+$ sudo fips-mode-setup --enable -+ -+A reboot is required for the changes to take effect.Verify if GnuTLS uses defined DOD-approved TLS Crypto Policy with the following command: -+ -+ $ update-crypto-policies --show -+FIPS -+ -+If the system wide crypto policy is not set to "FIPS", this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-672035RHEL 9 must implement DOD-approved encryption in the OpenSSL package.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 OpenSSL library to use the system cryptographic policy. -+ -+Edit the "/etc/pki/tls/openssl.cnf" and add or modify the following line: -+ -+.include = /etc/crypto-policies/back-ends/opensslcnf.configVerify that RHEL 9 OpenSSL library is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command: -+ -+$ sudo grep -i opensslcnf.config /etc/pki/tls/openssl.cnf -+ -+.include = /etc/crypto-policies/back-ends/opensslcnf.config -+ -+If the "opensslcnf.config" is not defined in the "/etc/pki/tls/openssl.cnf" file, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>RHEL-09-672040RHEL 9 must implement DOD-approved TLS encryption in the OpenSSL package.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-001453Configure the RHEL 9 OpenSSL library to use only DOD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file: -+ -+TLS.MinProtocol = TLSv1.2 -+DTLS.MinProtocol = DTLSv1.2 -+ -+A reboot is required for the changes to take effect.Verify that RHEL 9 OpenSSL library is configured to use TLS 1.2 encryption or stronger with following command: -+ -+$ grep -i minprotocol /etc/crypto-policies/back-ends/opensslcnf.config -+ -+TLS.MinProtocol = TLSv1.2 -+DTLS.MinProtocol = DTLSv1.2 -+ -+If the "TLS.MinProtocol" is set to anything older than "TLSv1.2" or the "DTLS.MinProtocol" is set to anything older than "DTLSv1.2", this is a finding.SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>RHEL-09-672045RHEL 9 must implement a system-wide encryption policy.<VulnDiscussion>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. -+ -+Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002450CCI-002890CCI-003123Configure the operating system to implement FIPS mode with the following command -+ -+$ sudo fips-mode-setup --enable -+ -+Reboot the system for the changes to take effect.Verify that the RHEL 9 cryptography policy has been configured correctly with the following commands: -+ -+$ sudo update-crypto-policies --show -+ -+FIPS -+ -+If the cryptography is not set to "FIPS" and is not applied, this is a finding. -+ -+$ sudo update-crypto-policies --check -+ -+The configured policy matches the generated policy -+ -+If the command does not return "The configured policy matches the generated policy", this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>RHEL-09-672050RHEL 9 must implement DOD-approved encryption in the bind package.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. -+ -+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. -+ -+RHEL 9 incorporates system-wide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/ directory. -+ -+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Red Hat Enterprise Linux 9DISADPMS TargetRed Hat Enterprise Linux 95551CCI-002418CCI-002422Configure BIND to use the system crypto policy. -+ -+Add the following line to the "options" section in "/etc/named.conf": -+ -+include "/etc/crypto-policies/back-ends/bind.config";Verify that BIND uses the system crypto policy with the following command: -+ -+Note: If the "bind" package is not installed, this requirement is Not Applicable. -+ -+$ sudo grep include /etc/named.conf -+ -+include "/etc/crypto-policies/back-ends/bind.config";' -+ -+If BIND is installed and the BIND config file doesn't contain the include "/etc/crypto-policies/back-ends/bind.config" directive, or the line is commented out, this is a finding. -\ No newline at end of file -diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt -index 89b3909b74..0b93a14ec5 100644 ---- a/tests/CMakeLists.txt -+++ b/tests/CMakeLists.txt -@@ -283,15 +283,37 @@ if(PYTHON_VERSION_MAJOR GREATER 2 AND PYTHON_VERSION_MINOR GREATER 6) - endif() - - macro(ssg_refcheck_test PRODUCT PROFILE KEY) -- add_test( -+ # If you pass comma separated list as the fourth argument those rules will be excluded from the check. -+ set(extra_args ${ARGN}) -+ list(LENGTH extra_args extra_args_length) -+ if(${extra_args_length} EQUAL 1) -+ list(GET extra_args 0 excludes) -+ add_test( -+ NAME "refchecker-${PRODUCT}-${PROFILE}" -+ COMMAND env "PYTHONPATH=$ENV{PYTHONPATH}" "${PYTHON_EXECUTABLE}" "${CMAKE_SOURCE_DIR}/utils/refchecker.py" --json "${CMAKE_SOURCE_DIR}/build/rule_dirs.json" --build-config-yaml "${CMAKE_BINARY_DIR}/build_config.yml" "--exclude" "${excludes}" "${PRODUCT}" "${PROFILE}" "${KEY}" -+ ) -+ else() -+ add_test( - NAME "refchecker-${PRODUCT}-${PROFILE}" - COMMAND env "PYTHONPATH=$ENV{PYTHONPATH}" "${PYTHON_EXECUTABLE}" "${CMAKE_SOURCE_DIR}/utils/refchecker.py" --json "${CMAKE_SOURCE_DIR}/build/rule_dirs.json" --build-config-yaml "${CMAKE_BINARY_DIR}/build_config.yml" "${PRODUCT}" "${PROFILE}" "${KEY}" -- ) -+ ) -+ endif() - set_tests_properties("refchecker-${PRODUCT}-${PROFILE}" PROPERTIES FIXTURES_REQUIRED "rule-dir-json") - set_tests_properties("refchecker-${PRODUCT}-${PROFILE}" PROPERTIES DEPENDS "test-rule-dir-json") - set_tests_properties("refchecker-${PRODUCT}-${PROFILE}" PROPERTIES LABELS quick) - endmacro() - -+if(PYTHON_VERSION_MAJOR GREATER 2 AND SSG_PRODUCT_RHEL9) -+ ssg_refcheck_test("rhel9" "cis_workstation_l1" "cis") -+ ssg_refcheck_test("rhel9" "cis_workstation_l2" "cis") -+ ssg_refcheck_test("rhel9" "cis_server_l1" "cis") -+ ssg_refcheck_test("rhel9" "cis" "cis") -+ ssg_refcheck_test("rhel9" "ccn_basic" "ccn") -+ ssg_refcheck_test("rhel9" "ccn_advanced" "ccn") -+ # This exclude can be removed once enable_authselect has a stigid -+ ssg_refcheck_test("rhel9" "stig" "stigid" "enable_authselect") -+endif() -+ - if(PYTHON_VERSION_MAJOR GREATER 2 AND SSG_PRODUCT_RHEL8) - ssg_refcheck_test("rhel8" "cis_workstation_l1" "cis") - ssg_refcheck_test("rhel8" "cis_workstation_l2" "cis") -@@ -335,6 +357,7 @@ if(SSG_PRODUCT_RHEL8) - endif() - if(SSG_PRODUCT_RHEL9) - ssg_controlrefcheck_test("rhel9" "cis_rhel9" "cis") -+ ssg_controlrefcheck_test("rhel9" "stig_rhel9" "stigid") - endif() - - -diff --git a/utils/controlrefcheck.py b/utils/controlrefcheck.py -index f955b02230..33a0853e5e 100755 ---- a/utils/controlrefcheck.py -+++ b/utils/controlrefcheck.py -@@ -80,6 +80,10 @@ def get_controls_env(args): - return controls_manager, env_yaml - - -+def check_stig(reference: str, control_id: str) -> bool: -+ return reference == 'stigid' and not re.match(r'(\w){4}-\w{2}-\d{6}', control_id) -+ -+ - def check_cis(reference: str, control_id: str) -> bool: - return reference == 'cis' and not re.match(r"\d(\.\d+){0,3}", control_id) - -@@ -88,6 +92,9 @@ def should_rule_be_checked(reference: str, control_id: str) -> bool: - if check_cis(reference, control_id): - print(f'Skipping {control_id} as it does not match a CIS id.') - return False -+ if check_stig(reference, control_id): -+ print(f'Skipping {control_id} as it does not match a STIG id.') -+ return False - return True - - -diff --git a/utils/refchecker.py b/utils/refchecker.py -index 4ae789d02a..d3cec5a9b7 100755 ---- a/utils/refchecker.py -+++ b/utils/refchecker.py -@@ -36,10 +36,13 @@ def parse_args(): - help="Directory that contains control files with policy controls.") - parser.add_argument("-p", "--profiles-root", - help="Override where to look for profile files.") -- parser.add_argument("product", type=str, help="Product to check has required references") -+ parser.add_argument("product", type=str, -+ help="Product to check has required references") - parser.add_argument("profile", type=str, help="Profile to iterate over") -- parser.add_argument("reference", type=str, help="Required reference system to check for") -- -+ parser.add_argument("reference", type=str, -+ help="Required reference system to check for") -+ parser.add_argument("--exclude", "-e", type=str, -+ help="A comma separated list of rules to be ignored") - return parser.parse_args() - - -@@ -64,20 +67,37 @@ def load_for_product(rule_obj, product, env_yaml=None): - return rule - - --def reference_check(env_yaml, rule_dirs, profile_path, product, product_yaml, reference, -- profiles_root, controls_manager=None): -- profile = ssg.build_yaml.ProfileWithInlinePolicies.from_yaml(profile_path, env_yaml) -+def _process_controls_manager(controls_manager, env_yaml, product_yaml, profile, rule_dirs): - product_cpes = ProductCPEs() - product_cpes.load_product_cpes(env_yaml) - product_cpes.load_content_cpes(env_yaml) -- - if controls_manager: - profile_files = ssg.products.get_profile_files_from_root(env_yaml, product_yaml) - all_profiles = ssg.build_profile.make_name_to_profile_mapping(profile_files, env_yaml, - product_cpes) - profile.resolve(all_profiles, rule_dirs, controls_manager) - -+ -+def _process_excludes(excludes): -+ if not excludes or excludes == '': -+ return list() -+ result = list() -+ if ',' not in excludes: -+ result.append(excludes) -+ return result -+ for item in excludes.split(','): -+ result.append(item.strip()) -+ return result -+ -+ -+def reference_check(env_yaml, rule_dirs, profile_path, product, product_yaml, reference, -+ excludes, controls_manager=None): -+ profile = ssg.build_yaml.ProfileWithInlinePolicies.from_yaml(profile_path, env_yaml) -+ _process_controls_manager(controls_manager, env_yaml, product_yaml, profile, rule_dirs) -+ - ok = True -+ processed_excludes = _process_excludes(excludes) -+ - for rule_id in profile.selected + profile.unselected: - if rule_id not in rule_dirs: - msg = "Unable to find rule in rule_dirs.json: {0}" -@@ -86,6 +106,9 @@ def reference_check(env_yaml, rule_dirs, profile_path, product, product_yaml, re - - rule = load_for_product(rule_dirs[rule_id], product, env_yaml=env_yaml) - -+ if rule_id in processed_excludes: -+ continue -+ - if reference not in rule.references: - ok = False - msg = "Rule {0} lacks required reference {1} or {1}@{2}" -@@ -132,7 +155,7 @@ def main(): - raise ValueError(msg) - - ok = reference_check(env_yaml, all_rules, profile_path, args.product, product_yaml, -- args.reference, profiles_root, controls_manager) -+ args.reference, args.exclude, controls_manager) - if not ok: - sys.exit(1) - --- -2.43.0 - diff --git a/scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch b/scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch deleted file mode 100644 index 88afb22..0000000 --- a/scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch +++ /dev/null @@ -1,26 +0,0 @@ -From eb4cedf1097bb556134a03648a99c60b16fa4726 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:22:29 +0100 -Subject: [PATCH 12/14] Add SRG id to `file_owner_grub2_cfg` for RHEL 9 STIG - -Patch-name: scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch -Patch-status: Add SRG id to `file_owner_grub2_cfg` for RHEL 9 STIG ---- - .../bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml | 1 + - 1 file changed, 1 insertion(+) - -diff --git a/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -index fef91a47df..3df07a5689 100644 ---- a/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/non-uefi/file_owner_grub2_cfg/rule.yml -@@ -45,6 +45,7 @@ references: - nist-csf: PR.AC-4,PR.DS-5 - pcidss: Req-7.1 - pcidss4: "2.2.6" -+ srg: SRG-OS-000480-GPOS-00227 - stigid@rhel9: RHEL-09-212030 - - ocil_clause: '{{{ ocil_clause_file_owner(file=grub2_boot_path ~ "/grub.cfg", owner="root") }}}' --- -2.43.0 - diff --git a/scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch b/scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch deleted file mode 100644 index 4e3a0ad..0000000 --- a/scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch +++ /dev/null @@ -1,26 +0,0 @@ -From 89c7d9f8e9837383047b036c9a42a9986590f307 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:22:29 +0100 -Subject: [PATCH 11/14] Add var_networkmanager_dns_mode to RHEL 9 STIG - -Patch-name: scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch -Patch-status: Add var_networkmanager_dns_mode to RHEL 9 STIG ---- - controls/stig_rhel9.yml | 1 + - 1 file changed, 1 insertion(+) - -diff --git a/controls/stig_rhel9.yml b/controls/stig_rhel9.yml -index 0966ebb6fc..b576ba08c3 100644 ---- a/controls/stig_rhel9.yml -+++ b/controls/stig_rhel9.yml -@@ -1516,6 +1516,7 @@ controls: - title: RHEL 9 must configure a DNS processing mode set be Network Manager. - rules: - - networkmanager_dns_mode -+ - var_networkmanager_dns_mode=none - status: automated - - - id: RHEL-09-252045 --- -2.43.0 - diff --git a/scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch b/scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch deleted file mode 100644 index 5942c0c..0000000 --- a/scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch +++ /dev/null @@ -1,294 +0,0 @@ -From 6f11431ae6ff21170b11e6777141cbe33a8ffe42 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:05:37 +0100 -Subject: [PATCH 08/14] New Rule networkmanager_dns_mode - -Patch-name: scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch -Patch-status: New Rule networkmanager_dns_mode ---- - components/networkmanager.yml | 5 +++ - .../srg_gpos/SRG-OS-000480-GPOS-00227.yml | 4 +++ - .../system/network/networkmanager/group.yml | 7 ++++ - .../ansible/shared.yml | 14 ++++++++ - .../networkmanager_dns_mode/bash/shared.sh | 11 ++++++ - .../networkmanager_dns_mode/oval/shared.xml | 12 +++++++ - .../policy/stig/shared.yml | 15 ++++++++ - .../networkmanager_dns_mode/rule.yml | 34 +++++++++++++++++++ - .../tests/correct.pass.sh | 8 +++++ - .../tests/correct_default.pass.sh | 8 +++++ - .../tests/missing.fail.sh | 4 +++ - .../tests/wrong_value.fail.sh | 8 +++++ - .../var_networkmanager_dns_mode.var | 19 +++++++++++ - shared/applicability/package.yml | 2 ++ - shared/references/cce-redhat-avail.txt | 1 - - 15 files changed, 151 insertions(+), 1 deletion(-) - create mode 100644 components/networkmanager.yml - create mode 100644 linux_os/guide/system/network/networkmanager/group.yml - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/ansible/shared.yml - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/bash/shared.sh - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/oval/shared.xml - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/policy/stig/shared.yml - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct.pass.sh - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct_default.pass.sh - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/missing.fail.sh - create mode 100644 linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/wrong_value.fail.sh - create mode 100644 linux_os/guide/system/network/networkmanager/var_networkmanager_dns_mode.var - -diff --git a/components/networkmanager.yml b/components/networkmanager.yml -new file mode 100644 -index 0000000000..75d54b9490 ---- /dev/null -+++ b/components/networkmanager.yml -@@ -0,0 +1,5 @@ -+name: NetworkManager -+packages: -+- NetworkManager -+rules: -+- networkmanager_dns_mode -diff --git a/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml b/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -index 1aceb0b187..be60a154c1 100644 ---- a/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -+++ b/controls/srg_gpos/SRG-OS-000480-GPOS-00227.yml -@@ -225,6 +225,10 @@ controls: - - set_firewalld_default_zone - - firewalld_sshd_port_enabled - -+ # NetworkManger -+ - networkmanager_dns_mode -+ - var_networkmanager_dns_mode=none -+ - # misc - - enable_authselect - - no_host_based_files -diff --git a/linux_os/guide/system/network/networkmanager/group.yml b/linux_os/guide/system/network/networkmanager/group.yml -new file mode 100644 -index 0000000000..4abf48ed96 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/group.yml -@@ -0,0 +1,7 @@ -+documentation_complete: true -+ -+title: 'Network Manager' -+ -+description: |- -+ The NetworkManager daemon configures a variety of network connections. -+ This section discusses how to configure NetworkManager. -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/ansible/shared.yml b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/ansible/shared.yml -new file mode 100644 -index 0000000000..b416038bd9 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/ansible/shared.yml -@@ -0,0 +1,14 @@ -+# platform = multi_platform_all -+# reboot = false -+# strategy = configure -+# complexity = low -+# disruption = low -+ -+{{{ ansible_instantiate_variables("var_networkmanager_dns_mode") }}} -+ -+{{{ ansible_ini_file_set("/etc/NetworkManager/NetworkManager.conf", "main", "dns", "{{ var_networkmanager_dns_mode }}") }}} -+ -+- name: "{{{ rule_title }}} - Ensure Network Manager" -+ ansible.builtin.systemd: -+ name: NetworkManager -+ state: reloaded -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/bash/shared.sh b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/bash/shared.sh -new file mode 100644 -index 0000000000..88491d288d ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/bash/shared.sh -@@ -0,0 +1,11 @@ -+# platform = multi_platform_all -+# reboot = false -+# strategy = configure -+# complexity = low -+# disruption = medium -+ -+{{{ bash_instantiate_variables("var_networkmanager_dns_mode") }}} -+ -+{{{ bash_ini_file_set("/etc/NetworkManager/NetworkManager.conf", "main", "dns", "$var_networkmanager_dns_mode") }}} -+ -+systemctl reload NetworkManager -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/oval/shared.xml b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/oval/shared.xml -new file mode 100644 -index 0000000000..cb07c9a9ed ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/oval/shared.xml -@@ -0,0 +1,12 @@ -+{{{ -+oval_check_ini_file( -+ path="/etc/NetworkManager/NetworkManager.conf", -+ section="main", -+ parameter="dns", -+ value="default|none", -+ missing_parameter_pass=false, -+ application="NetworkManager", -+ multi_value=false, -+ missing_config_file_fail=true -+) -+}}} -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/policy/stig/shared.yml b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/policy/stig/shared.yml -new file mode 100644 -index 0000000000..b644587b41 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/policy/stig/shared.yml -@@ -0,0 +1,15 @@ -+checktext: |- -+ [main] -+ dns=none -+ -+ If the dns key under main does not exist or is not set to "none" or "default", this is a finding. -+ -+fixtext: |- -+ Configure NetworkManager in RHEL 9 to use a DNS mode. -+ -+ In "/etc/NetworkManager/NetworkManager.conf" add the following line in the "[main]" section: -+ -+ dns = none -+ -+srg_requirement: |- -+ {{ full_name }} must configure a DNS processing mode set be Network Manager. -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml -new file mode 100644 -index 0000000000..8b703cb2f1 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/rule.yml -@@ -0,0 +1,34 @@ -+documentation_complete: true -+ -+prodtype: rhel9 -+ -+title: 'NetworkManager DNS Mode Must Be Must Configured' -+ -+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. -+ -+severity: medium -+ -+identifiers: -+ cce@rhel9: CCE-86805-9 -+ -+references: -+ disa: CCI-000366 -+ nist: CM-6(b) -+ srg: SRG-OS-000480-GPOS-00227 -+ -+ocil_clause: 'the dns key under main does not exist or is not set to "none" or "default"' -+ -+ -+ocil: |- -+ Verify that {{{ full_name }}} has a DNS mode configured in Network Manager. -+ -+ $ NetworkManager --print-config -+ [main] -+ dns={{{ xccdf_value("var_networkmanager_dns_mode") }}} -+ -+platform: package[NetworkManager] -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct.pass.sh b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct.pass.sh -new file mode 100644 -index 0000000000..7af3e14fc3 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct.pass.sh -@@ -0,0 +1,8 @@ -+#!/bin/bash -+# variables = var_networkmanager_dns_mode = none -+# packages = NetworkManager -+ -+cat > /etc/NetworkManager/NetworkManager.conf << EOM -+[main] -+dns=none -+EOM -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct_default.pass.sh b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct_default.pass.sh -new file mode 100644 -index 0000000000..a19040e2d5 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/correct_default.pass.sh -@@ -0,0 +1,8 @@ -+#!/bin/bash -+# variables = var_networkmanager_dns_mode = default -+# packages = NetworkManager -+ -+cat > /etc/NetworkManager/NetworkManager.conf << EOM -+[main] -+dns=default -+EOM -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/missing.fail.sh b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/missing.fail.sh -new file mode 100644 -index 0000000000..b81d82c807 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/missing.fail.sh -@@ -0,0 +1,4 @@ -+#!/bin/bash -+# variables = var_networkmanager_dns_mode = default -+ -+sed '/^dns=.*$/d' /etc/NetworkManager/NetworkManager.conf -diff --git a/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/wrong_value.fail.sh b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/wrong_value.fail.sh -new file mode 100644 -index 0000000000..6de904b372 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/networkmanager_dns_mode/tests/wrong_value.fail.sh -@@ -0,0 +1,8 @@ -+#!/bin/bash -+# variables = var_networkmanager_dns_mode = default -+# packages = NetworkManager -+ -+cat > /etc/NetworkManager/NetworkManager.conf << EOM -+[main] -+dns=dnsmasq -+EOM -diff --git a/linux_os/guide/system/network/networkmanager/var_networkmanager_dns_mode.var b/linux_os/guide/system/network/networkmanager/var_networkmanager_dns_mode.var -new file mode 100644 -index 0000000000..1be615dff9 ---- /dev/null -+++ b/linux_os/guide/system/network/networkmanager/var_networkmanager_dns_mode.var -@@ -0,0 +1,19 @@ -+documentation_complete: true -+ -+title: 'NetoworkManager DNS Mode' -+ -+type: string -+ -+description: |- -+ This sets how NetworkManager handles DNS. -+ -+ none - NetworkManager will not modify resolv.conf. -+ default - NetworkManager will update /etc/resolv.conf to reflect the nameservers provided by currently active connections. -+ -+interactive: true -+ -+operator: 'equals' -+ -+options: -+ none: none -+ default: default -diff --git a/shared/applicability/package.yml b/shared/applicability/package.yml -index ee52a50f1f..4718c7cf71 100644 ---- a/shared/applicability/package.yml -+++ b/shared/applicability/package.yml -@@ -87,3 +87,5 @@ args: - pkgname: zypper - openssh: - pkgname: openssh -+ networkmanager: -+ pkgname: NetworkManager -diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt -index 538d9d488d..60663b117a 100644 ---- a/shared/references/cce-redhat-avail.txt -+++ b/shared/references/cce-redhat-avail.txt -@@ -459,7 +459,6 @@ CCE-86799-4 - CCE-86802-6 - CCE-86803-4 - CCE-86804-2 --CCE-86805-9 - CCE-86806-7 - CCE-86807-5 - CCE-86808-3 --- -2.43.0 - diff --git a/scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch b/scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch deleted file mode 100644 index 0c45ea7..0000000 --- a/scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch +++ /dev/null @@ -1,67 +0,0 @@ -From 9062da533315a871939f3c22d4154e1f4141d432 Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= -Date: Tue, 5 Dec 2023 16:22:30 +0100 -Subject: [PATCH 13/14] Minor modifications to RHEL STIG profiles - -Patch-name: scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch -Patch-status: Minor modifications to RHEL STIG profiles ---- - controls/stig_rhel9.yml | 2 +- - .../password_quality/passwd_system-auth_substack/rule.yml | 1 - - .../audit_rules_immutable_login_uids/rule.yml | 1 + - .../auditing/policy_rules/audit_immutable_login_uids/rule.yml | 2 -- - 4 files changed, 2 insertions(+), 4 deletions(-) - -diff --git a/controls/stig_rhel9.yml b/controls/stig_rhel9.yml -index b576ba08c3..73d9e9e1aa 100644 ---- a/controls/stig_rhel9.yml -+++ b/controls/stig_rhel9.yml -@@ -4114,7 +4114,7 @@ controls: - - medium - title: RHEL 9 audit system must protect logon UIDs from unauthorized change. - rules: -- - audit_immutable_login_uids -+ - audit_rules_immutable_login_uids - status: automated - - - id: RHEL-09-654275 -diff --git a/linux_os/guide/system/accounts/accounts-pam/password_quality/passwd_system-auth_substack/rule.yml b/linux_os/guide/system/accounts/accounts-pam/password_quality/passwd_system-auth_substack/rule.yml -index 89b82af3f2..55d3e47a54 100644 ---- a/linux_os/guide/system/accounts/accounts-pam/password_quality/passwd_system-auth_substack/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-pam/password_quality/passwd_system-auth_substack/rule.yml -@@ -19,7 +19,6 @@ references: - nist: IA-5(1)(a),IA-5(1).1(v),IA-5(1)(a) - srg: SRG-OS-000069-GPOS-00037 - stigid@ol7: OL07-00-010118 -- stigid@rhel7: RHEL-07-010118 - - ocil_clause: '/etc/pam.d/passwd does not implement /etc/pam.d/system-auth' - -diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable_login_uids/rule.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable_login_uids/rule.yml -index 46e249efbb..6a8ea53fc5 100644 ---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable_login_uids/rule.yml -+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable_login_uids/rule.yml -@@ -33,6 +33,7 @@ references: - disa: CCI-000162,CCI-000163,CCI-000164 - srg: SRG-OS-000462-GPOS-00206,SRG-OS-000475-GPOS-00220,SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029 - stigid@rhel8: RHEL-08-030122 -+ stigid@rhel9: RHEL-09-654270 - - ocil_clause: 'the system is not configured to make login UIDs immutable' - -diff --git a/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml b/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -index 9f2f7dbc11..dbf1015a19 100644 ---- a/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -+++ b/linux_os/guide/system/auditing/policy_rules/audit_immutable_login_uids/rule.yml -@@ -35,8 +35,6 @@ references: - ospp: FAU_GEN.1.2 - srg: SRG-OS-000462-GPOS-00206,SRG-OS-000475-GPOS-00220,SRG-OS-000057-GPOS-00027,SRG-OS-000058-GPOS-00028,SRG-OS-000059-GPOS-00029 - stigid@ol8: OL08-00-030122 -- stigid@rhel8: RHEL-08-030122 -- stigid@rhel9: RHEL-09-654270 - - ocil_clause: 'the file does not exist or the content differs' - --- -2.43.0 - diff --git a/scap-security-guide.spec b/scap-security-guide.spec index 52c9edd..fb9cacd 100644 --- a/scap-security-guide.spec +++ b/scap-security-guide.spec @@ -5,39 +5,12 @@ # global _default_patch_fuzz 2 # Normally shouldn't be needed as patches should apply cleanly Name: scap-security-guide -Version: 0.1.69 -Release: 3%{?dist} +Version: 0.1.72 +Release: 1%{?dist} Summary: Security guidance and baselines in SCAP formats License: BSD-3-Clause URL: https://github.com/ComplianceAsCode/content/ Source0: https://github.com/ComplianceAsCode/content/releases/download/v%{version}/scap-security-guide-%{version}.tar.bz2 -# Fix rule enable_fips_mode -Patch1: scap-security-guide-0.1.70-improve_readability_enable_fips_mode-PR_10911.patch -Patch2: scap-security-guide-0.1.70-fix_enable_fips_mode-PR_10961.patch -# remove rules harden_sshd_(macs/ciphers)_openssh_conf_crypto_policy from STIG profile -Patch3: scap-security-guide-0.1.70-remove_openssh_hardening_stig-PR_10996.patch -# remove rule sebool_secure_mode_insmod from ANSSI high profile because it prevents UEFI-based systems from booting -Patch4: scap-security-guide-0.1.70-remove_secure_mode_insmod_anssi-PR_11001.patch -# Update sshd_approved_ciphers value for RHEL in STIG profile -Patch5: scap-security-guide-0.1.70-sshd_approved_ciphers_stig-PR_10966.patch -# Add rule `package_s-nail-installed` -Patch6: scap-security-guide-0.1.70-add_package_smail_installed-PR_11144.patch -# New Rule networkmanager_dns_mode -Patch7: scap-security-guide-0.1.71-new_rule_dns_mode_nm-PR_11160.patch -# Add cron.deny Owership Rules -Patch8: scap-security-guide-0.1.71-add_cron_deny_rules-PR_11185.patch -# Add RHEL 9 STIG -Patch9: scap-security-guide-0.1.71-add_rhel9_stig-PR_11193.patch -# Add var_networkmanager_dns_mode to RHEL 9 STIG -Patch10: scap-security-guide-0.1.71-fix_var_networkmanager_dns_mode_rhel9_stig-PR_11242.patch -# Add SRG id to `file_owner_grub2_cfg` for RHEL 9 STIG -Patch11: scap-security-guide-0.1.71-add_srg_to_file_owner_grub2_cfg-PR_11261.patch -# Minor modifications to RHEL STIG profiles -Patch12: scap-security-guide-0.1.72-remove_stig_ids-PR_11327.patch -# Add variable support to `auditd_name_format` rule -Patch13: scap-security-guide-0.1.70-name_format_variable-PR_11019.patch -# Update ssh stig HMACS and Ciphers allowed in OL8 STIG -Patch14: scap-security-guide-0.1.70-update_ssh_stig_algos-PR_10920.patch BuildArch: noarch BuildRequires: libxslt @@ -125,6 +98,15 @@ rm %{buildroot}/%{_docdir}/%{name}/Contributors.md %endif %changelog +* Tue Feb 13 2024 Marcus Burghardt - 0.1.72-1 +- Rebase to a new upstream release 0.1.72 (RHEL-21425) +- Check dropin files in /etc/systemd/journald.conf.d/ (RHEL-14484) +- Fix remediation to not update comments (RHEL-1484) +- Fix package check on SCAP tests for dnf settings (RHEL-17417) +- Update description for audit_rules_kernel_module_loading (RHEL-1489) +- Disable remediation for /dev/shm options in offline mode (RHEL-16801) +- Include explanatory comment in the remediation of CCE-83871-4 (RHEL-17418) + * Tue Dec 05 2023 Jan Černý - 0.1.69-3 - Align STIG profile with official DISA STIG for RHEL 9 (RHEL-1807) diff --git a/sources b/sources index b00e054..5ef0e99 100644 --- a/sources +++ b/sources @@ -1 +1 @@ -SHA512 (scap-security-guide-0.1.69.tar.bz2) = 224d308608c1254a74290f2967f39ba0cef2df199399d70cb1b90386836bb1da313bf699e488d15a308c0a6ea70c30a8f5cc4a6c0b58a863f2f8154f022dd7bb +SHA512 (scap-security-guide-0.1.72.tar.bz2) = 2b3fb7ff4d7f69796968afc61049753bce9f2cd5bc57ecc41f9ea17dbd2bb8c278a6e02ef98e34b1561dd38e55498ba2ba92079dbdc4ef5848186964cefbd92a