| Finding ID |
Severity |
Title |
Description |
|
V-268322
|
High |
RHEL 8 must not allow blank or null passwords in the system-auth file. |
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. |
|
V-251706
|
High |
The RHEL 8 operating system must not have accounts configured with blank or null 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. |
|
V-244541
|
High |
RHEL 8 must not allow blank or null passwords in the password-auth file. |
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. |
|
V-230558
|
High |
A File Transfer Protocol (FTP) server package must not be installed unless mission essential on RHEL 8. |
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-230534
|
High |
The root account must be the only account having unrestricted access to the RHEL 8 system. |
If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account. |
|
V-230533
|
High |
The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for RHEL 8 operational support. |
If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established. |
|
V-230531
|
High |
The systemd Ctrl-Alt-Delete burst key sequence in RHEL 8 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-230530
|
High |
The x86 Ctrl-Alt-Delete key sequence in RHEL 8 must be disabled if a graphical user interface is installed. |
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-230529
|
High |
The x86 Ctrl-Alt-Delete key sequence must be disabled on RHEL 8. |
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-230492
|
High |
RHEL 8 must not have the rsh-server 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-230487
|
High |
RHEL 8 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 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-230380
|
High |
RHEL 8 must not allow accounts configured with blank or null 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. |
|
V-230329
|
High |
Unattended or automatic logon via the RHEL 8 graphical user interface must not be allowed. |
Failure to restrict system access to authenticated users negatively impacts operating system security. |
|
V-230284
|
High |
There must be no .shosts files on the RHEL 8 operating system. |
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-230283
|
High |
There must be no shosts.equiv files on the RHEL 8 operating system. |
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-230265
|
High |
RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. |
Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed... |
|
V-230264
|
High |
RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. |
Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed... |
|
V-230235
|
High |
RHEL 8 operating systems booted with a BIOS must require authentication upon booting into single-user and maintenance modes. |
If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password... |
|
V-230234
|
High |
RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user mode and maintenance. |
If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password... |
|
V-230224
|
High |
All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. |
RHEL 8 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-230223
|
High |
RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
Use of weak or untested encryption algorithms undermines the purposes of using 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.
RHEL 8 utilizes GRUB 2 as the... |
|
V-230221
|
High |
RHEL 8 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-257258
|
Medium |
RHEL 8.7 and higher 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-256974
|
Medium |
RHEL 8 must be configured to allow sending email notifications of unauthorized configuration changes to designated personnel. |
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-256973
|
Medium |
RHEL 8 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-255924
|
Medium |
RHEL 8 SSH server must be configured to use only FIPS-validated key exchange algorithms. |
Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection.
RHEL 8 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed... |
|
V-254520
|
Medium |
RHEL 8 must prevent nonprivileged users from executing privileged functions, including disabling, circumventing, or altering implemented security safeguards/countermeasures. |
Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Nonprivileged users are individuals who do not possess appropriate authorizations.... |
|
V-251718
|
Medium |
The graphical display manager must not be the default target on RHEL 8 unless approved. |
Internet services that are not required for system or application processes must not be active 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-251716
|
Medium |
RHEL 8 systems, version 8.4 and above, must ensure the password complexity module 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-251715
|
Medium |
RHEL 8 systems below version 8.4 must ensure the password complexity module in the password-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-251714
|
Medium |
RHEL 8 systems below version 8.4 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-251713
|
Medium |
RHEL 8 must ensure the password complexity module is enabled in the system-auth file. |
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-251712
|
Medium |
The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation. |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate.
Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158 |
|
V-251711
|
Medium |
RHEL 8 must specify the default "include" directory for the /etc/sudoers file. |
The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used to configure authorized "sudo" users as well as the programs they are allowed to run. Some configuration options in the "/etc/sudoers" file allow configured users to run... |
|
V-251710
|
Medium |
The RHEL 8 operating system must use a file integrity tool to verify correct operation of all security functions. |
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-251709
|
Medium |
RHEL 8 library directories must be group-owned by root or a system account. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-251708
|
Medium |
RHEL 8 library directories must be owned by root. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-251707
|
Medium |
RHEL 8 library directories must have mode 755 or less permissive. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-250317
|
Medium |
RHEL 8 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 software is used when not required, system network information may be unnecessarily transmitted across the network.
The sysctl --system command will load settings from all system configuration files. All configuration files are... |
|
V-250316
|
Medium |
RHEL 8 systems below version 8.2 must configure SELinux context type to allow the use of a non-default faillock tally directory. |
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.
From "Pam_Faillock" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot... |
|
V-250315
|
Medium |
RHEL 8 systems, versions 8.2 and above, must configure SELinux context type to allow the use of a non-default faillock tally directory. |
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.
From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot... |
|
V-244554
|
Medium |
RHEL 8 must enable hardening for the Berkeley Packet Filter Just-in-time compiler. |
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.
Enabling hardening for the Berkeley Packet Filter... |
|
V-244553
|
Medium |
RHEL 8 must ignore 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.
The sysctl --system command will load settings from all... |
|
V-244552
|
Medium |
RHEL 8 must not forward IPv4 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-244551
|
Medium |
RHEL 8 must not forward IPv4 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-244550
|
Medium |
RHEL 8 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.
The sysctl --system command will load settings from all... |
|
V-244549
|
Medium |
All RHEL 8 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-244548
|
Medium |
RHEL 8 must enable the USBGuard. |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers.
A new feature that RHEL 8 provides is the USBGuard software framework. The USBguard-daemon is the main component of the... |
|
V-244547
|
Medium |
RHEL 8 must have the USBGuard installed. |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers.
A new feature that RHEL 8 provides is the USBGuard software framework. The USBguard-daemon is the main component of the... |
|
V-244546
|
Medium |
The RHEL 8 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 whitelisting.
Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized... |
|
V-244545
|
Medium |
The RHEL 8 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 whitelisting.
Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized... |
|
V-244544
|
Medium |
A firewall must be active on RHEL 8. |
"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-244543
|
Medium |
RHEL 8 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-244542
|
Medium |
RHEL 8 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of 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.
Audit record content that may be necessary to satisfy this requirement includes, for... |
|
V-244539
|
Medium |
RHEL 8 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-244538
|
Medium |
RHEL 8 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 log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating... |
|
V-244536
|
Medium |
RHEL 8 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-244535
|
Medium |
RHEL 8 must initiate a session lock for graphical user interfaces when the screensaver is activated. |
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-244534
|
Medium |
RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. |
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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-244533
|
Medium |
RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. |
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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-244532
|
Medium |
RHEL 8 must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member. |
If a local interactive user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them. |
|
V-244531
|
Medium |
All RHEL 8 local interactive user home directory files 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-244530
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative... |
|
V-244529
|
Medium |
RHEL 8 must use a separate file system for /var/tmp. |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-244528
|
Medium |
The RHEL 8 SSH daemon must not allow GSSAPI authentication, except to fulfill documented and validated mission requirements. |
Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. |
|
V-244526
|
Medium |
The RHEL 8 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, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-244525
|
Medium |
RHEL 8 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-244524
|
Medium |
The RHEL 8 pam_unix.so module must be configured in the system-auth file to use a FIPS 140-2 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 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is... |
|
V-244523
|
Medium |
RHEL 8 operating systems must require authentication upon booting into emergency mode. |
If the system does not require valid root authentication before it boots into emergency or rescue mode, anyone who invokes emergency or rescue mode is granted privileged access to all files on the system. |
|
V-244522
|
Medium |
RHEL 8 operating systems booted with a BIOS must require a unique superusers name upon booting into single-user and maintenance modes. |
If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password... |
|
V-244521
|
Medium |
RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require a unique superusers name upon booting into single-user mode and maintenance. |
If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password... |
|
V-244519
|
Medium |
RHEL 8 must display a 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-237643
|
Medium |
RHEL 8 must require re-authentication when using the "sudo" command. |
Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the capability to escalate a functional capability, it is critical the organization requires the user to re-authenticate when using the "sudo" command.
If the value is set to an integer... |
|
V-237642
|
Medium |
RHEL 8 must use the invoking user's password for privilege escalation when using "sudo". |
The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates the invoking user's credentials. 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... |
|
V-237641
|
Medium |
RHEL 8 must restrict privilege elevation to authorized personnel. |
The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your request to execute a command by checking a file, called sudoers. If the "sudoers" file is not configured correctly, any user defined on the system can initiate... |
|
V-237640
|
Medium |
The krb5-server package must not be installed on RHEL 8. |
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 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
Currently, Kerberos does... |
|
V-230561
|
Medium |
The tuned package must not be installed unless mission essential on RHEL 8. |
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-230560
|
Medium |
The iprutils package must not be installed unless mission essential on RHEL 8. |
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-230559
|
Medium |
The gssproxy package must not be installed unless mission essential on RHEL 8. |
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-230557
|
Medium |
If the Trivial File Transfer Protocol (TFTP) server is required, the RHEL 8 TFTP daemon must be configured to operate in secure mode. |
Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files. |
|
V-230556
|
Medium |
The RHEL 8 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 DIPSLAY environment variable... |
|
V-230555
|
Medium |
RHEL 8 remote X connections for interactive users must be disabled unless to fulfill documented and validated mission requirements. |
The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator may have a stance in which they want to protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding,... |
|
V-230554
|
Medium |
RHEL 8 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-230553
|
Medium |
The graphical display manager must not be installed on RHEL 8 unless approved. |
Internet services that are not required for system or application processes must not be active 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-230550
|
Medium |
RHEL 8 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-230549
|
Medium |
RHEL 8 must use reverse path filtering on all IPv4 interfaces. |
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.
The sysctl --system command will load settings... |
|
V-230548
|
Medium |
RHEL 8 must disable the use of user namespaces. |
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.
The sysctl --system command will load settings... |
|
V-230547
|
Medium |
RHEL 8 must restrict exposed kernel pointer addresses access. |
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.
The sysctl --system command will load settings... |
|
V-230546
|
Medium |
RHEL 8 must restrict usage of ptrace to descendant processes. |
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.
The sysctl --system command will load settings... |
|
V-230545
|
Medium |
RHEL 8 must disable access to network bpf syscall from unprivileged processes. |
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.
The sysctl --system command will load settings... |
|
V-230544
|
Medium |
RHEL 8 must ignore IPv6 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.
The sysctl --system command will load settings from all... |
|
V-230543
|
Medium |
RHEL 8 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.
There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version... |
|
V-230542
|
Medium |
RHEL 8 must not accept router advertisements on all IPv6 interfaces by default. |
Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
An illicit router advertisement message could result in a man-in-the-middle attack.
The sysctl --system command will... |
|
V-230541
|
Medium |
RHEL 8 must not accept router advertisements on all IPv6 interfaces. |
Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
An illicit router advertisement message could result in a man-in-the-middle attack.
The sysctl --system command will... |
|
V-230540
|
Medium |
RHEL 8 must not enable IPv6 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 software is used when not required, system network information may be unnecessarily transmitted across the network.
The sysctl --system command will load settings from all system configuration files. All configuration files are... |
|
V-230539
|
Medium |
RHEL 8 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-230538
|
Medium |
RHEL 8 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-230537
|
Medium |
RHEL 8 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.
There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). IPv6 does not implement the same method of broadcast as IPv4. Instead, IPv6 uses multicast addressing to the all-hosts... |
|
V-230536
|
Medium |
RHEL 8 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.
There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version... |
|
V-230535
|
Medium |
RHEL 8 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.
The sysctl --system command will load settings from all... |
|
V-230532
|
Medium |
The debug-shell systemd service must be disabled on RHEL 8. |
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-230527
|
Medium |
RHEL 8 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-230526
|
Medium |
All RHEL 8 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-230525
|
Medium |
A firewall must be able to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring RHEL 8 can implement rate-limiting measures on impacted network interfaces. |
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 8 to mitigate the impact of DoS attacks that have occurred or are ongoing... |
|
V-230524
|
Medium |
RHEL 8 must block unauthorized peripherals before establishing a connection. |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but are not limited to, such devices as flash drives, external storage, and printers.
A new feature that RHEL 8 provides is the USBGuard software framework. The USBguard-daemon is the main component of the... |
|
V-230523
|
Medium |
The RHEL 8 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 whitelisting.
Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized... |
|
V-230522
|
Medium |
RHEL 8 must mount /var/tmp with the noexec option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230521
|
Medium |
RHEL 8 must mount /var/tmp with the nosuid option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230520
|
Medium |
RHEL 8 must mount /var/tmp with the nodev option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230519
|
Medium |
RHEL 8 must mount /var/log/audit with the noexec option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230518
|
Medium |
RHEL 8 must mount /var/log/audit with the nosuid option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230517
|
Medium |
RHEL 8 must mount /var/log/audit with the nodev option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230516
|
Medium |
RHEL 8 must mount /var/log with the noexec option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230515
|
Medium |
RHEL 8 must mount /var/log with the nosuid option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230514
|
Medium |
RHEL 8 must mount /var/log with the nodev option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230513
|
Medium |
RHEL 8 must mount /tmp with the noexec option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230512
|
Medium |
RHEL 8 must mount /tmp with the nosuid option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230511
|
Medium |
RHEL 8 must mount /tmp with the nodev option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230510
|
Medium |
RHEL 8 must mount /dev/shm with the noexec option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230509
|
Medium |
RHEL 8 must mount /dev/shm with the nosuid option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230508
|
Medium |
RHEL 8 must mount /dev/shm with the nodev option. |
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 whitelisting.
The "noexec" mount option causes the system to not execute binary files. This option must... |
|
V-230507
|
Medium |
RHEL 8 Bluetooth must be disabled. |
Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the RHEL 8 operating system.
This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 8 systems.... |
|
V-230506
|
Medium |
RHEL 8 wireless network adapters must be disabled. |
Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the RHEL 8 operating system.
This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 8 systems.... |
|
V-230505
|
Medium |
A firewall must be installed on RHEL 8. |
"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-230504
|
Medium |
A RHEL 8 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 8 incorporates the "firewalld" daemon, which allows for many different configurations. One of these configurations is zones. Zones can be utilized to... |
|
V-230503
|
Medium |
RHEL 8 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 |
|
V-230502
|
Medium |
The RHEL 8 file system automounter must be disabled unless required. |
Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity. |
|
V-230500
|
Medium |
RHEL 8 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 physical and logical ports/protocols on information systems.
Operating systems are capable of providing a wide variety of functions and services. Some... |
|
V-230493
|
Medium |
RHEL 8 must cover or disable the built-in or attached camera when not in use. |
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 from collaborative computing devices... |
|
V-230489
|
Medium |
RHEL 8 must not have the sendmail 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-230488
|
Medium |
RHEL 8 must not have any automated bug reporting tools 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-230484
|
Medium |
RHEL 8 must securely compare internal information system clocks at least every 24 hours with a server synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). |
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-230483
|
Medium |
RHEL 8 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-230482
|
Medium |
RHEL 8 must authenticate the remote logging server for off-loading audit logs. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230481
|
Medium |
RHEL 8 must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230480
|
Medium |
RHEL 8 must take appropriate action when the internal event queue is full. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230479
|
Medium |
The RHEL 8 audit records must be off-loaded onto a different system or storage media from the system being audited. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230478
|
Medium |
RHEL 8 must have the packages required for encrypting offloaded audit logs installed. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230477
|
Medium |
RHEL 8 must have the packages required for offloading audit logs installed. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
RHEL 8 installation media provides "rsyslogd". "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain... |
|
V-230476
|
Medium |
RHEL 8 must allocate audit record storage capacity to store at least one week of audit records, when audit records are not immediately sent to a central audit record storage facility. |
To ensure RHEL 8 systems have a sufficient storage capacity in which to write the audit logs, RHEL 8 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 8. |
|
V-230475
|
Medium |
RHEL 8 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-230474
|
Medium |
RHEL 8 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 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing... |
|
V-230473
|
Medium |
RHEL 8 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 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing... |
|
V-230472
|
Medium |
RHEL 8 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 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing... |
|
V-230471
|
Medium |
RHEL 8 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-230467
|
Medium |
Successful/unsuccessful modifications to the lastlog file in RHEL 8 must generate an audit record. |
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.
Audit records can be generated from various components within the information system (e.g., module or policy filter).
The list of audited events... |
|
V-230466
|
Medium |
Successful/unsuccessful modifications to the faillock log file in RHEL 8 must generate an audit record. |
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.
Audit records can be generated from various components within the information system (e.g., module or policy filter).
The list of audited events... |
|
V-230465
|
Medium |
Successful/unsuccessful uses of the kmod command in RHEL 8 must generate an audit record. |
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.
Audit records can be generated from various components within the information system (e.g., module or policy filter). The "kmod" command is used... |
|
V-230464
|
Medium |
Successful/unsuccessful uses of the chacl command in RHEL 8 must generate an audit record. |
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-230463
|
Medium |
Successful/unsuccessful uses of the usermod command in RHEL 8 must generate an audit record. |
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-230462
|
Medium |
Successful/unsuccessful uses of the sudo command in RHEL 8 must generate an audit record. |
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-230456
|
Medium |
Successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls in RHEL 8 must generate an audit record. |
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-230455
|
Medium |
Successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls in RHEL 8 must generate an audit record. |
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-230449
|
Medium |
Successful/unsuccessful uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls in RHEL 8 must generate an audit record. |
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-230448
|
Medium |
Successful/unsuccessful uses of the chsh command in RHEL 8 must generate an audit record. |
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-230447
|
Medium |
Successful/unsuccessful uses of the crontab command in RHEL 8 must generate an audit record. |
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-230446
|
Medium |
Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record. |
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-230444
|
Medium |
Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record. |
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-230439
|
Medium |
Successful/unsuccessful uses of the rename, unlink, rmdir, renameat, and unlinkat system calls in RHEL 8 must generate an audit record. |
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-230438
|
Medium |
Successful/unsuccessful uses of the init_module and finit_module system calls in RHEL 8 must generate an audit record. |
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-230437
|
Medium |
Successful/unsuccessful uses of the newgrp command in RHEL 8 must generate an audit record. |
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-230436
|
Medium |
Successful/unsuccessful uses of the pam_timestamp_check command in RHEL 8 must generate an audit record. |
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-230435
|
Medium |
Successful/unsuccessful uses of the setfacl command in RHEL 8 must generate an audit record. |
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-230434
|
Medium |
Successful/unsuccessful uses of the ssh-keysign in RHEL 8 must generate an audit record. |
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-230433
|
Medium |
Successful/unsuccessful uses of unix_chkpwd in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230432
|
Medium |
Successful/unsuccessful uses of setsebool in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230431
|
Medium |
Successful/unsuccessful uses of userhelper in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230430
|
Medium |
Successful/unsuccessful uses of setfiles in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230429
|
Medium |
Successful/unsuccessful uses of semanage in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230428
|
Medium |
Successful/unsuccessful uses of postqueue in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230427
|
Medium |
Successful/unsuccessful uses of postdrop in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230426
|
Medium |
Successful/unsuccessful uses of the unix_update in RHEL 8 must generate an audit record. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-230425
|
Medium |
Successful/unsuccessful uses of the mount syscall in RHEL 8 must generate an audit record. |
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-230424
|
Medium |
Successful/unsuccessful uses of the umount command in RHEL 8 must generate an audit record. |
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-230423
|
Medium |
Successful/unsuccessful uses of the mount command in RHEL 8 must generate an audit record. |
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-230422
|
Medium |
Successful/unsuccessful uses of the passwd command in RHEL 8 must generate an audit record. |
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-230421
|
Medium |
Successful/unsuccessful uses of the ssh-agent in RHEL 8 must generate an audit record. |
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-230419
|
Medium |
Successful/unsuccessful uses of the chcon command in RHEL 8 must generate an audit record. |
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-230418
|
Medium |
Successful/unsuccessful uses of the chage command in RHEL 8 must generate an audit record. |
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-230413
|
Medium |
The RHEL 8 audit system must be configured to audit any usage 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-230412
|
Medium |
Successful/unsuccessful uses of the su command in RHEL 8 must generate an audit record. |
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-230411
|
Medium |
The RHEL 8 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-230410
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/. |
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-230409
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers. |
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-230408
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. |
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-230407
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. |
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-230406
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. |
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-230405
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd. |
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-230404
|
Medium |
RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. |
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-230403
|
Medium |
RHEL 8 audit system must protect logon UIDs 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 8 system activity.
In immutable mode, unauthorized users cannot execute changes to the audit system to... |
|
V-230402
|
Medium |
RHEL 8 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 8 system activity.
In immutable mode, unauthorized users cannot execute changes to the audit system to... |
|
V-230401
|
Medium |
RHEL 8 audit log directory must have a mode of 0700 or less permissive to prevent unauthorized read access. |
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 8 system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-230400
|
Medium |
RHEL 8 audit log directory must be group-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.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-230399
|
Medium |
RHEL 8 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.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-230398
|
Medium |
RHEL 8 audit logs must be group-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.
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-230397
|
Medium |
RHEL 8 audit logs must be owned by root to prevent unauthorized read access. |
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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230396
|
Medium |
RHEL 8 audit logs must have a mode of 0600 or less permissive to prevent unauthorized read access. |
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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230394
|
Medium |
RHEL 8 must label all off-loaded audit logs before sending them to the central log server. |
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-230393
|
Medium |
The RHEL 8 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.
Audit record content that may be necessary to satisfy this requirement includes, for... |
|
V-230392
|
Medium |
The RHEL 8 audit system must take appropriate action when the audit storage volume is full. |
It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend... |
|
V-230390
|
Medium |
The RHEL 8 System must take appropriate action when an 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-230389
|
Medium |
The RHEL 8 Information System Security Officer (ISSO) and System Administrator (SA) (at a minimum) must have mail aliases to be notified 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-230388
|
Medium |
The RHEL 8 System Administrator (SA) and 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-230387
|
Medium |
Cron logging must be implemented in RHEL 8. |
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-230386
|
Medium |
The RHEL 8 audit system must be configured to audit the execution of privileged functions and prevent all software from executing at higher privilege levels than users executing the software. |
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-230385
|
Medium |
RHEL 8 must define default permissions for logon and non-logon shells. |
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-230384
|
Medium |
RHEL 8 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-230383
|
Medium |
RHEL 8 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-230382
|
Medium |
RHEL 8 must display the date and time of the last successful account logon upon an SSH logon. |
Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use. |
|
V-230379
|
Medium |
RHEL 8 must not have unnecessary 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-230378
|
Medium |
RHEL 8 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. |
Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in... |
|
V-230377
|
Medium |
RHEL 8 must prevent the use of dictionary words for passwords. |
If RHEL 8 allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks. |
|
V-230376
|
Medium |
RHEL 8 must prohibit the use of cached authentications after one day. |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
RHEL 8 includes multiple options for configuring authentication, but this requirement will be focus on the System Security Services Daemon (SSSD). By default sssd does not cache credentials. |
|
V-230375
|
Medium |
All RHEL 8 passwords must contain at least one special character. |
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-230374
|
Medium |
RHEL 8 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-230373
|
Medium |
RHEL 8 account identifiers (individuals, groups, roles, and devices) must be disabled 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. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
RHEL 8 needs to track periods of inactivity and... |
|
V-230372
|
Medium |
RHEL 8 must implement smart card logon for multifactor authentication for access to interactive accounts. |
Using an authentication device, such as a Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
Multifactor solutions that require devices separate from information systems gaining... |
|
V-230371
|
Medium |
RHEL 8 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.
Interactive users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Interactive users (and processes acting on behalf of users)... |
|
V-230370
|
Medium |
RHEL 8 passwords for new users must have 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-230369
|
Medium |
RHEL 8 passwords must have 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-230367
|
Medium |
RHEL 8 user account passwords must be configured so that existing passwords are restricted to a 60-day maximum lifetime. |
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If RHEL 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised. |
|
V-230366
|
Medium |
RHEL 8 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 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised. |
|
V-230365
|
Medium |
RHEL 8 passwords for new users or password changes must have a 24 hours/1 day 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, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password... |
|
V-230364
|
Medium |
RHEL 8 passwords must have a 24 hours/1 day 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-230363
|
Medium |
RHEL 8 must require the change of at least 8 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-230362
|
Medium |
RHEL 8 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-230361
|
Medium |
RHEL 8 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-230360
|
Medium |
RHEL 8 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-230359
|
Medium |
RHEL 8 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-230358
|
Medium |
RHEL 8 must enforce password complexity by requiring that at least one lower-case 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-230357
|
Medium |
RHEL 8 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-230356
|
Medium |
RHEL 8 must ensure the password complexity module is enabled in the password-auth file. |
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-230355
|
Medium |
RHEL 8 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.
There are various methods of mapping certificates to user/group accounts for RHEL 8. For the purposes of this requirement, the... |
|
V-230354
|
Medium |
RHEL 8 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 log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating... |
|
V-230352
|
Medium |
RHEL 8 must automatically lock graphical user sessions after 15 minutes of inactivity. |
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-230351
|
Medium |
RHEL 8 must be able to initiate directly a session lock for all connection types using smartcard when the smartcard 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-230347
|
Medium |
RHEL 8 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-230345
|
Medium |
RHEL 8 must include root when automatically locking an account until the locked 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, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230344
|
Medium |
RHEL 8 must include root when automatically locking an account until the locked 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, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230343
|
Medium |
RHEL 8 must log user name information when 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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230342
|
Medium |
RHEL 8 must log user name information when 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.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230341
|
Medium |
RHEL 8 must prevent system messages from being presented 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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230340
|
Medium |
RHEL 8 must prevent system messages from being presented 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.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230339
|
Medium |
RHEL 8 must ensure account lockouts persist. |
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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230338
|
Medium |
RHEL 8 must ensure account lockouts persist. |
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.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230337
|
Medium |
RHEL 8 must automatically lock an account until the locked 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, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230336
|
Medium |
RHEL 8 must automatically lock an account until the locked 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, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230335
|
Medium |
RHEL 8 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-force attacks, is reduced. Limits are imposed by locking the account.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230334
|
Medium |
RHEL 8 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-force attacks, is reduced. Limits are imposed by locking the account.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230333
|
Medium |
RHEL 8 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.
In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced... |
|
V-230332
|
Medium |
RHEL 8 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.
RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may... |
|
V-230331
|
Medium |
RHEL 8 temporary user accounts must be provisioned with an expiration time of 72 hours or less. |
If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.
Temporary accounts are established as part of normal account activation... |
|
V-230330
|
Medium |
RHEL 8 must not allow users to override SSH environment variables. |
SSH environment options potentially allow users to bypass access restriction in some configurations. |
|
V-230328
|
Medium |
A separate RHEL 8 filesystem must be used for user home directories (such as /home or an equivalent). |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-230327
|
Medium |
All RHEL 8 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-230326
|
Medium |
All RHEL 8 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 un-owned files. |
|
V-230325
|
Medium |
All RHEL 8 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-230324
|
Medium |
All RHEL 8 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-230323
|
Medium |
All RHEL 8 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-230322
|
Medium |
All RHEL 8 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 user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should. |
|
V-230321
|
Medium |
All RHEL 8 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-230320
|
Medium |
All RHEL 8 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-230319
|
Medium |
All RHEL 8 world-writable directories must be group-owned by root, sys, bin, or an application group. |
If a world-writable directory is not group-owned by root, sys, bin, or an application Group Identifier (GID), 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-230318
|
Medium |
All RHEL 8 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-230317
|
Medium |
Executable search paths within the initialization files of all local interactive RHEL 8 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 user's home directory), executables in these directories may be executed instead of system commands. This variable is... |
|
V-230316
|
Medium |
For RHEL 8 systems using Domain Name Servers (DNS) resolution, at least two name servers must be 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-230315
|
Medium |
RHEL 8 must disable core dump backtraces. |
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.
A core dump includes a memory image... |
|
V-230314
|
Medium |
RHEL 8 must disable storing core dumps. |
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.
A core dump includes a memory image... |
|
V-230313
|
Medium |
RHEL 8 must disable core dumps for all users. |
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.
A core dump includes a memory image... |
|
V-230312
|
Medium |
RHEL 8 must disable acquiring, saving, and processing core dumps. |
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.
A core dump includes a memory image... |
|
V-230311
|
Medium |
RHEL 8 must disable the kernel.core_pattern. |
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.
The sysctl --system command will load settings... |
|
V-230310
|
Medium |
RHEL 8 must disable kernel dumps unless needed. |
Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may 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.
RHEL 8 installation media... |
|
V-230309
|
Medium |
Local RHEL 8 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-230308
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative... |
|
V-230307
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative access. |
|
V-230306
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative access. |
|
V-230305
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative... |
|
V-230304
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative access. |
|
V-230303
|
Medium |
RHEL 8 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 block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. |
|
V-230302
|
Medium |
RHEL 8 must prevent code from being executed on file systems that contain user home directories. |
The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. |
|
V-230301
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative access. The only legitimate location for device files is the /dev directory located on the... |
|
V-230300
|
Medium |
RHEL 8 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 unprivileged users to attain unauthorized administrative... |
|
V-230299
|
Medium |
RHEL 8 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 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 unprivileged users to attain unauthorized administrative... |
|
V-230298
|
Medium |
The rsyslog service must be running in RHEL 8. |
Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-230296
|
Medium |
RHEL 8 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 on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system. |
|
V-230295
|
Medium |
A separate RHEL 8 filesystem must be used for the /tmp directory. |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-230291
|
Medium |
The RHEL 8 SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements. |
Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use unused methods of authentication, even in the event of misconfiguration elsewhere. |
|
V-230290
|
Medium |
The RHEL 8 SSH daemon must not allow authentication using known host’s authentication. |
Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere. |
|
V-230288
|
Medium |
The RHEL 8 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 on to the system as another user. |
|
V-230287
|
Medium |
The RHEL 8 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-230286
|
Medium |
The RHEL 8 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-230282
|
Medium |
RHEL 8 must enable the SELinux targeted policy. |
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-230280
|
Medium |
RHEL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. |
Some adversaries launch attacks with the intent of executing code in non-executable 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-230279
|
Medium |
RHEL 8 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-230278
|
Medium |
RHEL 8 must disable virtual syscalls. |
Syscalls are special routines in the Linux kernel, which userspace applications ask to do privileged tasks. Invoking a system call is an expensive operation because the processor must interrupt the currently executing task and switch context to kernel mode and then back to userspace after the system call completes. Virtual... |
|
V-230277
|
Medium |
RHEL 8 must clear the page allocator to prevent use-after-free attacks. |
Some adversaries launch attacks with the intent of executing code in non-executable 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-230276
|
Medium |
RHEL 8 must implement non-executable data to protect its memory from unauthorized code execution. |
Some adversaries launch attacks with the intent of executing code in non-executable 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-230275
|
Medium |
RHEL 8 must accept Personal Identity Verification (PIV) credentials. |
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-230274
|
Medium |
RHEL 8 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-230273
|
Medium |
RHEL 8 must have the packages required for multifactor authentication installed. |
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-230272
|
Medium |
RHEL 8 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 the user reauthenticate.
Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158 |
|
V-230271
|
Medium |
RHEL 8 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 the user reauthenticate.
Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158 |
|
V-230268
|
Medium |
RHEL 8 must enable kernel parameters to enforce discretionary access control on hardlinks. |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via... |
|
V-230267
|
Medium |
RHEL 8 must enable kernel parameters to enforce discretionary access control on symlinks. |
Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via... |
|
V-230266
|
Medium |
RHEL 8 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-230263
|
Medium |
The RHEL 8 file integrity tool must notify the system administrator when changes to the baseline configuration or anomalies in the operation of any security functions are discovered within an organizationally defined frequency. |
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-230262
|
Medium |
RHEL 8 library files must be group-owned by root or a system account. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230261
|
Medium |
RHEL 8 library files must be owned by root. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230260
|
Medium |
RHEL 8 library files must have mode 755 or less permissive. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230259
|
Medium |
RHEL 8 system commands must be group-owned by root or a system account. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230258
|
Medium |
RHEL 8 system commands must be owned by root. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230257
|
Medium |
RHEL 8 system commands must have mode 755 or less permissive. |
If RHEL 8 were to allow 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 8 with software libraries that are accessible and configurable,... |
|
V-230256
|
Medium |
The RHEL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Transport Layer Security (TLS) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring... |
|
V-230255
|
Medium |
The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-230254
|
Medium |
The RHEL 8 operating system must implement DoD-approved encryption in the OpenSSL package. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-230252
|
Medium |
The RHEL 8 operating system must implement DOD-approved encryption 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-230251
|
Medium |
The RHEL 8 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. |
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-230250
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230249
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230248
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230247
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230246
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230245
|
Medium |
The RHEL 8 /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 8 system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized... |
|
V-230244
|
Medium |
RHEL 8 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-230243
|
Medium |
A sticky bit must be set on all RHEL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. |
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-230240
|
Medium |
RHEL 8 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-230239
|
Medium |
The krb5-workstation package must not be installed on RHEL 8. |
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 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
Currently, Kerberos does... |
|
V-230238
|
Medium |
RHEL 8 must prevent system daemons from using Kerberos for 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 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
The key derivation... |
|
V-230237
|
Medium |
The RHEL 8 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-2 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 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is... |
|
V-230236
|
Medium |
RHEL 8 operating systems must require authentication upon booting into rescue mode. |
If the system does not require valid root authentication before it boots into emergency or rescue mode, anyone who invokes emergency or rescue mode is granted privileged access to all files on the system. |
|
V-230233
|
Medium |
The RHEL 8 shadow password suite must be configured to use a sufficient number of hashing rounds. |
The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not... |
|
V-230232
|
Medium |
RHEL 8 must employ FIPS 140-2 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. |
|
V-230231
|
Medium |
RHEL 8 must encrypt all stored passwords with a FIPS 140-2 approved cryptographic hashing algorithm. |
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.
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot... |
|
V-230230
|
Medium |
RHEL 8, for certificate-based authentication, must enforce authorized access to the corresponding private key. |
If an unauthorized user obtains access to a private key without a passcode, that user would have unauthorized access to any system where the associated public key has been installed. |
|
V-230229
|
Medium |
RHEL 8, 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-230228
|
Medium |
All RHEL 8 remote access methods must be monitored. |
Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-230227
|
Medium |
RHEL 8 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 logon interfaces with human users... |
|
V-230226
|
Medium |
RHEL 8 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-230225
|
Medium |
RHEL 8 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a ssh logon. |
|
|
V-230222
|
Medium |
RHEL 8 vendor packaged system security patches and updates must be installed and up to date. |
Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced System Administrators... |
|
V-244527
|
Low |
RHEL 8 must have the packages required to use 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... |
|
V-230552
|
Low |
The RHEL 8 file integrity tool must be configured to verify Access Control Lists (ACLs). |
ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.
RHEL 8 installation media come with a file integrity tool, Advanced Intrusion Detection Environment (AIDE). |
|
V-230551
|
Low |
The RHEL 8 file integrity tool must be configured to verify extended attributes. |
Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.
RHEL 8 installation media come with a file integrity tool, Advanced Intrusion Detection Environment (AIDE). |
|
V-230499
|
Low |
RHEL 8 must disable IEEE 1394 (FireWire) Support. |
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.
The IEEE 1394 (FireWire) is a serial... |
|
V-230498
|
Low |
RHEL 8 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-230497
|
Low |
RHEL 8 must disable the transparent inter-process communication (TIPC) protocol. |
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-230496
|
Low |
RHEL 8 must disable the stream control transmission protocol (SCTP). |
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-230495
|
Low |
RHEL 8 must disable the controller area network (CAN) protocol. |
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-230494
|
Low |
RHEL 8 must disable the asynchronous transfer mode (ATM) protocol. |
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-230491
|
Low |
RHEL 8 must enable mitigations against processor-based vulnerabilities. |
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-230486
|
Low |
RHEL 8 must disable network management of the chrony daemon. |
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.
Not exposing... |
|
V-230485
|
Low |
RHEL 8 must disable the chrony daemon from acting as a server. |
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.
Minimizing the... |
|
V-230470
|
Low |
RHEL 8 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-230469
|
Low |
RHEL 8 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-230468
|
Low |
RHEL 8 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-230395
|
Low |
RHEL 8 must resolve audit information before writing to disk. |
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-230381
|
Low |
RHEL 8 must display the date and time of the last successful account logon upon logon. |
Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. |
|
V-230346
|
Low |
RHEL 8 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 DoS attacks.
This requirement addresses concurrent sessions for information system accounts and... |
|
V-230294
|
Low |
RHEL 8 must use a separate file system for the system audit data path. |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-230293
|
Low |
RHEL 8 must use a separate file system for /var/log. |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-230292
|
Low |
RHEL 8 must use a separate file system for /var. |
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
|
V-230285
|
Low |
RHEL 8 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... |
|
V-230281
|
Low |
YUM must remove all software components after updated versions have been installed on RHEL 8. |
Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system. |
|
V-230270
|
Low |
RHEL 8 must prevent kernel profiling by unprivileged 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-230269
|
Low |
RHEL 8 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-230253
|
Low |
RHEL 8 must ensure the SSH server uses strong entropy. |
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... |
|
V-230241
|
Low |
RHEL 8 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... |