Rules In DISA STIG for Oracle Linux 8


Total Missing Implemented Coverage STIG ids missing rule
379 23 356 93.93% OL08-00-020011 OL08-00-020013 OL08-00-020015 OL08-00-020016 OL08-00-020017 OL08-00-020018 OL08-00-020019 OL08-00-020020 OL08-00-020021 OL08-00-020023 OL08-00-020025 OL08-00-020026 OL08-00-020027 OL08-00-020028 OL08-00-020082 OL08-00-020102 OL08-00-020103 OL08-00-020261 OL08-00-020332 OL08-00-040020 OL08-00-040090 OL08-00-040137 OL08-00-040259
V-ID CCI CAT Title SRG Description Check Procedures Fixtext Version Mapped Rule
V-248521 366 high OL 8 must be a vendor-supported release. SRG-OS-ID
An operating system is considered "supported" if the vendor continues to
provide security patches for the product.  With an unsupported release, it
will not be possible to resolve any security issue discovered in the system
software.
The installed operating system must be maintained by a vendor.

Oracle Linux is supported by Oracle Corporation. As the Oracle
Linux vendor, Oracle Corporation is responsible for providing security patches.
OL08-00-010000 installed_OS_is_vendor_supported
V-248522 1233 medium The OL 8 operating system must implement the Endpoint Security for Linux Threat Prevention tool. SRG-OS-ID
Virus scanning software can be used to detect if a system has been compromised by
computer viruses, as well as to limit their spread to other systems.
Install McAfee Endpoint Security for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
presence of viruses on the filesystem.
OL08-00-010001 agent_mfetpd_running
V-248523 366 medium OL 8 vendor-packaged system security patches and updates must be installed and up to date. SRG-OS-ID
Installing software updates is a fundamental mitigation against
the exploitation of publicly-known vulnerabilities. If the most
recent security patches and updates are not installed, unauthorized
users may take advantage of weaknesses in the unpatched software. The
lack of prompt attention to patching could result in a system compromise.
If the system is joined to the ULN
or a yum server, run the following command to install updates:
$ sudo yum update
If the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the ULN and installed using rpm.

NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy dictates.
OL08-00-010010 security_patches_up_to_date
V-248524 3123 high OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the OpenSSH client
violate expectations, and makes system configuration more fragmented. By
specifying a cipher list with the order of ciphers being in a “strongest to
weakest” orientation, the system will automatically attempt to use the
strongest cipher for securing SSH connections.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.

To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/openssh.config contains the following
line and is not commented out:
Ciphers 
OL08-00-010020 harden_sshd_ciphers_openssh_conf_crypto_policy
V-248525 2476 medium All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. SRG-OS-ID
The risk of a system's physical compromise, particularly mobile systems such as
laptops, places its data at risk of compromise.  Encrypting this data mitigates
the risk of its loss if the system is lost.
Oracle Linux 8 natively supports partition encryption through the
Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to
encrypt a partition is during installation time.


For manual installations, select the Encrypt checkbox during partition creation to encrypt the partition. When this option is selected the system will prompt for a passphrase to use in decrypting the partition. The passphrase will subsequently need to be entered manually every time the system boots.

For automated/unattended installations, it is possible to use Kickstart by adding the --encrypted and --passphrase= options to the definition of each partition to be encrypted. For example, the following line would encrypt the root partition:
part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASE
Any PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly. Omitting the --passphrase= option from the partition definition will cause the installer to pause and interactively ask for the passphrase during installation.

By default, the Anaconda installer uses aes-xts-plain64 cipher with a minimum 512 bit key size which should be compatible with FIPS enabled.

Detailed information on encrypting partitions using LUKS or LUKS ciphers can be found on the Oracle Linux 8 Documentation web site:
https://docs.oracle.com/en/operating-systems/oracle-linux/8/install/install-InstallingOracleLinuxManually.html#install-storage-network .
OL08-00-010030 encrypt_partitions
V-248526 1388 medium OL 8 must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via an SSH logon. SRG-OS-ID
The warning message reinforces policy awareness during the logon process and
facilitates possible legal action against attackers. Alternatively, systems
whose ownership should not be obvious should ensure usage of a banner that does
not provide easy attribution.
To enable the warning banner and ensure it is consistent
across the system, add or correct the following line in


/etc/ssh/sshd_config:

Banner /etc/issue
Another section contains information on how to create an appropriate system-wide warning banner.
OL08-00-010040 sshd_enable_warning_banner
V-248527 1388 medium OL 8 must display a banner before granting local or remote access to the system via a graphical user logon. SRG-OS-ID
Display of a standardized and approved use notification before granting access to the operating system
ensures privacy and security notification verbiage used is consistent with applicable federal laws,
Executive Orders, directives, policies, regulations, standards, and guidance.


For U.S. Government systems, system use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist.
In the default graphical environment, displaying a login warning banner
in the GNOME Display Manager's login screen can be enabled on the login
screen by setting banner-message-enable to true.


To enable, add or edit banner-message-enable to /etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/login-screen]
banner-message-enable=true
Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/login-screen/banner-message-enable
After the settings have been set, run dconf update. The banner text must also be set.
OL08-00-010049 dconf_gnome_banner_enabled
V-248528 1388 medium OL 8 must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. SRG-OS-ID
An appropriate warning message reinforces policy awareness during the logon
process and facilitates possible legal action against attackers.
In the default graphical environment, configuring the login warning banner text
in the GNOME Display Manager's login screen can be configured on the login
screen by setting banner-message-text to 'APPROVED_BANNER'
where APPROVED_BANNER is the approved banner for your environment.


To enable, add or edit banner-message-text to /etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/login-screen]
banner-message-text='APPROVED_BANNER'
Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/login-screen/banner-message-text
After the settings have been set, run dconf update. When entering a warning banner that spans several lines, remember to begin and end the string with ' and use \n for new lines.
OL08-00-010050 dconf_gnome_login_banner_text
V-248529 1388 medium OL 8 must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon. SRG-OS-ID
Display of a standardized and approved use notification before granting
access to the operating system ensures privacy and security notification
verbiage used is consistent with applicable federal laws, Executive Orders,
directives, policies, regulations, standards, and guidance.


System use notifications are required only for access via login interfaces with human users and are not required when such human interfaces do not exist.
To configure the system login banner edit /etc/issue. Replace the
default text with a message compliant with the local site policy or a legal
disclaimer.


The DoD required text is either:


You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests -- not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.


OR:

I've read & consent to terms in IS user agreem't.
OL08-00-010060 banner_etc_issue
V-248530 67 medium All OL 8 remote access methods must be monitored. SRG-OS-ID
Logging remote access methods can be used to trace the decrease the risks
associated with remote user access management. It can also be used to spot
cyber attacks and ensure ongoing compliance with organizational policies
surrounding the use of remote access methods.
Logging of remote access methods must be implemented to help identify cyber
attacks and ensure ongoing compliance with remote access policies are being
audited and upheld. An examples of a remote access method is the use of the
Remote Desktop Protocol (RDP) from an external, non-organization controlled
network. The /etc/rsyslog.conf or
/etc/rsyslog.d/*.conf file should contain a match for the following
selectors: auth.*, authpriv.*, and daemon.*. If
not, use the following as an example configuration:
auth.*;authpriv.*;daemon.*                              /var/log/secure
OL08-00-010070 rsyslog_remote_access_monitoring
V-248531 1991 medium OL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. SRG-OS-ID
Without path validation, an informed trust decision by the relying party cannot be made when
presented with any certificate not already explicitly trusted.

A trust anchor is an authoritative entity represented via a public key and associated data. It
is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.

When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor;
it can be, for example, a Certification Authority (CA). A certification path starts with the
subject certificate and proceeds through a number of intermediate certificates up to a trusted
root certificate, typically issued by a trusted CA.

This requirement verifies that a certification path to an accepted trust anchor is used for
certificate validation and that the path includes status information. Path validation is
necessary for a relying party to make an informed trust decision when presented with any
certificate not already explicitly trusted. Status information for certification paths includes
certificate revocation lists or online certificate status protocol responses.
Validation of the certificate status information is out of scope for this requirement.
SSSD must have acceptable trust anchor present.
OL08-00-010090 sssd_has_trust_anchor
V-248532 186 medium OL 8, for certificate-based authentication, must enforce authorized access to the corresponding private key. SRG-OS-ID
If an unauthorized user obtains access to a private key without a passcode, that user would
have unauthorized access to any system where the associated public key has been installed.
Verify the SSH private key files have a passcode.
For each private key stored on the system, use the following command:

$ sudo ssh-keygen -y -f /path/to/file
If the contents of the key are displayed, without asking a passphrase this is a finding.
OL08-00-010100 ssh_private_keys_have_passcode
V-248533 196 medium OL 8 must encrypt all stored passwords with a FIPS 140-2 approved cryptographic hashing algorithm. SRG-OS-ID
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords.
If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords
that are encrypted with a weak algorithm are no more protected than if they are kept in plain text.


Using a stronger hashing algorithm makes password cracking attacks more difficult.
In /etc/login.defs, add or correct the following line to ensure
the system will use SHA-512 as the hashing algorithm:
ENCRYPT_METHOD SHA512
OL08-00-010110 set_password_hashing_algorithm_logindefs
V-248534 196 medium OL 8 must employ FIPS 140-2 approved cryptographic hashing algorithms for all stored passwords. SRG-OS-ID
The system must use a strong hashing algorithm to store the password. The
system must use a sufficient number of hashing rounds to ensure the required
level of entropy.
Verify the operating system requires the shadow password suite
configuration be set to encrypt interactive user passwords using a strong
cryptographic hash.
Check that the interactive user account passwords are using a strong
password hash with the following command:
$ sudo cut -d: -f2 /etc/shadow
$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/
Password hashes ! or * indicate inactive accounts not available for logon and are not evaluated. If any interactive user password hash does not begin with $6, this is a finding.
OL08-00-010120 accounts_password_all_shadowed_sha512
V-252650 366 high The OL 8 operating system must not have accounts configured with blank or null passwords. SRG-OS-ID
If an account has an empty password, anyone could log in and
run commands with the privileges of that account. Accounts with
empty passwords should never be used in operational environments.
Check the "/etc/shadow" file for blank passwords with the
following command:
$ sudo awk -F: '!$2 {print $1}' /etc/shadow
If the command returns any results, this is a finding. Configure all accounts on the system to have a password or lock the account with the following commands: Perform a password reset:
$ sudo passwd [username]
Lock an account:
$ sudo passwd -l [username]
OL08-00-010121 no_empty_passwords_etc_shadow
V-248535 196 medium The OL 8 shadow password suite must be configured to use a sufficient number of hashing rounds. SRG-OS-ID
Using a higher number of rounds makes password cracking attacks more difficult.
Configure the number or rounds for the password hashing algorithm. This can be
accomplished by using the rounds option for the pam_unix PAM module.


In file /etc/pam.d/system-auth append rounds= to the pam_unix.so entry, as shown below:
password sufficient pam_unix.so ...existing_options... rounds=
The system's default number of rounds is 5000.
OL08-00-010130 accounts_password_pam_unix_rounds_system_auth
V-248537 213 high OL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user mode and maintenance. SRG-OS-ID
Password protection on the boot loader configuration ensures
users with physical access cannot trivially alter
important bootloader settings. These include which kernel to use,
and whether to enter single-user mode.
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.


Since plaintext passwords are a security risk, generate a hash for the password by running the following command:
# grub2-setpassword
When prompted, enter the password that was selected.

OL08-00-010140 grub2_uefi_password
V-248538 213 medium OL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must have a unique name for the grub superusers account when booting into single-user mode and maintenance. SRG-OS-ID
Having a non-default grub superuser username makes password-guessing attacks less effective.
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.


To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change.

It is highly suggested not to use common administrator account names like root, admin, or administrator for the grub2 superuser account.

Change the superuser to a different username (The default is 'root').
$ sed -i 's/\(set superusers=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users


Once the superuser account has been added, update the grub.cfg file by running:
grubby --update-kernel=ALL --env=/boot/grub2/grubenv
OL08-00-010141 grub2_uefi_admin_username
V-248539 213 medium OL 8 operating systems booted with a BIOS must have a unique name for the grub superusers account when booting into single-user and maintenance modes. SRG-OS-ID
Having a non-default grub superuser username makes password-guessing attacks less effective.
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.


To maximize the protection, select a password-protected superuser account with unique name, and modify the /etc/grub.d/01_users configuration file to reflect the account name change.

Do not to use common administrator account names like root, admin, or administrator for the grub2 superuser account.

Change the superuser to a different username (The default is 'root').
$ sed -i 's/\(set superuser=\).*/\1"<unique user ID>"/g' /etc/grub.d/01_users


Once the superuser account has been added, update the grub.cfg file by running:
grubby --update-kernel=ALL --env=/boot/grub2/grubenv
OL08-00-010149 grub2_admin_username
V-248540 213 high OL 8 operating systems booted with a BIOS must require authentication upon booting into single-user and maintenance modes. SRG-OS-ID
Password protection on the boot loader configuration ensures
users with physical access cannot trivially alter
important bootloader settings. These include which kernel to use,
and whether to enter single-user mode.
The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.


Since plaintext passwords are a security risk, generate a hash for the password by running the following command:
# grub2-setpassword
When prompted, enter the password that was selected.

OL08-00-010150 grub2_password
V-248541 213 medium OL 8 operating systems must require authentication upon booting into rescue mode. SRG-OS-ID
This prevents attackers with physical access from trivially bypassing security
on the machine and gaining root access. Such accesses are further prevented
by configuring the bootloader password.
Single-user mode is intended as a system recovery
method, providing a single user root access to the system by
providing a boot option at startup. By default, no authentication
is performed if single-user mode is selected.


By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service.
OL08-00-010151 require_singleuser_auth
V-248542 213 medium OL 8 operating systems must require authentication upon booting into emergency mode. SRG-OS-ID
This prevents attackers with physical access from trivially bypassing security
on the machine and gaining root access. Such accesses are further prevented
by configuring the bootloader password.
Emergency mode is intended as a system recovery
method, providing a single user root access to the system
during a failed boot sequence.


By default, Emergency mode is protected by requiring a password and is set in /usr/lib/systemd/system/emergency.service.
OL08-00-010152 require_emergency_target_auth
V-248543 803 medium The OL 8 "pam_unix.so" module must be configured in the system-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. SRG-OS-ID
Passwords need to be protected at all times, and encryption is the standard
method for protecting passwords. If passwords are not encrypted, they can
be plainly read (i.e., clear text) and easily compromised. Passwords that
are encrypted with a weak algorithm are no more protected than if they are
kepy in plain text.


This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style configuration option ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult.
The PAM system service can be configured to only store encrypted
representations of passwords. In "/etc/pam.d/system-auth", the
password section of the file controls which PAM modules execute
during a password change. Set the pam_unix.so module in the
password section to include the argument sha512, as shown
below:

password    sufficient    pam_unix.so sha512 other arguments...

This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default.
OL08-00-010159 set_password_hashing_algorithm_systemauth
V-248544 803 medium The OL 8 "pam_unix.so" module must be configured in the password-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. SRG-OS-ID
Passwords need to be protected at all times, and encryption is the standard
method for protecting passwords. If passwords are not encrypted, they can
be plainly read (i.e., clear text) and easily compromised. Passwords that
are encrypted with a weak algorithm are no more protected than if they are
kepy in plain text.


This setting ensures user and group account administration utilities are configured to store only encrypted representations of passwords. Additionally, the crypt_style configuration option ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult.
The PAM system service can be configured to only store encrypted
representations of passwords. In
/etc/pam.d/password-auth,
the
password section of the file controls which PAM modules execute
during a password change. Set the pam_unix.so module in the
password section to include the argument sha512, as shown
below:

password    sufficient    pam_unix.so sha512 other arguments...

This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default.
OL08-00-010160 set_password_hashing_algorithm_passwordauth
V-248545 803 medium OL 8 must prevent system daemons from using Kerberos for authentication. SRG-OS-ID
The key derivation function (KDF) in Kerberos is not FIPS compatible.
Kerberos is not an approved key distribution method for
Common Criteria. To prevent using Kerberos by system daemons,
remove the Kerberos keytab files, especially
/etc/krb5.keytab.
OL08-00-010161 kerberos_disable_no_keytab
V-248546 803 medium The krb5-workstation package must not be installed on OL 8. SRG-OS-ID
Kerberos is a network authentication system. The krb5-workstation package contains the basic
Kerberos programs (kinit, klist, kdestroy, kpasswd).
The krb5-workstation package can be removed with the following command:
$ sudo yum erase krb5-workstation
OL08-00-010162 package_krb5-workstation_removed
V-248547 803 medium The krb5-server package must not be installed on OL 8. SRG-OS-ID
Unnecessary packages should not be installed to decrease the attack
surface of the system.  While this software is clearly essential on an KDC
server, it is not necessary on typical desktop or workstation systems.
The krb5-server package should be removed if not in use.
Is this system the Kerberos server? If not, remove the package.
The krb5-server package can be removed with the following command:
$ sudo yum erase krb5-server
The krb5-server RPM is not installed by default on a Oracle Linux 8 system. It is needed only by the Kerberos servers, not by the clients which use Kerberos for authentication. If the system is not intended for use as a Kerberos Server it should be removed.
OL08-00-010163 package_krb5-server_removed
V-248548 1084 medium OL 8 must use a Linux Security Module configured to enforce limits on system services. SRG-OS-ID
Setting the SELinux state to enforcing ensures SELinux is able to confine
potentially compromised processes to the security policy, which is designed to
prevent them from causing damage to the system or further elevating their
privileges.
The SELinux state should be set to  at
system boot time.  In the file /etc/selinux/config, add or correct the
following line to configure the system to boot into enforcing mode:
SELINUX=
OL08-00-010170 selinux_state
V-248549 1084 low OL 8 must have the "policycoreutils" package installed. SRG-OS-ID
Security-enhanced Linux is a feature of the Linux kernel and a number of utilities
with enhanced security functionality designed to add mandatory access controls to Linux.
The Security-enhanced Linux kernel contains new architectural components originally
developed to improve security of the Flask operating system. These architectural components
provide general support for the enforcement of many kinds of mandatory access control
policies, including those based on the concepts of Type Enforcement, Role-based Access
Control, and Multi-level Security.

policycoreutils contains the policy core utilities that are required for
basic operation of an SELinux-enabled system. These utilities include load_policy
to load SELinux policies, setfiles to label filesystems, newrole to
switch roles, and so on.
The policycoreutils package can be installed with the following command:
$ sudo yum install policycoreutils
OL08-00-010171 package_policycoreutils_installed
V-248551 1090 medium A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. SRG-OS-ID
Failing to set the sticky bit on public directories allows unauthorized
users to delete files in the directory structure.


The only authorized public directories are those temporary directories supplied with the system, or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system, by users for temporary file storage (such as /tmp), and for directories requiring global read/write access.
When the so-called 'sticky bit' is set on a directory,
only the owner of a given file may remove that file from the
directory. Without the sticky bit, any user with write access to a
directory may remove any file in the directory. Setting the sticky
bit prevents users from removing each other's files. In cases where
there is no reason for a directory to be world-writable, a better
solution is to remove that permission rather than to set the sticky
bit. However, if a directory is used by a particular application,
consult that application's documentation instead of blindly
changing modes.

To set the sticky bit on a world-writable directory DIR, run the following command:
$ sudo chmod +t DIR
OL08-00-010190 dir_perms_world_writable_sticky_bits
V-248552 2361 medium OL 8 must be configured so that all network connections associated with SSH traffic are terminate after a period of inactivity. SRG-OS-ID
This ensures a user login will be terminated as soon as the ClientAliveInterval
is reached.
The SSH server sends at most ClientAliveCountMax messages
during a SSH session and waits for a response from the SSH client.
The option ClientAliveInterval configures timeout after
each ClientAliveCountMax message. If the SSH server does not
receive a response from the client, then the connection is considered idle
and terminated.

To ensure the SSH idle timeout occurs precisely when the
ClientAliveInterval is set, set the ClientAliveCountMax to
value of 0 in


/etc/ssh/sshd_config:
OL08-00-010200 sshd_set_keepalive_0
V-248553 2361 medium OL 8 must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity. SRG-OS-ID
Terminating an idle ssh session within a short time period reduces the window of
opportunity for unauthorized personnel to take control of a management session
enabled on the console or console port that has been let unattended.
SSH allows administrators to set an idle timeout interval. After this interval
has passed, the idle user will be automatically logged out.


To set an idle timeout interval, edit the following line in /etc/ssh/sshd_config as follows:
ClientAliveInterval 


The timeout interval is given in seconds. For example, have a timeout of 10 minutes, set interval to 600.

If a shorter timeout has already been set for the login shell, that value will preempt any SSH setting made in /etc/ssh/sshd_config. Keep in mind that some processes may stop SSH from correctly detecting that the user is idle.
OL08-00-010201 sshd_set_idle_timeout
V-248554 1314 medium The OL 8 "/var/log/messages" file must have mode 0640 or less permissive. SRG-OS-ID
The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel.
To properly set the permissions of /var/log/messages, run the command:
$ sudo chmod 0640 /var/log/messages
OL08-00-010210 file_permissions_var_log_messages
V-248555 1314 medium The OL 8 "/var/log/messages" file must be owned by root. SRG-OS-ID
The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel.
 To properly set the owner of /var/log/messages, run the command: 
$ sudo chown root /var/log/messages 
OL08-00-010220 file_owner_var_log_messages
V-248556 1314 medium The OL 8 "/var/log/messages" file must be group-owned by root. SRG-OS-ID
The /var/log/messages file contains logs of error messages in
the system and should only be accessed by authorized personnel.
 To properly set the group owner of /var/log/messages, run the command: 
$ sudo chgrp root /var/log/messages
OL08-00-010230 file_groupowner_var_log_messages
V-248557 1314 medium The OL 8 "/var/log" directory must have mode 0755 or less permissive. SRG-OS-ID
The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel.
To properly set the permissions of /var/log, run the command:
$ sudo chmod 0755 /var/log
OL08-00-010240 file_permissions_var_log
V-248558 1314 medium The OL 8 "/var/log" directory must be owned by root. SRG-OS-ID
The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel.
 To properly set the owner of /var/log, run the command: 
$ sudo chown root /var/log 
OL08-00-010250 file_owner_var_log
V-248559 1314 medium The OL 8 "/var/log" directory must be group-owned by root. SRG-OS-ID
The /var/log directory contains files with logs of error
messages in the system and should only be accessed by authorized
personnel.
 To properly set the group owner of /var/log, run the command: 
$ sudo chgrp root /var/log
OL08-00-010260 file_groupowner_var_log
V-248560 1453 medium The OL 8 SSH daemon must be configured to use system-wide crypto policies. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the SSH service violate expectations,
and makes system configuration more fragmented.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
SSH is supported by crypto policy, but the SSH configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, ensure that
the CRYPTO_POLICY variable is either commented or not set at all
in the /etc/sysconfig/sshd.
OL08-00-010287 configure_ssh_crypto_policy
V-248561 877 medium The OL 8 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-2 validated cryptographic hash algorithms. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the OpenSSH
server violate expectations, and makes system configuration more
fragmented.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.

To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oMACS=hmac-sha2-512,hmac-sha2-256
OL08-00-010290 harden_sshd_macs_opensshserver_conf_crypto_policy
V-248562 877 medium The OL 8 SSH server must be configured to use only ciphers employing FIPS 140-2 validated cryptographic algorithms. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the OpenSSH server
violate expectations, and makes system configuration more fragmented. By
specifying a cipher list with the order of ciphers being in a “strongest to
weakest” orientation, the system will automatically attempt to use the
strongest cipher for securing SSH connections.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSH is supported by system crypto policy, but the OpenSSH configuration may be
set up incorrectly.

To check that Crypto Policies settings for ciphers are configured correctly, ensure that
/etc/crypto-policies/back-ends/opensshserver.config contains the following
text and is not commented out:
-oCiphers=
OL08-00-010291 harden_sshd_ciphers_opensshserver_conf_crypto_policy
V-248563 366 low The OL 8 SSH server must be configured to use strong entropy. SRG-OS-ID
SSH implementation in Oracle Linux 8 uses the openssl library, which doesn't use
high-entropy sources by default. Randomness is needed to generate data-encryption keys, and as
plaintext padding and initialization vectors in encryption algorithms, and high-quality
entropy elliminates the possibility that the output of the random number generator used by SSH
would be known to potential attackers.
To set up SSH server to use entropy from a high-quality source, edit the /etc/sysconfig/sshd file.
The SSH_USE_STRONG_RNG configuration value determines how many bytes of entropy to use, so
make sure that the file contains line
SSH_USE_STRONG_RNG=32
OL08-00-010292 sshd_use_strong_rng
V-248564 1453 medium The OL 8 operating system must implement DoD-approved encryption in the OpenSSL package. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the Java runtime violates expectations,
and makes system configuration more fragmented.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
OpenSSL is supported by crypto policy, but the OpenSSL configuration may be
set up to ignore it.
To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
available under /etc/pki/tls/openssl.cnf.
This file has the ini format, and it enables crypto policy support
if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive.
OL08-00-010293 configure_openssl_crypto_policy
V-248565 1453 medium The OL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package. SRG-OS-ID
Without cryptographic integrity protections, information can be altered by
unauthorized users without detection.
Crypto Policies are means of enforcing certain cryptographic settings for
selected applications including OpenSSL. OpenSSL is by default configured to
modify its configuration based on currently configured Crypto Policy.
Editing the Crypto Policy back-end is not recommended.

Check the crypto-policies(7) man page and choose a policy that configures TLS
protocol to version 1.2 or higher, for example DEFAULT, FUTURE or FIPS policy.
Or create and apply a custom policy that restricts minimum TLS version to 1.2.

For example for versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch
this is expected:

$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config

MinProtocol = TLSv1.2
Or for version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer this is expected:
$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config

TLS.MinProtocol = TLSv1.2
DTLS.MinProtocol = DTLSv1.2
OL08-00-010294 configure_openssl_tls_crypto_policy
V-248566 1453 medium The OL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package. SRG-OS-ID
Overriding the system crypto policy makes the behavior of the GnuTLS
library violate expectations, and makes system configuration more
fragmented.
Crypto Policies provide a centralized control over crypto algorithms usage of many packages.
GnuTLS is supported by system crypto policy, but the GnuTLS configuration may be
set up to ignore it.

To check that Crypto Policies settings are configured correctly, ensure that
/etc/crypto-policies/back-ends/gnutls.config contains the following
line and is not commented out:
+VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0
OL08-00-010295 configure_gnutls_tls_crypto_policy
V-248567 1499 medium OL 8 system commands must have mode 755 or less permissive. SRG-OS-ID
System binaries are executed by privileged users, as well as system services,
and restrictive permissions are necessary to ensure execution of these programs
cannot be co-opted.
System executables are stored in the following directories by default:
/bin
/sbin
/usr/bin
/usr/libexec
/usr/local/bin
/usr/local/sbin
/usr/sbin
All files in these directories should not be group-writable or world-writable. If any file FILE in these directories is found to be group-writable or world-writable, correct its permission with the following command:
$ sudo chmod go-w FILE
OL08-00-010300 file_permissions_binary_dirs
V-248568 1499 medium OL 8 system commands must be owned by root. SRG-OS-ID
System binaries are executed by privileged users as well as system services,
and restrictive permissions are necessary to ensure that their
execution of these programs cannot be co-opted.
System executables are stored in the following directories by default:
/bin
/sbin
/usr/bin
/usr/libexec
/usr/local/bin
/usr/local/sbin
/usr/sbin
All files in these directories should be owned by the root user. If any file FILE in these directories is found to be owned by a user other than root, correct its ownership with the following command:
$ sudo chown root FILE
OL08-00-010310 file_ownership_binary_dirs
V-248569 1499 medium OL 8 system commands must be group-owned by root or a system account. SRG-OS-ID
If the operating system allows any user to make changes to software
libraries, then those changes might be implemented without undergoing the
appropriate testing and approvals that are part of a robust change management
process.
This requirement applies to operating systems with software libraries
that are accessible and configurable, as in the case of interpreted languages.
Software libraries also include privileged programs which execute with
escalated privileges. Only qualified and authorized individuals must be
allowed to obtain access to information system components for purposes
of initiating changes, including upgrades and modifications.
System commands files are stored in the following directories by default:
/bin
/sbin
/usr/bin
/usr/sbin
/usr/local/bin
/usr/local/sbin
All files in these directories should be owned by the root group, or a system account. If the directory, or any file in these directories, is found to be owned by a group other than root or a a system account correct its ownership with the following command:
$ sudo chgrp root FILE
OL08-00-010320 file_groupownership_system_commands_dirs
V-248570 1499 medium OL 8 library files must have mode 755 or less permissive. SRG-OS-ID
Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Restrictive permissions are necessary to protect the integrity of the system.
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules. All files in these directories should not be group-writable or world-writable. If any file in these directories is found to be group-writable or world-writable, correct its permission with the following command:
$ sudo chmod go-w FILE
OL08-00-010330 file_permissions_library_dirs
V-252651 1499 medium OL 8 library directories must have mode 755 or less permissive. SRG-OS-ID
If the operating system were to allow any user to make changes to software libraries,
then those changes might be implemented without undergoing the appropriate testing
and approvals that are part of a robust change management process.

This requirement applies to operating systems with software libraries that are accessible
and configurable, as in the case of interpreted languages. Software libraries also include
privileged programs which execute with escalated privileges. Only qualified and authorized
individuals must be allowed to obtain access to information system components for purposes
of initiating changes, including upgrades and modifications.
System-wide shared library directories, which contain are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules. All sub-directories in these directories should not be group-writable or world-writable. If any file in these directories is found to be group-writable or world-writable, correct its permission with the following command:
$ sudo chmod go-w DIR
OL08-00-010331 dir_permissions_library_dirs
V-248571 1499 medium OL 8 library files must be owned by root. SRG-OS-ID
Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership is necessary to protect the integrity of the system.
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be owned by the root user. If the directory, or any file in these directories, is found to be owned by a user other than root correct its ownership with the following command:
$ sudo chown root FILE
OL08-00-010340 file_ownership_library_dirs
V-252652 1499 medium OL 8 library directories must be owned by root. SRG-OS-ID
Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership of library directories is necessary to protect
the integrity of the system.
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be owned by the root user. If the directories, is found to be owned by a user other than root correct its ownership with the following command:
$ sudo chown root DIR
OL08-00-010341 dir_ownership_library_dirs
V-248572 1499 medium OL 8 library files must be group-owned by root. SRG-OS-ID
If the operating system were to allow any user to make changes to software libraries,
then those changes might be implemented without undergoing the appropriate testing and
approvals that are part of a robust change management process.

This requirement applies to operating systems with software libraries that are
accessible and configurable, as in the case of interpreted languages. Software libraries
also include privileged programs which execute with escalated privileges. Only qualified
and authorized individuals must be allowed to obtain access to information system components
for purposes of initiating changes, including upgrades and modifications.
System-wide library files are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
All system-wide shared library files should be protected from unauthorised access. If any of these files is not group-owned by root, correct its group-owner with the following command:
$ sudo chgrp root FILE
OL08-00-010350 root_permissions_syslibrary_files
V-252653 1499 medium OL 8 library directories must be group-owned by root or a system account. SRG-OS-ID
Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership of library directories is necessary to protect
the integrity of the system.
System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
/lib
/lib64
/usr/lib
/usr/lib64
Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be group-owned by the root user. If the directories, is found to be owned by a user other than root correct its ownership with the following command:
$ sudo chgrp root DIR
OL08-00-010351 dir_group_ownership_library_dirs
V-252654 2696 medium The OL 8 operating system must use a file integrity tool to verify correct operation of all security functions. SRG-OS-ID
The AIDE package must be installed if it is to be available for integrity checking.
The aide package can be installed with the following command:
$ sudo yum install aide
OL08-00-010359 package_aide_installed
V-248573 2702 medium The OL 8 file integrity tool must notify the System Administrator (SA) when changes to the baseline configuration or anomalies in the operation of any security functions are discovered within an organizationally defined frequency. SRG-OS-ID
Unauthorized changes to the baseline configuration could make the system vulnerable
to various attacks or allow unauthorized access to the operating system. Changes to
operating system configurations can have unintended side effects, some of which may
be relevant to security.


Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.
AIDE should notify appropriate personnel of the details of a scan after the scan has been run.
If AIDE has already been configured for periodic execution in /etc/crontab, append the
following line to the existing AIDE line:
 | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost
Otherwise, add the following line to /etc/crontab:
05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost
AIDE can be executed periodically through other means; this is merely one example.
OL08-00-010360 aide_scan_notification
V-248574 1749 high YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. SRG-OS-ID
Verifying the authenticity of the software prior to installation validates
the integrity of the patch or upgrade received from a vendor. This ensures
the software has not been tampered with and that it has been provided by a
trusted vendor. Self-signed certificates are disallowed by this
requirement. Certificates used to verify the software must be from an
approved Certificate Authority (CA)."
To ensure signature checking is not disabled for
any repos, remove any lines from files in /etc/yum.repos.d of the form:
gpgcheck=0
OL08-00-010370 ensure_gpgcheck_never_disabled
V-248575 1749 high OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. SRG-OS-ID
Changes to any software components can have significant effects to the overall security
of the operating system. This requirement ensures the software has not been tampered and
has been provided by a trusted vendor.


Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
yum should be configured to verify the signature(s) of local packages
prior to installation. To configure yum to verify signatures of local
packages, set the localpkg_gpgcheck to 1 in /etc/yum.conf.
OL08-00-010371 ensure_gpgcheck_local_packages
V-248576 1749 medium OL 8 must prevent the loading of a new kernel for later execution. SRG-OS-ID
Disabling kexec_load allows greater control of the kernel memory.
It makes it impossible to load another kernel image after it has been disabled.
To set the runtime status of the kernel.kexec_load_disabled kernel parameter, run the following command: 
$ sudo sysctl -w kernel.kexec_load_disabled=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.kexec_load_disabled = 1
OL08-00-010372 sysctl_kernel_kexec_load_disabled
V-248577 2165 medium OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. SRG-OS-ID
By enabling this kernel parameter, symbolic links are permitted to be followed
only when outside a sticky world-writable directory, or when the UID of the
link and follower match, or when the directory owner matches the symlink's owner.
Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system
accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of
open() or creat().
To set the runtime status of the fs.protected_symlinks kernel parameter, run the following command: 
$ sudo sysctl -w fs.protected_symlinks=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
fs.protected_symlinks = 1
OL08-00-010373 sysctl_fs_protected_symlinks
V-248578 2165 medium OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on hardlinks. SRG-OS-ID
By enabling this kernel parameter, users can no longer create soft or hard links to
files which they do not own. Disallowing such hardlinks mitigate vulnerabilities
based on insecure file system accessed by privileged programs, avoiding an
exploitation vector exploiting unsafe use of open() or creat().
To set the runtime status of the fs.protected_hardlinks kernel parameter, run the following command: 
$ sudo sysctl -w fs.protected_hardlinks=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
fs.protected_hardlinks = 1
OL08-00-010374 sysctl_fs_protected_hardlinks
V-248579 1090 low OL 8 must restrict access to the kernel message buffer. SRG-OS-ID
Unprivileged access to the kernel syslog can expose sensitive kernel
address information.
To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command: 
$ sudo sysctl -w kernel.dmesg_restrict=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.dmesg_restrict = 1
OL08-00-010375 sysctl_kernel_dmesg_restrict
V-248580 1090 low OL 8 must prevent kernel profiling by unprivileged users. SRG-OS-ID
Kernel profiling can reveal sensitive information about kernel behaviour.
To set the runtime status of the kernel.perf_event_paranoid kernel parameter, run the following command: 
$ sudo sysctl -w kernel.perf_event_paranoid=2
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.perf_event_paranoid = 2
OL08-00-010376 sysctl_kernel_perf_event_paranoid
V-252655 366 medium OL 8 must specify the default "include" directory for the /etc/sudoers file. SRG-OS-ID
Some sudo configurtion options allow users to run programs without re-authenticating.
Use of these configuration options makes it easier for one compromised accound to be used to
compromise other accounts.
Administrators can configure authorized sudo users via drop-in files, and it is possible to include
other directories and configuration files from the file currently being parsed.

Make sure that /etc/sudoers only includes drop-in configuration files from /etc/sudoers.d.
The /etc/sudoers should contain only one #includedir directive pointing to
/etc/sudoers.d, and no file in /etc/sudoers.d/ should include other files or directories.
Note that the '#' character doesn't denote a comment in the configuration file.
OL08-00-010379 sudoers_default_includedir
V-248581 2038 medium OL 8 must require users to provide a password for privilege escalation. SRG-OS-ID
Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.


When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate.
The sudo NOPASSWD tag, when specified, allows a user to execute
commands using sudo without having to authenticate. This should be disabled
by making sure that the NOPASSWD tag does not exist in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/.
OL08-00-010380 sudo_remove_nopasswd
V-248582 2038 medium OL 8 must require users to reauthenticate for privilege escalation and changing roles. SRG-OS-ID
Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.


When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate.
The sudo !authenticate option, when specified, allows a user to execute commands using
sudo without having to authenticate. This should be disabled by making sure that the
!authenticate option does not exist in /etc/sudoers configuration file or
any sudo configuration snippets in /etc/sudoers.d/.
OL08-00-010381 sudo_remove_no_authenticate
V-248583 366 medium OL 8 must restrict privilege elevation to authorized personnel. SRG-OS-ID
If the "sudoers" file is not configured correctly, any user defined
on the system can initiate privileged actions on the target system.
The sudo command allows a user to execute programs with elevated
(administrator) privileges. It prompts the user for their password
and confirms your request to execute a command by checking a file,
called sudoers.
Restrict privileged actions by removing the following entries from the sudoers file:
ALL ALL=(ALL) ALL
ALL ALL=(ALL:ALL) ALL
OL08-00-010382 sudo_restrict_privilege_elevation_to_authorized
V-248584 366 medium OL 8 must use the invoking user's password for privilege escalation when using "sudo". SRG-OS-ID
If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt
the invoking user for the "root" user password.
The sudoers security policy requires that users authenticate themselves before they can use sudo.
When sudoers requires authentication, it validates the invoking user's credentials.
The expected output for:
sudo egrep -i '(!rootpw|!targetpw|!runaspw)' /etc/sudoers /etc/sudoers.d/* | grep -v '#'
 /etc/sudoers:Defaults !targetpw
      /etc/sudoers:Defaults !rootpw
      /etc/sudoers:Defaults !runaspw 
OL08-00-010383 sudoers_validate_passwd
V-248585 2038 medium OL 8 must require re-authentication when using the "sudo" command. SRG-OS-ID
Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.


When operating systems provide the capability to escalate a functional capability, it is critical that the user re-authenticate.
The sudo timestamp_timeout tag sets the amount of time sudo password prompt waits.
The default timestamp_timeout value is 5 minutes.
The timestamp_timeout should be configured by making sure that the
timestamp_timeout tag exists in
/etc/sudoers configuration file or any sudo configuration snippets
in /etc/sudoers.d/.
If the value is set to an integer less than 0, the user's time stamp will not expire 
and the user will not have to re-authenticate for privileged actions until the user's session is terminated.
OL08-00-010384 sudo_require_reauthentication
V-252656 2038 medium The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. SRG-OS-ID
Without re-authentication, users may access resources or perform tasks for which they do not
have authorization. When operating systems provide the capability to escalate a functional
capability, it is critical the user re-authenticate.
Verify the operating system is not configured to bypass password requirements for privilege
escalation. Check the configuration of the "/etc/pam.d/sudo" file with the following command:
$ sudo grep pam_succeed_if /etc/pam.d/sudo
If any occurrences of "pam_succeed_if" is returned from the command, this is a finding.
OL08-00-010385 disallow_bypass_password_sudo
V-248586 1948 low OL 8 must have the package required for multifactor authentication installed. SRG-OS-ID
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
compromised, that compromise will not affect credentials stored on the
authentication device.


Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
Configure the operating system to implement multifactor authentication by
installing the required package with the following command:

The openssl-pkcs11 package can be installed with the following command:
$ sudo yum install openssl-pkcs11
OL08-00-010390 install_smartcard_packages
V-248587 1954 medium OL 8 must implement certificate status checking for multifactor authentication. SRG-OS-ID
Ensuring that multifactor solutions certificates are checked via Online Certificate Status Protocol (OCSP)
ensures the security of the system.
Multifactor solutions that require devices separate from information systems gaining access include,
for example, hardware tokens providing time-based or challenge-response authenticators and smart cards.
Configuring certificate_verification to ocsp_dgst= ensures that certificates for
multifactor solutions are checked via Online Certificate Status Protocol (OCSP).
OL08-00-010400 sssd_certificate_verification
V-248588 1953 medium OL 8 must accept Personal Identity Verification (PIV) credentials. SRG-OS-ID
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
compromised, that compromise will not affect credentials stored on the
authentication device.


Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
The opensc package can be installed with the following command:
$ sudo yum install opensc
OL08-00-010410 package_opensc_installed
V-248589 2824 medium OL 8 must implement non-executable data to protect its memory from unauthorized code execution. SRG-OS-ID
Computers with the ability to prevent this type of code execution frequently put an option in the BIOS that will
allow users to turn the feature on or off at will.
Reboot the system and enter the BIOS or Setup configuration menu.
Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
on AMD-based systems.
OL08-00-010420 bios_enable_execution_restrictions
V-248590 1084 medium OL 8 must clear the page allocator to prevent use-after-free attacks. SRG-OS-ID
Poisoning writes an arbitrary value to freed pages, so any modification or
reference to that page after being freed or before being initialized will be
detected and prevented.
This prevents many types of use-after-free vulnerabilities at little performance cost.
Also prevents leak of data and detection of corrupted memory.
To enable poisoning of free pages,
add the argument page_poison=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that page_poison=1 is added as a kernel command line
argument to newly installed kernels, add page_poison=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... page_poison=1 ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="page_poison=1"
OL08-00-010421 grub2_page_poison_argument
V-248591 1084 medium OL 8 must disable virtual syscalls. SRG-OS-ID
Virtual Syscalls provide an opportunity of attack for a user who has control
of the return instruction pointer.
To disable use of virtual syscalls,
add the argument vsyscall=none to the default
GRUB 2 command line for the Linux operating system.
To ensure that vsyscall=none is added as a kernel command line
argument to newly installed kernels, add vsyscall=none to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... vsyscall=none ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="vsyscall=none"
OL08-00-010422 grub2_vsyscall_argument
V-248592 1084 medium OL 8 must clear SLUB/SLAB objects to prevent use-after-free attacks. SRG-OS-ID
Poisoning writes an arbitrary value to freed objects, so any modification or
reference to that object after being freed or before being initialized will be
detected and prevented.
This prevents many types of use-after-free vulnerabilities at little performance cost.
Also prevents leak of data and detection of corrupted memory.
To enable poisoning of SLUB/SLAB objects,
add the argument slub_debug=P to the default
GRUB 2 command line for the Linux operating system.
To ensure that slub_debug=P is added as a kernel command line
argument to newly installed kernels, add slub_debug=P to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... slub_debug=P ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="slub_debug=P"
OL08-00-010423 grub2_slub_debug_argument
V-248593 366 medium OL 8 must not let Meltdown and Spectre exploit critical vulnerabilities in modern processors. SRG-OS-ID
Hardware vulnerabilities allow programs to steal data that is currently processed on the
computer. While programs are typically not permitted to read data from other programs, a
malicious program can exploit Meltdown and Spectre to obtain secrets stored in the memory of
other running programs. This might include passwords stored in a password manager or browser;
personal photos, emails, and instant messages; and business-critical documents.
Determine the default kernel:
$ sudo grubby --default-kernel

/boot/vmlinuz-5.4.17-2011.1.2.el8uek.x86_64
Using the default kernel, verify that Meltdown mitigations are not disabled:
$ sudo grubby --info=path-to-default-kernel | grep mitigation
The mitigation must be set to "on".
OL08-00-010424 grub2_mitigation_argument
V-248594 2824 medium OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. SRG-OS-ID
Address space layout randomization (ASLR) makes it more difficult for an
attacker to predict the location of attack code they have introduced into a
process's address space during an attempt at exploitation. Additionally,
ASLR makes it more difficult for an attacker to know the location of
existing code in order to re-purpose it using return oriented programming
(ROP) techniques.
To set the runtime status of the kernel.randomize_va_space kernel parameter, run the following command: 
$ sudo sysctl -w kernel.randomize_va_space=2
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.randomize_va_space = 2
OL08-00-010430 sysctl_kernel_randomize_va_space
V-248595 2617 low YUM must remove all software components after updated versions have been installed on OL 8. SRG-OS-ID
Previous versions of software components that are not removed from the information
system after updates have been installed may be exploited by some adversaries.
yum should be configured to remove previous software components after
new versions have been installed. To configure yum to remove the

previous software components after updating, set the clean_requirements_on_remove


to 1 in /etc/yum.conf.
OL08-00-010440 clean_components_post_updating
V-248596 2696 medium OL 8 must enable the SELinux targeted policy. SRG-OS-ID
Setting the SELinux policy to targeted or a more specialized policy
ensures the system will confine processes that are likely to be
targeted for exploitation, such as network or system services.


Note: During the development or debugging of SELinux modules, it is common to temporarily place non-production systems in permissive mode. In such temporary cases, SELinux policies should be developed, and once work is completed, the system should be reconfigured to .
The SELinux targeted policy is appropriate for
general-purpose desktops and servers, as well as systems in many other roles.
To configure the system to use this policy, add or correct the following line
in /etc/selinux/config:
SELINUXTYPE=
Other policies, such as mls, provide additional security labeling and greater confinement but are not compatible with many general-purpose use cases.
OL08-00-010450 selinux_policytype
V-248597 366 high There must be no "shosts.equiv" files on the OL 8 operating system. SRG-OS-ID
The shosts.equiv files are used to configure host-based authentication for the
system via SSH. Host-based authentication is not sufficient for preventing
unauthorized access to the system, as it does not require interactive
identification and authentication of a connection request, or for the use of
two-factor authentication.
The shosts.equiv file list remote hosts
and users that are trusted by the local system.
To remove these files, run the following command to delete them from any
location:
$ sudo rm /[path]/[to]/[file]/shosts.equiv
OL08-00-010460 no_host_based_files
V-248598 366 high There must be no ".shosts" files on the OL 8 operating system. SRG-OS-ID
The .shosts files are used to configure host-based authentication for
individual users or the system via SSH. Host-based authentication is not
sufficient for preventing unauthorized access to the system, as it does not
require interactive identification and authentication of a connection request,
or for the use of two-factor authentication.
The ~/.shosts (in each user's home directory) files
list remote hosts and users that are trusted by the
local system. To remove these files, run the following command
to delete them from any location:
$ sudo find / -name '.shosts' -type f -delete
OL08-00-010470 no_user_host_based_files
V-248599 366 low OL 8 must enable the hardware random number generator entropy gatherer service. SRG-OS-ID
The rngd service
feeds random data from hardware device to kernel random device.
The Hardware RNG Entropy Gatherer service should be enabled.

The rngd service can be enabled with the following command:
$ sudo systemctl enable rngd.service
OL08-00-010471 service_rngd_enabled
V-248600 366 low OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. SRG-OS-ID
rng-tools provides hardware random number generator tools,
such as those used in the formation of x509/PKI certificates.
The rng-tools package can be installed with the following command:
$ sudo yum install rng-tools
OL08-00-010472 package_rng-tools_installed
V-248601 366 medium The OL 8 SSH public host key files must have mode "0644" or less permissive. SRG-OS-ID
If a public host key file is modified by an unauthorized user, the SSH service
may be compromised.
 To properly set the permissions of /etc/ssh/*.pub, run the command: 
$ sudo chmod 0644 /etc/ssh/*.pub
OL08-00-010480 file_permissions_sshd_pub_key
V-248602 366 medium The OL 8 SSH private host key files must have mode "0600" or less permissive. SRG-OS-ID
If an unauthorized user obtains the private SSH host key file, the host could be
impersonated.
SSH server private keys - files that match the /etc/ssh/*_key glob, have to have restricted permissions.
If those files are owned by the root user and the root group, they have to have the 0600 permission or stricter.
OL08-00-010490 file_permissions_sshd_private_key
V-248603 366 medium The OL 8 SSH daemon must perform strict mode checking of home directory configuration files. SRG-OS-ID
If other users have access to modify user-specific SSH configuration files, they
may be able to log into the system as another user.
SSHs StrictModes option checks file and ownership permissions in
the user's home directory .ssh folder before accepting login. If world-
writable permissions are found, logon is rejected.

The default SSH configuration has StrictModes enabled. The appropriate configuration is used if no value is set for StrictModes.
To explicitly enable StrictModes in SSH, add or correct the following line in /etc/ssh/sshd_config:
StrictModes yes
OL08-00-010500 sshd_enable_strictmodes
V-248604 366 medium The OL 8 SSH daemon must not allow compression or must only allow compression after successful authentication. SRG-OS-ID
If compression is allowed in an SSH connection prior to authentication,
vulnerabilities in the compression software could result in compromise of the
system from an unauthenticated connection, potentially with root privileges.
Compression is useful for slow network connections over long
distances but can cause performance issues on local LANs. If use of compression
is required, it should be enabled only after a user has authenticated; otherwise,
it should be disabled. To disable compression or delay compression until after
a user has successfully authenticated, add or correct the following line in the
/etc/ssh/sshd_config file:
Compression 
OL08-00-010510 sshd_disable_compression
V-248605 366 medium The OL 8 SSH daemon must not allow authentication using known host's authentication. SRG-OS-ID
Configuring this setting for the SSH daemon provides additional
assurance that remote login via SSH will require a password, even
in the event of misconfiguration elsewhere.
SSH can allow system users to connect to systems if a cache of the remote
systems public keys is available.  This should be disabled.


To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config:
IgnoreUserKnownHosts yes
OL08-00-010520 sshd_disable_user_known_hosts
V-248606 366 medium The OL 8 SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements. SRG-OS-ID
Kerberos authentication for SSH is often implemented using GSSAPI. If Kerberos
is enabled through SSH, the SSH daemon provides a means of access to the
system's Kerberos implementation. 
Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use unused methods of authentication, even in the event of misconfiguration elsewhere. 
Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like Kerberos.

The default SSH configuration disallows authentication validation through Kerberos. The appropriate configuration is used if no value is set for KerberosAuthentication.
To explicitly disable Kerberos authentication, add or correct the following line in /etc/ssh/sshd_config:
KerberosAuthentication no
OL08-00-010521 sshd_disable_kerb_auth
V-248607 366 medium The OL 8 SSH daemon must not allow GSSAPI authentication, except to fulfill documented and validated mission requirements. SRG-OS-ID
GSSAPI authentication is used to provide additional authentication mechanisms to
applications. Allowing GSSAPI authentication through SSH exposes the system's
GSSAPI to remote hosts, increasing the attack surface of the system.
Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like GSSAPI.

The default SSH configuration disallows authentications based on GSSAPI. The appropriate configuration is used if no value is set for GSSAPIAuthentication.
To explicitly disable GSSAPI authentication, add or correct the following line in /etc/ssh/sshd_config:
GSSAPIAuthentication no
OL08-00-010522 sshd_disable_gssapi_auth
V-248608 366 low OL 8 must use a separate file system for "/var". SRG-OS-ID
Ensuring that /var is mounted on its own partition enables the
setting of more restrictive mount options. This helps protect
system services such as daemons or other programs which use it.
It is not uncommon for the /var directory to contain
world-writable directories installed by other software packages.
The /var directory is used by daemons and other system
services to store frequently-changing data. Ensure that /var has its own partition
or logical volume at installation time, or migrate it using LVM.
OL08-00-010540 partition_for_var
V-248609 366 low OL 8 must use a separate file system for "/var/log". SRG-OS-ID
Placing /var/log in its own partition
enables better separation between log files
and other files in /var/.
System logs are stored in the /var/log directory.

Ensure that /var/log has its own partition or logical
volume at installation time, or migrate it using LVM.
OL08-00-010541 partition_for_var_log
V-248610 366 low OL 8 must use a separate file system for the system audit data path. SRG-OS-ID
Placing /var/log/audit in its own partition
enables better separation between audit files
and other files, and helps ensure that
auditing cannot be halted due to the partition running out
of space.
Audit logs are stored in the /var/log/audit directory.

Ensure that /var/log/audit has its own partition or logical
volume at installation time, or migrate it using LVM.
Make absolutely certain that it is large enough to store all
audit logs that will be created by the auditing daemon.
OL08-00-010542 partition_for_var_log_audit
V-248611 366 medium OL 8 must use a separate file system for "/tmp". SRG-OS-ID
The /tmp partition is used as temporary storage by many programs.
Placing /tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it.
The /tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM.
OL08-00-010543 partition_for_tmp
V-248612 366 medium OL 8 must use a separate file system for /var/tmp. SRG-OS-ID
The /var/tmp partition is used as temporary storage by many programs.
Placing /var/tmp in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it.
The /var/tmp directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM.
OL08-00-010544 partition_for_var_tmp
V-248613 770 medium OL 8 must not permit direct logons to the root account using remote access via SSH. SRG-OS-ID
Even though the communications channel may be encrypted, an additional layer of
security is gained by extending the policy of not logging directly on as root.
In addition, logging in with a user-specific account provides individual
accountability of actions performed on the system and also helps to minimize
direct attack attempts on root's password.
The root user should never be allowed to login to a
system directly over a network.
To disable root login via SSH, add or correct the following line in


/etc/ssh/sshd_config:

PermitRootLogin no
OL08-00-010550 sshd_disable_root_login
V-248615 366 medium OL 8 must have the rsyslog service enabled and active. SRG-OS-ID
The rsyslog service must be running in order to provide
logging services, which are essential to system administration.
The rsyslog service provides syslog-style logging by default on Oracle Linux 8.

The rsyslog service can be enabled with the following command:
$ sudo systemctl enable rsyslog.service
OL08-00-010561 service_rsyslog_enabled
V-248616 366 medium OL 8 must prevent files with the setuid and setgid bit set from being executed on file systems that contain user home directories. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from user home directory partitions.
The nosuid mount option can be used to prevent
execution of setuid programs in /home. The SUID and SGID permissions
should not be required in these user data directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/home.
OL08-00-010570 mount_option_home_nosuid
V-248617 366 medium OL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot directory. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from boot partitions.
The nosuid mount option can be used to prevent
execution of setuid programs in /boot. The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot.
OL08-00-010571 mount_option_boot_nosuid
V-248618 366 medium OL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from boot partitions.
The nosuid mount option can be used to prevent
execution of setuid programs in /boot/efi. The SUID and SGID permissions
should not be required on the boot partition.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/boot/efi.
OL08-00-010572 mount_option_boot_efi_nosuid
V-248619 366 medium OL 8 must prevent special devices on non-root local partitions. SRG-OS-ID
The nodev mount option prevents files from being
interpreted as character or block devices. The only legitimate location
for device files is the /dev directory located on the root partition.
The only exception to this is chroot jails, for which it is not advised
to set nodev on these filesystems.
The nodev mount option prevents files from being interpreted as
character or block devices. Legitimate character and block devices should
exist only in the /dev directory on the root partition or within
chroot jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of

    any non-root local partitions.
OL08-00-010580 mount_option_nodev_nonroot_local_partitions
V-248620 366 medium OL 8 file systems that contain user home directories must not execute binary files. SRG-OS-ID
The /home directory contains data of individual users. Binaries in
this directory should not be considered as trusted and users should not be
able to execute them.
The noexec mount option can be used to prevent binaries from being
executed out of /home. 
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/home.
OL08-00-010590 mount_option_home_noexec
V-248621 366 medium OL 8 file systems must not interpret character or block special devices from untrusted file systems. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. An exception to this is chroot jails, and it is
not advised to set nodev on partitions which contain their root
filesystems.
The nodev mount option prevents files from being
interpreted as character or block devices.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of

    any removable media partitions.
OL08-00-010600 mount_option_nodev_removable_partitions
V-248622 366 medium OL 8 file systems must not execute binary files on removable media. SRG-OS-ID
Allowing users to execute binaries from removable media such as USB keys exposes
the system to potential compromise.
The noexec mount option prevents the direct execution of binaries
on the mounted filesystem. Preventing the direct execution of binaries from
removable media (such as a USB key) provides a defense against malicious
software that may be present on such untrusted media.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of

    any removable media partitions.
OL08-00-010610 mount_option_noexec_removable_partitions
V-248623 366 medium OL 8 must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Allowing
users to introduce SUID or SGID binaries from partitions mounted off of
removable media would allow them to introduce their own highly-privileged programs.
The nosuid mount option prevents set-user-identifier (SUID)
and set-group-identifier (SGID) permissions from taking effect. These permissions
allow users to execute binaries with the same permissions as the owner and group
of the file respectively. Users should not be allowed to introduce SUID and SGID
files into the system via partitions mounted from removeable media.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of

    any removable media partitions.
OL08-00-010620 mount_option_nosuid_removable_partitions
V-248624 366 medium OL 8 file systems must not execute binary files that are imported via Network File System (NFS). SRG-OS-ID
The noexec mount option causes the system not to execute binary files. This option must be used
for mounting any file system not containing approved binary files as they may be incompatible. Executing
files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized
administrative access.
Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts.
OL08-00-010630 mount_option_noexec_remote_filesystems
V-248625 366 medium OL 8 file systems must not interpret character or block special devices that are imported via NFS. SRG-OS-ID
Legitimate device files should only exist in the /dev directory. NFS mounts
should not present device files to users.
Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts.
OL08-00-010640 mount_option_nodev_remote_filesystems
V-248626 366 medium OL 8 must prevent files with the setuid and setgid bit set from being executed on file systems that are imported via Network File System (NFS). SRG-OS-ID
NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables
should be installed to their default location on the local filesystem.
Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of
any NFS mounts.
OL08-00-010650 mount_option_nosuid_remote_filesystems
V-248627 366 medium Local OL 8 initialization files must not execute world-writable programs. SRG-OS-ID
If user start-up files execute world-writable programs, especially in
unprotected directories, they could be maliciously modified to destroy user
files or otherwise compromise the system at the user level. If the system is
compromised at the user level, it is easier to elevate privileges to eventually
compromise the system at the root and network level.
Set the mode on files being executed by the user initialization files with the
following command:
$ sudo chmod o-w FILE
OL08-00-010660 accounts_user_dot_no_world_writable_programs
V-248628 1665 medium OL 8 must disable kernel dumps unless needed. SRG-OS-ID
Kernel core dumps may contain the full contents of system memory at the
time of the crash. Kernel core dumps consume a considerable amount of disk
space and may result in denial of service by exhausting the available space
on the target file system partition. Unless the system is used for kernel
development or testing, there is little need to run the kdump service.
The kdump service provides a kernel crash dump analyzer. It uses the kexec
system call to boot a secondary kernel ("capture" kernel) following a system
crash, which can load information from the crashed kernel for analysis.

The kdump service can be disabled with the following command:
$ sudo systemctl mask --now kdump.service
OL08-00-010670 service_kdump_disabled
V-248629 366 medium OL 8 must disable the "kernel.core_pattern". SRG-OS-ID
A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data and is generally useful
only for developers trying to debug problems.
To set the runtime status of the kernel.core_pattern kernel parameter, run the following command: 
$ sudo sysctl -w kernel.core_pattern=|/bin/false
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.core_pattern = |/bin/false
OL08-00-010671 sysctl_kernel_core_pattern
V-248630 366 medium OL 8 must disable acquiring, saving, and processing core dumps. SRG-OS-ID
A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data
and is generally useful only for developers trying to debug problems.
The systemd-coredump.socket unit is a socket activation of
the systemd-coredump@.service which processes core dumps.
By masking the unit, core dump processing is disabled.
OL08-00-010672 service_systemd-coredump_disabled
V-248631 366 medium OL 8 must disable core dumps for all users. SRG-OS-ID
A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data and is generally useful
only for developers trying to debug problems.
To disable core dumps for all users, add the following line to
/etc/security/limits.conf, or to a file within the
/etc/security/limits.d/ directory:
*     hard   core    0
OL08-00-010673 disable_users_coredumps
V-248632 366 medium OL 8 must disable storing core dumps. SRG-OS-ID
A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data
and is generally useful only for developers or system operators trying to
debug problems. Enabling core dumps on production systems is not recommended,
however there may be overriding operational requirements to enable advanced
debuging. Permitting temporary enablement of core dumps during such situations
should be reviewed through local needs and policy.
The Storage option in [Coredump] section
of /etc/systemd/coredump.conf
can be set to none to disable storing core dumps permanently.
OL08-00-010674 coredump_disable_storage
V-248633 366 medium OL 8 must disable core dump backtraces. SRG-OS-ID
A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data
and is generally useful only for developers or system operators trying to
debug problems.

Enabling core dumps on production systems is not recommended,
however there may be overriding operational requirements to enable advanced
debuging. Permitting temporary enablement of core dumps during such situations
should be reviewed through local needs and policy.
The ProcessSizeMax option in [Coredump] section
of /etc/systemd/coredump.conf
specifies the maximum size in bytes of a core which will be processed.
Core dumps exceeding this size may be stored, but the backtrace will not
be generated.
OL08-00-010675 coredump_disable_backtraces
V-248634 366 medium For OL 8 systems using Domain Name Servers (DNS) resolution, at least two name servers must be configured. SRG-OS-ID
To provide availability for name resolution services, multiple redundant
name servers are mandated. A failure in name resolution could lead to the
failure of security functions requiring name resolution, which may include
time synchronization, centralized authentication, and remote system logging.
Determine whether the system is using local or DNS name resolution with the
following command:
$ sudo grep hosts /etc/nsswitch.conf
hosts: files dns
If the DNS entry is missing from the host's line in the "/etc/nsswitch.conf" file, the "/etc/resolv.conf" file must be empty. Verify the "/etc/resolv.conf" file is empty with the following command:
$ sudo ls -al /etc/resolv.conf
-rw-r--r-- 1 root root 0 Aug 19 08:31 resolv.conf
If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file, then verify the following:
Multiple Domain Name System (DNS) Servers should be configured in /etc/resolv.conf. This provides redundant name resolution services in the event that a domain server crashes. To configure the system to contain as least 2 DNS servers, add a corresponding nameserver ip_address entry in /etc/resolv.conf for each DNS server where ip_address is the IP address of a valid DNS server. For example:
search example.com
nameserver 192.168.0.1
nameserver 192.168.0.2
OL08-00-010680 network_configure_name_resolution
V-248635 366 medium Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's home directory. SRG-OS-ID
The executable search path (typically the PATH environment variable) contains a
list of directories for the shell to search to find executables. If this path
includes the current working directory (other than the users home directory),
executables in these directories may be executed instead of system commands.
This variable is formatted as a colon-separated list of directories. If there is
an empty entry, such as a leading or trailing colon or two consecutive colons,
this is interpreted as the current working directory. If deviations from the
default system search path for the local interactive user are required, they
must be documented with the Information System Security Officer (ISSO).
Ensure that all interactive user initialization files executable search
path statements do not contain statements that will reference a working
directory other than the users home directory.
OL08-00-010690 accounts_user_home_paths_only
V-248636 366 medium All OL 8 world-writable directories must be owned by root, sys, bin, or an application user. SRG-OS-ID
Allowing a user account to own a world-writable directory is
undesirable because it allows the owner of that directory to remove
or replace any files that may be placed in the directory by other
users.
All directories in local partitions which are
world-writable should be owned by root or another
system account. If any world-writable directories are not
owned by a system account, this should be investigated.
Following this, the files should be deleted or assigned to an
appropriate owner.
OL08-00-010700 dir_perms_world_writable_system_owned
V-248637 366 medium All OL 8 world-writable directories must be group-owned by root, sys, bin, or an application group. SRG-OS-ID
Allowing a user account to group own a world-writable directory is
undesirable because it allows the owner of that directory to remove
or replace any files that may be placed in the directory by other
users.
All directories in local partitions which are
world-writable should be group owned by root or another
system account. If any world-writable directories are not
group owned by a system account, this should be investigated.
Following this, the files should be deleted or assigned to an
appropriate group.
OL08-00-010710 dir_perms_world_writable_system_owned_group
V-248638 366 medium All OL 8 local interactive users must have a home directory assigned in the "/etc/passwd" file. SRG-OS-ID
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.
Assign home directories to all interactive users that currently do not
have a home directory assigned.

This rule checks if the home directory is properly defined in a folder which has
at least one parent folder, like "user" in "/home/user" or "/remote/users/user".
Therefore, this rule will report a finding for home directories like /users,
/tmp or /.
OL08-00-010720 accounts_user_interactive_home_directory_defined
V-248639 366 medium All OL 8 local interactive user home directories must have mode "0750" or less permissive. SRG-OS-ID
Excessive permissions on local interactive user home directories may allow
unauthorized access to user files by other users.
Change the mode of interactive users home directories to 0750. To
change the mode of interactive users home directory, use the
following command:
$ sudo chmod 0750 /home/USER
OL08-00-010730 file_permissions_home_directories
V-248640 366 medium All OL 8 local interactive user home directory files must have mode "0750" or less permissive. SRG-OS-ID
If a local interactive user files have excessive permissions, unintended users
may be able to access or modify them.
Set the mode on files and directories in the local interactive user home
directory with the following command:
$ sudo chmod 0750 /home/USER/FILE_DIR
Files that begin with a "." are excluded from this requirement.
OL08-00-010731 accounts_users_home_files_permissions
V-248641 366 medium All OL 8 local interactive user home directories must be group-owned by the home directory owner's primary group. SRG-OS-ID
If the Group Identifier (GID) of a local interactive users home directory is
not the same as the primary GID of the user, this would allow unauthorized
access to the users files, and users that share the same group may not be
able to access files that they legitimately should.
Change the group owner of interactive users home directory to the
group found in /etc/passwd. To change the group owner of
interactive users home directory, use the following command:
$ sudo chgrp USER_GROUP /home/USER
This rule ensures every home directory related to an interactive user is group-owned by an interactive user. It also ensures that interactive users are group-owners of one and only one home directory.
OL08-00-010740 file_groupownership_home_directories
V-248642 366 medium OL 8 must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member. SRG-OS-ID
If a local interactive users files are group-owned by a group of which the
user is not a member, unintended users may be able to access them.
Change the group of a local interactive users files and directories to a
group that the interactive user is a member of. To change the group owner of a
local interactive users files and directories, use the following command:
$ sudo chgrp USER_GROUP /home/USER/FILE_DIR
This rule ensures every file or directory under the home directory related to an interactive user is group-owned by an interactive user.
OL08-00-010741 accounts_users_home_files_groupownership
V-248643 366 medium All OL 8 local interactive user home directories defined in the "/etc/passwd" file must exist. SRG-OS-ID
If a local interactive user has a home directory defined that does not exist,
the user may be given access to the / directory as the current working directory
upon logon. This could create a Denial of Service because the user would not be
able to access their logon configuration files, and it may give them visibility
to system files they normally would not be able to access.
Create home directories to all interactive users that currently do not
have a home directory assigned. Use the following commands to create the user
home directory assigned in /etc/passwd:
$ sudo mkdir /home/USER
OL08-00-010750 accounts_user_interactive_home_directory_exists
V-248644 366 medium All OL 8 local interactive user accounts must be assigned a home directory upon creation. SRG-OS-ID
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.
All local interactive user accounts, upon creation, should be assigned a home directory.


Configure the operating system to assign home directories to all new local interactive users by setting the CREATE_HOME parameter in /etc/login.defs to yes as follows:

CREATE_HOME yes
OL08-00-010760 accounts_have_homedir_login_defs
V-248645 366 medium All OL 8 local initialization files must have mode "0740" or less permissive. SRG-OS-ID
Local initialization files are used to configure the user's shell environment
upon logon. Malicious modification of these files could compromise accounts upon
logon.
Set the mode of the user initialization files to 0740 with the
following command:
$ sudo chmod 0740 /home/USER/.INIT_FILE
OL08-00-010770 file_permission_user_init_files
V-248646 366 medium All OL 8 files and directories must have a valid owner. SRG-OS-ID
Unowned files do not directly imply a security problem, but they are generally
a sign that something is amiss. They may
be caused by an intruder, by incorrect software installation or
draft software removal, or by failure to remove all files belonging
to a deleted account. The files should be repaired so they
will not cause problems when accounts are created in the future,
and the cause should be discovered and addressed.
If any files are not owned by a user, then the
cause of their lack of ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate user. The following command will discover and print
any files on local partitions which do not belong to a valid user:
$ df --local -P | awk {'if (NR!=1) print $6'} | sudo xargs -I '{}' find '{}' -xdev -nouser
To search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition:
$ sudo find PARTITION -xdev -nouser
OL08-00-010780 no_files_unowned_by_user
V-248647 366 medium All OL 8 files and directories must have a valid group owner. SRG-OS-ID
Unowned files do not directly imply a security problem, but they are generally
a sign that something is amiss. They may
be caused by an intruder, by incorrect software installation or
draft software removal, or by failure to remove all files belonging
to a deleted account. The files should be repaired so they
will not cause problems when accounts are created in the future,
and the cause should be discovered and addressed.
If any files are not owned by a group, then the
cause of their lack of group-ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate group. The following command will discover and print
any files on local partitions which do not belong to a valid group:
$ df --local -P | awk '{if (NR!=1) print $6}' | sudo xargs -I '{}' find '{}' -xdev -nogroup
To search all filesystems on a system including network mounted filesystems the following command can be run manually for each partition:
$ sudo find PARTITION -xdev -nogroup
OL08-00-010790 file_permissions_ungroupowned
V-248648 366 medium A separate OL 8 filesystem must be used for user home directories (such as "/home" or an equivalent). SRG-OS-ID
Ensuring that /home is mounted on its own partition enables the
setting of more restrictive mount options, and also helps ensure that
users cannot trivially fill partitions used for log or audit data storage.
If user home directories will be stored locally, create a separate partition
for /home at installation time (or migrate it later using LVM). If
/home will be mounted from another system such as an NFS server, then
creating a separate partition is not necessary at installation time, and the
mountpoint can instead be configured later.
OL08-00-010800 partition_for_home
V-248649 366 high Unattended or automatic logon via the OL 8 graphical user interface must not be allowed. SRG-OS-ID
Failure to restrict system access to authenticated users negatively impacts operating
system security.
The GNOME Display Manager (GDM) can allow users to automatically login without
user interaction or credentials. User should always be required to authenticate themselves
to the system that they are authorized to use. To disable user ability to automatically
login to the system, set the AutomaticLoginEnable to false in the
[daemon] section in /etc/gdm/custom.conf. For example:
[daemon]
AutomaticLoginEnable=false
OL08-00-010820 gnome_gdm_disable_automatic_login
V-248650 366 high OL 8 must not allow users to override SSH environment variables. SRG-OS-ID
SSH environment options potentially allow users to bypass
access restriction in some configurations.
Ensure that users are not able to override environment variables of the SSH daemon.

The default SSH configuration disables environment processing. The appropriate configuration is used if no value is set for PermitUserEnvironment.
To explicitly disable Environment options, add or correct the following /etc/ssh/sshd_config:
PermitUserEnvironment no
OL08-00-010830 sshd_do_not_permit_user_env
V-248651 16 medium OL 8 temporary user accounts must be provisioned with an expiration time of 72 hours or less. SRG-OS-ID
If temporary user accounts remain active when no longer needed or for
an excessive period, these accounts may be used to gain unauthorized access.
To mitigate this risk, automated termination of all temporary accounts
must be set upon account creation.

Temporary accounts are established as part of normal account activation
procedures when there is a need for short-term accounts. In the event
temporary or emergency accounts are required, configure the system to
terminate them after a documented time period. For every temporary and
emergency account, run the following command to set an expiration date on
it, substituting USER and YYYY-MM-DD
appropriately:
$ sudo chage -E YYYY-MM-DD USER
YYYY-MM-DD indicates the documented expiration date for the account. For U.S. Government systems, the operating system must be configured to automatically terminate these types of accounts after a period of 72 hours.
OL08-00-020000 account_temp_expire_date
V-248652 2238 medium OL 8 systems below version 8.2 must automatically lock an account when three unsuccessful logon attempts occur. SRG-OS-ID
Locking out user accounts after a number of incorrect attempts prevents direct password
guessing attacks. In combination with the silent option, user enumeration attacks
are also mitigated.
This rule configures the system to lock out accounts after a number of incorrect login attempts
using pam_faillock.so.

pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version.
OL08-00-020010 accounts_passwords_pam_faillock_deny
V-248653 medium OL 8 systems, versions 8.2 and above, must automatically lock an account when three unsuccessful logon attempts occur. SRG-OS-ID
OL08-00-020011 Missing Rule
V-248654 2238 medium OL 8 systems below version 8.2 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
By limiting the number of failed logon attempts the risk of unauthorized system
access via user password guessing, otherwise known as brute-forcing, is reduced.
Limits are imposed by locking the account.
Utilizing pam_faillock.so, the fail_interval directive configures the system
to lock out an account after a number of incorrect login attempts within a specified time
period.
OL08-00-020012 accounts_passwords_pam_faillock_interval
V-248655 medium OL 8 systems, versions 8.2 and above, must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
OL08-00-020013 Missing Rule
V-248656 2238 medium OL 8 systems below version 8.2 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
Locking out user accounts after a number of incorrect attempts prevents direct password
guessing attacks. Ensuring that an administrator is involved in unlocking locked accounts
draws appropriate attention to such situations.
This rule configures the system to lock out accounts during a specified time period after a
number of incorrect login attempts using pam_faillock.so.

pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid any errors when manually editing these files,
it is recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version.
OL08-00-020014 accounts_passwords_pam_faillock_unlock_time
V-248657 medium OL 8 systems, versions 8.2 and above, must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
OL08-00-020015 Missing Rule
V-248658 medium OL 8 systems below version 8.2 must ensure account lockouts persist. SRG-OS-ID
OL08-00-020016 Missing Rule
V-248659 medium OL 8 systems, versions 8.2 and above, must ensure account lockouts persist. SRG-OS-ID
OL08-00-020017 Missing Rule
V-248660 medium OL 8 systems below version 8.2 must prevent system messages from being presented when three unsuccessful logon attempts occur. SRG-OS-ID
OL08-00-020018 Missing Rule
V-248661 medium OL 8 systems, versions 8.2 and above, must prevent system messages from being presented when three unsuccessful logon attempts occur. SRG-OS-ID
OL08-00-020019 Missing Rule
V-248662 medium OL 8 systems below version 8.2 must log user name information when unsuccessful logon attempts occur. SRG-OS-ID
OL08-00-020020 Missing Rule
V-248663 medium OL 8 systems, versions 8.2 and above, must log user name information when unsuccessful logon attempts occur. SRG-OS-ID
OL08-00-020021 Missing Rule
V-248664 2238 medium OL 8 systems below version 8.2 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
By limiting the number of failed logon attempts, the risk of unauthorized system access via
user password guessing, also known as brute-forcing, is reduced. Limits are imposed by locking
the account.
This rule configures the system to lock out the root account after a number of
incorrect login attempts using pam_faillock.so.

pam_faillock.so module requires multiple entries in pam files. These entries must be carefully
defined to work as expected. In order to avoid errors when manually editing these files, it is
recommended to use the appropriate tools, such as authselect or authconfig,
depending on the OS version.
OL08-00-020022 accounts_passwords_pam_faillock_deny_root
V-248665 medium OL 8 systems, versions 8.2 and above, must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period. SRG-OS-ID
OL08-00-020023 Missing Rule
V-248666 54 low OL 8 must limit the number of concurrent sessions to 10 for all accounts and/or account types. SRG-OS-ID
Limiting simultaneous user logins can insulate the system from denial of service
problems caused by excessive logins. Automated login processes operating improperly or
maliciously may result in an exceptional number of simultaneous login sessions.
Limiting the number of allowed users and sessions per user can limit risks related to Denial of
Service attacks. This addresses concurrent sessions for a single account and does not address
concurrent sessions by a single user via multiple accounts. To set the number of concurrent
sessions per user add the following line in /etc/security/limits.conf or
a file under /etc/security/limits.d/:
* hard maxlogins 
OL08-00-020024 accounts_max_concurrent_login_sessions
V-248667 medium OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. SRG-OS-ID
OL08-00-020025 Missing Rule
V-248668 medium OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. SRG-OS-ID
OL08-00-020026 Missing Rule
V-248669 medium OL 8 systems, versions 8.2 and above, must configure SELinux context type to allow the use of a non-default faillock tally directory. SRG-OS-ID
OL08-00-020027 Missing Rule
V-248670 medium OL 8 systems below version 8.2 must configure SELinux context type to allow the use of a non-default faillock tally directory. SRG-OS-ID
OL08-00-020028 Missing Rule
V-248671 58 medium OL 8 must enable a user session lock until that user reestablishes access using established identification and authentication procedures for graphical user sessions. SRG-OS-ID
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absense.
To activate locking of the screensaver in the GNOME3 desktop when it is activated,
add or set lock-enabled to true in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/desktop/screensaver]
lock-enabled=true
Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/desktop/screensaver/lock-enabled
After the settings have been set, run dconf update.
OL08-00-020030 dconf_gnome_screensaver_lock_enabled
V-248672 60 medium OL 8 must initiate a session lock for graphical user interfaces when the screensaver is activated. SRG-OS-ID
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absense.
To activate the locking delay of the screensaver in the GNOME3 desktop when
the screensaver is activated, add or set lock-delay to uint32  in
/etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/desktop/screensaver]
lock-delay=uint32 
After the settings have been set, run dconf update.
OL08-00-020031 dconf_gnome_screensaver_lock_delay
V-248673 366 medium OL 8 must disable the user list at logon for graphical user interfaces. SRG-OS-ID
Leaving the user list enabled is a security risk since it allows anyone
with physical access to the system to quickly enumerate known user accounts
without logging in.
In the default graphical environment, users logging directly into the
system are greeted with a login screen that displays all known users.
This functionality should be disabled by setting disable-user-list
to true.


To disable, add or edit disable-user-list to /etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/login-screen]
disable-user-list=true
Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/login-screen/disable-user-list
After the settings have been set, run dconf update.
OL08-00-020032 dconf_gnome_disable_user_list
V-248674 58 medium OL 8 must have the tmux package installed. SRG-OS-ID
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operation system session prior to vacating the vicinity,
operating systems need to be able to identify when a user's session has idled and take action to initiate the
session lock.


The tmux package allows for a session lock to be implemented and configured.
To enable console screen locking, install the tmux package.
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity can be determined.
Rather than be forced to wait for a period of time to expire before the user session can be locked, Oracle Linux 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
Instruct users to begin new terminal sessions with the following command:
$ tmux
The console can now be locked with the following key combination:
ctrl+b :lock-session
OL08-00-020039 package_tmux_installed
V-248675 58 medium OL 8 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for command line sessions. SRG-OS-ID
The tmux package allows for a session lock to be implemented and configured.
However, the session lock is implemented by an external command. The tmux
default configuration does not contain an effective session lock.
To enable console screen locking in tmux terminal multiplexer,
the vlock command must be configured to be used as a locking
mechanism.
Add the following line to /etc/tmux.conf:
set -g lock-command vlock
. The console can now be locked with the following key combination:
ctrl+b :lock-session
OL08-00-020040 configure_tmux_lock_command
V-248676 58 medium OL 8 must ensure session control is automatically started at shell initialization. SRG-OS-ID
Unlike bash itself, the tmux terminal multiplexer
provides a mechanism to lock sessions after period of inactivity.
A session lock is a temporary action taken when a user stops work and moves away from the
immediate physical vicinity of the information system but does not want to
log out because of the temporary nature of the absence.
The tmux terminal multiplexer is used to implement
automatic session locking. It should be started from
/etc/bashrc or drop-in files within /etc/profile.d/.
OL08-00-020041 configure_bashrc_exec_tmux
V-248677 58 low OL 8 must prevent users from disabling session control mechanisms. SRG-OS-ID
Not listing tmux among permitted shells
prevents malicious program running as user
from lowering security by disabling the screen lock.
The tmux terminal multiplexer is used to implement
automatic session locking. It should not be listed in
/etc/shells.
OL08-00-020042 no_tmux_in_shells
V-248678 58 medium OL 8 must enable a user session lock until that user reestablishes access using established identification and authentication procedures for command line sessions. SRG-OS-ID
A session lock is a temporary action taken when a user stops work and
moves away from the immediate physical vicinity of the information
system but does not want to log out because of the temporary nature of
the absence.

The session lock is implemented at the point where session activity can
be determined.

Regardless of where the session lock is determined and implemented,
once invoked, the session lock must remain in place until the user
reauthenticates. No other activity aside from reauthentication must
unlock the system.
The Oracle Linux 8 operating system must have vlock installed to allow for session locking.


The kbd package can be installed with the following command:
$ sudo yum install kbd
OL08-00-020043 vlock_installed
V-248679 58 medium OL 8 must be able to initiate directly a session lock for all connection types using smartcard when the smartcard is removed. SRG-OS-ID
Locking the screen automatically when removing the smartcard can
prevent undesired access to system.
In the default graphical environment, screen locking on smartcard removal
can be enabled by setting removal-action
to 'lock-screen'.


To enable, add or edit removal-action to /etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/settings-daemon/peripherals/smartcard]
removal-action='lock-screen'
Once the setting has been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/settings-daemon/peripherals/smartcard/removal-action
After the settings have been set, run dconf update.
OL08-00-020050 dconf_gnome_lock_screen_on_smartcard_removal
V-248680 60 medium OL 8 must automatically lock graphical user sessions after 15 minutes of inactivity. SRG-OS-ID
A session time-out lock is a temporary action taken when a user stops work and moves away from
the immediate physical vicinity of the information system but does not logout because of the
temporary nature of the absence. Rather than relying on the user to manually lock their operating
system session prior to vacating the vicinity, GNOME3 can be configured to identify when
a user's session has idled and take action to initiate a session lock.
The idle time-out value for inactivity in the GNOME3 desktop is configured via the idle-delay
setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory
and locked in /etc/dconf/db/local.d/locks directory to prevent user modification.


For example, to configure the system for a 15 minute delay, add the following to /etc/dconf/db/local.d/00-security-settings:
[org/gnome/desktop/session]
idle-delay=uint32 900
OL08-00-020060 dconf_gnome_screensaver_idle_delay
V-248681 60 medium OL 8 must automatically lock command line user sessions after 15 minutes of inactivity. SRG-OS-ID
Locking the session after a period of inactivity limits the
potential exposure if the session is left unattended.
To enable console screen locking in tmux terminal multiplexer
after a period of inactivity,
the lock-after-time option has to be set to a value greater than 0 and less than
or equal to 900 in /etc/tmux.conf.
OL08-00-020070 configure_tmux_lock_after_time
V-248682 60 medium OL 8 must prevent a user from overriding the session lock-delay setting for the graphical user interface. SRG-OS-ID
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock. As such, users should not be allowed to change session settings.
If not already configured, ensure that users cannot change GNOME3 screensaver lock settings
by adding /org/gnome/desktop/screensaver/lock-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/screensaver/lock-delay
After the settings have been set, run dconf update.
OL08-00-020080 dconf_gnome_screensaver_user_locks
V-248683 60 medium OL 8 must prevent a user from overriding the session idle-delay setting for the graphical user interface. SRG-OS-ID
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock. As such, users should not be allowed to change session settings.
If not already configured, ensure that users cannot change GNOME3 session idle settings
by adding /org/gnome/desktop/session/idle-delay
to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification.
For example:
/org/gnome/desktop/session/idle-delay
After the settings have been set, run dconf update.
OL08-00-020081 dconf_gnome_session_idle_user_locks
V-248684 medium OL 8 must prevent a user from overriding the session lock-enabled setting for the graphical user interface. SRG-OS-ID
OL08-00-020082 Missing Rule
V-248685 187 medium OL 8 must map the authenticated identity to the user or group account for PKI-based authentication. SRG-OS-ID
Without mapping the certificate used to authenticate to the user account, the ability to
determine the identity of the individual user or group will not be available for forensic
analysis.
SSSD should be configured to verify the certificate of the user or group. To set this up
 ensure that section like certmap/testing.test/rule_name is setup in
/etc/sssd/sssd.conf. For example
[certmap/testing.test/rule_name]
matchrule =<SAN>.*EDIPI@mil
maprule = (userCertificate;binary={cert!bin})
domains = testing.test
OL08-00-020090 sssd_enable_certmap
V-248686 366 medium OL 8 must ensure the password complexity module is enabled in the password-auth file. SRG-OS-ID
Enabling PAM password complexity permits to enforce strong passwords and consequently
makes the system less prone to dictionary attacks.
To enable PAM password complexity in password-auth file:
Edit the password section in
/etc/pam.d/password-auth to show
password    requisite                                    pam_pwquality.so.
OL08-00-020100 accounts_password_pam_pwquality_password_auth
V-252657 366 medium OL 8 must ensure the password complexity module is enabled in the system-auth file. SRG-OS-ID
Enabling PAM password complexity permits to enforce strong passwords and consequently
makes the system less prone to dictionary attacks.
To enable PAM password complexity in system-auth file:
Edit the password section in
/etc/pam.d/system-auth to show
password    requisite                                    pam_pwquality.so.
OL08-00-020101 accounts_password_pam_pwquality_system_auth
V-252658 medium OL 8 systems below version 8.4 must ensure the password complexity module in the system-auth file is configured for three retries or less. SRG-OS-ID
OL08-00-020102 Missing Rule
V-252659 medium OL 8 systems below version 8.4 must ensure the password complexity module in the password-auth file is configured for three retries or less. SRG-OS-ID
OL08-00-020103 Missing Rule
V-252660 366 medium OL 8 systems, version 8.4 and above, must ensure the password complexity module is configured for three retries or less. SRG-OS-ID
Setting the password retry prompts that are permitted on a per-session basis to a low value
requires some software, such as SSH, to re-connect. This can slow down and
draw additional attention to some types of password-guessing attacks. Note that this
is different from account lockout, which is provided by the pam_faillock module.
To configure the number of retry prompts that are permitted per-session:

Edit the pam_pwquality.so statement in

/etc/pam.d/system-auth to show


retry=, or a lower value if site
policy is more restrictive. The DoD requirement is a maximum of 3 prompts
per session.
OL08-00-020104 accounts_password_pam_retry
V-248687 193 low OL 8 must enforce password complexity by requiring that at least one uppercase character be used. SRG-OS-ID
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts
at guessing and brute-force attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.
The pam_pwquality module's ucredit= parameter controls requirements for
usage of uppercase letters in a password. When set to a negative number, any password will be required to
contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each uppercase character. Modify the ucredit setting in
/etc/security/pwquality.conf to require the use of an uppercase character in passwords.
OL08-00-020110 accounts_password_pam_ucredit
V-248688 193 low OL 8 must enforce password complexity by requiring that at least one lowercase character be used. SRG-OS-ID
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.

Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possble combinations that need to be tested before the password is compromised. Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space.
The pam_pwquality module's lcredit parameter controls requirements for
usage of lowercase letters in a password. When set to a negative number, any password will be required to
contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each lowercase character. Modify the lcredit setting in
/etc/security/pwquality.conf to require the use of a lowercase character in passwords.
OL08-00-020120 accounts_password_pam_lcredit
V-248689 194 low OL 8 must enforce password complexity by requiring that at least one numeric character be used. SRG-OS-ID
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring digits makes password guessing attacks more difficult by ensuring a larger search space.
The pam_pwquality module's dcredit parameter controls requirements for
usage of digits in a password. When set to a negative number, any password will be required to
contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each digit. Modify the dcredit setting in
/etc/security/pwquality.conf to require the use of a digit in passwords.
OL08-00-020130 accounts_password_pam_dcredit
V-248690 195 medium OL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed. SRG-OS-ID
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting
attempts at guessing and brute-force attacks.

Password complexity is one factor of several that determines how long it takes to crack a password. The more complex a password, the greater the number of possible combinations that need to be tested before the password is compromised.
The pam_pwquality module's maxclassrepeat parameter controls requirements for
consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters from the same character class. Modify the
maxclassrepeat setting in /etc/security/pwquality.conf to equal 
to prevent a run of ( + 1) or more identical characters.
OL08-00-020140 accounts_password_pam_maxclassrepeat
V-248691 195 medium OL 8 must require the maximum number of repeating characters be limited to three when passwords are changed. SRG-OS-ID
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at
guessing and brute-force attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.

Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks.
The pam_pwquality module's maxrepeat parameter controls requirements for
consecutive repeating characters. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters. Modify the maxrepeat setting
in /etc/security/pwquality.conf to equal  to prevent a
run of ( + 1) or more identical characters.
OL08-00-020150 accounts_password_pam_maxrepeat
V-248692 195 medium OL 8 must require the change of at least four character classes when passwords are changed. SRG-OS-ID
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts
at guessing and brute-force attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.

Requiring a minimum number of character categories makes password guessing attacks more difficult by ensuring a larger search space.
The pam_pwquality module's minclass parameter controls
requirements for usage of different character classes, or types, of character
that must exist in a password before it is considered valid. For example,
setting this value to three (3) requires that any password must have characters
from at least three different categories in order to be approved. The default
value is zero (0), meaning there are no required classes. There are four
categories available:
* Upper-case characters
* Lower-case characters
* Digits
* Special characters (for example, punctuation)
Modify the minclass setting in /etc/security/pwquality.conf entry to require differing categories of characters when changing passwords.
OL08-00-020160 accounts_password_pam_minclass
V-248693 195 low OL 8 must require the change of at least 8 characters when passwords are changed. SRG-OS-ID
Use of a complex password helps to increase the time and resources
required to compromise the password. Password complexity, or strength,
is a measure of the effectiveness of a password in resisting attempts
at guessing and brute–force attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.

Requiring a minimum number of different characters during password changes ensures that newly changed passwords should not resemble previously compromised ones. Note that passwords which are changed on compromised systems will still be compromised, however.
The pam_pwquality module's difok parameter sets the number of characters
in a password that must not be present in and old password during a password change.


Modify the difok setting in /etc/security/pwquality.conf to equal to require differing characters when changing passwords.
OL08-00-020170 accounts_password_pam_difok
V-248694 198 medium OL 8 passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in "/etc/shadow". SRG-OS-ID
Enforcing a minimum password lifetime helps to prevent repeated password
changes to defeat the password reuse or history enforcement requirement. If
users are allowed to immediately and continually change their password, the
password could be repeatedly changed in a short period of time to defeat the
organization's policy regarding password reuse.
Configure non-compliant accounts to enforce a 24 hours/1 day minimum password
lifetime by running the following command:
$ sudo chage -m 1 USER
OL08-00-020180 accounts_password_set_min_life_existing
V-248695 198 medium OL 8 passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in "/etc/logins.def". SRG-OS-ID
Enforcing a minimum password lifetime helps to prevent repeated password
changes to defeat the password reuse or history enforcement requirement. If
users are allowed to immediately and continually change their password,
then the password could be repeatedly changed in a short period of time to
defeat the organization's policy regarding password reuse.


Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement.
To specify password minimum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MIN_DAYS 
A value of 1 day is considered sufficient for many environments. The DoD requirement is 1. The profile requirement is .
OL08-00-020190 accounts_minimum_age_login_defs
V-248696 199 medium OL 8 user account passwords must have a 60-day maximum password lifetime restriction. SRG-OS-ID
Any password, no matter how complex, can eventually be cracked. Therefore, passwords
need to be changed periodically. If the operating system does not limit the lifetime
of passwords and force users to change their passwords, there is the risk that the
operating system passwords could be compromised.


Setting the password maximum age ensures users are required to periodically change their passwords. Requiring shorter password lifetimes increases the risk of users writing down the password in a convenient location subject to physical compromise.
To specify password maximum age for new accounts,
edit the file /etc/login.defs
and add or correct the following line:
PASS_MAX_DAYS 
A value of 180 days is sufficient for many environments. The DoD requirement is 60. The profile requirement is .
OL08-00-020200 accounts_maximum_age_login_defs
V-248697 199 medium OL 8 user account passwords must be configured so that existing passwords are restricted to a 60-day maximum lifetime. SRG-OS-ID
Any password, no matter how complex, can eventually be cracked. Therefore,
passwords need to be changed periodically. If the operating system does
not limit the lifetime of passwords and force users to change their
passwords, there is the risk that the operating system passwords could be
compromised.
Configure non-compliant accounts to enforce a -day maximum password lifetime
restriction by running the following command:
$ sudo chage -M  USER
OL08-00-020210 accounts_password_set_max_life_existing
V-248698 200 low OL 8 must be configured in the password-auth file to prohibit password reuse for a minimum of five generations. SRG-OS-ID
Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user.
Do not allow users to reuse recent passwords. This can be accomplished by using the
remember option for the pam_pwhistory PAM module.
OL08-00-020220 accounts_password_pam_pwhistory_remember_password_auth
V-252661 200 medium OL 8 must be configured in the system-auth file to prohibit password reuse for a minimum of five generations. SRG-OS-ID
Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user.
Do not allow users to reuse recent passwords. This can be accomplished by using the
remember option for the pam_pwhistory PAM module.
OL08-00-020221 accounts_password_pam_pwhistory_remember_system_auth
V-248699 205 medium OL 8 passwords must have a minimum of 15 characters. SRG-OS-ID
The shorter the password, the lower the number of possible combinations
that need to be tested before the password is compromised.

Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.
The pam_pwquality module's minlen parameter controls requirements for
minimum characters required in a password. Add minlen=
after pam_pwquality to set minimum password length requirements.
OL08-00-020230 accounts_password_pam_minlen
V-248700 205 medium OL 8 passwords for new users must have a minimum of 15 characters. SRG-OS-ID
Requiring a minimum password length makes password
cracking attacks more difficult by ensuring a larger
search space. However, any security benefit from an onerous requirement
must be carefully weighed against usability problems, support costs, or counterproductive
behavior that may result.
To specify password length requirements for new accounts, edit the file
/etc/login.defs and add or correct the following line:
PASS_MIN_LEN 


The DoD requirement is 15. The FISMA requirement is 12. The profile requirement is . If a program consults /etc/login.defs and also another PAM module (such as pam_pwquality) during a password change operation, then the most restrictive must be satisfied. See PAM section for more information about enforcing password quality requirements.
OL08-00-020231 accounts_password_minlen_login_defs
V-248701 804 medium OL 8 duplicate User IDs (UIDs) must not exist for interactive users. SRG-OS-ID
To assure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system.
Change user IDs (UIDs), or delete accounts, so each has a unique name.
OL08-00-020240 account_unique_id
V-248702 768 medium OL 8 must implement multifactor authentication for access to interactive accounts. SRG-OS-ID
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
compromised, that compromise will not affect credentials stored on the
authentication device.


Multi-Factor Authentication (MFA) solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
SSSD should be configured to authenticate access to the system using smart cards.
To enable smart cards in SSSD, set pam_cert_auth to True under the
[pam] section in /etc/sssd/sssd.conf. For example:
[pam]
pam_cert_auth = True
Add or update "pam_sss.so" line in auth section of "/etc/pam.d/system-auth" file to include "try_cert_auth" or "require_cert_auth" option, like in the following example:
/etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth
Also add or update "pam_sss.so" line in auth section of "/etc/pam.d/smartcard-auth" file to include the "allow_missing_name" option, like in the following example:
/etc/pam.d/smartcard-auth:auth sufficient pam_sss.so allow_missing_name
OL08-00-020250 sssd_enable_smartcards
V-248703 795 medium The OL 8 system-auth file must disable access to the system for account identifiers (individuals, groups, roles, and devices) with 35 days of inactivity. SRG-OS-ID
Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system.
Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials.
Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
To specify the number of days after a password expires (which
signifies inactivity) until an account is permanently disabled, add or correct
the following line in /etc/default/useradd:
INACTIVE=
If a password is currently on the verge of expiration, then day(s) remain(s) until the account is automatically disabled. However, if the password will not expire for another 60 days, then 60 days plus day(s) could elapse until the account would be automatically disabled. See the useradd man page for more information.
OL08-00-020260 account_disable_post_pw_expiration
V-248704 medium The OL 8 password-auth file must disable access to the system for account identifiers (individuals, groups, roles, and devices) with 35 days of inactivity. SRG-OS-ID
OL08-00-020261 Missing Rule
V-248705 1314 medium The OL 8 lastlog command must have a mode of "0750" or less permissive. SRG-OS-ID
Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to
attackers, thus compromising its confidentiality.
To properly set the permissions of /usr/bin/lastlog, run the command:
$ sudo chmod 0750 /usr/bin/lastlog
OL08-00-020262 file_permissions_lastlog
V-248706 1314 medium The OL 8 lastlog command must be owned by root. SRG-OS-ID
Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to
attackers, thus compromising its confidentiality.
To properly set the owner of /usr/bin/lastlog, run the command:
$ sudo chown root /usr/bin/lastlog 
OL08-00-020263 file_ownership_lastlog
V-248707 1314 medium The OL 8 lastlog command must be group-owned by root. SRG-OS-ID
Unauthorized disclosure of the contents of the /var/log/lastlog file can reveal system data to
attackers, thus compromising its confidentiality.
To properly set the group owner of /var/log/lastlog, run the command:
$ sudo chgrp root /var/log/lastlog
OL08-00-020264 file_groupownership_lastlog
V-248708 1682 medium OL 8 emergency accounts must be automatically removed or disabled after the crisis is resolved or within 72 hours. SRG-OS-ID
If emergency user accounts remain active when no longer needed or for
an excessive period, these accounts may be used to gain unauthorized access.
To mitigate this risk, automated termination of all emergency accounts
must be set upon account creation.

Emergency accounts are privileged accounts established in response to
crisis situations where the need for rapid account activation is required.
In the event emergency accounts are required, configure the system to
terminate them after a documented time period. For every emergency account,
run the following command to set an expiration date on it, substituting
ACCOUNT_NAME and YYYY-MM-DD
appropriately:
$ sudo chage -E YYYY-MM-DD ACCOUNT_NAME
YYYY-MM-DD indicates the documented expiration date for the account. For U.S. Government systems, the operating system must be configured to automatically terminate these types of accounts after a period of 72 hours.
OL08-00-020270 account_emergency_expire_date
V-248709 1619 low All OL 8 passwords must contain at least one special character. SRG-OS-ID
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space.
The pam_pwquality module's ocredit= parameter controls requirements for
usage of special (or "other") characters in a password. When set to a negative number,
any password will be required to contain that many special characters.
When set to a positive number, pam_pwquality will grant +1
additional length credit for each special character. Modify the ocredit setting
in /etc/security/pwquality.conf to equal 
to require use of a special character in passwords.
OL08-00-020280 accounts_password_pam_ocredit
V-248710 2007 medium OL 8 must prohibit the use of cached authentications after one day. SRG-OS-ID
If cached authentication information is out-of-date, the validity of the
authentication information may be questionable.
SSSD should be configured to expire offline credentials after 1 day.

Check if SSSD allows cached authentications with the following command:
$ sudo grep cache_credentials /etc/sssd/sssd.conf
cache_credentials = true
If "cache_credentials" is set to "false" or is missing no further checks are required.
To configure SSSD to expire offline credentials, set offline_credentials_expiration to 1 under the [pam] section in /etc/sssd/sssd.conf. For example:
[pam]
offline_credentials_expiration = 1
OL08-00-020290 sssd_offline_cred_expiration
V-248711 366 medium OL 8 must prevent the use of dictionary words for passwords. SRG-OS-ID
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at
guessing and brute-force attacks.


Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.

Passwords with dictionary words may be more vulnerable to password-guessing attacks.
The pam_pwquality module's dictcheck check if passwords contains dictionary words. When
dictcheck is set to 1 passwords will be checked for dictionary words.
OL08-00-020300 accounts_password_pam_dictcheck
V-248712 366 medium OL 8 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. SRG-OS-ID
Increasing the time between a failed authentication attempt and re-prompting to
enter credentials helps to slow a single-threaded brute force attack.
To ensure the logon failure delay controlled by /etc/login.defs is set properly,
add or correct the FAIL_DELAY setting in /etc/login.defs to read as follows:
FAIL_DELAY 
OL08-00-020310 accounts_logon_fail_delay
V-248713 366 medium OL 8 must not have unnecessary accounts. SRG-OS-ID
Accounts providing no operational purpose provide additional opportunities for
system compromise. Unnecessary accounts include user accounts for individuals not
requiring access to the system and application accounts for applications not installed
on the system.
Enterprise Application tends to use the server or virtual machine exclusively.
Besides the default operating system user, there should be only authorized local
users required by the installed software groups and applications that exist on
the operating system. The authorized user list can be customized in the refine
value variable var_accounts_authorized_local_users_regex.
OVAL regular expression is used for the user list.
Configure the system so all accounts on the system are assigned to an active system,
application, or user account. Remove accounts that do not support approved system
activities or that allow for a normal user to perform administrative-level actions.
To remove unauthorized system accounts, use the following command:
$ sudo userdel unauthorized_user
OL08-00-020320 accounts_authorized_local_users
V-248714 366 high OL 8 must not allow accounts configured with blank or null passwords. SRG-OS-ID
Configuring this setting for the SSH daemon provides additional assurance
that remote login via SSH will require a password, even in the event of
misconfiguration elsewhere.
Disallow SSH login with empty passwords.
The default SSH configuration disables logins with empty passwords. The appropriate
configuration is used if no value is set for PermitEmptyPasswords.

To explicitly disallow SSH login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config:
PermitEmptyPasswords no
Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords.
OL08-00-020330 sshd_disable_empty_passwords
V-248715 366 high OL 8 must not allow blank or null passwords in the system-auth file. SRG-OS-ID
If an account has an empty password, anyone could log in and
run commands with the privileges of that account. Accounts with
empty passwords should never be used in operational environments.
If an account is configured for password authentication
but does not have an assigned password, it may be possible to log
into the account without authentication. Remove any instances of the
nullok in

/etc/pam.d/system-auth

to prevent logins with empty passwords.
OL08-00-020331 no_empty_passwords
V-248716 high OL 8 must not allow blank or null passwords in the password-auth file. SRG-OS-ID
OL08-00-020332 Missing Rule
V-248717 366 low OL 8 must display the date and time of the last successful account logon upon logon. SRG-OS-ID
Users need to be aware of activity that occurs regarding
their account. Providing users with information regarding the number
of unsuccessful attempts that were made to login to their account
allows the user to determine if any unauthorized activity has occurred
and gives them an opportunity to notify administrators.
To configure the system to notify users of last logon/access
using pam_lastlog, add or correct the pam_lastlog
settings in
/etc/pam.d/postlogin to read as follows:
session     required pam_lastlog.so showfailed
And make sure that the silent option is not set for pam_lastlog module.
OL08-00-020340 display_login_attempts
V-248718 366 medium OL 8 must display the date and time of the last successful account logon upon an SSH logon. SRG-OS-ID
Providing users feedback on when account accesses last occurred facilitates user
recognition and reporting of unauthorized account use.
Ensure that SSH will display the date and time of the last successful account logon.

The default SSH configuration enables print of the date and time of the last login. The appropriate configuration is used if no value is set for PrintLastLog.
To explicitly enable LastLog in SSH, add or correct the following line in /etc/ssh/sshd_config:
PrintLastLog yes
OL08-00-020350 sshd_print_last_log
V-248719 366 medium OL 8 default permissions must be defined in such a way that all authenticated users can read and modify only their own files. SRG-OS-ID
The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read and
written to by unauthorized users.
To ensure the default umask controlled by /etc/login.defs is set properly,
add or correct the UMASK setting in /etc/login.defs to read as follows:
UMASK 
OL08-00-020351 accounts_umask_etc_login_defs
V-248720 366 medium OL 8 must set the umask value to 077 for all local interactive user accounts. SRG-OS-ID
The umask controls the default access mode assigned to newly created files. A
umask of 077 limits new files to mode 700 or less permissive. Although umask can
be represented as a four-digit number, the first digit representing special
access modes is typically ignored or required to be 0. This requirement
applies to the globally configured system defaults and the local interactive
user defaults for each account on the system.
Remove the UMASK environment variable from all interactive users initialization files.
OL08-00-020352 accounts_umask_interactive_users
V-248721 366 medium OL 8 must define default permissions for logon and non-logon shells. SRG-OS-ID
The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users.
To ensure the default umask controlled by /etc/profile is set properly,
add or correct the umask setting in /etc/profile to read as follows:
umask 
OL08-00-020353 accounts_umask_etc_profile
V-248722 2234 medium The OL 8 audit system must be configured to audit the execution of privileged functions and prevent all software from executing at higher privilege levels than users executing the software. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have
compromised information system accounts, is a serious and ongoing concern
and can have significant adverse impacts on organizations. Auditing the use
of privileged functions is one way to detect such misuse and identify the
risk from insider threats and the advanced persistent threat.
Verify the system generates an audit record when privileged functions are executed.

If audit is using the "auditctl" tool to load the rules, run the following command:

$ sudo grep execve /etc/audit/audit.rules
If audit is using the "augenrules" tool to load the rules, run the following command:
$ sudo grep -r execve /etc/audit/rules.d
-a always,exit -F arch=b32 -S execve -C uid!=euid -k setuid
-a always,exit -F arch=b64 -S execve -C uid!=euid -k setuid
-a always,exit -F arch=b32 -S execve -C gid!=egid -k setgid
-a always,exit -F arch=b64 -S execve -C gid!=egid -k setgid
If both the "b32" and "b64" audit rules for "SUID" files are not defined, this is a finding. If both the "b32" and "b64" audit rules for "SGID" files are not defined, this is a finding.
OL08-00-030000 audit_rules_suid_privilege_function
V-248723 366 medium Cron logging must be implemented in OL 8. SRG-OS-ID
Cron logging can be used to trace the successful or unsuccessful execution
of cron jobs. It can also be used to spot intrusions into the use of the cron
facility by unauthorized and malicious users.
Cron logging must be implemented to spot intrusions or trace
cron job status. If cron is not logging to rsyslog, it
can be implemented by adding the following to the RULES section of
/etc/rsyslog.conf:
cron.*                                                  /var/log/cron
OL08-00-030010 rsyslog_cron_logging
V-248724 139 medium The OL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted of an audit processing failure event. SRG-OS-ID
Email sent to the root account is typically aliased to the
administrators of the system, who can take appropriate action.
The auditd service can be configured to send email to
a designated account in certain situations. Add or correct the following line
in /etc/audit/auditd.conf to ensure that administrators are notified
via email for those situations:
action_mail_acct = 
OL08-00-030020 auditd_data_retention_action_mail_acct
V-248725 139 medium The OL 8 Information System Security Officer (ISSO) and System Administrator (SA) (at a minimum) must have mail aliases to be notified of an audit processing failure. SRG-OS-ID
It is critical for the appropriate personnel to be aware if a system is at risk of failing to
process audit logs as required. Without this notification, the security personnel may be
unaware of an impending failure of the audit capability, and system operation may be adversely
affected.

Audit processing failures include software/hardware errors, failures in the audit capturing
mechanisms, and audit storage capacity being reached or exceeded.
Verify the administrators are notified in the event of an audit processing failure.
Check that the "/etc/aliases" file has a defined value for "root".
$ sudo grep "postmaster:\s*root$" /etc/aliases

postmaster: root
OL08-00-030030 postfix_client_configure_mail_alias_postmaster
V-248726 140 medium The OL 8 System must take appropriate action when an audit processing failure occurs. SRG-OS-ID
Taking appropriate action in case of disk errors will minimize the possibility of
losing audit records.
The auditd service can be configured to take an action
when there is a disk error.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting ACTION appropriately:
disk_error_action = ACTION
Set this value to single to cause the system to switch to single-user mode for corrective action. Acceptable values also include syslog, exec, single, and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. Details regarding all possible values for ACTION are described in the auditd.conf man page.
OL08-00-030040 auditd_data_disk_error_action
V-248728 140 medium The OL 8 audit system must take appropriate action when the audit storage volume is full. SRG-OS-ID
Taking appropriate action in case of a filled audit storage volume will minimize
the possibility of losing audit records.
The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting ACTION appropriately:
disk_full_action = ACTION
Set this value to single to cause the system to switch to single-user mode for corrective action. Acceptable values also include syslog, exec, single, and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. Details regarding all possible values for ACTION are described in the auditd.conf man page.
OL08-00-030060 auditd_data_disk_full_action
V-248729 366 medium The OL 8 audit system must audit local events. SRG-OS-ID
If option local_events isn't set to yes only events from
network will be aggregated.
To configure Audit daemon to include local events in Audit logs, set
local_events to yes in /etc/audit/auditd.conf.
This is the default setting.
OL08-00-030061 auditd_local_events
V-248730 1851 medium OL 8 must label all offloaded audit logs before sending them to the central log server. SRG-OS-ID
If option name_format is left at its default value of
none, audit events from different computers may be hard
to distinguish.
To configure Audit daemon to use value returned by gethostname
syscall as computer node name in the audit events,
set name_format to hostname
in /etc/audit/auditd.conf.
OL08-00-030062 auditd_name_format
V-248731 366 medium OL 8 must resolve audit information before writing to disk. SRG-OS-ID
If option log_format isn't set to ENRICHED, the
audit records will be stored in a format exactly as the kernel sends them.
To configure Audit daemon to resolve all uid, gid, syscall,
architecture, and socket address information before writing the
events to disk, set log_format to ENRICHED
in /etc/audit/auditd.conf.
OL08-00-030063 auditd_log_format
V-248732 164 medium OL 8 audit logs must have a mode of "0600" or less permissive to prevent unauthorized read access. SRG-OS-ID
If users can write to audit logs, audit trails can be modified or destroyed.
Determine where the audit logs are stored with the following command:
$ sudo grep -iw log_file /etc/audit/auditd.conf
log_file = /var/log/audit/audit.log
Configure the audit log to be protected from unauthorized read access by setting the correct permissive mode with the following command:
$ sudo chmod 0600 audit_log_file
By default, audit_log_file is "/var/log/audit/audit.log".
OL08-00-030070 file_permissions_var_log_audit
V-248733 164 medium OL 8 audit logs must be owned by root to prevent unauthorized read access. SRG-OS-ID
Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality.
All audit logs must be owned by root user. The path for audit log can be
configured via log_file parameter in 
/etc/audit/auditd.conf
or by default, the path for audit log is
/var/log/audit/
. To properly set the owner of /var/log/audit/*, run the command:
$ sudo chown root /var/log/audit/* 
OL08-00-030080 file_ownership_var_log_audit_stig
V-248734 164 medium OL 8 audit logs must be group-owned by root to prevent unauthorized read access. SRG-OS-ID
Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality.
All audit logs must be group owned by root user. The path for audit log can
be configured via log_file parameter in 
/etc/audit/auditd.conf
or, by default, the path for audit log is
/var/log/audit/
. To properly set the group owner of /var/log/audit/*, run the command:
$ sudo chgrp root /var/log/audit/*
OL08-00-030090 file_group_ownership_var_log_audit
V-248735 164 medium The OL 8 audit log directory must be owned by root to prevent unauthorized read access. SRG-OS-ID
Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality.
All audit directories must be owned by root user. By default, the path for audit log is 
/var/log/audit/
. To properly set the owner of /var/log/audit, run the command:
$ sudo chown root /var/log/audit 
OL08-00-030100 directory_ownership_var_log_audit
V-248736 164 medium The OL 8 audit log directory must be group-owned by root to prevent unauthorized read access. SRG-OS-ID
Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality.
All audit directories must be group owned by root user. By default, the path for audit log is 
/var/log/audit/
. To properly set the group owner of /var/log/audit, run the command:
$ sudo chgrp root /var/log/audit
OL08-00-030110 directory_group_ownership_var_log_audit
V-248737 164 medium The OL 8 audit log directory must have a mode of 0700 or less permissive to prevent unauthorized read access. SRG-OS-ID
If users can write to audit logs, audit trails can be modified or destroyed.
Verify the audit log directories have a mode of "0700" or less permissive by first determining
where the audit logs are stored with the following command:
$ sudo grep -iw log_file /etc/audit/auditd.conf

log_file = /var/log/audit/audit.log
Configure the audit log directory to be protected from unauthorized read access by setting the correct permissive mode with the following command:
$ sudo chmod 0700 audit_log_directory
By default, audit_log_directory is "/var/log/audit".
OL08-00-030120 directory_permissions_var_log_audit
V-248738 164 medium The OL 8 audit system must protect auditing rules from unauthorized change. SRG-OS-ID
Making the audit configuration immutable prevents accidental as
well as malicious modification of the audit rules, although it may be
problematic if legitimate changes are needed during system
operation.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d in order to make the auditd configuration
immutable:
-e 2
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file in order to make the auditd configuration immutable:
-e 2
With this setting, a reboot will be required to change any audit rules.
OL08-00-030121 audit_rules_immutable
V-248739 164 medium The OL 8 audit system must protect logon UIDs from unauthorized change. SRG-OS-ID
If modification of login UIDs is not prevented, they can be changed by unprivileged users and
make auditing complicated or impossible.
Configure kernel to prevent modification of login UIDs once they are set.
Changing login UIDs while this configuration is enforced requires special capabilities which
are not available to unprivileged users.

The following rules configure audit as described above:
## Make the loginuid immutable. This prevents tampering with the auid.
--loginuid-immutable    
Load new Audit rules into kernel by running:
augenrules --load
OL08-00-030122 audit_immutable_login_uids
V-248740 2884 medium OL 8 must generate audit records for all account creation events that affect "/etc/shadow". SRG-OS-ID
In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d, in order to capture events that modify
account changes:


-w /etc/shadow -p wa -k audit_rules_usergroup_modification


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:

-w /etc/shadow -p wa -k audit_rules_usergroup_modification
OL08-00-030130 audit_rules_usergroup_modification_shadow
V-248741 2884 medium OL 8 must generate audit records for all account creation events that affect "/etc/security/opasswd". SRG-OS-ID
In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d, in order to capture events that modify
account changes:


-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:

-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
OL08-00-030140 audit_rules_usergroup_modification_opasswd
V-248742 2884 medium OL 8 must generate audit records for all account creation events that affect "/etc/passwd". SRG-OS-ID
In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d, in order to capture events that modify
account changes:


-w /etc/passwd -p wa -k audit_rules_usergroup_modification


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:

-w /etc/passwd -p wa -k audit_rules_usergroup_modification
OL08-00-030150 audit_rules_usergroup_modification_passwd
V-248743 2884 medium OL 8 must generate audit records for all account creation events that affect "/etc/gshadow". SRG-OS-ID
In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d, in order to capture events that modify
account changes:


-w /etc/gshadow -p wa -k audit_rules_usergroup_modification


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:

-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
OL08-00-030160 audit_rules_usergroup_modification_gshadow
V-248744 2884 medium OL 8 must generate audit records for all account creation events that affect "/etc/group". SRG-OS-ID
In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.
If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d, in order to capture events that modify
account changes:


-w /etc/group -p wa -k audit_rules_usergroup_modification


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:

-w /etc/group -p wa -k audit_rules_usergroup_modification
OL08-00-030170 audit_rules_usergroup_modification_group
V-248745 2884 medium OL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers". SRG-OS-ID
The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.
Editing the sudoers file may be sign of an attacker trying to
establish persistent methods to a system, auditing the editing of the sudoers
files mitigates this risk.
At a minimum, the audit system should collect administrator actions
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the default),
add the following line to a file with suffix .rules in the directory
/etc/audit/rules.d:
-w /etc/sudoers -p wa -k actions
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-w /etc/sudoers -p wa -k actions
OL08-00-030171 audit_rules_sudoers
V-248746 2884 medium OL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/". SRG-OS-ID
The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.
Editing the sudoers file may be sign of an attacker trying to
establish persistent methods to a system, auditing the editing of the sudoers
files mitigates this risk.
At a minimum, the audit system should collect administrator actions
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the default),
add the following line to a file with suffix .rules in the directory
/etc/audit/rules.d:
-w /etc/sudoers.d/ -p wa -k actions
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-w /etc/sudoers.d/ -p wa -k actions
OL08-00-030172 audit_rules_sudoers_d
V-248519 2884 medium The OL 8 audit package must be installed. SRG-OS-ID
The auditd service is an access monitoring and accounting daemon, watching system calls to audit any access, in comparison with potential local access control policy such as SELinux policy.
The audit package should be installed.
OL08-00-030180 package_audit_installed
V-248520 2884 medium OL 8 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events. SRG-OS-ID
Without establishing what type of events occurred, it would be difficult
to establish, correlate, and investigate the events leading up to an outage or attack.
Ensuring the auditd service is active ensures audit records
generated by the kernel are appropriately recorded.


Additionally, a properly configured audit subsystem ensures that actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.
The auditd service is an essential userspace component of
the Linux Auditing System, as it is responsible for writing audit records to
disk.

The auditd service can be enabled with the following command:
$ sudo systemctl enable auditd.service
OL08-00-030181 service_auditd_enabled
V-248747 2884 medium OL 8 must generate audit records for any use of the "su" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030190 audit_rules_privileged_commands_su
V-248748 2884 medium The OL 8 audit system must be configured to audit any use of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls. SRG-OS-ID
The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.
At a minimum, the audit system should collect file permission
changes for all users and root.


If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod


If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod


If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b32 -S removexattr -F auid=0 -F key=perm_mod


If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b64 -S removexattr -F auid=0 -F key=perm_mod
OL08-00-030200 audit_rules_dac_modification_removexattr
V-248753 2884 medium OL 8 must generate audit records for any use of the "chage" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030250 audit_rules_privileged_commands_chage
V-248754 2884 medium OL 8 must generate audit records for any uses of the "chcon" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect any execution attempt
of the chcon command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030260 audit_rules_execution_chcon
V-248755 2884 medium The OL 8 audit system must be configured to audit any use of the "setxattr" system call. SRG-OS-ID
The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.
At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b32 -S setxattr -F auid=0 -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=unset -F key=perm_mod
-a always,exit -F arch=b64 -S setxattr -F auid=0 -F key=perm_mod
OL08-00-030270 audit_rules_dac_modification_setxattr
V-248756 2884 medium OL 8 must generate audit records for any use of the "ssh-agent" command. SRG-OS-ID
Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.

Audit records can be generated from various components within the
information system (e.g., module or policy filter).
At a minimum, the audit system should collect any execution attempt
of the ssh-agent command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh-agent
OL08-00-030280 audit_rules_privileged_commands_ssh_agent
V-248757 2884 medium OL 8 must generate audit records for any use of the "passwd" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030290 audit_rules_privileged_commands_passwd
V-248758 2884 medium OL 8 must generate audit records for any use of the "mount" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030300 audit_rules_privileged_commands_mount
V-248759 2884 medium OL 8 must generate audit records for any use of the "umount" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030301 audit_rules_privileged_commands_umount
V-248760 2884 medium OL 8 must generate audit records for any use of the "mount" syscall. SRG-OS-ID
The unauthorized exportation of data to external media could result in an information leak
where classified information, Privacy Act information, and intellectual property could be lost. An audit
trail should be created each time a filesystem is mounted to help identify and guard against information
loss.
At a minimum, the audit system should collect media exportation
events for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=export
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=unset -F key=export
OL08-00-030302 audit_rules_media_export
V-248761 2884 medium OL 8 must generate audit records for any use of the "unix_update" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030310 audit_rules_privileged_commands_unix_update
V-248762 2884 medium OL 8 must generate audit records for any use of the "postdrop" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030311 audit_rules_privileged_commands_postdrop
V-248763 2884 medium OL 8 must generate audit records for any use of the "postqueue" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030312 audit_rules_privileged_commands_postqueue
V-248764 169 medium OL 8 must generate audit records for any use of the "semanage" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect any execution attempt
of the semanage command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030313 audit_rules_execution_semanage
V-248765 169 medium OL 8 must generate audit records for any use of the "setfiles" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect any execution attempt
of the setfiles command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030314 audit_rules_execution_setfiles
V-248766 169 medium OL 8 must generate audit records for any use of the "userhelper" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030315 audit_rules_privileged_commands_userhelper
V-248767 2884 medium OL 8 must generate audit records for any use of the "setsebool" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect any execution attempt
of the setsebool command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030316 audit_rules_execution_setsebool
V-248768 2884 medium OL 8 must generate audit records for any use of the "unix_chkpwd" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030317 audit_rules_privileged_commands_unix_chkpwd
V-248769 2884 medium OL 8 must generate audit records for any use of the "ssh-keysign" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030320 audit_rules_privileged_commands_ssh_keysign
V-248770 2884 medium OL 8 must generate audit records for any use of the "setfacl" command. SRG-OS-ID
Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter).
At a minimum, the audit system should collect any execution attempt
of the setfacl command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030330 audit_rules_execution_setfacl
V-248771 2884 medium OL 8 must generate audit records for any use of the "pam_timestamp_check" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/pam_timestamp_check
-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/pam_timestamp_check
-F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030340 audit_rules_privileged_commands_pam_timestamp_check
V-248772 2884 medium OL 8 must generate audit records for any use of the "newgrp" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030350 audit_rules_privileged_commands_newgrp
V-248773 2884 medium OL 8 must generate audit records for any use of the "init_module" and "finit_module" system calls. SRG-OS-ID
The addition of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel.
To capture kernel module loading events, use following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:

-a always,exit -F arch=ARCH -S init_module -F auid>=1000 -F auid!=unset -F key=modules
Place to add the line depends on a way auditd daemon is configured. If it is configured to use the augenrules program (the default), add the line to a file with suffix .rules in the directory /etc/audit/rules.d. If the auditd daemon is configured to use the auditctl utility, add the line to file /etc/audit/audit.rules.
OL08-00-030360 audit_rules_kernel_module_loading_init
V-248774 2884 medium OL 8 must generate audit records for any use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls. SRG-OS-ID
Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence.
At a minimum, the audit system should collect file deletion events
for all users and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following line to a file with suffix .rules in the
directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S unlinkat -F auid>=1000 -F auid!=unset -F key=delete
OL08-00-030361 audit_rules_file_deletion_events_unlinkat
V-248779 2884 medium OL 8 must generate audit records for any use of the "gpasswd" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030370 audit_rules_privileged_commands_gpasswd
V-248781 2884 medium OL 8 must generate audit records for any use of the delete_module syscall. SRG-OS-ID
The removal of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel.
To capture kernel module unloading events, use following line, setting ARCH to
either b32 for 32-bit system, or having two lines for both b32 and b64 in case your system is 64-bit:

-a always,exit -F arch=ARCH -S delete_module -F auid>=1000 -F auid!=unset -F key=modules
Place to add the line depends on a way auditd daemon is configured. If it is configured to use the augenrules program (the default), add the line to a file with suffix .rules in the directory /etc/audit/rules.d. If the auditd daemon is configured to use the auditctl utility, add the line to file /etc/audit/audit.rules.
OL08-00-030390 audit_rules_kernel_module_loading_delete
V-248782 2884 medium OL 8 must generate audit records for any use of the "crontab" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030400 audit_rules_privileged_commands_crontab
V-248783 2884 medium OL 8 must generate audit records for any use of the "chsh" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030410 audit_rules_privileged_commands_chsh
V-248784 2884 medium OL 8 must generate audit records for any use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls. SRG-OS-ID
Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise.
At a minimum, the audit system should collect unauthorized file
accesses for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access
-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access
If the system is 64 bit then also add the following lines:
-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access
-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access
-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access
If the system is 64 bit then also add the following lines:
-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -F key=access
-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -F key=access
OL08-00-030420 audit_rules_unsuccessful_file_modification_truncate
V-248790 2884 medium OL 8 must generate audit records for any use of the "chown", "fchown", "fchownat", and "lchown" system calls. SRG-OS-ID
The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.
At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured
to use the augenrules program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=unset -F key=perm_mod
OL08-00-030480 audit_rules_dac_modification_lchown
V-248791 2884 medium OL 8 must generate audit records for any use of the "chmod", "fchmod", and "fchmodat" system calls. SRG-OS-ID
The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.
At a minimum, the audit system should collect file permission
changes for all users and root. If the auditd daemon is configured to
use the augenrules program to read audit rules during daemon startup
(the default), add the following line to a file with suffix .rules in
the directory /etc/audit/rules.d:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod
OL08-00-030490 audit_rules_dac_modification_fchmodat
V-248797 2884 medium OL 8 must generate audit records for any use of the "sudo" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030550 audit_rules_privileged_commands_sudo
V-248798 2884 medium OL 8 must generate audit records for any use of the "usermod" command. SRG-OS-ID
Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations.
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threats.


Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030560 audit_rules_privileged_commands_usermod
V-248799 2884 medium OL 8 must generate audit records for any use of the "chacl" command. SRG-OS-ID
Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
Audit records can be generated from various components within the
information system (e.g., module or policy filter).
At a minimum, the audit system should collect any execution attempt
of the chacl command for all users and root. If the auditd
daemon is configured to use the augenrules program to read audit rules
during daemon startup (the default), add the following lines to a file with suffix
.rules in the directory /etc/audit/rules.d:
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -F key=privileged
OL08-00-030570 audit_rules_execution_chacl
V-248800 2884 medium OL 8 must generate audit records for any use of the "kmod" command. SRG-OS-ID
Without generating audit records that are specific to the security and
mission needs of the organization, it would be difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.

Audit records can be generated from various components within the
information system (e.g., module or policy filter).
At a minimum, the audit system should collect the execution of
privileged commands for all users and root. If the auditd daemon is
configured to use the augenrules program to read audit rules during
daemon startup (the default), add a line of the following form to a file with
suffix .rules in the directory /etc/audit/rules.d:
-w /usr/bin/kmod -p x -k modules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules:
-w /usr/bin/kmod -p x -k modules
OL08-00-030580 audit_rules_privileged_commands_kmod
V-248801 2884 medium OL 8 must generate audit records for any attempted modifications to the "faillock" log file. SRG-OS-ID
Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion.
The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d in order to watch for attempted manual
edits of files involved in storing logon events:
-w /var/log/faillock -p wa -k logins
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for unattempted manual edits of files involved in storing logon events:
-w /var/log/faillock -p wa -k logins
OL08-00-030590 audit_rules_login_events_faillock
V-248802 2884 medium OL 8 must generate audit records for any attempted modifications to the "lastlog" file. SRG-OS-ID
Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion.
The audit system already collects login information for all users
and root. If the auditd daemon is configured to use the
augenrules program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix .rules in the
directory /etc/audit/rules.d in order to watch for attempted manual
edits of files involved in storing logon events:
-w /var/log/lastlog -p wa -k logins
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for unattempted manual edits of files involved in storing logon events:
-w /var/log/lastlog -p wa -k logins
OL08-00-030600 audit_rules_login_events_lastlog
V-248803 2884 medium OL 8 must enable auditing of processes that start prior to the audit daemon. SRG-OS-ID
Each process on the system carries an "auditable" flag which indicates whether
its activities can be audited. Although auditd takes care of enabling
this for all processes which launch after it does, adding the kernel argument
ensures it is set for every process during boot.
To ensure all processes can be audited, even those which start
prior to the audit daemon, add the argument audit=1 to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit=1 is added as a kernel command line
argument to newly installed kernels, add audit=1 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit=1 ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="audit=1"
OL08-00-030601 grub2_audit_argument
V-248804 2884 low OL 8 must allocate an "audit_backlog_limit" of sufficient size to capture processes that start prior to the audit daemon. SRG-OS-ID
audit_backlog_limit sets the queue length for audit events awaiting transfer
to the audit daemon. Until the audit daemon is up and running, all log messages
are stored in this queue.  If the queue is overrun during boot process, the action
defined by audit failure flag is taken.
To improve the kernel capacity to queue all log events, even those which occurred
prior to the audit daemon, add the argument audit_backlog_limit=8192 to the default
GRUB 2 command line for the Linux operating system.
To ensure that audit_backlog_limit=8192 is added as a kernel command line
argument to newly installed kernels, add audit_backlog_limit=8192 to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... audit_backlog_limit=8192 ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="audit_backlog_limit=8192"
OL08-00-030602 grub2_audit_backlog_limit_argument
V-248805 172 medium OL 8 must enable Linux audit logging for the USBGuard daemon. SRG-OS-ID
Using the Linux Audit logging allows for centralized trace
of events.
To configure USBGuard daemon to log via Linux Audit
(as opposed directly to a file),
AuditBackend option in /etc/usbguard/usbguard-daemon.conf
needs to be set to LinuxAudit.
OL08-00-030603 configure_usbguard_auditbackend
V-248806 171 medium OL 8 must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. SRG-OS-ID
Without the capability to restrict the roles and individuals that can select which events
are audited, unauthorized personnel may be able to prevent the auditing of critical
events. Misconfigured audits may degrade the system's performance by overwhelming
the audit log. Misconfigured audits may also make it more difficult to establish,
correlate, and investigate the events relating to an incident or identify
those responsible for one.
To properly set the permissions of /etc/audit/rules.d/*.rules, run the command:
$ sudo chmod 0640 /etc/audit/rules.d/*.rules
OL08-00-030610 file_permissions_etc_audit_rulesd
V-248807 1493 medium OL 8 audit tools must have a mode of "0755" or less permissive. SRG-OS-ID
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data.
Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit information.
Oracle Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.

Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Audit tools must have a mode of 0755 or less permissive.
OL08-00-030620 file_audit_tools_permissions
V-248808 1495 medium OL 8 audit tools must be owned by root. SRG-OS-ID
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data.
Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit information.
Oracle Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.

Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Audit tools must have the correct owner.
OL08-00-030630 file_audit_tools_ownership
V-248809 1495 medium OL 8 audit tools must be group-owned by root. SRG-OS-ID
Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data.
Therefore, protecting audit tools is necessary to prevent unauthorized operations on audit information.
Oracle Linux 8 systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools, and the corresponding rights the user enjoys, to make access decisions regarding the access to audit tools.

Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Audit tools must have the correct group owner.
OL08-00-030640 file_audit_tools_group_ownership
V-248810 1496 medium OL 8 must use cryptographic mechanisms to protect the integrity of audit tools. SRG-OS-ID
Protecting the integrity of the tools used for auditing purposes is a
critical step toward ensuring the integrity of audit information. Audit
information includes all information (e.g., audit records, audit settings,
and audit reports) needed to successfully audit information system
activity.

Audit tools include but are not limited to vendor-provided and open-source
audit tools needed to successfully view and manipulate audit information
system activity and records. Audit tools include custom queries and report
generators.

It is not uncommon for attackers to replace the audit tools or inject code
into the existing tools to provide the capability to hide or erase system
activity from the audit logs.

To address this risk, audit tools must be cryptographically signed to
provide the capability to identify when the audit tools have been modified,
manipulated, or replaced. An example is a checksum hash of the file or
files.
The operating system file integrity tool must be configured to protect the integrity of the audit tools.
OL08-00-030650 aide_check_audit_tools
V-248811 1849 medium OL 8 must allocate audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. SRG-OS-ID
Information stored in one location is vulnerable to accidental or incidental
deletion or alteration. Off-loading is a common process in information
systems with limited audit storage capacity.
The Oracle Linux 8 operating system must allocate audit record storage
capacity to store at least one weeks worth of audit records when audit
records are not immediately sent to a central audit record storage
facility.

The partition size needed to capture a week's worth of audit records is
based on the activity level of the system and the total storage capacity
available. In normal circumstances, 10.0 GB of storage space for audit
records will be sufficient.

Determine which partition the audit records are being written to with the
following command:

$ sudo grep log_file /etc/audit/auditd.conf
log_file = /var/log/audit/audit.log
Check the size of the partition that audit records are written to with the following command:
$ sudo df -h /var/log/audit/
/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit
OL08-00-030660 auditd_audispd_configure_sufficiently_large_partition
V-248812 366 medium OL 8 must have the packages required for offloading audit logs installed. SRG-OS-ID
The rsyslog package provides the rsyslog daemon, which provides
system logging services.
Rsyslog is installed by default. The rsyslog package can be installed with the following command: 
 $ sudo yum install rsyslog
OL08-00-030670 package_rsyslog_installed
V-248813 366 medium OL 8 must have the packages required for encrypting offloaded audit logs installed. SRG-OS-ID
The rsyslog-gnutls package provides Transport Layer Security (TLS) support
for the rsyslog daemon, which enables secure remote logging.
TLS protocol support for rsyslog is installed.
The rsyslog-gnutls package can be installed with the following command:
$ sudo yum install rsyslog-gnutls
OL08-00-030680 package_rsyslog-gnutls_installed
V-248814 1851 medium The OL 8 audit records must be offloaded onto a different system or storage media from the system being audited. SRG-OS-ID
A log server (loghost) receives syslog messages from one or more
systems. This data can be used as an additional log source in the event a
system is compromised and its local logs are suspect. Forwarding log messages
to a remote loghost also provides system administrators with a centralized
place to view the status of multiple hosts within the enterprise.
To configure rsyslog to send logs to a remote log server,
open /etc/rsyslog.conf and read and understand the last section of the file,
which describes the multiple directives necessary to activate remote
logging.
Along with these other directives, the system can be configured
to forward its logs to a particular log server by
adding or correcting one of the following lines,
substituting  appropriately.
The choice of protocol depends on the environment of the system;
although TCP and RELP provide more reliable message delivery,
they may not be supported in all environments.

To use UDP for log message delivery:
*.* @

To use TCP for log message delivery:
*.* @@

To use RELP for log message delivery:
*.* :omrelp:

There must be a resolvable DNS CNAME or Alias record set to "" for logs to be sent correctly to the centralized logging utility.
OL08-00-030690 rsyslog_remote_loghost
V-248815 1851 medium OL 8 must take appropriate action when the internal event queue is full. SRG-OS-ID
The audit system should have an action setup in the event the internal event queue becomes full
so that no data is lost.
The audit system should have an action setup in the event the internal event queue becomes full.
To setup an overflow action edit /etc/audit/auditd.conf. Set overflow_action
to one of the following values: syslog, single, halt.
OL08-00-030700 auditd_overflow_action
V-248816 1851 medium OL 8 must encrypt the transfer of audit records offloaded onto a different system or media from the system being audited. SRG-OS-ID
The audit records generated by Rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Audit records should be
protected from unauthorized access.
Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging.  Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.

When using rsyslogd to off-load logs off an encryption system must be used.
OL08-00-030710 rsyslog_encrypt_offload_defaultnetstreamdriver
V-248817 1851 medium OL 8 must authenticate the remote logging server for offloading audit logs. SRG-OS-ID
The audit records generated by Rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Audit records should be
protected from unauthorized access.
Rsyslogd is a system utility providing support for message logging. Support
for both internet and UNIX domain sockets enables this utility to support both local
and remote logging.  Couple this utility with gnutls (which is a secure communications
library implementing the SSL, TLS and DTLS protocols), and you have a method to securely
encrypt and off-load auditing.

When using rsyslogd to off-load logs the remote system must be authenticated.
OL08-00-030720 rsyslog_encrypt_offload_actionsendstreamdriverauthmode
V-248818 1855 medium OL 8 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. SRG-OS-ID
Notifying administrators of an impending disk space problem may allow them to
take corrective action prior to any disruption.
The auditd service can be configured to take an action
when disk space is running low but prior to running out of space completely.
Edit the file /etc/audit/auditd.conf. Add or modify the following line,
substituting PERCENTAGE appropriately:
space_left = PERCENTAGE%
Set this value to at least 25 to cause the system to notify the user of an issue.
OL08-00-030730 auditd_data_retention_space_left_percentage
V-248819 1855 medium OL 8 must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated audit record storage volume 75 percent utilization. SRG-OS-ID
Notifying administrators of an impending disk space problem may
allow them to take corrective action prior to any disruption.
The auditd service can be configured to take an action
when disk space starts to run low.
Edit the file /etc/audit/auditd.conf. Modify the following line,
substituting ACTION appropriately:
space_left_action = ACTION
Possible values for ACTION are described in the auditd.conf man page. These include:
  • syslog
  • email
  • exec
  • suspend
  • single
  • halt
Set this to email (instead of the default, which is suspend) as it is more likely to get prompt attention. Acceptable values also include suspend, single, and halt.
OL08-00-030731 auditd_data_retention_space_left_action
V-248820 2046 medium OL 8 must compare internal information system clocks at least every 24 hours with a server synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). SRG-OS-ID
Depending on the infrastruture being used the pool directive may not be supported.
Check that Chrony only has time sources configured with the server directive.
OL08-00-030740 chronyd_server_directive
V-248821 381 low OL 8 must disable the chrony daemon from acting as a server. SRG-OS-ID
Minimizing the exposure of the server functionality of the chrony
daemon diminishes the attack surface.
The port option in /etc/chrony.conf can be set to
0 to make chrony daemon to never open any listening port
for server operation and to operate strictly in a client-only mode.
OL08-00-030741 chronyd_client_only
V-248822 381 low OL 8 must disable network management of the chrony daemon. SRG-OS-ID
Not exposing the management interface of the chrony daemon on
the network diminishes the attack space.
The cmdport option in /etc/chrony.conf can be set to
0 to stop chrony daemon from listening on the UDP port 323
for management connections made by chronyc.
OL08-00-030742 chronyd_no_chronyc_network
V-248823 381 high OL 8 must not have the telnet-server package installed. SRG-OS-ID
It is detrimental for operating systems to provide, or install by default,
functionality exceeding requirements or mission objectives. These
unnecessary capabilities are often overlooked and therefore may remain
unsecure. They increase the risk to the platform by providing additional
attack vectors.

The telnet service provides an unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to login using this service, the privileged user password could be compromised.
Removing the telnet-server package decreases the risk of the telnet service's accidental (or intentional) activation.
The telnet-server package can be removed with the following command:
$ sudo yum erase telnet-server
OL08-00-040000 package_telnet-server_removed
V-248824 381 medium OL 8 must not have any automated bug reporting tools installed. SRG-OS-ID
Mishandling crash data could expose sensitive information about
vulnerabilities in software executing on the system, as well as sensitive
information from within a process's address space or registers.
The Automatic Bug Reporting Tool (abrt) collects
and reports crash data when an application crash is detected. Using a variety
of plugins, abrt can email crash reports to system administrators, log crash
reports to files, or forward crash reports to a centralized issue tracking
system such as RHTSupport.
The abrt package can be removed with the following command:
$ sudo yum erase abrt
OL08-00-040001 package_abrt_removed
V-248825 381 medium OL 8 must not have the sendmail package installed. SRG-OS-ID
The sendmail software was not developed with security in mind and
its design prevents it from being effectively contained by SELinux.  Postfix
should be used instead.
Sendmail is not the default mail transfer agent and is
not installed by default.
The sendmail package can be removed with the following command:
$ sudo yum erase sendmail
OL08-00-040002 package_sendmail_removed
V-248826 381 low OL 8 must enable mitigations against processor-based vulnerabilities. SRG-OS-ID
Kernel page-table isolation is a kernel feature that mitigates
the Meltdown security vulnerability and hardens the kernel
against attempts to bypass kernel address space layout
randomization (KASLR).
To enable Kernel page-table isolation,
add the argument pti=on to the default
GRUB 2 command line for the Linux operating system.
To ensure that pti=on is added as a kernel command line
argument to newly installed kernels, add pti=on to the
default Grub2 command line for Linux operating systems. Modify the line within
/etc/default/grub as shown below:
GRUB_CMDLINE_LINUX="... pti=on ..."
Run the following command to update command line for already installed kernels:
# grubby --update-kernel=ALL --args="pti=on"
OL08-00-040004 grub2_pti_argument
V-248827 381 high OL 8 must not have the rsh-server package installed. SRG-OS-ID
The rsh-server service provides unencrypted remote access service which does not
provide for the confidentiality and integrity of user passwords or the remote session and has very weak
authentication. If a privileged user were to login using this service, the privileged user password
could be compromised. The rsh-server package provides several obsolete and insecure
network services. Removing it decreases the risk of those services' accidental (or intentional)
activation.
The rsh-server package can be removed with the following command:
$ sudo yum erase rsh-server
OL08-00-040010 package_rsh-server_removed
V-248828 medium OL 8 must cover or disable the built-in or attached camera when not in use. SRG-OS-ID
OL08-00-040020 Missing Rule
V-248829 366 medium OL 8 must not have the asynchronous transfer mode (ATM) kernel module installed if not required for operational support. SRG-OS-ID
Disabling ATM protects the system against exploitation of any
flaws in its implementation.
The Asynchronous Transfer Mode (ATM) is a protocol operating on
network, data link, and physical layers, based on virtual circuits
and virtual paths.

To configure the system to prevent the atm
kernel module from being loaded, add the following line to the file /etc/modprobe.d/atm.conf:
install atm /bin/true
To configure the system to prevent the atm from being used, add the following line to file /etc/modprobe.d/atm.conf:
blacklist atm
OL08-00-040021 kernel_module_atm_disabled
V-248830 366 medium OL 8 must not have the Controller Area Network (CAN) kernel module installed if not required for operational support. SRG-OS-ID
Disabling CAN protects the system against exploitation of any
flaws in its implementation.
The Controller Area Network (CAN) is a serial communications
protocol which was initially developed for automotive and
is now also used in marine, industrial, and medical applications.

To configure the system to prevent the can
kernel module from being loaded, add the following line to the file /etc/modprobe.d/can.conf:
install can /bin/true
To configure the system to prevent the can from being used, add the following line to file /etc/modprobe.d/can.conf:
blacklist can
OL08-00-040022 kernel_module_can_disabled
V-248831 366 medium OL 8 must not have the stream control transmission protocol (SCTP) kernel module installed if not required for operational support. SRG-OS-ID
Disabling SCTP protects
the system against exploitation of any flaws in its implementation.
The Stream Control Transmission Protocol (SCTP) is a
transport layer protocol, designed to support the idea of
message-oriented communication, with several streams of messages
within one connection.

To configure the system to prevent the sctp
kernel module from being loaded, add the following line to the file /etc/modprobe.d/sctp.conf:
install sctp /bin/true
To configure the system to prevent the sctp from being used, add the following line to file /etc/modprobe.d/sctp.conf:
blacklist sctp
OL08-00-040023 kernel_module_sctp_disabled
V-248832 381 low OL 8 must disable the transparent inter-process communication (TIPC) protocol. SRG-OS-ID
Disabling TIPC protects
the system against exploitation of any flaws in its implementation.
The Transparent Inter-Process Communication (TIPC) protocol
is designed to provide communications between nodes in a
cluster.

To configure the system to prevent the tipc
kernel module from being loaded, add the following line to the file /etc/modprobe.d/tipc.conf:
install tipc /bin/true
To configure the system to prevent the tipc from being used, add the following line to file /etc/modprobe.d/tipc.conf:
blacklist tipc
OL08-00-040024 kernel_module_tipc_disabled
V-248833 381 low OL 8 must disable mounting of cramfs. SRG-OS-ID
Removing support for unneeded filesystem types reduces the local attack surface
of the server.
To configure the system to prevent the cramfs
kernel module from being loaded, add the following line to the file /etc/modprobe.d/cramfs.conf:
install cramfs /bin/true
To configure the system to prevent the cramfs from being used, add the following line to file /etc/modprobe.d/cramfs.conf:
blacklist cramfs
This effectively prevents usage of this uncommon filesystem. The cramfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A cramfs image can be used without having to first decompress the image.
OL08-00-040025 kernel_module_cramfs_disabled
V-248834 381 low OL 8 must disable IEEE 1394 (FireWire) Support. SRG-OS-ID
Disabling FireWire protects the system against exploitation of any
flaws in its implementation.
The IEEE 1394 (FireWire) is a serial bus standard for
high-speed real-time communication.

To configure the system to prevent the firewire-core
kernel module from being loaded, add the following line to the file /etc/modprobe.d/firewire-core.conf:
install firewire-core /bin/true
To configure the system to prevent the firewire-core from being used, add the following line to file /etc/modprobe.d/firewire-core.conf:
blacklist firewire-core
OL08-00-040026 kernel_module_firewire-core_disabled
V-248835 382 medium OL 8 must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments. SRG-OS-ID
In order to prevent unauthorized connection of devices, unauthorized transfer of information,
or unauthorized tunneling (i.e., embedding of data types within data types), organizations must
disable or restrict unused or unnecessary physical and logical ports/protocols on information
systems.


Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by one component.

To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business.
Configure the firewalld ports to allow approved services to have access to the system.
To configure firewalld to open ports, run the following command:
firewall-cmd --permanent --add-port=port_number/tcp
To configure firewalld to allow access for pre-defined services, run the following command:
firewall-cmd --permanent --add-service=service_name
OL08-00-040030 configure_firewalld_ports
V-248836 778 medium The OL 8 file system automounter must be disabled unless required. SRG-OS-ID
Disabling the automounter permits the administrator to
statically control filesystem mounting through /etc/fstab.


Additionally, automatically mounting filesystems permits easy introduction of unknown devices, thereby facilitating malicious activity.
The autofs daemon mounts and unmounts filesystems, such as user
home directories shared via NFS, on demand. In addition, autofs can be used to handle
removable media, and the default configuration provides the cdrom device as /misc/cd.
However, this method of providing access to removable media is not common, so autofs
can almost always be disabled if NFS is not in use. Even if NFS is required, it may be
possible to configure filesystem mounts statically by editing /etc/fstab
rather than relying on the automounter.


The autofs service can be disabled with the following command:
$ sudo systemctl mask --now autofs.service
OL08-00-040070 service_autofs_disabled
V-248837 778 medium OL 8 must be configured to disable the ability to use USB mass storage devices. SRG-OS-ID
USB storage devices such as thumb drives can be used to introduce
malicious software.
To prevent USB storage devices from being used, configure the kernel module loading system
to prevent automatic loading of the USB storage driver.

To configure the system to prevent the usb-storage
kernel module from being loaded, add the following line to the file /etc/modprobe.d/usb-storage.conf:
install usb-storage /bin/true
To configure the system to prevent the usb-storage from being used, add the following line to file /etc/modprobe.d/usb-storage.conf:
blacklist usb-storage
This will prevent the modprobe program from loading the usb-storage module, but will not prevent an administrator (or another program) from using the insmod program to load the module manually.
OL08-00-040080 kernel_module_usb-storage_disabled
V-248839 medium An OL 8 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems. SRG-OS-ID
OL08-00-040090 Missing Rule
V-248840 2314 medium A firewall must be installed on OL 8. SRG-OS-ID
"Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.

Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.

Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.

Oracle Linux 8 functionality (e.g., SSH) must be capable of taking enforcement action if the audit reveals unauthorized activity.
Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets)."
The firewalld package can be installed with the following command:
$ sudo yum install firewalld
OL08-00-040100 package_firewalld_installed
V-248841 2314 medium A firewall must be active on OL 8. SRG-OS-ID
Access control methods provide the ability to enhance system security posture
by restricting services and known good IP addresses and address ranges. This
prevents connections from unknown hosts and protocols.
The firewalld service can be enabled with the following command:
$ sudo systemctl enable firewalld.service
OL08-00-040101 service_firewalld_enabled
V-248842 2418 medium OL 8 wireless network adapters must be disabled. SRG-OS-ID
The use of wireless networking can introduce many different attack vectors into
the organization's network. Common attack vectors such as malicious association
and ad hoc networks will allow an attacker to spoof a wireless access point
(AP), allowing validated systems to connect to the malicious AP and enabling the
attacker to monitor and record network traffic. These malicious APs can also
serve to create a man-in-the-middle attack or be used to create a denial of
service to valid network resources.
Deactivating wireless network interfaces should prevent normal usage of the wireless
capability.


Configure the system to disable all wireless network interfaces with the following command:
$ sudo nmcli radio all off
OL08-00-040110 wireless_disable_interfaces
V-248843 2418 medium OL 8 Bluetooth must be disabled. SRG-OS-ID
If Bluetooth functionality must be disabled, preventing the kernel
from loading the kernel module provides an additional safeguard against its
activation.
The kernel's module loading system can be configured to prevent
loading of the Bluetooth module. Add the following to
the appropriate /etc/modprobe.d configuration file
to prevent the loading of the Bluetooth module:
install bluetooth /bin/true
OL08-00-040111 kernel_module_bluetooth_disabled
V-248844 1764 medium OL 8 must mount "/dev/shm" with the "nodev" option. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails.
The nodev mount option can be used to prevent creation of device
files in /dev/shm. Legitimate character and block devices should
not exist within temporary directories like /dev/shm.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm.
OL08-00-040120 mount_option_dev_shm_nodev
V-248845 1764 medium OL 8 must mount "/dev/shm" with the "nosuid" option. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions.
The nosuid mount option can be used to prevent execution
of setuid programs in /dev/shm.  The SUID and SGID permissions should not
be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm.
OL08-00-040121 mount_option_dev_shm_nosuid
V-248846 1764 medium OL 8 must mount "/dev/shm" with the "noexec" option. SRG-OS-ID
Allowing users to execute binaries from world-writable directories
such as /dev/shm can expose the system to potential compromise.
The noexec mount option can be used to prevent binaries
from being executed out of /dev/shm.
It can be dangerous to allow the execution of binaries
from world-writable temporary storage directories such as /dev/shm.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/dev/shm.
OL08-00-040122 mount_option_dev_shm_noexec
V-248847 1764 medium OL 8 must mount "/tmp" with the "nodev" option. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails.
The nodev mount option can be used to prevent device files from
being created in /tmp. Legitimate character and block devices
should not exist within temporary directories like /tmp.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp.
OL08-00-040123 mount_option_tmp_nodev
V-248848 1764 medium OL 8 must mount "/tmp" with the "nosuid" option. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions.
The nosuid mount option can be used to prevent
execution of setuid programs in /tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp.
OL08-00-040124 mount_option_tmp_nosuid
V-248849 1764 medium OL 8 must mount "/tmp" with the "noexec" option. SRG-OS-ID
Allowing users to execute binaries from world-writable directories
such as /tmp should never be necessary in normal operation and
can expose the system to potential compromise.
The noexec mount option can be used to prevent binaries
from being executed out of /tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/tmp.
OL08-00-040125 mount_option_tmp_noexec
V-248850 1764 medium OL 8 must mount "/var/log" with the "nodev" option. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails.
The nodev mount option can be used to prevent device files from
being created in /var/log.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log.
OL08-00-040126 mount_option_var_log_nodev
V-248851 1764 medium OL 8 must mount "/var/log" with the "nosuid" option. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from partitions
designated for log files.
The nosuid mount option can be used to prevent
execution of setuid programs in /var/log. The SUID and SGID permissions
should not be required in directories containing log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log.
OL08-00-040127 mount_option_var_log_nosuid
V-248852 1764 medium OL 8 must mount "/var/log" with the "noexec" option. SRG-OS-ID
Allowing users to execute binaries from directories containing log files
such as /var/log should never be necessary in normal operation and
can expose the system to potential compromise.
The noexec mount option can be used to prevent binaries
from being executed out of /var/log.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log.
OL08-00-040128 mount_option_var_log_noexec
V-248853 1764 medium OL 8 must mount "/var/log/audit" with the "nodev" option. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails.
The nodev mount option can be used to prevent device files from
being created in /var/log/audit.
Legitimate character and block devices should exist only in
the /dev directory on the root partition or within chroot
jails built for system services.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit.
OL08-00-040129 mount_option_var_log_audit_nodev
V-248854 1764 medium OL 8 must mount "/var/log/audit" with the "nosuid" option. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from partitions
designated for audit log files.
The nosuid mount option can be used to prevent
execution of setuid programs in /var/log/audit. The SUID and SGID permissions
should not be required in directories containing audit log files.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit.
OL08-00-040130 mount_option_var_log_audit_nosuid
V-248855 1764 medium OL 8 must mount "/var/log/audit" with the "noexec" option. SRG-OS-ID
Allowing users to execute binaries from directories containing audit log files
such as /var/log/audit should never be necessary in normal operation and
can expose the system to potential compromise.
The noexec mount option can be used to prevent binaries
from being executed out of /var/log/audit.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/log/audit.
OL08-00-040131 mount_option_var_log_audit_noexec
V-248856 1764 medium OL 8 must mount "/var/tmp" with the "nodev" option. SRG-OS-ID
The only legitimate location for device files is the /dev directory
located on the root partition. The only exception to this is chroot jails.
The nodev mount option can be used to prevent device files from
being created in /var/tmp. Legitimate character and block devices
should not exist within temporary directories like /var/tmp.
Add the nodev option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp.
OL08-00-040132 mount_option_var_tmp_nodev
V-248857 1764 medium OL 8 must mount "/var/tmp" with the "nosuid" option. SRG-OS-ID
The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions.
The nosuid mount option can be used to prevent
execution of setuid programs in /var/tmp. The SUID and SGID permissions
should not be required in these world-writable directories.
Add the nosuid option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp.
OL08-00-040133 mount_option_var_tmp_nosuid
V-248858 1764 medium OL 8 must mount "/var/tmp" with the "noexec" option. SRG-OS-ID
Allowing users to execute binaries from world-writable directories
such as /var/tmp should never be necessary in normal operation and
can expose the system to potential compromise.
The noexec mount option can be used to prevent binaries
from being executed out of /var/tmp.
Add the noexec option to the fourth column of
/etc/fstab for the line which controls mounting of
/var/tmp.
OL08-00-040134 mount_option_var_tmp_noexec
V-248859 1774 medium The OL 8 "fapolicy" module must be installed. SRG-OS-ID
fapolicyd (File Access Policy Daemon)
implements application whitelisting to decide file access rights.
The fapolicyd package can be installed with the following command:
$ sudo yum install fapolicyd
OL08-00-040135 package_fapolicyd_installed
V-248860 1774 medium The OL 8 "fapolicy" module must be enabled. SRG-OS-ID
The fapolicyd service (File Access Policy Daemon)
implements application whitelisting to decide file access rights.
The File Access Policy service should be enabled.

The fapolicyd service can be enabled with the following command:
$ sudo systemctl enable fapolicyd.service
OL08-00-040136 service_fapolicyd_enabled
V-248861 medium The OL 8 fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. SRG-OS-ID
OL08-00-040137 Missing Rule
V-248862 1958 medium OL 8 must have the USBGuard installed. SRG-OS-ID
usbguard is a software framework that helps to protect
against rogue USB devices by implementing basic whitelisting/blacklisting
capabilities based on USB device attributes.
The usbguard package can be installed with the following command:
$ sudo yum install usbguard
OL08-00-040139 package_usbguard_installed
V-248863 1958 medium OL 8 must block unauthorized peripherals before establishing a connection. SRG-OS-ID
The usbguard must be configured to allow connected USB devices to work
properly, avoiding the system to become inaccessible.
By default USBGuard when enabled prevents access to all USB devices and this lead
to inaccessible system if they use USB mouse/keyboard. To prevent this scenario,
the initial policy configuration must be generated based on current connected USB
devices.
OL08-00-040140 usbguard_generate_policy
V-248864 1958 medium OL 8 must enable the USBGuard. SRG-OS-ID
The usbguard service must be running in order to
enforce the USB device authorization policy for all USB devices.
The USBGuard service should be enabled.

The usbguard service can be enabled with the following command:
$ sudo systemctl enable usbguard.service
OL08-00-040141 service_usbguard_enabled
V-248865 2385 medium A firewall must be able to protect against or limit the effects of denial-of-service (DoS) attacks by ensuring OL 8 can implement rate-limiting measures on impacted network interfaces. SRG-OS-ID
Nftables is modern kernel module for controling network connections coming into a system.
Utilizing the limit statement in "nftables" can help to mitigate DoS attacks.
Firewalld can be configured with many backends, such as nftables.
OL08-00-040150 firewalld-backend
V-248866 2422 medium All OL 8 networked systems must have SSH installed. SRG-OS-ID
Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.
The openssh-server package should be installed.
The openssh-server package can be installed with the following command:
$ sudo yum install openssh-server
OL08-00-040159 package_openssh-server_installed
V-248867 2422 medium All OL 8 networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission. SRG-OS-ID
Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.


This checklist item applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, etc). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
The SSH server service, sshd, is commonly needed.

The sshd service can be enabled with the following command:
$ sudo systemctl enable sshd.service
OL08-00-040160 service_sshd_enabled
V-248868 68 medium OL 8 must force a frequent session key renegotiation for SSH connections to the server. SRG-OS-ID
By decreasing the limit based on the amount of data and enabling
time-based limit, effects of potential attacks against
encryption keys are limited.
The RekeyLimit parameter specifies how often
the session key of the is renegotiated, both in terms of
amount of data that may be transmitted and the time
elapsed.
To decrease the default limits, add or correct the following line in /etc/ssh/sshd_config:
RekeyLimit  
OL08-00-040161 sshd_rekey_limit
V-248869 366 high The x86 Ctrl-Alt-Delete key sequence must be disabled on OL 8. SRG-OS-ID
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot.
By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed.


To configure the system to ignore the Ctrl-Alt-Del key sequence from the command line instead of rebooting the system, do either of the following:
ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.target
or
systemctl mask ctrl-alt-del.target


Do not simply delete the /usr/lib/systemd/system/ctrl-alt-del.service file, as this file may be restored during future system updates.
OL08-00-040170 disable_ctrlaltdel_reboot
V-248870 366 high The x86 Ctrl-Alt-Delete key sequence in OL 8 must be disabled if a graphical user interface is installed. SRG-OS-ID
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot.
By default, GNOME will reboot the system if the
Ctrl-Alt-Del key sequence is pressed.


To configure the system to ignore the Ctrl-Alt-Del key sequence from the Graphical User Interface (GUI) instead of rebooting the system, add or set logout to '' in /etc/dconf/db/local.d/00-security-settings. For example:
[org/gnome/settings-daemon/plugins/media-keys]
logout=''
Once the settings have been added, add a lock to /etc/dconf/db/local.d/locks/00-security-settings-lock to prevent user modification. For example:
/org/gnome/settings-daemon/plugins/media-keys/logout
After the settings have been set, run dconf update.
OL08-00-040171 dconf_gnome_disable_ctrlaltdel_reboot
V-248871 366 medium OL 8 must disable the systemd Ctrl-Alt-Delete burst key sequence. SRG-OS-ID
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot.
By default, SystemD will reboot the system if the Ctrl-Alt-Del
key sequence is pressed Ctrl-Alt-Delete more than 7 times in 2 seconds.


To configure the system to ignore the CtrlAltDelBurstAction setting, add or modify the following to /etc/systemd/system.conf:
CtrlAltDelBurstAction=none
OL08-00-040172 disable_ctrlaltdel_burstaction
V-248872 366 low OL 8 must disable the debug-shell systemd service. SRG-OS-ID
This prevents attackers with physical access from trivially bypassing security
on the machine through valid troubleshooting configurations and gaining root
access when the system is rebooted.
SystemD's debug-shell service is intended to
diagnose SystemD related boot issues with various systemctl
commands. Once enabled and following a system reboot, the root shell
will be available on tty9 which is access by pressing
CTRL-ALT-F9. The debug-shell service should only be used
for SystemD related issues and should otherwise be disabled.


By default, the debug-shell SystemD service is already disabled. The debug-shell service can be disabled with the following command:
$ sudo systemctl mask --now debug-shell.service
OL08-00-040180 service_debug-shell_disabled
V-248873 366 high The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for OL 8 operational support. SRG-OS-ID
Removing the tftp-server package decreases the risk of the accidental
(or intentional) activation of tftp services.


If TFTP is required for operational support (such as transmission of router configurations), its use must be documented with the Information Systems Securty Manager (ISSM), restricted to only authorized personnel, and have access control rules established.
The tftp-server package can be removed with the following command: 
 $ sudo yum erase tftp-server
OL08-00-040190 package_tftp-server_removed
V-248874 366 high The root account must be the only account having unrestricted access to the OL 8 system. SRG-OS-ID
An account has root authority if it has a UID of 0. Multiple accounts
with a UID of 0 afford more opportunity for potential intruders to
guess a password for a privileged account. Proper configuration of
sudo is recommended to afford multiple system administrators
access to root privileges in an accountable manner.
If any account other than root has a UID of 0, this misconfiguration should
be investigated and the accounts other than root should be removed or have
their UID changed.

If the account is associated with system commands or applications the UID should be changed to one greater than "0" but less than "1000." Otherwise assign a UID greater than "1000" that has not already been assigned.
OL08-00-040200 accounts_no_uid_except_zero
V-248875 366 medium OL 8 must prevent IPv4 Internet Control Message Protocol (ICMP) redirect messages from being accepted. SRG-OS-ID
ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.

This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required.
To set the runtime status of the net.ipv4.conf.default.accept_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.default.accept_redirects = 0
OL08-00-040209 sysctl_net_ipv4_conf_default_accept_redirects
V-248876 366 medium OL 8 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted. SRG-OS-ID
An illicit ICMP redirect message could result in a man-in-the-middle attack.
To set the runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.default.accept_redirects = 0
OL08-00-040210 sysctl_net_ipv6_conf_default_accept_redirects
V-248877 366 medium OL 8 must not send Internet Control Message Protocol (ICMP) redirects. SRG-OS-ID
ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.

The ability to send ICMP redirects is only appropriate for systems acting as routers.
To set the runtime status of the net.ipv4.conf.all.send_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.all.send_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.all.send_redirects = 0
OL08-00-040220 sysctl_net_ipv4_conf_all_send_redirects
V-248878 366 medium OL 8 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address. SRG-OS-ID
Responding to broadcast (ICMP) echoes facilitates network mapping
and provides a vector for amplification attacks.

Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network.
To set the runtime status of the net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.icmp_echo_ignore_broadcasts = 1
OL08-00-040230 sysctl_net_ipv4_icmp_echo_ignore_broadcasts
V-248879 366 medium OL 8 must not forward IPv4 source-routed packets. SRG-OS-ID
Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures. This requirement
applies only to the forwarding of source-routerd traffic, such as when IPv4
forwarding is enabled and the system is functioning as a router.


Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required.
To set the runtime status of the net.ipv4.conf.all.accept_source_route kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.all.accept_source_route = 0
OL08-00-040239 sysctl_net_ipv4_conf_all_accept_source_route
V-248880 366 medium OL 8 must not forward IPv6 source-routed packets. SRG-OS-ID
Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.


Accepting source-routed packets in the IPv6 protocol has few legitimate uses. It should be disabled unless it is absolutely required.
To set the runtime status of the net.ipv6.conf.all.accept_source_route kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.all.accept_source_route = 0
OL08-00-040240 sysctl_net_ipv6_conf_all_accept_source_route
V-248881 366 medium OL 8 must not forward IPv4 source-routed packets by default. SRG-OS-ID
Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router,
which can be used to bypass network security measures.

Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required, such as when IPv4 forwarding is enabled and the system is legitimately functioning as a router.
To set the runtime status of the net.ipv4.conf.default.accept_source_route kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.default.accept_source_route = 0
OL08-00-040249 sysctl_net_ipv4_conf_default_accept_source_route
V-248882 366 medium OL 8 must not forward IPv6 source-routed packets by default. SRG-OS-ID
Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.

Accepting source-routed packets in the IPv6 protocol has few legitimate
uses. It should be disabled unless it is absolutely required.
To set the runtime status of the net.ipv6.conf.default.accept_source_route kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.default.accept_source_route = 0
OL08-00-040250 sysctl_net_ipv6_conf_default_accept_source_route
V-252662 medium OL 8 must not enable IPv4 packet forwarding unless the system is a router. SRG-OS-ID
OL08-00-040259 Missing Rule
V-248883 366 medium OL 8 must not enable IPv6 packet forwarding unless the system is a router. SRG-OS-ID
Routing protocol daemons are typically used on routers to exchange
network topology information with other routers. If this capability is used when
not required, system network information may be unnecessarily transmitted across
the network.
To set the runtime status of the net.ipv4.ip_forward kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.ip_forward=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.ip_forward = 0
OL08-00-040260 sysctl_net_ipv4_ip_forward
V-248884 366 medium OL 8 must not accept router advertisements on all IPv6 interfaces. SRG-OS-ID
An illicit router advertisement message could result in a man-in-the-middle attack.
To set the runtime status of the net.ipv6.conf.all.accept_ra kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.all.accept_ra=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.all.accept_ra = 0
OL08-00-040261 sysctl_net_ipv6_conf_all_accept_ra
V-248885 366 medium OL 8 must not accept router advertisements on all IPv6 interfaces by default. SRG-OS-ID
An illicit router advertisement message could result in a man-in-the-middle attack.
To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.default.accept_ra=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.default.accept_ra = 0
OL08-00-040262 sysctl_net_ipv6_conf_default_accept_ra
V-248886 366 medium OL 8 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default. SRG-OS-ID
ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.

The ability to send ICMP redirects is only appropriate for systems acting as routers.
To set the runtime status of the net.ipv4.conf.default.send_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.default.send_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.default.send_redirects = 0
OL08-00-040270 sysctl_net_ipv4_conf_default_send_redirects
V-248887 366 medium OL 8 must ignore IPv4 Internet Control Message Protocol (ICMP) redirect messages. SRG-OS-ID
ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages modify the
host's route table and are unauthenticated. An illicit ICMP redirect
message could result in a man-in-the-middle attack.

This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless absolutely required."
To set the runtime status of the net.ipv4.conf.all.accept_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.all.accept_redirects = 0
OL08-00-040279 sysctl_net_ipv4_conf_all_accept_redirects
V-248888 366 medium OL 8 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages. SRG-OS-ID
An illicit ICMP redirect message could result in a man-in-the-middle attack.
To set the runtime status of the net.ipv6.conf.all.accept_redirects kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv6.conf.all.accept_redirects = 0
OL08-00-040280 sysctl_net_ipv6_conf_all_accept_redirects
V-248889 366 medium OL 8 must disable access to the network "bpf" syscall from unprivileged processes. SRG-OS-ID
Loading and accessing the packet filters programs and maps using the bpf()
syscall has the potential of revealing sensitive information about the kernel state.
To set the runtime status of the kernel.unprivileged_bpf_disabled kernel parameter, run the following command: 
$ sudo sysctl -w kernel.unprivileged_bpf_disabled=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.unprivileged_bpf_disabled = 1
OL08-00-040281 sysctl_kernel_unprivileged_bpf_disabled
V-248890 366 medium OL 8 must restrict the use of "ptrace" to descendant processes. SRG-OS-ID
Unrestricted usage of ptrace allows compromised binaries to run ptrace
on another processes of the user. Like this, the attacker can steal
sensitive information from the target processes (e.g. SSH sessions, web browser, ...)
without any additional assistance from the user (i.e. without resorting to phishing).
To set the runtime status of the kernel.yama.ptrace_scope kernel parameter, run the following command: 
$ sudo sysctl -w kernel.yama.ptrace_scope=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.yama.ptrace_scope = 1
OL08-00-040282 sysctl_kernel_yama_ptrace_scope
V-248891 366 medium OL 8 must restrict exposed kernel pointer addresses access. SRG-OS-ID
Exposing kernel pointers (through procfs or seq_printf()) exposes kernel
writeable structures which may contain functions pointers. If a write vulnerability
occurs in the kernel, allowing write access to any of this structure, the kernel can
be compromised. This option disallow any program without the CAP_SYSLOG capability
to get the addresses of kernel pointers by replacing them with 0.
To set the runtime status of the kernel.kptr_restrict kernel parameter, run the following command: 
$ sudo sysctl -w kernel.kptr_restrict=
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
kernel.kptr_restrict = 
OL08-00-040283 sysctl_kernel_kptr_restrict
V-248892 366 medium OL 8 must disable the use of user namespaces. SRG-OS-ID
It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or system objectives.
These unnecessary capabilities or services are often overlooked and therefore may remain unsecured.
They increase the risk to the platform by providing additional attack vectors.
User namespaces are used primarily for Linux containers. The value 0
disallows the use of user namespaces.
To set the runtime status of the user.max_user_namespaces kernel parameter,
run the following command:
$ sudo sysctl -w user.max_user_namespaces=0
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
user.max_user_namespaces = 0
When containers are deployed on the machine, the value should be set to large non-zero value.
OL08-00-040284 sysctl_user_max_user_namespaces
V-248893 366 medium OL 8 must use reverse path filtering on all IPv4 interfaces. SRG-OS-ID
Enabling reverse path filtering drops packets with source addresses
that should not have been able to be received on the interface they were
received on. It should not be used on systems which are routers for
complicated networks, but is helpful for end hosts and routers serving small
networks.
To set the runtime status of the net.ipv4.conf.all.rp_filter kernel parameter, run the following command: 
$ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.ipv4.conf.all.rp_filter = 1
OL08-00-040285 sysctl_net_ipv4_conf_all_rp_filter
V-248894 366 medium OL 8 must enable hardening for the Berkeley Packet Filter Just-in-time compiler. SRG-OS-ID
When hardened, the extended Berkeley Packet Filter just-in-time compiler
will randomize any kernel addresses in the BPF programs and maps,
and will not expose the JIT addresses in /proc/kallsyms.
To set the runtime status of the net.core.bpf_jit_harden kernel parameter, run the following command: 
$ sudo sysctl -w net.core.bpf_jit_harden=2
To make sure that the setting is persistent, add the following line to a file in the directory /etc/sysctl.d:
net.core.bpf_jit_harden = 2
OL08-00-040286 sysctl_net_core_bpf_jit_harden
V-248895 366 medium OL 8 must be configured to prevent unrestricted mail relaying. SRG-OS-ID
If unrestricted mail relaying is permitted, unauthorized senders could use this
host as a mail relay for the purpose of sending spam or other unauthorized
activity.
Modify the 
/etc/postfix/main.cf
file to restrict client connections to the local network with the following command:
$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'
OL08-00-040290 postfix_prevent_unrestricted_relay
V-248896 366 low The OL 8 file integrity tool must be configured to verify extended attributes. SRG-OS-ID
Extended attributes in file systems are used to contain arbitrary data and file metadata
with security implications.
By default, the xattrs option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the xattrs option is missing, add xattrs
to the appropriate ruleset.
For example, add xattrs to the following line in /etc/aide.conf:
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256
AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds xattrs to all rule sets available in /etc/aide.conf
OL08-00-040300 aide_verify_ext_attributes
V-248897 366 low The OL 8 file integrity tool must be configured to verify Access Control Lists (ACLs). SRG-OS-ID
ACLs can provide permissions beyond those permitted through the file mode and must be
verified by the file integrity tools.
By default, the acl option is added to the FIPSR ruleset in AIDE.
If using a custom ruleset or the acl option is missing, add acl
to the appropriate ruleset.
For example, add acl to the following line in /etc/aide.conf:
FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256
AIDE rules can be configured in multiple ways; this is merely one example that is already configured by default. The remediation provided with this rule adds acl to all rule sets available in /etc/aide.conf
OL08-00-040310 aide_verify_acls
V-248898 366 medium The graphical display manager must not be installed on OL 8 unless approved. SRG-OS-ID
Unnecessary service packages must not be installed to decrease the attack surface of the system. X windows has a long history of security
vulnerabilities and should not be installed unless approved and documented.
By removing the following packages,  the system no longer has X Windows installed.

xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland

If X Windows is not installed then the system cannot boot into graphical user mode.
This prevents the system from being accidentally or maliciously booted into a graphical.target
mode. To do so, run the following command:

sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
OL08-00-040320 xwindows_remove_packages
V-252663 366 medium The graphical display manager must not be the default target on OL 8 unless approved. SRG-OS-ID
Services that are not required for system and application processes
must not be active to decrease the attack surface of the system. X windows has a
long history of security vulnerabilities and should not be used unless approved
and documented.
Systems that do not require a graphical user interface should only boot by
default into multi-user.target mode. This prevents accidental booting of the system
into a graphical.target mode. Setting the system's default target to
multi-user.target will prevent automatic startup of the X server. To do so, run:
$ systemctl set-default multi-user.target
You should see the following output:
Removed symlink /etc/systemd/system/default.target.
Created symlink from /etc/systemd/system/default.target to /usr/lib/systemd/system/multi-user.target.
OL08-00-040321 xwindows_runlevel_target
V-248899 366 medium OL 8 network interfaces must not be in promiscuous mode. SRG-OS-ID
Network interfaces in promiscuous mode allow for the capture of all network traffic
visible to the system. If unauthorized individuals can access these applications, it
may allow them to collect information such as logon IDs, passwords, and key exchanges
between systems.


If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information Systems Security Manager (ISSM) and restricted to only authorized personnel.
The system should not be acting as a network sniffer, which can
capture all traffic on the network to which it is connected. Run the following
to determine if any interface is running in promiscuous mode:
$ ip link | grep PROMISC
Promiscuous mode of an interface can be disabled with the following command:
$ sudo ip link set dev device_name multicast off promisc off
OL08-00-040330 network_sniffer_disabled
V-248900 366 medium OL 8 remote X connections for interactive users must be disabled unless to fulfill documented and validated mission requirements. SRG-OS-ID
Disable X11 forwarding unless there is an operational requirement to use X11
applications directly. There is a small risk that the remote X11 servers of
users who are logged in via SSH with X11 forwarding could be compromised by
other users on the X11 server. Note that even if X11 forwarding is disabled,
users can always install their own forwarders.
The X11Forwarding parameter provides the ability to tunnel X11 traffic
through the connection to enable remote graphic connections.
SSH has the capability to encrypt remote X11 connections when SSH's
X11Forwarding option is enabled.

The default SSH configuration disables X11Forwarding. The appropriate configuration is used if no value is set for X11Forwarding.
To explicitly disable X11 Forwarding, add or correct the following line in /etc/ssh/sshd_config:
X11Forwarding no
OL08-00-040340 sshd_disable_x11_forwarding
V-248901 366 medium The OL 8 SSH daemon must prevent remote hosts from connecting to the proxy display. SRG-OS-ID
When X11 forwarding is enabled, there may be additional exposure to the
server and client displays if the sshd proxy display is configured to listen
on the wildcard address. By default, sshd binds the forwarding server to the
loopback address and sets the hostname part of the DISPLAY
environment variable to localhost. This prevents remote hosts from
connecting to the proxy display.  
The SSH daemon should prevent remote hosts from connecting to the proxy
display.

The default SSH configuration for X11UseLocalhost is yes, which prevents remote hosts from connecting to the proxy display.
To explicitly prevent remote connections to the proxy display, add or correct the following line in /etc/ssh/sshd_config: X11UseLocalhost yes
OL08-00-040341 sshd_x11_use_localhost
V-248902 366 medium If the Trivial File Transfer Protocol (TFTP) server is required, the OL 8 TFTP daemon must be configured to operate in secure mode. SRG-OS-ID
Using the -s option causes the TFTP service to only serve files from the
given directory. Serving files from an intentionally-specified directory
reduces the risk of sharing files which should remain private.
If running the tftp service is necessary, it should be configured
to change its root directory at startup. To do so, ensure
/etc/xinetd.d/tftp includes -s as a command line argument, as shown in
the following example:
server_args = -s 
OL08-00-040350 tftpd_uses_secure_mode
V-248903 366 high A File Transfer Protocol (FTP) server package must not be installed unless mission essential on OL 8. SRG-OS-ID
Removing the vsftpd package decreases the risk of its
accidental activation.
The vsftpd package can be removed with the following command: 
 $ sudo yum erase vsftpd
OL08-00-040360 package_vsftpd_removed
V-248904 366 medium OL 8 must not have the "gssproxy" package installed if not required for operational support. SRG-OS-ID
gssproxy is a proxy for GSS API credential handling.
The gssproxy package can be removed with the following command:
$ sudo yum erase gssproxy
OL08-00-040370 package_gssproxy_removed
V-248905 366 medium OL 8 must not have the "iprutils" package installed if not required for operational support. SRG-OS-ID
iprutils provides a suite of utlilities to manage and configure SCSI devices
supported by the ipr SCSI storage device driver.
The iprutils package can be removed with the following command:
$ sudo yum erase iprutils
OL08-00-040380 package_iprutils_removed
V-248906 366 medium OL 8 must not have the "tuned" package installed if not required for operational support. SRG-OS-ID
tuned contains a daemon that tunes the system settings dynamically.
It does so by monitoring the usage of several system components periodically. Based
on that information, components will then be put into lower or higher power savings
modes to adapt to the current usage.
The tuned package can be removed with the following command:
$ sudo yum erase tuned
OL08-00-040390 package_tuned_removed
V-248907 2235 medium OL 8 must prevent non-privileged users from executing privileged functions, including disabling, circumventing, or altering implemented security safeguards/countermeasures. SRG-OS-ID
Preventing non-privileged users from executing privileged functions mitigates
the risk that unauthorized individuals or processes may gain unnecessary access
to information or privileges.


Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.
Configure the operating system to prevent non-privileged users from executing
privileged functions to include disabling, circumventing, or altering
implemented security safeguards/countermeasures. All administrators must be
mapped to the sysadm_u or staff_u users with the
appropriate domains (sysadm_t and staff_t).
$ sudo semanage login -m -s sysadm_u USER
or
$ sudo semanage login -m -s staff_u USER


All authorized non-administrative users must be mapped to the user_u role or the appropriate domain (user_t).
$ sudo semanage login -m -s user_u USER
OL08-00-040400 selinux_user_login_roles