| V-248519 | | The OL 8 audit package must be installed. | Without establishing what type of events occurred and their source, location, and outcome, it would be difficult to establish, correlate, and investig... |
| V-248520 | | OL 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 and their source, location, and outcome, it would be difficult to establish, correlate, and investig... |
| V-248523 | | OL 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. Howev... |
| V-248526 | | OL 8 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via an SSH logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-248527 | | OL 8 must display a banner before granting local or remote access to the system via a graphical user logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-248528 | | OL 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 verbi... |
| V-248529 | | OL 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 verbi... |
| V-248530 | | All OL 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... |
| V-248531 | | OL 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, the relying party cannot make an informed trust decision when presented with any certificate not already explicitly trusted. ... |
| V-248532 | | OL 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 associate... |
| V-248533 | | OL 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 ... |
| V-248534 | | OL 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 m... |
| V-248535 | | The OL 8 shadow password suite must be configured to use a sufficient number of hashing rounds. | The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required... |
| V-248538 | | OL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must have a unique name for the grub superusers account when 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 maintenanc... |
| V-248539 | | OL 8 operating systems booted with a BIOS must have a unique name for the grub superusers account when 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 maintenanc... |
| V-248541 | | OL 8 operating systems must require authentication upon booting into rescue mode. | If the system does not require valid root authentication before it boots into emergency or rescue mode, anyone who invokes emergency or rescue mode is... |
| V-248542 | | OL 8 operating systems must require authentication upon booting into emergency mode. | If the system does not require valid root authentication before it boots into emergency or rescue mode, anyone who invokes emergency or rescue mode is... |
| V-248543 | | The OL 8 "pam_unix.so" module must be configured in the system-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248544 | | The OL 8 "pam_unix.so" module must be configured in the password-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248545 | | OL 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 on to provide confi... |
| V-248546 | | The krb5-workstation package must not be installed on OL 8. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248547 | | The krb5-server package must not be installed on OL 8. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248548 | | OL 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 de... |
| V-248551 | | A sticky bit must be set on all OL 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 a... |
| V-248552 | | OL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-248553 | | OL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-248554 | | The OL 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 st... |
| V-248555 | | The OL 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 st... |
| V-248556 | | The OL 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 st... |
| V-248557 | | The OL 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 st... |
| V-248558 | | The OL 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 st... |
| V-248559 | | The OL 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 st... |
| V-248560 | | The OL 8 SSH daemon must be configured to use system-wide crypto policies. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-248561 | | The OL 8 SSH server 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 acces... |
| V-248562 | | The OL 8 SSH server must be configured to use only ciphers employing FIPS 140-2 validated cryptographic algorithms. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248564 | | The OL 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 acces... |
| V-248565 | | The OL 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... |
| V-248566 | | The OL 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) enc... |
| V-248567 | | OL 8 system commands must have mode 755 or less permissive. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248568 | | OL 8 system commands must be owned by root. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248569 | | OL 8 system commands must be group-owned by root or a system account. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248570 | | OL 8 library files must have mode 755 or less permissive. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248571 | | OL 8 library files must be owned by root. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248572 | | OL 8 library files must be group-owned by root. | If OL 8 were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate testing an... |
| V-248573 | | The OL 8 file integrity tool must notify the system administrator (SA) 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 s... |
| V-248576 | | OL 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... |
| V-248577 | | OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. | 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 obj... |
| V-248578 | | OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on hardlinks. | 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 obj... |
| V-248581 | | OL 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 ca... |
| V-248582 | | OL 8 must require users to reauthenticate for privilege escalation and changing roles. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ca... |
| V-248583 | | OL 8 must restrict privilege elevation to authorized personnel. | The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your ... |
| V-248584 | | OL 8 must use the invoking user's password for privilege escalation when using "sudo". | The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates t... |
| V-248585 | | OL 8 must require reauthentication when using the "sudo" command. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the c... |
| V-248587 | | OL 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... |
| V-248588 | | OL 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 Acce... |
| V-248589 | | OL 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. Secu... |
| V-248590 | | OL 8 must clear the page allocator to prevent use-after-free attacks. | Adversaries may launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Secur... |
| V-248591 | | OL 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 ope... |
| V-248592 | | OL 8 must clear memory when it is freed to prevent use-after-free attacks. | Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Secur... |
| V-248593 | | OL 8 must not let Meltdown and Spectre exploit critical vulnerabilities in modern processors. | Hardware vulnerabilities allow programs to steal data that is currently processed on the computer. While programs are typically not permitted to read ... |
| V-248594 | | OL 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. Secu... |
| V-248596 | | OL 8 must enable the SELinux targeted policy. | Without verification of the security functions, they may not operate correctly and the failure may go unnoticed. Security function is defined as the h... |
| V-248601 | | The OL 8 SSH public host key files must have mode "0644" or less permissive. | If a public host key file is modified by an unauthorized user, the SSH service may be compromised.... |
| V-248602 | | The OL 8 SSH private host key files must have mode "0640" or less permissive. | If an unauthorized user obtains the private SSH host key file, the host could be impersonated.... |
| V-248603 | | The OL 8 SSH daemon must perform strict mode checking of home directory configuration files. | If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.... |
| V-248605 | | The OL 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 misc... |
| V-248606 | | The OL 8 SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-248607 | | The OL 8 SSH daemon must not allow GSSAPI authentication, except to fulfill documented and validated mission requirements. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-248611 | | OL 8 must use a separate file system for "/tmp". | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248612 | | OL 8 must use a separate file system for /var/tmp. | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248613 | | OL 8 must not permit direct logons to the root account using remote access via SSH. | Although the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as ... |
| V-248615 | | OL 8 must have the rsyslog service enabled and active. | Configuring OL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and e... |
| V-248616 | | OL 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 an... |
| V-248617 | | OL 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 an... |
| V-248618 | | OL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory. | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-248619 | | OL 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 untr... |
| V-248620 | | OL 8 file systems that contain user home directories must not execute binary files. | 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... |
| V-248621 | | OL 8 file systems must not interpret character or block special devices from untrusted file systems. | The "nodev" mount option causes the system not to interpret character or block special devices. Executing character or block special devices from untr... |
| V-248622 | | OL 8 file systems must not execute binary files on 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... |
| V-248623 | | OL 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 an... |
| V-248624 | | OL 8 file systems must not execute binary files 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... |
| V-248625 | | OL 8 file systems must not interpret character or block special devices that are imported via NFS. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-248626 | | OL 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 an... |
| V-248627 | | Local OL 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 file... |
| V-248628 | | OL 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... |
| V-248629 | | OL 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 unnecessa... |
| V-248630 | | OL 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 unnecessa... |
| V-248631 | | OL 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 unnecessa... |
| V-248632 | | OL 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 unnecessa... |
| V-248633 | | OL 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 unnecessa... |
| V-248634 | | For OL 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 fai... |
| V-248635 | | Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's 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 th... |
| V-248636 | | All OL 8 world-writable directories must be owned by root, sys, bin, or an application user. | If a world-writable directory is not owned by root, sys, bin, or an application User Identifier (UID), unauthorized users may be able to modify files ... |
| V-248637 | | All OL 8 world-writable directories must be group-owned by root, sys, bin, or an application group. | If a world-writable directory is not group-owned by root, sys, bin, or an application Group Identifier (GID), unauthorized users may be able to modify... |
| V-248638 | | All OL 8 local interactive users must have a home directory assigned in the "/etc/passwd" file. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-248639 | | All OL 8 local interactive user home directories must have mode "0750" or less permissive. | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.... |
| V-248640 | | All OL 8 local interactive user home directory files must have mode "0750" or less permissive. | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.... |
| V-248641 | | All OL 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 unauthoriz... |
| V-248642 | | OL 8 must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member. | If a local interactive user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them.... |
| V-248643 | | All OL 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... |
| V-248644 | | All OL 8 local interactive user accounts must be assigned a home directory upon creation. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-248645 | | All OL 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 accou... |
| V-248646 | | All OL 8 files and directories must have a valid owner. | Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier "UID" as the UID of the unowned files.... |
| V-248647 | | All OL 8 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 with... |
| V-248648 | | A separate OL 8 filesystem must be used for user home directories (such as "/home" or an equivalent). | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248651 | | OL 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 ... |
| V-248652 | | OL 8 systems below version 8.2 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 att... |
| V-248653 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248654 | | OL 8 systems below version 8.2 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 att... |
| V-248655 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248656 | | OL 8 systems below version 8.2 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 att... |
| V-248657 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248658 | | OL 8 systems below version 8.2 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 att... |
| V-248659 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248660 | | OL 8 systems below version 8.2 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 att... |
| V-248661 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248662 | | OL 8 systems below version 8.2 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 att... |
| V-248663 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248664 | | OL 8 systems below version 8.2 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 att... |
| V-248665 | | OL 8 systems, versions 8.2 and above, 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 att... |
| V-248667 | | OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-248668 | | OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-248669 | | OL 8 systems, versions 8.2 and above, must configure SELinux context type to allow the use of a non-default faillock tally directory. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-248670 | | OL 8 systems below version 8.2 must configure SELinux context type to allow the use of a non-default faillock tally directory. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-248671 | | OL 8 must enable a user session lock until that user reestablishes access using established identification and authentication procedures for graphical user sessions. | To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity ... |
| V-248672 | | OL 8 must initiate a session lock for graphical user interfaces when the screensaver is activated. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-248673 | | OL 8 must disable the user list at logon for graphical user interfaces. | Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to enumerate known user accounts without au... |
| V-248678 | | OL 8 must enable a user session lock until that user reestablishes 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 do... |
| V-248679 | | OL 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 do... |
| V-248680 | | OL 8 must automatically lock graphical user sessions after 15 minutes of inactivity. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-248682 | | OL 8 must prevent a user from overriding the session lock-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-248683 | | OL 8 must prevent a user from overriding the session idle-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-248684 | | OL 8 must prevent a user from overriding the session lock-enabled setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-248685 | | OL 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 n... |
| V-248686 | | OL 8 must ensure the password complexity module is enabled in the password-auth file. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-248690 | | OL 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... |
| V-248691 | | OL 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... |
| V-248692 | | OL 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... |
| V-248694 | | OL 8 passwords for new users or password changes must have a 24 hours/one 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 u... |
| V-248695 | | OL 8 passwords for new users or password changes must have a 24 hours/one day minimum password lifetime restriction in "/etc/login.defs". | Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If u... |
| V-248696 | | OL 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 OL 8 does not limit the lifet... |
| V-248697 | | OL 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 OL 8 does not limit the lifet... |
| V-248699 | | OL 8 passwords must have a minimum of 15 characters. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password ... |
| V-248700 | | OL 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 complex... |
| V-248701 | | OL 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 co... |
| V-248702 | | OL 8 must implement 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 inf... |
| V-248703 | | The OL 8 system-auth file must disable access to the system for account identifiers (individuals, groups, roles, and devices) with 35 days of inactivity. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-248704 | | The OL 8 password-auth file must disable access to the system for account identifiers (individuals, groups, roles, and devices) with 35 days of inactivity. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-248705 | | The OL 8 lastlog command must have a mode of "0750" or less permissive. | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality.... |
| V-248706 | | The OL 8 lastlog command must be owned by root. | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality.... |
| V-248707 | | The OL 8 lastlog command must be group-owned by root. | Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to attackers, thus compromising its confidentiality.... |
| V-248708 | | OL 8 must automatically expire temporary accounts within 72 hours. | Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware confi... |
| V-248710 | | OL 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.
OL 8 includes multiple opt... |
| V-248711 | | OL 8 must prevent the use of dictionary words for passwords. | If OL 8 allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity... |
| V-248712 | | OL 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 federa... |
| V-248713 | | OL 8 must not have unnecessary accounts. | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for indiv... |
| V-248718 | | OL 8 must display the date and time of the last successful account logon upon an SSH logon. | Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-248719 | | OL 8 default permissions must be defined in such a way that all authenticated users can read and modify only their own files. | Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.... |
| V-248720 | | OL 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 u... |
| V-248721 | | OL 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 u... |
| V-248722 | | The OL 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 compromise... |
| V-248723 | | Cron logging must be implemented in OL 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 cr... |
| V-248724 | | The OL 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 notificatio... |
| V-248725 | | The OL 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 notificatio... |
| V-248726 | | The OL 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 notificatio... |
| V-248728 | | The OL 8 audit system must take appropriate action when the audit storage volume is full. | It is critical that when OL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failu... |
| V-248729 | | The OL 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 es... |
| V-248730 | | OL 8 must label all offloaded audit logs before sending them to the central log server. | Without establishing what type of events occurred and their source, location, and outcome, it would be difficult to establish, correlate, and investig... |
| V-248731 | | OL 8 must resolve audit information before writing to disk. | Without establishing what type of events occurred and their source, location, and outcome, it would be difficult to establish, correlate, and investig... |
| V-248732 | | OL 8 audit logs must have a mode of "0600" 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 inform... |
| V-248733 | | OL 8 audit logs 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 inform... |
| V-248734 | | OL 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 inform... |
| V-248735 | | The OL 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 inform... |
| V-248736 | | The OL 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 inform... |
| V-248737 | | The OL 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 inform... |
| V-248738 | | The OL 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 inform... |
| V-248739 | | The OL 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 inform... |
| V-248740 | | OL 8 must generate audit records for all account creation 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, correlat... |
| V-248741 | | OL 8 must generate audit records for all account creation 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, correlat... |
| V-248742 | | OL 8 must generate audit records for all account creation 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, correlat... |
| V-248743 | | OL 8 must generate audit records for all account creation 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, correlat... |
| V-248744 | | OL 8 must generate audit records for all account creation 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, correlat... |
| V-248745 | | OL 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, correlat... |
| V-248746 | | OL 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, correlat... |
| V-248747 | | OL 8 must generate audit records for any use of the "su" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248748 | | The OL 8 audit system must be configured to audit any use of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248753 | | OL 8 must generate audit records for any use of the "chage" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248754 | | OL 8 must generate audit records for any uses of the "chcon" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248756 | | OL 8 must generate audit records for any use of the "ssh-agent" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248757 | | OL 8 must generate audit records for any use of the "passwd" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248758 | | OL 8 must generate audit records for any use of the "mount" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248759 | | OL 8 must generate audit records for any use of the "umount" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248760 | | OL 8 must generate audit records for any use of the "mount" syscall. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248761 | | OL 8 must generate audit records for any use of the "unix_update" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organiz... |
| V-248762 | | OL 8 must generate audit records for any use of the "postdrop" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248763 | | OL 8 must generate audit records for any use of the "postqueue" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248764 | | OL 8 must generate audit records for any use of the "semanage" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248765 | | OL 8 must generate audit records for any use of the "setfiles" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248766 | | OL 8 must generate audit records for any use of the "userhelper" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248767 | | OL 8 must generate audit records for any use of the "setsebool" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248768 | | OL 8 must generate audit records for any use of the "unix_chkpwd" command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-248769 | | OL 8 must generate audit records for any use of the "ssh-keysign" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248770 | | OL 8 must generate audit records for any use of the "setfacl" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248771 | | OL 8 must generate audit records for any use of the "pam_timestamp_check" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248772 | | OL 8 must generate audit records for any use of the "newgrp" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248773 | | OL 8 must generate audit records for any use of the "init_module" and "finit_module" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248774 | | OL 8 must generate audit records for any use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248779 | | OL 8 must generate audit records for any use of the "gpasswd" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248781 | | OL 8 must generate audit records for any use of the delete_module syscall. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248782 | | OL 8 must generate audit records for any use of the "crontab" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248783 | | OL 8 must generate audit records for any use of the "chsh" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248784 | | OL 8 must generate audit records for any use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248790 | | OL 8 must generate audit records for any use of the "chown", "fchown", "fchownat", and "lchown" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248791 | | OL 8 must generate audit records for any use of the "chmod", "fchmod", and "fchmodat" system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248797 | | OL 8 must generate audit records for any use of the "sudo" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248798 | | OL 8 must generate audit records for any use of the "usermod" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248799 | | OL 8 must generate audit records for any use of the "chacl" command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248800 | | OL 8 must generate audit records for any use of the "kmod" command. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-248801 | | OL 8 must generate audit records for any attempted modifications to the "faillock" log file. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-248802 | | OL 8 must generate audit records for any attempted modifications to the "lastlog" file. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-248803 | | OL 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... |
| V-248805 | | OL 8 must enable Linux audit logging for the USBGuard daemon. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-248806 | | OL 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 t... |
| V-248807 | | OL 8 audit tools must have a mode of "0755" or less permissive. | Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ... |
| V-248808 | | OL 8 audit tools must be owned by root. | Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ... |
| V-248809 | | OL 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 tool... |
| V-248810 | | OL 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 informat... |
| V-248811 | | OL 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 OL 8 systems have a sufficient storage capacity in which to write the audit logs, OL 8 needs to be able to allocate audit record storage cap... |
| V-248812 | | OL 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.
Offloading is a common process in information ... |
| V-248813 | | OL 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.
Offloading is a common process in information ... |
| V-248814 | | The OL 8 audit records must be offloaded 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.
Offloading is a common process in information ... |
| V-248815 | | OL 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.
Offloading is a common process in information ... |
| V-248816 | | OL 8 must encrypt the transfer of audit records offloaded 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.
Offloading is a common process in information ... |
| V-248817 | | OL 8 must authenticate the remote logging server for offloading audit logs. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information... |
| V-248818 | | OL 8 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. | If security personnel are not notified immediately when storage volume reaches a maximum of 75 percent utilization, they are unable to plan for audit ... |
| V-248819 | | OL 8 must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated audit record storage volume 75 percent utilization. | If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storag... |
| V-248820 | | OL 8 must 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 ev... |
| V-248824 | | OL 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 unnecessa... |
| V-248825 | | OL 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 unnecessa... |
| V-248828 | | OL 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 unnecessa... |
| V-248829 | | OL 8 must not have the asynchronous transfer mode (ATM) kernel module installed if not required for operational support. | The ATM is a transport layer protocol
designed for digital transmission of multiple types of traffic, including telephony (voice), data, and video si... |
| V-248830 | | OL 8 must not have the Controller Area Network (CAN) kernel module installed if not required for operational support. | The CAN protocol is a robust vehicle bus standard designed to allow microcontrollers and devices to communicate with each other's applications without... |
| V-248831 | | OL 8 must not have the stream control transmission protocol (SCTP) kernel module installed if not required for operational support. | The SCTP is a transport layer protocol, designed to support the idea of message-oriented communication, with several streams of messages within one co... |
| V-248835 | | OL 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 d... |
| V-248836 | | The OL 8 file system automounter must be disabled unless required. | Verify the operating system disables the ability to automount devices.
Determine if automounter service is active with the following command:
$ ... |
| V-248837 | | OL 8 must be configured to disable the ability to use USB mass storage devices. | USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.... |
| V-248839 | | An OL 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 conne... |
| V-248840 | | A firewall must be installed on OL 8. | "Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services,... |
| V-248841 | | A firewall must be active on OL 8. | "Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services,... |
| V-248842 | | OL 8 wireless network adapters must be disabled. | Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications ca... |
| V-248843 | | OL 8 Bluetooth must be disabled. | Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications ca... |
| V-248844 | | OL 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 program... |
| V-248845 | | OL 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 program... |
| V-248846 | | OL 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 program... |
| V-248847 | | OL 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 program... |
| V-248848 | | OL 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 program... |
| V-248849 | | OL 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 program... |
| V-248850 | | OL 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 program... |
| V-248851 | | OL 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 program... |
| V-248852 | | OL 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 program... |
| V-248853 | | OL 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 program... |
| V-248854 | | OL 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 program... |
| V-248855 | | OL 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 program... |
| V-248856 | | OL 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 program... |
| V-248857 | | OL 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 program... |
| V-248858 | | OL 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 program... |
| V-248859 | | The OL 8 "fapolicy" module must be installed. | The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software program... |
| V-248860 | | The OL 8 "fapolicy" module must be enabled. | The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software program... |
| V-248861 | | The OL 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 program... |
| V-248862 | | OL 8 must have the USBGuard installed. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include but... |
| V-248863 | | OL 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... |
| V-248864 | | OL 8 must enable the USBGuard. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include but... |
| V-248865 | | A firewall must be able to protect against or limit the effects of denial-of-service (DoS) attacks by ensuring OL 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 m... |
| V-248866 | | All OL 8 networked systems must have SSH installed. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-248867 | | All OL 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 intercep... |
| V-248868 | | OL 8 must force a frequent session key renegotiation for SSH connections to the server. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-248871 | | OL 8 must disable the systemd Ctrl-Alt-Delete burst key sequence. | 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 o... |
| V-248875 | | OL 8 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-248876 | | OL 8 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-248877 | | OL 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 inform... |
| V-248878 | | OL 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 betw... |
| V-248879 | | OL 8 must not forward IPv4 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-248880 | | OL 8 must not forward IPv6 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-248881 | | OL 8 must not forward IPv4 source-routed packets by default. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-248882 | | OL 8 must not forward IPv6 source-routed packets by default. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-248883 | | OL 8 must not enable IPv6 packet forwarding unless the system is a router. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not ... |
| V-248884 | | OL 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 ... |
| V-248885 | | OL 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 ... |
| V-248886 | | OL 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 inform... |
| V-248887 | | OL 8 must ignore IPv4 Internet Control Message Protocol (ICMP) redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-248888 | | OL 8 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-248889 | | OL 8 must disable access to the 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 unnecessa... |
| V-248890 | | OL 8 must restrict the use of "ptrace" to descendant processes. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-248891 | | OL 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 unnecessa... |
| V-248892 | | OL 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 unnecessa... |
| V-248893 | | OL 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 unnecessa... |
| V-248894 | | OL 8 must enable hardening for the Berkeley Packet Filter Just-in-time compiler. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-248895 | | OL 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 to send spam or for other unauthorized activity.... |
| V-248898 | | The graphical display manager must not be installed on OL 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. X Windows... |
| V-248899 | | OL 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 thes... |
| V-248900 | | OL 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 ... |
| V-248901 | | The OL 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 o... |
| V-248902 | | If the Trivial File Transfer Protocol (TFTP) server is required, the OL 8 TFTP daemon must be configured to operate in secure mode. | Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.... |
| V-248904 | | OL 8 must not have the "gssproxy" package installed if not required for operational support. | Verify the operating system is configured to disable nonessential capabilities. The most secure way of ensuring a nonessential capability is disabled ... |
| V-248905 | | OL 8 must not have the "iprutils" package installed if not required for operational support. | The "iprutils" package provides a suite of utilities to manage and configure IBM Power Linux RAID Adapters supported by the IPR SCSI storage device dr... |
| V-248906 | | OL 8 must not have the "tuned" package installed if not required for operational support. | "Tuned" is a daemon that uses "udev" to monitor connected devices and statically and dynamically tunes system settings according to a selected profile... |
| V-248907 | | OL 8 must prevent nonprivileged users from executing privileged functions, including disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-252651 | | OL 8 library directories must have mode 755 or less permissive. | If OL 8 were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testi... |
| V-252652 | | OL 8 library directories must be owned by root. | If OL 8 were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testi... |
| V-252653 | | OL 8 library directories must be group-owned by root or a system account. | If OL 8 were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testi... |
| V-252654 | | The OL 8 operating system must use a file integrity tool to verify correct operation of all security functions. | Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is d... |
| V-252655 | | OL 8 must specify the default "include" directory for the /etc/sudoers file. | The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used ... |
| V-252656 | | The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the c... |
| V-252657 | | OL 8 must ensure the password complexity module is enabled in the system-auth file. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-252658 | | OL 8 systems below version 8.4 must ensure the password complexity module in the system-auth file is configured for three retries or less. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-252659 | | OL 8 systems below version 8.4 must ensure the password complexity module in the password-auth file is configured for three retries or less. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-252660 | | OL 8 systems, version 8.4 and above, must ensure the password complexity module is configured for three retries or less. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-252662 | | OL 8 must not enable IPv4 packet forwarding unless the system is a router. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not ... |
| V-252663 | | The graphical display manager must not be the default target on OL 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... |
| V-255898 | | OL 8 SSH server must be configured to use only FIPS-validated key exchange algorithms. | Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized... |
| V-256978 | | OL 8 must ensure cryptographic verification of vendor software packages. | Cryptographic verification of vendor software packages ensures that all software packages are obtained from a valid source and protects against spoofi... |
| V-256979 | | OL 8 must be configured to allow sending email notifications of unauthorized configuration changes to designated personnel. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-257259 | | OL 8 must terminate idle user sessions. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management se... |
| V-274876 | | OL 8 must audit any script or executable called by cron as root or by any privileged user. | Any script or executable called by cron as root or by any privileged user must be owned by that user and must have the permissions 755 or more restric... |
| V-248549 | | OL 8 must have the "policycoreutils" package installed. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-248563 | | The OL 8 SSH server must be configured to use 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 ... |
| V-248579 | | OL 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 a... |
| V-248580 | | OL 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 a... |
| V-248586 | | OL 8 must have the package 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... |
| V-248595 | | YUM must remove all software components after updated versions have been installed on OL 8. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by advers... |
| V-248599 | | OL 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 ... |
| V-248600 | | OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. | The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to ... |
| V-248608 | | OL 8 must use a separate file system for "/var". | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248609 | | OL 8 must use a separate file system for "/var/log". | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248610 | | OL 8 must use a separate file system for the system audit data path. | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-248666 | | OL 8 must limit the number of concurrent sessions to 10 for all accounts and/or account types. | Operating system management includes the ability to control the number of users and user sessions that use an operating system. Limiting the number of... |
| V-248687 | | OL 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... |
| V-248688 | | OL 8 must enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-248689 | | OL 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... |
| V-248693 | | OL 8 must require the change of at least eight characters when passwords are changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-248709 | | All OL 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... |
| V-248717 | | OL 8 must display the date and time of the last successful account logon upon logon. | Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-248804 | | OL 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... |
| V-248821 | | OL 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 ev... |
| V-248822 | | OL 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 ev... |
| V-248826 | | OL 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 unnecessa... |
| V-248832 | | OL 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 unnecessa... |
| V-248833 | | OL 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 unnecessa... |
| V-248834 | | OL 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 unnecessa... |
| V-248872 | | OL 8 must disable the debug-shell systemd service. | The debug-shell requires no authentication and provides root privileges to anyone who has physical access to the machine. While this feature is disabl... |
| V-248896 | | The OL 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.
OL 8 installation media come w... |
| V-248897 | | The OL 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.
OL 8 installation media com... |
| V-248521 | | OL 8 must be a vendor-supported release. | Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federa... |
| V-248524 | | OL 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 cryptog... |
| V-248525 | | All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. | OL 8 systems handling data requiring "data-at-rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modificati... |
| V-248537 | | OL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user mode and maintenance. | If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenanc... |
| V-248540 | | OL 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 maintenanc... |
| V-248574 | | YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate 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... |
| V-248575 | | OL 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... |
| V-248597 | | There must be no "shosts.equiv" files on the OL 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 preve... |
| V-248598 | | There must be no ".shosts" files on the OL 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 suffi... |
| V-248649 | | Unattended or automatic logon via the OL 8 graphical user interface must not be allowed. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-248650 | | OL 8 must not allow users to override SSH environment variables. | SSH environment options potentially allow users to bypass access restriction in some configurations.... |
| V-248714 | | OL 8 must not allow accounts configured with blank or null passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-248715 | | OL 8 must not allow blank or null passwords in the system-auth file. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-248716 | | OL 8 must not allow blank or null passwords in the password-auth file. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-248823 | | OL 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 unnecessa... |
| V-248827 | | OL 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 unnecessa... |
| V-248869 | | The x86 Ctrl-Alt-Delete key sequence must be disabled on OL 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... |
| V-248870 | | The x86 Ctrl-Alt-Delete key sequence in OL 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 cas... |
| V-248873 | | The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for OL 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... |
| V-248874 | | The root account must be the only account having unrestricted access to the OL 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 op... |
| V-248903 | | A File Transfer Protocol (FTP) server package must not be installed unless mission essential on OL 8. | The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote sess... |
| V-252650 | | The OL 8 operating system must not have accounts configured with blank or null passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
