| Finding ID |
Severity |
Title |
Description |
|
V-258236
|
High |
RHEL 9 cryptographic policy must not be overridden. |
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 using encryption to protect data.
Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174 |
|
V-258230
|
High |
RHEL 9 must enable FIPS mode. |
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... |
|
V-258094
|
High |
RHEL 9 must not allow blank or null passwords. |
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. |
|
V-258078
|
High |
RHEL 9 must use a Linux Security Module configured to enforce limits on system services. |
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... |
|
V-258059
|
High |
The root account must be the only account having unrestricted access to RHEL 9 system. |
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... |
|
V-258018
|
High |
RHEL 9 must not allow unattended or automatic logon via the graphical user interface. |
Failure to restrict system access to authenticated users negatively impacts operating system security. |
|
V-257986
|
High |
RHEL 9 must enable the Pluggable Authentication Module (PAM) interface for SSHD. |
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... |
|
V-257984
|
High |
RHEL 9 SSHD must not allow blank passwords. |
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 |
|
V-257956
|
High |
There must be no .shosts files on RHEL 9. |
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. |
|
V-257955
|
High |
There must be no shosts.equiv files on RHEL 9. |
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. |
|
V-257879
|
High |
RHEL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. |
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... |
|
V-257835
|
High |
RHEL 9 must not have a Trivial File Transfer Protocol (TFTP) server package installed. |
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... |
|
V-257826
|
High |
RHEL 9 must not have a File Transfer Protocol (FTP) server package installed. |
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... |
|
V-257822
|
High |
RHEL 9 must have GPG signature verification enabled for all software repositories. |
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... |
|
V-257821
|
High |
RHEL 9 must check the GPG signature of locally installed software packages before installation. |
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... |
|
V-257820
|
High |
RHEL 9 must check the GPG signature of software packages originating from external software repositories before installation. |
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... |
|
V-257789
|
High |
RHEL 9 must require a unique superusers name upon booting into single-user and maintenance modes. |
Having a nondefault grub superuser username makes password-guessing attacks less effective. |
|
V-257785
|
High |
The x86 Ctrl-Alt-Delete key sequence must be disabled on RHEL 9. |
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,... |
|
V-257784
|
High |
The systemd Ctrl-Alt-Delete burst key sequence in RHEL 9 must be disabled. |
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,... |
|
V-257777
|
High |
RHEL 9 must be a vendor-supported release. |
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... |
|
V-270180
|
Medium |
The RHEL 9 fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
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 allow listing.
Using an allow list provides a configuration management method for allowing the execution of... |
|
V-270178
|
Medium |
The RHEL 9 SSH client must be configured to use only DOD-approved Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. |
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... |
|
V-270177
|
Medium |
The RHEL 9 SSH client must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. |
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... |
|
V-270176
|
Medium |
RHEL 9 "/etc/audit/" must be group-owned by root. |
The "/etc/audit/" directory contains files that ensure the proper auditing of command execution, privilege escalation, file manipulation, and more. Protection of this directory is critical for system security. |
|
V-270175
|
Medium |
RHEL 9 "/etc/audit/" must be owned by root. |
The "/etc/audit/" directory contains files that ensure the proper auditing of command execution, privilege escalation, file manipulation, and more. Protection of this directory is critical for system security. |
|
V-270174
|
Medium |
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. |
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 logon interfaces with human users... |
|
V-258242
|
Medium |
RHEL 9 must implement DOD-approved encryption in the bind package. |
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... |
|
V-258241
|
Medium |
RHEL 9 must implement a FIPS 140-3 compliant systemwide cryptographic policy. |
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 using encryption to protect data.
Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174 |
|
V-258237
|
Medium |
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. |
Overriding the system crypto policy makes the behavior of Kerberos violate expectations and makes system configuration more fragmented. |
|
V-258234
|
Medium |
RHEL 9 must have the crypto-policies package installed. |
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 using encryption to protect data.
Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174 |
|
V-258233
|
Medium |
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. |
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... |
|
V-258232
|
Medium |
RHEL 9 IP tunnels must use FIPS 140-3 approved cryptographic algorithms. |
Overriding the system crypto policy makes the behavior of the Libreswan service violate expectations, and makes system configuration more fragmented. |
|
V-258231
|
Medium |
RHEL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords. |
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 |
|
V-258229
|
Medium |
RHEL 9 audit system must protect auditing rules from unauthorized change. |
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... |
|
V-258228
|
Medium |
RHEL 9 audit system must protect logon UIDs from unauthorized change. |
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 |
|
V-258227
|
Medium |
RHEL 9 must take appropriate action when a critical audit processing failure occurs. |
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... |
|
V-258226
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/tallylog. |
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 |
|
V-258225
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/lastlog. |
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 |
|
V-258224
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/faillock. |
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 |
|
V-258223
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. |
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 |
|
V-258222
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. |
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 |
|
V-258221
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd. |
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 |
|
V-258220
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. |
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 |
|
V-258219
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. |
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 |
|
V-258218
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/ directory. |
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... |
|
V-258217
|
Medium |
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers. |
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... |
|
V-258216
|
Medium |
Successful/unsuccessful uses of the umount2 system call in RHEL 9 must generate an audit record. |
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 |
|
V-258215
|
Medium |
Successful/unsuccessful uses of the umount system call in RHEL 9 must generate an audit record. |
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 |
|
V-258214
|
Medium |
Successful/unsuccessful uses of the shutdown command in RHEL 9 must generate an audit record. |
Misuse of the shutdown command may cause availability issues for the system. |
|
V-258213
|
Medium |
Successful/unsuccessful uses of the reboot command in RHEL 9 must generate an audit record. |
Misuse of the reboot command may cause availability issues for the system. |
|
V-258212
|
Medium |
Successful/unsuccessful uses of the poweroff command in RHEL 9 must generate an audit record. |
Misuse of the poweroff command may cause availability issues for the system. |
|
V-258211
|
Medium |
Successful/unsuccessful uses of the init command in RHEL 9 must generate an audit record. |
Misuse of the init command may cause availability issues for the system. |
|
V-258210
|
Medium |
RHEL 9 must audit all uses of the mount command. |
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.,... |
|
V-258209
|
Medium |
RHEL 9 must audit all uses of the usermod command. |
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... |
|
V-258208
|
Medium |
RHEL 9 must audit all uses of the userhelper command. |
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... |
|
V-258207
|
Medium |
RHEL 9 must audit all uses of the unix_update command. |
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... |
|
V-258206
|
Medium |
RHEL 9 must audit all uses of the unix_chkpwd command. |
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... |
|
V-258205
|
Medium |
RHEL 9 must audit all uses of the sudoedit command. |
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... |
|
V-258204
|
Medium |
RHEL 9 must audit all uses of the sudo command. |
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... |
|
V-258203
|
Medium |
RHEL 9 must audit all uses of the su command. |
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... |
|
V-258202
|
Medium |
RHEL 9 must audit all uses of the ssh-keysign command. |
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... |
|
V-258201
|
Medium |
RHEL 9 must audit all uses of the ssh-agent command. |
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... |
|
V-258200
|
Medium |
RHEL 9 must audit all uses of the postqueue command. |
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... |
|
V-258199
|
Medium |
RHEL 9 must audit all uses of the postdrop command. |
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... |
|
V-258198
|
Medium |
RHEL 9 must audit all uses of the passwd command. |
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... |
|
V-258197
|
Medium |
RHEL 9 must audit all uses of the pam_timestamp_check command. |
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... |
|
V-258196
|
Medium |
RHEL 9 must audit all uses of the newgrp command. |
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... |
|
V-258195
|
Medium |
RHEL 9 must audit all uses of the kmod command. |
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.,... |
|
V-258194
|
Medium |
RHEL 9 must audit all uses of the gpasswd command. |
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... |
|
V-258193
|
Medium |
RHEL 9 must audit all uses of the crontab command. |
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... |
|
V-258192
|
Medium |
RHEL 9 must audit all uses of the chsh command. |
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... |
|
V-258191
|
Medium |
RHEL 9 must audit all uses of the chage command. |
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... |
|
V-258190
|
Medium |
RHEL 9 must audit all uses of the init_module and finit_module system calls. |
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... |
|
V-258189
|
Medium |
RHEL 9 must audit all uses of the delete_module system call. |
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... |
|
V-258188
|
Medium |
RHEL 9 must audit all uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls. |
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... |
|
V-258187
|
Medium |
RHEL 9 must audit all uses of the rename, unlink, rmdir, renameat, and unlinkat system calls. |
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... |
|
V-258186
|
Medium |
RHEL 9 must audit all uses of the setsebool command. |
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... |
|
V-258185
|
Medium |
RHEL 9 must audit all uses of the setfiles command. |
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... |
|
V-258184
|
Medium |
RHEL 9 must audit all uses of the semanage command. |
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... |
|
V-258183
|
Medium |
RHEL 9 must audit all uses of the chcon command. |
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.,... |
|
V-258182
|
Medium |
RHEL 9 must audit all uses of the setfacl command. |
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... |
|
V-258181
|
Medium |
RHEL 9 must audit all uses of the chacl command. |
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... |
|
V-258180
|
Medium |
RHEL 9 must audit all uses of umount system calls. |
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... |
|
V-258179
|
Medium |
RHEL 9 must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls. |
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.,... |
|
V-258178
|
Medium |
RHEL 9 must audit all uses of the chown, fchown, fchownat, and lchown system calls. |
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.,... |
|
V-258177
|
Medium |
RHEL 9 must audit all uses of the chmod, fchmod, and fchmodat system calls. |
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.,... |
|
V-258176
|
Medium |
RHEL 9 must audit uses of the "execve" system call. |
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... |
|
V-258175
|
Medium |
RHEL 9 audispd-plugins package must be installed. |
"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. |
|
V-258174
|
Medium |
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. |
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... |
|
V-258172
|
Medium |
RHEL 9 /etc/audit/auditd.conf file must have 0640 or less permissive to prevent unauthorized access. |
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,... |
|
V-258171
|
Medium |
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. |
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,... |
|
V-258170
|
Medium |
RHEL 9 must write audit records to disk. |
Audit data should be synchronously written to disk to ensure log integrity. This setting assures that all audit event data is written disk. |
|
V-258169
|
Medium |
RHEL 9 must produce audit records containing information to establish the identity of any individual or process associated with the event. |
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... |
|
V-258168
|
Medium |
RHEL 9 must periodically flush audit records to disk to prevent the loss of audit records. |
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. |
|
V-258167
|
Medium |
RHEL 9 audit logs file must have mode 0600 or less permissive to prevent unauthorized access to the audit log. |
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... |
|
V-258166
|
Medium |
RHEL 9 audit log directory must be owned by root to prevent unauthorized read access. |
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 |
|
V-258165
|
Medium |
RHEL 9 audit logs must be group-owned by root or by a restricted logging group to prevent unauthorized read access. |
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 |
|
V-258164
|
Medium |
RHEL 9 audit system must audit local events. |
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... |
|
V-258163
|
Medium |
RHEL 9 System Administrator (SA) and/or information system security officer (ISSO) (at a minimum) must be alerted of an audit processing failure event. |
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... |
|
V-258162
|
Medium |
RHEL 9 must take appropriate action when the internal event queue is full. |
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.... |
|
V-258161
|
Medium |
RHEL 9 must label all offloaded audit logs before sending them to the central log server. |
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... |
|
V-258160
|
Medium |
RHEL 9 audit system must take appropriate action when the audit files have reached maximum size. |
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... |
|
V-258159
|
Medium |
RHEL 9 must take action when allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity. |
If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity. |
|
V-258158
|
Medium |
RHEL 9 must take action when allocated audit record storage volume reaches 95 percent of the audit record storage capacity. |
If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity. |
|
V-258157
|
Medium |
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. |
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. |
|
V-258156
|
Medium |
RHEL 9 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. |
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. |
|
V-258155
|
Medium |
RHEL 9 must allocate audit record storage capacity to store at least one week's worth of audit records. |
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 |
|
V-258154
|
Medium |
RHEL 9 audit system must take appropriate action when the audit storage volume is full. |
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... |
|
V-258153
|
Medium |
RHEL 9 audit system must take appropriate action when an error writing to the audit storage volume occurs. |
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... |
|
V-258152
|
Medium |
RHEL 9 audit service must be enabled. |
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... |
|
V-258151
|
Medium |
RHEL 9 audit package must be installed. |
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... |
|
V-258150
|
Medium |
RHEL 9 must use cron logging. |
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. |
|
V-258149
|
Medium |
RHEL 9 must be configured to forward audit records via TCP to a different system or media from the system being audited via rsyslog. |
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... |
|
V-258148
|
Medium |
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. |
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... |
|
V-258147
|
Medium |
RHEL 9 must encrypt the transfer of audit records offloaded onto a different system or media from the system being audited via rsyslog. |
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... |
|
V-258146
|
Medium |
RHEL 9 must authenticate the remote logging server for offloading audit logs via rsyslog. |
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... |
|
V-258144
|
Medium |
All RHEL 9 remote access methods must be monitored. |
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. |
|
V-258143
|
Medium |
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. |
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... |
|
V-258142
|
Medium |
The rsyslog service on RHEL 9 must be active. |
The "rsyslog" service must be running to provide logging services, which are essential to system administration. |
|
V-258141
|
Medium |
RHEL 9 must have the packages required for encrypting offloaded audit logs installed. |
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 |
|
V-258140
|
Medium |
RHEL 9 must have the rsyslog package installed. |
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... |
|
V-258137
|
Medium |
RHEL 9 must use cryptographic mechanisms to protect the integrity of audit tools. |
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... |
|
V-258136
|
Medium |
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. |
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... |
|
V-258135
|
Medium |
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. |
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... |
|
V-258134
|
Medium |
RHEL 9 must have the AIDE package installed. |
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... |
|
V-258133
|
Medium |
RHEL 9 must prohibit the use of cached authenticators after one day. |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable. |
|
V-258132
|
Medium |
RHEL 9 must map the authenticated identity to the user or group account for PKI-based authentication. |
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. |
|
V-258131
|
Medium |
RHEL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. |
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... |
|
V-258130
|
Medium |
RHEL 9 must prevent system daemons from using Kerberos for authentication. |
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... |
|
V-258129
|
Medium |
RHEL 9 must require authentication to access single-user mode. |
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... |
|
V-258128
|
Medium |
RHEL 9 must require authentication to access emergency mode. |
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... |
|
V-258127
|
Medium |
RHEL 9, for PKI-based authentication, must enforce authorized access to the corresponding private key. |
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... |
|
V-258126
|
Medium |
RHEL 9 must have the opensc package installed. |
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... |
|
V-258125
|
Medium |
The pcscd service on RHEL 9 must be active. |
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... |
|
V-258124
|
Medium |
RHEL 9 must have the pcsc-lite package installed. |
The pcsc-lite package must be installed if it is to be available for multifactor authentication using smart cards. |
|
V-258123
|
Medium |
RHEL 9 must implement certificate status checking for multifactor authentication. |
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... |
|
V-258122
|
Medium |
RHEL 9 must enable certificate based smart card authentication. |
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... |
|
V-258121
|
Medium |
RHEL 9 must use the common access card (CAC) smart card driver. |
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,... |
|
V-258120
|
Medium |
RHEL 9 must not have accounts configured with blank or null passwords. |
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. |
|
V-258118
|
Medium |
RHEL 9 must not be configured to bypass password requirements for privilege escalation. |
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 |
|
V-258117
|
Medium |
RHEL 9 must be configured to use the shadow file to store only encrypted representations of passwords. |
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... |
|
V-258116
|
Medium |
RHEL 9 must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords. |
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... |
|
V-258115
|
Medium |
RHEL 9 must require the change of at least four character classes when passwords are changed. |
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... |
|
V-258114
|
Medium |
RHEL 9 must require the maximum number of repeating characters be limited to three when passwords are changed. |
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... |
|
V-258113
|
Medium |
RHEL 9 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed. |
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... |
|
V-258112
|
Medium |
RHEL 9 must require the change of at least eight characters when passwords are changed. |
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... |
|
V-258111
|
Medium |
RHEL 9 must enforce password complexity by requiring that at least one uppercase character be used. |
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... |
|
V-258110
|
Medium |
RHEL 9 must prevent the use of dictionary words for passwords. |
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... |
|
V-258109
|
Medium |
RHEL 9 must enforce password complexity by requiring that at least one special character be used. |
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... |
|
V-258107
|
Medium |
RHEL 9 passwords must be created with a minimum of 15 characters. |
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... |
|
V-258106
|
Medium |
RHEL 9 must require users to provide a password for privilege escalation. |
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 |
|
V-258105
|
Medium |
RHEL 9 passwords must have a 24 hours minimum password lifetime restriction in /etc/shadow. |
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... |
|
V-258104
|
Medium |
RHEL 9 passwords for new users or password changes must have a 24 hours minimum password lifetime restriction in /etc/login.defs. |
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... |
|
V-258103
|
Medium |
RHEL 9 must enforce password complexity by requiring that at least one numeric character be used. |
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... |
|
V-258102
|
Medium |
RHEL 9 must enforce password complexity by requiring that at least one lowercase character be used. |
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... |
|
V-258101
|
Medium |
RHEL 9 must enforce password complexity rules for the root account. |
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... |
|
V-258100
|
Medium |
RHEL 9 system-auth must be configured to use a sufficient number of hashing rounds. |
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... |
|
V-258099
|
Medium |
RHEL 9 password-auth must be configured to use a sufficient number of hashing rounds. |
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... |
|
V-258098
|
Medium |
RHEL 9 must ensure the password complexity module is enabled in the system-auth file. |
Enabling PAM password complexity permits enforcement of strong passwords and consequently makes the system less prone to dictionary attacks. |
|
V-258097
|
Medium |
RHEL 9 must ensure the password complexity module is enabled in the password-auth file. |
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 |
|
V-258096
|
Medium |
RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. |
If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks. |
|
V-258095
|
Medium |
RHEL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. |
If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks. |
|
V-258091
|
Medium |
RHEL 9 must ensure the password complexity module in the system-auth file is configured for three retries or less. |
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... |
|
V-258090
|
Medium |
RHEL 9 fapolicy module must be enabled. |
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... |
|
V-258089
|
Medium |
RHEL 9 fapolicy module must be installed. |
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 allow listing.
Utilizing an allow list provides a configuration management method for allowing the execution of... |
|
V-258088
|
Medium |
RHEL 9 must restrict the use of the "su" command. |
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 |
|
V-258087
|
Medium |
RHEL 9 must restrict privilege elevation to authorized personnel. |
If the "sudoers" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system. |
|
V-258086
|
Medium |
RHEL 9 must require users to reauthenticate for privilege escalation. |
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 |
|
V-258085
|
Medium |
RHEL 9 must use the invoking user's password for privilege escalation when using "sudo". |
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. |
|
V-258084
|
Medium |
RHEL 9 must require reauthentication when using the "sudo" command. |
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... |
|
V-258083
|
Medium |
RHEL 9 must have the sudo package installed. |
"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. |
|
V-258082
|
Medium |
RHEL 9 policycoreutils-python-utils package must be installed. |
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. |
|
V-258081
|
Medium |
RHEL 9 must have policycoreutils package installed. |
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... |
|
V-258080
|
Medium |
RHEL 9 must configure SELinux context type to allow the use of a nondefault faillock tally directory. |
Not having the correct SELinux context on the faillock directory may lead to unauthorized access to the directory. |
|
V-258079
|
Medium |
RHEL 9 must enable the SELinux targeted policy. |
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"... |
|
V-258077
|
Medium |
RHEL 9 must terminate idle user sessions. |
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. |
|
V-258075
|
Medium |
RHEL 9 must define default permissions for the system default profile. |
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... |
|
V-258074
|
Medium |
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. |
Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access. |
|
V-258073
|
Medium |
RHEL 9 must define default permissions for the c shell. |
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... |
|
V-258072
|
Medium |
RHEL 9 must define default permissions for the bash shell. |
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... |
|
V-258071
|
Medium |
RHEL 9 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. |
Increasing the time between a failed authentication attempt and reprompting to enter credentials helps to slow a single-threaded brute force attack. |
|
V-258070
|
Medium |
RHEL 9 must log username information when unsuccessful logon attempts occur. |
Without auditing of these events, it may be harder or impossible to identify what an attacker did after an attack. |
|
V-258068
|
Medium |
RHEL 9 must automatically exit interactive command shell user sessions after 15 minutes of inactivity. |
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 |
|
V-258062
|
Medium |
Local RHEL 9 initialization files must not execute world-writable programs. |
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... |
|
V-258061
|
Medium |
RHEL 9 groups must have unique Group ID (GID). |
To ensure accountability and prevent unauthenticated access, groups must be identified uniquely to prevent potential misuse and compromise of the system. |
|
V-258060
|
Medium |
RHEL 9 must ensure account lockouts persist. |
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. |
|
V-258058
|
Medium |
RHEL 9 must not have unauthorized accounts. |
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. |
|
V-258057
|
Medium |
RHEL 9 must maintain an account lock until the locked account is released by an administrator. |
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 |
|
V-258056
|
Medium |
RHEL 9 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period. |
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 |
|
V-258055
|
Medium |
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. |
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 |
|
V-258054
|
Medium |
RHEL 9 must automatically lock an account when three unsuccessful logon attempts occur. |
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 |
|
V-258053
|
Medium |
All RHEL 9 local interactive user home directories must be group-owned by the home directory owner's primary group. |
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. |
|
V-258052
|
Medium |
All RHEL 9 local interactive user home directories defined in the /etc/passwd file must exist. |
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... |
|
V-258051
|
Medium |
All RHEL 9 local interactive users must have a home directory assigned in the /etc/passwd file. |
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. |
|
V-258050
|
Medium |
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. |
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... |
|
V-258049
|
Medium |
RHEL 9 must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. |
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... |
|
V-258048
|
Medium |
All RHEL 9 interactive users must have a primary group that exists. |
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. |
|
V-258047
|
Medium |
RHEL 9 must automatically expire temporary accounts within 72 hours. |
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... |
|
V-258046
|
Medium |
RHEL 9 system accounts must not have an interactive login shell. |
Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts. |
|
V-258045
|
Medium |
RHEL 9 duplicate User IDs (UIDs) must not exist for interactive users. |
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 |
|
V-258044
|
Medium |
RHEL 9 must set the umask value to 077 for all local interactive user accounts. |
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... |
|
V-258043
|
Medium |
All RHEL 9 local interactive user accounts must be assigned a home directory upon creation. |
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. |
|
V-258042
|
Medium |
RHEL 9 user account passwords must have a 60-day maximum password lifetime restriction. |
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. |
|
V-258041
|
Medium |
RHEL 9 user account passwords for new users or password changes must have a 60-day maximum password lifetime restriction in /etc/login.defs. |
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... |
|
V-258040
|
Medium |
RHEL 9 wireless network adapters must be disabled. |
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... |
|
V-258039
|
Medium |
RHEL 9 Bluetooth must be disabled. |
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... |
|
V-258038
|
Medium |
RHEL 9 must block unauthorized peripherals before establishing a connection. |
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... |
|
V-258036
|
Medium |
RHEL 9 must have the USBGuard package enabled. |
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... |
|
V-258035
|
Medium |
RHEL 9 must have the USBGuard package installed. |
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... |
|
V-258034
|
Medium |
RHEL 9 must be configured to disable USB mass storage. |
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 |
|
V-258033
|
Medium |
RHEL 9 must disable the user list at logon for graphical user interfaces. |
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. |
|
V-258032
|
Medium |
RHEL 9 must prevent a user from overriding the Ctrl-Alt-Del sequence settings for the graphical user interface. |
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. |
|
V-258031
|
Medium |
RHEL 9 must disable the ability of a user to accidentally press Ctrl-Alt-Del and cause a system to shut down or reboot. |
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. |
|
V-258030
|
Medium |
RHEL 9 must prevent a user from overriding the disable-restart-buttons setting for the graphical user interface. |
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. |
|
V-258029
|
Medium |
RHEL 9 must disable the ability of a user to restart the system from the login screen. |
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. |
|
V-258028
|
Medium |
RHEL 9 effective dconf policy must match the policy keyfiles. |
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... |
|
V-258027
|
Medium |
RHEL 9 must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
Setting the screensaver mode to blank-only conceals the contents of the display from passersby. |
|
V-258026
|
Medium |
RHEL 9 must prevent a user from overriding the session lock-delay setting for the graphical user interface. |
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... |
|
V-258025
|
Medium |
RHEL 9 must initiate a session lock for graphical user interfaces when the screensaver is activated. |
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. |
|
V-258024
|
Medium |
RHEL 9 must prevent a user from overriding the session idle-delay setting for the graphical user interface. |
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... |
|
V-258023
|
Medium |
RHEL 9 must automatically lock graphical user sessions after 15 minutes of inactivity. |
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... |
|
V-258022
|
Medium |
RHEL 9 must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface. |
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... |
|
V-258021
|
Medium |
RHEL 9 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for graphical user sessions. |
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... |
|
V-258020
|
Medium |
RHEL 9 must prevent a user from overriding the disabling of the graphical user smart card removal action. |
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... |
|
V-258019
|
Medium |
RHEL 9 must be able to initiate directly a session lock for all connection types using smart card when the smart card is removed. |
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... |
|
V-258017
|
Medium |
RHEL 9 must prevent a user from overriding the disabling of the graphical user interface autorun function. |
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 |
|
V-258016
|
Medium |
RHEL 9 must disable the graphical user interface autorun function unless required. |
Allowing autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents autorun commands from executing. |
|
V-258015
|
Medium |
RHEL 9 must prevent a user from overriding the disabling of the graphical user interface automount function. |
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 |
|
V-258014
|
Medium |
RHEL 9 must disable the graphical user interface automount function unless required. |
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 |
|
V-258013
|
Medium |
RHEL 9 must prevent a user from overriding the banner-message-enable setting for the graphical user interface. |
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... |
|
V-258012
|
Medium |
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. |
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... |
|
V-258011
|
Medium |
RHEL 9 SSH daemon must prevent remote hosts from connecting to the proxy display. |
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... |
|
V-258009
|
Medium |
RHEL 9 SSH daemon must display the date and time of the last successful account logon upon an SSH logon. |
Providing users feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. |
|
V-258008
|
Medium |
RHEL 9 SSH daemon must perform strict mode checking of home directory configuration files. |
If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user. |
|
V-258007
|
Medium |
RHEL 9 SSH daemon must disable remote X connections for interactive users. |
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... |
|
V-258006
|
Medium |
RHEL 9 SSH daemon must not allow known hosts authentication. |
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. |
|
V-258005
|
Medium |
RHEL 9 SSH daemon must not allow rhosts authentication. |
SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
|
V-258004
|
Medium |
RHEL 9 SSH daemon must not allow Kerberos authentication. |
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 |
|
V-258003
|
Medium |
RHEL 9 SSH daemon must not allow GSSAPI authentication. |
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 |
|
V-258002
|
Medium |
RHEL 9 SSH daemon must not allow compression or must only allow compression after successful authentication. |
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. |
|
V-258001
|
Medium |
RHEL 9 SSH public host key files must have mode 0644 or less permissive. |
If a public host key file is modified by an unauthorized user, the SSH service may be compromised. |
|
V-258000
|
Medium |
RHEL 9 SSH private host key files must have mode 0640 or less permissive. |
If an unauthorized user obtains the private SSH host key file, the host could be impersonated. |
|
V-257999
|
Medium |
RHEL 9 SSH server configuration file must have mode 0600 or less permissive. |
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. |
|
V-257998
|
Medium |
RHEL 9 SSH server configuration file must be owned by root. |
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. |
|
V-257997
|
Medium |
RHEL 9 SSH server configuration file must be group-owned by root. |
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. |
|
V-257996
|
Medium |
RHEL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. |
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... |
|
V-257995
|
Medium |
RHEL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. |
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... |
|
V-257994
|
Medium |
RHEL 9 must force a frequent session key renegotiation for SSH connections to the server. |
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... |
|
V-257993
|
Medium |
RHEL 9 must not allow users to override SSH environment variables. |
SSH environment options potentially allow users to bypass access restriction in some configurations. |
|
V-257992
|
Medium |
RHEL 9 must not allow a noncertificate trusted host SSH logon to the system. |
SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
|
V-257991
|
Medium |
The RHEL 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. |
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... |
|
V-257989
|
Medium |
The RHEL 9 SSH server must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. |
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... |
|
V-257988
|
Medium |
RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH connections. |
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... |
|
V-257987
|
Medium |
RHEL 9 SSH daemon must be configured to use system-wide crypto policies. |
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... |
|
V-257985
|
Medium |
RHEL 9 must not permit direct logons to the root account using remote access via SSH. |
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... |
|
V-257983
|
Medium |
RHEL 9 SSHD must accept public key authentication. |
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 common access card (CAC) with... |
|
V-257982
|
Medium |
RHEL 9 must log SSH connection attempts and failures to the server. |
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... |
|
V-257981
|
Medium |
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. |
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 |
|
V-257980
|
Medium |
RHEL 9 must have the openssh-clients package installed. |
This package includes utilities to make encrypted connections and transfer files securely to SSH servers. |
|
V-257979
|
Medium |
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. |
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... |
|
V-257978
|
Medium |
All RHEL 9 networked systems must have SSH installed. |
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... |
|
V-257977
|
Medium |
RHEL 9 must not forward IPv6 source-routed packets by default. |
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... |
|
V-257976
|
Medium |
RHEL 9 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted. |
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. |
|
V-257975
|
Medium |
RHEL 9 must not accept router advertisements on all IPv6 interfaces by default. |
An illicit router advertisement message could result in a man-in-the-middle attack. |
|
V-257974
|
Medium |
RHEL 9 must not enable IPv6 packet forwarding unless the system is a router. |
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. |
|
V-257973
|
Medium |
RHEL 9 must not forward IPv6 source-routed packets. |
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... |
|
V-257972
|
Medium |
RHEL 9 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages. |
An illicit ICMP redirect message could result in a man-in-the-middle attack. |
|
V-257971
|
Medium |
RHEL 9 must not accept router advertisements on all IPv6 interfaces. |
An illicit router advertisement message could result in a man-in-the-middle attack. |
|
V-257970
|
Medium |
RHEL 9 must not enable IPv4 packet forwarding unless the system is a router. |
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. |
|
V-257969
|
Medium |
RHEL 9 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default. |
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. |
|
V-257968
|
Medium |
RHEL 9 must not send Internet Control Message Protocol (ICMP) redirects. |
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. |
|
V-257967
|
Medium |
RHEL 9 must limit the number of bogus Internet Control Message Protocol (ICMP) response errors logs. |
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... |
|
V-257966
|
Medium |
RHEL 9 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address. |
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. |
|
V-257965
|
Medium |
RHEL 9 must use a reverse-path filter for IPv4 network traffic when possible by default. |
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. |
|
V-257964
|
Medium |
RHEL 9 must not forward IPv4 source-routed packets by default. |
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... |
|
V-257963
|
Medium |
RHEL 9 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect messages from being accepted. |
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... |
|
V-257962
|
Medium |
RHEL 9 must use reverse path filtering on all IPv4 interfaces. |
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. |
|
V-257961
|
Medium |
RHEL 9 must log IPv4 packets with impossible addresses by default. |
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. |
|
V-257960
|
Medium |
RHEL 9 must log IPv4 packets with impossible addresses. |
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. |
|
V-257959
|
Medium |
RHEL 9 must not forward Internet Protocol version 4 (IPv4) source-routed packets. |
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... |
|
V-257958
|
Medium |
RHEL 9 must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages. |
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... |
|
V-257957
|
Medium |
RHEL 9 must be configured to use TCP syncookies. |
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... |
|
V-257954
|
Medium |
RHEL 9 libreswan package must be installed. |
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 |
|
V-257953
|
Medium |
RHEL 9 must forward mail from postmaster to the root account using a postfix alias. |
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... |
|
V-257951
|
Medium |
RHEL 9 must be configured to prevent unrestricted mail relaying. |
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. |
|
V-257950
|
Medium |
RHEL 9 must not have unauthorized IP tunnels configured. |
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). |
|
V-257949
|
Medium |
RHEL 9 must configure a DNS processing mode in Network Manager. |
In order to ensure that DNS resolver settings are respected, a DNS mode in Network Manager must be configured. |
|
V-257948
|
Medium |
RHEL 9 systems using Domain Name Servers (DNS) resolution must have at least two name servers configured. |
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. |
|
V-257945
|
Medium |
RHEL 9 must securely compare internal information system clocks at least every 24 hours. |
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... |
|
V-257944
|
Medium |
RHEL 9 chronyd service must be enabled. |
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... |
|
V-257943
|
Medium |
RHEL 9 must have the chrony package installed. |
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. |
|
V-257942
|
Medium |
RHEL 9 must enable hardening for the Berkeley Packet Filter just-in-time compiler. |
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". |
|
V-257941
|
Medium |
RHEL 9 network interfaces must not be in promiscuous mode. |
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... |
|
V-257940
|
Medium |
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. |
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. |
|
V-257939
|
Medium |
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. |
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... |
|
V-257937
|
Medium |
A RHEL 9 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems. |
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... |
|
V-257936
|
Medium |
The firewalld service on RHEL 9 must be active. |
"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.... |
|
V-257935
|
Medium |
RHEL 9 must have the firewalld package installed. |
"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.... |
|
V-257934
|
Medium |
RHEL 9 /etc/shadow file must have mode 0000 to prevent unauthorized access. |
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. |
|
V-257933
|
Medium |
RHEL 9 /etc/crontab file must have mode 0600. |
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. |
|
V-257932
|
Medium |
RHEL 9 must be configured so that all system device files are correctly labeled to prevent unauthorized modification. |
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. |
|
V-257931
|
Medium |
All RHEL 9 local files and directories must have a valid owner. |
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. |
|
V-257930
|
Medium |
All RHEL 9 local files and directories must have a valid group owner. |
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. |
|
V-257929
|
Medium |
A sticky bit must be set on all RHEL 9 public directories. |
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.,... |
|
V-257928
|
Medium |
All RHEL 9 world-writable directories must be owned by root, sys, bin, or an application user. |
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... |
|
V-257927
|
Medium |
RHEL 9 cron configuration files directory must be group-owned by root. |
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. |
|
V-257926
|
Medium |
RHEL 9 cron configuration files directory must be owned by root. |
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. |
|
V-257925
|
Medium |
RHEL 9 audit tools must be group-owned by root. |
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... |
|
V-257924
|
Medium |
RHEL 9 audit tools must be owned by root. |
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... |
|
V-257923
|
Medium |
RHEL 9 library directories must be group-owned by root or a system account. |
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... |
|
V-257922
|
Medium |
RHEL 9 library directories must be owned by root. |
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... |
|
V-257921
|
Medium |
RHEL 9 library files must be group-owned by root or a system account. |
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... |
|
V-257920
|
Medium |
RHEL 9 library files must be owned by root. |
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... |
|
V-257919
|
Medium |
RHEL 9 system commands must be group-owned by root or a system account. |
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... |
|
V-257918
|
Medium |
RHEL 9 system commands must be owned by root. |
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... |
|
V-257917
|
Medium |
RHEL 9 /var/log/messages file must be group-owned by root. |
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... |
|
V-257916
|
Medium |
RHEL 9 /var/log/messages file must be owned by root. |
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... |
|
V-257915
|
Medium |
RHEL 9 /var/log directory must be group-owned by root. |
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... |
|
V-257914
|
Medium |
RHEL 9 /var/log directory must be owned by root. |
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... |
|
V-257913
|
Medium |
RHEL 9 /etc/shadow- file must be group-owned by root. |
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. |
|
V-257912
|
Medium |
RHEL 9 /etc/shadow- file must be owned by root. |
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. |
|
V-257911
|
Medium |
RHEL 9 /etc/shadow file must be group-owned by root. |
The "/etc/shadow" file stores password hashes. Protection of this file is critical for system security. |
|
V-257910
|
Medium |
RHEL 9 /etc/shadow file must be owned by root. |
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. |
|
V-257909
|
Medium |
RHEL 9 /etc/passwd- file must be group-owned by root. |
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. |
|
V-257908
|
Medium |
RHEL 9 /etc/passwd- file must be owned by root. |
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. |
|
V-257907
|
Medium |
RHEL 9 /etc/passwd file must be group-owned by root. |
The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
|
V-257906
|
Medium |
RHEL 9 /etc/passwd file must be owned by root. |
The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
|
V-257905
|
Medium |
RHEL 9 /etc/gshadow- file must be group-owned by root. |
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. |
|
V-257904
|
Medium |
RHEL 9 /etc/gshadow- file must be owned by root. |
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. |
|
V-257903
|
Medium |
RHEL 9 /etc/gshadow file must be group-owned by root. |
The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security. |
|
V-257902
|
Medium |
RHEL 9 /etc/gshadow file must be owned by root. |
The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security. |
|
V-257901
|
Medium |
RHEL 9 /etc/group- file must be group-owned by root. |
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. |
|
V-257900
|
Medium |
RHEL 9 /etc/group- file must be owned by root. |
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. |
|
V-257899
|
Medium |
RHEL 9 /etc/group file must be group-owned by root. |
The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
|
V-257898
|
Medium |
RHEL 9 /etc/group file must be owned by root. |
The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
|
V-257897
|
Medium |
RHEL 9 /etc/shadow- file must have mode 0000 or less permissive to prevent unauthorized access. |
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. |
|
V-257896
|
Medium |
RHEL 9 /etc/passwd- file must have mode 0644 or less permissive to prevent unauthorized access. |
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. |
|
V-257895
|
Medium |
RHEL 9 /etc/passwd file must have mode 0644 or less permissive to prevent unauthorized access. |
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. |
|
V-257894
|
Medium |
RHEL 9 /etc/gshadow- file must have mode 0000 or less permissive to prevent unauthorized access. |
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. |
|
V-257893
|
Medium |
RHEL 9 /etc/gshadow file must have mode 0000 or less permissive to prevent unauthorized access. |
The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security. |
|
V-257892
|
Medium |
RHEL 9 /etc/group- file must have mode 0644 or less permissive to prevent unauthorized access. |
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. |
|
V-257891
|
Medium |
RHEL 9 /etc/group file must have mode 0644 or less permissive to prevent unauthorized access. |
The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
|
V-257890
|
Medium |
All RHEL 9 local interactive user home directories must have mode 0750 or less permissive. |
Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users. |
|
V-257889
|
Medium |
All RHEL 9 local initialization files must have mode 0740 or less permissive. |
Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon. |
|
V-257888
|
Medium |
RHEL 9 cron configuration directories must have a mode of 0700 or less permissive. |
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. |
|
V-257887
|
Medium |
RHEL 9 audit tools must have a mode of 0755 or less permissive. |
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... |
|
V-257886
|
Medium |
RHEL 9 /var/log/messages file must have mode 0640 or less permissive. |
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... |
|
V-257885
|
Medium |
RHEL 9 /var/log directory must have mode 0755 or less permissive. |
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... |
|
V-257884
|
Medium |
RHEL 9 library files must have mode 755 or less permissive. |
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... |
|
V-257883
|
Medium |
RHEL 9 library directories must have mode 755 or less permissive. |
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... |
|
V-257882
|
Medium |
RHEL 9 system commands must have mode 755 or less permissive. |
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... |
|
V-257881
|
Medium |
RHEL 9 must prevent special devices on non-root local partitions. |
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... |
|
V-257878
|
Medium |
RHEL 9 must mount /var/tmp with the nosuid option. |
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... |
|
V-257877
|
Medium |
RHEL 9 must mount /var/tmp with the noexec option. |
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. |
|
V-257876
|
Medium |
RHEL 9 must mount /var/tmp with the nodev option. |
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... |
|
V-257875
|
Medium |
RHEL 9 must mount /var/log/audit with the nosuid option. |
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... |
|
V-257874
|
Medium |
RHEL 9 must mount /var/log/audit with the noexec option. |
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. |
|
V-257873
|
Medium |
RHEL 9 must mount /var/log/audit with the nodev option. |
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... |
|
V-257872
|
Medium |
RHEL 9 must mount /var/log with the nosuid option. |
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... |
|
V-257871
|
Medium |
RHEL 9 must mount /var/log with the noexec option. |
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. |
|
V-257870
|
Medium |
RHEL 9 must mount /var/log with the nodev option. |
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... |
|
V-257869
|
Medium |
RHEL 9 must mount /var with the nodev option. |
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... |
|
V-257868
|
Medium |
RHEL 9 must mount /tmp with the nosuid option. |
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... |
|
V-257867
|
Medium |
RHEL 9 must mount /tmp with the noexec option. |
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. |
|
V-257866
|
Medium |
RHEL 9 must mount /tmp with the nodev option. |
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... |
|
V-257865
|
Medium |
RHEL 9 must mount /dev/shm with the nosuid option. |
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... |
|
V-257864
|
Medium |
RHEL 9 must mount /dev/shm with the noexec option. |
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. |
|
V-257863
|
Medium |
RHEL 9 must mount /dev/shm with the nodev option. |
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... |
|
V-257862
|
Medium |
RHEL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory. |
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... |
|
V-257861
|
Medium |
RHEL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot directory. |
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... |
|
V-257860
|
Medium |
RHEL 9 must mount /boot with the nodev option. |
The only legitimate location for device files is the "/dev" directory located on the root partition. The only exception to this is chroot jails. |
|
V-257859
|
Medium |
RHEL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media. |
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... |
|
V-257858
|
Medium |
RHEL 9 must prevent special devices on file systems that are used with removable media. |
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. |
|
V-257857
|
Medium |
RHEL 9 must prevent code from being executed on file systems that are used with removable media. |
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. |
|
V-257856
|
Medium |
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). |
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... |
|
V-257855
|
Medium |
RHEL 9 must prevent code from being executed on file systems that are imported via Network File System (NFS). |
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. |
|
V-257854
|
Medium |
RHEL 9 must prevent special devices on file systems that are imported via Network File System (NFS). |
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. |
|
V-257852
|
Medium |
RHEL 9 must prevent code from being executed on file systems that contain user home directories. |
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. |
|
V-257851
|
Medium |
RHEL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that contain user home directories. |
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... |
|
V-257850
|
Medium |
RHEL 9 must prevent device files from being interpreted on file systems that contain user home directories. |
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... |
|
V-257849
|
Medium |
RHEL 9 file system automount function must be disabled unless required. |
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 |
|
V-257848
|
Medium |
RHEL 9 must use a separate file system for /var/tmp. |
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. |
|
V-257844
|
Medium |
RHEL 9 must use a separate file system for /tmp. |
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. |
|
V-257843
|
Medium |
A separate RHEL 9 file system must be used for user home directories (such as /home or an equivalent). |
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. |
|
V-257842
|
Medium |
RHEL 9 must have the s-nail package installed. |
The "s-nail" package provides the mail command required to allow sending email notifications of unauthorized configuration changes to designated personnel. |
|
V-257841
|
Medium |
RHEL 9 must have the rng-tools package installed. |
"rng-tools" provides hardware random number generator tools, such as those used in the formation of x509/PKI certificates. |
|
V-257840
|
Medium |
RHEL 9 must have the nss-tools package installed. |
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. |
|
V-257839
|
Medium |
RHEL 9 must have the gnutls-utils package installed. |
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... |
|
V-257838
|
Medium |
RHEL 9 must have the openssl-pkcs11 package installed. |
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... |
|
V-257837
|
Medium |
A graphical display manager must not be installed on RHEL 9 unless approved. |
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. |
|
V-257836
|
Medium |
RHEL 9 must not have the quagga package installed. |
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. |
|
V-257834
|
Medium |
RHEL 9 must not have the tuned package installed. |
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... |
|
V-257833
|
Medium |
RHEL 9 must not have the iprutils package installed. |
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... |
|
V-257832
|
Medium |
RHEL 9 must not have the gssproxy package installed. |
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... |
|
V-257831
|
Medium |
RHEL 9 must not have the telnet-server package installed. |
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,... |
|
V-257830
|
Medium |
RHEL 9 must not have the rsh-server package installed. |
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... |
|
V-257829
|
Medium |
RHEL 9 must not have the ypserv package installed. |
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. |
|
V-257828
|
Medium |
RHEL 9 must not have the nfs-utils package installed. |
"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... |
|
V-257827
|
Medium |
RHEL 9 must not have the sendmail package installed. |
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 |
|
V-257825
|
Medium |
RHEL 9 subscription-manager package must be installed. |
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... |
|
V-257823
|
Medium |
RHEL 9 must be configured so that the cryptographic hashes of system files match vendor values. |
The hashes of important files such as 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. |
|
V-257819
|
Medium |
RHEL 9 must ensure cryptographic verification of vendor software packages. |
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... |
|
V-257818
|
Medium |
The kdump service on RHEL 9 must be disabled. |
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... |
|
V-257817
|
Medium |
RHEL 9 must implement nonexecutable data to protect its memory from unauthorized code execution. |
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... |
|
V-257816
|
Medium |
RHEL 9 must disable the use of user namespaces. |
User namespaces are used primarily for Linux containers. The value "0" disallows the use of user namespaces. |
|
V-257815
|
Medium |
RHEL 9 must disable acquiring, saving, and processing core dumps. |
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. |
|
V-257814
|
Medium |
RHEL 9 must disable core dumps for all users. |
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. |
|
V-257813
|
Medium |
RHEL 9 must disable storing core dumps. |
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... |
|
V-257812
|
Medium |
RHEL 9 must disable core dump backtraces. |
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... |
|
V-257811
|
Medium |
RHEL 9 must restrict usage of ptrace to descendant processes. |
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 |
|
V-257810
|
Medium |
RHEL 9 must disable access to network bpf system call from nonprivileged processes. |
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 |
|
V-257809
|
Medium |
RHEL 9 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. |
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... |
|
V-257808
|
Medium |
RHEL 9 must disable the Transparent Inter Process Communication (TIPC) kernel module. |
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... |
|
V-257807
|
Medium |
RHEL 9 must disable the Stream Control Transmission Protocol (SCTP) kernel module. |
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... |
|
V-257806
|
Medium |
RHEL 9 must be configured to disable the FireWire kernel module. |
Disabling firewire protects the system against exploitation of any flaws in its implementation. |
|
V-257805
|
Medium |
RHEL 9 must be configured to disable the Controller Area Network kernel module. |
Disabling Controller Area Network (CAN) protects the system against exploitation of any flaws in its implementation. |
|
V-257804
|
Medium |
RHEL 9 must be configured to disable the Asynchronous Transfer Mode kernel module. |
Disabling Asynchronous Transfer Mode (ATM) protects the system against exploitation of any flaws in its implementation. |
|
V-257803
|
Medium |
RHEL 9 must disable the kernel.core_pattern. |
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. |
|
V-257802
|
Medium |
RHEL 9 must enable kernel parameters to enforce discretionary access control on symlinks. |
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... |
|
V-257801
|
Medium |
RHEL 9 must enable kernel parameters to enforce discretionary access control on hardlinks. |
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 |
|
V-257800
|
Medium |
RHEL 9 must restrict exposed kernel pointer addresses access. |
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... |
|
V-257799
|
Medium |
RHEL 9 must prevent the loading of a new kernel for later execution. |
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... |
|
V-257798
|
Medium |
RHEL 9 must prevent kernel profiling by nonprivileged users. |
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.,... |
|
V-257797
|
Medium |
RHEL 9 must restrict access to the kernel message buffer. |
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.,... |
|
V-257794
|
Medium |
RHEL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks. |
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... |
|
V-257793
|
Medium |
RHEL 9 must clear the page allocator to prevent use-after-free attacks. |
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:... |
|
V-257792
|
Medium |
RHEL 9 must disable virtual system calls. |
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.... |
|
V-257791
|
Medium |
RHEL 9 /boot/grub2/grub.cfg file must be owned by root. |
The " /boot/grub2/grub.cfg" file stores sensitive system configuration. Protection of this file is critical for system security. |
|
V-257790
|
Medium |
RHEL 9 /boot/grub2/grub.cfg file must be group-owned by root. |
The "root" group is a highly privileged group. Furthermore, the group-owner of this file should not have any access privileges anyway. |
|
V-257788
|
Medium |
RHEL 9 must disable the ability of systemd to spawn an interactive boot process. |
Using interactive or recovery boot, the console user could disable auditing, firewalls, or other services, weakening system security. |
|
V-257787
|
Medium |
RHEL 9 must require a boot loader superuser password. |
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... |
|
V-257786
|
Medium |
RHEL 9 debug-shell systemd service must be disabled. |
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... |
|
V-257783
|
Medium |
RHEL 9 systemd-journald service must be enabled. |
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. |
|
V-257781
|
Medium |
The graphical display manager must not be the default target on RHEL 9 unless approved. |
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. |
|
V-257779
|
Medium |
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. |
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... |
|
V-257778
|
Medium |
RHEL 9 vendor packaged system security patches and updates must be installed and up to date. |
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. |
|
V-258173
|
Low |
RHEL 9 must allocate an audit_backlog_limit of sufficient size to capture processes that start prior to the audit daemon. |
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... |
|
V-258139
|
Low |
RHEL 9 must be configured so that the file integrity tool verifies extended attributes. |
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... |
|
V-258138
|
Low |
RHEL 9 must be configured so that the file integrity tool verifies Access Control Lists (ACLs). |
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... |
|
V-258076
|
Low |
RHEL 9 must display the date and time of the last successful account logon upon logon. |
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. |
|
V-258069
|
Low |
RHEL 9 must limit the number of concurrent sessions to ten for all accounts and/or account types. |
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... |
|
V-258037
|
Low |
RHEL 9 must enable Linux audit logging for the USBGuard daemon. |
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... |
|
V-257947
|
Low |
RHEL 9 must disable network management of the chrony daemon. |
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 |
|
V-257946
|
Low |
RHEL 9 must disable the chrony daemon from acting as a server. |
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 |
|
V-257880
|
Low |
RHEL 9 must disable mounting of cramfs. |
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... |
|
V-257847
|
Low |
RHEL 9 must use a separate file system for the system audit data path. |
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 |
|
V-257846
|
Low |
RHEL 9 must use a separate file system for /var/log. |
Placing "/var/log" in its own partition enables better separation between log files and other files in "/var/". |
|
V-257845
|
Low |
RHEL 9 must use a separate file system for /var. |
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. |
|
V-257824
|
Low |
RHEL 9 must remove all software components after updated versions have been installed. |
Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some adversaries. |
|
V-257796
|
Low |
RHEL 9 must enable auditing of processes that start prior to the audit daemon. |
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... |
|
V-257795
|
Low |
RHEL 9 must enable mitigations against processor-based vulnerabilities. |
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 |
|
V-257782
|
Low |
RHEL 9 must enable the hardware random number generator entropy gatherer service. |
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... |