| V-271438 | | OL 9 must be a vendor supported release. | An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release... |
| V-271451 | | OL 9 must require a unique superuser's name upon booting into single-user and maintenance modes. | Having a nondefault grub superuser username makes password-guessing attacks less effective.... |
| V-271452 | | OL 9 must use a Linux Security Module configured to enforce limits on system services. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-271454 | | OL 9 must enable FIPS mode. | Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The operating system must implement cryptog... |
| V-271462 | | OL 9 must not have a File Transfer Protocol (FTP) server package installed. | The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote sess... |
| V-271463 | | OL 9 must not have a Trivial File Transfer Protocol (TFTP) server package installed. | Removing the "tftp-server" package decreases the risk of the accidental (or intentional) activation of tftp services.
If TFTP is required for operati... |
| V-271481 | | OL 9 cryptographic policy files must match files shipped with the operating system. | The OL 9 package crypto-policies defines the cryptography policies for the system.
If the files are changed from those shipped with the operating sys... |
| V-271523 | | OL 9 must check the GPG signature of locally installed software packages before installation. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-271524 | | OL 9 must check the GPG signature of software packages originating from external software repositories before installation. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-271525 | | OL 9 must have GPG signature verification enabled for all software repositories. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-271634 | | OL 9 must not allow blank or null passwords. | If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-271691 | | OL 9 must not allow unattended or automatic logon via the graphical user interface. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-271706 | | OL 9 SSHD must not allow blank passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-271707 | | OL 9 must enable the Pluggable Authentication Module (PAM) interface for SSHD. | When UsePAM is set to "yes", PAM runs through account and session types properly. This is important when restricted access to services based off of IP... |
| V-271751 | | OL 9 must be configured so that the systemd Ctrl-Alt-Delete burst key sequence is disabled. | A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case o... |
| V-271752 | | OL 9 must be configured so that the x86 Ctrl-Alt-Delete key sequence is disabled. | A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case o... |
| V-271756 | | OL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. | OL 9 systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modificati... |
| V-271757 | | OL 9 file systems must not contain shosts.equiv files. | The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for prevent... |
| V-271758 | | OL 9 file systems must not contain .shosts files. | The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not suffici... |
| V-271831 | | OL 9 must be configured so that the root account is the only account having unrestricted access to the system. | An account has root authority if it has a user identifier (UID) of "0". Multiple accounts with a UID of "0" afford more opportunity for potential intr... |
| V-271431 | | The OL 9 operating system must implement cryptographic mechanisms to prevent unauthorized modification of all information at rest. | Operating systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modif... |
| V-271433 | | OL 9 must be configured so that a separate file system must be used for user home directories (such as /home or an equivalent). | Ensuring that "/home" is mounted on its own partition enables the setting of more restrictive mount options, and also helps ensure that users cannot t... |
| V-271434 | | OL 9 must use a separate file system for /tmp. | The "/tmp" partition is used as temporary storage by many programs. Placing "/tmp" in its own partition enables the setting of more restrictive mount ... |
| V-271437 | | OL 9 must use a separate file system for /var/tmp. | The "/var/tmp" partition is used as temporary storage by many programs. Placing "/var/tmp" in its own partition enables the setting of more restrictiv... |
| V-271439 | | OL 9 vendor packaged system security patches and updates must be installed and up to date. | Installing software updates is a fundamental mitigation against the exploitation of publicly known vulnerabilities. If the most recent security patche... |
| V-271440 | | OL 9 must be configured so that the graphical display manager is not the default target unless approved. | Unnecessary service packages must not be installed to decrease the attack surface of the system. Graphical display managers have a long history of sec... |
| V-271441 | | OL 9 must require authentication to access emergency mode. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD syst... |
| V-271442 | | OL 9 must require authentication to access single-user mode. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD syst... |
| V-271443 | | OL 9 must be configured to disable the Asynchronous Transfer Mode (ATM) kernel module. | Disabling ATM protects the system against exploitation of any flaws in its implementation.... |
| V-271444 | | OL 9 must be configured to disable the Controller Area Network (CAN) kernel module. | Disabling CAN protects the system against exploitation of any flaws in its implementation.... |
| V-271445 | | OL 9 must be configured to disable the FireWire kernel module. | Disabling firewire protects the system against exploitation of any flaws in its implementation.... |
| V-271446 | | OL 9 must disable the Stream Control Transmission Protocol (SCTP) kernel module. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271447 | | OL 9 must disable the Transparent Inter Process Communication (TIPC) kernel module. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271449 | | OL 9 Bluetooth must be disabled. | This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with OL 9 systems. Wireless periphe... |
| V-271450 | | OL 9 must be configured to disable USB mass storage. | USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-0... |
| V-271453 | | OL 9 must enable the SELinux targeted policy. | Setting the SELinux policy to "targeted" or a more specialized policy ensures the system will confine processes that are likely to be targeted for exp... |
| V-271455 | | OL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a command line user logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-271456 | | OL 9 must not have the nfs-utils package installed. | "nfs-utils" provides a daemon for the kernel NFS server and related tools. This package also contains the "showmount" program. "showmount" queries the... |
| V-271457 | | OL 9 must not have the rsh-server package installed. | The "rsh-server" service provides unencrypted remote access service, which does not provide for the confidentiality and integrity of user passwords or... |
| V-271458 | | OL 9 must not have the telnet-server package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271459 | | OL 9 must not have the gssproxy package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271460 | | OL 9 must not have the iprutils package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271461 | | OL 9 must not have the tuned package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271464 | | OL 9 must not have the quagga package installed. | Quagga is a network routing software suite providing implementations of Open Shortest Path First (OSPF), Routing Information Protocol (RIP), Border Ga... |
| V-271465 | | OL 9 must not have a graphical display manager installed unless approved. | Unnecessary service packages must not be installed to decrease the attack surface of the system. Graphical display managers have a long history of sec... |
| V-271466 | | OL 9 must not have the sendmail package installed. | The sendmail software was not developed with security in mind, and its design prevents it from being effectively contained by SELinux. Postfix must be... |
| V-271467 | | OL 9 must have policycoreutils package installed. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-271468 | | OL 9 policycoreutils-python-utils package must be installed. | The policycoreutils-python-utils package is required to operate and manage an SELinux environment and its policies. It provides utilities such as sema... |
| V-271469 | | OL 9 must have the firewalld package installed. | Firewalld provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services, s... |
| V-271470 | | OL 9 must be configured so that the firewalld service is active. | Firewalld provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services, s... |
| V-271471 | | OL 9 must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-271472 | | OL 9 must control remote access methods. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-271473 | | OL 9 must be configured so that the firewall employs 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-271474 | | OL 9 must have the sudo package installed. | sudo is a program designed to allow a system administrator to give limited root privileges to users and log root activity. The basic philosophy is to ... |
| V-271475 | | OL 9 must use the invoking user's password for privilege escalation when using sudo. | If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" u... |
| V-271476 | | OL 9 must restrict privilege elevation to authorized personnel. | If the sudoers file is not configured correctly, any user defined on the system can initiate privileged actions on the target system.... |
| V-271477 | | OL 9 must have the crypto-policies package installed. | Centralized cryptographic policies simplify applying secure ciphers across an operating system and the applications that run on that operating system.... |
| V-271478 | | OL 9 must implement a FIPS 140-3 compliant system-wide cryptographic policy. | Centralized cryptographic policies simplify applying secure ciphers across an operating system and the applications that run on that operating system.... |
| V-271479 | | OL 9 must not allow the cryptographic policy to be overridden. | Centralized cryptographic policies simplify applying secure ciphers across an operating system and the applications that run on that operating system.... |
| V-271480 | | OL 9 must be configured so that the cryptographic hashes of system files match vendor values. | The hashes of important files like system executables should match the information given by the RPM database. Executables with erroneous hashes could ... |
| V-271482 | | OL 9 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-271483 | | OL 9 networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-271484 | | The OL 9 SSH daemon must be configured to use systemwide cryptographic policies. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-271485 | | OL 9 SSH server must be configured to use only ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-271486 | | OL 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-271487 | | OL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a SSH logon. | The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, syste... |
| V-271488 | | OL 9 must have the openssh-clients package installed. | This package includes utilities to make encrypted connections and transfer files securely to SSH servers.... |
| V-271489 | | OL 9 SSH client must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-271490 | | OL 9 SSH client must be configured to use only DOD-approved Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-271491 | | OL 9 must have the openssl-pkcs11 package installed. | Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires us... |
| V-271492 | | OL 9 must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-271493 | | OL 9 must have the SSSD package installed. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-271494 | | OL 9 must use the SSSD package for multifactor authentication services. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-271495 | | OL 9 must have the s-nail package installed. | The s-nail package provides the mail command required to allow sending email notifications of unauthorized configuration changes to designated personn... |
| V-271496 | | OL 9 must have the Advanced Intrusion Detection Environment (AIDE) package installed. | Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is d... |
| V-271497 | | OL 9 must routinely check the baseline configuration for unauthorized changes and notify the system administrator (SA) when anomalies in the operation of any security functions are discovered. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-271498 | | OL 9 must use a file integrity tool that is configured to use FIPS 140-3-approved cryptographic hashes for validating file contents and directories. | OL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable... |
| V-271501 | | OL 9 must have the chrony package installed. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular ev... |
| V-271502 | | OL 9 must enable the chronyd service. | 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-271503 | | OL 9 must have the USBGuard package installed. | The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device autho... |
| V-271504 | | OL 9 must enable the USBGuard package. | The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device autho... |
| V-271505 | | OL 9 must have the subscription-manager package installed. | Oracle Linux Manager, based on the Spacewalk open source software, helps automate Oracle Linux systems management. This enables users to control the s... |
| V-271506 | | OL 9 must have the fapolicy module installed. | The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software program... |
| V-271507 | | OL 9 must enable the fapolicy module. | The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software program... |
| V-271508 | | OL 9 must have the rsyslog package installed. | rsyslogd is a system utility providing support for message logging. Support for both internet and Unix domain sockets enables this utility to support ... |
| V-271509 | | OL 9 must be configured so that the rsyslog service is active. | The rsyslog service must be running to provide logging services, which are essential to system administration.... |
| V-271510 | | OL 9 must have the packages required for encrypting offloaded audit logs installed. | The rsyslog-gnutls package provides Transport Layer Security (TLS) support for the rsyslog daemon, which enables secure remote logging.... |
| V-271512 | | OL 9 must have the rng-tools package installed. | rng-tools provides hardware random number generator tools, such as those used in the formation of x509/PKI certificates.... |
| V-271513 | | OL 9 must have the nss-tools package installed. | Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server application... |
| V-271514 | | OL 9 must have the pcsc-lite package installed. | The pcsc-lite package must be installed if it is to be available for multifactor authentication using smart cards.... |
| V-271515 | | OL 9 must have the opensc package installed. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
The DOD has mandated the use of the Common Access... |
| V-271516 | | OL 9 must be configured so that the pcscd service is active. | The information system ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentic... |
| V-271517 | | OL 9 must have the libreswan package installed. | Providing the ability for remote users or systems to initiate a secure VPN connection protects information when it is transmitted over a wide area net... |
| V-271518 | | OL 9 must have the gnutls-utils package installed. | GnuTLS is a secure communications library implementing the SSL, TLS, and DTLS protocols and technologies around them. It provides a simple C language ... |
| V-271519 | | OL 9 must have the audit package installed. | Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to es... |
| V-271520 | | OL 9 audit service must be enabled. | Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage o... |
| V-271521 | | OL 9 must have the audispd-plugins package installed. | audispd-plugins provides plug-ins for the real-time interface to the audit subsystem, audispd. These plug-ins can do things like relay events to remot... |
| V-271526 | | OL 9 must ensure cryptographic verification of vendor software packages. | Cryptographic verification of vendor software packages ensures that all software packages are obtained from a valid source and protects against spoofi... |
| V-271527 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers. | The actions taken by system administrators must be audited to keep a record of what was executed on the system, as well as for accountability purposes... |
| V-271528 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/ directory. | The actions taken by system administrators must be audited to keep a record of what was executed on the system, as well as for accountability purposes... |
| V-271529 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, ... |
| V-271530 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, ... |
| V-271531 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, ... |
| V-271532 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, ... |
| V-271533 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, ... |
| V-271534 | | OL 9 must audit all uses of the unix_update command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271535 | | OL 9 must audit all uses of the su command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271536 | | OL 9 must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271537 | | OL 9 must audit all uses of the chage command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271538 | | OL 9 must audit all uses of the chcon command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271539 | | OL 9 must audit all uses of the setfacl command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271540 | | OL 9 must audit all uses of the chsh command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271541 | | OL 9 must audit all uses of the crontab command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271542 | | OL 9 must audit all uses of the gpasswd command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271543 | | OL 9 must audit all uses of the newgrp command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271544 | | OL 9 must audit all uses of the pam_timestamp_check command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271545 | | OL 9 must audit all uses of the passwd command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271546 | | OL 9 must audit all uses of the postdrop command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271547 | | OL 9 must audit all uses of the postqueue command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271548 | | OL 9 must audit all uses of the ssh-agent command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271549 | | OL 9 must audit all uses of the ssh-keysign command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271550 | | OL 9 must audit all uses of the sudoedit command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271551 | | OL 9 must audit all uses of the unix_chkpwd command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271552 | | OL 9 must audit all uses of the userhelper command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271553 | | OL 9 must audit all uses of the mount command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271554 | | OL 9 must audit all uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271555 | | OL 9 must audit all uses of the chmod, fchmod, and fchmodat system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271556 | | OL 9 must audit all uses of the chown, fchown, fchownat, and lchown system calls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271557 | | OL 9 must audit all uses of the semanage command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271558 | | OL 9 must audit all uses of the setfiles command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271559 | | OL 9 must audit all uses of the setsebool command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271560 | | OL 9 must audit all uses of the chacl command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271561 | | OL 9 must audit all uses of the sudo command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271562 | | OL 9 must audit all uses of the usermod command. | Without generating audit record specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and inv... |
| V-271563 | | OL 9 must audit all uses of the rename, unlink, rmdir, renameat, and unlinkat system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271564 | | OL 9 must audit all uses of the delete_module system call. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271565 | | OL 9 must audit all uses of the init_module and finit_module system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271566 | | OL 9 must audit all uses of the kmod command. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-271567 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/lastlog. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271568 | | OL 9 must audit all uses of umount system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271569 | | OL 9 must use cryptographic mechanisms to protect the integrity of audit tools. | Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit informat... |
| V-271570 | | OL 9 must audit uses of the execve system call. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromise... |
| V-271571 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/faillock. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271572 | | OL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/tallylog. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-271573 | | OL 9 must be configured so that successful/unsuccessful uses of the init command generate an audit record. | Misuse of the init command may cause availability issues for the system.... |
| V-271574 | | OL 9 must be configured so that successful/unsuccessful uses of the poweroff command generate an audit record. | Misuse of the poweroff command may cause availability issues for the system.... |
| V-271575 | | OL 9 must be configured so that successful/unsuccessful uses of the reboot command generate an audit record. | Misuse of the reboot command may cause availability issues for the system.... |
| V-271576 | | OL 9 must be configured so that successful/unsuccessful uses of the shutdown command generate an audit record. | Misuse of the shutdown command may cause availability issues for the system.... |
| V-271578 | | OL 9 must label all offloaded audit logs before sending them to the central log server. | Enriched logging is needed to determine who, what, and when events occur on a system. Without this, determining root cause of an event will be much mo... |
| V-271579 | | OL 9 audit system must take appropriate action when an error writing to the audit storage volume occurs. | It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit ... |
| V-271580 | | OL 9 audit system must take appropriate action when the audit storage volume is full. | It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit ... |
| V-271581 | | OL 9 audit system must take appropriate action when the audit files have reached maximum size. | It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit ... |
| V-271582 | | OL 9 must periodically flush audit records to disk to prevent the loss of audit records. | If option "freq" is not set to a value that requires audit records being written to disk after a threshold number is reached, then audit records may b... |
| V-271583 | | OL 9 audit logs must be group-owned by root or by a restricted logging group to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Satisfies: SRG... |
| V-271584 | | OL 9 audit log directory must be owned by root to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Satisfies: SRG... |
| V-271585 | | OL 9 audit logs file must have mode 0600 or less permissive to prevent unauthorized access to the audit log. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271586 | | OL 9 audit system must audit local events. | Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to es... |
| V-271587 | | OL 9 must allow only the information system security manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | Without the capability to restrict the roles and individuals that can select which events are audited, unauthorized personnel may be able to prevent t... |
| V-271588 | | OL 9 /etc/audit/auditd.conf file must have 0640 or less permissive to prevent unauthorized access. | Without the capability to restrict the roles and individuals that can select which events are audited, unauthorized personnel may be able to prevent t... |
| V-271589 | | OL 9 must forward mail from postmaster to the root account using a postfix alias. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-271590 | | OL 9 must take appropriate action when a critical audit processing failure occurs. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-271591 | | The OL 9 system administrator (SA) and/or information system security officer (ISSO) (at a minimum) must be alerted of an audit processing failure event. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-271593 | | OL 9 must produce audit records containing information to establish the identity of any individual or process associated with the event. | Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to es... |
| V-271594 | | OL 9 must be configured so that successful/unsuccessful uses of the umount system call generate an audit record. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing D... |
| V-271595 | | OL 9 must be configured so that successful/unsuccessful uses of the umount2 system call generate an audit record. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing d... |
| V-271596 | | OL 9 must allocate audit record storage capacity to store at least one week's worth of audit records. | To ensure OL 9 systems have a sufficient storage capacity in which to write the audit logs, OL 9 needs to be able to allocate audit record storage cap... |
| V-271597 | | OL 9 must be configured to offload audit records onto a different system from the system being audited via syslog. | The auditd service does not include the ability to send audit records to a centralized server for management directly. However, it can use a plug-in f... |
| V-271598 | | OL 9 must take appropriate action when the internal event queue is full. | The audit system should have an action setup in the event the internal event queue becomes full so that no data is lost. Information stored in one loc... |
| V-271599 | | OL 9 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. | If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storag... |
| V-271600 | | OL 9 must notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume 75 percent utilization. | If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storag... |
| V-271601 | | OL 9 must take action when allocated audit record storage volume reaches 95 percent of the audit record storage capacity. | If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity.... |
| V-271602 | | OL 9 must write audit records to disk. | Audit data should be synchronously written to disk to ensure log integrity. This setting ensures that all audit event data is written disk.... |
| V-271603 | | OL 9 must act when allocated audit record storage volume reaches 95 percent of the repository maximum audit record storage capacity. | If action is not taken when storage volume reaches 95 percent utilization, the auditing system may fail when the storage volume reaches capacity.... |
| V-271604 | | OL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly tru... |
| V-271605 | | OL 9, for PKI-based authentication, must enforce authorized access to the corresponding private key. | If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure.
Th... |
| V-271606 | | OL 9 must map the authenticated identity to the user or group account for PKI-based authentication. | Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will n... |
| V-271607 | | OL 9 must enable certificate-based smart card authentication. | Without the use of multifactor authentication (MFA), the ease of access to privileged functions is greatly increased. Multifactor authentication requi... |
| V-271608 | | OL 9 must implement certificate status checking for multifactor authentication (MFA). | 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-271609 | | OL 9 must prohibit the use of cached authenticators after one day. | If cached authentication information is out-of-date, the validity of the authentication information may be questionable.... |
| V-271610 | | OL 9 must use the CAC smart card driver. | Smart card login provides two-factor authentication stronger than that provided by a username and password combination. Smart cards leverage public ke... |
| V-271611 | | OL 9 must ensure the password complexity module is enabled in the system-auth file. | Enabling PAM password complexity permits enforcement of strong passwords and consequently makes the system less prone to dictionary attacks.... |
| V-271612 | | OL 9 must ensure the password complexity module in the system-auth file is configured for three retries or less. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271613 | | OL 9 must enforce password complexity by requiring that at least one uppercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271614 | | OL 9 must ensure the password complexity module is enabled in the password-auth file. | Enabling PAM password complexity permits enforcement of strong passwords and consequently makes the system less prone to dictionary attacks.
Satisfie... |
| V-271615 | | OL 9 must enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271616 | | OL 9 must enforce password complexity by requiring that at least one numeric character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271617 | | OL 9 must require the change of at least eight characters when passwords are changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271618 | | OL 9 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271619 | | OL 9 must require the maximum number of repeating characters be limited to three when passwords are changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271620 | | OL 9 must require the change of at least four character classes when passwords are changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271621 | | OL 9 must enforce password complexity rules for the root account. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271622 | | OL 9 must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-271623 | | OL 9 must be configured to use the shadow file to store only encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-271624 | | OL 9 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-3 approved cryptographic hashing algorithm for system authentication. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore, cannot be relied upon to provide co... |
| V-271625 | | OL 9 password-auth must be configured to use a sufficient number of hashing rounds. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-271626 | | OL 9 system-auth must be configured to use a sufficient number of hashing rounds. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-271627 | | OL 9 shadow password suite must be configured to use a sufficient number of hashing rounds. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-271628 | | OL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords. | The system must use a strong hashing algorithm to store the password.
Passwords need to be protected at all times, and encryption is the standard met... |
| V-271629 | | OL 9 passwords for new users or password changes must have a 24-hour 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-271630 | | OL 9 passwords must have a 24-hour 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-271631 | | OL 9 user account passwords for new users or password changes must have a 60-day maximum password lifetime restriction in /etc/login.defs. | Any password, no matter how complex, can eventually be cracked; therefore, passwords need to be changed periodically. If the operating system does not... |
| V-271632 | | OL 9 user account passwords must have a 60-day maximum password lifetime restriction. | Any password, no matter how complex, can eventually be cracked; therefore, passwords need to be changed periodically. If OL 9 does not limit the lifet... |
| V-271633 | | OL 9 passwords must be created with a minimum of 15 characters. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-271635 | | OL 9 must require a boot loader superuser password. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD syst... |
| V-271636 | | OL 9 must enforce password complexity by requiring that at least one special character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271637 | | OL 9 must prevent the use of dictionary words for passwords. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-271638 | | OL 9 must not have accounts configured with blank or null passwords. | If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-271639 | | OL 9 file system automount function must be disabled unless required. | An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous aut... |
| V-271640 | | OL 9 must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS. | When an NFS server is configured to use RPCSEC_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and gro... |
| V-271641 | | OL 9 must prevent special devices on file systems that are imported via Network File System (NFS). | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271642 | | OL 9 must prevent code from being executed on file systems that are imported via Network File System (NFS). | The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271643 | | OL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that are imported via Network File System (NFS). | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271644 | | OL 9 must prevent code from being executed on file systems that are used with removable media. | The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271645 | | OL 9 must prevent special devices on file systems that are used with removable media. | The "nodev" mount option causes the system not to interpret character or block special devices. Executing character or blocking special devices from u... |
| V-271646 | | OL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media. | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271647 | | OL 9 must mount /boot with the nodev option. | The only legitimate location for device files is the "/dev" directory located on the root partition. The only exception to this is chroot jails.... |
| V-271648 | | OL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot directory. | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271649 | | OL 9 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory. | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271650 | | OL 9 must mount /dev/shm with the nodev option. | The nodev mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrus... |
| V-271651 | | OL 9 must mount /dev/shm with the noexec option. | The noexec mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved b... |
| V-271652 | | OL 9 must mount /dev/shm with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271653 | | OL 9 must mount /tmp with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271654 | | OL 9 must mount /tmp with the noexec option. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271655 | | OL 9 must mount /tmp with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271656 | | OL 9 must mount /var with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271657 | | OL 9 must mount /var/log with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271658 | | OL 9 must mount /var/log with the noexec option. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271659 | | OL 9 must mount /var/log with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271660 | | OL 9 must mount /var/log/audit with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271661 | | OL 9 must mount /var/log/audit with the noexec option. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271662 | | OL 9 must mount /var/log/audit with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271663 | | OL 9 must mount /var/tmp with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271664 | | OL 9 must mount /var/tmp with the noexec option. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-271665 | | OL 9 must mount /var/tmp with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271666 | | OL 9 must prevent device files from being interpreted on file systems that contain user home directories. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untr... |
| V-271667 | | OL 9 must prevent files with the setuid and setgid bit set from being executed on file systems that contain user home directories. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-271668 | | OL 9 must prevent code from being executed on file systems that contain user home directories. | The noexec mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved b... |
| V-271669 | | OL 9 must prevent special devices on nonroot 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-271670 | | OL 9 must disable the graphical user interface automount function unless required. | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-G... |
| V-271671 | | OL 9 must disable the graphical user interface autorun function unless required. | Allowing autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents autorun commands from executing.... |
| V-271672 | | OL 9 must disable the user list at logon for graphical user interfaces. | Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to enumerate known user accounts without au... |
| V-271673 | | OL 9 must initiate a session lock for graphical user interfaces when the screensaver is activated. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-271674 | | OL 9 must automatically lock graphical user sessions after 15 minutes of inactivity. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-271676 | | OL 9 must conceal, via the session lock, information previously visible on the display with a publicly viewable image. | Setting the screensaver mode to blank-only conceals the contents of the display from passersby.... |
| V-271677 | | OL 9 must disable the ability of a user to accidentally press Ctrl-Alt-Del and cause a system to shut down or reboot. | A locally logged-in user who presses Ctrl-Alt-Del, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of... |
| V-271678 | | OL 9 must prevent a user from overriding the disabling of the graphical user interface automount function. | A nonprivileged account is any operating system account with authorizations of a nonprivileged user.
Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-0003... |
| V-271679 | | OL 9 must prevent a user from overriding the disabling of the graphical user interface autorun function. | Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Secu... |
| V-271680 | | OL 9 must prevent a user from overriding the banner-message-enable setting for the graphical user interface. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-271681 | | OL 9 must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-271682 | | OL 9 must prevent a user from overriding the session idle-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-271683 | | OL 9 must prevent a user from overriding the session lock-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-271684 | | OL 9 must prevent a user from overriding the disabling of the graphical user smart card removal action. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-271685 | | OL 9 must disable the ability of a user to restart the system from the login screen. | A user who is at the console can reboot the system at the login screen. If restart or shutdown buttons are pressed at the login screen, this can creat... |
| V-271686 | | OL 9 must prevent a user from overriding the disable-restart-buttons setting for the graphical user interface. | A user who is at the console can reboot the system at the login screen. If restart or shutdown buttons are pressed at the login screen, this can creat... |
| V-271687 | | OL 9 must prevent a user from overriding the Ctrl-Alt-Del sequence settings for the graphical user interface. | A locally logged-in user who presses Ctrl-Alt-Del, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of... |
| V-271688 | | OL 9 must be configured to enable the display of 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-271689 | | OL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-271690 | | OL 9 must be able to directly initiate a session lock for all connection types using smart card when the smart card is removed. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-271692 | | OL 9 effective dconf policy must match the policy keyfiles. | Unlike text-based keyfiles, the binary database is impossible to check through most automated and all manual means; therefore, to evaluate dconf confi... |
| V-271693 | | OL 9 must define default permissions for the bash shell. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 or less permissive. Although u... |
| V-271694 | | OL 9 must define default permissions for the c shell. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 or less permissive. Although u... |
| V-271695 | | OL 9 must define default permissions for the system default profile. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 or less permissive. Although u... |
| V-271696 | | OL 9 must define default permissions for all authenticated users in such a way that the user can only read and modify their own files. | Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.... |
| V-271699 | | OL 9 must securely compare internal information system clocks at least every 24 hours. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular ev... |
| V-271701 | | OL 9 must block unauthorized peripherals before establishing a connection. | The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device autho... |
| V-271702 | | OL 9 must disable automatic mounting of Universal Serial Bus (USB) mass storage driver. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include, but ... |
| V-271703 | | OL 9 must log SSH connection attempts and failures to the server. | SSH provides several logging levels with varying amounts of verbosity. "DEBUG" is specifically not recommended other than strictly for debugging SSH c... |
| V-271704 | | OL 9 SSH daemon must not allow Generic Security Service Application Program Interface (GSSAPI) authentication. | GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the ... |
| V-271705 | | OL 9 must force a frequent session key renegotiation for SSH connections to the server. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-271708 | | OL 9 must not permit direct logons to the root account using remote access via SSH. | Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging directly on ... |
| V-271709 | | OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-271710 | | OL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-271711 | | OL 9 SSH daemon must not allow rhosts authentication. | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.... |
| V-271712 | | OL 9 SSH daemon must not allow known hosts authentication. | Configuring the IgnoreUserKnownHosts setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even ... |
| V-271713 | | OL 9 SSH daemon must disable remote X connections for interactive users. | When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the SSHD proxy display is configured to listen o... |
| V-271714 | | OL 9 SSH daemon must perform strict mode checking of home directory configuration files. | If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user.... |
| V-271715 | | OL 9 SSH daemon must display the date and time of the last successful account logon upon an SSH logon. | Providing users feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-271716 | | OL 9 SSH daemon must prevent remote hosts from connecting to the proxy display. | When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the SSHD proxy display is configured to listen o... |
| V-271717 | | OL 9 SSH daemon must not allow compression or must only allow compression after successful authentication. | If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the ... |
| V-271718 | | OL 9 SSH daemon must not allow Kerberos authentication. | Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled thr... |
| V-271719 | | OL 9 must not allow a noncertificate trusted host SSH logon to the system. | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.... |
| V-271720 | | OL 9 must not allow users to override SSH environment variables. | SSH environment options potentially allow users to bypass access restriction in some configurations.... |
| V-271721 | | OL 9 SSHD must accept public key authentication. | Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires us... |
| V-271722 | | OL 9 must require reauthentication when using the "sudo" command. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the c... |
| V-271723 | | OL 9 must restrict the use of the su command. | The su program allows to run commands with a substitute user and group ID. It is commonly used to run commands as the root user. Limiting access to su... |
| V-271724 | | OL 9 must require users to reauthenticate for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ca... |
| V-271725 | | OL 9 must require users to provide a password for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ca... |
| V-271726 | | OL 9 must not be configured to bypass password requirements for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When operating systems provide the cap... |
| V-271727 | | OL 9 must disable the use of user namespaces. | User namespaces are used primarily for Linux containers. The value "0" disallows the use of user namespaces.... |
| V-271728 | | OL 9 must disable the kernel.core_pattern. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data an... |
| V-271729 | | OL 9 must disable core dump backtraces. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data an... |
| V-271730 | | OL 9 must disable storing core dumps. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data an... |
| V-271731 | | OL 9 must disable core dumps for all users. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data an... |
| V-271732 | | OL 9 must disable acquiring, saving, and processing core dumps. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data an... |
| V-271733 | | OL 9 must be configured so that the kdump service is disabled. | Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps consume a considerable amount of disk spa... |
| V-271734 | | OL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks. | Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Secur... |
| V-271736 | | OL 9 must disable the ability of systemd to spawn an interactive boot process. | Using interactive or recovery boot, the console user could disable auditing, firewalls, or other services, weakening system security.... |
| V-271737 | | OL 9 must disable virtual system calls. | System calls are special routines in the Linux kernel, which userspace applications ask to do privileged tasks. Invoking a system call is an expensive... |
| V-271738 | | OL 9 must clear the page allocator to prevent use-after-free attacks. | Poisoning writes an arbitrary value to freed pages, so any modification or reference to that page after being freed or before being initialized will b... |
| V-271739 | | OL 9 systemd-journald service must be enabled. | In the event of a system failure, OL 9 must preserve any information necessary to determine cause of failure and any information necessary to return t... |
| V-271740 | | OL 9 must enable kernel parameters to enforce discretionary access control on hardlinks. | By enabling the fs.protected_hardlinks kernel parameter, users can no longer create soft or hard links to files they do not own. Disallowing such hard... |
| V-271741 | | OL 9 must enable kernel parameters to enforce discretionary access control on symlinks. | By enabling the fs.protected_symlinks kernel parameter, symbolic links are permitted to be followed only when outside a sticky world-writable director... |
| V-271742 | | OL 9 debug-shell systemd service must be disabled. | The debug-shell requires no authentication and provides root privileges to anyone who has physical access to the machine. While this feature is disabl... |
| V-271743 | | OL 9 IP tunnels must use 140-3 approved cryptographic algorithms. | Overriding the system crypto policy makes the behavior of the Libreswan service violate expectations and makes system configuration more fragmented.... |
| V-271744 | | OL 9 must have mail aliases to notify the information system security officer (ISSO) and system administrator (SA) (at a minimum) in the event of an audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-271745 | | OL 9 must restrict access to the kernel message buffer. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-271746 | | OL 9 must prevent kernel profiling by nonprivileged users. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-271747 | | OL 9 must restrict exposed kernel pointer addresses access. | Exposing kernel pointers (through procfs or "seq_printf()") exposes kernel writeable structures, which may contain functions pointers. If a write vuln... |
| V-271748 | | OL 9 must disable access to network bpf system call from nonprivileged processes. | Loading and accessing the packet filters programs and maps using the bpf() system call has the potential of revealing sensitive information about the ... |
| V-271749 | | OL 9 must restrict usage of ptrace to descendant processes. | Unrestricted usage of ptrace allows compromised binaries to run ptrace on other processes of the user. Like this, the attacker can steal sensitive inf... |
| V-271750 | | OL 9 must automatically exit interactive command shell user sessions after 15 minutes of inactivity. | Terminating an idle interactive command shell user session within a short time period reduces the window of opportunity for unauthorized personnel to ... |
| V-271754 | | OL 9 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period. | By limiting the number of failed logon attempts the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, i... |
| V-271755 | | OL 9 must maintain an account lock until the locked account is released by an administrator. | By limiting the number of failed logon attempts the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, i... |
| V-271759 | | OL 9 must implement DOD-approved encryption in the bind package. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Cryptographic mechanisms used for pr... |
| V-271760 | | OL 9 must implement nonexecutable data to protect its memory from unauthorized code execution. | ExecShield uses the segmentation feature on all x86 systems to prevent execution in memory higher than a certain address. It writes an address as a li... |
| V-271761 | | OL 9 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. | ASLR makes it more difficult for an attacker to predict the location of attack code they have introduced into a process' address space during an attem... |
| V-271762 | | OL 9 must use mechanisms meeting the requirements of applicable federal laws, executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. | Overriding the system crypto policy makes the behavior of Kerberos violate expectations and makes system configuration more fragmented.... |
| V-271763 | | OL 9 must be configured to prevent unrestricted mail relaying. | If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthor... |
| V-271764 | | OL 9 Trivial File Transfer Protocol (TFTP) daemon must be configured to operate in secure mode if the TFTP server is required. | Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files. Using the "-s" option causes t... |
| V-271765 | | OL 9 must be configured so that local initialization files do 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-271766 | | OL 9 must prevent the loading of a new kernel for later execution. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-271767 | | OL 9 must prevent system daemons from using Kerberos for authentication. | Unapproved mechanisms used for authentication to the cryptographic module are not verified; therefore, cannot be relied upon to provide confidentialit... |
| V-271768 | | OL 9 must enable hardening for the Berkeley Packet Filter (BPF) just-in-time compiler. | When hardened, the extended BPF just-in-time (JIT) compiler will randomize any kernel addresses in the BPF programs and maps and will not expose the J... |
| V-271769 | | OL 9 must be configured so that all system device files are correctly labeled to prevent unauthorized modification. | If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized op... |
| V-271770 | | OL 9 must not have unauthorized accounts. | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for indiv... |
| V-271771 | | OL 9 SSH private host key files must have mode 0640 or less permissive. | If an unauthorized user obtains the private SSH host key file, the host could be impersonated.... |
| V-271772 | | OL 9 SSH public host key files must have mode 0644 or less permissive. | If a public host key file is modified by an unauthorized user, the SSH service may be compromised.... |
| V-271773 | | OL 9 system commands must be group-owned by root or a system account. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271774 | | OL 9 system commands must be owned by root. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271775 | | OL 9 system commands must have mode 755 or less permissive. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271776 | | OL 9 SSH server configuration file must be group-owned by root. | Service configuration files enable or disable features of their respective services, which if configured incorrectly, can lead to insecure and vulnera... |
| V-271777 | | OL 9 SSH server configuration file must be owned by root. | Service configuration files enable or disable features of their respective services, which if configured incorrectly, can lead to insecure and vulnera... |
| V-271778 | | OL 9 SSH server configuration file must have mode 0600 or less permissive. | Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable... |
| V-271779 | | OL 9 must be configured so that a sticky bit must be set on all public directories. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-271780 | | OL 9 local files and directories must have a valid group owner. | Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files with... |
| V-271781 | | OL 9 local files and directories must have a valid owner. | Unowned files and directories may be unintentionally inherited if a user is assigned the same user identifier "UID" as the UID of the unowned files.... |
| V-271782 | | OL 9 local initialization files must have mode 0740 or less permissive. | Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accou... |
| V-271783 | | OL 9 local interactive user home directories must be group-owned by the home directory owner's primary group. | If the Group Identifier (GID) of a local interactive user's home directory is not the same as the primary GID of the user, this would allow unauthoriz... |
| V-271784 | | OL 9 local interactive user home directories must have mode 0750 or less permissive. | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.... |
| V-271785 | | OL 9 world-writable directories must be owned by root, sys, bin, or an application user. | If a world-writable directory is not owned by root, sys, bin, or an application user identifier (UID), unauthorized users may be able to modify files ... |
| V-271786 | | OL 9 library directories must be group-owned by root or a system account. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271787 | | OL 9 library directories must be owned by root. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271788 | | OL 9 library directories must have mode 755 or less permissive. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271789 | | OL 9 library files must be group-owned by root or a system account. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271790 | | OL 9 library files must be owned by root. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271791 | | OL 9 library files must have mode 755 or less permissive. | If OL 9 allowed any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and... |
| V-271792 | | OL 9 /boot/grub2/grub.cfg file must be group-owned by root. | The "root" group is a highly privileged group. The group-owner of this file should not have any access privileges.... |
| V-271793 | | OL 9 /boot/grub2/grub.cfg file must be owned by root. | The "/boot/grub2/grub.cfg" file stores sensitive system configuration. Protection of this file is critical for system security.... |
| V-271794 | | OL 9 /etc/group file must be group-owned by root. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system securit... |
| V-271795 | | OL 9 /etc/group- file must be group-owned by root. | The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protect... |
| V-271796 | | OL 9 /etc/group file must be owned by root. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system securit... |
| V-271797 | | OL 9 /etc/group- file must be owned by root. | The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protect... |
| V-271798 | | OL 9 /etc/group file must have mode 0644 or less permissive to prevent unauthorized access. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system securit... |
| V-271799 | | OL 9 /etc/group- file must have mode 0644 or less permissive to prevent unauthorized access. | The "/etc/group-" file is a backup file of "/etc/group", and as such, contains information regarding groups that are configured on the system. Protect... |
| V-271800 | | OL 9 /etc/gshadow file must be group-owned by root. | The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.... |
| V-271801 | | OL 9 /etc/gshadow- file must be group-owned by root. | The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system se... |
| V-271802 | | OL 9 /etc/gshadow file must be owned by root. | The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.... |
| V-271803 | | OL 9 /etc/gshadow- file must be owned by root. | The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system se... |
| V-271804 | | OL 9 /etc/gshadow file must have mode 0000 or less permissive to prevent unauthorized access. | The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security.... |
| V-271805 | | OL 9 /etc/gshadow- file must have mode 0000 or less permissive to prevent unauthorized access. | The "/etc/gshadow-" file is a backup of "/etc/gshadow", and as such, contains group password hashes. Protection of this file is critical for system se... |
| V-271806 | | OL 9 /etc/passwd file must be group-owned by root. | The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security... |
| V-271807 | | OL 9 /etc/passwd- file must be group-owned by root. | The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protec... |
| V-271808 | | OL 9 /etc/passwd file must be owned by root. | The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security... |
| V-271809 | | OL 9 /etc/passwd- file must be owned by root. | The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protec... |
| V-271810 | | OL 9 /etc/passwd file must have mode 0644 or less permissive to prevent unauthorized access. | If the "/etc/passwd" file is writable by a group-owner or the world the risk of its compromise is increased. The file contains the list of accounts on... |
| V-271811 | | OL 9 /etc/passwd- file must have mode 0644 or less permissive to prevent unauthorized access. | The "/etc/passwd-" file is a backup file of "/etc/passwd", and as such, contains information about the users that are configured on the system. Protec... |
| V-271812 | | OL 9 /etc/shadow file must be group-owned by root. | The "/etc/shadow" file stores password hashes. Protection of this file is critical for system security.... |
| V-271813 | | OL 9 /etc/shadow- file must be group-owned by root. | The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of ... |
| V-271814 | | OL 9 /etc/shadow file must be owned by root. | The "/etc/shadow" file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security.... |
| V-271815 | | OL 9 /etc/shadow- file must be owned by root. | The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of ... |
| V-271816 | | OL 9 /etc/shadow- file must have mode 0000 or less permissive to prevent unauthorized access. | The "/etc/shadow-" file is a backup file of "/etc/shadow", and as such, contains the list of local system accounts and password hashes. Protection of ... |
| V-271817 | | OL 9 /etc/shadow file must have mode 0000 to prevent unauthorized access. | The "/etc/shadow" file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security.... |
| V-271818 | | OL 9 /var/log directory must be group-owned by root. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271819 | | OL 9 /var/log directory must be owned by root. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271820 | | OL 9 /var/log directory must have mode 0755 or less permissive. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271821 | | OL 9 /var/log/messages file must be group-owned by root. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271822 | | OL 9 /var/log/messages file must be owned by root. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271823 | | OL 9 /var/log/messages file must have mode 0640 or less permissive. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-271824 | | OL 9 audit tools must be group-owned by root. | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data; therefore, protecting audit tool... |
| V-271825 | | OL 9 audit tools must be owned by root. | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tool... |
| V-271826 | | OL 9 audit tools must have a mode of 0755 or less permissive. | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tool... |
| V-271827 | | OL 9 cron configuration directories must have a mode of 0700 or less permissive. | Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable... |
| V-271828 | | OL 9 cron configuration files directory must be group-owned by root. | Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable... |
| V-271829 | | OL 9 cron configuration files directory must be owned by root. | Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable... |
| V-271830 | | OL 9 /etc/crontab file must have mode 0600. | Service configuration files enable or disable features of their respective services that if configured incorrectly can lead to insecure and vulnerable... |
| V-271832 | | OL 9 duplicate User IDs (UIDs) must not exist for interactive users. | To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and co... |
| V-271833 | | OL 9 local interactive users must have a home directory assigned in the /etc/passwd file. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-271834 | | OL 9 interactive users must have a primary group that exists. | If a user is assigned the Group Identifier (GID) of a group that does not exist on the system, and a group with the GID is subsequently created, the u... |
| V-271835 | | OL 9 groups must have unique Group ID (GID). | To ensure accountability and prevent unauthenticated access, groups must be identified uniquely to prevent potential misuse and compromise of the syst... |
| V-271836 | | OL 9 must configure SELinux context type to allow the use of a nondefault faillock tally directory. | Not having the correct SELinux context on the faillock directory may lead to unauthorized access to the directory.... |
| V-271837 | | OL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. | If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks.... |
| V-271838 | | OL 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. | If the pam_faillock.so module is not loaded, the system will not correctly lockout accounts to prevent password guessing attacks.... |
| V-271839 | | OL 9 must automatically lock an account when three unsuccessful logon attempts occur. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-271840 | | OL 9 must automatically lock the root account until the root account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, also known as brute-forcing, is re... |
| V-271841 | | OL 9 must log username information when unsuccessful logon attempts occur. | Without auditing of these events, it may be harder or impossible to identify what an attacker did after an attack.... |
| V-271842 | | OL 9 must ensure account lockouts persist. | Having lockouts persist across reboots ensures that account is only unlocked by an administrator. If the lockouts did not persist across reboots, an a... |
| V-271843 | | OL 9 must automatically expire temporary accounts within 72 hours. | Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware confi... |
| V-271844 | | OL 9 local interactive user home directories defined in the /etc/passwd file must exist. | If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working d... |
| V-271845 | | OL 9 system accounts must not have an interactive login shell. | Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts.... |
| V-271846 | | OL 9 local interactive user accounts must be assigned a home directory upon creation. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-271847 | | OL 9 must be configured so that executable search paths within the initialization files of all local interactive users must only contain paths that resolve to the system default or the users home directory. | The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If th... |
| V-271848 | | OL 9 must set the umask value to 077 for all local interactive user accounts. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 or less permissive. Although u... |
| V-271849 | | OL 9 must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-271850 | | OL 9 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. | Increasing the time between a failed authentication attempt and reprompting to enter credentials helps to slow a single-threaded brute force attack.... |
| V-271851 | | OL 9 remote access methods must be monitored. | Logging remote access methods can be used to trace the decrease in the risks associated with remote user access management. It can also be used to spo... |
| V-271852 | | OL 9 must be configured to forward audit records via TCP to a different system or media from the system being audited via rsyslog. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-271853 | | OL 9 must use cron logging. | Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cr... |
| V-271854 | | OL 9 must authenticate the remote logging server for offloading audit logs via rsyslog. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-271855 | | OL 9 must encrypt the transfer of audit records offloaded onto a different system or media from the system being audited via rsyslog. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-271856 | | OL 9 must encrypt via the gtls driver the transfer of audit records offloaded onto a different system or media from the system being audited via rsyslog. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-271857 | | OL 9 must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation. | Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server co... |
| V-271858 | | OL 9 must protect against or limit the effects of denial-of-service (DoS) attacks by ensuring rate-limiting measures on impacted network interfaces are implemented. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-271859 | | OL 9 wireless network adapters must be disabled. | This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with OL 9 systems. Wireless periphe... |
| V-271860 | | OL 9 must configure a DNS processing mode set be Network Manager. | To ensure that DNS resolver settings are respected, a DNS mode in Network Manager must be configured.... |
| V-271861 | | OL 9 systems using Domain Name Servers (DNS) resolution must have at least two name servers configured. | To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the fai... |
| V-271862 | | OL 9 network interfaces must not be in promiscuous mode. | Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access thes... |
| V-271863 | | OL 9 must not have unauthorized IP tunnels configured. | IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the information system security ... |
| V-271864 | | OL 9 must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-271865 | | OL 9 must not forward Internet Protocol version 4 (IPv4) source-routed packets. | Source-routed packets allow the source of the packet to suggest routers forward the packet along a different path than configured on the router, which... |
| V-271866 | | OL 9 must log IPv4 packets with impossible addresses. | The presence of "martian" packets (which have impossible addresses) as well as spoofed packets, source-routed packets, and redirects could be a sign o... |
| V-271867 | | OL 9 must log IPv4 packets with impossible addresses by default. | The presence of "martian" packets (which have impossible addresses) as well as spoofed packets, source-routed packets, and redirects could be a sign o... |
| V-271868 | | OL 9 must use reverse path filtering on all IPv4 interfaces. | Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface on which they were ... |
| V-271869 | | OL 9 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-271870 | | OL 9 must not forward IPv4 source-routed packets by default. | Source-routed packets allow the source of the packet to suggest routers forward the packet along a different path than configured on the router, which... |
| V-271871 | | OL 9 must use a reverse-path filter for IPv4 network traffic, when possible, by default. | Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface on which they were ... |
| V-271872 | | OL 9 must not enable IPv4 packet forwarding unless the system is a router. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this capability is used when no... |
| V-271873 | | OL 9 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address. | Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks.
Ignoring ICMP echo requests (pings... |
| V-271874 | | OL 9 must limit the number of bogus Internet Control Message Protocol (ICMP) response errors logs. | Some routers will send responses to broadcast frames that violate RFC-1122, which fills up a log file system with many useless error messages. An atta... |
| V-271875 | | OL 9 must not send Internet Control Message Protocol (ICMP) redirects. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain inform... |
| V-271876 | | OL 9 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain inform... |
| V-271877 | | OL 9 must not accept router advertisements on all IPv6 interfaces. | An illicit router advertisement message could result in a man-in-the-middle attack.... |
| V-271878 | | OL 9 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages. | An illicit ICMP redirect message could result in a man-in-the-middle attack.... |
| V-271879 | | OL 9 must not forward IPv6 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-271880 | | OL 9 must not enable IPv6 packet forwarding unless the system is a router. | IP forwarding permits the kernel to forward packets from one network interface to another. The ability to forward packets between two networks is only... |
| V-271881 | | OL 9 must not accept router advertisements on all IPv6 interfaces by default. | An illicit router advertisement message could result in a man-in-the-middle attack.... |
| V-271882 | | OL 9 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-271883 | | OL 9 must not forward IPv6 source-routed packets by default. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-271884 | | OL 9 must be configured to use TCP syncookies. | Denial of service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accompl... |
| V-271885 | | OL 9 audit system must protect logon UIDs from unauthorized change. | If modification of login user identifiers (UIDs) is not prevented, they can be changed by nonprivileged users and make auditing complicated or impossi... |
| V-271886 | | OL 9 audit system must protect auditing rules from unauthorized change. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-271901 | | OL 9 must only allow the use of DOD PKI-established certificate authorities for authentication in the establishment of protected sessions to OL 9. | Untrusted certificate authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD syst... |
| V-271432 | | OL 9 must use a separate file system for the system audit data path. | Placing "/var/log/audit" in its own partition enables better separation between audit files and other system files and helps ensure that auditing cann... |
| V-271435 | | OL 9 must use a separate file system for /var. | Ensuring that "/var" is mounted on its own partition enables the setting of more restrictive mount options. This helps protect system services such as... |
| V-271436 | | OL 9 must use a separate file system for /var/log. | Placing "/var/log" in its own partition enables better separation between log files and other files in "/var/".... |
| V-271448 | | OL 9 must disable mounting of cramfs. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-271499 | | OL 9 must be configured so that the file integrity tool verifies Access Control Lists (ACLs). | OL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable... |
| V-271500 | | OL 9 must be configured so that the file integrity tool verifies extended attributes. | OL 9 installation media ships with an optional file integrity tool called Advanced Intrusion Detection Environment (AIDE). AIDE is highly configurable... |
| V-271511 | | OL 9 must enable the hardware random number generator entropy gatherer service. | The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to ... |
| V-271522 | | OL 9 must remove all software components after updated versions have been installed. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by some a... |
| V-271577 | | OL 9 must enable auditing of processes that start prior to the audit daemon. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-271592 | | OL 9 must allocate an audit_backlog_limit of sufficient size to capture processes that start prior to the audit daemon. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-271697 | | OL 9 must disable the chrony daemon from acting as a server. | Minimizing the exposure of the server functionality of the chrony daemon diminishes the attack surface.
Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-0... |
| V-271698 | | OL 9 must disable network management of the chrony daemon. | Not exposing the management interface of the chrony daemon on the network diminishes the attack space.
Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-00... |
| V-271700 | | OL 9 must enable Linux audit logging for the USBGuard daemon. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-271735 | | OL 9 must enable mitigations against processor-based vulnerabilities. | Kernel page-table isolation is a kernel feature that mitigates the Meltdown security vulnerability and hardens the kernel against attempts to bypass k... |
| V-271753 | | OL 9 must limit the number of concurrent sessions to ten for all accounts and/or account types. | Operating system management includes the ability to control the number of users and user sessions that use an operating system. Limiting the number of... |
