Red Hat Enterprise Linux 8 Security Technical Implementation Guide

Description

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R1

Published: 2020-11-25

Updated At: 2021-02-04 18:25:15

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-230221r599732_rule RHEL-08-010000 CCI-000366 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 t
    SV-230222r599732_rule RHEL-08-010010 CCI-000366 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 prof
    SV-230223r599732_rule RHEL-08-010020 CCI-000068 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 as
    SV-230224r599732_rule RHEL-08-010030 CCI-001199 MEDIUM 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
    SV-230225r599732_rule RHEL-08-010040 CCI-000048 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. 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,
    SV-230226r599732_rule RHEL-08-010050 CCI-000048 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,
    SV-230227r599732_rule RHEL-08-010060 CCI-000048 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,
    SV-230228r599732_rule RHEL-08-010070 CCI-000067 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
    SV-230229r599732_rule RHEL-08-010090 CCI-000185 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
    SV-230230r599732_rule RHEL-08-010100 CCI-000186 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.
    SV-230231r599732_rule RHEL-08-010110 CCI-000196 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 authe
    SV-230232r599732_rule RHEL-08-010120 CCI-000196 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)
    SV-230233r599732_rule RHEL-08-010130 CCI-000196 MEDIUM RHEL 8 must employ FIPS 140-2 approved cryptographic hashing algorithms for all created passwords. 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 fo
    SV-230234r599732_rule RHEL-08-010140 CCI-000213 HIGH RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) implemented 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 RHE
    SV-230235r599732_rule RHEL-08-010150 CCI-000213 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 RHE
    SV-230236r599732_rule RHEL-08-010151 CCI-000213 MEDIUM RHEL 8 operating systems must require authentication upon booting into emergency or rescue modes. 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.
    SV-230237r599732_rule RHEL-08-010160 CCI-000803 MEDIUM The RHEL 8 pam_unix.so module must 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 requ
    SV-230238r599732_rule RHEL-08-010161 CCI-000803 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 requ
    SV-230239r599732_rule RHEL-08-010162 CCI-000803 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 requ
    SV-230240r599732_rule RHEL-08-010170 CCI-001084 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
    SV-230241r599732_rule RHEL-08-010171 CCI-001084 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
    SV-230242r599732_rule RHEL-08-010180 CCI-001090 MEDIUM All RHEL 8 public directories must be owned by root or a system account 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 bein
    SV-230243r599732_rule RHEL-08-010190 CCI-001090 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 bein
    SV-230244r599732_rule RHEL-08-010200 CCI-001133 MEDIUM RHEL 8 must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements. Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly term
    SV-230245r599732_rule RHEL-08-010210 CCI-001314 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
    SV-230246r599732_rule RHEL-08-010220 CCI-001314 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
    SV-230247r599732_rule RHEL-08-010230 CCI-001314 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
    SV-230248r599732_rule RHEL-08-010240 CCI-001314 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
    SV-230249r599732_rule RHEL-08-010250 CCI-001314 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
    SV-230250r599732_rule RHEL-08-010260 CCI-001314 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
    SV-230251r599732_rule RHEL-08-010290 CCI-001453 MEDIUM The RHEL 8 SSH daemon must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-2 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 throu
    SV-230252r599778_rule RHEL-08-010291 CCI-001453 MEDIUM The RHEL 8 operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections. Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Remote access (e.g., RDP) is access to DoD nonpublic information systems by an authorized user (or an information system) communicating throu
    SV-230253r599732_rule RHEL-08-010292 CCI-000366 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.
    SV-230254r599732_rule RHEL-08-010293 CCI-001453 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 throu
    SV-230255r599732_rule RHEL-08-010294 CCI-001453 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 throu
    SV-230256r599732_rule RHEL-08-010295 CCI-001453 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 Secu
    SV-230257r599732_rule RHEL-08-010300 CCI-001499 MEDIUM RHEL 8 system commands must have mode 0755 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
    SV-230258r599732_rule RHEL-08-010310 CCI-001499 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
    SV-230259r599732_rule RHEL-08-010320 CCI-001499 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
    SV-230260r599732_rule RHEL-08-010330 CCI-001499 MEDIUM RHEL 8 library files must have mode 0755 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
    SV-230261r599732_rule RHEL-08-010340 CCI-001499 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
    SV-230262r599732_rule RHEL-08-010350 CCI-001499 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
    SV-230263r599732_rule RHEL-08-010360 CCI-001744 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
    SV-230264r599732_rule RHEL-08-010370 CCI-001749 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, ser
    SV-230265r599732_rule RHEL-08-010371 CCI-001749 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, ser
    SV-230266r599732_rule RHEL-08-010372 CCI-001749 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 prev
    SV-230267r599732_rule RHEL-08-010373 CCI-002165 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
    SV-230268r599818_rule RHEL-08-010374 CCI-002165 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
    SV-230269r599820_rule RHEL-08-010375 CCI-001090 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 bein
    SV-230270r599823_rule RHEL-08-010376 CCI-001090 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 bein
    SV-230271r599732_rule RHEL-08-010380 CCI-002038 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-
    SV-230272r599732_rule RHEL-08-010381 CCI-002038 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-
    SV-230273r599732_rule RHEL-08-010390 CCI-001948 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.
    SV-230274r599732_rule RHEL-08-010400 CCI-001948 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.
    SV-230275r599732_rule RHEL-08-010410 CCI-001953 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
    SV-230276r599732_rule RHEL-08-010420 CCI-002824 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 sp
    SV-230277r599732_rule RHEL-08-010421 CCI-001084 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 sp
    SV-230278r599732_rule RHEL-08-010422 CCI-001084 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 mo
    SV-230279r599732_rule RHEL-08-010423 CCI-001084 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 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 sp
    SV-230280r599732_rule RHEL-08-010430 CCI-002824 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 sp
    SV-230281r599732_rule RHEL-08-010440 CCI-002617 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
    SV-230282r599732_rule RHEL-08-010450 CCI-002696 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
    SV-230283r599732_rule RHEL-08-010460 CCI-000366 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 authentica
    SV-230284r599732_rule RHEL-08-010470 CCI-000366 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
    SV-230285r599779_rule RHEL-08-010471 CCI-000366 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.
    SV-230286r599732_rule RHEL-08-010480 CCI-000366 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.
    SV-230287r599732_rule RHEL-08-010490 CCI-000366 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.
    SV-230288r599732_rule RHEL-08-010500 CCI-000366 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.
    SV-230289r599732_rule RHEL-08-010510 CCI-000366 MEDIUM The RHEL 8 SSH daemon must not allow compression or must only allow compression after successful authentication. If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.
    SV-230290r599732_rule RHEL-08-010520 CCI-000366 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.
    SV-230291r599732_rule RHEL-08-010521 CCI-000366 MEDIUM The RHEL 8 SSH daemon must not allow unused methods of authentication. 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.
    SV-230292r599732_rule RHEL-08-010540 CCI-000366 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.
    SV-230293r599732_rule RHEL-08-010541 CCI-000366 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.
    SV-230294r599732_rule RHEL-08-010542 CCI-000366 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.
    SV-230295r599732_rule RHEL-08-010543 CCI-000366 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.
    SV-230296r599732_rule RHEL-08-010550 CCI-000770 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 actio
    SV-230297r599732_rule RHEL-08-010560 CCI-000366 MEDIUM The auditd 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 postur
    SV-230298r599732_rule RHEL-08-010561 CCI-000366 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 postur
    SV-230299r599732_rule RHEL-08-010570 CCI-000366 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 s
    SV-230300r599732_rule RHEL-08-010571 CCI-000366 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 s
    SV-230301r599732_rule RHEL-08-010580 CCI-000366 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
    SV-230302r599732_rule RHEL-08-010590 CCI-000366 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 opp
    SV-230303r599732_rule RHEL-08-010600 CCI-000366 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
    SV-230304r599732_rule RHEL-08-010610 CCI-000366 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 opp
    SV-230305r599732_rule RHEL-08-010620 CCI-000366 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 s
    SV-230306r599732_rule RHEL-08-010630 CCI-000366 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 opportunit
    SV-230307r599732_rule RHEL-08-010640 CCI-000366 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
    SV-230308r599732_rule RHEL-08-010650 CCI-000366 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 s
    SV-230309r599732_rule RHEL-08-010660 CCI-000366 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, i
    SV-230310r599780_rule RHEL-08-010670 CCI-000366 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 pa
    SV-230311r599732_rule RHEL-08-010671 CCI-000366 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 ri
    SV-230312r599782_rule RHEL-08-010672 CCI-000366 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 ri
    SV-230313r599784_rule RHEL-08-010673 CCI-000366 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 ri
    SV-230314r599732_rule RHEL-08-010674 CCI-000366 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 ri
    SV-230315r599732_rule RHEL-08-010675 CCI-000366 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 ri
    SV-230316r599732_rule RHEL-08-010680 CCI-000366 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
    SV-230317r599732_rule RHEL-08-010690 CCI-000366 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 the
    SV-230318r599732_rule RHEL-08-010700 CCI-000366 MEDIUM All RHEL 8 world-writable directories must be owned by root, sys, bin, or an application group. If a world-writable directory has the sticky bit set and 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
    SV-230319r599732_rule RHEL-08-010710 CCI-000366 MEDIUM All RHEL 8 world-writable directories must be group-owned by root, sys, bin, or an application group. If a world-writable directory has the sticky bit set and 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 te
    SV-230320r599732_rule RHEL-08-010720 CCI-000366 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.
    SV-230321r599732_rule RHEL-08-010730 CCI-000366 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.
    SV-230322r599732_rule RHEL-08-010740 CCI-000366 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 th
    SV-230323r599732_rule RHEL-08-010750 CCI-000366 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
    SV-230324r599732_rule RHEL-08-010760 CCI-000366 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.
    SV-230325r599732_rule RHEL-08-010770 CCI-000366 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.
    SV-230326r599732_rule RHEL-08-010780 CCI-000366 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.
    SV-230327r599732_rule RHEL-08-010790 CCI-000366 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.
    SV-230328r599732_rule RHEL-08-010800 CCI-000366 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.
    SV-230329r599732_rule RHEL-08-010820 CCI-000366 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.
    SV-230330r599732_rule RHEL-08-010830 CCI-000366 MEDIUM Unattended or automatic logon to RHEL 8 via ssh must not be allowed. Failure to restrict system access to authenticated users negatively impacts RHEL 8 security.
    SV-230331r599824_rule RHEL-08-020000 CCI-000016 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. T
    SV-230332r599827_rule RHEL-08-020010 CCI-000044 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" fo
    SV-230333r599828_rule RHEL-08-020011 CCI-000044 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.con
    SV-230334r599829_rule RHEL-08-020012 CCI-000044 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" fo
    SV-230335r599830_rule RHEL-08-020013 CCI-000044 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.con
    SV-230336r599831_rule RHEL-08-020014 CCI-000044 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" fo
    SV-230337r599832_rule RHEL-08-020015 CCI-000044 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.con
    SV-230338r599833_rule RHEL-08-020016 CCI-000044 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" fo
    SV-230339r599834_rule RHEL-08-020017 CCI-000044 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.con
    SV-230340r599835_rule RHEL-08-020018 CCI-000044 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" fo
    SV-230341r599836_rule RHEL-08-020019 CCI-000044 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.con
    SV-230342r599837_rule RHEL-08-020020 CCI-000044 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" fo
    SV-230343r599838_rule RHEL-08-020021 CCI-000044 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.con
    SV-230344r599839_rule RHEL-08-020022 CCI-000044 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" fo
    SV-230345r599840_rule RHEL-08-020023 CCI-000044 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.con
    SV-230346r599786_rule RHEL-08-020024 CCI-000054 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 r
    SV-230347r599732_rule RHEL-08-020030 CCI-000056 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 a
    SV-230348r599732_rule RHEL-08-020040 CCI-000056 MEDIUM RHEL 8 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for command line 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 a
    SV-230349r599732_rule RHEL-08-020041 CCI-000056 MEDIUM RHEL 8 must ensure session control is automatically started at shell initialization. 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 a
    SV-230350r599732_rule RHEL-08-020042 CCI-000056 LOW RHEL 8 must prevent users from disabling session control mechanisms. 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 a
    SV-230351r599792_rule RHEL-08-020050 CCI-000056 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 a
    SV-230352r599732_rule RHEL-08-020060 CCI-000057 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 a
    SV-230353r599732_rule RHEL-08-020070 CCI-000057 MEDIUM RHEL 8 must automatically lock command line user sessions after 15 minutes of inactivity. 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. In addition, quickly terminat
    SV-230354r599732_rule RHEL-08-020080 CCI-000057 MEDIUM RHEL 8 must prevent a user from overriding graphical user interface settings. 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 t
    SV-230355r599732_rule RHEL-08-020090 CCI-000187 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 a
    SV-230356r599732_rule RHEL-08-020100 CCI-000192 MEDIUM RHEL 8 must ensure a password complexity module is enabled. 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
    SV-230357r599732_rule RHEL-08-020110 CCI-000192 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
    SV-230358r599732_rule RHEL-08-020120 CCI-000193 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
    SV-230359r599732_rule RHEL-08-020130 CCI-000194 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
    SV-230360r599732_rule RHEL-08-020140 CCI-000195 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
    SV-230361r599732_rule RHEL-08-020150 CCI-000195 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
    SV-230362r599732_rule RHEL-08-020160 CCI-000195 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
    SV-230363r599732_rule RHEL-08-020170 CCI-000195 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
    SV-230364r599732_rule RHEL-08-020180 CCI-000198 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 c
    SV-230365r599732_rule RHEL-08-020190 CCI-000198 MEDIUM RHEL 8 passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in /etc/logins.def. 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 c
    SV-230366r599732_rule RHEL-08-020200 CCI-000199 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 cou
    SV-230367r599732_rule RHEL-08-020210 CCI-000199 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 cou
    SV-230368r599732_rule RHEL-08-020220 CCI-000200 MEDIUM RHEL 8 passwords must be prohibited from reuse for a minimum of five generations. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to reuse their password consecutively when that password
    SV-230369r599732_rule RHEL-08-020230 CCI-000205 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 bru
    SV-230370r599732_rule RHEL-08-020231 CCI-000205 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 bru
    SV-230371r599732_rule RHEL-08-020240 CCI-000764 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 organizati
    SV-230372r599732_rule RHEL-08-020250 CCI-000765 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
    SV-230373r599732_rule RHEL-08-020260 CCI-000795 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 acco
    SV-230374r599732_rule RHEL-08-020270 CCI-001682 MEDIUM RHEL 8 emergency accounts must be automatically removed or disabled after the crisis is resolved or within 72 hours. Emergency accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts a
    SV-230375r599732_rule RHEL-08-020280 CCI-001619 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
    SV-230376r599732_rule RHEL-08-020290 CCI-002007 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 D
    SV-230377r599732_rule RHEL-08-020300 CCI-000366 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.
    SV-230378r599732_rule RHEL-08-020310 CCI-000366 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
    SV-230379r599732_rule RHEL-08-020320 CCI-000366 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
    SV-230380r599732_rule RHEL-08-020330 CCI-000366 HIGH RHEL 8 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.
    SV-230381r599732_rule RHEL-08-020340 CCI-000366 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.
    SV-230382r599732_rule RHEL-08-020350 CCI-000366 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.
    SV-230383r599732_rule RHEL-08-020351 CCI-000366 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.
    SV-230384r599732_rule RHEL-08-020352 CCI-000366 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 typi
    SV-230385r599732_rule RHEL-08-020353 CCI-000366 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 typi
    SV-230386r599732_rule RHEL-08-030000 CCI-002233 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
    SV-230387r599732_rule RHEL-08-030010 CCI-000366 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.
    SV-230388r599732_rule RHEL-08-030020 CCI-000139 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 oper
    SV-230389r599732_rule RHEL-08-030030 CCI-000139 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 oper
    SV-230390r599732_rule RHEL-08-030040 CCI-000140 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 oper
    SV-230391r599732_rule RHEL-08-030050 CCI-000140 MEDIUM The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted 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 cap
    SV-230392r599732_rule RHEL-08-030060 CCI-000140 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 cap
    SV-230393r599732_rule RHEL-08-030061 CCI-000366 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 t
    SV-230394r599732_rule RHEL-08-030062 CCI-001851 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 t
    SV-230395r599732_rule RHEL-08-030063 CCI-000366 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 t
    SV-230396r599732_rule RHEL-08-030070 CCI-000162 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
    SV-230397r599732_rule RHEL-08-030080 CCI-000162 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
    SV-230398r599732_rule RHEL-08-030090 CCI-000162 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
    SV-230399r599732_rule RHEL-08-030100 CCI-000162 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
    SV-230400r599732_rule RHEL-08-030110 CCI-000162 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
    SV-230401r599732_rule RHEL-08-030120 CCI-000162 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
    SV-230402r599732_rule RHEL-08-030121 CCI-000162 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
    SV-230403r599732_rule RHEL-08-030122 CCI-000162 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
    SV-230404r599732_rule RHEL-08-030130 CCI-000169 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 recor
    SV-230405r599732_rule RHEL-08-030140 CCI-000169 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 recor
    SV-230406r599732_rule RHEL-08-030150 CCI-000169 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 recor
    SV-230407r599732_rule RHEL-08-030160 CCI-000169 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 recor
    SV-230408r599732_rule RHEL-08-030170 CCI-000169 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 recor
    SV-230409r599732_rule RHEL-08-030171 CCI-000169 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 recor
    SV-230410r599732_rule RHEL-08-030172 CCI-000169 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 recor
    SV-230411r599732_rule RHEL-08-030180 CCI-000169 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 t
    SV-230412r599732_rule RHEL-08-030190 CCI-000169 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 recor
    SV-230413r599732_rule RHEL-08-030200 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the lremovexattr system call. 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 recor
    SV-230414r599732_rule RHEL-08-030210 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the removexattr system call. 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 recor
    SV-230415r599732_rule RHEL-08-030220 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the lsetxattr system call. 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 recor
    SV-230416r599732_rule RHEL-08-030230 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the fsetxattr system call. 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 recor
    SV-230417r599732_rule RHEL-08-030240 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the fremovexattr system call. 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 recor
    SV-230418r599732_rule RHEL-08-030250 CCI-000169 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 recor
    SV-230419r599732_rule RHEL-08-030260 CCI-000169 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 recor
    SV-230420r599794_rule RHEL-08-030270 CCI-000169 MEDIUM The RHEL 8 audit system must be configured to audit any usage of the setxattr system call. 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 recor
    SV-230421r599732_rule RHEL-08-030280 CCI-000169 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 recor
    SV-230422r599732_rule RHEL-08-030290 CCI-000169 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 recor
    SV-230423r599732_rule RHEL-08-030300 CCI-000169 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 recor
    SV-230424r599732_rule RHEL-08-030301 CCI-000169 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 recor
    SV-230425r599732_rule RHEL-08-030302 CCI-000169 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 recor
    SV-230426r599732_rule RHEL-08-030310 CCI-000169 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 trail
    SV-230427r599732_rule RHEL-08-030311 CCI-000169 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 trail
    SV-230428r599732_rule RHEL-08-030312 CCI-000169 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 trail
    SV-230429r599732_rule RHEL-08-030313 CCI-000169 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 trail
    SV-230430r599732_rule RHEL-08-030314 CCI-000169 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 trail
    SV-230431r599732_rule RHEL-08-030315 CCI-000169 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 trail
    SV-230432r599732_rule RHEL-08-030316 CCI-000169 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 trail
    SV-230433r599732_rule RHEL-08-030317 CCI-000169 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 trail
    SV-230434r599732_rule RHEL-08-030320 CCI-000169 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 recor
    SV-230435r599732_rule RHEL-08-030330 CCI-000169 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 recor
    SV-230436r599732_rule RHEL-08-030340 CCI-000169 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 recor
    SV-230437r599732_rule RHEL-08-030350 CCI-000169 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 recor
    SV-230438r599732_rule RHEL-08-030360 CCI-000169 MEDIUM Successful/unsuccessful uses of the init_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 recor
    SV-230439r599732_rule RHEL-08-030361 CCI-000169 MEDIUM Successful/unsuccessful uses of the rename 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 recor
    SV-230440r599732_rule RHEL-08-030362 CCI-000169 MEDIUM Successful/unsuccessful uses of the renameat 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 recor
    SV-230441r599732_rule RHEL-08-030363 CCI-000169 MEDIUM Successful/unsuccessful uses of the rmdir 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 recor
    SV-230442r599732_rule RHEL-08-030364 CCI-000169 MEDIUM Successful/unsuccessful uses of the unlink 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 recor
    SV-230443r599732_rule RHEL-08-030365 CCI-000169 MEDIUM Successful/unsuccessful uses of the unlinkat 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 recor
    SV-230444r599732_rule RHEL-08-030370 CCI-000169 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 recor
    SV-230445r599732_rule RHEL-08-030380 CCI-000169 MEDIUM Successful/unsuccessful uses of the finit_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 recor
    SV-230446r599732_rule RHEL-08-030390 CCI-000169 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 recor
    SV-230447r599732_rule RHEL-08-030400 CCI-000169 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 recor
    SV-230448r599732_rule RHEL-08-030410 CCI-000169 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 recor
    SV-230449r599732_rule RHEL-08-030420 CCI-000169 MEDIUM Successful/unsuccessful uses of the truncate 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 recor
    SV-230450r599732_rule RHEL-08-030430 CCI-000169 MEDIUM Successful/unsuccessful uses of the openat system call 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 recor
    SV-230451r599732_rule RHEL-08-030440 CCI-000169 MEDIUM Successful/unsuccessful uses of the open system call 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 recor
    SV-230452r599732_rule RHEL-08-030450 CCI-000169 MEDIUM Successful/unsuccessful uses of the open_by_handle_at system call 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 recor
    SV-230453r599732_rule RHEL-08-030460 CCI-000169 MEDIUM Successful/unsuccessful uses of the ftruncate 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 recor
    SV-230454r599732_rule RHEL-08-030470 CCI-000169 MEDIUM Successful/unsuccessful uses of the creat system call 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 recor
    SV-230455r599732_rule RHEL-08-030480 CCI-000169 MEDIUM Successful/unsuccessful uses of the chown 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 recor
    SV-230456r599732_rule RHEL-08-030490 CCI-000169 MEDIUM Successful/unsuccessful uses of the chmod 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 recor
    SV-230457r599732_rule RHEL-08-030500 CCI-000169 MEDIUM Successful/unsuccessful uses of the lchown system call 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 recor
    SV-230458r599732_rule RHEL-08-030510 CCI-000169 MEDIUM Successful/unsuccessful uses of the fchownat system call 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 recor
    SV-230459r599732_rule RHEL-08-030520 CCI-000169 MEDIUM Successful/unsuccessful uses of the fchown system call 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 recor
    SV-230460r599732_rule RHEL-08-030530 CCI-000169 MEDIUM Successful/unsuccessful uses of the fchmodat system call 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 recor
    SV-230461r599732_rule RHEL-08-030540 CCI-000169 MEDIUM Successful/unsuccessful uses of the fchmod system call 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 recor
    SV-230462r599732_rule RHEL-08-030550 CCI-000169 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 recor
    SV-230463r599732_rule RHEL-08-030560 CCI-000169 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 recor
    SV-230464r599732_rule RHEL-08-030570 CCI-000169 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 recor
    SV-230465r599732_rule RHEL-08-030580 CCI-000169 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 i
    SV-230466r599841_rule RHEL-08-030590 CCI-000169 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 i
    SV-230467r599732_rule RHEL-08-030600 CCI-000169 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 i
    SV-230468r599732_rule RHEL-08-030601 CCI-000169 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
    SV-230469r599732_rule RHEL-08-030602 CCI-001849 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
    SV-230470r599732_rule RHEL-08-030603 CCI-000169 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
    SV-230471r599732_rule RHEL-08-030610 CCI-000171 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
    SV-230472r599732_rule RHEL-08-030620 CCI-001493 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
    SV-230473r599732_rule RHEL-08-030630 CCI-001493 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
    SV-230474r599732_rule RHEL-08-030640 CCI-001493 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
    SV-230475r599732_rule RHEL-08-030650 CCI-001496 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 successfu
    SV-230476r599732_rule RHEL-08-030660 CCI-001849 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 inst
    SV-230477r599732_rule RHEL-08-030670 CCI-000366 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" i
    SV-230478r599732_rule RHEL-08-030680 CCI-000366 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" i
    SV-230479r599732_rule RHEL-08-030690 CCI-001851 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" i
    SV-230480r599732_rule RHEL-08-030700 CCI-001851 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" i
    SV-230481r599796_rule RHEL-08-030710 CCI-001851 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" i
    SV-230482r599732_rule RHEL-08-030720 CCI-001851 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" i
    SV-230483r599732_rule RHEL-08-030730 CCI-001855 MEDIUM RHEL 8 must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) 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.
    SV-230484r599732_rule RHEL-08-030740 CCI-001891 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. S
    SV-230485r599732_rule RHEL-08-030741 CCI-000381 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. S
    SV-230486r599732_rule RHEL-08-030742 CCI-000381 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. S
    SV-230487r599732_rule RHEL-08-040000 CCI-000381 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 ri
    SV-230488r599732_rule RHEL-08-040001 CCI-000381 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 ri
    SV-230489r599732_rule RHEL-08-040002 CCI-000381 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 ri
    SV-230490r599732_rule RHEL-08-040003 CCI-000381 MEDIUM RHEL 8 must not have the gssproxy package installed. It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the ri
    SV-230491r599732_rule RHEL-08-040004 CCI-000381 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 ri
    SV-230492r599732_rule RHEL-08-040010 CCI-000381 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 ri
    SV-230493r599732_rule RHEL-08-040020 CCI-000381 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 ri
    SV-230494r599732_rule RHEL-08-040021 CCI-000381 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 ri
    SV-230495r599732_rule RHEL-08-040022 CCI-000381 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 ri
    SV-230496r599732_rule RHEL-08-040023 CCI-000381 LOW RHEL 8 must disable the stream control transmission (SCTP) 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 ri
    SV-230497r599732_rule RHEL-08-040024 CCI-000381 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 ri
    SV-230498r599732_rule RHEL-08-040025 CCI-000381 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 ri
    SV-230499r599732_rule RHEL-08-040026 CCI-000381 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 ri
    SV-230500r599732_rule RHEL-08-040030 CCI-000382 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/proto
    SV-230501r599732_rule RHEL-08-040060 CCI-001941 HIGH RHEL 8 must enforce SSHv2 for network access to all accounts. A replay attack may enable an unauthorized user to gain access to RHEL 8. Authentication sessions between the authenticator and RHEL 8 validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay att
    SV-230502r599732_rule RHEL-08-040070 CCI-000778 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.
    SV-230503r599732_rule RHEL-08-040080 CCI-000778 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
    SV-230504r599732_rule RHEL-08-040090 CCI-002314 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 a
    SV-230505r599732_rule RHEL-08-040100 CCI-002314 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 c
    SV-230506r599732_rule RHEL-08-040110 CCI-001444 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 requi
    SV-230507r599732_rule RHEL-08-040111 CCI-001443 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 requi
    SV-230508r599797_rule RHEL-08-040120 CCI-001764 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 whiteli
    SV-230509r599732_rule RHEL-08-040121 CCI-001764 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 whiteli
    SV-230510r599798_rule RHEL-08-040122 CCI-001764 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 whiteli
    SV-230511r599799_rule RHEL-08-040123 CCI-001764 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 whiteli
    SV-230512r599732_rule RHEL-08-040124 CCI-001764 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 whiteli
    SV-230513r599800_rule RHEL-08-040125 CCI-001764 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 whiteli
    SV-230514r599801_rule RHEL-08-040126 CCI-001764 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 whiteli
    SV-230515r599802_rule RHEL-08-040127 CCI-001764 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 whiteli
    SV-230516r599803_rule RHEL-08-040128 CCI-001764 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 whiteli
    SV-230517r599804_rule RHEL-08-040129 CCI-001764 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 whiteli
    SV-230518r599805_rule RHEL-08-040130 CCI-001764 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 whiteli
    SV-230519r599806_rule RHEL-08-040131 CCI-001764 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 whiteli
    SV-230520r599807_rule RHEL-08-040132 CCI-001764 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 whiteli
    SV-230521r599808_rule RHEL-08-040133 CCI-001764 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 whiteli
    SV-230522r599809_rule RHEL-08-040134 CCI-001764 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 whiteli
    SV-230523r599732_rule RHEL-08-040135 CCI-001764 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 whiteli
    SV-230524r599732_rule RHEL-08-040140 CCI-001958 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 RHE
    SV-230525r599732_rule RHEL-08-040150 CCI-002385 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
    SV-230526r599732_rule RHEL-08-040160 CCI-002418 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
    SV-230527r599732_rule RHEL-08-040161 CCI-000068 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
    SV-230528r599732_rule RHEL-08-040162 CCI-000068 MEDIUM RHEL 8 must force a frequent session key renegotiation for SSH connections by the client. 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
    SV-230529r599811_rule RHEL-08-040170 CCI-000366 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
    SV-230530r599732_rule RHEL-08-040171 CCI-000366 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 t
    SV-230531r599813_rule RHEL-08-040172 CCI-000366 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 u
    SV-230532r599815_rule RHEL-08-040180 CCI-000366 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 depend
    SV-230533r599732_rule RHEL-08-040190 CCI-000366 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 establis
    SV-230534r599732_rule RHEL-08-040200 CCI-000366 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 gues
    SV-230535r599732_rule RHEL-08-040210 CCI-000366 MEDIUM RHEL 8 must prevent 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-mi
    SV-230536r599732_rule RHEL-08-040220 CCI-000366 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 nota
    SV-230537r599732_rule RHEL-08-040230 CCI-000366 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
    SV-230538r599732_rule RHEL-08-040240 CCI-000366 MEDIUM RHEL 8 must not forward 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
    SV-230539r599732_rule RHEL-08-040250 CCI-000366 MEDIUM RHEL 8 must not forward 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
    SV-230540r599732_rule RHEL-08-040260 CCI-000366 MEDIUM RHEL 8 must not be performing 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.
    SV-230541r599732_rule RHEL-08-040261 CCI-000366 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 rou
    SV-230542r599732_rule RHEL-08-040262 CCI-000366 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 rou
    SV-230543r599732_rule RHEL-08-040270 CCI-000366 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 nota
    SV-230544r599732_rule RHEL-08-040280 CCI-000366 MEDIUM RHEL 8 must ignore 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-mi
    SV-230545r599732_rule RHEL-08-040281 CCI-000366 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 ri
    SV-230546r599732_rule RHEL-08-040282 CCI-000366 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 ri
    SV-230547r599732_rule RHEL-08-040283 CCI-000366 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 ri
    SV-230548r599732_rule RHEL-08-040284 CCI-000366 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 ri
    SV-230549r599732_rule RHEL-08-040285 CCI-000366 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 ri
    SV-230550r599732_rule RHEL-08-040290 CCI-000366 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.
    SV-230551r599732_rule RHEL-08-040300 CCI-000366 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).
    SV-230552r599732_rule RHEL-08-040310 CCI-000366 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).
    SV-230553r599732_rule RHEL-08-040320 CCI-000366 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 a
    SV-230554r599732_rule RHEL-08-040330 CCI-000366 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
    SV-230555r599816_rule RHEL-08-040340 CCI-000366 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
    SV-230556r599732_rule RHEL-08-040341 CCI-000366 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 th
    SV-230557r599732_rule RHEL-08-040350 CCI-000366 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.
    SV-230558r599732_rule RHEL-08-040360 CCI-000366 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 compro
    SV-230559r599732_rule RHEL-08-040370 CCI-000366 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 ri
    SV-230560r599732_rule RHEL-08-040380 CCI-000366 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 ri
    SV-230561r599732_rule RHEL-08-040390 CCI-000366 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 ri