Oracle Linux 8 Security Technical Implementation Guide
- Version/Release: V1R9
- Published: 2023-12-01
-
Expand All:
- Severity:
-
Sort:
Compare
Select any two versions of this STIG to compare the individual requirements
View
Select any old version/release of this STIG to view the previous requirements
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030180
- Vuln IDs
-
- V-248519
- Rule IDs
-
- SV-248519r853745_rule
Checks: C-51953r779121_chk
Verify the audit service is configured to produce audit records. Check that the audit service is installed with the following command: $ sudo yum list installed audit If the "auditd" package is not installed, this is a finding.
Fix: F-51907r779122_fix
Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. Install the audit service (if the audit service is not already installed) with the following command: $ sudo yum install audit
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030181
- Vuln IDs
-
- V-248520
- Rule IDs
-
- SV-248520r853746_rule
Checks: C-51954r818593_chk
Verify the audit service is configured to produce audit records with the following command: $ sudo systemctl status auditd.service auditd.service - Security Auditing Service Loaded:loaded (/usr/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) Active: active (running) since Tues 2020-12-11 12:56:56 EST; 4 weeks 0 days ago If the audit service is not "active" and "running", this is a finding.
Fix: F-51908r779125_fix
Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred with the following commands: $ sudo systemctl enable auditd.service $ sudo systemctl start auditd.service
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010000
- Vuln IDs
-
- V-248521
- Rule IDs
-
- SV-248521r779129_rule
Checks: C-51955r779127_chk
Verify the version of the operating system is vendor supported. Check the version of the operating system with the following command: $ udo cat /etc/oracle-release Oracle Linux Server release 8.2 Current End of Premier Support for Oracle Linux 8 is July 2029, while Extended Support might consider an extended term. If the release is not supported by the vendor, this is a finding.
Fix: F-51909r779128_fix
Upgrade to a supported version of the operating system.
- RMF Control
- SI-2
- Severity
- Medium
- CCI
- CCI-001233
- Version
- OL08-00-010001
- Vuln IDs
-
- V-248522
- Rule IDs
-
- SV-248522r943103_rule
Checks: C-51956r943102_chk
Check that the following package has been installed: # rpm -qa | grep -i mcafeetp If the "mcafeetp" package is not installed, this is a finding. Verify that the daemon is running: # ps -ef | grep -i mfetpd If the daemon is not running, this is a finding.
Fix: F-51910r779131_fix
Install and enable the latest McAfee ENSLTP package.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010010
- Vuln IDs
-
- V-248523
- Rule IDs
-
- SV-248523r779135_rule
Checks: C-51957r779133_chk
Verify the operating system security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). Obtain the list of available package security updates from Oracle. The URL for updates is https://linux.oracle.com/errata/. It is important to note that updates provided by Oracle may not be present on the system if the underlying packages are not installed. Check that the available package security updates have been installed on the system with the following command: $ sudo yum history list | more Loaded plugins: langpacks, product-id, subscription-manager ID | Command line | Date and time | Action(s) | Altered ------------------------------------------------------------------------------- 70 | install aide | 2020-03-05 10:58 | Install | 1 69 | update -y | 2020-03-04 14:34 | Update | 18 EE 68 | install vlc | 2020-02-21 17:12 | Install | 21 67 | update -y | 2020-02-21 17:04 | Update | 7 EE If package updates have not been performed on the system within the timeframe that the site/program documentation requires, this is a finding. Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM. If the operating system is not in compliance with the Information Assurance Vulnerability Management (IAVM) process, this is a finding.
Fix: F-51911r779134_fix
Install the operating system patches or updated packages available from Oracle within 30 days or sooner as local policy dictates.
- RMF Control
- AC-17
- Severity
- High
- CCI
- CCI-000068
- Version
- OL08-00-010020
- Vuln IDs
-
- V-248524
- Rule IDs
-
- SV-248524r928551_rule
Checks: C-51958r928549_chk
Verify the operating system implements DOD-approved encryption to protect the confidentiality of remote access sessions. Check to see if FIPS mode is enabled with the following command: $ fips-mode-setup --check FIPS mode is enabled If FIPS mode is "enabled", check to see if the kernel boot parameter is configured for FIPS mode with the following command: $ sudo grub2-editenv list | grep fips kernelopts=root=/dev/mapper/ol-root ro resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 boot=UUID=25856928-386b-4205-9a0e-a2953ae2712d audit=1 audit_backlog_limit=8192 pti=on random.trust_cpu=on slub_debug=P page_poison=1 If the kernel boot parameter is configured to use FIPS mode, check to see if the system is in FIPS mode with the following command: $ sudo cat /proc/sys/crypto/fips_enabled 1 If FIPS mode is not "enabled", the kernel boot parameter is not configured for FIPS mode, or the system does not have a value of "1" for "fips_enabled" in "/proc/sys/crypto", this is a finding.
Fix: F-51912r928550_fix
Configure the operating system to implement DOD-approved encryption by following the steps below: To enable strict FIPS compliance, the fips=1 kernel option must be added to the kernel boot parameters during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place. Enable FIPS mode after installation (not strict FIPS-compliant) with the following command: $ sudo fips-mode-setup --enable Reboot the system for the changes to take effect.
- RMF Control
- SC-28
- Severity
- Medium
- CCI
- CCI-001199
- Version
- OL08-00-010030
- Vuln IDs
-
- V-248525
- Rule IDs
-
- SV-248525r917893_rule
Checks: C-51959r917892_chk
Verify OL 8 prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption. If there is a documented and approved reason for not having data-at-rest encryption at the operating system level, such as encryption provided by a hypervisor or a disk storage array in a virtualized environment, this requirement is not applicable. Verify all system partitions are encrypted with the following command: $ sudo blkid /dev/mapper/ol-root: UUID="67b7d7fe-de60-6fd0-befb-e6748cf97743" TYPE="crypto_LUKS" Every persistent disk partition present must be of type "crypto_LUKS". If any partitions other than the boot partition or pseudo file systems (such as "/proc" or "/sys") are not listed, ask the administrator to indicate how the partitions are encrypted. If there is no evidence that these partitions are encrypted, this is a finding.
Fix: F-51913r779140_fix
Configure OL 8 to prevent unauthorized modification of all information at rest by using disk encryption. Encrypting a partition in an already-installed system is more difficult because existing partitions will need to be resized and changed. To encrypt an entire partition, dedicate a partition for encryption in the partition layout.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- OL08-00-010040
- Vuln IDs
-
- V-248526
- Rule IDs
-
- SV-248526r858561_rule
Checks: C-51960r858560_chk
Verify any publicly accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. Check for the location of the banner file being used with the following command: $ sudo grep -ir banner /etc/ssh/sshd_config* banner /etc/issue This command will return the banner keyword and the name of the file that contains the SSH banner (in this case "/etc/issue"). If the line is commented out, this is a finding. If conflicting results are returned, this is a finding. View the file specified by the banner keyword to check that it matches the text of the Standard Mandatory DoD Notice and Consent Banner: "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." If the system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding. If the text in the file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.
Fix: F-51914r779143_fix
Configure OL 8 to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the SSH. Edit the "/etc/ssh/sshd_config" file to uncomment the banner keyword and configure it to point to a file that will contain the logon banner (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). An example configuration line is: banner /etc/issue Either create the file containing the banner or replace the text in the file with the Standard Mandatory DoD Notice and Consent Banner. The DoD-required text is: "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." The SSH service must be restarted for changes to take effect.
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- OL08-00-010049
- Vuln IDs
-
- V-248527
- Rule IDs
-
- SV-248527r779147_rule
Checks: C-51961r779145_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify OL 8 displays a banner before granting access to the operating system via a graphical user logon. Determine if the operating system displays a banner at the logon screen with the following command: $ sudo grep banner-message-enable /etc/dconf/db/local.d/* banner-message-enable=true If "banner-message-enable" is set to "false" or is missing, this is a finding.
Fix: F-51915r779146_fix
Configure the operating system to display a banner before granting access to the system. Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command: $ sudo touch /etc/dconf/db/local.d/01-banner-message Add the following lines to the [org/gnome/login-screen] section of the "/etc/dconf/db/local.d/01-banner-message": [org/gnome/login-screen] banner-message-enable=true Run the following command to update the database: $ sudo dconf update
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- OL08-00-010050
- Vuln IDs
-
- V-248528
- Rule IDs
-
- SV-248528r779150_rule
Checks: C-51962r779148_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify OL 8 displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon. Check that the operating system displays the exact Standard Mandatory DoD Notice and Consent Banner text with the command: $ sudo grep banner-message-text /etc/dconf/db/local.d/* banner-message-text= 'You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-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.\n-At any time, the USG may inspect and seize data stored on this IS.\n-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.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-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. ' Note: The "\n" characters are for formatting only. They will not be displayed on the graphical interface. If the banner does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.
Fix: F-51916r779149_fix
Configure OL 8 to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. Note: If the system does not have a graphical user interface installed, this requirement is Not Applicable. Add the following lines to the [org/gnome/login-screen] section of the "/etc/dconf/db/local.d/01-banner-message": banner-message-text='You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-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.\n-At any time, the USG may inspect and seize data stored on this IS.\n-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.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-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. ' Note: The "\n" characters are for formatting only. They will not be displayed on the graphical interface. Run the following command to update the database: $ sudo dconf update
- RMF Control
- AC-8
- Severity
- Medium
- CCI
- CCI-000048
- Version
- OL08-00-010060
- Vuln IDs
-
- V-248529
- Rule IDs
-
- SV-248529r779153_rule
Checks: C-51963r779151_chk
Verify OL 8 displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a command line user logon. Check that OL 8 displays a banner at the command line login screen with the following command: $ sudo cat /etc/issue If the banner is set correctly, it will return the following text: "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." If the banner text does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.
Fix: F-51917r779152_fix
Configure OL 8 to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via command line logon. Edit the "/etc/issue" file to replace the default text with the Standard Mandatory DoD Notice and Consent Banner. The DoD-required text is: "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."
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000067
- Version
- OL08-00-010070
- Vuln IDs
-
- V-248530
- Rule IDs
-
- SV-248530r779156_rule
Checks: C-51964r779154_chk
Verify that OL 8 monitors all remote access methods. Check that remote access methods are being logged by running the following command: $ sudo grep -E '(auth.*|authpriv.*|daemon.*)' /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.conf:auth.*;authpriv.*;daemon.* /var/log/secure If "auth.*", "authpriv.*", or "daemon.*" are not configured to be logged, this is a finding.
Fix: F-51918r779155_fix
Configure OL 8 to monitor all remote access methods by installing rsyslog with the following command: $ sudo yum install rsyslog Add or update the following lines to the "/etc/rsyslog.conf" file: auth.*;authpriv.*;daemon.* /var/log/secure The "rsyslog" service must be restarted for the changes to take effect. To restart the "rsyslog" service, run the following command: $ sudo systemctl restart rsyslog.service
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000185
- Version
- OL08-00-010090
- Vuln IDs
-
- V-248531
- Rule IDs
-
- SV-248531r860907_rule
Checks: C-51965r858601_chk
Verify OL 8, for PKI-based authentication, has valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor. Note: If the System Administrator demonstrates the use of an approved alternate multifactor authentication method, this requirement is not applicable. Check that the system has a valid DoD root CA installed with the following command: $ sudo openssl x509 -text -in /etc/sssd/pki/sssd_auth_ca_db.pem Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha256WithRSAEncryption Issuer: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 Validity Not Before: Mar 20 18:46:41 2012 GMT Not After : Dec 30 18:46:41 2029 GMT Subject: C = US, O = U.S. Government, OU = DoD, OU = PKI, CN = DoD Root CA 3 Subject Public Key Info: Public Key Algorithm: rsaEncryption If the root ca file is not a DoD-issued certificate with a valid date installed in the "/etc/sssd/pki/sssd_auth_ca_db.pem" location, this is a finding.
Fix: F-51919r818597_fix
Configure OL 8, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. Obtain a valid copy of the DoD root CA file from the PKI CA certificate bundle at cyber.mil and copy it into the following file: /etc/sssd/pki/sssd_auth_ca_db.pem
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000186
- Version
- OL08-00-010100
- Vuln IDs
-
- V-248532
- Rule IDs
-
- SV-248532r779162_rule
Checks: C-51966r779160_chk
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, this is a finding.
Fix: F-51920r779161_fix
Create a new private and public key pair that uses a passcode with the following command: $ sudo ssh-keygen -n [passphrase]
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000196
- Version
- OL08-00-010110
- Vuln IDs
-
- V-248533
- Rule IDs
-
- SV-248533r877397_rule
Checks: C-51967r779163_chk
Verify that the shadow password suite configuration is set to encrypt passwords with a FIPS 140-2 approved cryptographic hashing algorithm. Check the hashing algorithm that is being used to hash passwords with the following command: $ sudo cat /etc/login.defs | grep -i crypt ENCRYPT_METHOD SHA512 If "ENCRYPT_METHOD" does not equal SHA512 or greater, this is a finding.
Fix: F-51921r779164_fix
Configure OL 8 to encrypt all stored passwords. Edit/modify the following line in the "/etc/login.defs" file and set "[ENCRYPT_METHOD]" to SHA512: ENCRYPT_METHOD SHA512
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000196
- Version
- OL08-00-010120
- Vuln IDs
-
- V-248534
- Rule IDs
-
- SV-248534r877397_rule
Checks: C-51968r779166_chk
Confirm 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.
Fix: F-51922r779167_fix
Lock all interactive user accounts not using SHA-512 hashing until the passwords can be regenerated with SHA-512.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000196
- Version
- OL08-00-010130
- Vuln IDs
-
- V-248535
- Rule IDs
-
- SV-248535r880546_rule
Checks: C-51969r880545_chk
Check that a minimum number of hash rounds is configured by running the following command: $ sudo grep -E "^SHA_CRYPT_" /etc/login.defs If only one of "SHA_CRYPT_MIN_ROUNDS" or "SHA_CRYPT_MAX_ROUNDS" is set, and this value is below "5000", this is a finding. If both "SHA_CRYPT_MIN_ROUNDS" and "SHA_CRYPT_MAX_ROUNDS" are set, and the value for either is below "5000", this is a finding.
Fix: F-51923r818600_fix
Configure OL 8 to encrypt all stored passwords with a strong cryptographic hash. Edit/modify the following line in the "/etc/login.defs" file and set "SHA_CRYPT_MIN_ROUNDS" to a value no lower than "5000": SHA_CRYPT_MIN_ROUNDS 5000
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- OL08-00-010140
- Vuln IDs
-
- V-248537
- Rule IDs
-
- SV-248537r779177_rule
Checks: C-51971r779175_chk
For systems that use BIOS, this is not applicable. Determine if an encrypted password is set for the grub superusers account. On systems that use UEFI, use the following command: $ sudo grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash] If the grub superusers account password does not begin with "grub.pbkdf2.sha512", this is a finding.
Fix: F-51925r779176_fix
Configure the system to require an encrypted grub bootloader password for the grub superusers account with the grub2-setpassword command, which creates/overwrites the "/boot/efi/EFI/redhat/user.cfg" file. Generate an encrypted grub2 password for the grub superusers account with the following command: $ sudo grub2-setpassword Enter password: Confirm password:
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- OL08-00-010141
- Vuln IDs
-
- V-248538
- Rule IDs
-
- SV-248538r818603_rule
Checks: C-51972r818602_chk
For systems that use BIOS, this is Not Applicable. Verify that a unique name is set as the "superusers" account: $ sudo grep -iw "superusers" /boot/efi/EFI/redhat/grub.cfg set superusers="[someuniqueUserNamehere]" export superusers If "superusers" is identical to any OS account name or is missing a name, this is a finding.
Fix: F-51926r779179_fix
Configure the system to replace "root" with a unique name for the grub superusers account. Edit the /etc/grub.d/01_users file and add or modify the following lines: set superusers="[someuniqueUserNamehere]" export superusers password_pbkdf2 [someuniqueUserNamehere] ${GRUB2_PASSWORD} Generate a new grub.cfg file with the following command: $ sudo grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- OL08-00-010149
- Vuln IDs
-
- V-248539
- Rule IDs
-
- SV-248539r818605_rule
Checks: C-51973r818604_chk
For systems that use UEFI, this is Not Applicable. Verify that a unique name is set as the "superusers" account: $ sudo grep -iw "superusers" /boot/grub2/grub.cfg set superusers="[someuniqueUserNamehere]" export superusers If "superusers" is identical to any OS account name or is missing a name, this is a finding.
Fix: F-51927r779182_fix
Configure the system to replace "root" with a unique name for the grub superusers account. Edit the /etc/grub.d/01_users file and add or modify the following lines: set superusers="[someuniqueUserNamehere]" export superusers password_pbkdf2 [someuniqueUserNamehere] ${GRUB2_PASSWORD} Generate a new grub.cfg file with the following command: $ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
- RMF Control
- AC-3
- Severity
- High
- CCI
- CCI-000213
- Version
- OL08-00-010150
- Vuln IDs
-
- V-248540
- Rule IDs
-
- SV-248540r779186_rule
Checks: C-51974r779184_chk
For systems that use UEFI, this is not applicable. Determine if an encrypted password is set for the grub superusers account. On systems that use a BIOS, use the following command: $ sudo grep -iw grub2_password /boot/grub2/user.cfg GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash] If the grub superusers account password does not begin with "grub.pbkdf2.sha512", this is a finding.
Fix: F-51928r779185_fix
Configure the system to require a grub bootloader password for the grub superusers account with the grub2-setpassword command, which creates/overwrites the "/boot/grub2/user.cfg" file. Generate an encrypted grub2 password for the grub superusers account with the following command: $ sudo grub2-setpassword Enter password: Confirm password:
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- OL08-00-010151
- Vuln IDs
-
- V-248541
- Rule IDs
-
- SV-248541r779189_rule
Checks: C-51975r779187_chk
Determine if the system requires authentication for rescue mode with the following command: $ sudo grep sulogin-shell /usr/lib/systemd/system/rescue.service ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell rescue" or is commented out or missing, this is a finding.
Fix: F-51929r779188_fix
Configure the system to require authentication upon booting into rescue mode by adding the following line to the "/usr/lib/systemd/system/rescue.service" file: ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-000213
- Version
- OL08-00-010152
- Vuln IDs
-
- V-248542
- Rule IDs
-
- SV-248542r779192_rule
Checks: C-51976r779190_chk
Determine if the system requires authentication for emergency mode with the following command: $ sudo grep sulogin-shell /usr/lib/systemd/system/emergency.service ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell emergency" or is commented out or missing, this is a finding.
Fix: F-51930r779191_fix
Configure the system to require authentication upon booting into emergency mode by adding the following line to the "/usr/lib/systemd/system/emergency.service" file: ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- OL08-00-010159
- Vuln IDs
-
- V-248543
- Rule IDs
-
- SV-248543r818608_rule
Checks: C-51977r818606_chk
Verify that the "pam_unix.so" module is configured to use sha512. Check that pam_unix.so module is configured to use sha512 in /etc/pam.d/system-auth with the following command: $ sudo grep password /etc/pam.d/system-auth | grep pam_unix password sufficient pam_unix.so sha512 If "sha512" is missing, or is commented out, this is a finding.
Fix: F-51931r818607_fix
Configure OL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. Edit/modify the following line in the "/etc/pam.d/system-auth" file to include the sha512 option for pam_unix.so: password sufficient pam_unix.so sha512
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- OL08-00-010160
- Vuln IDs
-
- V-248544
- Rule IDs
-
- SV-248544r818611_rule
Checks: C-51978r818609_chk
Verify that the "pam_unix.so" module is configured to use sha512 in "/etc/pam.d/password-auth" with the following command: $ sudo grep password /etc/pam.d/password-auth | grep pam_unix password sufficient pam_unix.so sha512 If "sha512" is missing, or is commented out, this is a finding.
Fix: F-51932r818610_fix
Configure OL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication. Edit/modify the following line in the "/etc/pam.d/password-auth" file to include the sha512 option for pam_unix.so: password sufficient pam_unix.so sha512
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- OL08-00-010161
- Vuln IDs
-
- V-248545
- Rule IDs
-
- SV-248545r779201_rule
Checks: C-51979r779199_chk
Verify that OL 8 prevents system daemons from using Kerberos for authentication. If the system is a server using krb5-server-1.17-18.el8.x86_64 or newer, this requirement is not applicable. If the system is a workstation using krb5-workstation-1.17-18.el8.x86_64 or newer, this requirement is not applicable. Check if there are available keytabs with the following command: $ sudo ls -al /etc/*.keytab If this command produces any file(s), this is a finding.
Fix: F-51933r779200_fix
Configure OL 8 to prevent system daemons from using Kerberos for authentication. Remove any files with the .keytab extension from the operating system.
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- OL08-00-010162
- Vuln IDs
-
- V-248546
- Rule IDs
-
- SV-248546r779204_rule
Checks: C-51980r779202_chk
Verify the krb5-workstation package has not been installed on the system with the following commands: If the system is a server or is using krb5-workstation-1.17-18.el8.x86_64 or newer, this is Not Applicable. $ sudo yum list installed krb5-workstation krb5-workstation.x86_64 1.17-9.el8 repository If the krb5-workstation package is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-51934r779203_fix
Document the krb5-workstation package with the ISSO as an operational requirement or remove it from the system with the following command: $ sudo yum remove krb5-workstation
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- OL08-00-010163
- Vuln IDs
-
- V-248547
- Rule IDs
-
- SV-248547r779207_rule
Checks: C-51981r779205_chk
Verify the krb5-server package has not been installed on the system with the following commands: If the system is a workstation or is using krb5-server-1.17-18.el8.x86_64 or newer, this is Not Applicable $ sudo yum list installed krb5-server krb5-server.x86_64 1.17-9.el8 repository If the krb5-server package is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-51935r779206_fix
Document the krb5-server package with the ISSO as an operational requirement or remove it from the system with the following command: $ sudo yum remove krb5-server
- RMF Control
- SC-3
- Severity
- Medium
- CCI
- CCI-001084
- Version
- OL08-00-010170
- Vuln IDs
-
- V-248548
- Rule IDs
-
- SV-248548r779210_rule
Checks: C-51982r779208_chk
Verify the operating system verifies correct operation of all security functions. Check if "SELinux" is in "Enforcing" mode with the following command: $ getenforce Enforcing If "SELinux" is not in "Enforcing" mode, this is a finding.
Fix: F-51936r779209_fix
Configure OL 8 to verify correct operation of all security functions. Set "SELinux" to "Enforcing" mode by modifying the "/etc/selinux/config" file with the following line: SELINUX=enforcing A reboot is required for the changes to take effect.
- RMF Control
- SC-3
- Severity
- Low
- CCI
- CCI-001084
- Version
- OL08-00-010171
- Vuln IDs
-
- V-248549
- Rule IDs
-
- SV-248549r779213_rule
Checks: C-51983r779211_chk
Verify the operating system has the "policycoreutils" package installed with the following command: $ sudo yum list installed policycoreutils policycoreutils.x86_64 2.9-3.el8 @anaconda If the "policycoreutils" package is not installed, this is a finding.
Fix: F-51937r779212_fix
Install the "policycoreutil" package, if it is not already installed, by running the following command: $ sudo yum install policycoreutils
- RMF Control
- SC-4
- Severity
- Medium
- CCI
- CCI-001090
- Version
- OL08-00-010190
- Vuln IDs
-
- V-248551
- Rule IDs
-
- SV-248551r779219_rule
Checks: C-51985r779217_chk
Verify that all world-writable directories have the sticky bit set. Verify that all world-writable directories have the sticky bit set by running the following command: $ sudo find / -type d \( -perm -0002 -a ! -perm -1000 \) -print 2>/dev/null If any of the returned directories are world-writable and do not have the sticky bit set, this is a finding.
Fix: F-51939r779218_fix
Configure all world-writable directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources. Set the sticky bit on all world-writable directories using the command, replace "[World-Writable Directory]" with any directory path missing the sticky bit: $ sudo chmod 1777 [World-Writable Directory]
- RMF Control
- MA-4
- Severity
- Medium
- CCI
- CCI-000879
- Version
- OL08-00-010200
- Vuln IDs
-
- V-248552
- Rule IDs
-
- SV-248552r917896_rule
Checks: C-51986r917894_chk
Verify the SSH server automatically terminates a user session after the SSH client has become unresponsive. Check that the "ClientAliveCountMax" is set to "1" by running the following command: $ sudo grep -ir ClientAliveCountMax /etc/ssh/sshd_config* ClientAliveCountMax 1 If "ClientAliveCountMax" does not exist, does not have a product value of "1" in "/etc/ssh/sshd_config", or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51940r917895_fix
Note: This setting must be applied in conjunction with OL08-00-010201 to function correctly. Configure the SSH server to terminate a user session automatically after the SSH client has become unresponsive. Modify or append the following line in the "/etc/ssh/sshd_config" file: ClientAliveCountMax 1 For the changes to take effect, the SSH daemon must be restarted. $ sudo systemctl restart sshd.service
- RMF Control
- MA-4
- Severity
- Medium
- CCI
- CCI-000879
- Version
- OL08-00-010201
- Vuln IDs
-
- V-248553
- Rule IDs
-
- SV-248553r917899_rule
Checks: C-51987r917897_chk
Verify the SSH server automatically terminates a user session after the SSH client has been unresponsive for 10 minutes. Check that the "ClientAliveInterval" variable is set to a value of "600" or less by running the following command: $ sudo grep -ir ClientAliveInterval /etc/ssh/sshd_config* ClientAliveInterval 600 If "ClientAliveInterval" does not exist, does not have a product value of "600" or less in "/etc/ssh/sshd_config", or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51941r917898_fix
Note: This setting must be applied in conjunction with OL08-00-010200 to function correctly. Configure the SSH server to terminate a user session automatically after the SSH client has been unresponsive for 10 minutes. Modify or append the following lines in the "/etc/ssh/sshd_config" file to have a product value of "600" or less: ClientAliveInterval 600 The SSH daemon must be restarted for changes to take effect. $ sudo systemctl restart sshd.service
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010210
- Vuln IDs
-
- V-248554
- Rule IDs
-
- SV-248554r779228_rule
Checks: C-51988r779226_chk
Verify that the "/var/log/messages" file has mode "0640" or less permissive with the following command: $ sudo stat -c "%a %n" /var/log/messages 640 /var/log/messages If a value of "0640" or less permissive is not returned, this is a finding.
Fix: F-51942r779227_fix
Change the permissions of the file "/var/log/messages" to "0640" by running the following command: $ sudo chmod 0640 /var/log/messages
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010220
- Vuln IDs
-
- V-248555
- Rule IDs
-
- SV-248555r779231_rule
Checks: C-51989r779229_chk
Verify that the /var/log/messages file is owned by root with the following command: $ sudo stat -c "%U" /var/log/messages root If "root" is not returned as a result, this is a finding.
Fix: F-51943r779230_fix
Change the owner of the file /var/log/messages to root by running the following command: $ sudo chown root /var/log/messages
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010230
- Vuln IDs
-
- V-248556
- Rule IDs
-
- SV-248556r779234_rule
Checks: C-51990r779232_chk
Verify the "/var/log/messages" file is group-owned by root with the following command: $ sudo stat -c "%G" /var/log/messages root If "root" is not returned as a result, this is a finding.
Fix: F-51944r779233_fix
Change the group of the file "/var/log/messages" to "root" by running the following command: $ sudo chgrp root /var/log/messages
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010240
- Vuln IDs
-
- V-248557
- Rule IDs
-
- SV-248557r779237_rule
Checks: C-51991r779235_chk
Verify that the "/var/log" directory has a mode of "0755" or less with the following command: $ sudo stat -c "%a %n" /var/log 755 /var/log If a value of "0755" or less permissive is not returned, this is a finding.
Fix: F-51945r779236_fix
Change the permissions of the directory "/var/log" to "0755" by running the following command: $ sudo chmod 0755 /var/log
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010250
- Vuln IDs
-
- V-248558
- Rule IDs
-
- SV-248558r779240_rule
Checks: C-51992r779238_chk
Verify the /var/log directory is owned by root with the following command: $ sudo stat -c "%U" /var/log root If "root" is not returned as a result, this is a finding.
Fix: F-51946r779239_fix
Change the owner of the directory /var/log to root by running the following command: $ sudo chown root /var/log
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-010260
- Vuln IDs
-
- V-248559
- Rule IDs
-
- SV-248559r779243_rule
Checks: C-51993r779241_chk
Verify the "/var/log" directory is group-owned by root with the following command: $ sudo stat -c "%G" /var/log root If "root" is not returned as a result, this is a finding.
Fix: F-51947r779242_fix
Change the group of the directory "/var/log" to "root" by running the following command: $ sudo chgrp root /var/log
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-001453
- Version
- OL08-00-010287
- Vuln IDs
-
- V-248560
- Rule IDs
-
- SV-248560r877394_rule
Checks: C-51994r818612_chk
Verify that system-wide crypto policies are in effect: $ sudo grep -i CRYPTO_POLICY /etc/sysconfig/sshd # CRYPTO_POLICY= If the "CRYPTO_POLICY" is uncommented, this is a finding.
Fix: F-51948r818613_fix
Configure the OL 8 SSH daemon to use system-wide crypto policies by adding the following line to /etc/sysconfig/sshd: # CRYPTO_POLICY= A reboot is required for the changes to take effect.
- RMF Control
- MA-4
- Severity
- Medium
- CCI
- CCI-000877
- Version
- OL08-00-010290
- Vuln IDs
-
- V-248561
- Rule IDs
-
- SV-248561r917902_rule
Checks: C-51995r917900_chk
Verify the SSH server is configured to use only MACs employing FIPS 140-2-approved algorithms with the following command: $ sudo grep -i macs /etc/crypto-policies/back-ends/opensshserver.config -oMACS=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com If the MACs entries in the "opensshserver.config" file have any hashes other than shown here, the order differs from the example above, or they are missing or commented out, this is a finding.
Fix: F-51949r917901_fix
Configure the OL 8 SSH server to use only MACs employing FIPS 140-2 approved algorithms: Update the "/etc/crypto-policies/back-ends/opensshserver.config" file to include these MACs employing FIPS 140-2 approved algorithms: -oMACS=hmac-sha2-512,hmac-sha2-256,hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com A reboot is required for the changes to take effect.
- RMF Control
- MA-4
- Severity
- Medium
- CCI
- CCI-000877
- Version
- OL08-00-010291
- Vuln IDs
-
- V-248562
- Rule IDs
-
- SV-248562r917905_rule
Checks: C-51996r917903_chk
Verify the OL 8 SSH server is configured to use only ciphers employing FIPS 140-2 approved algorithms with the following command: $ sudo grep -i ciphers /etc/crypto-policies/back-ends/opensshserver.config CRYPTO_POLICY='-oCiphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com' If the cipher entries in the "opensshserver.config" file have any ciphers other than shown here, the order differs from the example above, or they are missing or commented out, this is a finding.
Fix: F-51950r917904_fix
Configure the OL 8 SSH server to use only ciphers employing FIPS 140-2 approved algorithms: Update the "/etc/crypto-policies/back-ends/opensshserver.config" file to include these ciphers employing FIPS 140-2-approved algorithms: CRYPTO_POLICY='-oCiphers=aes256-ctr,aes192-ctr,aes128-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com' A reboot is required for the changes to take effect.
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010292
- Vuln IDs
-
- V-248563
- Rule IDs
-
- SV-248563r779255_rule
Checks: C-51997r779253_chk
Verify the operating system SSH server uses strong entropy with the following command: $ sudo grep -i ssh_use_strong_rng /etc/sysconfig/sshd SSH_USE_STRONG_RNG=32 If the "SSH_USE_STRONG_RNG" line does not equal "32" or is commented out or missing, this is a finding.
Fix: F-51951r779254_fix
Configure the operating system SSH server to use strong entropy. Add or modify the following line in the "/etc/sysconfig/sshd" file. SSH_USE_STRONG_RNG=32 The SSH service must be restarted for changes to take effect.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-001453
- Version
- OL08-00-010293
- Vuln IDs
-
- V-248564
- Rule IDs
-
- SV-248564r877394_rule
Checks: C-51998r779256_chk
Verify the OpenSSL library is configured to use only ciphers employing FIPS 140-2-approved algorithms: Verify that system-wide crypto policies are in effect: $ sudo grep -i opensslcnf.config /etc/pki/tls/openssl.cnf .include /etc/crypto-policies/back-ends/opensslcnf.config If the "opensslcnf.config" is not defined in the "/etc/pki/tls/openssl.cnf" file, this is a finding. Verify which system-wide crypto policy is in use: $ sudo update-crypto-policies --show FIPS If the system-wide crypto policy is set to anything other than "FIPS", this is a finding.
Fix: F-51952r779257_fix
Configure the OL 8 OpenSSL library to use only ciphers employing FIPS 140-2-approved algorithms with the following command: $ sudo fips-mode-setup --enable A reboot is required for the changes to take effect.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-001453
- Version
- OL08-00-010294
- Vuln IDs
-
- V-248565
- Rule IDs
-
- SV-248565r877394_rule
Checks: C-51999r818615_chk
Verify the OpenSSL library is configured to use only DoD-approved TLS encryption: For versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch: $ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config MinProtocol = TLSv1.2 If the "MinProtocol" is set to anything older than "TLSv1.2", this is a finding. For version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer: $ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config TLS.MinProtocol = TLSv1.2 DTLS.MinProtocol = DTLSv1.2 If the "TLS.MinProtocol" is set to anything older than "TLSv1.2" or the "DTLS.MinProtocol" is set to anything older than "DTLSv1.2", this is a finding.
Fix: F-51953r818616_fix
Configure the OL 8 OpenSSL library to use only DoD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file: For versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch: MinProtocol = TLSv1.2 For version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer: TLS.MinProtocol = TLSv1.2 DTLS.MinProtocol = DTLSv1.2 A reboot is required for the changes to take effect.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-001453
- Version
- OL08-00-010295
- Vuln IDs
-
- V-248566
- Rule IDs
-
- SV-248566r877394_rule
Checks: C-52000r818618_chk
Verify the GnuTLS library is configured to only allow DoD-approved SSL/TLS versions: $ sudo grep -io +vers.* /etc/crypto-policies/back-ends/gnutls.config +VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0:+COMP-NULL:%PROFILE_MEDIUM If the "gnutls.config" does not list "-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0" to disable unapproved SSL/TLS versions, this is a finding.
Fix: F-51954r779263_fix
Configure the OL 8 GnuTLS library to use only DoD-approved encryption by adding the following line to "/etc/crypto-policies/back-ends/gnutls.config": +VERS-ALL:-VERS-DTLS0.9:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1:-VERS-DTLS1.0 A reboot is required for the changes to take effect.
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010300
- Vuln IDs
-
- V-248567
- Rule IDs
-
- SV-248567r818622_rule
Checks: C-52001r818620_chk
Verify the system commands contained in the following directories have mode "755" or less permissive with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -exec ls -l {} \; If any system commands are found to be group-writable or world-writable, this is a finding.
Fix: F-51955r818621_fix
Configure the system commands to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any system command with a mode more permissive than "755". $ sudo chmod 755 [FILE]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010310
- Vuln IDs
-
- V-248568
- Rule IDs
-
- SV-248568r779270_rule
Checks: C-52002r779268_chk
Verify the system commands contained in the following directories are owned by "root" with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -exec ls -l {} \; If any system commands are returned, this is a finding.
Fix: F-51956r779269_fix
Configure the system commands to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any system command file not owned by "root". $ sudo chown root [FILE]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010320
- Vuln IDs
-
- V-248569
- Rule IDs
-
- SV-248569r818625_rule
Checks: C-52003r818623_chk
Verify the system commands contained in the following directories are group-owned by "root" or a required system account, with the following command: $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -exec ls -l {} \; If any system commands are returned and is not group-owned by a required system account, this is a finding.
Fix: F-51957r818624_fix
Configure the system commands to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any system command file not group-owned by "root" or a required system account. $ sudo chgrp root [FILE]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010330
- Vuln IDs
-
- V-248570
- Rule IDs
-
- SV-248570r818628_rule
Checks: C-52004r818626_chk
Verify the system-wide shared library files contained in the following directories have mode "755" or less permissive with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type f -exec ls -l {} \; If any system-wide shared library file is found to be group-writable or world-writable, this is a finding.
Fix: F-51958r818627_fix
Configure the library files to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any library file with a mode more permissive than 755. $ sudo chmod 755 [FILE]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010340
- Vuln IDs
-
- V-248571
- Rule IDs
-
- SV-248571r779279_rule
Checks: C-52005r779277_chk
Verify the system-wide shared library files are owned by "root" with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -user root -exec ls -l {} \; If any system-wide shared library file is returned, this is a finding.
Fix: F-51959r779278_fix
Configure the system-wide shared library files (/lib, /lib64, /usr/lib, and /usr/lib64) to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any library file not owned by "root". $ sudo chown root [FILE]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010350
- Vuln IDs
-
- V-248572
- Rule IDs
-
- SV-248572r779282_rule
Checks: C-52006r779280_chk
Verify the system-wide shared library files are group-owned by "root" with the following command: $ sudo find -L /lib /lib64 /usr/lib /usr/lib64 ! -group root -exec ls -l {} \; If any system-wide shared library file is returned, this is a finding.
Fix: F-51960r779281_fix
Configure the system-wide shared library files (/lib, /lib64, /usr/lib, and /usr/lib64) to be protected from unauthorized access. Run the following command, replacing "[FILE]" with any library file not group-owned by "root". $ sudo chgrp root [FILE]
- RMF Control
- CM-3
- Severity
- Medium
- CCI
- CCI-001744
- Version
- OL08-00-010360
- Vuln IDs
-
- V-248573
- Rule IDs
-
- SV-248573r902806_rule
Checks: C-52007r902804_chk
Verify the operating system routinely checks the baseline configuration for unauthorized changes and notifies the SA when anomalies in the operation of any security functions are discovered. Check that OL 8 routinely executes a file integrity scan for changes to the system baseline. The command used in the example will use a daily occurrence. Check the cron directories for scripts controlling the execution and notification of results of the file integrity application. For example, if AIDE is installed on the system, use the following commands: $ sudo ls -al /etc/cron.* | grep aide -rwxr-xr-x 1 root root 29 Nov 22 2015 aide $ sudo grep aide /etc/crontab /var/spool/cron/root /etc/crontab: 30 04 * * * /root/aide /var/spool/cron/root: 30 04 * * * /root/aide $ sudo more /etc/cron.daily/aide #!/bin/bash /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil If the file integrity application does not exist, a script file controlling the execution of the file integrity application does not exist, or the file integrity application does not notify designated personnel of changes, this is a finding.
Fix: F-51961r902805_fix
Configure the file integrity tool to run automatically on the system at least weekly and to notify designated personnel if baseline configurations are changed in an unauthorized manner. The AIDE tool can be configured to email designated personnel with the use of the cron system. The following example output is generic. It will set cron to run AIDE daily and to send an email at the completion of the analysis. $ sudo more /etc/cron.daily/aide #!/bin/bash /usr/sbin/aide --check |/bin/mail -s "$HOSTNAME - Daily AIDE integrity check run" root@example_server_name.mil Note: Per requirement OL08-00-010358, the "mailx" package must be installed on the system to enable email functionality.
- RMF Control
- CM-5
- Severity
- High
- CCI
- CCI-001749
- Version
- OL08-00-010370
- Vuln IDs
-
- V-248574
- Rule IDs
-
- SV-248574r877463_rule
Checks: C-52008r779286_chk
Check that YUM verifies the signature of packages from a repository prior to install with the following command: $ sudo grep gpgcheck /etc/yum.repos.d/*.repo gpgcheck=1 If "gpgcheck" is not set to "1", or if options are missing or commented out, ask the System Administrator how the certificates for patches and other operating system components are verified. If there is no process to validate certificates that is approved by the organization, this is a finding.
Fix: F-51962r779287_fix
Configure OL 8 to verify the signature of packages from a repository prior to install by setting the following option in the "/etc/yum.repos.d/[your_repo_name].repo" file: gpgcheck=1
- RMF Control
- CM-5
- Severity
- High
- CCI
- CCI-001749
- Version
- OL08-00-010371
- Vuln IDs
-
- V-248575
- Rule IDs
-
- SV-248575r877463_rule
Checks: C-52009r779289_chk
Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components from a repository without verification that they have been digitally signed using a certificate that is recognized and approved by the organization. Check if YUM is configured to perform a signature check on local packages with the following command: $ sudo grep -i localpkg_gpgcheck /etc/dnf/dnf.conf localpkg_gpgcheck =True If "localpkg_gpgcheck" is not set to either "1", "True", or "yes", commented out, or is missing from "/etc/dnf/dnf.conf", this is a finding.
Fix: F-51963r779290_fix
Configure the operating system to remove all software components after updated versions have been installed. Set the "localpkg_gpgcheck" option to "True" in the "/etc/dnf/dnf.conf" file: localpkg_gpgcheck=True
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001749
- Version
- OL08-00-010372
- Vuln IDs
-
- V-248576
- Rule IDs
-
- SV-248576r917907_rule
Checks: C-52010r917906_chk
Note: For OL 8 systems using the Oracle Unbreakable Enterprise Kernel (UEK) Release 6 or above and with secureboot enabled, this requirement is not applicable. Verify the operating system is configured to disable kernel image loading with the following commands. Check the status of the "kernel.kexec_load_disabled" kernel parameter: $ sudo sysctl kernel.kexec_load_disabled kernel.kexec_load_disabled = 1 If "kernel.kexec_load_disabled" is not set to "1" or is missing, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r kernel.kexec_load_disabled /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:kernel.kexec_load_disabled = 1 If "kernel.kexec_load_disabled" is not set to "1" or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51964r858608_fix
Configure OL 8 to disable kernel image loading. Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: kernel.kexec_load_disabled = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-002165
- Version
- OL08-00-010373
- Vuln IDs
-
- V-248577
- Rule IDs
-
- SV-248577r860911_rule
Checks: C-52011r858610_chk
Verify the operating system is configured to enable DAC on symlinks with the following commands. Check the status of the "fs.protected_symlinks" kernel parameter: $ sudo sysctl fs.protected_symlinks fs.protected_symlinks = 1 If "fs.protected_symlinks" is not set to "1" or is missing, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r fs.protected_symlinks /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:fs.protected_symlinks = 1 If "fs.protected_symlinks" is not set to "1" or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51965r858611_fix
Configure OL 8 to enable DAC on symlinks. Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: fs.protected_symlinks = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- AC-3
- Severity
- Medium
- CCI
- CCI-002165
- Version
- OL08-00-010374
- Vuln IDs
-
- V-248578
- Rule IDs
-
- SV-248578r860912_rule
Checks: C-52012r858613_chk
Verify the operating system is configured to enable DAC on hardlinks with the following commands. Check the status of the "fs.protected_hardlinks" kernel parameter: $ sudo sysctl fs.protected_hardlinks fs.protected_hardlinks = 1 If "fs.protected_hardlinks" is not set to "1" or is missing, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r fs.protected_hardlinks /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:fs.protected_hardlinks = 1 If "fs.protected_hardlinks" is not set to "1" or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51966r858614_fix
Configure OL 8 to enable DAC on hardlinks. Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: fs.protected_hardlinks = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- SC-4
- Severity
- Low
- CCI
- CCI-001090
- Version
- OL08-00-010375
- Vuln IDs
-
- V-248579
- Rule IDs
-
- SV-248579r858617_rule
Checks: C-52013r833200_chk
Verify the operating system is configured to restrict access to the kernel message buffer with the following commands. Check the status of the "kernel.dmesg_restrict" kernel parameter: $ sudo sysctl kernel.dmesg_restrict kernel.dmesg_restrict = 1 If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r kernel.dmesg_restrict /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:kernel.dmesg_restrict = 1 If "kernel.dmesg_restrict" is not set to "1" or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51967r858616_fix
Configure OL 8 to restrict access to the kernel message buffer. Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: kernel.dmesg_restrict = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- SC-4
- Severity
- Low
- CCI
- CCI-001090
- Version
- OL08-00-010376
- Vuln IDs
-
- V-248580
- Rule IDs
-
- SV-248580r858619_rule
Checks: C-52014r833202_chk
Verify the operating system is configured to prevent kernel profiling by unprivileged users with the following commands. Check the status of the "kernel.perf_event_paranoid" kernel parameter: $ sudo sysctl kernel.perf_event_paranoid kernel.perf_event_paranoid = 2 If "kernel.perf_event_paranoid" is not set to "2" or is missing, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r kernel.perf_event_paranoid /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:kernel.perf_event_paranoid = 2 If "kernel.perf_event_paranoid" is not set to "2" or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51968r858618_fix
Configure OL 8 to prevent kernel profiling by unprivileged users. Add or edit the following line in a system configuration file in the "/etc/sysctl.d/" directory: kernel.perf_event_paranoid = 2 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- IA-11
- Severity
- Medium
- CCI
- CCI-002038
- Version
- OL08-00-010380
- Vuln IDs
-
- V-248581
- Rule IDs
-
- SV-248581r860915_rule
Checks: C-52015r860913_chk
Verify that "/etc/sudoers" has no occurrences of "NOPASSWD". Check that the "/etc/sudoers" file has no occurrences of "NOPASSWD" by running the following command: $ sudo grep -ir nopasswd /etc/sudoers /etc/sudoers.d %admin ALL=(ALL) NOPASSWD: ALL If any occurrences of "NOPASSWD" are returned from the command and have not been documented with the ISSO as an organizationally defined administrative group using MFA, this is a finding.
Fix: F-51969r860914_fix
Configure the operating system to require users to supply a password for privilege escalation. Check the configuration of the "/etc/sudoers" file with the following command: $ sudo visudo Remove any occurrences of "NOPASSWD" tags in the file. Check the configuration of the /etc/sudoers.d/* files with the following command: $ sudo grep -ir nopasswd /etc/sudoers.d Remove any occurrences of "NOPASSWD" tags in the file.
- RMF Control
- IA-11
- Severity
- Medium
- CCI
- CCI-002038
- Version
- OL08-00-010381
- Vuln IDs
-
- V-248582
- Rule IDs
-
- SV-248582r880551_rule
Checks: C-52016r880550_chk
Verify that the "/etc/sudoers" file has no occurrences of "!authenticate" by running the following command: $ sudo grep -Ei !authenticate /etc/sudoers /etc/sudoers.d/* If any occurrences of "!authenticate" return from the command, this is a finding.
Fix: F-51970r779311_fix
Remove any occurrence of "!authenticate" found in the "/etc/sudoers" file or files in the "/etc/sudoers.d" directory.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010382
- Vuln IDs
-
- V-248583
- Rule IDs
-
- SV-248583r779315_rule
Checks: C-52017r779313_chk
Verify the "sudoers" file restricts sudo access to authorized personnel. $ sudo grep -iw 'ALL' /etc/sudoers /etc/sudoers.d/* If the either of the following entries are returned, this is a finding: ALL ALL=(ALL) ALL ALL ALL=(ALL:ALL) ALL
Fix: F-51971r779314_fix
Remove the following entries from the sudoers file: ALL ALL=(ALL) ALL ALL ALL=(ALL:ALL) ALL
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010383
- Vuln IDs
-
- V-248584
- Rule IDs
-
- SV-248584r880554_rule
Checks: C-52018r880552_chk
Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation. $ sudo grep -Eir '(rootpw|targetpw|runaspw)' /etc/sudoers /etc/sudoers.d* | grep -v '#' /etc/sudoers:Defaults !targetpw /etc/sudoers:Defaults !rootpw /etc/sudoers:Defaults !runaspw If conflicting results are returned, this is a finding. If "Defaults !targetpw" is not defined, this is a finding. If "Defaults !rootpw" is not defined, this is a finding. If "Defaults !runaspw" is not defined, this is a finding.
Fix: F-51972r880553_fix
Define the following in the Defaults section of the /etc/sudoers file or a configuration file in the /etc/sudoers.d/ directory: Defaults !targetpw Defaults !rootpw Defaults !runaspw Remove any configurations that conflict with the above from the following locations: /etc/sudoers /etc/sudoers.d/
- RMF Control
- IA-11
- Severity
- Medium
- CCI
- CCI-002038
- Version
- OL08-00-010384
- Vuln IDs
-
- V-248585
- Rule IDs
-
- SV-248585r880557_rule
Checks: C-52019r880555_chk
Verify the operating system requires re-authentication when using the "sudo" command to elevate privileges. $ sudo grep -Eir 'timestamp_timeout' /etc/sudoers /etc/sudoers.d* /etc/sudoers:Defaults timestamp_timeout=0 If conflicting results are returned, this is a finding. If "timestamp_timeout" is set to a negative number, is commented out, or no results are returned, this is a finding.
Fix: F-51973r880556_fix
Configure the "sudo" command to require re-authentication. Edit the /etc/sudoers file: $ sudo visudo Add or modify the following line: Defaults timestamp_timeout=[value] Note: The "[value]" must be a number that is greater than or equal to "0". Remove any duplicate or conflicting lines from /etc/sudoers and /etc/sudoers.d/ files.
- RMF Control
- IA-2
- Severity
- Low
- CCI
- CCI-001948
- Version
- OL08-00-010390
- Vuln IDs
-
- V-248586
- Rule IDs
-
- SV-248586r853767_rule
Checks: C-52020r779322_chk
Verify the operating system has the package required for multifactor authentication installed with the following command: $ sudo yum list installed openssl-pkcs11 openssl-pkcs11.x86_64 0.4.8-2.el8 @anaconda If the "openssl-pkcs11" package is not installed, ask the administrator to indicate what type of multifactor authentication is being used and what packages are installed to support it. If there is no evidence of multifactor authentication being used, this is a finding.
Fix: F-51974r779323_fix
Configure OL 8 to implement multifactor authentication by installing the required package with the following command: $ sudo yum install openssl-pkcs11
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-001948
- Version
- OL08-00-010400
- Vuln IDs
-
- V-248587
- Rule IDs
-
- SV-248587r860917_rule
Checks: C-52021r858603_chk
Verify the operating system implements certificate status checking for multifactor authentication. Note: If the System Administrator demonstrates the use of an approved alternate multifactor authentication method, this requirement is not applicable. Determine if Online Certificate Status Protocol (OCSP) is enabled and using the proper digest value on the system with the following command: $ sudo grep certificate_verification /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf | grep -v "^#" certificate_verification = ocsp_dgst=sha1 If the certificate_verification line is missing from the [sssd] section, or is missing "ocsp_dgst=sha1", ask the administrator to indicate what type of multifactor authentication is being used and how the system implements certificate status checking. If there is no evidence of certificate status checking being used, this is a finding.
Fix: F-51975r818643_fix
Configure OL 8 to implement certificate status checking for multifactor authentication. Review the "/etc/sssd/sssd.conf" file to determine if the system is configured to prevent OCSP or certificate verification. Add the following line to the [sssd] section of the "/etc/sssd/sssd.conf" file: certificate_verification = ocsp_dgst=sha1 The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-001953
- Version
- OL08-00-010410
- Vuln IDs
-
- V-248588
- Rule IDs
-
- SV-248588r853769_rule
Checks: C-52022r779328_chk
Verify OL 8 accepts PIV credentials. Check that the "opensc" package is installed on the system with the following command: $ sudo yum list installed opensc opensc.x86_64 0.19.0-5.el8 @anaconda Check that "opensc" accepts PIV cards with the following command: $ sudo opensc-tool --list-drivers | grep -i piv PIV-II Personal Identity Verification Card If the "opensc" package is not installed and the "opensc-tool" driver list does not include "PIV-II", this is a finding.
Fix: F-51976r779329_fix
Configure OL 8 to accept PIV credentials. Install the "opensc" package using the following command: $ sudo yum install opensc
- RMF Control
- SI-16
- Severity
- Medium
- CCI
- CCI-002824
- Version
- OL08-00-010420
- Vuln IDs
-
- V-248589
- Rule IDs
-
- SV-248589r853770_rule
Checks: C-52023r779331_chk
Verify the NX (no-execution) bit flag is set on the system with the following commands: $ sudo dmesg | grep NX [ 0.000000] NX (Execute Disable) protection: active If "dmesg" does not show "NX (Execute Disable) protection" active, check the "cpuinfo" settings with the following command: $ sudo less /proc/cpuinfo | grep -i flags flags : fpu vme de pse tsc ms nx rdtscp lm constant_tsc If "flags" does not contain the "nx" flag, this is a finding.
Fix: F-51977r779332_fix
Enable the NX bit execute protection in the system BIOS.
- RMF Control
- SC-3
- Severity
- Medium
- CCI
- CCI-001084
- Version
- OL08-00-010421
- Vuln IDs
-
- V-248590
- Rule IDs
-
- SV-248590r779336_rule
Checks: C-52024r779334_chk
Verify that GRUB 2 is configured to enable page poisoning to mitigate use-after-free vulnerabilities with the following commands: $ sudo grub2-editenv list | grep page_poison kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 page_poison=1 vsyscall=none audit=1 audit_backlog_limit=8192 boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If "page_poison" is not set to "1" or is missing, this is a finding. Check that page poisoning is enabled by default to persist in kernel updates: $ sudo grep page_poison /etc/default/grub GRUB_CMDLINE_LINUX="page_poison=1" If "page_poison" is not set to "1" or is missing or commented out, this is a finding.
Fix: F-51978r779335_fix
Configure OL 8 to enable page poisoning with the following commands: $ sudo grubby --update-kernel=ALL --args="page_poison=1" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="page_poison=1"
- RMF Control
- SC-3
- Severity
- Medium
- CCI
- CCI-001084
- Version
- OL08-00-010422
- Vuln IDs
-
- V-248591
- Rule IDs
-
- SV-248591r779339_rule
Checks: C-52025r779337_chk
Verify that GRUB 2 is configured to disable vsyscalls with the following commands: $ sudo grub2-editenv list | grep vsyscall kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 page_poison=1 vsyscall=none audit=1 audit_backlog_limit=8192 boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If "vsyscall" is not set to "none" or is missing, this is a finding. Check that vsyscalls are disabled by default to persist in kernel updates: $ sudo grep vsyscall /etc/default/grub GRUB_CMDLINE_LINUX="vsyscall=none" If "vsyscall" is not set to "none", is missing or commented out and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-51979r779338_fix
Document the use of vsyscalls with the ISSO as an operational requirement or disable them with the following command: $ sudo grubby --update-kernel=ALL --args="vsyscall=none" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="vsyscall=none"
- RMF Control
- SC-3
- Severity
- Medium
- CCI
- CCI-001084
- Version
- OL08-00-010423
- Vuln IDs
-
- V-248592
- Rule IDs
-
- SV-248592r779342_rule
Checks: C-52026r779340_chk
Verify that GRUB 2 is configured to enable poisoning of SLUB/SLAB objects to mitigate use-after-free vulnerabilities with the following commands: Check that the current GRUB 2 configuration has poisoning of SLUB/SLAB objects enabled: $ sudo grub2-editenv list | grep slub_debug kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 slub_debug=P page_poison=1 vsyscall=none audit=1 audit_backlog_limit=8192 boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If "slub_debug" is not set to "P" or is missing, this is a finding. Check that poisoning of SLUB/SLAB objects is enabled by default to persist in kernel updates: $ sudo grep slub_debug /etc/default/grub GRUB_CMDLINE_LINUX="slub_debug=P" If "slub_debug" is not set to "P", is missing or commented out, this is a finding.
Fix: F-51980r779341_fix
Configure OL 8 to enable poisoning of SLUB/SLAB objects with the following commands: $ sudo grubby --update-kernel=ALL --args="slub_debug=P" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="slub_debug=P"
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010424
- Vuln IDs
-
- V-248593
- Rule IDs
-
- SV-248593r779345_rule
Checks: C-52027r779343_chk
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 If the mitigation parameter is set to "off" this is a finding.
Fix: F-51981r779344_fix
Determine the default kernel: $ sudo grubby --default-kernel /boot/vmlinuz-5.4.17-2011.1.2.el8uek.x86_64 Using the default kernel, remove the Meltdown mitigations: $ sudo grubby --update-kernel=<path-to-default-kernel> --remove-args=mitigation=off Reboot the system for the change to take effect.
- RMF Control
- SI-16
- Severity
- Medium
- CCI
- CCI-002824
- Version
- OL08-00-010430
- Vuln IDs
-
- V-248594
- Rule IDs
-
- SV-248594r860918_rule
Checks: C-52028r858625_chk
Verify that OL 8 implements ASLR with the following command: $ sudo sysctl kernel.randomize_va_space kernel.randomize_va_space = 2 If "kernel.randomize_va_space" is not set to "2", this is a finding. Check that the configuration files are present to enable this kernel parameter. $ sudo grep -r kernel.randomize_va_space /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:kernel.randomize_va_space = 2 If "kernel.randomize_va_space" is not set to "2", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51982r858626_fix
Configure OL 8 to implement virtual address space randomization. Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.d/*.conf" (or modify the line to have the required value): kernel.randomize_va_space=2 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Issue the following command to make the changes take effect: $ sudo sysctl --system
- RMF Control
- SI-2
- Severity
- Low
- CCI
- CCI-002617
- Version
- OL08-00-010440
- Vuln IDs
-
- V-248595
- Rule IDs
-
- SV-248595r853773_rule
Checks: C-52029r779349_chk
Verify the operating system removes all software components after updated versions have been installed. Check if YUM is configured to remove unneeded packages with the following command: $ sudo grep -i clean_requirements_on_remove /etc/yum.conf clean_requirements_on_remove=True If "clean_requirements_on_remove" is not set to "True", commented out, or missing from "/etc/yum.conf", this is a finding.
Fix: F-51983r779350_fix
Configure OL 8 to remove all software components after updated versions have been installed. Set the "clean_requirements_on_remove" option to "True" in the "/etc/yum.conf" file: clean_requirements_on_remove=True
- RMF Control
- SI-6
- Severity
- Medium
- CCI
- CCI-002696
- Version
- OL08-00-010450
- Vuln IDs
-
- V-248596
- Rule IDs
-
- SV-248596r853774_rule
Checks: C-52030r779352_chk
Ensure the operating system verifies correct operation of all security functions. Verify that "SELinux" is active and is enforcing the targeted policy with the following command: $ sudo sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 31 If the "Loaded policy name" is not set to "targeted", this is a finding. Verify that the "/etc/selinux/config" file is configured to the "SELINUXTYPE" as "targeted": $ sudo grep -i "selinuxtype" /etc/selinux/config | grep -v '^#' SELINUXTYPE = targeted If no results are returned or "SELINUXTYPE" is not set to "targeted", this is a finding.
Fix: F-51984r779353_fix
Configure OL 8 to verify correct operation of all security functions. Set the "SELinuxtype" to the "targeted" policy by modifying the "/etc/selinux/config" file to have the following line: SELINUXTYPE=targeted A reboot is required for the changes to take effect.
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010460
- Vuln IDs
-
- V-248597
- Rule IDs
-
- SV-248597r779357_rule
Checks: C-52031r779355_chk
Verify there are no "shosts.equiv" files on OL 8 with the following command: $ sudo find / -name shosts.equiv If an "shosts.equiv" file is found, this is a finding.
Fix: F-51985r779356_fix
Remove any found "shosts.equiv" files from the system. $ sudo rm /etc/ssh/shosts.equiv
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010470
- Vuln IDs
-
- V-248598
- Rule IDs
-
- SV-248598r779360_rule
Checks: C-52032r779358_chk
Verify there are no ".shosts" files on OL 8 with the following command: $ sudo find / -name '*.shosts' If any ".shosts" files are found, this is a finding.
Fix: F-51986r779359_fix
Remove any found ".shosts" files from the system. $ sudo rm /[path]/[to]/[file]/.shosts
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010473
- Vuln IDs
-
- V-248599
- Rule IDs
-
- SV-248599r943105_rule
Checks: C-52033r928552_chk
Note: For OL versions 8.4 and above running with kernel FIPS mode enabled as specified by OL08-00-010020, this requirement is Not Applicable. Check that OL 8 has enabled the hardware random number generator entropy gatherer service. Verify the rngd service is enabled and active with the following commands: $ sudo systemctl is-enabled rngd enabled $ sudo systemctl is-active rngd active If the service is not "enabled" and "active", this is a finding.
Fix: F-51987r917909_fix
Start the rngd service and enable it with the following commands: $ sudo systemctl start rngd.service $ sudo systemctl enable rngd.service
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010472
- Vuln IDs
-
- V-248600
- Rule IDs
-
- SV-248600r779366_rule
Checks: C-52034r779364_chk
Check that OL 8 has the packages required to enabled the hardware random number generator entropy gatherer service with the following command: $ sudo yum list installed rng-tools rng-tools.x86_64 6.8-3.el8 @anaconda If the "rng-tools" package is not installed, this is a finding.
Fix: F-51988r779365_fix
Install the packages required to enabled the hardware random number generator entropy gatherer service with the following command: $ sudo yum install rng-tools
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010480
- Vuln IDs
-
- V-248601
- Rule IDs
-
- SV-248601r779369_rule
Checks: C-52035r779367_chk
Verify the SSH public host key files have mode "0644" or less permissive with the following command: $ sudo ls -l /etc/ssh/*.pub -rw-r--r-- 1 root wheel 618 Nov 28 06:43 ssh_host_dsa_key.pub -rw-r--r-- 1 root wheel 347 Nov 28 06:43 ssh_host_key.pub -rw-r--r-- 1 root wheel 238 Nov 28 06:43 ssh_host_rsa_key.pub If any "key.pub" file has a mode more permissive than "0644", this is a finding. Note: SSH public key files may be found in other directories on the system depending on the installation.
Fix: F-51989r779368_fix
Change the mode of public host key files under "/etc/ssh" to "0644" with the following command: $ sudo chmod 0644 /etc/ssh/*key.pub The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010490
- Vuln IDs
-
- V-248602
- Rule IDs
-
- SV-248602r880541_rule
Checks: C-52036r880539_chk
Verify the SSH private host key files have mode "0640" or less permissive with the following command: $ sudo ls -alL /etc/ssh/ssh_host*key -rw-r----- 1 root wheel 668 Nov 28 06:43 ssh_host_dsa_key -rw-r----- 1 root wheel 582 Nov 28 06:43 ssh_host_key -rw-r----- 1 root wheel 887 Nov 28 06:43 ssh_host_rsa_key If any private host key file has a mode more permissive than "0640", this is a finding.
Fix: F-51990r880540_fix
Configure the mode of SSH private host key files under "/etc/ssh" to "0640" with the following command: $ sudo chmod 0640 /etc/ssh/ssh_host*key The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010500
- Vuln IDs
-
- V-248603
- Rule IDs
-
- SV-248603r858568_rule
Checks: C-52037r858567_chk
Verify the SSH daemon performs strict mode checking of home directory configuration files with the following command: $ sudo grep -ir strictmodes /etc/ssh/sshd_config* StrictModes yes If "StrictModes" is set to "no" or is missing, or if the returned line is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51991r779374_fix
Configure SSH to perform strict mode checking of home directory configuration files. Uncomment the "StrictModes" keyword in "/etc/ssh/sshd_config" and set the value to "yes": StrictModes yes The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010520
- Vuln IDs
-
- V-248605
- Rule IDs
-
- SV-248605r858572_rule
Checks: C-52039r858571_chk
Verify the SSH daemon does not allow authentication using known host’s authentication with the following command: $ sudo grep -ir IgnoreUserKnownHosts /etc/ssh/sshd_config* IgnoreUserKnownHosts yes If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51993r779380_fix
Configure the SSH daemon to not allow authentication using known host’s authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes": IgnoreUserKnownHosts yes The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010521
- Vuln IDs
-
- V-248606
- Rule IDs
-
- SV-248606r858574_rule
Checks: C-52040r858573_chk
Verify the SSH daemon does not allow Kerberos authentication with the following command: $ sudo grep -ir "KerberosAuthentication" /etc/ssh/sshd_config* KerberosAuthentication no If the value is returned as "yes", the returned line is commented out, or no output is returned, or has not been documented with the ISSO, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51994r779383_fix
Configure the SSH daemon to not allow Kerberos authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "no": KerberosAuthentication no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010522
- Vuln IDs
-
- V-248607
- Rule IDs
-
- SV-248607r858576_rule
Checks: C-52041r858575_chk
Verify the SSH daemon does not allow GSSAPI authentication with the following command: $ sudo grep -ir GSSAPIAuthentication /etc/ssh/sshd_config* GSSAPIAuthentication no If the value is returned as "yes", the returned line is commented out, no output is returned, or has not been documented with the ISSO, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-51995r779386_fix
Configure the SSH daemon to not allow GSSAPI authentication. Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "no": GSSAPIAuthentication no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010540
- Vuln IDs
-
- V-248608
- Rule IDs
-
- SV-248608r902793_rule
Checks: C-52042r902792_chk
Verify that a separate file system has been created for "/var" with the following command: $ sudo grep /var /etc/fstab /dev/mapper/... /var xfs defaults,nodev 0 0 If a separate entry for "/var" is not in use, this is a finding.
Fix: F-51996r779389_fix
Migrate the "/var" path onto a separate file system.
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010541
- Vuln IDs
-
- V-248609
- Rule IDs
-
- SV-248609r902795_rule
Checks: C-52043r902794_chk
Verify that a separate file system has been created for "/var/log". Check that a file system has been created for "/var/log" with the following command: $ sudo grep /var/log /etc/fstab /dev/mapper/... /var/log xfs defaults,nodev,noexec,nosuid 0 0 If a separate entry for "/var/log" is not in use, this is a finding.
Fix: F-51997r779392_fix
Migrate the "/var/log" path onto a separate file system.
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-010542
- Vuln IDs
-
- V-248610
- Rule IDs
-
- SV-248610r779396_rule
Checks: C-52044r779394_chk
Verify that a separate file system/partition has been created for the system audit data path with the following command: Note: "/var/log/audit" is used as the example as it is a common location. $ sudo grep /var/log/audit /etc/fstab UUID=3645951a /var/log/audit ext4 defaults 1 2 If an entry for "/var/log/audit" does not exist, ask the System Administrator if the system audit logs are being written to a different file system/partition on the system and then grep for that file system/partition. If a separate file system/partition does not exist for the system audit data path, this is a finding.
Fix: F-51998r779395_fix
Migrate the system audit data path onto a separate file system.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010543
- Vuln IDs
-
- V-248611
- Rule IDs
-
- SV-248611r779399_rule
Checks: C-52045r779397_chk
The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. Check Text: Verify that a separate file system/partition has been created for non-privileged local interactive user home directories. $ sudo grep /tmp /etc/fstab /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0 If a separate entry for the file system/partition "/tmp" does not exist, this is a finding.
Fix: F-51999r779398_fix
Migrate the "/tmp" directory onto a separate file system/partition.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010544
- Vuln IDs
-
- V-248612
- Rule IDs
-
- SV-248612r902797_rule
Checks: C-52046r902796_chk
Verify that a separate file system has been created for "/var/tmp". Check that a file system has been created for "/var/tmp" with the following command: $ sudo grep /var/tmp /etc/fstab /dev/mapper/... /var/tmp xfs defaults,nodev,noexec,nosuid 0 0 If a separate entry for "/var/tmp" is not in use, this is a finding.
Fix: F-52000r779401_fix
Migrate the "/var/tmp" path onto a separate file system.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000770
- Version
- OL08-00-010550
- Vuln IDs
-
- V-248613
- Rule IDs
-
- SV-248613r858578_rule
Checks: C-52047r858577_chk
Verify remote access using SSH prevents users from logging on directly as "root" with the following command: $ sudo grep -ir PermitRootLogin /etc/ssh/sshd_config* PermitRootLogin no If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52001r779404_fix
Configure OL 8 to stop users from logging on remotely as the "root" user via SSH. Edit the appropriate "/etc/ssh/sshd_config" file to uncomment or add the line for the "PermitRootLogin" keyword and set its value to "no": PermitRootLogin no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010561
- Vuln IDs
-
- V-248615
- Rule IDs
-
- SV-248615r779411_rule
Checks: C-52049r779409_chk
Verify the rsyslog service is enabled and active with the following commands: $ sudo systemctl is-enabled rsyslog enabled $ sudo systemctl is-active rsyslog active If the service is not enabled and active, this is a finding.
Fix: F-52003r779410_fix
Start and enable the rsyslog service with the following commands: $ sudo systemctl start rsyslog.service $ sudo systemctl enable rsyslog.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010570
- Vuln IDs
-
- V-248616
- Rule IDs
-
- SV-248616r779414_rule
Checks: C-52050r779412_chk
Verify that file systems containing user home directories are mounted with the "nosuid" option. Find the file system(s) that contain the user home directories with the following command: $ sudo awk -F: '($3>=1000)&&($1!="nobody"){print $1,$3,$6}' /etc/passwd smithj 1001 /home/smithj robinst 1002 /home/robinst Check the file systems that are mounted at boot time with the following command: $ sudo more /etc/fstab UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered,nosuid,nodev,noexec 0 2 If a file system found in "/etc/fstab" refers to the user home directory file system and it does not have the "nosuid" option set, this is a finding.
Fix: F-52004r779413_fix
Configure "/etc/fstab" to use the "nosuid" option on file systems that contain user home directories for interactive users.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010571
- Vuln IDs
-
- V-248617
- Rule IDs
-
- SV-248617r779417_rule
Checks: C-52051r779415_chk
For systems that use UEFI, this is Not Applicable. Verify the /boot directory is mounted with the "nosuid" option with the following command: $ sudo mount | grep '\s/boot\s' /dev/sda1 on /boot type xfs (rw,nosuid,relatime,seclabe,attr2,inode64,noquota) If the /boot file system does not have the "nosuid" option set, this is a finding.
Fix: F-52005r779416_fix
Configure the "/etc/fstab" to use the "nosuid" option on the /boot directory.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010572
- Vuln IDs
-
- V-248618
- Rule IDs
-
- SV-248618r818648_rule
Checks: C-52052r818647_chk
For systems that use BIOS, this is Not Applicable. Verify the /boot/efi directory is mounted with the "nosuid" option with the following command: $ sudo mount | grep '\s/boot/efi\s' /dev/sda1 on /boot/efi type vfat (rw,nosuid,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) If the /boot/efi file system does not have the "nosuid" option set, this is a finding.
Fix: F-52006r779419_fix
Configure the "/etc/fstab" to use the "nosuid" option on the /boot/efi directory.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010580
- Vuln IDs
-
- V-248619
- Rule IDs
-
- SV-248619r779423_rule
Checks: C-52053r779421_chk
Verify all non-root local partitions are mounted with the "nodev" option with the following command: $ sudo mount | grep '^/dev\S* on /\S' | grep --invert-match 'nodev' If any output is produced, this is a finding.
Fix: F-52007r779422_fix
Configure the "/etc/fstab" to use the "nodev" option on all non-root local partitions.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010590
- Vuln IDs
-
- V-248620
- Rule IDs
-
- SV-248620r779426_rule
Checks: C-52054r779424_chk
Verify that file systems containing user home directories are mounted with the "noexec" option. Find the file system(s) that contain the user home directories with the following command: $ sudo awk -F: '($3>=1000)&&($1!="nobody"){print $1,$3,$6}' /etc/passwd smithj 1001 /home/smithj robinst 1002 /home/robinst Check the file systems that are mounted at boot time with the following command: $ sudo more /etc/fstab UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered,nosuid,nodev,noexec 0 2 If a file system found in "/etc/fstab" refers to the user home directory file system and it does not have the "noexec" option set, this is a finding.
Fix: F-52008r779425_fix
Configure the "/etc/fstab" to use the "noexec" option on file systems that contain user home directories for interactive users.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010600
- Vuln IDs
-
- V-248621
- Rule IDs
-
- SV-248621r779429_rule
Checks: C-52055r779427_chk
Verify that file systems used for removable media are mounted with the "nodev" option with the following command: $ sudo more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to removable media and it does not have the "nodev" option set, this is a finding.
Fix: F-52009r779428_fix
Configure the "/etc/fstab" to use the "nodev" option on file systems that are associated with removable media.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010610
- Vuln IDs
-
- V-248622
- Rule IDs
-
- SV-248622r779432_rule
Checks: C-52056r779430_chk
Verify that file systems used for removable media are mounted with the "noexec" option with the following command: $ sudo more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to removable media and it does not have the "noexec" option set, this is a finding.
Fix: F-52010r779431_fix
Configure the "/etc/fstab" to use the "noexec" option on file systems that are associated with removable media.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010620
- Vuln IDs
-
- V-248623
- Rule IDs
-
- SV-248623r779435_rule
Checks: C-52057r779433_chk
Verify that file systems used for removable media are mounted with the "nosuid" option with the following command: $ sudo more /etc/fstab UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set, this is a finding.
Fix: F-52011r779434_fix
Configure the "/etc/fstab" to use the "nosuid" option on file systems that are associated with removable media.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010630
- Vuln IDs
-
- V-248624
- Rule IDs
-
- SV-248624r779438_rule
Checks: C-52058r779436_chk
Verify that file systems being imported via NFS are mounted with the "noexec" option with the following command: $ sudo grep nfs /etc/fstab | grep noexec UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to NFS and it does not have the "noexec" option set, this is a finding.
Fix: F-52012r779437_fix
Configure the "/etc/fstab" to use the "noexec" option on file systems that are being imported via NFS.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010640
- Vuln IDs
-
- V-248625
- Rule IDs
-
- SV-248625r779441_rule
Checks: C-52059r779439_chk
Verify that file systems being imported via NFS are mounted with the "nodev" option with the following command: $ sudo grep nfs /etc/fstab | grep nodev UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to NFS and it does not have the "nodev" option set, this is a finding.
Fix: F-52013r779440_fix
Configure the "/etc/fstab" to use the "nodev" option on file systems that are being imported via NFS.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010650
- Vuln IDs
-
- V-248626
- Rule IDs
-
- SV-248626r779444_rule
Checks: C-52060r779442_chk
Verify that file systems being imported via NFS are mounted with the "nosuid" option with the following command: $ sudo grep nfs /etc/fstab | grep nosuid UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid,nodev,noexec 0 0 If a file system found in "/etc/fstab" refers to NFS and it does not have the "nosuid" option set, this is a finding.
Fix: F-52014r779443_fix
Configure the "/etc/fstab" to use the "nosuid" option on file systems that are being imported via NFS.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010660
- Vuln IDs
-
- V-248627
- Rule IDs
-
- SV-248627r779447_rule
Checks: C-52061r779445_chk
Verify that local initialization files do not execute world-writable programs. Check the system for world-writable files. The following command will discover and print world-writable files. Run it once for each local partition [PART]: $ sudo find [PART] -xdev -type f -perm -0002 -print For all files listed, check for their presence in the local initialization files with the following commands: Note: The example will be for a system that is configured to create users' home directories in the "/home" directory. $ sudo grep <file> /home/*/.* If any local initialization files are found to reference world-writable files, this is a finding.
Fix: F-52015r779446_fix
Set the mode on files being executed by the local initialization files with the following command: $ sudo chmod 0755 <file>
- RMF Control
- SC-24
- Severity
- Medium
- CCI
- CCI-001665
- Version
- OL08-00-010670
- Vuln IDs
-
- V-248628
- Rule IDs
-
- SV-248628r779450_rule
Checks: C-52062r779448_chk
Verify that kernel core dumps are disabled unless needed with the following command: $ sudo systemctl status kdump.service kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code)since Mon 2020-05-04 16:08:09 EDT; 3min ago Main PID: 1130 (code=exited, status=0/FAILURE) If the "kdump" service is active, ask the System Administrator if the use of the service is required and documented with the Information System Security Officer (ISSO). If the service is active and is not documented, this is a finding.
Fix: F-52016r779449_fix
If kernel core dumps are not required, disable the "kdump" service with the following command: $ sudo systemctl disable kdump.service If kernel core dumps are required, document the need with the ISSO.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010671
- Vuln IDs
-
- V-248629
- Rule IDs
-
- SV-248629r858629_rule
Checks: C-52063r833215_chk
Verify that OL 8 disables storing core dumps with the following commands: $ sudo sysctl kernel.core_pattern kernel.core_pattern = |/bin/false If the returned line does not have a value of "|/bin/false", or a line is not returned and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Check that the configuration files are present to enable this kernel parameter: $ sudo grep -r kernel.core_pattern /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf:kernel.core_pattern = |/bin/false If "kernel.core_pattern" is not set to "|/bin/false", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52017r858628_fix
Configure OL 8 to disable storing core dumps by adding the following line to a file in the "/etc/sysctl.d" directory: kernel.core_pattern = |/bin/false Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010672
- Vuln IDs
-
- V-248630
- Rule IDs
-
- SV-248630r779456_rule
Checks: C-52064r779454_chk
Verify OL 8 is not configured to acquire, save, or process core dumps with the following command: $ sudo systemctl status systemd-coredump.socket systemd-coredump.socket Loaded: masked (Reason: Unit systemd-coredump.socket is masked.) Active: inactive (dead) If the "systemd-coredump.socket" is loaded and not masked and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-52018r779455_fix
Configure the system to disable the "systemd-coredump.socket" with the following commands: $ sudo systemctl disable --now systemd-coredump.socket $ sudo systemctl mask systemd-coredump.socket Created symlink /etc/systemd/system/systemd-coredump.socket -> /dev/null
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010673
- Vuln IDs
-
- V-248631
- Rule IDs
-
- SV-248631r779459_rule
Checks: C-52065r779457_chk
Verify the operating system disables core dumps for all users with the following command: $ sudo grep -r -s '^[^#].*core' /etc/security/limits.conf /etc/security/limits.d/*.conf * hard core 0 This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. If the "core" item is missing or commented out or the value is anything other than "0", and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.
Fix: F-52019r779458_fix
Configure OL 8 to disable core dumps for all users. Add the following line to the top of "/etc/security/limits.conf" or in a ".conf" file defined in "/etc/security/limits.d/": * hard core 0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010674
- Vuln IDs
-
- V-248632
- Rule IDs
-
- SV-248632r779462_rule
Checks: C-52066r779460_chk
Verify the operating system disables storing core dumps for all users with the following command: $ sudo grep -i storage /etc/systemd/coredump.conf Storage=none If the "Storage" item is missing or commented out or the value is anything other than "none", and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.
Fix: F-52020r779461_fix
Configure OL 8 to disable storing core dumps for all users. Add or modify the following line in "/etc/systemd/coredump.conf": Storage=none
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010675
- Vuln IDs
-
- V-248633
- Rule IDs
-
- SV-248633r779465_rule
Checks: C-52067r779463_chk
Verify the operating system disables core dump backtraces by issuing the following command: $ sudo grep -i ProcessSizeMax /etc/systemd/coredump.conf ProcessSizeMax=0 If the "ProcessSizeMax" item is missing or commented out or the value is anything other than "0", and the need for core dumps is not documented with the Information System Security Officer (ISSO) as an operational requirement for all domains that have the "core" item assigned, this is a finding.
Fix: F-52021r779464_fix
Configure OL 8 to disable core dump backtraces. Add or modify the following line in "/etc/systemd/coredump.conf": ProcessSizeMax=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010680
- Vuln IDs
-
- V-248634
- Rule IDs
-
- SV-248634r779468_rule
Checks: C-52068r779466_chk
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 local host authentication is being used and the "/etc/resolv.conf" file is not empty, this is a finding. If the DNS entry is found on the host's line of the "/etc/nsswitch.conf" file, verify the operating system is configured to use two or more name servers for DNS resolution. Determine the name servers used by the system with the following command: $ sudo grep nameserver /etc/resolv.conf nameserver 192.168.1.2 nameserver 192.168.1.3 If fewer than two lines are returned that are not commented out, this is a finding.
Fix: F-52022r779467_fix
Configure OL 8 to use two or more name servers for DNS resolution. By default, "NetworkManager" on OL 8 dynamically updates the "/etc/resolv.conf" file with the DNS settings from active "NetworkManager" connection profiles. However, this feature can be disabled to allow manual configurations. If manually configuring DNS, edit the "/etc/resolv.conf" file to uncomment or add the two or more "nameserver" option lines with the IP address of local authoritative name servers. If local host resolution is being performed, the "/etc/resolv.conf" file must be empty. An empty "/etc/resolv.conf" file can be created as follows: $ sudo echo -n > /etc/resolv.conf
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010690
- Vuln IDs
-
- V-248635
- Rule IDs
-
- SV-248635r779471_rule
Checks: C-52069r779469_chk
Verify that all local interactive user initialization files' executable search path statements do not contain statements that will reference a working directory other than the users' home directory with the following commands: Note: The example will be for the "smithj" user, which has a home directory of "/home/smithj". $ sudo grep -i path /home/smithj/.* /home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin /home/smithj/.bash_profile:export PATH If any local interactive user initialization files have executable search path statements that include directories outside of their home directory, this is a finding.
Fix: F-52023r779470_fix
Edit the local interactive user initialization files to change any PATH variable statements that reference directories other than their home directory. If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the ISSO.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010700
- Vuln IDs
-
- V-248636
- Rule IDs
-
- SV-248636r779474_rule
Checks: C-52070r779472_chk
The following command will discover and print world-writable directories that are not owned by a system account, given the assumption that only system accounts have a UID lower than 1000. Run it once for each local partition [PART]: $ sudo find [PART] -xdev -type d -perm -0002 -uid +999 -print If there is output, this is a finding.
Fix: F-52024r779473_fix
Investigate any world-writable directories that are not owned by a system account and then delete the files or assign them to an appropriate group.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010710
- Vuln IDs
-
- V-248637
- Rule IDs
-
- SV-248637r779477_rule
Checks: C-52071r779475_chk
The following command will discover and print world-writable directories that are not group-owned by a system account, given the assumption that only system accounts have a gid lower than 1000. Run it once for each local partition [PART]: $ sudo find [PART] -xdev -type d -perm -0002 -gid +999 -print If there is output, this is a finding.
Fix: F-52025r779476_fix
Investigate any world-writable directories that are not group-owned by a system account and then delete the files or assign them to an appropriate group.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010720
- Vuln IDs
-
- V-248638
- Rule IDs
-
- SV-248638r779480_rule
Checks: C-52072r779478_chk
Verify local interactive users on OL 8 have a home directory assigned with the following command: $ sudo pwck -r user 'lp': directory '/var/spool/lpd' does not exist user 'news': directory '/var/spool/news' does not exist user 'uucp': directory '/var/spool/uucp' does not exist user 'www-data': directory '/var/www' does not exist Ask the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command: $ sudo awk -F: '($3>=1000)&&($7 !~ /nologin/){print $1, $3, $6}' /etc/passwd If any interactive users do not have a home directory assigned, this is a finding.
Fix: F-52026r779479_fix
Assign home directories to all local interactive users on OL 8 that currently do not have a home directory assigned.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010730
- Vuln IDs
-
- V-248639
- Rule IDs
-
- SV-248639r779483_rule
Checks: C-52073r779481_chk
Verify the assigned home directory of all local interactive users has a mode of "0750" or less permissive with the following command. Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. $ sudo ls -ld $(awk -F: '($3>=1000)&&($1!="nobody"){print $6}' /etc/passwd) drwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj If home directories of interactive users referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.
Fix: F-52027r779482_fix
Change the mode of interactive users' home directories to "0750" using the following command. Note: The example will be for the user "smithj". $ sudo chmod 0750 /home/smithj
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010731
- Vuln IDs
-
- V-248640
- Rule IDs
-
- SV-248640r779486_rule
Checks: C-52074r779484_chk
Verify all files and directories contained in a local interactive user home directory, excluding local initialization files, have a mode of "0750". Files that begin with a "." are excluded from this requirement. Note: The example will be for the user "smithj", who has a home directory of "/home/smithj". $ sudo ls -lLR /home/smithj -rwxr-x--- 1 smithj smithj 18 Mar 5 17:06 file1 -rwxr----- 1 smithj smithj 193 Mar 5 17:06 file2 -rw-r-x--- 1 smithj smithj 231 Mar 5 17:06 file3 If any files or directories are found with a mode more permissive than "0750", this is a finding.
Fix: F-52028r779485_fix
Set the mode on files and directories in the local interactive user home directory with the following command: Note: The example will be for the user smithj, who has a home directory of "/home/smithj" and is a member of the users group. $ sudo chmod 0750 /home/smithj/<file or directory>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010740
- Vuln IDs
-
- V-248641
- Rule IDs
-
- SV-248641r880567_rule
Checks: C-52075r880565_chk
Verify the assigned home directory of all local interactive users is group-owned by that user’s primary GID with the following command. Note: This may miss local interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. The returned directory "/home/smithj" is used as an example. $ sudo ls -ld $(awk -F: '($3>=1000)&&($1!="nobody"){print $6}' /etc/passwd) drwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj Check the user's primary group with the following command: $ sudo grep $(grep smithj /etc/passwd | awk -F: '{print $4}') /etc/group admin:x:250:smithj,jonesj,jacksons If the user home directory referenced in "/etc/passwd" is not group-owned by that user’s primary GID, this is a finding.
Fix: F-52029r880566_fix
Change the group owner of a local interactive user’s home directory to the group found in "/etc/passwd" using the following command. Note: The example will be for the user "smithj", who has a home directory of "/home/smithj" and has a primary group of users. $ sudo chgrp users /home/smithj
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010741
- Vuln IDs
-
- V-248642
- Rule IDs
-
- SV-248642r779492_rule
Checks: C-52076r779490_chk
Verify all files and directories in a local interactive user home directory are group-owned by a group that the user is a member. Check the group owner of all files and directories in a local interactive user's home directory with the following command: Note: The example will be for the user "smithj", who has a home directory of "/home/smithj". $ sudo ls -lLR /<home directory>/<users home directory>/ -rw-r--r-- 1 smithj smithj 18 Mar 5 17:06 file1 -rw-r--r-- 1 smithj smithj 193 Mar 5 17:06 file2 -rw-r--r-- 1 smithj sa 231 Mar 5 17:06 file3 If any files found with a group-owner different from the home directory user private group, determine if the user is a member of that group with the following command: $ sudo grep smithj /etc/group sa:x:100:juan,shelley,bob,smithj smithj:x:521:smithj If any files or directories are group owned by a group that the directory owner is not a member of, this is a finding.
Fix: F-52030r779491_fix
Change the group of a local interactive user's files and directories to a group that the interactive user is a member. To change the group owner of a local interactive user's files and directories, use the following command: Note: The example will be for the user smithj, who has a home directory of "/home/smithj" and is a member of the users group. $ sudo chgrp smithj /home/smithj/<file or directory>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010750
- Vuln IDs
-
- V-248643
- Rule IDs
-
- SV-248643r779495_rule
Checks: C-52077r779493_chk
Verify that the assigned home directory of all local interactive users on OL 8 exists with the following command: $ sudo ls -ld $(awk -F: '($3>=1000)&&($1!="nobody"){print $6}' /etc/passwd) drwxr-xr-x 2 smithj admin 4096 Jun 5 12:41 smithj Note: This may miss interactive users that have been assigned a privileged User ID (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information. Check that all referenced home directories exist with the following command: $ sudo pwck -r user 'smithj': directory '/home/smithj' does not exist If any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.
Fix: F-52031r779494_fix
Create home directories to all local 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". Note: The example will be for the user smithj, who has a home directory of "/home/smithj", a UID of "smithj", and a Group Identifier (GID) of "users assigned" in "/etc/passwd". $ sudo mkdir /home/smithj $ sudo chown smithj /home/smithj $ sudo chgrp users /home/smithj $ sudo chmod 0750 /home/smithj
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010760
- Vuln IDs
-
- V-248644
- Rule IDs
-
- SV-248644r779498_rule
Checks: C-52078r779496_chk
Verify all local interactive users on OL 8 are assigned a home directory upon creation with the following command: $ sudo grep -i create_home /etc/login.defs CREATE_HOME yes If the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.
Fix: F-52032r779497_fix
Configure OL 8 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
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010770
- Vuln IDs
-
- V-248645
- Rule IDs
-
- SV-248645r779501_rule
Checks: C-52079r779499_chk
Verify that all local initialization files have a mode of "0740" or less permissive with the following command: Note: The example will be for the "smithj" user, who has a home directory of "/home/smithj". $ sudo ls -al /home/smithj/.* | more -rwxr----- 1 smithj users 896 Mar 10 2011 .profile -rwxr----- 1 smithj users 497 Jan 6 2007 .login -rwxr----- 1 smithj users 886 Jan 6 2007 .something If any local initialization files have a mode more permissive than "0740", this is a finding.
Fix: F-52033r779500_fix
Set the mode of the local initialization files to "0740" with the following command: Note: The example will be for the smithj user, who has a home directory of "/home/smithj". $ sudo chmod 0740 /home/smithj/.<INIT_FILE>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010780
- Vuln IDs
-
- V-248646
- Rule IDs
-
- SV-248646r779504_rule
Checks: C-52080r779502_chk
Verify all files and directories on OL 8 have a valid owner with the following command: $ sudo find / -nouser If any files on the system do not have an assigned owner, this is a finding.
Fix: F-52034r779503_fix
Either remove all files and directories from the system that do not have a valid user or assign a valid user to all unowned files and directories on OL 8 with the "chown" command: $ sudo chown <user> <file>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010790
- Vuln IDs
-
- V-248647
- Rule IDs
-
- SV-248647r779507_rule
Checks: C-52081r779505_chk
Verify all files and directories on OL 8 have a valid group with the following command: $ sudo find / -nogroup If any files on the system do not have an assigned group, this is a finding.
Fix: F-52035r779506_fix
Either remove all files and directories from OL 8 that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command: $ sudo chgrp <group> <file>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010800
- Vuln IDs
-
- V-248648
- Rule IDs
-
- SV-248648r902800_rule
Checks: C-52082r902798_chk
Verify that a separate file system has been created for non-privileged local interactive user home directories. Check the home directory assignment for all non-privileged users, users with a User Identifier (UID) greater than 1000, on the system with the following command: $ sudo awk -F: '($3>=1000)&&($1!="nobody"){print $1,$3,$6}' /etc/passwd doej 1001 /home/doej publicj 1002 /home/publicj smithj 1003 /home/smithj The output of the command will give the directory that contains the home directories for the nonprivileged users on the system (in this example, "/home") and users’ shell. All accounts with a valid shell (such as "/bin/bash") are considered interactive users. Check that a file system has been created for the nonprivileged interactive users with the following command. Note: The partition of "/home" is used in the example. $ sudo grep /home /etc/fstab /dev/mapper/... /home xfs defaults,noexec,nosuid,nodev 0 0 If a separate entry for the file system that contains the nonprivileged interactive users' home directories does not exist, this is a finding.
Fix: F-52036r902799_fix
Migrate the "/home" directory onto a separate file system.
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010820
- Vuln IDs
-
- V-248649
- Rule IDs
-
- SV-248649r877377_rule
Checks: C-52083r779511_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system does not allow an unattended or automatic logon to the system via a graphical user interface. Check for the value of "AutomaticLoginEnable" in the "/etc/gdm/custom.conf" file with the following command: $ sudo grep -i automaticloginenable /etc/gdm/custom.conf AutomaticLoginEnable=false If the value of "AutomaticLoginEnable" is not set to "false", this is a finding.
Fix: F-52037r779512_fix
Configure OL 8 to not allow an unattended or automatic logon to the system via a graphical user interface. Add or edit the line for the "AutomaticLoginEnable" parameter in the [daemon] section of the "/etc/gdm/custom.conf" file to "false": [daemon] AutomaticLoginEnable=false
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010830
- Vuln IDs
-
- V-248650
- Rule IDs
-
- SV-248650r877377_rule
Checks: C-52084r858579_chk
Verify that unattended or automatic login via SSH is disabled with the following command: $ sudo grep -ir PermitUserEnvironment /etc/ssh/sshd_config* PermitUserEnvironment no If "PermitUserEnvironment" is set to "yes", is missing completely, or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52038r779515_fix
Configure OL 8 to allow the SSH daemon to not allow unattended or automatic login to the system. Add or edit the following line in the "/etc/ssh/sshd_config" file: PermitUserEnvironment no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000016
- Version
- OL08-00-020000
- Vuln IDs
-
- V-248651
- Rule IDs
-
- SV-248651r779519_rule
Checks: C-52085r779517_chk
Verify that temporary accounts have been provisioned with an expiration date of 72 hours. For every existing temporary account, run the following command to obtain its account expiration information. $ sudo chage -l system_account_name Verify each of these accounts has an expiration date set within 72 hours. If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.
Fix: F-52039r779518_fix
If a temporary account must be created, configure the system to terminate the account after a 72-hour time period with the following command to set an expiration date on it. Substitute "system_account_name" with the account to be created. $ sudo chage -E `date -d "+3 days" +%Y-%m-%d` system_account_name
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020010
- Vuln IDs
-
- V-248652
- Rule IDs
-
- SV-248652r853775_rule
Checks: C-52086r779520_chk
Verify the system locks an account after three unsuccessful logon attempts with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "deny" option is not set to "3" or less (but not "0") on the "preauth" line with the "pam_faillock.so" module or is missing from this line, this is a finding. If any line referencing the "pam_faillock.so" module is commented out, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "deny" option is not set to "3" or less (but not "0") on the "preauth" line with the "pam_faillock.so" module or is missing from this line, this is a finding. If any line referencing the "pam_faillock.so" module is commented out, this is a finding.
Fix: F-52040r779521_fix
Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020011
- Vuln IDs
-
- V-248653
- Rule IDs
-
- SV-248653r853776_rule
Checks: C-52087r779523_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to lock an account after three unsuccessful logon attempts: $ sudo grep 'deny =' /etc/security/faillock.conf deny = 3 If the "deny" option is not set to "3" or less (but not "0") or is missing or commented out, this is a finding.
Fix: F-52041r779524_fix
Configure OL 8 to lock an account when three unsuccessful logon attempts occur. Add/modify the "/etc/security/faillock.conf" file to match the following line: deny = 3
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020012
- Vuln IDs
-
- V-248654
- Rule IDs
-
- SV-248654r853777_rule
Checks: C-52088r779526_chk
Verify the system locks an account after three unsuccessful logon attempts within a period of 15 minutes with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "fail_interval" option is not set to "900" or more on the "preauth" lines with the "pam_faillock.so" module or is missing from this line, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "fail_interval" option is not set to "900" or more on the "preauth" lines with the "pam_faillock.so" module or is missing from this line, this is a finding.
Fix: F-52042r779527_fix
Configure the operating system to lock an account when three unsuccessful logon attempts occur in 15 minutes. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020013
- Vuln IDs
-
- V-248655
- Rule IDs
-
- SV-248655r853778_rule
Checks: C-52089r779529_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to lock an account after three unsuccessful logon attempts within 15 minutes: $ sudo grep 'fail_interval =' /etc/security/faillock.conf fail_interval = 900 If the "fail_interval" option is not set to "900" or more or is missing or commented out, this is a finding.
Fix: F-52043r779530_fix
Configure OL 8 to lock an account when three unsuccessful logon attempts occur. Add/modify the "/etc/security/faillock.conf" file to match the following line: fail_interval = 900
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020014
- Vuln IDs
-
- V-248656
- Rule IDs
-
- SV-248656r853779_rule
Checks: C-52090r779532_chk
Verify the system locks an account after three unsuccessful logon attempts within a period of 15 minutes until released by an administrator with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "unlock_time" option is not set to "0" on the "preauth" and "authfail" lines with the "pam_faillock.so" module or is missing from these lines, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "unlock_time" option is not set to "0" on the "preauth" and "authfail" lines with the "pam_faillock.so" module or is missing from these lines, this is a finding.
Fix: F-52044r779533_fix
Configure the operating system to lock an account until released by an administrator when three unsuccessful logon attempts occur in 15 minutes. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020015
- Vuln IDs
-
- V-248657
- Rule IDs
-
- SV-248657r853780_rule
Checks: C-52091r779535_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to lock an account until released by an administrator after three unsuccessful logon attempts: $ sudo grep 'unlock_time =' /etc/security/faillock.conf unlock_time = 0 If the "unlock_time" option is not set to "0" or is missing or commented out, this is a finding.
Fix: F-52045r779536_fix
Configure OL 8 to lock an account until released by an administrator when three unsuccessful logon attempts occur in 15 minutes. Add/modify the "/etc/security/faillock.conf" file to match the following line: unlock_time = 0
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020016
- Vuln IDs
-
- V-248658
- Rule IDs
-
- SV-248658r853781_rule
Checks: C-52092r779538_chk
Verify the faillock directory contents persist after a reboot with the following commands: Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "dir" option is not set to a non-default documented tally log directory on the "preauth" and "authfail" lines with the "pam_faillock.so" module or is missing from these lines, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "dir" option is not set to a non-default documented tally log directory on the "preauth" and "authfail" lines with the "pam_faillock.so" module or is missing from these lines, this is a finding.
Fix: F-52046r779539_fix
Configure the operating system maintain the contents of the faillock directory after a reboot. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines. Note: Using the default faillock directory of "/var/run/faillock" will result in the contents being cleared in the event of a reboot. auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020017
- Vuln IDs
-
- V-248659
- Rule IDs
-
- SV-248659r853782_rule
Checks: C-52093r779541_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured use a non-default faillock directory to ensure contents persist after reboot: $ sudo grep 'dir =' /etc/security/faillock.conf dir = /var/log/faillock If the "dir" option is not set to a non-default documented tally log directory or is missing or commented out, this is a finding.
Fix: F-52047r779542_fix
Configure OL 8 to maintain the contents of the faillock directory after a reboot. Add/modify the "/etc/security/faillock.conf" file to match the following line: dir = /var/log/faillock
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020018
- Vuln IDs
-
- V-248660
- Rule IDs
-
- SV-248660r853783_rule
Checks: C-52094r779544_chk
Verify the system prevents informative messages from being presented to the user pertaining to logon information with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "silent" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "silent" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding.
Fix: F-52048r779545_fix
Configure the operating system to prevent informative messages from being presented at logon attempts. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020019
- Vuln IDs
-
- V-248661
- Rule IDs
-
- SV-248661r853784_rule
Checks: C-52095r779547_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to prevent informative messages from being presented at logon attempts: $ sudo grep silent /etc/security/faillock.conf silent If the "silent" option is not set or is missing or commented out, this is a finding.
Fix: F-52049r779548_fix
Configure the operating system to prevent informative messages from being presented at logon attempts. Add/modify the "/etc/security/faillock.conf" file to match the following line: silent
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020020
- Vuln IDs
-
- V-248662
- Rule IDs
-
- SV-248662r853785_rule
Checks: C-52096r779550_chk
Verify the system logs user name information when unsuccessful logon attempts occur with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "audit" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "audit" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding.
Fix: F-52050r779551_fix
Configure the operating system to log user name information when unsuccessful logon attempts occur. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020021
- Vuln IDs
-
- V-248663
- Rule IDs
-
- SV-248663r853786_rule
Checks: C-52097r779553_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to log user name information when unsuccessful logon attempts occur: $ sudo grep audit /etc/security/faillock.conf audit If the "audit" option is not set, is missing or commented out, this is a finding.
Fix: F-52051r779554_fix
Configure the operating system to log user name information when unsuccessful logon attempts occur. Add/modify the "/etc/security/faillock.conf" file to match the following line: audit
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020022
- Vuln IDs
-
- V-248664
- Rule IDs
-
- SV-248664r853787_rule
Checks: C-52098r779556_chk
Verify the system includes the root account when locking an account after three unsuccessful logon attempts within a period of 15 minutes with the following commands. Note: If the System Administrator demonstrates the use of an approved centralized account management method that locks an account after three unsuccessful logon attempts within a period of 15 minutes, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "even_deny_root" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding. $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so If the "even_deny_root" option is missing from the "preauth" line with the "pam_faillock.so" module, this is a finding.
Fix: F-52052r779557_fix
Configure the operating system to include root when locking an account after three unsuccessful logon attempts occur in 15 minutes. Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines: auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 account required pam_faillock.so The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020023
- Vuln IDs
-
- V-248665
- Rule IDs
-
- SV-248665r853788_rule
Checks: C-52099r779559_chk
Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the "/etc/security/faillock.conf" file is configured to log user name information when unsuccessful logon attempts occur: $ sudo grep even_deny_root /etc/security/faillock.conf even_deny_root If the "even_deny_root" option is not set or is missing or commented out, this is a finding.
Fix: F-52053r779560_fix
Configure the operating system to include root when locking an account after three unsuccessful logon attempts occur in 15 minutes. Add/modify the "/etc/security/faillock.conf" file to match the following line: even_deny_root
- RMF Control
- AC-10
- Severity
- Low
- CCI
- CCI-000054
- Version
- OL08-00-020024
- Vuln IDs
-
- V-248666
- Rule IDs
-
- SV-248666r877399_rule
Checks: C-52100r779562_chk
Verify the operating system limits the number of concurrent sessions to 10 for all accounts and/or account types by issuing the following command: $ sudo grep "maxlogins" /etc/security/limits.conf /etc/security/limits.d/*.conf * hard maxlogins 10 This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains. If the "maxlogins" item is missing or commented out, or the value is not set to "10" or less for all domains that have the "maxlogins" item assigned, this is a finding.
Fix: F-52054r779563_fix
Configure OL 8 to limit the number of concurrent sessions to 10 for all accounts and/or account types. Add the following line to the top of "/etc/security/limits.conf" or in a ".conf" file defined in "/etc/security/limits.d/": * hard maxlogins 10
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020025
- Vuln IDs
-
- V-248667
- Rule IDs
-
- SV-248667r853789_rule
Checks: C-52101r779565_chk
Note: This check applies to OL versions 8.2 or newer, if the system is OL version 8.0 or 8.1, this check is not applicable. Verify the pam_faillock.so module is present in the "/etc/pam.d/system-auth" file: $ sudo grep pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth auth required pam_faillock.so authfail account required pam_faillock.so If the pam_faillock.so module is not present in the "/etc/pam.d/system-auth" file with the "preauth" line listed before pam_unix.so, this is a finding.
Fix: F-52055r779566_fix
Configure the operating system to include the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. Add/Modify the appropriate sections of the "/etc/pam.d/system-auth" file to match the following lines: Note: The "preauth" line must be listed before pam_unix.so. auth required pam_faillock.so preauth auth required pam_faillock.so authfail account required pam_faillock.so
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020026
- Vuln IDs
-
- V-248668
- Rule IDs
-
- SV-248668r853790_rule
Checks: C-52102r779568_chk
Note: This check applies to OL versions 8.2 or newer, if the system is OL version 8.0 or 8.1, this check is not applicable. Verify the pam_faillock.so module is present in the "/etc/pam.d/password-auth" file: $ sudo grep pam_faillock.so /etc/pam.d/password-auth auth required pam_faillock.so preauth auth required pam_faillock.so authfail account required pam_faillock.so If the pam_faillock.so module is not present in the "/etc/pam.d/password-auth" file with the "preauth" line listed before pam_unix.so, this is a finding.
Fix: F-52056r779569_fix
Configure the operating system to include the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. Add/Modify the appropriate sections of the "/etc/pam.d/password-auth" file to match the following lines: Note: The "preauth" line must be listed before pam_unix.so. auth required pam_faillock.so preauth auth required pam_faillock.so authfail account required pam_faillock.so
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020027
- Vuln IDs
-
- V-248669
- Rule IDs
-
- SV-248669r853791_rule
Checks: C-52103r779571_chk
If the system does not have SELinux enabled and enforcing a targeted policy, or if the pam_faillock module is not configured for use, this requirement is not applicable. Note: This check applies to OL versions 8.2 or newer. If the system is OL version 8.0 or 8.1, this check is not applicable. Verify the location of the non-default tally directory for the pam_faillock module with the following command: $ sudo grep -w dir /etc/security/faillock.conf dir = /var/log/faillock Check the security context type of the non-default tally directory with the following command: $ sudo ls -Zd /var/log/faillock unconfined_u:object_r:faillog_t:s0 /var/log/faillock If the security context type of the non-default tally directory is not "faillog_t", this is a finding.
Fix: F-52057r779572_fix
Configure OL 8 to allow the use of a non-default faillock tally directory while SELinux enforces a targeted policy. Create a non-default faillock tally directory (if it does not already exist) with the following example: $ sudo mkdir /var/log/faillock Update the /etc/selinux/targeted/contexts/files/file_contexts.local with "faillog_t" context type for the non-default faillock tally directory with the following command: $ sudo semanage fcontext -a -t faillog_t "/var/log/faillock(/.*)?" Next, update the context type of the non-default faillock directory/subdirectories and files with the following command: $ sudo restorecon -R -v /var/log/faillock
- RMF Control
- AC-7
- Severity
- Medium
- CCI
- CCI-000044
- Version
- OL08-00-020028
- Vuln IDs
-
- V-248670
- Rule IDs
-
- SV-248670r853792_rule
Checks: C-52104r779574_chk
If the system does not have SELinux enabled and enforcing a targeted policy, or if the pam_faillock module is not configured for use, this requirement is not applicable. Note: This check applies to OL versions 8.0 and 8.1. If the system is OL version 8.2 or newer, this check is not applicable. Verify the location of the non-default tally directory for the pam_faillock module with the following command: $ sudo grep -w dir /etc/pam.d/password-auth auth required pam_faillock.so preauth dir=/var/log/faillock auth required pam_faillock.so authfail dir=/var/log/faillock Check the security context type of the non-default tally directory with the following command: $ sudo ls -Zd /var/log/faillock unconfined_u:object_r:faillog_t:s0 /var/log/faillock If the security context type of the non-default tally directory is not "faillog_t", this is a finding.
Fix: F-52058r779575_fix
Configure OL 8 to allow the use of a non-default faillock tally directory while SELinux enforces a targeted policy. Update the /etc/selinux/targeted/contexts/files/file_contexts.local with "faillog_t" context type for the non-default faillock tally directory with the following command: $ sudo semanage fcontext -a -t faillog_t "/var/log/faillock(/.*)?" Next, update the context type of the non-default faillock directory/subdirectories and files with the following command: $ sudo restorecon -R -v /var/log/faillock
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020030
- Vuln IDs
-
- V-248671
- Rule IDs
-
- SV-248671r779579_rule
Checks: C-52105r779577_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system enables a user's session lock until that user reestablishes access using established identification and authentication procedures with the following command: $ sudo gsettings get org.gnome.desktop.screensaver lock-enabled true If the setting is "false", this is a finding.
Fix: F-52059r779578_fix
Configure OL 8 to enable a user's session lock until that user reestablishes access using established identification and authentication procedures. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following example: $ sudo vi /etc/dconf/db/local.d/00-screensaver Edit the "[org/gnome/desktop/screensaver]" section of the database file and add or update the following lines: # Set this to true to lock the screen when the screensaver activates lock-enabled=true Update the system databases: $ sudo dconf update
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020031
- Vuln IDs
-
- V-248672
- Rule IDs
-
- SV-248672r779582_rule
Checks: C-52106r779580_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system initiates a session lock a for graphical user interfaces when the screensaver is activated with the following command: $ sudo gsettings get org.gnome.desktop.screensaver lock-delay uint32 5 If the "uint32" setting is missing, or is not set to "5" or less, this is a finding.
Fix: F-52060r779581_fix
Configure the operating system to initiate a session lock for graphical user interfaces when a screensaver is activated. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. $ sudo touch /etc/dconf/db/local.d/00-screensaver [org/gnome/desktop/screensaver] lock-delay=uint32 5 The "uint32" must be included along with the integer key values as shown. Update the system databases: $ sudo dconf update
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020032
- Vuln IDs
-
- V-248673
- Rule IDs
-
- SV-248673r779585_rule
Checks: C-52107r779583_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system disables the user logon list for graphical user interfaces with the following command: $ sudo gsettings get org.gnome.login-screen disable-user-list true If the setting is "false", this is a finding.
Fix: F-52061r779584_fix
Configure the operating system to disable the user list at logon for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. $ sudo touch /etc/dconf/db/local.d/02-login-screen [org/gnome/login-screen] disable-user-list=true Update the system databases: $ sudo dconf update
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020039
- Vuln IDs
-
- V-248674
- Rule IDs
-
- SV-248674r779588_rule
Checks: C-52108r779586_chk
Verify OL 8 has the "tmux" package installed, by running the following command: $ sudo yum list installed tmux tmux.x86.64 2.7-1.el8 @repository If "tmux" is not installed, this is a finding.
Fix: F-52062r779587_fix
Configure the operating system to enable a user to initiate a session lock via tmux. Install the "tmux" package, if it is not already installed, by running the following command: $ sudo yum install tmux
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020040
- Vuln IDs
-
- V-248675
- Rule IDs
-
- SV-248675r902786_rule
Checks: C-52109r902785_chk
Verify the operating system enables the user to manually initiate a session lock with the following command: $ sudo grep -Ei 'lock-command|lock-session' /etc/tmux.conf set -g lock-command vlock bind X lock-session If the "lock-command" is not set and "lock-session" is not bound to a specific keyboard key in the global settings, this is a finding.
Fix: F-52063r880563_fix
Configure the operating system to enable a user to manually initiate a session lock via tmux. This configuration binds the uppercase letter "X" to manually initiate a session lock after the prefix key "Ctrl + b" has been sent. The complete key sequence is thus "Ctrl + b" then "Shift + x" to lock tmux. Create a global configuration file "/etc/tmux.conf" and add the following lines: set -g lock-command vlock bind X lock-session Reload tmux configuration to take effect. This can be performed in tmux while it is running: $ tmux source-file /etc/tmux.conf
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020041
- Vuln IDs
-
- V-248676
- Rule IDs
-
- SV-248676r917911_rule
Checks: C-52110r880536_chk
Verify the operating system shell initialization file is configured to start each shell with the tmux terminal multiplexer with the following commands: Determine if tmux is currently running: $ sudo ps all | grep tmux | grep -v grep If the command does not produce output, this is a finding. Determine the location of the tmux script: $ sudo grep tmux /etc/profile.d/* /etc/profile.d/tmux.sh: case "$name" in (sshd|login) tmux ;; esac Review the tmux script by using the following example: $ sudo cat /etc/profile.d/tmux.sh if [ "$PS1" ]; then parent=$(ps -o ppid= -p $$) name=$(ps -o comm= -p $parent) case "$name" in (sshd|login) tmux ;; esac fi If "tmux" is not configured as the example above, is commented out or missing, this is a finding.
Fix: F-52064r880537_fix
Configure the operating system to initialize the tmux terminal multiplexer as each shell is called by adding the following lines to a custom.sh shell script in the /etc/profile.d/ directory: if [ "$PS1" ]; then parent=$(ps -o ppid= -p $$) name=$(ps -o comm= -p $parent) case "$name" in (sshd|login) tmux ;; esac fi This setting will take effect at next logon.
- RMF Control
- AC-11
- Severity
- Low
- CCI
- CCI-000056
- Version
- OL08-00-020042
- Vuln IDs
-
- V-248677
- Rule IDs
-
- SV-248677r779597_rule
Checks: C-52111r779595_chk
Verify the operating system prevents users from disabling the tmux terminal multiplexer with the following command: $ sudo grep -i tmux /etc/shells If any output is produced, this is a finding.
Fix: F-52065r779596_fix
Configure the operating system to prevent users from disabling the tmux terminal multiplexer by editing the "/etc/shells" configuration file to remove any instances of tmux.
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020043
- Vuln IDs
-
- V-248678
- Rule IDs
-
- SV-248678r779600_rule
Checks: C-52112r779598_chk
Verify OL 8 has the "vlock" package installed by running the following command: $ sudo grep vlock /usr/bin/* Binary file /usr/bin/vlock matches If "vlock" is not installed, this is a finding.
Fix: F-52066r779599_fix
Install the "vlock" package, if it is not already installed, by running the following command: $ sudo yum install kbd.x86_64
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000056
- Version
- OL08-00-020050
- Vuln IDs
-
- V-248679
- Rule IDs
-
- SV-248679r818655_rule
Checks: C-52113r818654_chk
Verify the operating system enables a user's session lock until that user reestablishes access using established identification and authentication procedures with the following command: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. $ sudo grep -r removal-action /etc/dconf/db/* /etc/dconf/db/distro.d/20-authselect:removal-action='lock-screen' If the "removal-action='lock-screen'" setting is missing or commented out from the "dconf" database files, this is a finding.
Fix: F-52067r779602_fix
Configure OL 8 to enable a user's session lock until that user reestablishes access using established identification and authentication procedures. Select/create an "authselect" profile and incorporate the "with-smartcard-lock-on-removal" feature as in the following example: $ sudo authselect select sssd with-smartcard with-smartcard-lock-on-removal Alternatively, the "dconf" settings can be edited in the "/etc/dconf/db/*" location. Edit or add the "[org/gnome/settings-daemon/peripherals/smartcard]" section of the database file and add or update the following line: removal-action='lock-screen' Update the system databases: $ sudo dconf update
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020060
- Vuln IDs
-
- V-248680
- Rule IDs
-
- SV-248680r779606_rule
Checks: C-52114r779604_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system initiates a session lock after a 15-minute period of inactivity for graphical user interfaces with the following commands: $ sudo gsettings get org.gnome.desktop.session idle-delay uint32 900 If "idle-delay" is set to "0" or a value greater than "900", this is a finding.
Fix: F-52068r779605_fix
Configure OL 8 to initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: $ sudo touch /etc/dconf/db/local.d/00-screensaver Edit "/etc/dconf/db/local.d/00-screensaver" and add or update the following lines: [org/gnome/desktop/session] # Set the lock time out to 900 seconds before the session is considered idle idle-delay=uint32 900 Update the system databases: $ sudo dconf update
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020070
- Vuln IDs
-
- V-248681
- Rule IDs
-
- SV-248681r779609_rule
Checks: C-52115r779607_chk
Verify the operating system initiates a session lock after 15 minutes of inactivity. Check the value of the system inactivity timeout with the following command: $ sudo grep -i lock-after-time /etc/tmux.conf set -g lock-after-time 900 If "lock-after-time" is not set to "900" or less in the global tmux configuration file to enforce session lock after inactivity, this is a finding.
Fix: F-52069r779608_fix
Configure the operating system to enforce session lock after a period of 15 minutes of inactivity by adding the following line to the "/etc/tmux.conf" global configuration file: set -g lock-after-time 900
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020080
- Vuln IDs
-
- V-248682
- Rule IDs
-
- SV-248682r779612_rule
Checks: C-52116r779610_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system prevents a user from overriding settings for graphical user interfaces. Determine which profile the system database is using with the following command: $ sudo grep system-db /etc/dconf/profile/user system-db:local Check that graphical settings are locked from non-privileged user modification with the following command. Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. $ sudo grep -i lock-delay /etc/dconf/db/local.d/locks/* /org/gnome/desktop/screensaver/lock-delay If the command does not return at least the example result, this is a finding.
Fix: F-52070r779611_fix
Configure OL 8 to prevent a user from overriding settings for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command. Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. $ sudo touch /etc/dconf/db/local.d/locks/session Add the following setting to prevent non-privileged users from modifying it: /org/gnome/desktop/screensaver/lock-delay
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020081
- Vuln IDs
-
- V-248683
- Rule IDs
-
- SV-248683r779615_rule
Checks: C-52117r779613_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system prevents a user from overriding settings for graphical user interfaces. Determine which profile the system database is using with the following command: $ sudo grep system-db /etc/dconf/profile/user system-db:local Check that graphical settings are locked from non-privileged user modification with the following command. Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. $ sudo grep -i idle /etc/dconf/db/local.d/locks/* /org/gnome/desktop/screensaver/idle-delay If the command does not return at least the example result, this is a finding.
Fix: F-52071r779614_fix
Configure OL 8 to prevent a user from overriding settings for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command. Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. $ sudo touch /etc/dconf/db/local.d/locks/session Add the following setting to prevent non-privileged users from modifying it: /org/gnome/desktop/screensaver/idle-delay
- RMF Control
- AC-11
- Severity
- Medium
- CCI
- CCI-000057
- Version
- OL08-00-020082
- Vuln IDs
-
- V-248684
- Rule IDs
-
- SV-248684r779618_rule
Checks: C-52118r779616_chk
Note: This requirement assumes the use of the OL 8 default graphical user interface, Gnome Shell. If the system does not have any graphical user interface installed, this requirement is Not Applicable. Verify the operating system prevents a user from overriding settings for graphical user interfaces. Determine which profile the system database is using with the following command: $ sudo grep system-db /etc/dconf/profile/user system-db:local Check that graphical settings are locked from non-privileged user modification with the following command. Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used. $ sudo grep -i lock-enabled /etc/dconf/db/local.d/locks/* /org/gnome/desktop/screensaver/lock-enabled If the command does not return at least the example result, this is a finding.
Fix: F-52072r779617_fix
Configure OL 8 to prevent a user from overriding settings for graphical user interfaces. Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command. Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory. $ sudo touch /etc/dconf/db/local.d/locks/session Add the following setting to prevent non-privileged users from modifying it: /org/gnome/desktop/screensaver/lock-enabled
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000187
- Version
- OL08-00-020090
- Vuln IDs
-
- V-248685
- Rule IDs
-
- SV-248685r858606_rule
Checks: C-52119r858605_chk
Verify the certificate of the user or group is mapped to the corresponding user or group in the "sssd.conf" file with the following command: Note: If the System Administrator demonstrates the use of an approved alternate multifactor authentication method, this requirement is not applicable. $ sudo cat /etc/sssd/sssd.conf [sssd] config_file_version = 2 services = pam, sudo, ssh domains = testing.test [pam] pam_cert_auth = True [domain/testing.test] id_provider = ldap [certmap/testing.test/rule_name] matchrule =<SAN>.*EDIPI@mil maprule = (userCertificate;binary={cert!bin}) domains = testing.test If the "certmap" section does not exist, this is a finding.
Fix: F-52073r779620_fix
Configure OL 8 to map the authenticated identity to the user or group account by adding or modifying the "certmap" section of the "/etc/sssd/sssd.conf" file based on the following example: [certmap/testing.test/rule_name] matchrule =<SAN>.*EDIPI@mil maprule = (userCertificate;binary={cert!bin}) domains = testing.test The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020100
- Vuln IDs
-
- V-248686
- Rule IDs
-
- SV-248686r902809_rule
Checks: C-52120r902807_chk
Verify the operating system uses "pwquality" to enforce the password complexity rules. Check for the use of "pwquality" in the password-auth file with the following command: $ sudo cat /etc/pam.d/password-auth | grep pam_pwquality password requisite pam_pwquality.so If the command does not return a line containing the value "pam_pwquality.so" as shown, or the line is commented out, this is a finding.
Fix: F-52074r902808_fix
Configure the operating system to use "pwquality" to enforce password complexity rules. Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value): password requisite pam_pwquality.so
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-000192
- Version
- OL08-00-020110
- Vuln IDs
-
- V-248687
- Rule IDs
-
- SV-248687r858631_rule
Checks: C-52121r833219_chk
Verify the value for "ucredit" in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r ucredit /etc/security/pwquality.conf* /etc/security/pwquality.conf:ucredit = -1 If the value of "ucredit" is a positive number or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52075r858630_fix
Configure OL 8 to enforce password complexity by requiring that at least one uppercase character be used by setting the "ucredit" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: ucredit = -1 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-000193
- Version
- OL08-00-020120
- Vuln IDs
-
- V-248688
- Rule IDs
-
- SV-248688r858633_rule
Checks: C-52122r833221_chk
Verify the value for "lcredit" in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r lcredit /etc/security/pwquality.conf* /etc/security/pwquality.conf:lcredit = -1 If the value of "lcredit" is a positive number or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52076r858632_fix
Configure OL 8 to enforce password complexity by requiring that at least one lowercase character be used by setting the "lcredit" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: lcredit = -1 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-000194
- Version
- OL08-00-020130
- Vuln IDs
-
- V-248689
- Rule IDs
-
- SV-248689r858635_rule
Checks: C-52123r833223_chk
Verify the value for "dcredit" in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r dcredit /etc/security/pwquality.conf* /etc/security/pwquality.conf:dcredit = -1 If the value of "dcredit" is a positive number or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52077r858634_fix
Configure OL 8 to enforce password complexity by requiring that at least one numeric character be used by setting the "dcredit" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: dcredit = -1 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000195
- Version
- OL08-00-020140
- Vuln IDs
-
- V-248690
- Rule IDs
-
- SV-248690r858637_rule
Checks: C-52124r833225_chk
Check for the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r maxclassrepeat /etc/security/pwquality.conf* /etc/security/pwquality.conf:maxclassrepeat = 4 If the value of "maxclassrepeat" is set to "0", more than "4" or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52078r858636_fix
Configure OL 8 to require the change of the number of repeating characters of the same character class when passwords are changed by setting the "maxclassrepeat" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: maxclassrepeat = 4 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000195
- Version
- OL08-00-020150
- Vuln IDs
-
- V-248691
- Rule IDs
-
- SV-248691r858639_rule
Checks: C-52125r833227_chk
Check for the value of the "maxrepeat" option in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r maxrepeat /etc/security/pwquality.conf* /etc/security/pwquality.conf:maxrepeat = 3 If the value of "maxrepeat" is set to more than "3" or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52079r858638_fix
Configure OL 8 to require the change of the number of repeating consecutive characters when passwords are changed by setting the "maxrepeat" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: maxrepeat = 3 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000195
- Version
- OL08-00-020160
- Vuln IDs
-
- V-248692
- Rule IDs
-
- SV-248692r858641_rule
Checks: C-52126r833229_chk
Verify the value of the "minclass" option in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r minclass /etc/security/pwquality.conf* /etc/security/pwquality.conf:minclass = 4 If the value of "minclass" is set to less than "4" or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52080r858640_fix
Configure OL 8 to require the change of at least four character classes when passwords are changed by setting the "minclass" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: minclass = 4 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-000195
- Version
- OL08-00-020170
- Vuln IDs
-
- V-248693
- Rule IDs
-
- SV-248693r858643_rule
Checks: C-52127r833231_chk
Verify the value of the "difok" option in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r difok /etc/security/pwquality.conf* /etc/security/pwquality.conf:difok = 8 If the value of "difok" is set to less than "8" or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52081r858642_fix
Configure OL 8 to require the change of at least eight of the total number of characters when passwords are changed by setting the "difok" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: difok = 8 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000198
- Version
- OL08-00-020180
- Vuln IDs
-
- V-248694
- Rule IDs
-
- SV-248694r779648_rule
Checks: C-52128r779646_chk
Verify the minimum time period between password changes for each user account is one day or greater. $ sudo awk -F: '$4 < 1 {print $1 " " $4}' /etc/shadow If any results are returned that are not associated with a system account, this is a finding.
Fix: F-52082r779647_fix
Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime: $ sudo chage -m 1 [user]
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000198
- Version
- OL08-00-020190
- Vuln IDs
-
- V-248695
- Rule IDs
-
- SV-248695r858592_rule
Checks: C-52129r779649_chk
Verify the operating system enforces 24 hours/1 day as the minimum password lifetime for new user accounts. Check for the value of "PASS_MIN_DAYS" in "/etc/login.defs" with the following command: $ sudo grep -i pass_min_days /etc/login.defs PASS_MIN_DAYS 1 If the "PASS_MIN_DAYS" parameter value is not "1" or greater or is commented out, this is a finding.
Fix: F-52083r779650_fix
Configure OL 8 to enforce 24 hours/1 day as the minimum password lifetime. Add the following line in "/etc/login.defs" (or modify the line to have the required value): PASS_MIN_DAYS 1
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000199
- Version
- OL08-00-020200
- Vuln IDs
-
- V-248696
- Rule IDs
-
- SV-248696r779654_rule
Checks: C-52130r779652_chk
Verify that OL 8 enforces a 60-day maximum password lifetime for new user accounts by running the following command: $ sudo grep -i pass_max_days /etc/login.defs PASS_MAX_DAYS 60 If the "PASS_MAX_DAYS" parameter value is greater than "60", or commented out, this is a finding.
Fix: F-52084r779653_fix
Configure OL 8 to enforce a 60-day maximum password lifetime. Add or modify the following line in the "/etc/login.defs" file: PASS_MAX_DAYS 60
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000199
- Version
- OL08-00-020210
- Vuln IDs
-
- V-248697
- Rule IDs
-
- SV-248697r779657_rule
Checks: C-52131r779655_chk
Verify the maximum time period for existing passwords is restricted to 60 days with the following commands: $ sudo awk -F: '$5 > 60 {print $1 " " $5}' /etc/shadow $ sudo awk -F: '$5 <= 0 {print $1 " " $5}' /etc/shadow If any results are returned that are not associated with a system account, this is a finding.
Fix: F-52085r779656_fix
Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction. $ sudo chage -M 60 [user]
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-000200
- Version
- OL08-00-020220
- Vuln IDs
-
- V-248698
- Rule IDs
-
- SV-248698r902821_rule
Checks: C-52132r902819_chk
Verify the operating system is configured in the password-auth file to prohibit password reuse for a minimum of five generations. Check for the value of the "remember" argument in "/etc/pam.d/password-auth" with the following command: $ sudo grep -i remember /etc/pam.d/password-auth password requisite pam_pwhistory.so use_authtok remember=5 retry=3 If the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "5", this is a finding.
Fix: F-52086r902820_fix
Configure the operating system in the password-auth file to prohibit password reuse for a minimum of five generations. Add the following line in "/etc/pam.d/password-auth" (or modify the line to have the required value): password requisite pam_pwhistory.so use_authtok remember=5 retry=3
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000205
- Version
- OL08-00-020230
- Vuln IDs
-
- V-248699
- Rule IDs
-
- SV-248699r858645_rule
Checks: C-52133r833233_chk
Verify the operating system enforces a minimum 15-character password length. The "minlen" option sets the minimum number of characters in a new password. Check for the value of the "minlen" option in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r minlen /etc/security/pwquality.conf* /etc/security/pwquality.conf:minlen = 15 If the command does not return a "minlen" value of 15 or greater or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52087r858644_fix
Configure OL 8 to enforce a minimum 15-character password length. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: minlen = 15 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000205
- Version
- OL08-00-020231
- Vuln IDs
-
- V-248700
- Rule IDs
-
- SV-248700r779666_rule
Checks: C-52134r779664_chk
Verify that OL 8 enforces a minimum 15-character password length for new user accounts by running the following command: $ sudo grep -i pass_min_len /etc/login.defs PASS_MIN_LEN 15 If the "PASS_MIN_LEN" parameter value is less than "15" or is commented out, this is a finding.
Fix: F-52088r779665_fix
Configure operating system to enforce a minimum 15-character password length for new user accounts. Add or modify the following line in the "/etc/login.defs" file: PASS_MIN_LEN 15
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000135
- Version
- OL08-00-020240
- Vuln IDs
-
- V-248701
- Rule IDs
-
- SV-248701r779669_rule
Checks: C-52135r779667_chk
Verify that OL 8 contains no duplicate UIDs for interactive users with the following command: $ sudo awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd If output is produced and the accounts listed are interactive user accounts, this is a finding.
Fix: F-52089r779668_fix
Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate UID with a unique UID.
- RMF Control
- IA-2
- Severity
- Medium
- CCI
- CCI-000765
- Version
- OL08-00-020250
- Vuln IDs
-
- V-248702
- Rule IDs
-
- SV-248702r943098_rule
Checks: C-52136r943096_chk
Verify OL 8 uses multifactor authentication for local access to accounts. Note: If the System Administrator demonstrates the use of an approved alternate multifactor authentication method, this requirement is not applicable. Check that the "pam_cert_auth" setting is set to "true" in the "/etc/sssd/sssd.conf" file. Check that the "try_cert_auth" or "require_cert_auth" options are configured in both "/etc/pam.d/system-auth" and "/etc/pam.d/smartcard-auth" files with the following command: $ sudo grep -ir cert_auth /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf /etc/pam.d/* /etc/sssd/sssd.conf:pam_cert_auth = True /etc/pam.d/smartcard-auth:auth sufficient pam_sss.so try_cert_auth /etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth If "pam_cert_auth" is not set to "true" in "/etc/sssd/sssd.conf", this is a finding. If "pam_sss.so" is not set to "try_cert_auth" or "require_cert_auth" in both the "/etc/pam.d/smartcard-auth" and "/etc/pam.d/system-auth" files, this is a finding.
Fix: F-52090r943097_fix
Configure OL 8 to use multifactor authentication for local access to accounts. Add or update the "pam_cert_auth" setting in the "/etc/sssd/sssd.conf" file to match the following line: [pam] pam_cert_auth = True Add or update "pam_sss.so" with "try_cert_auth" or "require_cert_auth" in the "/etc/pam.d/system-auth" and "/etc/pam.d/smartcard-auth" files based on the following examples: /etc/pam.d/smartcard-auth:auth sufficient pam_sss.so try_cert_auth /etc/pam.d/system-auth:auth [success=done authinfo_unavail=ignore ignore=ignore default=die] pam_sss.so try_cert_auth The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: $ sudo systemctl restart sssd.service
- RMF Control
- IA-4
- Severity
- Medium
- CCI
- CCI-000795
- Version
- OL08-00-020260
- Vuln IDs
-
- V-248703
- Rule IDs
-
- SV-248703r779675_rule
Checks: C-52137r779673_chk
Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity by checking the account inactivity value with the following command: $ sudo grep 'inactive\|pam_unix' /etc/pam.d/system-auth | grep -w auth auth required pam_lastlog.so inactive=35 auth sufficient pam_unix.so If the pam_lastlog.so module is listed below the pam_unix.so module in the "system-auth" file, this is a finding. If the value of "inactive" is set to zero, a negative number, or is greater than 35, this is a finding. If the line is commented out or missing, ask the administrator to indicate how the system disables access for account identifiers. If there is no evidence that the system is disabling access for account identifiers after 35 days of inactivity, this is a finding.
Fix: F-52091r779674_fix
Configure OL 8 to disable access to the system for account identifiers with 35 days of inactivity. Add/Modify the following line to "/etc/pam.d/system-auth" above the "pam_unix.so" statement: auth required pam_lastlog.so inactive=35 Note: The DoD recommendation is 35 days, but a lower value is acceptable.
- RMF Control
- IA-4
- Severity
- Medium
- CCI
- CCI-000795
- Version
- OL08-00-020261
- Vuln IDs
-
- V-248704
- Rule IDs
-
- SV-248704r779678_rule
Checks: C-52138r779676_chk
Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity by checking the account inactivity value with the following command: $ sudo grep 'inactive\|pam_unix' /etc/pam.d/password-auth | grep -w auth auth required pam_lastlog.so inactive=35 auth sufficient pam_unix.so If the pam_lastlog.so module is listed below the pam_unix.so module in the "password-auth" file, this is a finding. If the value of "inactive" is set to zero, a negative number, or is greater than 35, this is a finding. If the line is commented out or missing, ask the administrator to indicate how the system disables access for account identifiers. If there is no evidence that the system is disabling access for account identifiers after 35 days of inactivity, this is a finding.
Fix: F-52092r779677_fix
Configure OL 8 to disable access to the system for account identifiers with 35 days of inactivity. Add/Modify the following line to "/etc/pam.d/password-auth" above the "pam_unix.so" statement: auth required pam_lastlog.so inactive=35 Note: The DoD recommendation is 35 days, but a lower value is acceptable.
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-020262
- Vuln IDs
-
- V-248705
- Rule IDs
-
- SV-248705r779681_rule
Checks: C-52139r779679_chk
Verify the "lastlog" command has a mode of "0750" or less permissive with the following command: $ sudo stat -c "%a %n" /usr/bin/lastlog 750 /usr/bin/lastlog If the "lastlog" command has a mode more permissive than "0750", this is a finding.
Fix: F-52093r779680_fix
Configure the mode of the "lastlog" command for OL 8 to "0750" with the following command: $ sudo chmod 0750 /usr/bin/lastlog
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-020263
- Vuln IDs
-
- V-248706
- Rule IDs
-
- SV-248706r779684_rule
Checks: C-52140r779682_chk
Verify the "lastlog" command is owned by root with the following command: $ sudo ls -l /usr/bin/lastlog -rwxr-x---. 1 root root 21200 Nov 4 22:51 /usr/bin/lastlog If the "lastlog" command is not owned by root, this is a finding.
Fix: F-52094r779683_fix
Configure the "lastlog" command for OL 8 to be owned by root with the following command: $ sudo chown root /usr/bin/lastlog
- RMF Control
- SI-11
- Severity
- Medium
- CCI
- CCI-001314
- Version
- OL08-00-020264
- Vuln IDs
-
- V-248707
- Rule IDs
-
- SV-248707r779687_rule
Checks: C-52141r779685_chk
Verify the "lastlog" command is group-owned by root with the following command: $ sudo ls -l /usr/bin/lastlog -rwxr-x---. 1 root root 21200 Nov 4 22:51 /usr/bin/lastlog If the "lastlog" command is not group-owned by root, this is a finding.
Fix: F-52095r779686_fix
Configure the "lastlog" command for OL 8 to be group-owned by root with the following command: $ sudo chgrp root /usr/bin/lastlog
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-001682
- Version
- OL08-00-020270
- Vuln IDs
-
- V-248708
- Rule IDs
-
- SV-248708r902791_rule
Checks: C-52142r902789_chk
Verify temporary accounts have been provisioned with an expiration date of 72 hours. For every existing temporary account, run the following command to obtain its account expiration information: $ sudo chage -l <temporary_account_name> | grep -i "account expires" Verify each of these accounts has an expiration date set within 72 hours. If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.
Fix: F-52096r902790_fix
Configure the operating system to expire temporary accounts after 72 hours with the following command: $ sudo chage -E $(date -d +3days +%Y-%m-%d) <temporary_account_name>
- RMF Control
- IA-5
- Severity
- Low
- CCI
- CCI-001619
- Version
- OL08-00-020280
- Vuln IDs
-
- V-248709
- Rule IDs
-
- SV-248709r858647_rule
Checks: C-52143r833235_chk
Verify the value for "ocredit" in "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r ocredit /etc/security/pwquality.conf* /etc/security/pwquality.conf:ocredit = -1 If the value of "ocredit" is a positive number or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52097r858646_fix
Configure OL 8 to enforce password complexity by requiring that at least one special character be used by setting the "ocredit" option. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: ocredit = -1 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-002007
- Version
- OL08-00-020290
- Vuln IDs
-
- V-248710
- Rule IDs
-
- SV-248710r943101_rule
Checks: C-52144r943099_chk
Verify that the SSSD prohibits the use of cached authentications after one day. Note: If smart card authentication is not being used on the system, this item is not applicable. Check that SSSD allows cached authentications with the following command: $ sudo grep -ir cache_credentials /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf cache_credentials = true If "cache_credentials" is set to "false" or is missing from the configuration file, this is not a finding and no further checks are required. If "cache_credentials" is set to "true", check that SSSD prohibits the use of cached authentications after one day with the following command: $ sudo grep -ir offline_credentials_expiration /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf offline_credentials_expiration = 1 If "offline_credentials_expiration" is not set to a value of "1", this is a finding.
Fix: F-52098r943100_fix
Configure the SSSD to prohibit the use of cached authentications after one day. Add or change the following line in "/etc/sssd/sssd.conf" just below the line "[pam]". offline_credentials_expiration = 1
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020300
- Vuln IDs
-
- V-248711
- Rule IDs
-
- SV-248711r858649_rule
Checks: C-52145r833237_chk
Verify OL 8 prevents the use of dictionary words for passwords. Determine if the field "dictcheck" is set in the "/etc/security/pwquality.conf" or "/etc/security/pwquality.conf.d/*.conf" files with the following command: $ sudo grep -r dictcheck /etc/security/pwquality.conf* /etc/security/pwquality.conf:dictcheck=1 If the "dictcheck" parameter is not set to "1" or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52099r858648_fix
Configure OL 8 to prevent the use of dictionary words for passwords. Add or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the "/etc/security/pwquality.conf.d/" directory: dictcheck=1 Remove any configurations that conflict with the above value.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020310
- Vuln IDs
-
- V-248712
- Rule IDs
-
- SV-248712r779702_rule
Checks: C-52146r779700_chk
Verify the operating system enforces a delay of at least four seconds between console logon prompts following a failed logon attempt with the following command: $ sudo grep -i fail_delay /etc/login.defs FAIL_DELAY 4 If the value of "FAIL_DELAY" is not set to "4" or greater or the line is commented out, this is a finding.
Fix: F-52100r779701_fix
Configure OL 8 to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt. Modify the "/etc/login.defs" file to set the "FAIL_DELAY" parameter to "4" or greater: FAIL_DELAY 4
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020320
- Vuln IDs
-
- V-248713
- Rule IDs
-
- SV-248713r779705_rule
Checks: C-52147r779703_chk
Verify all accounts on the system are assigned to an active system, application, or user account. Obtain the list of authorized system accounts from the Information System Security Officer (ISSO). Check the system accounts on the system with the following command: $ sudo more /etc/passwd root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt games:x:12:100:games:/usr/games:/sbin/nologin gopher:x:13:30:gopher:/var/gopher:/sbin/nologin Accounts such as "games" and "gopher" are not authorized accounts as they do not support authorized system functions. If the accounts on the system do not match the provided documentation, or accounts that do not support an authorized system function are present, this is a finding.
Fix: F-52101r779704_fix
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. Document all authorized accounts on the system.
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-020330
- Vuln IDs
-
- V-248714
- Rule IDs
-
- SV-248714r858582_rule
Checks: C-52148r858581_chk
To verify that null passwords cannot be used, run the following command: $ sudo grep -ir permitemptypasswords /etc/ssh/sshd_config* PermitEmptyPasswords no If "PermitEmptyPasswords" is set to "yes", this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52102r779707_fix
Edit the following line in "etc/ssh/sshd_config" to prevent logons with empty passwords. PermitEmptyPasswords no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-020331
- Vuln IDs
-
- V-248715
- Rule IDs
-
- SV-248715r779711_rule
Checks: C-52149r779709_chk
To verify that null passwords cannot be used, run the following command: $ sudo grep -i nullok /etc/pam.d/system-auth If output is produced, this is a finding.
Fix: F-52103r779710_fix
Remove any instances of the "nullok" option in the "/etc/pam.d/system-auth" file to prevent logons with empty passwords. Note: Manual changes to the listed file may be overwritten by the "authselect" program.
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-020332
- Vuln IDs
-
- V-248716
- Rule IDs
-
- SV-248716r779714_rule
Checks: C-52150r779712_chk
To verify that null passwords cannot be used, run the following command: $ sudo grep -i nullok /etc/pam.d/password-auth If output is produced, this is a finding.
Fix: F-52104r779713_fix
Remove any instances of the "nullok" option in the "/etc/pam.d/password-auth" file to prevent logons with empty passwords. Note: Manual changes to the listed file may be overwritten by the "authselect" program.
- RMF Control
- AC-9
- Severity
- Low
- CCI
- CCI-000052
- Version
- OL08-00-020340
- Vuln IDs
-
- V-248717
- Rule IDs
-
- SV-248717r858591_rule
Checks: C-52151r779715_chk
Verify users are provided with feedback on when account accesses last occurred with the following command: $ sudo grep pam_lastlog /etc/pam.d/postlogin session required pam_lastlog.so showfailed If "pam_lastlog" is missing from the "/etc/pam.d/postlogin" file or the silent option is present, this is a finding.
Fix: F-52105r779716_fix
Configure OL 8 to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/postlogin". Add the following line to the top of "/etc/pam.d/postlogin": session required pam_lastlog.so showfailed
- RMF Control
- AC-9
- Severity
- Medium
- CCI
- CCI-000052
- Version
- OL08-00-020350
- Vuln IDs
-
- V-248718
- Rule IDs
-
- SV-248718r858584_rule
Checks: C-52152r858583_chk
Verify SSH provides users with feedback on when account accesses last occurred with the following command: $ sudo grep -ir printlastlog /etc/ssh/sshd_config* PrintLastLog yes If the "PrintLastLog" keyword is set to "no", is missing, or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52106r779719_fix
Configure SSH to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/sshd" or in the "sshd_config" file used by the system ("/etc/ssh/sshd_config" will be used in the example). Note that this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor. Modify the "PrintLastLog" line in "/etc/ssh/sshd_config" to match the following: PrintLastLog yes The SSH service must be restarted for changes to "sshd_config" to take effect.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020351
- Vuln IDs
-
- V-248719
- Rule IDs
-
- SV-248719r779723_rule
Checks: C-52153r779721_chk
Verify OL 8 defines default permissions for all authenticated users in such a way that the user can read and modify only their own files with the following command: $ sudo grep -i "umask" /etc/login.defs UMASK 077 If the "UMASK" variable is set to "000", this is a finding with the severity raised to a CAT I. If the value of "UMASK" is not set to "077", "UMASK" is commented out, or "UMASK" is missing completely, this is a finding.
Fix: F-52107r779722_fix
Configure OL 8 to define the default permissions for all authenticated users in such a way that the user can read and modify only their own files. Edit the "UMASK" parameter in the "/etc/login.defs" file to match the example below: UMASK 077
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020352
- Vuln IDs
-
- V-248720
- Rule IDs
-
- SV-248720r858597_rule
Checks: C-52154r858596_chk
Verify that the default umask for all local interactive users is "077". Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file. Check all local interactive user initialization files for interactive users with the following command: Note: The example is for a system that is configured to create users home directories in the "/home" directory. $ sudo grep -ir ^umask /home | grep -v '.bash_history' If any local interactive user initialization files are found to have a umask statement that has a value less restrictive than "077", this is a finding.
Fix: F-52108r779725_fix
Remove the umask statement from all local interactive user's initialization files. If the account is for an application, the requirement for a umask less restrictive than "077" can be documented with the Information System Security Officer, but the user agreement for access to the account must specify that the local interactive user must log on to their account first and then switch the user to the application account with the correct option to gain the account's environment variables.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020353
- Vuln IDs
-
- V-248721
- Rule IDs
-
- SV-248721r818666_rule
Checks: C-52155r818664_chk
Verify that the umask default for installed shells is "077". Check for the value of the "UMASK" parameter in the "/etc/bashrc", "/etc/csh.cshrc", and "/etc/profile" files with the following command: Note: If the value of the "UMASK" parameter is set to "000" in the "/etc/bashrc", "/etc/csh.cshrc", or the "/etc/profile" files, the Severity is raised to a CAT I. $ sudo grep -i umask /etc/bashrc /etc/csh.cshrc /etc/profile /etc/bashrc: umask 077 /etc/bashrc: umask 077 /etc/csh.cshrc: umask 077 /etc/csh.cshrc: umask 077 /etc/profile: umask 077 /etc/profile: umask 077 If the value for the "UMASK" parameter is not "077", or the "UMASK" parameter is missing or is commented out, this is a finding.
Fix: F-52109r818665_fix
Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files. Add or edit the lines for the "UMASK" parameter in the "/etc/bashrc", "etc/csh.cshrc", and "/etc/profile" files to "077": UMASK 077
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002233
- Version
- OL08-00-030000
- Vuln IDs
-
- V-248722
- Rule IDs
-
- SV-248722r853794_rule
Checks: C-52156r779730_chk
Verify OL 8 audits the execution of privileged functions. Check if OL 8 is configured to audit the execution of the "execve" system call, by running the following command: $ sudo grep execve /etc/audit/audit.rules -a always,exit -F arch=b32 -S execve -C uid!=euid -F key=execpriv -a always,exit -F arch=b64 -S execve -C uid!=euid -F key=execpriv -a always,exit -F arch=b32 -S execve -C gid!=egid -F key=execpriv -a always,exit -F arch=b64 -S execve -C gid!=egid -F key=execpriv If the command does not return all lines or the lines are commented out, this is a finding.
Fix: F-52110r779731_fix
Configure OL 8 to audit the execution of the "execve" system call. Add or update the following file system rules to "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S execve -C uid!=euid -F key=execpriv -a always,exit -F arch=b64 -S execve -C uid!=euid -F key=execpriv -a always,exit -F arch=b32 -S execve -C gid!=egid -F key=execpriv -a always,exit -F arch=b64 -S execve -C gid!=egid -F key=execpriv The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-030010
- Vuln IDs
-
- V-248723
- Rule IDs
-
- SV-248723r779735_rule
Checks: C-52157r779733_chk
Verify that "rsyslog" is configured to log cron events with the following command: Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files. $ sudo grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf cron.* /var/log/cron If the command does not return a response, check for cron logging all facilities by inspecting the "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files. Look for the following entry: *.* /var/log/messages If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.
Fix: F-52111r779734_fix
Configure "rsyslog" to log all cron messages by adding or updating the following line to "/etc/rsyslog.conf" or a configuration file in the "/etc/rsyslog.d/" directory: cron.* /var/log/cron The rsyslog daemon must be restarted for the changes to take effect: $ sudo systemctl restart rsyslog.service
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000139
- Version
- OL08-00-030020
- Vuln IDs
-
- V-248724
- Rule IDs
-
- SV-248724r779738_rule
Checks: C-52158r779736_chk
Verify that the SA and ISSO (at a minimum) are notified in the event of an audit processing failure with the following command: $ sudo grep action_mail_acct /etc/audit/auditd.conf action_mail_acct = root If the value of the "action_mail_acct" keyword is not set to "root" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the retuned line is commented out, ask the SA to indicate how they and the ISSO are notified of an audit process failure. If there is no evidence of the proper personnel being notified of an audit processing failure, this is a finding.
Fix: F-52112r779737_fix
Configure the "auditd" service to notify the SA and ISSO in the event of an audit processing failure. Edit the following line in "/etc/audit/auditd.conf" to ensure that administrators are notified via email for those situations: action_mail_acct = root
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000139
- Version
- OL08-00-030030
- Vuln IDs
-
- V-248725
- Rule IDs
-
- SV-248725r779741_rule
Checks: C-52159r779739_chk
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 If the command does not return a line or the line is commented out, this is a finding.
Fix: F-52113r779740_fix
Configure OL 8 to notify administrators in the event of an audit processing failure. Add/update the following line in "/etc/aliases": postmaster: root
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000140
- Version
- OL08-00-030040
- Vuln IDs
-
- V-248726
- Rule IDs
-
- SV-248726r779744_rule
Checks: C-52160r779742_chk
Verify OL 8 takes the appropriate action when an audit processing failure occurs with the following command: $ sudo grep disk_error_action /etc/audit/auditd.conf disk_error_action = HALT If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, this is a finding.
Fix: F-52114r779743_fix
Configure OL 8 to shut down by default upon audit failure (unless availability is an overriding concern). Add or update the following line ("disk_error_action" can be set to "SYSLOG" or "SINGLE" depending on configuration) in the "/etc/audit/auditd.conf" file: disk_error_action = HALT If availability has been determined to be more important, and this decision is documented with the ISSO, configure OL 8 to notify system administration staff and ISSO staff in the event of an audit processing failure by setting the "disk_error_action" to "SYSLOG".
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-000140
- Version
- OL08-00-030060
- Vuln IDs
-
- V-248728
- Rule IDs
-
- SV-248728r779750_rule
Checks: C-52162r779748_chk
Verify OL 8 takes the appropriate action when the audit storage volume is full with the following command: $ sudo grep disk_full_action /etc/audit/auditd.conf disk_full_action = HALT If the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, this is a finding.
Fix: F-52116r779749_fix
Configure OL 8 to shut down by default upon audit failure (unless availability is an overriding concern). Add or update the following line ("disk_full_action" can be set to "SYSLOG" or "SINGLE" depending on configuration) in the "/etc/audit/auditd.conf" file: disk_full_action = HALT If availability has been determined to be more important, and this decision is documented with the ISSO, configure OL 8 to notify system administration staff and ISSO staff in the event of an audit processing failure by setting the "disk_full_action" to "SYSLOG".
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-030061
- Vuln IDs
-
- V-248729
- Rule IDs
-
- SV-248729r779753_rule
Checks: C-52163r779751_chk
Verify the OL 8 Audit Daemon is configured to include local events, with the following command: $ sudo grep local_events /etc/audit/auditd.conf local_events = yes If the value of the "local_events" option is not set to "yes", or the line is commented out, this is a finding.
Fix: F-52117r779752_fix
Configure OL 8 to audit local events on the system. Add or update the following line in "/etc/audit/auditd.conf" file: local_events = yes
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- OL08-00-030062
- Vuln IDs
-
- V-248730
- Rule IDs
-
- SV-248730r877390_rule
Checks: C-52164r779754_chk
Verify the OL 8 audit daemon is configured to label all offloaded audit logs with the following command: $ sudo grep "name_format" /etc/audit/auditd.conf name_format = hostname If the "name_format" option is not "hostname", "fqd", or "numeric", or the line is commented out, this is a finding.
Fix: F-52118r779755_fix
Edit the "/etc/audit/auditd.conf" file and add or update the "name_format" option: name_format = hostname The audit daemon must be restarted for changes to take effect.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-030063
- Vuln IDs
-
- V-248731
- Rule IDs
-
- SV-248731r779759_rule
Checks: C-52165r779757_chk
Verify the OL 8 audit daemon is configured to resolve audit information before writing to disk, with the following command: $ sudo grep "log_format" /etc/audit/auditd.conf log_format = ENRICHED If the "log_format" option is not "ENRICHED", or the line is commented out, this is a finding.
Fix: F-52119r779758_fix
Configure OL 8 to resolve audit information before writing to disk by adding the following line to the "/etc/audit/auditd.conf" file and add or update the "log_format" option: log_format = ENRICHED The audit daemon must be restarted for changes to take effect.
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030070
- Vuln IDs
-
- V-248732
- Rule IDs
-
- SV-248732r779762_rule
Checks: C-52166r779760_chk
Verify the audit logs have a mode of "0600" or less permissive. 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 Using the location of the audit log file, determine if the audit log has a mode of "0600" or less permissive with the following command: $ sudo stat -c "%a %n" /var/log/audit/audit.log 600 /var/log/audit/audit.log If the audit log has a mode more permissive than "0600", this is a finding.
Fix: F-52120r779761_fix
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] Replace "[audit_log_file]" to the correct audit log path. By default, this location is "/var/log/audit/audit.log".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030080
- Vuln IDs
-
- V-248733
- Rule IDs
-
- SV-248733r779765_rule
Checks: C-52167r779763_chk
Verify the audit logs are owned by "root". 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 Using the location of the audit log file, determine if the audit log is owned by "root" using the following command: $ sudo ls -al /var/log/audit/audit.log rw------- 2 root root 23 Jun 11 11:56 /var/log/audit/audit.log If the audit log is not owned by "root", this is a finding.
Fix: F-52121r779764_fix
Configure the audit log to be protected from unauthorized read access by setting the correct owner as "root" with the following command: $ sudo chown root [audit_log_file] Replace "[audit_log_file]" to the correct audit log path. By default, this location is "/var/log/audit/audit.log".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030090
- Vuln IDs
-
- V-248734
- Rule IDs
-
- SV-248734r779768_rule
Checks: C-52168r779766_chk
Verify the audit logs are group-owned by "root". 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 Using the location of the audit log file, determine if the audit log is group-owned by "root" using the following command: $ sudo ls -al /var/log/audit/audit.log rw------- 2 root root 23 Jun 11 11:56 /var/log/audit/audit.log If the audit log is not group-owned by "root", this is a finding.
Fix: F-52122r779767_fix
Configure the audit log to be protected from unauthorized read access by setting the correct group-owner as "root" with the following command: $ sudo chgrp root [audit_log_file] Replace "[audit_log_file]" to the correct audit log path. By default, this location is "/var/log/audit/audit.log".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030100
- Vuln IDs
-
- V-248735
- Rule IDs
-
- SV-248735r779771_rule
Checks: C-52169r779769_chk
Verify the audit log directory is owned by "root" to prevent unauthorized read access. 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 Determine the owner of the audit log directory by using the output of the above command (ex: "/var/log/audit/"). Run the following command with the correct audit log directory path: $ sudo ls -ld /var/log/audit drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit If the audit log directory is not owned by "root", this is a finding.
Fix: F-52123r779770_fix
Configure the audit log to be protected from unauthorized read access by setting the correct owner as "root" with the following command: $ sudo chown root [audit_log_directory] Replace "[audit_log_directory]" with the correct audit log directory path. By default, this location is usually "/var/log/audit".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030110
- Vuln IDs
-
- V-248736
- Rule IDs
-
- SV-248736r779774_rule
Checks: C-52170r779772_chk
Verify the audit log directory is group-owned by "root" to prevent unauthorized read access. 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 Determine the group owner of the audit log directory by using the output of the above command (ex: "/var/log/audit/"). Run the following command with the correct audit log directory path: $ sudo ls -ld /var/log/audit drwx------ 2 root root 23 Jun 11 11:56 /var/log/audit If the audit log directory is not group-owned by "root", this is a finding.
Fix: F-52124r779773_fix
Configure the audit log to be protected from unauthorized read access by setting the correct group-owner as "root" with the following command: $ sudo chgrp root [audit_log_directory] Replace "[audit_log_directory]" with the correct audit log directory path. By default, this location is usually "/var/log/audit".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030120
- Vuln IDs
-
- V-248737
- Rule IDs
-
- SV-248737r779777_rule
Checks: C-52171r779775_chk
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 Using the location of the audit log, determine the directory where the audit logs are stored (ex: "/var/log/audit"). Run the following command to determine the permissions for the audit log folder: $ sudo stat -c "%a %n" /var/log/audit 700 /var/log/audit If the audit log directory has a mode more permissive than "0700", this is a finding.
Fix: F-52125r779776_fix
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] Replace "[audit_log_directory]" to the correct audit log directory path. By default, this location is "/var/log/audit".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030121
- Vuln IDs
-
- V-248738
- Rule IDs
-
- SV-248738r779780_rule
Checks: C-52172r779778_chk
Verify the audit system prevents unauthorized changes with the following command: $ sudo grep "^\s*[^#]" /etc/audit/audit.rules | tail -1 -e 2 If the audit system is not set to be immutable by adding the "-e 2" option to the "/etc/audit/audit.rules", this is a finding.
Fix: F-52126r779779_fix
Configure the audit system to set the audit rules to be immutable by adding the following line to "/etc/audit/rules.d/audit.rules": -e 2 Note: Once set, the system must be rebooted for auditing to be changed. It is recommended to add this option as the last step in securing the system.
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-000162
- Version
- OL08-00-030122
- Vuln IDs
-
- V-248739
- Rule IDs
-
- SV-248739r779783_rule
Checks: C-52173r779781_chk
Verify the audit system prevents unauthorized changes to logon UIDs with the following command: $ sudo grep -i immutable /etc/audit/audit.rules --loginuid-immutable If the login UIDs are not set to be immutable by adding the "--loginuid-immutable" option to the "/etc/audit/audit.rules", this is a finding.
Fix: F-52127r779782_fix
Configure the audit system to set the logon UIDs to be immutable by adding the following line to "/etc/audit/rules.d/audit.rules": --loginuid-immutable
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030130
- Vuln IDs
-
- V-248740
- Rule IDs
-
- SV-248740r853796_rule
Checks: C-52174r779784_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/shadow /etc/audit/audit.rules -w /etc/shadow -p wa -k identity If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52128r779785_fix
Configure OL 8 to generate audit records for all account creations events that affect "/etc/shadow". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/shadow -p wa -k identity The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030140
- Vuln IDs
-
- V-248741
- Rule IDs
-
- SV-248741r853797_rule
Checks: C-52175r779787_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/security/opasswd /etc/audit/audit.rules -w /etc/security/opasswd -p wa -k identity If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52129r779788_fix
Configure OL 8 to generate audit records for all account creations events that affect "/etc/security/opasswd". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/security/opasswd -p wa -k identity The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030150
- Vuln IDs
-
- V-248742
- Rule IDs
-
- SV-248742r853798_rule
Checks: C-52176r779790_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/passwd /etc/audit/audit.rules -w /etc/passwd -p wa -k identity If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52130r779791_fix
Configure OL 8 to generate audit records for all account creations events that affect "/etc/passwd". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/passwd -p wa -k identity The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030160
- Vuln IDs
-
- V-248743
- Rule IDs
-
- SV-248743r853799_rule
Checks: C-52177r779793_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/gshadow /etc/audit/audit.rules -w /etc/gshadow -p wa -k identity If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52131r779794_fix
Configure OL 8 to generate audit records for all account creations events that affect "/etc/gshadow". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/gshadow -p wa -k identity The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030170
- Vuln IDs
-
- V-248744
- Rule IDs
-
- SV-248744r853800_rule
Checks: C-52178r779796_chk
Verify OL 8 generates audit records for all account creations events that affect "/etc/group". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/group /etc/audit/audit.rules -w /etc/group -p wa -k identity If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52132r779797_fix
Configure OL 8 to generate audit records for all account creations events that affect "/etc/group". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/group -p wa -k identity The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030171
- Vuln IDs
-
- V-248745
- Rule IDs
-
- SV-248745r853801_rule
Checks: C-52179r779799_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/sudoers /etc/audit/audit.rules -w /etc/sudoers -p wa -k identity If the command does not return a line, or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52133r779800_fix
Configure OL 8 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/sudoers -p wa -k identity The audit daemon must be restarted for the changes to take effect. $ sudo service auditd restart
- RMF Control
- AC-2
- Severity
- Medium
- CCI
- CCI-000018
- Version
- OL08-00-030172
- Vuln IDs
-
- V-248746
- Rule IDs
-
- SV-248746r853802_rule
Checks: C-52180r779802_chk
Verify OL 8 generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/". Check the auditing rules in "/etc/audit/audit.rules" with the following command: $ sudo grep /etc/sudoers.d/ /etc/audit/audit.rules -w /etc/sudoers.d/ -p wa -k identity If the command does not return a line, or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52134r779803_fix
Configure OL 8 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/". Add or update the following file system rule to "/etc/audit/rules.d/audit.rules": -w /etc/sudoers.d/ -p wa -k identity The audit daemon must be restarted for the changes to take effect. $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030190
- Vuln IDs
-
- V-248747
- Rule IDs
-
- SV-248747r853803_rule
Checks: C-52181r779805_chk
Verify OL 8 generates audit records for any use of the "su" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -iw /usr/bin/su /etc/audit/audit.rules -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52135r779806_fix
Configure OL 8 to generate audit records for any use of the "su" command by adding or updating the following rule in "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030200
- Vuln IDs
-
- V-248748
- Rule IDs
-
- SV-248748r853804_rule
Checks: C-52182r818667_chk
Verify if OL 8 is configured to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by running the following command: $ sudo grep xattr /etc/audit/audit.rules -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod If the command does not return an audit rule for "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52136r818668_fix
Configure OL 8 to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030250
- Vuln IDs
-
- V-248753
- Rule IDs
-
- SV-248753r853805_rule
Checks: C-52187r779823_chk
Verify OL 8 generates an audit event for any use of the "chage" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w chage /etc/audit/audit.rules -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52141r779824_fix
Configure the audit system to generate an audit event for any use of the "chage" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030260
- Vuln IDs
-
- V-248754
- Rule IDs
-
- SV-248754r853806_rule
Checks: C-52188r779826_chk
Verify OL 8 generates an audit record for any use of the "chcon" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w chcon /etc/audit/audit.rules -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52142r779827_fix
Configure the audit system to generate an audit event for any use of the "chcon" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030280
- Vuln IDs
-
- V-248756
- Rule IDs
-
- SV-248756r853807_rule
Checks: C-52190r779832_chk
Verify OL 8 generates an audit record for any use of the "ssh-agent" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep ssh-agent /etc/audit/audit.rules -a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52144r779833_fix
Configure the audit system to generate an audit event for any use of the "ssh-agent" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030290
- Vuln IDs
-
- V-248757
- Rule IDs
-
- SV-248757r853808_rule
Checks: C-52191r779835_chk
Verify OL 8 generates an audit event for any use of the "passwd" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w passwd /etc/audit/audit.rules -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52145r779836_fix
Configure the audit system to generate an audit event for any use of the "passwd" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030300
- Vuln IDs
-
- V-248758
- Rule IDs
-
- SV-248758r853809_rule
Checks: C-52192r779838_chk
Verify OL 8 generates an audit event for any use of the "mount" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w /usr/bin/mount /etc/audit/audit.rules -a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52146r779839_fix
Configure the audit system to generate an audit event for any use of the "mount" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030301
- Vuln IDs
-
- V-248759
- Rule IDs
-
- SV-248759r853810_rule
Checks: C-52193r779841_chk
Verify OL 8 generates an audit event for any use of the "umount" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w /usr/bin/umount /etc/audit/audit.rules -a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52147r779842_fix
Configure the audit system to generate an audit event for any use of the "umount" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030302
- Vuln IDs
-
- V-248760
- Rule IDs
-
- SV-248760r853811_rule
Checks: C-52194r779844_chk
Verify OL 8 generates an audit event for any use of the "mount" syscall by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w mount /etc/audit/audit.rules -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k privileged-mount -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=unset -k privileged-mount If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52148r779845_fix
Configure the audit system to generate an audit event for any use of the "mount" syscall by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k privileged-mount -a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=unset -k privileged-mount The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030310
- Vuln IDs
-
- V-248761
- Rule IDs
-
- SV-248761r853812_rule
Checks: C-52195r779847_chk
Verify OL 8 generates an audit event for any use of the "unix_update" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w "unix_update" /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52149r779848_fix
Configure the audit system to generate an audit event for any use of the "unix_update" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030311
- Vuln IDs
-
- V-248762
- Rule IDs
-
- SV-248762r853813_rule
Checks: C-52196r779850_chk
Verify OL 8 generates an audit event for any use of the "postdrop" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w "postdrop" /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52150r779851_fix
Configure the audit system to generate an audit event for any use of the "postdrop" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030312
- Vuln IDs
-
- V-248763
- Rule IDs
-
- SV-248763r853814_rule
Checks: C-52197r779853_chk
Verify OL 8 generates an audit event for any use of the "postqueue" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w "postqueue" /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52151r779854_fix
Configure the audit system to generate an audit event for any use of the "postqueue" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-12
- Severity
- Medium
- CCI
- CCI-000169
- Version
- OL08-00-030313
- Vuln IDs
-
- V-248764
- Rule IDs
-
- SV-248764r779858_rule
Checks: C-52198r779856_chk
Verify if OL 8 is configured to audit the execution of the "semanage" command by running the following command: $ sudo grep -w semanage /etc/audit/audit.rules a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return all lines or the lines are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52152r779857_fix
Configure OL 8 to audit the execution of the "semanage" command by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-12
- Severity
- Medium
- CCI
- CCI-000169
- Version
- OL08-00-030314
- Vuln IDs
-
- V-248765
- Rule IDs
-
- SV-248765r779861_rule
Checks: C-52199r779859_chk
Verify OL 8 is configured to audit the execution of the "setfiles" command by running the following command: $ sudo grep -w setfiles /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return all lines or the lines are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52153r779860_fix
Configure OL 8 to audit the execution of the "setfiles" command by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/sbin/setfiles -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-12
- Severity
- Medium
- CCI
- CCI-000169
- Version
- OL08-00-030315
- Vuln IDs
-
- V-248766
- Rule IDs
-
- SV-248766r779864_rule
Checks: C-52200r779862_chk
Verify OL 8 is configured to audit the execution of the "userhelper" command by running the following command: $ sudo grep -w userhelper /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return all lines or the lines are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52154r779863_fix
Configure OL 8 to audit the execution of the "userhelper" command by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030316
- Vuln IDs
-
- V-248767
- Rule IDs
-
- SV-248767r853815_rule
Checks: C-52201r779865_chk
Verify OL 8 is configured to audit the execution of the "setsebool" command by running the following command: $ sudo grep -w setsebool /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return all lines or the lines are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52155r779866_fix
Configure OL 8 to audit the execution of the "setsebool" command by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030317
- Vuln IDs
-
- V-248768
- Rule IDs
-
- SV-248768r853816_rule
Checks: C-52202r779868_chk
Verify OL 8 is configured to audit the execution of the "unix_chkpwd" command by running the following command: $ sudo grep -w unix_chkpwd /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update If the command does not return all lines or the lines are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52156r779869_fix
Configure OL 8 to audit the execution of the "unix_chkpwd" command by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F path=/usr/sbin/unix_chkpwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030320
- Vuln IDs
-
- V-248769
- Rule IDs
-
- SV-248769r853817_rule
Checks: C-52203r779871_chk
Verify OL 8 generates an audit record for any use of "ssh-keysign" by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep ssh-keysign /etc/audit/audit.rules -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52157r779872_fix
Configure the audit system to generate an audit event for any use of "ssh-keysign" by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030330
- Vuln IDs
-
- V-248770
- Rule IDs
-
- SV-248770r853818_rule
Checks: C-52204r779874_chk
Verify OL 8 generates an audit record for any use of the "setfacl" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w setfacl /etc/audit/audit.rules -a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52158r779875_fix
Configure the audit system to generate an audit event for any use of the "setfacl" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030340
- Vuln IDs
-
- V-248771
- Rule IDs
-
- SV-248771r853819_rule
Checks: C-52205r779877_chk
Verify OL 8 generates an audit event for any use of the "pam_timestamp_check" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w pam_timestamp_check /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52159r779878_fix
Configure the audit system to generate an audit event for any use of the "pam_timestamp_check" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030350
- Vuln IDs
-
- V-248772
- Rule IDs
-
- SV-248772r853820_rule
Checks: C-52206r779880_chk
Verify OL 8 generates an audit record for any use of the "newgrp" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w newgrp /etc/audit/audit.rules -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52160r779881_fix
Configure the audit system to generate an audit event for any use of the "newgrp" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030360
- Vuln IDs
-
- V-248773
- Rule IDs
-
- SV-248773r853821_rule
Checks: C-52207r818670_chk
Verify OL 8 generates an audit record for any use of the "init_module" and "finit_module" system calls by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep init_module /etc/audit/audit.rules -a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng If the command does not return an audit rule for "init_module" and "finit_module" or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52161r818671_fix
Configure the audit system to generate an audit event for any use of the "init_module" and "finit_module" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng -a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030361
- Vuln IDs
-
- V-248774
- Rule IDs
-
- SV-248774r853822_rule
Checks: C-52208r818673_chk
Verify OL 8 is configured to generate audit records for any use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by running the following command: $ sudo grep 'rename\|unlink\|rmdir' /etc/audit/audit.rules -a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete -a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid>=1000 -F auid!=unset -k delete If the command does not return an audit rule for "rename", "unlink", "rmdir", "renameat" and "unlinkat" or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52162r818674_fix
Configure OL 8 to generate audit records for any use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by adding or updating the following lines to "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F success=1 -F auid>=1000 -F auid!=unset -k delete -a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F success=1 -F auid>=1000 -F auid!=unset -k delete The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030370
- Vuln IDs
-
- V-248779
- Rule IDs
-
- SV-248779r853823_rule
Checks: C-52213r779901_chk
Verify OL 8 generates an audit event for any use of the "gpasswd" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w gpasswd /etc/audit/audit.rules -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52167r779902_fix
Configure the audit system to generate an audit event for any use of the "gpasswd" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030390
- Vuln IDs
-
- V-248781
- Rule IDs
-
- SV-248781r853824_rule
Checks: C-52215r779907_chk
Verify OL 8 generates an audit record for any use of the "delete_module" syscall by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w "delete_module" /etc/audit/audit.rules -a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52169r779908_fix
Configure the audit system to generate an audit event for any use of the "delete_module" syscall by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng -a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030400
- Vuln IDs
-
- V-248782
- Rule IDs
-
- SV-248782r853825_rule
Checks: C-52216r779910_chk
Verify OL 8 generates an audit event for any use of the "crontab" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w crontab /etc/audit/audit.rules -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52170r779911_fix
Configure the audit system to generate an audit event for any use of the "crontab" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030410
- Vuln IDs
-
- V-248783
- Rule IDs
-
- SV-248783r853826_rule
Checks: C-52217r779913_chk
Verify OL 8 generates an audit record for any use of the "chsh" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w chsh /etc/audit/audit.rules -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52171r779914_fix
Configure the audit system to generate an audit event for any use of the "chsh" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030420
- Vuln IDs
-
- V-248784
- Rule IDs
-
- SV-248784r853827_rule
Checks: C-52218r818676_chk
Verify OL 8 generates an audit record for any use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep 'open\|truncate\|creat' /etc/audit/audit.rules -a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access If the output does not produce rules containing "-F exit=-EPERM", this is a finding. If the output does not produce rules containing "-F exit=-EACCES", this is a finding. If the command does not return an audit rule for "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52172r818677_fix
Configure the audit system to generate an audit event for any use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access -a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030480
- Vuln IDs
-
- V-248790
- Rule IDs
-
- SV-248790r853828_rule
Checks: C-52224r818679_chk
Verify OL 8 generates an audit record for any use of the "chown", "fchown", "fchownat", and "lchown" system calls by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep chown /etc/audit/audit.rules -a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng -a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng If audit rules are not defined for "chown", "fchown", "fchownat", and "lchown" or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52178r818680_fix
Configure the audit system to generate an audit event for any use of the "chown", "fchown", "fchownat", and "lchown" system calls by adding or updating the following line to "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng -a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030490
- Vuln IDs
-
- V-248791
- Rule IDs
-
- SV-248791r853829_rule
Checks: C-52225r818682_chk
Verify OL 8 generates an audit record for any use of the "chmod","fchmod", and "fchmodat" syscalls by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep chmod /etc/audit/audit.rules -a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng -a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng If the command does not return an audit rule for "chmod", "fchmod", and "fchmodat", or any of the lines returned are commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52179r818683_fix
Configure the audit system to generate an audit event for any use of the "chmod", "fchmod", and "fchmodat" syscalls by adding or updating the following line to "/etc/audit/rules.d/audit.rules": -a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng -a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030550
- Vuln IDs
-
- V-248797
- Rule IDs
-
- SV-248797r853830_rule
Checks: C-52231r779955_chk
Verify OL 8 generates an audit event for any use of the "sudo" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w sudo /etc/audit/audit.rules -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52185r779956_fix
Configure the audit system to generate an audit event for any use of the "sudo" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030560
- Vuln IDs
-
- V-248798
- Rule IDs
-
- SV-248798r853831_rule
Checks: C-52232r779958_chk
Verify OL 8 generates an audit event for any use of the "usermod" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w usermod /etc/audit/audit.rules -a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52186r779959_fix
Configure the audit system to generate an audit event for any use of the "usermod" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030570
- Vuln IDs
-
- V-248799
- Rule IDs
-
- SV-248799r853832_rule
Checks: C-52233r779961_chk
Verify OL 8 generates an audit record for any use of the "chacl" command by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w chacl /etc/audit/audit.rules -a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52187r779962_fix
Configure the audit system to generate an audit event for any use of the "chacl" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030580
- Vuln IDs
-
- V-248800
- Rule IDs
-
- SV-248800r853833_rule
Checks: C-52234r779964_chk
Verify OL 8 is configured to audit the execution of the module management program "kmod" by running the following command: $ sudo grep "/usr/bin/kmod" /etc/audit/audit.rules -w /usr/bin/kmod -p x -k modules If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52188r779965_fix
Configure OL 8 to audit the execution of the module management program "kmod" by adding or updating the following line to "/etc/audit/rules.d/audit.rules": -w /usr/bin/kmod -p x -k modules The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030590
- Vuln IDs
-
- V-248801
- Rule IDs
-
- SV-248801r853834_rule
Checks: C-52235r779967_chk
Verify OL 8 generates an audit record for any attempted modifications to the "faillock" file. Determine where the faillock tallies are stored with the following commands: For OL versions 8.0 and 8.1: $ sudo grep -i pam_faillock.so /etc/pam.d/system-auth auth required pam_faillock.so preauth dir=/var/log/faillock silent deny=3 fail_interval=900 even_deny_root For OL versions 8.2 and newer: $ sudo grep dir /etc/security/faillock.conf dir=/var/log/faillock Using the location of the faillock log file, check that the following calls are being audited by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w faillock /etc/audit/audit.rules -w /var/log/faillock -p wa -k logins If the command does not return a line or the line is commented out, this is a finding.
Fix: F-52189r779968_fix
Configure the audit system to generate an audit event for any attempted modifications to the "faillock" file by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -w /var/log/faillock -p wa -k logins The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030600
- Vuln IDs
-
- V-248802
- Rule IDs
-
- SV-248802r853835_rule
Checks: C-52236r779970_chk
Verify OL 8 generates an audit record for any attempted modifications to the "lastlog" file by running the following command to check the file system rules in "/etc/audit/audit.rules": $ sudo grep -w lastlog /etc/audit/audit.rules -w /var/log/lastlog -p wa -k logins If the command does not return a line or the line is commented out, this is a finding. Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
Fix: F-52190r779971_fix
Configure the audit system to generate an audit event for any attempted modifications to the "lastlog" file by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file: -w /var/log/lastlog -p wa -k logins The audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command: $ sudo service auditd restart
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000130
- Version
- OL08-00-030601
- Vuln IDs
-
- V-248803
- Rule IDs
-
- SV-248803r853836_rule
Checks: C-52237r779973_chk
Verify OL 8 enables auditing of processes that start prior to the audit daemon with the following commands: $ sudo grub2-editenv list | grep audit kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 audit=1 audit_backlog_limit=8192 boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If the "audit" entry does not equal "1", is missing, or the line is commented out, this is a finding. Check that auditing is enabled by default to persist in kernel updates: $ sudo grep audit /etc/default/grub GRUB_CMDLINE_LINUX="audit=1" If "audit" is not set to "1", is missing or commented out, this is a finding.
Fix: F-52191r779974_fix
Configure OL 8 to audit processes that start prior to the audit daemon with the following command: $ sudo grubby --update-kernel=ALL --args="audit=1" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="audit=1"
- RMF Control
- AU-3
- Severity
- Low
- CCI
- CCI-000130
- Version
- OL08-00-030602
- Vuln IDs
-
- V-248804
- Rule IDs
-
- SV-248804r853837_rule
Checks: C-52238r779976_chk
Verify OL 8 allocates a sufficient "audit_backlog_limit" to capture processes that start prior to the audit daemon with the following commands: $ sudo grub2-editenv list | grep audit kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 audit=1 audit_backlog_limit=8192 boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If the "audit_backlog_limit" entry does not equal "8192" or larger, is missing, or the line is commented out, this is a finding. Verify "audit_backlog_limit" is set to persist in kernel updates: $ sudo grep audit /etc/default/grub GRUB_CMDLINE_LINUX="audit_backlog_limit=8192" If "audit_backlog_limit" is not set to "8192" or larger or is missing or commented out, this is a finding.
Fix: F-52192r779977_fix
Configure OL 8 to allocate sufficient "audit_backlog_limit" to capture processes that start prior to the audit daemon with the following command: $ sudo grubby --update-kernel=ALL --args="audit_backlog_limit=8192" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="audit_backlog_limit=8192" If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.
- RMF Control
- AU-12
- Severity
- Medium
- CCI
- CCI-000172
- Version
- OL08-00-030603
- Vuln IDs
-
- V-248805
- Rule IDs
-
- SV-248805r779981_rule
Checks: C-52239r779979_chk
Verify OL 8 enables Linux audit logging of the USBGuard daemon with the following commands. Note: If the USBGuard daemon is not installed and enabled, this requirement is not applicable. $ sudo grep -i auditbackend /etc/usbguard/usbguard-daemon.conf AuditBackend=LinuxAudit If the "AuditBackend" entry does not equal "LinuxAudit", is missing, or the line is commented out, this is a finding.
Fix: F-52193r779980_fix
Configure OL 8 to enable Linux audit logging of the USBGuard daemon by adding or modifying the following line in "/etc/usbguard/usbguard-daemon.conf": AuditBackend=LinuxAudit
- RMF Control
- AU-12
- Severity
- Medium
- CCI
- CCI-000171
- Version
- OL08-00-030610
- Vuln IDs
-
- V-248806
- Rule IDs
-
- SV-248806r779984_rule
Checks: C-52240r779982_chk
Verify that the "/etc/audit/rules.d/audit.rules" and "/etc/audit/auditd.conf" file have a mode of "0640" or less permissive by using the following commands: $ sudo ls -al /etc/audit/rules.d/audit.rules -rw-r----- 1 root root 1280 Feb 16 17:09 audit.rules $ sudo ls -al /etc/audit/auditd.conf -rw-r----- 1 root root 621 Sep 22 2014 auditd.conf If the "/etc/audit/rules.d/audit.rules" or "/etc/audit/auditd.conf" files have a mode more permissive than "0640", this is a finding.
Fix: F-52194r779983_fix
Configure the "/etc/audit/rules.d/audit.rules" and "/etc/audit/auditd.conf" files to have a mode of "0640" with the following commands: $ sudo chmod 0640 /etc/audit/rules.d/audit.rules $ sudo chmod 0640 /etc/audit/auditd.conf
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-001493
- Version
- OL08-00-030620
- Vuln IDs
-
- V-248807
- Rule IDs
-
- SV-248807r779987_rule
Checks: C-52241r779985_chk
Verify the audit tools are protected from unauthorized access, deletion, or modification by checking the permissive mode. Check the octal permission of each audit tool by running the following command: $ sudo stat -c "%a %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules 755 /sbin/auditctl 755 /sbin/aureport 755 /sbin/ausearch 750 /sbin/autrace 755 /sbin/auditd 755 /sbin/rsyslogd 755 /sbin/augenrules If any of the audit tools has a mode more permissive than "0755", this is a finding.
Fix: F-52195r779986_fix
Configure the audit tools to be protected from unauthorized access by setting the correct permissive mode using the following command: $ sudo chmod 0755 [audit_tool] Replace "[audit_tool]" with the audit tool that does not have the correct permissive mode.
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-001493
- Version
- OL08-00-030630
- Vuln IDs
-
- V-248808
- Rule IDs
-
- SV-248808r779990_rule
Checks: C-52242r779988_chk
Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification. Check the owner of each audit tool by running the following command: $ sudo stat -c "%U %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules root /sbin/auditctl root /sbin/aureport root /sbin/ausearch root /sbin/autrace root /sbin/auditd root /sbin/rsyslogd root /sbin/augenrules If any of the audit tools are not owned by "root", this is a finding.
Fix: F-52196r779989_fix
Configure the audit tools to be owned by "root" by running the following command: $ sudo chown root [audit_tool] Replace "[audit_tool]" with each audit tool not owned by "root".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-001493
- Version
- OL08-00-030640
- Vuln IDs
-
- V-248809
- Rule IDs
-
- SV-248809r779993_rule
Checks: C-52243r779991_chk
Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification. Check the owner of each audit tool by running the following commands: $ sudo stat -c "%G %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/rsyslogd /sbin/augenrules root /sbin/auditctl root /sbin/aureport root /sbin/ausearch root /sbin/autrace root /sbin/auditd root /sbin/rsyslogd root /sbin/augenrules If any of the audit tools are not group-owned by "root", this is a finding.
Fix: F-52197r779992_fix
Configure the audit tools to be group-owned by "root" by running the following command: $ sudo chgrp root [audit_tool] Replace "[audit_tool]" with each audit tool not group-owned by "root".
- RMF Control
- AU-9
- Severity
- Medium
- CCI
- CCI-001496
- Version
- OL08-00-030650
- Vuln IDs
-
- V-248810
- Rule IDs
-
- SV-248810r880559_rule
Checks: C-52244r880558_chk
Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured to use cryptographic mechanisms to protect the integrity of audit tools. Check the selection lines to ensure AIDE is configured to add/check with the following command: $ sudo grep -E '(\/usr\/sbin\/(audit|au|rsys))' /etc/aide.conf /usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/rsyslogd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 If any of the audit tools listed above do not have an appropriate selection line, this is a finding.
Fix: F-52198r833240_fix
Add or update the following lines to "/etc/aide.conf" to protect the integrity of the audit tools. # Audit Tools /usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/rsyslogd p+i+n+u+g+s+b+acl+xattrs+sha512 /usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001849
- Version
- OL08-00-030660
- Vuln IDs
-
- V-248811
- Rule IDs
-
- SV-248811r877391_rule
Checks: C-52245r818685_chk
Verify OL 8 allocates 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. Determine to which partition the audit records are being written with the following command: $ sudo grep -iw log_file /etc/audit/auditd.conf log_file = /var/log/audit/audit.log Check the size of the partition to which audit records are written (with the example being "/var/log/audit/") with the following command: $ sudo df -h /var/log/audit/ /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit If the audit records are not written to a partition made specifically for audit records ("/var/log/audit" is a separate partition), determine the amount of space being used by other files in the partition with the following command: $ sudo du -sh [audit_partition] 1.8G /var/log/audit If the audit record partition is not allocated for sufficient storage capacity, this is a finding. Note: The partition size needed to capture a week of audit records is based on the activity level of the system and the total storage capacity available. Typically 10.0 GB of storage space for audit records should be sufficient.
Fix: F-52199r779998_fix
Allocate enough storage capacity for at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. If audit records are stored on a partition made specifically for audit records, use the "X" program to resize the partition with sufficient space to contain one week of audit records. If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-030670
- Vuln IDs
-
- V-248812
- Rule IDs
-
- SV-248812r780002_rule
Checks: C-52246r780000_chk
Verify the operating system has the packages required for offloading audit logs installed with the following commands: $ sudo yum list installed rsyslog rsyslog.x86_64 8.1911.0-3.el8 @AppStream If the "rsyslog" package is not installed, ask the administrator to indicate how audit logs are being offloaded and what packages are installed to support it. If there is no evidence of audit logs being offloaded, this is a finding.
Fix: F-52200r780001_fix
Configure the operating system to offload audit logs by installing the required packages with the following command: $ sudo yum install rsyslog
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-030680
- Vuln IDs
-
- V-248813
- Rule IDs
-
- SV-248813r780005_rule
Checks: C-52247r780003_chk
Verify the operating system has the packages required for encrypting offloaded audit logs installed with the following commands: $ sudo yum list installed rsyslog-gnutls rsyslog-gnutls.x86_64 8.1911.0-6.el8 @AppStream If the "rsyslog-gnutls" package is not installed, ask the administrator to indicate how audit logs are being encrypted during offloading and what packages are installed to support it. If there is no evidence of audit logs being encrypted during offloading, this is a finding.
Fix: F-52201r780004_fix
Configure the operating system to encrypt offloaded audit logs by installing the required packages with the following command: $ sudo yum install rsyslog-gnutls
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- OL08-00-030690
- Vuln IDs
-
- V-248814
- Rule IDs
-
- SV-248814r917914_rule
Checks: C-52248r917912_chk
Verify the audit system offloads audit records onto a different system or media from the system being audited with the following command: $ sudo grep @@ /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.conf:*.* @@[logaggregationserver.example.mil]:[port] If a remote server is not configured or the line is commented out, ask the system administrator to indicate how the audit logs are offloaded to a different system or media. If there is no evidence that the audit logs are being offloaded to another system or media, this is a finding.
Fix: F-52202r917913_fix
Configure OL 8 to offload audit records onto a different system or media from the system being audited by specifying the remote logging server in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf" with the name or IP address of the log aggregation server. For UDP: *.* @[logaggregationserver.example.mil]:[port] For TCP: *.* @@[logaggregationserver.example.mil]:[port]
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- OL08-00-030700
- Vuln IDs
-
- V-248815
- Rule IDs
-
- SV-248815r877390_rule
Checks: C-52249r780009_chk
Verify the audit system is configured to take an appropriate action when the internal event queue is full: $ sudo grep -i overflow_action /etc/audit/auditd.conf overflow_action = syslog If the value of the "overflow_action" option is not set to "syslog", "single", or "halt", or the line is commented out, ask the System Administrator to indicate how the audit logs are offloaded to a different system or media. If there is no evidence that the transfer of the audit logs being offloaded to another system or media takes appropriate action if the internal event queue becomes full, this is a finding.
Fix: F-52203r780010_fix
Edit the "/etc/audit/auditd.conf" file and add or update the "overflow_action" option: overflow_action = syslog The audit daemon must be restarted for changes to take effect.
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- OL08-00-030710
- Vuln IDs
-
- V-248816
- Rule IDs
-
- SV-248816r877390_rule
Checks: C-52250r818687_chk
Verify the operating system encrypts audit records offloaded onto a different system or media from the system being audited with the following commands: $ sudo grep -i '$DefaultNetstreamDriver' /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.conf:$DefaultNetstreamDriver gtls If the value of the "$DefaultNetstreamDriver" option is not set to "gtls" or the line is commented out, this is a finding. $ sudo grep -i '$ActionSendStreamDriverMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.conf:$ActionSendStreamDriverMode 1 If the value of the "$ActionSendStreamDriverMode" option is not set to "1" or the line is commented out, this is a finding. If neither of the definitions above are set, ask the System Administrator to indicate how the audit logs are offloaded to a different system or media. If there is no evidence that the transfer of the audit logs being offloaded to another system or media is encrypted, this is a finding.
Fix: F-52204r780013_fix
Configure the operating system to encrypt offloaded audit records by setting the following options in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf": $DefaultNetstreamDriver gtls $ActionSendStreamDriverMode 1
- RMF Control
- AU-4
- Severity
- Medium
- CCI
- CCI-001851
- Version
- OL08-00-030720
- Vuln IDs
-
- V-248817
- Rule IDs
-
- SV-248817r877390_rule
Checks: C-52251r780015_chk
Verify the operating system authenticates the remote logging server for offloading audit logs with the following command: $ sudo grep -i '$ActionSendStreamDriverAuthMode' /etc/rsyslog.conf /etc/rsyslog.d/*.conf /etc/rsyslog.conf:$ActionSendStreamDriverAuthMode x509/name If the value of the "$ActionSendStreamDriverAuthMode" option is not set to "x509/name" or the line is commented out, ask the System Administrator to indicate how the audit logs are offloaded to a different system or media. If there is no evidence that the transfer of the audit logs being offloaded to another system or media is encrypted, this is a finding.
Fix: F-52205r780016_fix
Configure the operating system to authenticate the remote logging server for offloading audit logs by setting the following option in "/etc/rsyslog.conf" or "/etc/rsyslog.d/[customfile].conf": $ActionSendStreamDriverAuthMode x509/name
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-001855
- Version
- OL08-00-030730
- Vuln IDs
-
- V-248818
- Rule IDs
-
- SV-248818r877389_rule
Checks: C-52252r780018_chk
Verify OL 8 takes action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following commands: $ sudo grep -w space_left /etc/audit/auditd.conf space_left = 25% If the value of the "space_left" keyword is not set to "25%" or if the line is commented out, ask the SA to demonstrate how the system is providing real-time alerts to the SA and ISSO. If there is no evidence that real-time alerts are configured on the system, this is a finding.
Fix: F-52206r780019_fix
Configure OL 8 to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the "/etc/audit/auditd.conf" file. space_left = 25%
- RMF Control
- AU-5
- Severity
- Medium
- CCI
- CCI-001855
- Version
- OL08-00-030731
- Vuln IDs
-
- V-248819
- Rule IDs
-
- SV-248819r877389_rule
Checks: C-52253r780021_chk
Verify OL 8 notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command: $ sudo grep -w space_left_action /etc/audit/auditd.conf space_left_action = email If the value of the "space_left_action" is not set to "email", or if the line is commented out, ask the System Administrator to indicate how the system is providing real-time alerts to the SA and ISSO. If there is no evidence that real-time alerts are configured on the system, this is a finding.
Fix: F-52207r780022_fix
Configure the operating system to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file. space_left_action = email Note: Option names and values in the auditd.conf file are case insensitive.
- RMF Control
- AU-8
- Severity
- Medium
- CCI
- CCI-001890
- Version
- OL08-00-030740
- Vuln IDs
-
- V-248820
- Rule IDs
-
- SV-248820r877038_rule
Checks: C-52254r780024_chk
Verify OL 8 is comparing internal information system clocks at least every 24 hours with an NTP server with the following command: $ sudo grep maxpoll /etc/chrony.conf server [ntp.server.name] iburst maxpoll 16 If the "maxpoll" option is set to a number greater than "16" or the line is commented out, this is a finding.
Fix: F-52208r780025_fix
Configure OL 8 to compare internal information system clocks at least every 24 hours with an NTP server by adding/modifying the following line in the "/etc/chrony.conf" file. server [ntp.server.name] iburst maxpoll 16
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-030741
- Vuln IDs
-
- V-248821
- Rule IDs
-
- SV-248821r928556_rule
Checks: C-52255r928554_chk
Note: If the system is approved and documented by the information system security officer (ISSO) to function as an NTP time server, this requirement is Not Applicable. Verify OL 8 disables the chrony daemon from acting as a server with the following command: $ sudo grep -w 'port' /etc/chrony.conf port 0 If the "port" option is not set to "0" or is commented out or missing, this is a finding.
Fix: F-52209r928555_fix
Configure OL 8 to disable the chrony daemon from acting as a server by adding or modifying the following line in the "/etc/chrony.conf" file. port 0
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-030742
- Vuln IDs
-
- V-248822
- Rule IDs
-
- SV-248822r928559_rule
Checks: C-52256r928557_chk
Note: If the system is approved and documented by the information system security officer (ISSO) to function as an NTP time server, this requirement is Not Applicable. Verify OL 8 disables network management of the chrony daemon with the following command: $ sudo grep -w 'cmdport' /etc/chrony.conf cmdport 0 If the "cmdport" option is not set to "0" or is commented out or missing, this is a finding.
Fix: F-52210r928558_fix
Configure OL 8 to disable network management of the chrony daemon by adding or modifying the following line in the "/etc/chrony.conf" file. cmdport 0
- RMF Control
- CM-7
- Severity
- High
- CCI
- CCI-000381
- Version
- OL08-00-040000
- Vuln IDs
-
- V-248823
- Rule IDs
-
- SV-248823r780035_rule
Checks: C-52257r780033_chk
Determine if the telnet-server package is installed with the following command: $ sudo yum list installed telnet-server If the telnet-server package is installed, this is a finding.
Fix: F-52211r780034_fix
Configure OL 8 to disable non-essential capabilities by removing the telnet-server package from the system with the following command: $ sudo yum remove telnet-server
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- OL08-00-040001
- Vuln IDs
-
- V-248824
- Rule IDs
-
- SV-248824r780038_rule
Checks: C-52258r780036_chk
Determine if any automated bug reporting packages are installed with the following command: $ sudo yum list installed abrt* If any automated bug reporting package is installed, this is a finding.
Fix: F-52212r780037_fix
Configure the operating system to disable non-essential capabilities by removing automated bug reporting packages from the system with the following command: $ sudo yum remove abrt*
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- OL08-00-040002
- Vuln IDs
-
- V-248825
- Rule IDs
-
- SV-248825r780041_rule
Checks: C-52259r780039_chk
Determine if the sendmail package is installed with the following command: $ sudo yum list installed sendmail If the sendmail package is installed, this is a finding.
Fix: F-52213r780040_fix
Configure the operating system to disable non-essential capabilities by removing the sendmail package from the system with the following command: $ sudo yum remove sendmail
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-040004
- Vuln IDs
-
- V-248826
- Rule IDs
-
- SV-248826r780044_rule
Checks: C-52260r780042_chk
Verify OL 8 enables kernel page-table isolation with the following commands: $ sudo grub2-editenv list | grep pti kernelopts=root=/dev/mapper/ol-root ro crashkernel=auto resume=/dev/mapper/ol-swap rd.lvm.lv=ol/root rd.lvm.lv=ol/swap rhgb quiet fips=1 audit=1 audit_backlog_limit=8192 pti=on boot=UUID=8d171156-cd61-421c-ba41-1c021ac29e82 If the "pti" entry does not equal "on", is missing, or the line is commented out, this is a finding. Check that kernel page-table isolation is enabled by default to persist in kernel updates: $ sudo grep pti /etc/default/grub GRUB_CMDLINE_LINUX="pti=on" If "pti" is not set to "on", is missing or commented out, this is a finding.
Fix: F-52214r780043_fix
Configure OL 8 to enable kernel page-table isolation with the following command: $ sudo grubby --update-kernel=ALL --args="pti=on" Add or modify the following line in "/etc/default/grub" to ensure the configuration survives kernel updates: GRUB_CMDLINE_LINUX="pti=on"
- RMF Control
- CM-7
- Severity
- High
- CCI
- CCI-000381
- Version
- OL08-00-040010
- Vuln IDs
-
- V-248827
- Rule IDs
-
- SV-248827r780047_rule
Checks: C-52261r780045_chk
Determine if the rsh-server package is installed with the following command: $ sudo yum list installed rsh-server If the rsh-server package is installed, this is a finding.
Fix: F-52215r780046_fix
Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command: $ sudo yum remove rsh-server
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000381
- Version
- OL08-00-040020
- Vuln IDs
-
- V-248828
- Rule IDs
-
- SV-248828r943068_rule
Checks: C-52262r943066_chk
If the device or operating system does not have a camera installed, this requirement is not applicable. This requirement is not applicable to mobile devices (smartphones and tablets), where the use of the camera is a local AO decision. This requirement is not applicable to dedicated VTC suites located in approved VTC locations that are centrally managed. For an external camera, if there is not a method for the operator to manually disconnect the camera at the end of collaborative computing sessions, this is a finding. For a built-in camera, the camera must be protected by a camera cover (e.g., laptop camera cover slide) when not in use. If the built-in camera is not protected with a camera cover or is not physically disabled, this is a finding. If the camera is not disconnected, covered, or physically disabled, determine if it is being disabled via software with the following commands: Verify the operating system disables the ability to load the uvcvideo kernel module. $ sudo grep -r uvcvideo /etc/modprobe.d/* | grep "/bin/false" install uvcvideo /bin/false If the command does not return any output, or the line is commented out, and the collaborative computing device has not been authorized for use, this is a finding. Verify the camera is disabled via blacklist with the following command: $ sudo grep -r uvcvideo /etc/modprobe.d/* | grep "blacklist" blacklist uvcvideo If the command does not return any output or the output is not "blacklist uvcvideo", and the collaborative computing device has not been authorized for use, this is a finding.
Fix: F-52216r943067_fix
Configure OL 8 to disable the built-in or attached camera when not in use. Build or modify the "/etc/modprobe.d/blacklist.conf" file by using the following example: install uvcvideo /bin/false blacklist uvcvideo Reboot the system for the settings to take effect.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040021
- Vuln IDs
-
- V-248829
- Rule IDs
-
- SV-248829r943071_rule
Checks: C-52263r943069_chk
Verify the operating system disables the ability to load the "atm" kernel module. $ sudo grep -r atm /etc/modprobe.d/* | grep -i "/bin/false" | grep -v "^#" install atm /bin/false If the command does not return any output or the line is commented out, and use of ATM is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use ATM with the following command: $ sudo grep atm /etc/modprobe.d/* | grep -i "blacklist" | grep -v "^#" blacklist atm If the command does not return any output or the output is not "blacklist atm", and use of ATM is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52217r943070_fix
Configure OL 8 to disable the ability to use the "atm" kernel module. Create a file under "/etc/modprobe.d" with the following command: $ sudo touch /etc/modprobe.d/atm.conf Add the following line to the created file: install atm /bin/false Configure OL 8 to disable the ability to use the atm kernel module. $ sudo vi /etc/modprobe.d/blacklist.conf Add or update the line: blacklist atm
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040022
- Vuln IDs
-
- V-248830
- Rule IDs
-
- SV-248830r943074_rule
Checks: C-52264r943072_chk
Verify the operating system disables the ability to load the "can" kernel module. $ sudo grep -r can /etc/modprobe.d/* | grep -i "/bin/false" | grep -v "^#" install can /bin/false If the command does not return any output or the line is commented out, and use of "can" is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use CAN with the following command: $ sudo grep can /etc/modprobe.d/* | grep -i "blacklist" | grep -v "^#" blacklist can If the command does not return any output or the output is not "blacklist can", and use of CAN is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52218r943073_fix
Configure OL 8 to disable the ability to use the "can" kernel module. Create a file under "/etc/modprobe.d" with the following command: $ sudo touch /etc/modprobe.d/can.conf Add the following line to the created file: install can /bin/false Configure OL 8 to disable the ability to use the can kernel module. $ sudo vi /etc/modprobe.d/blacklist.conf Add or update the line: blacklist can
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040023
- Vuln IDs
-
- V-248831
- Rule IDs
-
- SV-248831r943077_rule
Checks: C-52265r943075_chk
Verify the operating system disables the ability to load the "sctp" kernel module. $ sudo grep -r sctp /etc/modprobe.d/* | grep -i "/bin/false" | grep -v "^#" install sctp /bin/false If the command does not return any output or the line is commented out, and use of SCTP is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use SCTP with the following command: $ sudo grep sctp /etc/modprobe.d/* | grep -i "blacklist" | grep -v "^#" blacklist sctp If the command does not return any output or the output is not "blacklist sctp", and use of SCTP is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52219r943076_fix
Configure OL 8 to disable the ability to use the "sctp" kernel module. Create a file under "/etc/modprobe.d" with the following command: $ sudo touch /etc/modprobe.d/sctp.conf Add the following line to the created file: install sctp /bin/false Configure OL 8 to disable the ability to use the sctp kernel module. $ sudo vi /etc/modprobe.d/blacklist.conf Add or update the line: blacklist sctp
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-040024
- Vuln IDs
-
- V-248832
- Rule IDs
-
- SV-248832r943080_rule
Checks: C-52266r943078_chk
Verify the operating system disables the ability to load the TIPC protocol kernel module. $ sudo grep -r tipc /etc/modprobe.d/* | grep "/bin/false" install tipc /bin/false If the command does not return any output, or the line is commented out, and use of the TIPC protocol is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use the TIPC protocol. Determine if the TIPC protocol is disabled with the following command: $ sudo grep -r tipc /etc/modprobe.d/* | grep "blacklist" blacklist tipc If the command does not return any output or the output is not "blacklist tipc", and use of the TIPC protocol is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52220r943079_fix
Configure the operating system to disable the ability to use the TIPC protocol kernel module. Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf": install tipc /bin/false blacklist tipc Reboot the system for the settings to take effect.
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-040025
- Vuln IDs
-
- V-248833
- Rule IDs
-
- SV-248833r943083_rule
Checks: C-52267r943081_chk
Verify the operating system disables the ability to load the cramfs kernel module. $ sudo grep -ri cramfs /etc/modprobe.d/* | grep -i "/bin/false" install cramfs /bin/false If the command does not return any output, or the line is commented out, and use of the cramfs protocol is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use the cramfs kernel module. Determine if the cramfs kernel module is disabled with the following command: $ sudo grep -ri cramfs /etc/modprobe.d/* | grep -i "blacklist" blacklist cramfs If the command does not return any output or the output is not "blacklist cramfs", and use of the cramfs kernel module is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52221r943082_fix
Configure the operating system to disable the ability to use the cramfs kernel module. Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf": install cramfs /bin/false blacklist cramfs Reboot the system for the settings to take effect.
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- OL08-00-040026
- Vuln IDs
-
- V-248834
- Rule IDs
-
- SV-248834r943086_rule
Checks: C-52268r943084_chk
Verify the operating system disables the ability to load the firewire-core kernel module. $ sudo grep -ri firewire-core /etc/modprobe.d/* | grep -i "/bin/false" install firewire-core /bin/false If the command does not return any output, or the line is commented out, and use of the firewire-core protocol is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Verify the operating system disables the ability to use the firewire-core kernel module. Determine if the firewire-core kernel module is disabled with the following command: $ sudo grep -ri firewire-core /etc/modprobe.d/* | grep -i "blacklist" blacklist firewire-core If the command does not return any output or the output is not "blacklist firewire-core", and use of the firewire-core kernel module is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52222r943085_fix
Configure the operating system to disable the ability to use the firewire-core kernel module. Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf": install firewire-core /bin/false blacklist firewire-core Reboot the system for the settings to take effect.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-000382
- Version
- OL08-00-040030
- Vuln IDs
-
- V-248835
- Rule IDs
-
- SV-248835r780071_rule
Checks: C-52269r780069_chk
Inspect the firewall configuration and running services to verify it is configured to prohibit or restrict the use of functions, ports, protocols, and/or services that are unnecessary or prohibited. Check which services are currently active with the following command: $ sudo firewall-cmd --list-all custom (active) target: DROP icmp-block-inversion: no interfaces: ens33 sources: services: dhcpv6-client dns http https ldaps rpc-bind ssh ports: masquerade: no forward-ports: icmp-blocks: rich rules: Ask the System Administrator for the site or program PPSM Component Local Service Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. If there are additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding.
Fix: F-52223r780070_fix
Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL.
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-000778
- Version
- OL08-00-040070
- Vuln IDs
-
- V-248836
- Rule IDs
-
- SV-248836r780074_rule
Checks: C-52270r780072_chk
Verify the operating system disables the ability to automount devices. Determine if the automounter service is active with the following command: $ sudo systemctl status autofs autofs.service - Automounts filesystems on demand Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled) Active: inactive (dead) If the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-52224r780073_fix
Configure OL 8 to disable the ability to automount devices. Turn off the automount service with the following commands: $ sudo systemctl stop autofs $ sudo systemctl disable autofs If "autofs" is required for Network File System (NFS), it must be documented with the ISSO.
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-000778
- Version
- OL08-00-040080
- Vuln IDs
-
- V-248837
- Rule IDs
-
- SV-248837r943089_rule
Checks: C-52271r943087_chk
Verify the operating system disables the ability to load the USB Storage kernel module. $ sudo grep -r usb-storage /etc/modprobe.d/* | grep -i "/bin/false" install usb-storage /bin/false If the command does not return any output, or the line is commented out, and use of USB Storage is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Determine if USB mass storage is disabled with the following command: $ sudo grep usb-storage /etc/modprobe.d/* | grep -i "blacklist" | grep -v "^#" /etc/modprobe.d/blacklist.conf:blacklist usb-storage If the command does not return any output or the output is not "blacklist usb-storage" and use of USB storage devices is not documented with the ISSO as an operational requirement, this is a finding.
Fix: F-52225r943088_fix
Configure OL 8 to disable the ability to use the USB Storage kernel module and to use USB mass storage devices. $ sudo vi /etc/modprobe.d/blacklist.conf Add or update the lines: install usb-storage /bin/false blacklist usb-storage Reboot the system for the settings to take effect.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-002314
- Version
- OL08-00-040090
- Vuln IDs
-
- V-248839
- Rule IDs
-
- SV-248839r943095_rule
Checks: C-52273r943093_chk
Verify "firewalld" is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems with the following commands: $ sudo firewall-cmd --state running $ sudo firewall-cmd --get-active-zones [custom] interfaces: ens33 $ sudo firewall-cmd --info-zone=[custom] | grep target target: DROP If no zones are active on the OL 8 interfaces or if the target is set to an option other than "DROP", this is a finding. If the "firewalld" package is not installed, ask the System Administrator if an alternate firewall (such as iptables) is installed and in use, and how is it configured to employ a deny-all, allow-by-exception policy. If the alternate firewall is not configured to employ a deny-all, allow-by-exception policy, this is a finding. If no firewall is installed, this is a finding.
Fix: F-52227r943094_fix
Configure the "firewalld" daemon to employ a deny-all, allow-by-exception policy with the following commands: $ sudo firewall-cmd --permanent --new-zone=[custom] $ sudo cp /usr/lib/firewalld/zones/drop.xml /etc/firewalld/zones/[custom].xml This will provide a clean configuration file to work with that employs a deny-all approach. Note: Add the exceptions that are required for mission functionality and update the short title in the xml file to match the [custom] zone name. Reload the firewall rules to make the new [custom] zone available to load: $ sudo firewall-cmd --reload Set the default zone to the new [custom] zone: $ sudo firewall-cmd --set-default-zone=[custom] Note: This is a runtime and permanent change. Add any interfaces to the new [custom] zone: $ sudo firewall-cmd --permanent --zone=[custom] --change-interface=ens33 Reload the firewall rules for changes to take effect: $ sudo firewall-cmd --reload
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-002314
- Version
- OL08-00-040100
- Vuln IDs
-
- V-248840
- Rule IDs
-
- SV-248840r853847_rule
Checks: C-52274r780084_chk
Verify that "firewalld" is installed with the following commands: $ sudo yum list installed firewalld firewalld.noarch 0.7.0-5.el8 If the "firewalld" package is not installed, ask the System Administrator if another firewall is installed. If no firewall is installed this is a finding.
Fix: F-52228r780085_fix
Install "firewalld" with the following commands: $ sudo yum install firewalld.noarch
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-002314
- Version
- OL08-00-040101
- Vuln IDs
-
- V-248841
- Rule IDs
-
- SV-248841r853848_rule
Checks: C-52275r780087_chk
Verify that "firewalld" is active with the following commands: $ sudo systemctl is-active firewalld active If the "firewalld" package is not "active", ask the System Administrator if another firewall is installed. If no firewall is installed and active this is a finding.
Fix: F-52229r780088_fix
Configure "firewalld" to protect the operating system with the following commands: $ sudo systemctl enable firewalld $ sudo systemctl start firewalld
- RMF Control
- AC-18
- Severity
- Medium
- CCI
- CCI-001443
- Version
- OL08-00-040110
- Vuln IDs
-
- V-248842
- Rule IDs
-
- SV-248842r853849_rule
Checks: C-52276r780090_chk
Verify there are no wireless interfaces configured on the system with the following command. Note: This requirement is not applicable for systems that do not have physical wireless network radios. $ sudo nmcli device status DEVICE TYPE STATE CONNECTION virbr0 bridge connected virbr0 wlp7s0 wifi connected wifiSSID enp6s0 ethernet disconnected -- p2p-dev-wlp7s0 wifi-p2p disconnected -- lo loopback unmanaged -- virbr0-nic tun unmanaged -- If a wireless interface is configured and has not been documented and approved by the Information System Security Officer (ISSO), this is a finding.
Fix: F-52230r780091_fix
Configure the system to disable all wireless network interfaces with the following command: $ sudo nmcli radio all off
- RMF Control
- AC-18
- Severity
- Medium
- CCI
- CCI-001443
- Version
- OL08-00-040111
- Vuln IDs
-
- V-248843
- Rule IDs
-
- SV-248843r943092_rule
Checks: C-52277r943090_chk
If the device or operating system does not have a Bluetooth adapter installed, this requirement is not applicable. This requirement is not applicable to mobile devices (smartphones and tablets), where the use of Bluetooth is a local AO decision. Determine if Bluetooth is disabled with the following command: $ sudo grep -r bluetooth /etc/modprobe.d /etc/modprobe.d/bluetooth.conf:install bluetooth /bin/false If the command does not return any output or the line is commented out and the collaborative computing device has not been authorized for use, this is a finding. Verify the operating system disables the ability to use Bluetooth with the following command: $ sudo grep -r bluetooth /etc/modprobe.d | grep -i "blacklist" | grep -v "^#" blacklist bluetooth If the command does not return any output or the output is not "blacklist bluetooth", and use of Bluetooth is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-52231r943091_fix
Configure the operating system to disable the Bluetooth adapter when not in use. Build or modify the "/etc/modprobe.d/bluetooth.conf" file with the following line: install bluetooth /bin/false Disable the ability to use the Bluetooth kernel module. $ sudo vi /etc/modprobe.d/blacklist.conf Add or update the line: blacklist bluetooth Reboot the system for the settings to take effect.
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040120
- Vuln IDs
-
- V-248844
- Rule IDs
-
- SV-248844r853853_rule
Checks: C-52278r780096_chk
Verify "/dev/shm" is mounted with the "nodev" option: $ sudo mount | grep /dev/shm tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nodev" option is configured for "/dev/shm": $ sudo cat /etc/fstab | grep /dev/shm tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nodev" option is missing, or if "/dev/shm" is mounted without the "nodev" option, this is a finding.
Fix: F-52232r780097_fix
Configure OL 8 so that "/dev/shm" is mounted with the "nodev" option by adding/modifying "/etc/fstab" with the following line: tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040121
- Vuln IDs
-
- V-248845
- Rule IDs
-
- SV-248845r853854_rule
Checks: C-52279r780099_chk
Verify "/dev/shm" is mounted with the "nosuid" option: $ sudo mount | grep /dev/shm tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nosuid" option is configured for "/dev/shm": $ sudo cat /etc/fstab | grep /dev/shm tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nosuid" option is missing, or if "/dev/shm" is mounted without the "nosuid" option, this is a finding.
Fix: F-52233r780100_fix
Configure OL 8 so that "/dev/shm" is mounted with the "nosuid" option by adding/modifying "/etc/fstab" with the following line: tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040122
- Vuln IDs
-
- V-248846
- Rule IDs
-
- SV-248846r853855_rule
Checks: C-52280r780102_chk
Verify "/dev/shm" is mounted with the "noexec" option: $ sudo mount | grep /dev/shm tmpfs on /dev/shm type tmpfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "noexec" option is configured for "/dev/shm": $ sudo cat /etc/fstab | grep /dev/shm tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "noexec" option is missing, or if "/dev/shm" is mounted without the "noexec" option, this is a finding.
Fix: F-52234r780103_fix
Configure OL 8 so that "/dev/shm" is mounted with the "noexec" option by adding/modifying "/etc/fstab" with the following line: tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040123
- Vuln IDs
-
- V-248847
- Rule IDs
-
- SV-248847r853856_rule
Checks: C-52281r780105_chk
Verify "/tmp" is mounted with the "nodev" option: $ sudo mount | grep /tmp /dev/mapper/ol-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nodev" option is configured for /tmp: $ sudo cat /etc/fstab | grep /tmp /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nodev" option is missing, or if /tmp is mounted without the "nodev" option, this is a finding.
Fix: F-52235r780106_fix
Configure the system so that /tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040124
- Vuln IDs
-
- V-248848
- Rule IDs
-
- SV-248848r853857_rule
Checks: C-52282r780108_chk
Verify "/tmp" is mounted with the "nosuid" option: $ sudo mount | grep /tmp /dev/mapper/ol-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nosuid" option is configured for /tmp: $ sudo cat /etc/fstab | grep /tmp /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nosuid" option is missing, or if /tmp is mounted without the "nosuid" option, this is a finding.
Fix: F-52236r780109_fix
Configure the system so that /tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040125
- Vuln IDs
-
- V-248849
- Rule IDs
-
- SV-248849r853858_rule
Checks: C-52283r780111_chk
Verify "/tmp" is mounted with the "noexec" option: $ sudo mount | grep /tmp /dev/mapper/ol-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "noexec" option is configured for /tmp: $ sudo cat /etc/fstab | grep /tmp /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "noexec" option is missing, or if /tmp is mounted without the "noexec" option, this is a finding.
Fix: F-52237r780112_fix
Configure the system so that /tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040126
- Vuln IDs
-
- V-248850
- Rule IDs
-
- SV-248850r853859_rule
Checks: C-52284r780114_chk
Verify "/var/log" is mounted with the "nodev" option: $ sudo mount | grep /var/log /dev/mapper/ol-var_log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nodev" option is configured for /var/log: $ sudo cat /etc/fstab | grep /var/log /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nodev" option is missing, or if /var/log is mounted without the "nodev" option, this is a finding.
Fix: F-52238r780115_fix
Configure the system so that /var/log is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040127
- Vuln IDs
-
- V-248851
- Rule IDs
-
- SV-248851r853860_rule
Checks: C-52285r780117_chk
Verify "/var/log" is mounted with the "nosuid" option: $ sudo mount | grep /var/log /dev/mapper/ol-var_log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nosuid" option is configured for /var/log: $ sudo cat /etc/fstab | grep /var/log /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nosuid" option is missing, or if /var/log is mounted without the "nosuid" option, this is a finding.
Fix: F-52239r780118_fix
Configure the system so that /var/log is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040128
- Vuln IDs
-
- V-248852
- Rule IDs
-
- SV-248852r853861_rule
Checks: C-52286r780120_chk
Verify "/var/log" is mounted with the "noexec" option: $ sudo mount | grep /var/log /dev/mapper/ol-var_log on /var/log type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "noexec" option is configured for /var/log: $ sudo cat /etc/fstab | grep /var/log /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "noexec" option is missing, or if /var/log is mounted without the "noexec" option, this is a finding.
Fix: F-52240r780121_fix
Configure the system so that /var/log is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log /var/log xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040129
- Vuln IDs
-
- V-248853
- Rule IDs
-
- SV-248853r853862_rule
Checks: C-52287r780123_chk
Verify "/var/log/audit" is mounted with the "nodev" option: $ sudo mount | grep /var/log/audit /dev/mapper/ol-var_log_audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nodev" option is configured for /var/log/audit: $ sudo cat /etc/fstab | grep /var/log/audit /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nodev" option is missing, or if /var/log/audit is mounted without the "nodev" option, this is a finding.
Fix: F-52241r780124_fix
Configure the system so that /var/log/audit is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040130
- Vuln IDs
-
- V-248854
- Rule IDs
-
- SV-248854r853863_rule
Checks: C-52288r780126_chk
Verify "/var/log/audit" is mounted with the "nosuid" option: $ sudo mount | grep /var/log/audit /dev/mapper/ol-var_log_audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nosuid" option is configured for /var/log/audit: $ sudo cat /etc/fstab | grep /var/log/audit /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nosuid" option is missing, or if /var/log/audit is mounted without the "nosuid" option, this is a finding.
Fix: F-52242r780127_fix
Configure the system so that /var/log/audit is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040131
- Vuln IDs
-
- V-248855
- Rule IDs
-
- SV-248855r853864_rule
Checks: C-52289r780129_chk
Verify "/var/log/audit" is mounted with the "noexec" option: $ sudo mount | grep /var/log/audit /dev/mapper/ol-var_log_audit on /var/log/audit type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "noexec" option is configured for /var/log/audit: $ sudo cat /etc/fstab | grep /var/log/audit /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "noexec" option is missing, or if /var/log/audit is mounted without the "noexec" option, this is a finding.
Fix: F-52243r780130_fix
Configure the system so that /var/log/audit is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_log_audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040132
- Vuln IDs
-
- V-248856
- Rule IDs
-
- SV-248856r853865_rule
Checks: C-52290r780132_chk
Verify "/var/tmp" is mounted with the "nodev" option: $ sudo mount | grep /var/tmp /dev/mapper/ol-var_tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nodev" option is configured for /var/tmp: $ sudo cat /etc/fstab | grep /var/tmp /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nodev" option is missing, or if /var/tmp is mounted without the "nodev" option, this is a finding.
Fix: F-52244r780133_fix
Configure the system so that /var/tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040133
- Vuln IDs
-
- V-248857
- Rule IDs
-
- SV-248857r853866_rule
Checks: C-52291r780135_chk
Verify "/var/tmp" is mounted with the "nosuid" option: $ sudo mount | grep /var/tmp /dev/mapper/ol-var_tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "nosuid" option is configured for /var/tmp: $ sudo cat /etc/fstab | grep /var/tmp /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "nosuid" option is missing, or if /var/tmp is mounted without the "nosuid" option, this is a finding.
Fix: F-52245r780136_fix
Configure the system so that /var/tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040134
- Vuln IDs
-
- V-248858
- Rule IDs
-
- SV-248858r853867_rule
Checks: C-52292r780138_chk
Verify "/var/tmp" is mounted with the "noexec" option: $ sudo mount | grep /var/tmp /dev/mapper/ol-var_tmp on /var/tmp type xfs (rw,nodev,nosuid,noexec,seclabel) Verify that the "noexec" option is configured for /var/tmp: $ sudo cat /etc/fstab | grep /var/tmp /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0 If results are returned and the "noexec" option is missing, or if /var/tmp is mounted without the "noexec" option, this is a finding.
Fix: F-52246r780139_fix
Configure the system so that /var/tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line: /dev/mapper/ol-var_tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040135
- Vuln IDs
-
- V-248859
- Rule IDs
-
- SV-248859r853868_rule
Checks: C-52293r780141_chk
Verify the OL 8 "fapolicyd" is installed. Check that "fapolicyd" is installed with the following command: $ sudo yum list installed fapolicyd Installed Packages fapolicyd.x86_64 If "fapolicyd" is not installed, this is a finding.
Fix: F-52247r780142_fix
Install "fapolicyd" with the following command: $ sudo yum install fapolicyd.x86_64
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040136
- Vuln IDs
-
- V-248860
- Rule IDs
-
- SV-248860r853869_rule
Checks: C-52294r780144_chk
Verify the OL 8 "fapolicyd" is enabled and running with the following command: $ sudo systemctl status fapolicyd.service fapolicyd.service - File Access Policy Daemon Loaded: loaded (/usr/lib/systemd/system/fapolicyd.service; enabled; vendor preset: disabled) Active: active (running) If fapolicyd is not enabled and running, this is a finding.
Fix: F-52248r780145_fix
Enable "fapolicyd" using the following command: $ sudo systemctl enable --now fapolicyd
- RMF Control
- CM-7
- Severity
- Medium
- CCI
- CCI-001764
- Version
- OL08-00-040137
- Vuln IDs
-
- V-248861
- Rule IDs
-
- SV-248861r860922_rule
Checks: C-52295r858593_chk
Verify the OL 8 "fapolicyd" employs a deny-all, permit-by-exception policy. Check that "fapolicyd" is in enforcement mode with the following command: $ sudo grep permissive /etc/fapolicyd/fapolicyd.conf permissive = 0 Check that fapolicyd employs a deny-all policy on system mounts with the following commands: For OL 8.4 systems and older: $ sudo tail /etc/fapolicyd/fapolicyd.rules For OL 8.5 systems and newer: $ sudo tail /etc/fapolicyd/compiled.rules allow exe=/usr/bin/python3.7 : ftype=text/x-python deny_audit perm=any pattern=ld_so : all deny perm=any all : all If fapolicyd is not running in enforcement mode with a deny-all, permit-by-exception policy, this is a finding.
Fix: F-52249r858594_fix
Configure OL 8 to employ a deny-all, permit-by-exception application whitelisting policy with "fapolicyd". With the "fapolicyd" installed and enabled, configure the daemon to function in permissive mode until the whitelist is built correctly to avoid system lockout. Do this by editing the "/etc/fapolicyd/fapolicyd.conf" file with the following line: permissive = 1 For OL 8.4 systems and older: Build the whitelist in the "/etc/fapolicyd/fapolicyd.rules" file ensuring the last rule is "deny perm=any all : all". For OL 8.5 systems and newer: Build the whitelist in a file within the "/etc/fapolicyd/rules.d" directory ensuring the last rule is "deny perm=any all : all". Once it is determined the whitelist is built correctly, set the fapolicyd to enforcing mode by editing the "permissive" line in the /etc/fapolicyd/fapolicyd.conf file. permissive = 0
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-001958
- Version
- OL08-00-040139
- Vuln IDs
-
- V-248862
- Rule IDs
-
- SV-248862r853871_rule
Checks: C-52296r780150_chk
Verify USBGuard is installed on the operating system with the following command: $ sudo yum list installed usbguard Installed Packages usbguard.x86_64 0.7.8-7.el8 @ol8_appstream If the USBGuard package is not installed, ask the SA to indicate how unauthorized peripherals are being blocked. If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.
Fix: F-52250r780151_fix
Install the USBGuard package with the following command: $ sudo yum install usbguard.x86_64
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-001958
- Version
- OL08-00-040140
- Vuln IDs
-
- V-248863
- Rule IDs
-
- SV-248863r853872_rule
Checks: C-52297r780153_chk
Verify the USBGuard has a policy configured with the following command: $ sudo usbguard list-rules If the command does not return results or an error is returned, ask the SA to indicate how unauthorized peripherals are being blocked. If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.
Fix: F-52251r780154_fix
Configure the operating system to enable the blocking of unauthorized peripherals with the following command: This command must be run from a root shell and will create an allow list for any usb devices currently connect to the system. # usbguard generate-policy > /etc/usbguard/rules.conf Note: Enabling and starting usbguard without properly configuring it for an individual system will immediately prevent any access over a usb device such as a keyboard or mouse.
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-001958
- Version
- OL08-00-040141
- Vuln IDs
-
- V-248864
- Rule IDs
-
- SV-248864r853873_rule
Checks: C-52298r780156_chk
Verify the operating system has enabled the use of the USBGuard with the following command: $ sudo systemctl status usbguard.service usbguard.service - USBGuard daemon Loaded: loaded (/usr/lib/systemd/system/usbguard.service; enabled; vendor preset: disabled) Active: active (running) If the usbguard.service is not enabled and active, ask the SA to indicate how unauthorized peripherals are being blocked. If there is no evidence that unauthorized peripherals are being blocked before establishing a connection, this is a finding.
Fix: F-52252r780157_fix
Configure the operating system to enable the blocking of unauthorized peripherals with the following commands: $ sudo systemctl enable usbguard.service $ sudo systemctl start usbguard.service Note: Enabling and starting usbguard without properly configuring it for an individual system will immediately prevent any access over a usb device such as a keyboard or mouse.
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-001095
- Version
- OL08-00-040150
- Vuln IDs
-
- V-248865
- Rule IDs
-
- SV-248865r902788_rule
Checks: C-52299r780159_chk
Verify "nftables" is configured to allow rate limits on any connection to the system with the following command. Verify "firewalld" has "nftables" set as the default backend: $ sudo grep -i firewallbackend /etc/firewalld/firewalld.conf # FirewallBackend FirewallBackend=nftables If the "nftables" is not set as the "firewallbackend" default, this is a finding.
Fix: F-52253r902787_fix
Configure "nftables" to be the default "firewallbackend" for "firewalld" by adding or editing the following line in "/etc/firewalld/firewalld.conf": FirewallBackend=nftables Establish rate-limiting rules based on organization-defined types of DoS attacks on impacted network interfaces.
- RMF Control
- SC-8
- Severity
- Medium
- CCI
- CCI-002418
- Version
- OL08-00-040159
- Vuln IDs
-
- V-248866
- Rule IDs
-
- SV-248866r916422_rule
Checks: C-52300r780162_chk
Verify SSH is installed with the following command: $ sudo yum list installed openssh-server openssh-server.x86_64 8.0p1-5.el8 @anaconda If the "SSH server" package is not installed, this is a finding.
Fix: F-52254r780163_fix
Install SSH packages onto the host with the following command: $ sudo yum install openssh-server.x86_64
- RMF Control
- SC-8
- Severity
- Medium
- CCI
- CCI-002418
- Version
- OL08-00-040160
- Vuln IDs
-
- V-248867
- Rule IDs
-
- SV-248867r916422_rule
Checks: C-52301r780165_chk
Verify SSH is loaded and active with the following command: $ sudo systemctl status sshd sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled) Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days ago Main PID: 1348 (sshd) CGroup: /system.slice/sshd.service 1053 /usr/sbin/sshd -D If "sshd" does not show a status of "active" and "running", this is a finding.
Fix: F-52255r780166_fix
Configure the SSH service to automatically start after reboot with the following command: $ sudo systemctl enable sshd.service
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-000068
- Version
- OL08-00-040161
- Vuln IDs
-
- V-248868
- Rule IDs
-
- SV-248868r877398_rule
Checks: C-52302r858585_chk
Verify the SSH server is configured to force frequent session key renegotiation with the following command: $ sudo grep -ir RekeyLimit /etc/ssh/sshd_config* RekeyLimit 1G 1h If "RekeyLimit" does not have a maximum data amount and maximum time defined or is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52256r780169_fix
Configure the system to force a frequent session key renegotiation for SSH connections to the server by adding or modifying the following line in the "/etc/ssh/sshd_config" file: RekeyLimit 1G 1h The SSH daemon must be restarted for the settings to take effect. $ sudo systemctl restart sshd.service
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-040170
- Vuln IDs
-
- V-248869
- Rule IDs
-
- SV-248869r833246_rule
Checks: C-52303r780171_chk
Verify OL 8 is not configured to reboot the system when Ctrl-Alt-Delete is pressed with the following command: $ sudo systemctl status ctrl-alt-del.target | grep Loaded: Loaded: masked (Reason: Unit ctrl-alt-del.target is masked.) If the "ctrl-alt-del.target" Loaded: value is not set to "masked", this is a finding.
Fix: F-52257r833245_fix
Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commands: $ sudo systemctl disable ctrl-alt-del.target $ sudo systemctl mask ctrl-alt-del.target Created symlink /etc/systemd/system/ctrl-alt-del.target -> /dev/null Reload the daemon to take effect: $ sudo systemctl daemon-reload
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-040171
- Vuln IDs
-
- V-248870
- Rule IDs
-
- SV-248870r780176_rule
Checks: C-52304r780174_chk
Verify OL 8 is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface with the following command: $ sudo grep logout /etc/dconf/db/local.d/* logout='' If the "logout" key is bound to an action, is commented out, or is missing, this is a finding.
Fix: F-52258r780175_fix
Configure the system to disable the Ctrl-Alt-Delete sequence when using a graphical user interface by creating or editing the "/etc/dconf/db/local.d/00-disable-CAD" file. Add the setting to disable the Ctrl-Alt-Delete sequence for a graphical user interface: [org/gnome/settings-daemon/plugins/media-keys] logout='' Update the dconf settings: $ sudo dconf update
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040172
- Vuln IDs
-
- V-248871
- Rule IDs
-
- SV-248871r780179_rule
Checks: C-52305r780177_chk
Verify OL 8 is not configured to reboot the system when Ctrl-Alt-Delete is pressed seven times within two seconds with the following command: $ sudo grep -i ctrl /etc/systemd/system.conf CtrlAltDelBurstAction=none If the "CtrlAltDelBurstAction" is not set to "none" or is commented out or missing, this is a finding.
Fix: F-52259r780178_fix
Configure the system to disable the CtrlAltDelBurstAction by added or modifying the following line in the "/etc/systemd/system.conf" configuration file: CtrlAltDelBurstAction=none Reload the daemon for this change to take effect: $ sudo systemctl daemon-reload
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-040180
- Vuln IDs
-
- V-248872
- Rule IDs
-
- SV-248872r780182_rule
Checks: C-52306r780180_chk
Verify OL 8 is configured to mask the "debug-shell systemd" service with the following command: $ sudo systemctl status debug-shell.service debug-shell.service Loaded: masked (Reason: Unit debug-shell.service is masked.) Active: inactive (dead) If the "debug-shell.service" is loaded and not masked, this is a finding.
Fix: F-52260r780181_fix
Configure the system to mask the "debug-shell systemd" service with the following command: $ sudo systemctl mask debug-shell.service Created symlink /etc/systemd/system/debug-shell.service -> /dev/null Reload the daemon to take effect: $ sudo systemctl daemon-reload
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-040190
- Vuln IDs
-
- V-248873
- Rule IDs
-
- SV-248873r780185_rule
Checks: C-52307r780183_chk
Verify a TFTP server has not been installed on the system with the following command: $ sudo yum list installed tftp-server tftp-server.x86_64 5.2-24.el8 If TFTP is installed and the requirement for TFTP is not documented with the ISSO, this is a finding.
Fix: F-52261r780184_fix
Remove the TFTP package from the system with the following command: $ sudo yum remove tftp-server
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-040200
- Vuln IDs
-
- V-248874
- Rule IDs
-
- SV-248874r780188_rule
Checks: C-52308r780186_chk
Check the system for duplicate UID "0" assignments with the following command: $ sudo awk -F: '$3 == 0 {print $1}' /etc/passwd If any accounts other than root have a UID of "0", this is a finding.
Fix: F-52262r780187_fix
Change the UID of any account on the system, other than root, that has a UID of "0". If the account is associated with system commands or applications, change the UID to one greater than "0" but less than "1000". Otherwise, assign a UID of greater than "1000" that has not already been assigned.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040209
- Vuln IDs
-
- V-248875
- Rule IDs
-
- SV-248875r858651_rule
Checks: C-52309r833247_chk
Verify OL 8 will not accept IPv4 ICMP redirect messages. Check the value of the default "accept_redirects" variables with the following command: $ sudo sysctl net.ipv4.conf.default.accept_redirects net.ipv4.conf.default.accept_redirects = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.default.accept_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.default.accept_redirects = 0 If "net.ipv4.conf.default.accept_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52263r858650_fix
Configure OL 8 to prevent IPv4 ICMP redirect messages from being accepted with the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.default.accept_redirects=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040210
- Vuln IDs
-
- V-248876
- Rule IDs
-
- SV-248876r858653_rule
Checks: C-52310r833249_chk
Verify OL 8 will not accept IPv6 ICMP redirect messages. Note: IPv6 is disabled on the system, this requirement is Not Applicable. Check the value of the default "accept_redirects" variables with the following command: $ sudo sysctl net.ipv6.conf.default.accept_redirects net.ipv6.conf.default.accept_redirects = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.default.accept_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.default.accept_redirects = 0 If "net.ipv6.conf.default.accept_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52264r858652_fix
Configure OL 8 to prevent IPv6 ICMP redirect messages from being accepted with the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.default.accept_redirects=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040220
- Vuln IDs
-
- V-248877
- Rule IDs
-
- SV-248877r858655_rule
Checks: C-52311r833251_chk
Verify OL 8 does not send IPv4 ICMP redirect messages. Check the value of the "all send_redirects" variables with the following command: $ sudo sysctl net.ipv4.conf.all.send_redirects net.ipv4.conf.all.send_redirects = 0 If the returned line does not have a value of "0" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.all.send_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.all.send_redirects = 0 If "net.ipv4.conf.all.send_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52265r858654_fix
Configure OL 8 to not allow interfaces to perform IPv4 ICMP redirects with the following command: $ sudo sysctl -w net.ipv4.conf.all.send_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.all.send_redirects=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040230
- Vuln IDs
-
- V-248878
- Rule IDs
-
- SV-248878r858657_rule
Checks: C-52312r833253_chk
Verify OL 8 does not respond to ICMP echoes sent to a broadcast address. Check the value of the "icmp_echo_ignore_broadcasts" variable with the following command: $ sudo sysctl net.ipv4.icmp_echo_ignore_broadcasts net.ipv4.icmp_echo_ignore_broadcasts = 1 If the returned line does not have a value of "1", a line is not returned, or the retuned line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.icmp_echo_ignore_broadcasts /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.icmp_echo_ignore_broadcasts = 1 If "net.ipv4.icmp_echo_ignore_broadcasts" is not set to "1", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52266r858656_fix
Configure OL 8 to not respond to IPv4 ICMP echoes sent to a broadcast address with the following command: $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "1" is not the system's default value, add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d": net.ipv4.icmp_echo_ignore_broadcasts=1
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040239
- Vuln IDs
-
- V-248879
- Rule IDs
-
- SV-248879r858659_rule
Checks: C-52313r833255_chk
Verify OL 8 does not accept IPv4 source-routed packets. Check the value of the accept source route variable with the following command: $ sudo sysctl net.ipv4.conf.all.accept_source_route net.ipv4.conf.all.accept_source_route = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.all.accept_source_route /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.all.accept_source_route = 0 If "net.ipv4.conf.all.accept_source_route" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52267r858658_fix
Configure OL 8 to not forward IPv4 source-routed packets with the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's all value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.all.accept_source_route=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040240
- Vuln IDs
-
- V-248880
- Rule IDs
-
- SV-248880r858661_rule
Checks: C-52314r833257_chk
Verify OL 8 does not accept IPv6 source-routed packets. Note: If IPv6 is disabled on the system, this requirement is Not Applicable. Check the value of the accept source route variable with the following command: $ sudo sysctl net.ipv6.conf.all.accept_source_route net.ipv6.conf.all.accept_source_route = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.all.accept_source_route /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.all.accept_source_route = 0 If "net.ipv6.conf.all.accept_source_route" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52268r858660_fix
Configure OL 8 to not forward IPv6 source-routed packets with the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's all value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.all.accept_source_route=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040249
- Vuln IDs
-
- V-248881
- Rule IDs
-
- SV-248881r858663_rule
Checks: C-52315r833259_chk
Verify OL 8 does not accept IPv4 source-routed packets by default. Check the value of the accept source route variable with the following command: $ sudo sysctl net.ipv4.conf.default.accept_source_route net.ipv4.conf.default.accept_source_route = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.default.accept_source_route /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.default.accept_source_route = 0 If "net.ipv4.conf.default.accept_source_route" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52269r858662_fix
Configure OL 8 to not forward IPv4 source-routed packets by default with the following command: $ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.default.accept_source_route=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040250
- Vuln IDs
-
- V-248882
- Rule IDs
-
- SV-248882r858665_rule
Checks: C-52316r833261_chk
Verify OL 8 does not accept IPv6 source-routed packets by default. Note: If IPv6 is disabled on the system, this requirement is Not Applicable. Check the value of the accept source route variable with the following command: $ sudo sysctl net.ipv6.conf.default.accept_source_route net.ipv6.conf.default.accept_source_route = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.default.accept_source_route /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.default.accept_source_route = 0 If "net.ipv6.conf.default.accept_source_route" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52270r858664_fix
Configure OL 8 to not forward IPv6 source-routed packets by default with the following command: $ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.default.accept_source_route=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040260
- Vuln IDs
-
- V-248883
- Rule IDs
-
- SV-248883r858669_rule
Checks: C-52317r833265_chk
Verify OL 8 is not performing IPv6 packet forwarding unless the system is a router. Note: If IPv6 is disabled on the system, this requirement is Not Applicable. Determine if IPv6 forwarding is disabled using the following commands: $ sudo sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 0 If the IPv6 forwarding value is "1" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.all.forwarding /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.all.forwarding = 0 If "net.ipv6.conf.all.forwarding" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52271r858668_fix
Configure OL 8 to not allow IPv6 packet forwarding unless the system is a router with the following command: $ sudo sysctl -w net.ipv6.conf.all.forwarding=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following lines in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.all.forwarding=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040261
- Vuln IDs
-
- V-248884
- Rule IDs
-
- SV-248884r858671_rule
Checks: C-52318r833267_chk
Verify OL 8 does not accept router advertisements on all IPv6 interfaces unless the system is a router. Note: If IPv6 is disabled on the system, this requirement is not applicable. Determine if router advertisements are not accepted by using the following command: $ sudo sysctl net.ipv6.conf.all.accept_ra net.ipv6.conf.all.accept_ra = 0 If the "accept_ra" value is not "0" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.all.accept_ra /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.all.accept_ra = 0 If "net.ipv6.conf.all.accept_ra" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52272r858670_fix
Configure the system to not accept router advertisements on all IPv6 interfaces unless the system is a router with the following commands: $ sudo sysctl -w net.ipv6.conf.all.accept_ra=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following lines in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.all.accept_ra=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040262
- Vuln IDs
-
- V-248885
- Rule IDs
-
- SV-248885r858673_rule
Checks: C-52319r833269_chk
Verify OL 8 does not accept router advertisements on all IPv6 interfaces by default, unless the system is a router. Note: If IPv6 is disabled on the system, this requirement is not applicable. Determine if router advertisements are not accepted by using the following command: $ sudo sysctl net.ipv6.conf.default.accept_ra net.ipv6.conf.default.accept_ra = 0 If the "accept_ra" value is not "0" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.default.accept_ra /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.default.accept_ra = 0 If "net.ipv6.conf.default.accept_ra" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52273r858672_fix
Configure the system to not accept router advertisements on all IPv6 interfaces by default, unless the system is a router, with the following commands: $ sudo sysctl -w net.ipv6.conf.default.accept_ra=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following lines in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.default.accept_ra=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040270
- Vuln IDs
-
- V-248886
- Rule IDs
-
- SV-248886r858675_rule
Checks: C-52320r833271_chk
Verify OL 8 does not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default. Check the value of the "default send_redirects" variables with the following command: $ sudo sysctl net.ipv4.conf.default.send_redirects net.ipv4.conf.default.send_redirects=0 If the returned line does not have a value of "0" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.default.send_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.default.send_redirects = 0 If "net.ipv4.conf.default.send_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52274r858674_fix
Configure OL 8 to not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default with the following command: $ sudo sysctl -w net.ipv4.conf.default.send_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value, add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.default.send_redirects=0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040279
- Vuln IDs
-
- V-248887
- Rule IDs
-
- SV-248887r858677_rule
Checks: C-52321r833273_chk
Verify OL 8 ignores IPv4 ICMP redirect messages. Check the value of the "accept_redirects" variables with the following command: $ sudo sysctl net.ipv4.conf.all.accept_redirects net.ipv4.conf.all.accept_redirects = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.all.accept_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.all.accept_redirects = 0 If "net.ipv4.conf.all.accept_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52275r858676_fix
Configure OL 8 to ignore IPv4 ICMP redirect messages with the following command: $ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv4.conf.all.accept_redirects = 0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040280
- Vuln IDs
-
- V-248888
- Rule IDs
-
- SV-248888r858679_rule
Checks: C-52322r833275_chk
Verify OL 8 ignores IPv6 ICMP redirect messages. Note: If IPv6 is disabled on the system, this requirement is Not Applicable. Check the value of the "accept_redirects" variables with the following command: $ sudo sysctl net.ipv6.conf.all.accept_redirects net.ipv6.conf.all.accept_redirects = 0 If the returned line does not have a value of "0", a line is not returned, or the line is commented out, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv6.conf.all.accept_redirects /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv6.conf.all.accept_redirects = 0 If "net.ipv6.conf.all.accept_redirects" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52276r858678_fix
Configure OL 8 to ignore IPv6 ICMP redirect messages with the following command: $ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf If "0" is not the system's default value then add or update the following line in the appropriate file under "/etc/sysctl.d": net.ipv6.conf.all.accept_redirects = 0
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040281
- Vuln IDs
-
- V-248889
- Rule IDs
-
- SV-248889r858681_rule
Checks: C-52323r833277_chk
Verify OL 8 prevents privilege escalation through the kernel by disabling access to the "bpf" syscall with the following commands: $ sudo sysctl kernel.unprivileged_bpf_disabled kernel.unprivileged_bpf_disabled = 1 If the returned line does not have a value of "1" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r kernel.unprivileged_bpf_disabled /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: kernel.unprivileged_bpf_disabled = 1 If "kernel.unprivileged_bpf_disabled" is not set to "1", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52277r858680_fix
Configure the system to prevent privilege escalation through the kernel by disabling access to the "bpf" syscall by adding the following line to a file in the "/etc/sysctl.d" directory: kernel.unprivileged_bpf_disabled = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040282
- Vuln IDs
-
- V-248890
- Rule IDs
-
- SV-248890r858683_rule
Checks: C-52324r833279_chk
Verify OL 8 restricts the use of "ptrace" to descendant processes with the following commands: $ sudo sysctl kernel.yama.ptrace_scope kernel.yama.ptrace_scope = 1 If the returned line does not have a value of "1" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r kernel.yama.ptrace_scope /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: kernel.yama.ptrace_scope = 1 If "kernel.yama.ptrace_scope" is not set to "1", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52278r858682_fix
Configure the system to restrict the use of "ptrace" to descendant processes by adding the following line to a file in the "/etc/sysctl.d" directory: kernel.yama.ptrace_scope = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040283
- Vuln IDs
-
- V-248891
- Rule IDs
-
- SV-248891r858685_rule
Checks: C-52325r833281_chk
Verify OL 8 restricts exposed kernel pointer addresses access with the following commands: $ sudo sysctl kernel.kptr_restrict kernel.kptr_restrict = 1 If the returned line does not have a value of "1" or "2" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r kernel.kptr_restrict /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: kernel.kptr_restrict = 1 If "kernel.kptr_restrict" is not set to "1" or "2", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52279r858684_fix
Configure the system to restrict exposed kernel pointer addresses access by adding the following line to a file in the "/etc/sysctl.d" directory: kernel.kptr_restrict = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040284
- Vuln IDs
-
- V-248892
- Rule IDs
-
- SV-248892r928562_rule
Checks: C-52326r928560_chk
Verify OL 8 disables the use of user namespaces with the following commands. Note: If unprivileged user namespaces or "rootless" containers are in use, this requirement is not applicable. $ sudo sysctl user.max_user_namespaces user.max_user_namespaces = 0 If the returned line does not have a value of "0" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r user.max_user_namespaces /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: user.max_user_namespaces = 0 If "user.max_user_namespaces" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52280r928561_fix
Configure the system to disable the use of user namespaces by adding the following line to a file in the "/etc/sysctl.d" directory: user.max_user_namespaces = 0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040285
- Vuln IDs
-
- V-248893
- Rule IDs
-
- SV-248893r858689_rule
Checks: C-52327r833285_chk
Verify OL 8 uses reverse path filtering on all IPv4 interfaces with the following commands: $ sudo sysctl net.ipv4.conf.all.rp_filter net.ipv4.conf.all.rp_filter = 1 If the returned line does not have a value of "1" or "2" or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.ipv4.conf.all.rp_filter /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.all.rp_filter = 1 If "net.ipv4.conf.all.rp_filter" is not set to "1" or "2", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52281r858688_fix
Configure the system to use reverse path filtering on all IPv4 interfaces by adding the following line to a file in the "/etc/sysctl.d" directory: net.ipv4.conf.all.rp_filter = 1 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files must be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040286
- Vuln IDs
-
- V-248894
- Rule IDs
-
- SV-248894r858691_rule
Checks: C-52328r833287_chk
Verify OL 8 enables hardening for the BPF JIT with the following commands: $ sudo sysctl net.core.bpf_jit_harden net.core.bpf_jit_harden = 2 If the returned line does not have a value of "2", or a line is not returned, this is a finding. Check that the configuration files are present to enable this network parameter. $ sudo grep -r net.core.bpf_jit_harden /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.core.bpf_jit_harden = 2 If "net.core.bpf_jit_harden" is not set to "2", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52282r858690_fix
Configure OL 8 to enable hardening for the BPF JIT compiler by adding the following line to a file in the "/etc/sysctl.d" directory: net.core.bpf_jit_harden = 2 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040290
- Vuln IDs
-
- V-248895
- Rule IDs
-
- SV-248895r780251_rule
Checks: C-52329r780249_chk
Verify the system is configured to prevent unrestricted mail relaying. Determine if "postfix" is installed with the following commands: $ sudo yum list installed postfix postfix.x86_64 2:3.3.1-9.el8 If postfix is not installed, this is not applicable. If postfix is installed, determine if it is configured to reject connections from unknown or untrusted networks with the following command: $ sudo postconf -n smtpd_client_restrictions smtpd_client_restrictions = permit_mynetworks, reject If the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject", this is a finding.
Fix: F-52283r780250_fix
If "postfix" is installed, 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'
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-040300
- Vuln IDs
-
- V-248896
- Rule IDs
-
- SV-248896r780254_rule
Checks: C-52330r780252_chk
Verify the file integrity tool is configured to verify extended attributes. If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. Note: AIDE is highly configurable at install time. This requirement assumes the "aide.conf" file is under the "/etc" directory. Use the following command to determine if the file is in another location: $ sudo find / -name aide.conf Check the "aide.conf" file to determine if the "xattrs" rule has been added to the rule list being applied to the files and directories selection lists. An example rule that includes the "xattrs" rule follows: All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux /bin All # apply the custom rule to the files in bin /sbin All # apply the same custom rule to the files in sbin If the "xattrs" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.
Fix: F-52284r780253_fix
Configure the file integrity tool to check file and directory extended attributes. If AIDE is installed, ensure the "xattrs" rule is present on all uncommented file and directory selection lists.
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- OL08-00-040310
- Vuln IDs
-
- V-248897
- Rule IDs
-
- SV-248897r880561_rule
Checks: C-52331r880560_chk
Verify the file integrity tool is configured to verify ACLs. Use the following command to determine if the file is in a location other than "/etc/aide/aide.conf": $ sudo find / -name aide.conf Check the "aide.conf" file to determine if the "acl" rule has been added to the rule list being applied to the files and directories selection lists with the following command: $ sudo grep -E "[+]?acl" /etc/aide.conf VarFile = OwnerMode+n+l+X+acl If the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file or is commented out, or ACLs are not being checked by another file integrity tool, this is a finding.
Fix: F-52285r780256_fix
Configure the file integrity tool to check file and directory ACLs. If AIDE is installed, ensure the "acl" rule is present on all file and directory selection lists.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040320
- Vuln IDs
-
- V-248898
- Rule IDs
-
- SV-248898r780260_rule
Checks: C-52332r780258_chk
Verify that if the system has a display server installed, it is authorized. Check for the display server package with the following example command: $ sudo rpm -qa | grep xorg | grep server Ask the System Administrator if use of the display server is an operational requirement. If the use of a display server on the system is not documented with the Information System Security Officer (ISSO), this is a finding.
Fix: F-52286r780259_fix
Document the requirement for a display server with the ISSO or remove the related packages with the following example command: $ sudo rpm -e xorg-x11-server-common
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040330
- Vuln IDs
-
- V-248899
- Rule IDs
-
- SV-248899r780263_rule
Checks: C-52333r780261_chk
Verify network interfaces are not in promiscuous mode unless approved by the ISSO and documented. Check for the status with the following command: $ sudo ip link | grep -i promisc If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSO and documented, this is a finding.
Fix: F-52287r780262_fix
Configure network interfaces to turn off promiscuous mode unless approved by the ISSO and documented. Set the promiscuous mode of an interface to "off" with the following command: $ sudo ip link set dev <devicename> multicast off promisc off
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040340
- Vuln IDs
-
- V-248900
- Rule IDs
-
- SV-248900r858588_rule
Checks: C-52334r858587_chk
Verify "X11Forwarding" is disabled with the following command: $ sudo grep -ir x11forwarding /etc/ssh/sshd_config* | grep -v "^#" X11Forwarding no If the "X11Forwarding" keyword is set to "yes" and is not documented with the Information System Security Officer (ISSO) as an operational requirement or is missing, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52288r780265_fix
Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): X11Forwarding no The SSH service must be restarted for changes to take effect: $ sudo systemctl restart sshd
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040341
- Vuln IDs
-
- V-248901
- Rule IDs
-
- SV-248901r858590_rule
Checks: C-52335r858589_chk
Verify the OL 8 SSH daemon prevents remote hosts from connecting to the proxy display. Check the SSH "X11UseLocalhost" setting with the following command: $ sudo grep -ir x11uselocalhost /etc/ssh/sshd_config* X11UseLocalhost yes If the "X11UseLocalhost" keyword is set to "no", is missing, or is commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-52289r780268_fix
Configure the OL 8 SSH daemon to prevent remote hosts from connecting to the proxy display. Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11UseLocalhost" keyword and set its value to "yes" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): X11UseLocalhost yes
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040350
- Vuln IDs
-
- V-248902
- Rule IDs
-
- SV-248902r780272_rule
Checks: C-52336r780270_chk
Verify the TFTP daemon is configured to operate in secure mode with the following commands: $ sudo yum list installed tftp-server tftp-server.x86_64 x.x-x.el8 If a TFTP server is not installed, this is not applicable. If a TFTP server is installed, check for the server arguments with the following command: $ sudo grep server_args /etc/xinetd.d/tftp server_args = -s /var/lib/tftpboot If the "server_args" line does not have a "-s" option and a subdirectory is not assigned, this is a finding.
Fix: F-52290r780271_fix
Configure the TFTP daemon to operate in secure mode by adding the following line to "/etc/xinetd.d/tftp" (or modify the line to have the required value): server_args = -s /var/lib/tftpboot
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-040360
- Vuln IDs
-
- V-248903
- Rule IDs
-
- SV-248903r780275_rule
Checks: C-52337r780273_chk
Verify an FTP server has not been installed on the system with the following commands: $ sudo yum list installed | grep ftpd vsftpd-3.0.3.el8.x86_64.rpm If an FTP server is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fix: F-52291r780274_fix
Document the FTP server package with the ISSO as an operational requirement or remove it from the system with the following command: $ sudo yum remove vsftpd
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040370
- Vuln IDs
-
- V-248904
- Rule IDs
-
- SV-248904r780278_rule
Checks: C-52338r780276_chk
Determine if the "gssproxy" package is installed with the following command: $ sudo yum list installed gssproxy If the "gssproxy" package is installed, this is a finding.
Fix: F-52292r780277_fix
Configure OL 8 to disable non-essential capabilities by removing the "gssproxy" package from the system with the following command: $ sudo yum remove gssproxy
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040380
- Vuln IDs
-
- V-248905
- Rule IDs
-
- SV-248905r780281_rule
Checks: C-52339r780279_chk
Determine if the "iprutils" package is installed with the following command: $ sudo yum list installed iprutils If the "iprutils" package is installed, this is a finding.
Fix: F-52293r780280_fix
Configure OL 8 to disable non-essential capabilities by removing the "iprutils" package from the system with the following command: $ sudo yum remove iprutils
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040390
- Vuln IDs
-
- V-248906
- Rule IDs
-
- SV-248906r780284_rule
Checks: C-52340r780282_chk
Determine if the "tuned" package is installed with the following command: $ sudo yum list installed tuned If the "tuned" package is installed, this is a finding.
Fix: F-52294r780283_fix
Configure OL 8 to disable non-essential capabilities by removing the "tuned" package from the system with the following command: $ sudo yum remove tuned
- RMF Control
- AC-6
- Severity
- Medium
- CCI
- CCI-002235
- Version
- OL08-00-040400
- Vuln IDs
-
- V-248907
- Rule IDs
-
- SV-248907r928804_rule
Checks: C-52341r928563_chk
Verify the operating system prevents nonprivileged users from executing privileged functions, including disabling, circumventing, or altering implemented security safeguards/countermeasures. Obtain a list of authorized users (other than system administrator and guest accounts) for the system. Check the list against the system by using the following command: $ sudo semanage login -l | more Login Name SELinux User MLS/MCS Range Service __default__ user_u s0-s0:c0.c1023 * root unconfined_u s0-s0:c0.c1023 * system_u system_u s0-s0:c0.c1023 * joe staff_u s0-s0:c0.c1023 * All administrators must be mapped to the "sysadm_u", "staff_u", or an appropriately tailored confined role as defined by the organization. All authorized nonadministrative users must be mapped to the "user_u" role. If they are not mapped in this way, this is a finding.
Fix: F-52295r928804_fix
Configure OL 8 to prevent nonprivileged users from executing privileged functions, including disabling, circumventing, or altering implemented security safeguards/countermeasures. Use the following command to map a new user to the "sysadm_u" role: $ sudo semanage login -a -s sysadm_u <username> Use the following command to map an existing user to the "sysadm_u" role: $ sudo semanage login -m -s sysadm_u <username> Use the following command to map a new user to the "staff_u" role: $ sudo semanage login -a -s staff_u <username> Use the following command to map an existing user to the "staff_u" role: $ sudo semanage login -m -s staff_u <username> Use the following command to map a new user to the "user_u" role: $ sudo semanage login -a -s user_u <username> Use the following command to map an existing user to the "user_u" role: $ sudo semanage login -m -s user_u <username> Note: SELinux confined users mapped to sysadm_u are not allowed to log in to the system over SSH, by default. If this is a required function, it can be configured by setting the ssh_sysadm_login SELinux boolean to "on" with the following command: $ sudo setsebool -P ssh_sysadm_login on This must be documented with the information system security officer (ISSO) as an operational requirement.
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- OL08-00-010121
- Vuln IDs
-
- V-252650
- Rule IDs
-
- SV-252650r818746_rule
Checks: C-56106r818744_chk
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.
Fix: F-56056r818745_fix
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]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010331
- Vuln IDs
-
- V-252651
- Rule IDs
-
- SV-252651r818749_rule
Checks: C-56107r818747_chk
Verify the system-wide shared library directories within "/lib", "/lib64", "/usr/lib" and "/usr/lib64" have mode "755" or less permissive with the following command: $ sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type d -exec stat -c "%n %a" '{}' \; If any system-wide shared library directories are found to be group-writable or world-writable, this is a finding.
Fix: F-56057r818748_fix
Configure the library directories to be protected from unauthorized access. Run the following command, replacing "[DIRECTORY]" with any library directory with a mode more permissive than 755. $ sudo chmod 755 [DIRECTORY]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010341
- Vuln IDs
-
- V-252652
- Rule IDs
-
- SV-252652r818752_rule
Checks: C-56108r818750_chk
Verify the system-wide shared library directories are owned by "root" with the following command: $ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; If any system wide shared library directory is returned, this is a finding.
Fix: F-56058r818751_fix
Configure the system-wide shared library directories within (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. Run the following command, replacing "[DIRECTORY]" with any library directory not owned by "root". $ sudo chown root [DIRECTORY]
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001499
- Version
- OL08-00-010351
- Vuln IDs
-
- V-252653
- Rule IDs
-
- SV-252653r818755_rule
Checks: C-56109r818753_chk
Verify the system-wide shared library directories are group-owned by "root" with the following command: $ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; If any system wide shared library directory is returned and is not group-owned by a required system account, this is a finding.
Fix: F-56059r818754_fix
Configure the system-wide shared library directories (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access. Run the following command, replacing "[DIRECTORY]" with any library directory not group-owned by "root". $ sudo chgrp root [DIRECTORY]
- RMF Control
- SI-6
- Severity
- Medium
- CCI
- CCI-002696
- Version
- OL08-00-010359
- Vuln IDs
-
- V-252654
- Rule IDs
-
- SV-252654r880573_rule
Checks: C-56110r880571_chk
Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions. Check that the AIDE package is installed with the following command: $ sudo rpm -q aide aide-0.16-14.el8_5.1.x86_64 If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. If there is no application installed to perform integrity checks, this is a finding. If AIDE is installed, check if it has been initialized with the following command: $ sudo /usr/sbin/aide --check If the output is "Couldn't open file /var/lib/aide/aide.db.gz for reading", this is a finding.
Fix: F-56060r880572_fix
Install AIDE, initialize it, and perform a manual check. Install AIDE: $ sudo yum install aide Initialize it: $ sudo /usr/sbin/aide --init Example output: Number of entries: 48623 --------------------------------------------------- The attributes of the (uncompressed) database(s): --------------------------------------------------- /var/lib/aide/aide.db.new.gz SHA1 : LTAVQ8tFJthsrf4m9gfRpnf1vyc= SHA256 : NJ9+uzRQKSwmLQ8A6IpKNvYjVKGbhSjt BeJBVcmOVrI= SHA512 : 7d8I/F6A1b07E4ZuGeilZjefRgJJ/F20 eC2xoag1OsOVpctt3Mi7Jjjf3vFW4xoY 5mdS6/ImQpm0xtlTLOPeQQ== End timestamp: 2022-10-20 10:50:52 -0700 (run time: 0m 46s) The new database will need to be renamed to be read by AIDE: $ sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz Perform a manual check: $ sudo /usr/sbin/aide --check Example output: Start timestamp: 2022-10-20 11:03:16 -0700 (AIDE 0.16) AIDE found differences between database and filesystem!! ... Done.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-010379
- Vuln IDs
-
- V-252655
- Rule IDs
-
- SV-252655r880549_rule
Checks: C-56111r880547_chk
Note: If the "include" and "includedir" directives are not present in the /etc/sudoers file, this requirement is not applicable. Verify the operating system specifies only the default "include" directory for the /etc/sudoers file with the following command: $ sudo grep include /etc/sudoers #includedir /etc/sudoers.d If the results are not "/etc/sudoers.d" or additional files or directories are specified, this is a finding. Verify the operating system does not have nested "include" files or directories within the /etc/sudoers.d directory with the following command: $ sudo grep -Er include /etc/sudoers.d If results are returned, this is a finding.
Fix: F-56061r880548_fix
Configure the /etc/sudoers file to only include the /etc/sudoers.d directory. Edit the /etc/sudoers file with the following command: $ sudo visudo Add or modify the following line: #includedir /etc/sudoers.d
- RMF Control
- IA-11
- Severity
- Medium
- CCI
- CCI-002038
- Version
- OL08-00-010385
- Vuln IDs
-
- V-252656
- Rule IDs
-
- SV-252656r854184_rule
Checks: C-56112r818762_chk
Verify the operating system is not be 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.
Fix: F-56062r818763_fix
Configure the operating system to require users to supply a password for privilege escalation. Check the configuration of the "/etc/ pam.d/sudo" file with the following command: $ sudo vi /etc/pam.d/sudo Remove any occurrences of " pam_succeed_if " in the file.
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020101
- Vuln IDs
-
- V-252657
- Rule IDs
-
- SV-252657r902812_rule
Checks: C-56113r902810_chk
Verify the operating system uses "pwquality" to enforce the password complexity rules. Check for the use of "pwquality" in the system-auth file with the following command: $ sudo cat /etc/pam.d/system-auth | grep pam_pwquality password requisite pam_pwquality.so If the command does not return a line containing the value "pam_pwquality.so" as shown, or the line is commented out, this is a finding.
Fix: F-56063r902811_fix
Configure the operating system to use "pwquality" to enforce password complexity rules. Add the following line to the "/etc/pam.d/system-auth" file (or modify the line to have the required value): password requisite pam_pwquality.so
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020102
- Vuln IDs
-
- V-252658
- Rule IDs
-
- SV-252658r902815_rule
Checks: C-56114r902813_chk
Note: This requirement applies to OL versions 8.0 through 8.3. If the system is OL version 8.4 or newer, this requirement is not applicable. Verify the operating system is configured to limit the "pwquality" retry option to 3. Check for the use of the "pwquality" retry option in the system-auth file with the following command: $ sudo cat /etc/pam.d/system-auth | grep pam_pwquality password requisite pam_pwquality.so retry=3 If the value of "retry" is set to "0" or greater than "3", this is a finding.
Fix: F-56064r902814_fix
Configure the operating system to limit the "pwquality" retry option to 3. Add the following line to the "/etc/pam.d/system-auth" file (or modify the line to have the required value): password requisite pam_pwquality.so retry=3
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020103
- Vuln IDs
-
- V-252659
- Rule IDs
-
- SV-252659r902818_rule
Checks: C-56115r902816_chk
Note: This requirement applies to OL versions 8.0 through 8.3. If the system is OL version 8.4 or newer, this requirement is not applicable. Verify the operating system is configured to limit the "pwquality" retry option to 3. Check for the use of the "pwquality" retry option in the password-auth file with the following command: $ sudo cat /etc/pam.d/password-auth | grep pam_pwquality password requisite pam_pwquality.so retry=3 If the value of "retry" is set to "0" or greater than "3", this is a finding.
Fix: F-56065r902817_fix
Configure the operating system to limit the "pwquality" retry option to 3. Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value): password requisite pam_pwquality.so retry=3
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-020104
- Vuln IDs
-
- V-252660
- Rule IDs
-
- SV-252660r858600_rule
Checks: C-56116r858598_chk
Note: This requirement applies to OL versions 8.4 or newer. If the system is OL below version 8.4, this requirement is not applicable. Verify the operating system is configured to limit the "pwquality" retry option to 3. Check for the use of the "pwquality" retry option with the following command: $ sudo grep -r retry /etc/security/pwquality.conf* /etc/security/pwquality.conf:retry = 3 If the value of "retry" is set to "0" or greater than "3", is commented out or missing, this is a finding. If conflicting results are returned, this is a finding. Check for the use of the "pwquality" retry option in the system-auth and password-auth files with the following command: $ sudo grep pwquality /etc/pam.d/system-auth /etc/pam.d/password-auth | grep retry If the command returns any results, this is a finding.
Fix: F-56066r858599_fix
Configure the operating system to limit the "pwquality" retry option to 3. Add the following line to the "/etc/security/pwquality.conf" file(or modify the line to have the required value): retry = 3 Remove any configurations that conflict with the above value.
- RMF Control
- IA-5
- Severity
- Medium
- CCI
- CCI-000200
- Version
- OL08-00-020221
- Vuln IDs
-
- V-252661
- Rule IDs
-
- SV-252661r902824_rule
Checks: C-56117r902822_chk
Verify the operating system is configured in the system-auth file to prohibit password reuse for a minimum of five generations. Check for the value of the "remember" argument in "/etc/pam.d/system-auth" with the following command: $ sudo grep -i remember /etc/pam.d/system-auth password requisite pam_pwhistory.so use_authtok remember=5 retry=3 If the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "5", this is a finding.
Fix: F-56067r902823_fix
Configure the operating system in the system-auth file to prohibit password reuse for a minimum of five generations. Add the following line in "/etc/pam.d/system-auth" (or modify the line to have the required value): password requisite pam_pwhistory.so use_authtok remember=5 retry=3
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040259
- Vuln IDs
-
- V-252662
- Rule IDs
-
- SV-252662r858667_rule
Checks: C-56118r833263_chk
Verify OL 8 is not performing IPv4 packet forwarding, unless the system is a router. Check that IPv4 forwarding is disabled using the following command: $ sudo sysctl net.ipv4.conf.all.forwarding net.ipv4.conf.all.forwarding = 0 If the IPv4 forwarding value is not "0" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. Check that the configuration files are present to enable this network parameter: $ sudo grep -r net.ipv4.conf.all.forwarding /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf /etc/sysctl.d/99-sysctl.conf: net.ipv4.conf.all.forwarding = 0 If "net.ipv4.conf.all.forwarding" is not set to "0", is missing or commented out, this is a finding. If conflicting results are returned, this is a finding.
Fix: F-56068r858666_fix
Configure OL 8 to not allow IPv4 packet forwarding unless the system is a router. Add or edit the following line in a system configuration file, in the "/etc/sysctl.d/" directory: net.ipv4.conf.all.forwarding=0 Remove any configurations that conflict with the above from the following locations: /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf /etc/sysctl.d/*.conf Load settings from all system configuration files with the following command: $ sudo sysctl --system
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- OL08-00-040321
- Vuln IDs
-
- V-252663
- Rule IDs
-
- SV-252663r818785_rule
Checks: C-56119r818783_chk
Verify that the system is configured to boot to the command line: $ systemctl get-default multi-user.target If the system default target is not set to "multi-user.target" and the Information System Security Officer (ISSO) lacks a documented requirement for a graphical user interface, this is a finding.
Fix: F-56069r818784_fix
Document the requirement for a graphical user interface with the ISSO or reinstall the operating system without the graphical user interface. If reinstallation is not feasible, then continue with the following procedure: Open an SSH session and enter the following commands: $ sudo systemctl set-default multi-user.target A reboot is required for the changes to take effect.
- RMF Control
- AC-17
- Severity
- Medium
- CCI
- CCI-001453
- Version
- OL08-00-040342
- Vuln IDs
-
- V-255898
- Rule IDs
-
- SV-255898r917916_rule
Checks: C-59575r917915_chk
Verify that the SSH server is configured to use only FIPS-validated key exchange algorithms: $ sudo grep -i kexalgorithms /etc/crypto-policies/back-ends/opensshserver.config CRYPTO_POLICY='-oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512' If the entries following "KexAlgorithms" have any algorithms defined other than "ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512", appear in a different order than shown, or are missing or commented out, this is a finding.
Fix: F-59518r880543_fix
Configure the SSH server to use only FIPS-validated key exchange algorithms by adding or modifying the following line in "/etc/crypto-policies/back-ends/opensshserver.config": -oKexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512 A reboot is required for the changes to take effect.
- RMF Control
- CM-5
- Severity
- Medium
- CCI
- CCI-001749
- Version
- OL08-00-010019
- Vuln IDs
-
- V-256978
- Rule IDs
-
- SV-256978r902784_rule
Checks: C-60656r902782_chk
Confirm Oracle package-signing key is installed on the system and verify its fingerprint matches vendor value. Note: The GPG key is defined in key file "/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle" by default. List Oracle GPG keys installed on the system: $ sudo rpm -q --queryformat "%{SUMMARY}\n" gpg-pubkey | grep -i "oracle" gpg(Oracle OSS group (Open Source Software group) <build@oss.oracle.com>) If Oracle GPG key is not installed, this is a finding. List key fingerprint of installed Oracle GPG key: $ sudo gpg -q --keyid-format short --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle If key file "/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle" is missing, this is a finding. Example output: pub rsa4096/AD986DA3 2019-04-09 [SC] [expires: 2039-04-04] Key fingerprint = 76FD 3DB1 3AB6 7410 B89D B10E 8256 2EA9 AD98 6DA3 uid Oracle OSS group (Open Source Software group) <build@oss.oracle.com> sub rsa4096/D95DC12B 2019-04-09 [E] [expires: 2039-04-04] Compare key fingerprint of installed Oracle GPG key with fingerprint listed for OL 8 on Oracle verification webpage at https://linux.oracle.com/security/gpg/#gpg. If key fingerprint does not match, this is a finding.
Fix: F-60598r902783_fix
Install Oracle package-signing key on the system and verify its fingerprint matches vendor value. Insert OL 8 installation disc or attach OL 8 installation image to the system. Mount the disc or image to make the contents accessible inside the system. Assuming the mounted location is "/media/cdrom", use the following command to copy Oracle GPG key file onto the system: $ sudo cp /media/cdrom/RPM-GPG-KEY-oracle /etc/pki/rpm-gpg/ Import Oracle GPG keys from key file into system keyring: $ sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle Using the steps listed in the Check Text, confirm the newly imported key shows as installed on the system and verify its fingerprint matches vendor value.
- RMF Control
- CM-3
- Severity
- Medium
- CCI
- CCI-001744
- Version
- OL08-00-010358
- Vuln IDs
-
- V-256979
- Rule IDs
-
- SV-256979r902803_rule
Checks: C-60657r902801_chk
Verify that the operating system is configured to allow sending email notifications. Note: The "mailx" package provides the "mail" command that is used to send email messages. Verify that the "mailx" package is installed on the system: $ sudo yum list installed mailx mailx.x86_64 12.5-29.el8 @ol8_baseos_latest If "mailx" package is not installed, this is a finding.
Fix: F-60599r902802_fix
Install the "mailx" package on the system: $ sudo yum install mailx
- RMF Control
- SC-10
- Severity
- Medium
- CCI
- CCI-001133
- Version
- OL08-00-020035
- Vuln IDs
-
- V-257259
- Rule IDs
-
- SV-257259r917919_rule
Checks: C-60943r917917_chk
Verify that OL 8 logs out sessions that are idle for 15 minutes with the following command: $ sudo grep -i ^StopIdleSessionSec /etc/systemd/logind.conf StopIdleSessionSec=900 If "StopIdleSessionSec" is not configured to 900 seconds, this is a finding.
Fix: F-60885r917918_fix
Configure OL 8 to log out idle sessions by editing the /etc/systemd/logind.conf file with the following line: StopIdleSessionSec=900 The "logind" service must be restarted for the changes to take effect. To restart the "logind" service, run the following command: $ sudo systemctl restart systemd-logind