diff --git a/.gitignore b/.gitignore index 573eb37..8ecb471 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,2 @@ -SOURCES/scap-security-guide-0.1.50.tar.bz2 +SOURCES/scap-security-guide-0.1.52-2.el7_9-rhel6.tar.bz2 +SOURCES/scap-security-guide-0.1.54.tar.bz2 diff --git a/.scap-security-guide.metadata b/.scap-security-guide.metadata index d7de47e..517ac64 100644 --- a/.scap-security-guide.metadata +++ b/.scap-security-guide.metadata @@ -1 +1,2 @@ -1cf4a166c153a96841eb42384c2c76a4dee36919 SOURCES/scap-security-guide-0.1.50.tar.bz2 +b22b45d29ad5a97020516230a6ef3140a91d050a SOURCES/scap-security-guide-0.1.52-2.el7_9-rhel6.tar.bz2 +9c53524d1f6741913b19394fad9216f25f3ae05d SOURCES/scap-security-guide-0.1.54.tar.bz2 diff --git a/SOURCES/disable-not-in-good-shape-profiles.patch b/SOURCES/disable-not-in-good-shape-profiles.patch index 80b2a96..1d82938 100644 --- a/SOURCES/disable-not-in-good-shape-profiles.patch +++ b/SOURCES/disable-not-in-good-shape-profiles.patch @@ -1,24 +1,24 @@ -From 2dfbfa76867db56ee90f168b478437d916e0cd4e Mon Sep 17 00:00:00 2001 +From 48e959ebf2b892fefa642f19bc8cc1d2d639fb29 Mon Sep 17 00:00:00 2001 From: Watson Sato -Date: Fri, 17 Jan 2020 19:01:22 +0100 +Date: Thu, 3 Dec 2020 14:35:47 +0100 Subject: [PATCH] Disable profiles that are not in good shape for RHEL8 -They raise too many errors and fails. -Also disable tables for profiles that are not built. --- - rhel8/CMakeLists.txt | 2 -- - rhel8/profiles/cjis.profile | 2 +- - rhel8/profiles/rhelh-stig.profile | 2 +- - rhel8/profiles/rhelh-vpp.profile | 2 +- - rhel8/profiles/rht-ccp.profile | 2 +- - rhel8/profiles/standard.profile | 2 +- - 9 files changed, 8 insertions(+), 10 deletions(-) + rhel8/CMakeLists.txt | 6 ------ + rhel8/profiles/anssi_bp28_high.profile | 2 +- + rhel8/profiles/cjis.profile | 2 +- + rhel8/profiles/ism_o.profile | 2 +- + rhel8/profiles/rhelh-stig.profile | 2 +- + rhel8/profiles/rhelh-vpp.profile | 2 +- + rhel8/profiles/rht-ccp.profile | 2 +- + rhel8/profiles/standard.profile | 2 +- + 11 files changed, 10 insertions(+), 16 deletions(-) diff --git a/rhel8/CMakeLists.txt b/rhel8/CMakeLists.txt -index 40f2b2b0f..492a8dae1 100644 +index d61689c97..5e444a101 100644 --- a/rhel8/CMakeLists.txt +++ b/rhel8/CMakeLists.txt -@@ -14,9 +14,8 @@ ssg_build_html_table_by_ref(${PRODUCT} "cis") +@@ -14,15 +14,9 @@ ssg_build_html_table_by_ref(${PRODUCT} "cis") ssg_build_html_table_by_ref(${PRODUCT} "pcidss") ssg_build_html_table_by_ref(${PRODUCT} "anssi") @@ -26,18 +26,44 @@ index 40f2b2b0f..492a8dae1 100644 ssg_build_html_nistrefs_table(${PRODUCT} "ospp") ssg_build_html_nistrefs_table(${PRODUCT} "stig") - # Uncomment when anssi profiles are marked documentation_complete: true - #ssg_build_html_anssirefs_table(${PRODUCT} "nt28_minimal") +-ssg_build_html_anssirefs_table(${PRODUCT} "bp28_minimal") +-ssg_build_html_anssirefs_table(${PRODUCT} "bp28_intermediary") +-ssg_build_html_anssirefs_table(${PRODUCT} "bp28_enhanced") +-ssg_build_html_anssirefs_table(${PRODUCT} "bp28_high") +- + ssg_build_html_cce_table(${PRODUCT}) + + ssg_build_html_srgmap_tables(${PRODUCT} "stig" ${DISA_SRG_TYPE}) +diff --git a/rhel8/profiles/anssi_bp28_high.profile b/rhel8/profiles/anssi_bp28_high.profile +index ccad93d67..6a854378c 100644 +--- a/rhel8/profiles/anssi_bp28_high.profile ++++ b/rhel8/profiles/anssi_bp28_high.profile +@@ -1,4 +1,4 @@ +-documentation_complete: true ++documentation_complete: false + + title: 'ANSSI BP-028 (high)' + diff --git a/rhel8/profiles/cjis.profile b/rhel8/profiles/cjis.profile -index 05ea9cdd6..9c55ac5b1 100644 +index 035d2705b..c6475f33e 100644 --- a/rhel8/profiles/cjis.profile +++ b/rhel8/profiles/cjis.profile @@ -1,4 +1,4 @@ -documentation_complete: true +documentation_complete: false - title: 'Criminal Justice Information Services (CJIS) Security Policy' + metadata: + version: 5.4 +diff --git a/rhel8/profiles/ism_o.profile b/rhel8/profiles/ism_o.profile +index a3c427c01..4605dea3b 100644 +--- a/rhel8/profiles/ism_o.profile ++++ b/rhel8/profiles/ism_o.profile +@@ -1,4 +1,4 @@ +-documentation_complete: true ++documentation_complete: false + metadata: + SMEs: diff --git a/rhel8/profiles/rhelh-stig.profile b/rhel8/profiles/rhelh-stig.profile index 1efca5f44..c3d0b0964 100644 --- a/rhel8/profiles/rhelh-stig.profile @@ -79,5 +105,5 @@ index a63ae2cf3..da669bb84 100644 title: 'Standard System Security Profile for Red Hat Enterprise Linux 8' -- -2.21.1 +2.26.2 diff --git a/SOURCES/remove-ANSSI-high-ks.patch b/SOURCES/remove-ANSSI-high-ks.patch new file mode 100644 index 0000000..5298c70 --- /dev/null +++ b/SOURCES/remove-ANSSI-high-ks.patch @@ -0,0 +1,187 @@ +From 8e43a6a6432a8cbeb5742771ddbd0856669a7878 Mon Sep 17 00:00:00 2001 +From: Watson Sato +Date: Wed, 17 Feb 2021 15:36:59 +0100 +Subject: [PATCH] Remove kickstart for profile not shipped + +RHEL-8 ANSSI high is not shipped at the momment +--- + .../ssg-rhel8-anssi_bp28_high-ks.cfg | 167 ------------------ + 1 file changed, 167 deletions(-) + delete mode 100644 rhel8/kickstart/ssg-rhel8-anssi_bp28_high-ks.cfg + +diff --git a/rhel8/kickstart/ssg-rhel8-anssi_bp28_high-ks.cfg b/rhel8/kickstart/ssg-rhel8-anssi_bp28_high-ks.cfg +deleted file mode 100644 +index b5c09253a..000000000 +--- a/rhel8/kickstart/ssg-rhel8-anssi_bp28_high-ks.cfg ++++ /dev/null +@@ -1,167 +0,0 @@ +-# SCAP Security Guide ANSSI BP-028 (high) profile kickstart for Red Hat Enterprise Linux 8 +-# Version: 0.0.1 +-# Date: 2020-12-10 +-# +-# Based on: +-# https://pykickstart.readthedocs.io/en/latest/ +-# http://usgcb.nist.gov/usgcb/content/configuration/workstation-ks.cfg +- +-# Specify installation method to use for installation +-# To use a different one comment out the 'url' one below, update +-# the selected choice with proper options & un-comment it +-# +-# Install from an installation tree on a remote server via FTP or HTTP: +-# --url the URL to install from +-# +-# Example: +-# +-# url --url=http://192.168.122.1/image +-# +-# Modify concrete URL in the above example appropriately to reflect the actual +-# environment machine is to be installed in +-# +-# Other possible / supported installation methods: +-# * install from the first CD-ROM/DVD drive on the system: +-# +-# cdrom +-# +-# * install from a directory of ISO images on a local drive: +-# +-# harddrive --partition=hdb2 --dir=/tmp/install-tree +-# +-# * install from provided NFS server: +-# +-# nfs --server= --dir= [--opts=] +-# +-# Set language to use during installation and the default language to use on the installed system (required) +-lang en_US.UTF-8 +- +-# Set system keyboard type / layout (required) +-keyboard us +- +-# Configure network information for target system and activate network devices in the installer environment (optional) +-# --onboot enable device at a boot time +-# --device device to be activated and / or configured with the network command +-# --bootproto method to obtain networking configuration for device (default dhcp) +-# --noipv6 disable IPv6 on this device +-# +-# NOTE: Usage of DHCP will fail CCE-27021-5 (DISA FSO RHEL-06-000292). To use static IP configuration, +-# "--bootproto=static" must be used. For example: +-# network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1 +-# +-network --onboot yes --bootproto dhcp --noipv6 +- +-# Set the system's root password (required) +-# Plaintext password is: server +-# Refer to e.g. +-# https://pykickstart.readthedocs.io/en/latest/commands.html#rootpw +-# to see how to create encrypted password form for different plaintext password +-rootpw --iscrypted $6$0WWGZ1e6icT$1KiHZK.Nzp3HQerfiy8Ic3pOeCWeIzA.zkQ7mkvYT3bNC5UeGK2ceE5b6TkSg4D/kiSudkT04QlSKknsrNE220 +- +-# The selected profile will restrict root login +-# Add a user that can login and escalate privileges +-# Plaintext password is: admin123 +-user --name=admin --groups=wheel --password=$6$Ga6ZnIlytrWpuCzO$q0LqT1USHpahzUafQM9jyHCY9BiE5/ahXLNWUMiVQnFGblu0WWGZ1e6icTaCGO4GNgZNtspp1Let/qpM7FMVB0 --iscrypted +- +-# Configure firewall settings for the system (optional) +-# --enabled reject incoming connections that are not in response to outbound requests +-# --ssh allow sshd service through the firewall +-firewall --enabled --ssh +- +-# State of SELinux on the installed system (optional) +-# Defaults to enforcing +-selinux --enforcing +- +-# Set the system time zone (required) +-timezone --utc America/New_York +- +-# Specify how the bootloader should be installed (required) +-# Plaintext password is: password +-# Refer to e.g. +-# https://pykickstart.readthedocs.io/en/latest/commands.html#rootpw +-# to see how to create encrypted password form for different plaintext password +-bootloader --location=mbr --append="audit=1 audit_backlog_limit=8192" --password=$6$zCPaBARiNlBYUAS7$40phthWpqvaPVz3QUeIK6n5qoazJDJD5Nlc9OKy5SyYoX9Rt4jFaLjzqJCwpgR4RVAEFSADsqQot0WKs5qNto0 +- +-# Initialize (format) all disks (optional) +-zerombr +- +-# The following partition layout scheme assumes disk of size 20GB or larger +-# Modify size of partitions appropriately to reflect actual machine's hardware +-# +-# Remove Linux partitions from the system prior to creating new ones (optional) +-# --linux erase all Linux partitions +-# --initlabel initialize the disk label to the default based on the underlying architecture +-clearpart --linux --initlabel +- +-# Create primary system partitions (required for installs) +-part /boot --fstype=xfs --size=512 --fsoptions="nodev,nosuid,noexec" +-part pv.01 --grow --size=1 +- +-# Create a Logical Volume Management (LVM) group (optional) +-volgroup VolGroup --pesize=4096 pv.01 +- +-# Create particular logical volumes (optional) +-logvol / --fstype=xfs --name=LogVol06 --vgname=VolGroup --size=3192 --grow +-# Ensure /usr Located On Separate Partition +-logvol /usr --fstype=xfs --name=LogVol08 --vgname=VolGroup --size=5000 --fsoptions="nodev" +-# Ensure /opt Located On Separate Partition +-logvol /opt --fstype=xfs --name=LogVol09 --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid" +-# Ensure /srv Located On Separate Partition +-logvol /srv --fstype=xfs --name=LogVol10 --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid" +-# Ensure /home Located On Separate Partition +-logvol /home --fstype=xfs --name=home --vgname=VolGroup --size=1024 --fsoptions="nodev" +-# Ensure /tmp Located On Separate Partition +-logvol /tmp --fstype=xfs --name=tmp --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec" +-# Ensure /var/tmp Located On Separate Partition +-logvol /var/tmp --fstype=xfs --name=vartmp --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec" +-# Ensure /var Located On Separate Partition +-logvol /var --fstype=xfs --name=var --vgname=VolGroup --size=3072 --fsoptions="nodev" +-# Ensure /var/log Located On Separate Partition +-logvol /var/log --fstype=xfs --name=log --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec" +-# Ensure /var/log/audit Located On Separate Partition +-logvol /var/log/audit --fstype=xfs --name=audit --vgname=VolGroup --size=512 --fsoptions="nodev,nosuid,noexec" +-logvol swap --name=swap --vgname=VolGroup --size=2016 +- +-# The OpenSCAP installer add-on is used to apply SCAP (Security Content Automation Protocol) +-# content - security policies - on the installed system.This add-on has been enabled by default +-# since Red Hat Enterprise Linux 7.2. When enabled, the packages necessary to provide this +-# functionality will automatically be installed. However, by default, no policies are enforced, +-# meaning that no checks are performed during or after installation unless specifically configured. +-# +-# Important +-# Applying a security policy is not necessary on all systems. This screen should only be used +-# when a specific policy is mandated by your organization rules or government regulations. +-# Unlike most other commands, this add-on does not accept regular options, but uses key-value +-# pairs in the body of the %addon definition instead. These pairs are whitespace-agnostic. +-# Values can be optionally enclosed in single quotes (') or double quotes ("). +-# +-# The following keys are recognized by the add-on: +-# content-type - Type of the security content. Possible values are datastream, archive, rpm, and scap-security-guide. +-# - If the content-type is scap-security-guide, the add-on will use content provided by the +-# scap-security-guide package, which is present on the boot media. This means that all other keys except profile will have no effect. +-# content-url - Location of the security content. The content must be accessible using HTTP, HTTPS, or FTP; local storage is currently not supported. A network connection must be available to reach content definitions in a remote location. +-# datastream-id - ID of the data stream referenced in the content-url value. Used only if content-type is datastream. +-# xccdf-id - ID of the benchmark you want to use. +-# xccdf-path - Path to the XCCDF file which should be used; given as a relative path in the archive. +-# profile - ID of the profile to be applied. Use default to apply the default profile. +-# fingerprint - A MD5, SHA1 or SHA2 checksum of the content referenced by content-url. +-# tailoring-path - Path to a tailoring file which should be used, given as a relative path in the archive. +-# +-# The following is an example %addon org_fedora_oscap section which uses content from the +-# scap-security-guide on the installation media: +-%addon org_fedora_oscap +- content-type = scap-security-guide +- profile = xccdf_org.ssgproject.content_profile_anssi_bp28_high +-%end +- +-# Packages selection (%packages section is required) +-%packages +- +-# Require @Base +-@Base +- +-%end # End of %packages section +- +-# Reboot after the installation is complete (optional) +-# --eject attempt to eject CD or DVD media before rebooting +-reboot --eject +-- +2.26.2 + diff --git a/SOURCES/scap-security-guide-0.1.51-add-zipl-and-grub2-cpes_PR_5905.patch b/SOURCES/scap-security-guide-0.1.51-add-zipl-and-grub2-cpes_PR_5905.patch deleted file mode 100644 index d7fab70..0000000 --- a/SOURCES/scap-security-guide-0.1.51-add-zipl-and-grub2-cpes_PR_5905.patch +++ /dev/null @@ -1,737 +0,0 @@ -From 3aae2f86f3d75b8bd931922152b9a6175ed18a6b Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 23 Jun 2020 22:27:47 +0200 -Subject: [PATCH 1/5] Add check for zipl installed - -Based and valid in RHEL, where zipl is part of s390utils-base. ---- - rhel8/cpe/rhel8-cpe-dictionary.xml | 4 ++ - .../oval/installed_env_has_zipl_package.xml | 37 +++++++++++++++++++ - ssg/constants.py | 1 + - 3 files changed, 42 insertions(+) - create mode 100644 shared/checks/oval/installed_env_has_zipl_package.xml - -diff --git a/rhel8/cpe/rhel8-cpe-dictionary.xml b/rhel8/cpe/rhel8-cpe-dictionary.xml -index 694cbb5a4e..cccb3c5791 100644 ---- a/rhel8/cpe/rhel8-cpe-dictionary.xml -+++ b/rhel8/cpe/rhel8-cpe-dictionary.xml -@@ -67,4 +67,8 @@ - - installed_env_has_yum_package - -+ -+ System uses zipl -+ installed_env_has_zipl_package -+ - -diff --git a/shared/checks/oval/installed_env_has_zipl_package.xml b/shared/checks/oval/installed_env_has_zipl_package.xml -new file mode 100644 -index 0000000000..ab6545669d ---- /dev/null -+++ b/shared/checks/oval/installed_env_has_zipl_package.xml -@@ -0,0 +1,37 @@ -+ -+ -+ -+ System uses zIPL -+ -+ multi_platform_all -+ -+ Checks if system uses zIPL bootloader. -+ -+ -+ -+ -+ -+ -+ -+{{% if pkg_system == "rpm" %}} -+ -+ -+ -+ -+ s390utils-base -+ -+{{% elif pkg_system == "dpkg" %}} -+ -+ -+ -+ -+ s390utils-base -+ -+{{% endif %}} -+ -+ -diff --git a/ssg/constants.py b/ssg/constants.py -index fb20fe8107..f03aa87f09 100644 ---- a/ssg/constants.py -+++ b/ssg/constants.py -@@ -506,6 +506,7 @@ - "sssd": "cpe:/a:sssd", - "systemd": "cpe:/a:systemd", - "yum": "cpe:/a:yum", -+ "zipl": "cpe:/a:zipl", - } - - # _version_name_map = { - -From c70bdc89bf193f2fdf59cb8c3f06672fc43a0505 Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 23 Jun 2020 22:33:07 +0200 -Subject: [PATCH 2/5] Set zipl and machine platforms for zipl content - -Add zipl platform to bootloader-zipl and machine platform to all zipl -rules. -Final applicability of zipl rules is equivalent to "machine and zipl" -CPE platform. ---- - linux_os/guide/system/bootloader-zipl/group.yml | 2 +- - .../guide/system/bootloader-zipl/zipl_audit_argument/rule.yml | 2 ++ - .../bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml | 2 ++ - .../guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml | 2 ++ - .../system/bootloader-zipl/zipl_page_poison_argument/rule.yml | 2 ++ - .../guide/system/bootloader-zipl/zipl_pti_argument/rule.yml | 2 ++ - .../system/bootloader-zipl/zipl_slub_debug_argument/rule.yml | 2 ++ - .../system/bootloader-zipl/zipl_vsyscall_argument/rule.yml | 2 ++ - 8 files changed, 15 insertions(+), 1 deletion(-) - -diff --git a/linux_os/guide/system/bootloader-zipl/group.yml b/linux_os/guide/system/bootloader-zipl/group.yml -index 36da84530c..64c6c8dffb 100644 ---- a/linux_os/guide/system/bootloader-zipl/group.yml -+++ b/linux_os/guide/system/bootloader-zipl/group.yml -@@ -8,4 +8,4 @@ description: |- - options to it. - The default {{{ full_name }}} boot loader for s390x systems is called zIPL. - --platform: machine -+platform: zipl -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml -index 16c0b3f89a..2d31ef8ee7 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml -@@ -38,3 +38,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml -index 47a532d50f..40db232257 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml -@@ -39,3 +39,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml -index 5aa91c16aa..8d28d5495f 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml -@@ -35,3 +35,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml -index 8546325752..0a8e9a41e2 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml -@@ -39,3 +39,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml -index eaef25ce40..20c1448cc8 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml -@@ -38,3 +38,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml -index 68e91a92d6..54ac688ea0 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml -@@ -39,3 +39,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml -index 9624b43349..c5979a2016 100644 ---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml -+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml -@@ -36,3 +36,5 @@ ocil: |- - and /etc/zipl.conf: - 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
- No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -+ -+platform: machine - -From 02f961ecbe8bcafab72f544c2bc0f9141b9fa8fa Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 23 Jun 2020 23:02:44 +0200 -Subject: [PATCH 3/5] Add check for grub2 installed - -Apply new CPE grub2 to bootloader-grub2 group. ---- - .../file_groupowner_efi_grub2_cfg/rule.yml | 2 + - .../file_groupowner_grub2_cfg/rule.yml | 2 + - .../file_owner_efi_grub2_cfg/rule.yml | 2 + - .../file_owner_grub2_cfg/rule.yml | 2 + - .../guide/system/bootloader-grub2/group.yml | 2 +- - .../grub2_admin_username/rule.yml | 2 + - .../grub2_enable_iommu_force/rule.yml | 2 + - .../grub2_no_removeable_media/rule.yml | 2 + - .../bootloader-grub2/grub2_password/rule.yml | 2 + - .../grub2_uefi_admin_username/rule.yml | 2 + - .../grub2_uefi_password/rule.yml | 2 + - .../uefi_no_removeable_media/rule.yml | 2 + - .../oval/installed_env_has_grub2_package.xml | 37 +++++++++++++++++++ - ssg/constants.py | 1 + - 14 files changed, 61 insertions(+), 1 deletion(-) - create mode 100644 shared/checks/oval/installed_env_has_grub2_package.xml - -diff --git a/linux_os/guide/system/bootloader-grub2/file_groupowner_efi_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/file_groupowner_efi_grub2_cfg/rule.yml -index b5b583bd28..a6ac6f7b6b 100644 ---- a/linux_os/guide/system/bootloader-grub2/file_groupowner_efi_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/file_groupowner_efi_grub2_cfg/rule.yml -@@ -51,6 +51,8 @@ ocil: |- - {{{ ocil_file_group_owner(file="/boot/efi/EFI/redhat/grub.cfg", group="root") }}} - {{%- endif %}} - -+platform: machine -+ - template: - name: file_groupowner - vars: -diff --git a/linux_os/guide/system/bootloader-grub2/file_groupowner_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/file_groupowner_grub2_cfg/rule.yml -index 9d89ff5755..93dbf5222d 100644 ---- a/linux_os/guide/system/bootloader-grub2/file_groupowner_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/file_groupowner_grub2_cfg/rule.yml -@@ -39,6 +39,8 @@ ocil_clause: '{{{ ocil_clause_file_group_owner(file="/boot/grub2/grub.cfg", grou - - ocil: '{{{ ocil_file_group_owner(file="/boot/grub2/grub.cfg", group="root") }}}' - -+platform: machine -+ - template: - name: file_groupowner - vars: -diff --git a/linux_os/guide/system/bootloader-grub2/file_owner_efi_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/file_owner_efi_grub2_cfg/rule.yml -index ed17987478..e2c118cf0a 100644 ---- a/linux_os/guide/system/bootloader-grub2/file_owner_efi_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/file_owner_efi_grub2_cfg/rule.yml -@@ -49,6 +49,8 @@ ocil: |- - {{{ ocil_file_owner(file="/boot/efi/EFI/redhat/grub.cfg", owner="root") }}} - {{%- endif %}} - -+platform: machine -+ - template: - name: file_owner - vars: -diff --git a/linux_os/guide/system/bootloader-grub2/file_owner_grub2_cfg/rule.yml b/linux_os/guide/system/bootloader-grub2/file_owner_grub2_cfg/rule.yml -index 9ce4c3d60b..5086553921 100644 ---- a/linux_os/guide/system/bootloader-grub2/file_owner_grub2_cfg/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/file_owner_grub2_cfg/rule.yml -@@ -37,6 +37,8 @@ ocil_clause: '{{{ ocil_clause_file_owner(file="/boot/grub2/grub.cfg", owner="roo - - ocil: '{{{ ocil_file_owner(file="/boot/grub2/grub.cfg", owner="root") }}}' - -+platform: machine -+ - template: - name: file_owner - vars: -diff --git a/linux_os/guide/system/bootloader-grub2/group.yml b/linux_os/guide/system/bootloader-grub2/group.yml -index 69489bc0c2..4ffb40c0e8 100644 ---- a/linux_os/guide/system/bootloader-grub2/group.yml -+++ b/linux_os/guide/system/bootloader-grub2/group.yml -@@ -15,4 +15,4 @@ description: |- - with a password and ensure its configuration file's permissions - are set properly. - --platform: machine -+platform: grub2 -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml -index 63a6a7a83c..15db01a75f 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml -@@ -68,3 +68,5 @@ warnings: - - Also, do NOT manually add the superuser account and password to the - grub.cfg file as the grub2-mkconfig command overwrites this file. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_enable_iommu_force/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_enable_iommu_force/rule.yml -index baade9c13e..d4f455e66a 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_enable_iommu_force/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_enable_iommu_force/rule.yml -@@ -17,3 +17,5 @@ identifiers: - - references: - anssi: NT28(R11) -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_no_removeable_media/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_no_removeable_media/rule.yml -index 113726d34f..c8956c2f34 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_no_removeable_media/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_no_removeable_media/rule.yml -@@ -37,3 +37,5 @@ ocil: |- - usb0, cd, fd0, etc. are some examples of removeable - media which should not exist in the line: - 
set root='hd0,msdos1'
-+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml -index 985b8727d7..b6e9774608 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml -@@ -72,3 +72,5 @@ warnings: - - Also, do NOT manually add the superuser account and password to the - grub.cfg file as the grub2-mkconfig command overwrites this file. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_uefi_admin_username/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_uefi_admin_username/rule.yml -index 1926837db7..5abd86b9d9 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_uefi_admin_username/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_uefi_admin_username/rule.yml -@@ -75,3 +75,5 @@ warnings: - - Also, do NOT manually add the superuser account and password to the - grub.cfg file as the grub2-mkconfig command overwrites this file. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml -index 3ce5a2df13..3114d2d27c 100644 ---- a/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml -@@ -73,3 +73,5 @@ warnings: - - Also, do NOT manually add the superuser account and password to the - grub.cfg file as the grub2-mkconfig command overwrites this file. -+ -+platform: machine -diff --git a/linux_os/guide/system/bootloader-grub2/uefi_no_removeable_media/rule.yml b/linux_os/guide/system/bootloader-grub2/uefi_no_removeable_media/rule.yml -index c94185f3f4..5de05c057a 100644 ---- a/linux_os/guide/system/bootloader-grub2/uefi_no_removeable_media/rule.yml -+++ b/linux_os/guide/system/bootloader-grub2/uefi_no_removeable_media/rule.yml -@@ -35,3 +35,5 @@ ocil: |- - usb0, cd, fd0, etc. are some examples of removeable - media which should not exist in the line: - 
set root='hd0,msdos1'
-+ -+platform: machine -diff --git a/shared/checks/oval/installed_env_has_grub2_package.xml b/shared/checks/oval/installed_env_has_grub2_package.xml -new file mode 100644 -index 0000000000..e83f45bc3b ---- /dev/null -+++ b/shared/checks/oval/installed_env_has_grub2_package.xml -@@ -0,0 +1,37 @@ -+ -+ -+ -+ Package grub2 is installed -+ -+ multi_platform_all -+ -+ Checks if package grub2-pc is installed. -+ -+ -+ -+ -+ -+ -+ -+{{% if pkg_system == "rpm" %}} -+ -+ -+ -+ -+ grub2-pc -+ -+{{% elif pkg_system == "dpkg" %}} -+ -+ -+ -+ -+ grub2-pc -+ -+{{% endif %}} -+ -+ -diff --git a/ssg/constants.py b/ssg/constants.py -index f03aa87f09..318763b219 100644 ---- a/ssg/constants.py -+++ b/ssg/constants.py -@@ -498,6 +498,7 @@ - "container": "cpe:/a:container", - "chrony": "cpe:/a:chrony", - "gdm": "cpe:/a:gdm", -+ "grub2": "cpe:/a:grub2", - "libuser": "cpe:/a:libuser", - "nss-pam-ldapd": "cpe:/a:nss-pam-ldapd", - "ntp": "cpe:/a:ntp", - -From 8bb44ebe9c32b7916a7291b1fa5735b381494cfb Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Thu, 2 Jul 2020 16:58:14 +0200 -Subject: [PATCH 4/5] Move grub2_disable_interactive_boot to grub2 platform - -It should have both platforms machine and grub2. -But as the parent group is very broad, I cannot put parent group as -machine. - -As a side effect this change makes this rules applicable in containers. ---- - .../accounts-physical/grub2_disable_interactive_boot/rule.yml | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml b/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -index 3080470aa8..44ea1aa49a 100644 ---- a/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -+++ b/linux_os/guide/system/accounts/accounts-physical/grub2_disable_interactive_boot/rule.yml -@@ -48,4 +48,4 @@ ocil: |- - Presence of a systemd.confirm_spawn=(1|yes|true|on) indicates - that interactive boot is enabled at boot time. - --platform: machine -+platform: grub2 - -From 17ba5bc9ecc955911b7a3ab30bcd221283472b3f Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 23 Jun 2020 23:20:18 +0200 -Subject: [PATCH 5/5] Update CPE Dictionaries - -Again, whenever a package CPE is added, all CPE dictionaries need to be -updated. -Because the project doesn't share CPEs among the products. ---- - debian10/cpe/debian10-cpe-dictionary.xml | 5 +++++ - debian8/cpe/debian8-cpe-dictionary.xml | 5 +++++ - debian9/cpe/debian9-cpe-dictionary.xml | 5 +++++ - fedora/cpe/fedora-cpe-dictionary.xml | 5 +++++ - ol7/cpe/ol7-cpe-dictionary.xml | 5 +++++ - ol8/cpe/ol8-cpe-dictionary.xml | 5 +++++ - opensuse/cpe/opensuse-cpe-dictionary.xml | 5 +++++ - rhel7/cpe/rhel7-cpe-dictionary.xml | 5 +++++ - rhel8/cpe/rhel8-cpe-dictionary.xml | 5 +++++ - rhv4/cpe/rhv4-cpe-dictionary.xml | 5 +++++ - sle11/cpe/sle11-cpe-dictionary.xml | 5 +++++ - sle12/cpe/sle12-cpe-dictionary.xml | 5 +++++ - sle15/cpe/sle15-cpe-dictionary.xml | 5 +++++ - ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml | 5 +++++ - ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml | 5 +++++ - ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml | 5 +++++ - wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml | 5 +++++ - wrlinux8/cpe/wrlinux8-cpe-dictionary.xml | 5 +++++ - 18 files changed, 90 insertions(+) - -diff --git a/debian10/cpe/debian10-cpe-dictionary.xml b/debian10/cpe/debian10-cpe-dictionary.xml -index 5cc27ceb79..f2dbd09cfc 100644 ---- a/debian10/cpe/debian10-cpe-dictionary.xml -+++ b/debian10/cpe/debian10-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/debian8/cpe/debian8-cpe-dictionary.xml b/debian8/cpe/debian8-cpe-dictionary.xml -index 38d490138a..f385709052 100644 ---- a/debian8/cpe/debian8-cpe-dictionary.xml -+++ b/debian8/cpe/debian8-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/debian9/cpe/debian9-cpe-dictionary.xml b/debian9/cpe/debian9-cpe-dictionary.xml -index f01770b044..bc90a12bae 100644 ---- a/debian9/cpe/debian9-cpe-dictionary.xml -+++ b/debian9/cpe/debian9-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/fedora/cpe/fedora-cpe-dictionary.xml b/fedora/cpe/fedora-cpe-dictionary.xml -index 2964e320c2..ff7cebc322 100644 ---- a/fedora/cpe/fedora-cpe-dictionary.xml -+++ b/fedora/cpe/fedora-cpe-dictionary.xml -@@ -62,6 +62,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/ol7/cpe/ol7-cpe-dictionary.xml b/ol7/cpe/ol7-cpe-dictionary.xml -index c153272121..613f853a6d 100644 ---- a/ol7/cpe/ol7-cpe-dictionary.xml -+++ b/ol7/cpe/ol7-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/ol8/cpe/ol8-cpe-dictionary.xml b/ol8/cpe/ol8-cpe-dictionary.xml -index 3fd74e53ca..912fe01346 100644 ---- a/ol8/cpe/ol8-cpe-dictionary.xml -+++ b/ol8/cpe/ol8-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/opensuse/cpe/opensuse-cpe-dictionary.xml b/opensuse/cpe/opensuse-cpe-dictionary.xml -index 1ab4e85ea8..7f485b800e 100644 ---- a/opensuse/cpe/opensuse-cpe-dictionary.xml -+++ b/opensuse/cpe/opensuse-cpe-dictionary.xml -@@ -42,6 +42,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/rhel7/cpe/rhel7-cpe-dictionary.xml b/rhel7/cpe/rhel7-cpe-dictionary.xml -index a5214e36f0..f232b7ed29 100644 ---- a/rhel7/cpe/rhel7-cpe-dictionary.xml -+++ b/rhel7/cpe/rhel7-cpe-dictionary.xml -@@ -57,6 +57,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/rhel8/cpe/rhel8-cpe-dictionary.xml b/rhel8/cpe/rhel8-cpe-dictionary.xml -index cccb3c5791..eab827291f 100644 ---- a/rhel8/cpe/rhel8-cpe-dictionary.xml -+++ b/rhel8/cpe/rhel8-cpe-dictionary.xml -@@ -32,6 +32,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/rhv4/cpe/rhv4-cpe-dictionary.xml b/rhv4/cpe/rhv4-cpe-dictionary.xml -index ce9b06dcae..db1b4b239b 100644 ---- a/rhv4/cpe/rhv4-cpe-dictionary.xml -+++ b/rhv4/cpe/rhv4-cpe-dictionary.xml -@@ -32,6 +32,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/sle11/cpe/sle11-cpe-dictionary.xml b/sle11/cpe/sle11-cpe-dictionary.xml -index c732ecb48a..1b6b3e2518 100644 ---- a/sle11/cpe/sle11-cpe-dictionary.xml -+++ b/sle11/cpe/sle11-cpe-dictionary.xml -@@ -32,6 +32,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/sle12/cpe/sle12-cpe-dictionary.xml b/sle12/cpe/sle12-cpe-dictionary.xml -index 79daa31412..b1b66e1294 100644 ---- a/sle12/cpe/sle12-cpe-dictionary.xml -+++ b/sle12/cpe/sle12-cpe-dictionary.xml -@@ -32,6 +32,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/sle15/cpe/sle15-cpe-dictionary.xml b/sle15/cpe/sle15-cpe-dictionary.xml -index 91d3d78b19..0ee5a1b817 100644 ---- a/sle15/cpe/sle15-cpe-dictionary.xml -+++ b/sle15/cpe/sle15-cpe-dictionary.xml -@@ -32,6 +32,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml b/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml -index df5abff723..7f3ce4271b 100644 ---- a/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml -+++ b/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml b/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml -index 6269344376..83f0c8c516 100644 ---- a/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml -+++ b/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml b/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml -index ccb285768e..77b78d74ec 100644 ---- a/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml -+++ b/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml -@@ -27,6 +27,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml b/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml -index 73e419c9ab..cc4e806a4d 100644 ---- a/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml -+++ b/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml -@@ -26,6 +26,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - -diff --git a/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml b/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml -index 8449ea1416..824c575a6a 100644 ---- a/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml -+++ b/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml -@@ -26,6 +26,11 @@ - - installed_env_has_gdm_package - -+ -+ Package grub2 is installed -+ -+ installed_env_has_grub2_package -+ - - Package libuser is installed - diff --git a/SOURCES/scap-security-guide-0.1.51-add-zipl-rules_PR_5784.patch b/SOURCES/scap-security-guide-0.1.51-add-zipl-rules_PR_5784.patch deleted file mode 100644 index 084c528..0000000 --- a/SOURCES/scap-security-guide-0.1.51-add-zipl-rules_PR_5784.patch +++ /dev/null @@ -1,595 +0,0 @@ -From 2c354a6bfbcedee3f92fd8cbdd42ce0f0861fcaf Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Mon, 25 May 2020 14:33:06 +0200 -Subject: [PATCH 1/5] Add zIPL bootloader group - ---- - linux_os/guide/system/bootloader-zipl/group.yml | 11 +++++++++++ - 1 file changed, 11 insertions(+) - create mode 100644 linux_os/guide/system/bootloader-zipl/group.yml - -diff --git a/linux_os/guide/system/bootloader-zipl/group.yml b/linux_os/guide/system/bootloader-zipl/group.yml -new file mode 100644 -index 0000000000..36da84530c ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/group.yml -@@ -0,0 +1,11 @@ -+documentation_complete: true -+ -+title: 'zIPL bootloader configuration' -+ -+description: |- -+ During the boot process, the bootloader is -+ responsible for starting the execution of the kernel and passing -+ options to it. -+ The default {{{ full_name }}} boot loader for s390x systems is called zIPL. -+ -+platform: machine - -From 13c11b539e5c8cc929a5ccbc4b117a98bb35d915 Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Mon, 25 May 2020 15:26:19 +0200 -Subject: [PATCH 2/5] Add zIPL rule for early audit capability - ---- - .../zipl_audit_argument/rule.yml | 40 +++++++++++++++++++ - 1 file changed, 40 insertions(+) - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml - -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml -new file mode 100644 -index 0000000000..ce2bd60c59 ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml -@@ -0,0 +1,40 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Enable Auditing to Start Prior to the Audit Daemon in zIPL' -+ -+description: |- -+ To ensure all processes can be audited, even those which start prior to the audit daemon, -+ check that all boot entries in /boot/loader/entries/*.conf have audit=1 -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to enable audit, -+ add 
audit=1
to /etc/kernel/cmdline. -+ -+rationale: |- -+ Each process on the system carries an "auditable" flag which indicates whether -+ its activities can be audited. Although auditd takes care of enabling -+ this for all processes which launch after it does, adding the kernel argument -+ ensures it is set for every process during boot. -+ -+severity: medium -+ -+ocil_clause: 'auditing is not enabled at boot time' -+ -+ocil: |- -+ To check that audit is enabled at boot time, check all boot entries with following command: -+ 
sudo grep -L "^options\s+.*\baudit=1\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that doesn't enable audit. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. - -From 221979b3aebfe6dda39e1a446140454138e231bf Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 26 May 2020 15:06:12 +0200 -Subject: [PATCH 3/5] Add few more zIPL kernel option rules - -Add rules for following options: -- audit_backlog_limit -- selinux -- audit_backlog_limit -- enable_selinux -- page_poison -- pti -- slub_debug -- vsyscall ---- - .../rule.yml | 41 +++++++++++++++++++ - .../zipl_enable_selinux/rule.yml | 37 +++++++++++++++++ - .../zipl_page_poison_argument/rule.yml | 41 +++++++++++++++++++ - .../zipl_pti_argument/rule.yml | 40 ++++++++++++++++++ - .../zipl_slub_debug_argument/rule.yml | 41 +++++++++++++++++++ - .../zipl_vsyscall_argument/rule.yml | 41 +++++++++++++++++++ - 6 files changed, 241 insertions(+) - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml - create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml - -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml -new file mode 100644 -index 0000000000..08c5b53207 ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml -@@ -0,0 +1,41 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Extend Audit Backlog Limit for the Audit Daemon in zIPL' -+ -+description: |- -+ To improve the kernel capacity to queue all log events, even those which start prior to the audit daemon, -+ check that all boot entries in /boot/loader/entries/*.conf have audit_backlog_limit=8192 -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to extend the audit log events queue, -+ add 
audit_backlog_limit=8192
to /etc/kernel/cmdline. -+ -+rationale: |- -+ audit_backlog_limit sets the queue length for audit events awaiting transfer -+ to the audit daemon. Until the audit daemon is up and running, all log messages -+ are stored in this queue. If the queue is overrun during boot process, the action -+ defined by audit failure flag is taken. -+ -+severity: medium -+ -+ocil_clause: 'audit backlog limit is not configured' -+ -+ocil: |- -+ To check that all boot entries extend the backlog limit; -+ Check that all boot entries extend the log events queue: -+ 
sudo grep -L "^options\s+.*\baudit_backlog_limit=0\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that does not extend the log events queue. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml -new file mode 100644 -index 0000000000..e7a455b90c ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml -@@ -0,0 +1,37 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Ensure SELinux Not Disabled in zIPL' -+ -+description: |- -+ To ensure SELinux is not disabled at boot time, -+ check that no boot entry in /boot/loader/entries/*.conf has selinux=0 -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+rationale: |- -+ Disabling a major host protection feature, such as SELinux, at boot time prevents -+ it from confining system services at boot time. Further, it increases -+ the chances that it will remain off during system operation. -+ -+severity: medium -+ -+ocil_clause: 'SELinux is disabled at boot time' -+ -+ocil: |- -+ To check that selinux is not disabled at boot time; -+ Check that no boot entry disables selinux: -+ 
sudo grep -L "^options\s+.*\bselinux=0\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that disables SELinux. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml -new file mode 100644 -index 0000000000..b8a2eecee6 ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml -@@ -0,0 +1,41 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Enable page allocator poisoning in zIPL' -+ -+description: |- -+ To enable poisoning of free pages, -+ check that all boot entries in /boot/loader/entries/*.conf have page_poison=1 -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to enable page poisoning, -+ add 
page_poison=1
to /etc/kernel/cmdline. -+ -+rationale: |- -+ Poisoning writes an arbitrary value to freed pages, so any modification or -+ reference to that page after being freed or before being initialized will be -+ detected and prevented. -+ This prevents many types of use-after-free vulnerabilities at little performance cost. -+ Also prevents leak of data and detection of corrupted memory. -+ -+severity: medium -+ -+ocil_clause: 'page allocator poisoning is not enabled' -+ -+ocil: |- -+ To check that page poisoning is enabled at boot time, check all boot entries with following command: -+ 
sudo grep -L "^options\s+.*\bpage_poison=1\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that doesn't enable page poisoning. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml -new file mode 100644 -index 0000000000..4757871a5f ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml -@@ -0,0 +1,40 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Enable Kernel Page-Table Isolation (KPTI) in zIPL' -+ -+description: |- -+ To enable Kernel page-table isolation, -+ check that all boot entries in /boot/loader/entries/*.conf have pti=on -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to enable page-table isolation, -+ add 
pti=on
to /etc/kernel/cmdline. -+ -+rationale: |- -+ Kernel page-table isolation is a kernel feature that mitigates -+ the Meltdown security vulnerability and hardens the kernel -+ against attempts to bypass kernel address space layout -+ randomization (KASLR). -+ -+severity: medium -+ -+ocil_clause: 'Kernel page-table isolation is not enabled' -+ -+ocil: |- -+ To check that page-table isolation is enabled at boot time, check all boot entries with following command: -+ 
sudo grep -L "^options\s+.*\bpti=on\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that doesn't enable page-table isolation . -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml -new file mode 100644 -index 0000000000..166dd41afd ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml -@@ -0,0 +1,41 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Enable SLUB/SLAB allocator poisoning in zIPL' -+ -+description: |- -+ To enable poisoning of SLUB/SLAB objects, -+ check that all boot entries in /boot/loader/entries/*.conf have slub_debug=P -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to extend the audit log events queue, -+ add 
slub_debug=P
to /etc/kernel/cmdline. -+ -+rationale: |- -+ Poisoning writes an arbitrary value to freed objects, so any modification or -+ reference to that object after being freed or before being initialized will be -+ detected and prevented. -+ This prevents many types of use-after-free vulnerabilities at little performance cost. -+ Also prevents leak of data and detection of corrupted memory. -+ -+severity: medium -+ -+ocil_clause: 'SLUB/SLAB poisoning is not enabled' -+ -+ocil: |- -+ To check that SLUB/SLAB poisoning is enabled, check all boot entries with following command; -+ 
sudo grep -L "^options\s+.*\bslub_debug=P\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that does not enable poisoning. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. -diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml -new file mode 100644 -index 0000000000..6b95d16fb8 ---- /dev/null -+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml -@@ -0,0 +1,41 @@ -+documentation_complete: true -+ -+prodtype: rhel8 -+ -+title: 'Disable vsyscalls in zIPL' -+ -+description: |- -+ To disable use of virtual syscalls, -+ check that all boot entries in /boot/loader/entries/*.conf have vsyscall=none -+ included in its options. -+ Make sure /etc/zipl.conf doesn't contain 
image =
setting, -+ as {{{ full_name }}} adheres to Boot Loader Specification (BLS). -+ And run 
zipl
command so that /boot/bootmap is updated. -+ -+ To ensure that new kernels and boot entries continue to disable virtual syscalls, -+ add 
vsyscall=none
to /etc/kernel/cmdline. -+ -+rationale: |- -+ Poisoning writes an arbitrary value to freed pages, so any modification or -+ reference to that page after being freed or before being initialized will be -+ detected and prevented. -+ This prevents many types of use-after-free vulnerabilities at little performance cost. -+ Also prevents leak of data and detection of corrupted memory. -+ -+severity: medium -+ -+ocil_clause: 'vsyscalls are enabled' -+ -+ocil: |- -+ To check that virtual syscalls are disabled at boot time, check all boot entries with following command: -+ 
sudo grep -L "^options\s+.*\bvsyscall=none\b" /boot/loader/entries/*.conf
-+ No line should be returned, each line returned is a boot entry that doesn't disable virtual syscalls. -+ -+ Check that no image file is specified in /etc/zipl.conf: -+ 
grep -R "^image\s*=" /etc/zipl.conf
-+ No line should be returned, if a line is returned zipl may load a different kernel than intended. -+ -+ And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf -+ and /etc/zipl.conf: -+ 
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap
-+ No line should be returned, if a line is returned /boot/bootmap needs to be regenerated. - -From a45ba0eaa12de63abb43449c6caee4776100005c Mon Sep 17 00:00:00 2001 -From: Watson Sato -Date: Tue, 2 Jun 2020 13:29:39 +0200 -Subject: [PATCH 4/5] Fix formatting of zIPL rules - -
 is renderend in a separate line, while  is rendered inline.
-Add line breaks for better readability.
----
- .../bootloader-zipl/zipl_audit_argument/rule.yml       | 10 +++++-----
- .../zipl_audit_backlog_limit_argument/rule.yml         | 10 +++++-----
- .../bootloader-zipl/zipl_enable_selinux/rule.yml       |  8 ++++----
- .../bootloader-zipl/zipl_page_poison_argument/rule.yml | 10 +++++-----
- .../system/bootloader-zipl/zipl_pti_argument/rule.yml  | 10 +++++-----
- .../bootloader-zipl/zipl_slub_debug_argument/rule.yml  | 10 +++++-----
- .../bootloader-zipl/zipl_vsyscall_argument/rule.yml    | 10 +++++-----
- 7 files changed, 34 insertions(+), 34 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-index ce2bd60c59..16c0b3f89a 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Enable Auditing to Start Prior to the Audit Daemon in zIPL'
- description: |-
-     To ensure all processes can be audited, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit=1
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to enable audit,
--    add 
audit=1
 to /etc/kernel/cmdline.
-+    add audit=1 to /etc/kernel/cmdline.
- 
- rationale: |-
-     Each process on the system carries an "auditable" flag which indicates whether
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index 08c5b53207..47a532d50f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Extend Audit Backlog Limit for the Audit Daemon in zIPL'
- description: |-
-     To improve the kernel capacity to queue all log events, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit_backlog_limit=8192
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
--    add 
audit_backlog_limit=8192
 to /etc/kernel/cmdline.
-+    add audit_backlog_limit=8192 to /etc/kernel/cmdline.
- 
- rationale: |-
-     audit_backlog_limit sets the queue length for audit events awaiting transfer
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-index e7a455b90c..5aa91c16aa 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-@@ -7,10 +7,10 @@ title: 'Ensure SELinux Not Disabled in zIPL'
- description: |-
-     To ensure SELinux is not disabled at boot time,
-     check that no boot entry in /boot/loader/entries/*.conf has selinux=0
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
- rationale: |-
-     Disabling a major host protection feature, such as SELinux, at boot time prevents
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-index b8a2eecee6..8546325752 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Enable page allocator poisoning in zIPL'
- description: |-
-     To enable poisoning of free pages,
-     check that all boot entries in /boot/loader/entries/*.conf have page_poison=1
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.

- 
-     To ensure that new kernels and boot entries continue to enable page poisoning,
--    add 
page_poison=1
 to /etc/kernel/cmdline.
-+    add page_poison=1 to /etc/kernel/cmdline.
- 
- rationale: |-
-     Poisoning writes an arbitrary value to freed pages, so any modification or
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-index 4757871a5f..eaef25ce40 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Enable Kernel Page-Table Isolation (KPTI) in zIPL'
- description: |-
-     To enable Kernel page-table isolation,
-     check that all boot entries in /boot/loader/entries/*.conf have pti=on
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to enable page-table isolation,
--    add 
pti=on
 to /etc/kernel/cmdline.
-+    add pti=on to /etc/kernel/cmdline.
- 
- rationale: |-
-     Kernel page-table isolation is a kernel feature that mitigates
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index 166dd41afd..68e91a92d6 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Enable SLUB/SLAB allocator poisoning in zIPL'
- description: |-
-     To enable poisoning of SLUB/SLAB objects,
-     check that all boot entries in /boot/loader/entries/*.conf have slub_debug=P
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
--    add 
slub_debug=P
 to /etc/kernel/cmdline.
-+    add slub_debug=P to /etc/kernel/cmdline.
- 
- rationale: |-
-     Poisoning writes an arbitrary value to freed objects, so any modification or
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index 6b95d16fb8..8d39337f9e 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -7,13 +7,13 @@ title: 'Disable vsyscalls in zIPL'
- description: |-
-     To disable use of virtual syscalls,
-     check that all boot entries in /boot/loader/entries/*.conf have vsyscall=none
--    included in its options.
--    Make sure /etc/zipl.conf doesn't contain 
image = 
 setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).
--    And run 
zipl
 command so that /boot/bootmap is updated.
-+    included in its options.

-+    Make sure /etc/zipl.conf doesn't contain image =  setting,
-+    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-+    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to disable virtual syscalls,
--    add 
vsyscall=none
 to /etc/kernel/cmdline.
-+    add vsyscall=none to /etc/kernel/cmdline.
- 
- rationale: |-
-     Poisoning writes an arbitrary value to freed pages, so any modification or
-
-From ae8f9252c3c5c1d1ac1bed201e0981c0d50168aa Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 3 Jun 2020 13:08:07 +0200
-Subject: [PATCH 5/5] zipl_vsyscall_argument: Fix rationale
-
-copy-pasta error
----
- .../system/bootloader-zipl/zipl_vsyscall_argument/rule.yml | 7 ++-----
- 1 file changed, 2 insertions(+), 5 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index 8d39337f9e..9624b43349 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -16,11 +16,8 @@ description: |-
-     add vsyscall=none to /etc/kernel/cmdline.
- 
- rationale: |-
--    Poisoning writes an arbitrary value to freed pages, so any modification or
--    reference to that page after being freed or before being initialized will be
--    detected and prevented.
--    This prevents many types of use-after-free vulnerabilities at little performance cost.
--    Also prevents leak of data and detection of corrupted memory.
-+    Virtual Syscalls provide an opportunity of attack for a user who has control
-+    of the return instruction pointer.
- 
- severity: medium
- 
diff --git a/SOURCES/scap-security-guide-0.1.51-add_ansible_ensure_logrotate_activated_PR_5753.patch b/SOURCES/scap-security-guide-0.1.51-add_ansible_ensure_logrotate_activated_PR_5753.patch
deleted file mode 100644
index e859c54..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_ansible_ensure_logrotate_activated_PR_5753.patch
+++ /dev/null
@@ -1,71 +0,0 @@
-From 8605fc4fd40f5d2067d9b81f41d5f523d9a5ba98 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 12 May 2020 08:17:20 +0200
-Subject: [PATCH 1/2] Add Ansible for ensure_logrotate_activated
-
----
- .../ansible/shared.yml                        | 33 +++++++++++++++++++
- 1 file changed, 33 insertions(+)
- create mode 100644 linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/ansible/shared.yml
-
-diff --git a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/ansible/shared.yml b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/ansible/shared.yml
-new file mode 100644
-index 0000000000..5d76b3c073
---- /dev/null
-+++ b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/ansible/shared.yml
-@@ -0,0 +1,33 @@
-+# platform = multi_platform_all
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+
-+- name: Configure daily log rotation in /etc/logrotate.conf
-+  lineinfile:
-+    create: yes
-+    dest: "/etc/logrotate.conf"
-+    regexp: "^daily$"
-+    line: "daily"
-+
-+- name: Make sure daily log rotation setting is not overriden in /etc/logrotate.conf
-+  lineinfile:
-+    create: no
-+    dest: "/etc/logrotate.conf"
-+    regexp: "^(weekly|monthly|yearly)$"
-+    state: absent
-+
-+- name: Configure cron.daily if not already
-+  block:
-+    - name: Add shebang
-+      lineinfile:
-+        path: "/etc/cron.daily/logrotate"
-+        line: "#!/bin/sh"
-+        insertbefore: BOF
-+        create: yes
-+    - name: Add logrotate call
-+      lineinfile:
-+        path: "/etc/cron.daily/logrotate"
-+        line: '/usr/sbin/logrotate /etc/logrotate.conf'
-+        regexp: '^[\s]*/usr/sbin/logrotate[\s\S]*/etc/logrotate.conf$'
-
-From 085e5b2d18c9f50a6486a50f964ff71b74d5dade Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 12 May 2020 14:48:15 +0200
-Subject: [PATCH 2/2] Add test for ensure_logrotate_activated
-
-Test scenario when monthly is there, but weekly is not.
----
- .../tests/logrotate_conf_extra_monthly.fail.sh                | 4 ++++
- 1 file changed, 4 insertions(+)
- create mode 100644 linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/tests/logrotate_conf_extra_monthly.fail.sh
-
-diff --git a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/tests/logrotate_conf_extra_monthly.fail.sh b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/tests/logrotate_conf_extra_monthly.fail.sh
-new file mode 100644
-index 0000000000..b10362989b
---- /dev/null
-+++ b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/tests/logrotate_conf_extra_monthly.fail.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+sed -i "s/weekly/daily/g" /etc/logrotate.conf
-+echo "monthly" >> /etc/logrotate.conf
diff --git a/SOURCES/scap-security-guide-0.1.51-add_ansible_sshd_set_max_sessions_PR_5757.patch b/SOURCES/scap-security-guide-0.1.51-add_ansible_sshd_set_max_sessions_PR_5757.patch
deleted file mode 100644
index a864ebf..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_ansible_sshd_set_max_sessions_PR_5757.patch
+++ /dev/null
@@ -1,115 +0,0 @@
-From be529f2ca1f3644db9ad436dbd35aa00a9a5cf14 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 13 May 2020 20:49:08 +0200
-Subject: [PATCH 1/2] Add simple tests for sshd_set_max_sessions
-
----
- .../sshd_set_max_sessions/tests/correct_value.pass.sh | 11 +++++++++++
- .../sshd_set_max_sessions/tests/wrong_value.fail.sh   | 11 +++++++++++
- 2 files changed, 22 insertions(+)
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
-new file mode 100644
-index 0000000000..a816eea390
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
-@@ -0,0 +1,11 @@
-+# profiles = xccdf_org.ssgproject.content_profile_cis
-+# platform = Red Hat Enterprise Linux 8
-+
-+#!/bin/bash
-+SSHD_CONFIG="/etc/ssh/sshd_config"
-+
-+if grep -q "^MaxSessions" $SSHD_CONFIG; then
-+        sed -i "s/^MaxSessions.*/MaxSessions 4/" $SSHD_CONFIG
-+    else
-+            echo "MaxSessions 4" >> $SSHD_CONFIG
-+fi
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-new file mode 100644
-index 0000000000..b36125f5bb
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-@@ -0,0 +1,11 @@
-+# profiles = xccdf_org.ssgproject.content_profile_cis
-+# platform = Red Hat Enterprise Linux 8
-+
-+#!/bin/bash
-+SSHD_CONFIG="/etc/ssh/sshd_config"
-+
-+if grep -q "^MaxSessions" $SSHD_CONFIG; then
-+        sed -i "s/^MaxSessions.*/MaxSessions 10/" $SSHD_CONFIG
-+    else
-+            echo "MaxSessions 10" >> $SSHD_CONFIG
-+fi
-
-From 027299726c805b451b02694c737514750fd14b94 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 13 May 2020 20:53:50 +0200
-Subject: [PATCH 2/2] Add remediations for sshd_set_max_sessions
-
----
- .../sshd_set_max_sessions/ansible/shared.yml         |  8 ++++++++
- .../ssh_server/sshd_set_max_sessions/bash/shared.sh  | 12 ++++++++++++
- .../tests/correct_value.pass.sh                      |  2 +-
- .../sshd_set_max_sessions/tests/wrong_value.fail.sh  |  2 +-
- 4 files changed, 22 insertions(+), 2 deletions(-)
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/ansible/shared.yml
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/bash/shared.sh
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/ansible/shared.yml b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/ansible/shared.yml
-new file mode 100644
-index 0000000000..a7e171dfe9
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/ansible/shared.yml
-@@ -0,0 +1,8 @@
-+# platform = multi_platform_all
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+- (xccdf-var var_sshd_max_sessions)
-+
-+{{{ ansible_sshd_set(parameter="MaxSessions", value="{{ var_sshd_max_sessions}}") }}}
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/bash/shared.sh b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/bash/shared.sh
-new file mode 100644
-index 0000000000..fc0a1d8b42
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/bash/shared.sh
-@@ -0,0 +1,12 @@
-+# platform = multi_platform_all
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+
-+# Include source function library.
-+. /usr/share/scap-security-guide/remediation_functions
-+
-+populate var_sshd_max_sessions
-+
-+{{{ bash_sshd_config_set(parameter="MaxSessions", value="$var_sshd_max_sessions") }}}
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
-index a816eea390..4cc6d65988 100644
---- a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/correct_value.pass.sh
-@@ -7,5 +7,5 @@ SSHD_CONFIG="/etc/ssh/sshd_config"
- if grep -q "^MaxSessions" $SSHD_CONFIG; then
-         sed -i "s/^MaxSessions.*/MaxSessions 4/" $SSHD_CONFIG
-     else
--            echo "MaxSessions 4" >> $SSHD_CONFIG
-+        echo "MaxSessions 4" >> $SSHD_CONFIG
- fi
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-index b36125f5bb..bc0c47842a 100644
---- a/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_set_max_sessions/tests/wrong_value.fail.sh
-@@ -7,5 +7,5 @@ SSHD_CONFIG="/etc/ssh/sshd_config"
- if grep -q "^MaxSessions" $SSHD_CONFIG; then
-         sed -i "s/^MaxSessions.*/MaxSessions 10/" $SSHD_CONFIG
-     else
--            echo "MaxSessions 10" >> $SSHD_CONFIG
-+        echo "MaxSessions 10" >> $SSHD_CONFIG
- fi
diff --git a/SOURCES/scap-security-guide-0.1.51-add_ansible_system_shutdown_PR_5761.patch b/SOURCES/scap-security-guide-0.1.51-add_ansible_system_shutdown_PR_5761.patch
deleted file mode 100644
index ff529ca..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_ansible_system_shutdown_PR_5761.patch
+++ /dev/null
@@ -1,147 +0,0 @@
-From 2f6ceca58e64ab6c362afef629ac6ac235b0abe9 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 11:52:35 +0200
-Subject: [PATCH 1/4] audit_rules_system_shutdown: Don't remove unrelated line
-
-Very likey a copy-pasta error from bash remediation for
-audit_rules_immutable
----
- .../audit_rules_system_shutdown/bash/shared.sh                  | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-index 1c9748ce9b..b56513cdcd 100644
---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-@@ -8,7 +8,7 @@
- # files to check if '-f .*' setting is present in that '*.rules' file already.
- # If found, delete such occurrence since auditctl(8) manual page instructs the
- # '-f 2' rule should be placed as the last rule in the configuration
--find /etc/audit /etc/audit/rules.d -maxdepth 1 -type f -name '*.rules' -exec sed -i '/-e[[:space:]]\+.*/d' {} ';'
-+find /etc/audit /etc/audit/rules.d -maxdepth 1 -type f -name '*.rules' -exec sed -i '/-f[[:space:]]\+.*/d' {} ';'
- 
- # Append '-f 2' requirement at the end of both:
- # * /etc/audit/audit.rules file 		(for auditctl case)
-
-From 189aed2c79620940438fc025a3cb9919cd8ee80a Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 12:12:21 +0200
-Subject: [PATCH 2/4] Add Ansible for audit_rules_system_shutdown
-
-Along with very basic test scenarios
----
- .../ansible/shared.yml                        | 28 +++++++++++++++++++
- .../tests/augen_correct.pass.sh               |  4 +++
- .../tests/augen_e_2_immutable.fail.sh         |  3 ++
- 3 files changed, 35 insertions(+)
- create mode 100644 linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/ansible/shared.yml
- create mode 100644 linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_correct.pass.sh
- create mode 100644 linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_e_2_immutable.fail.sh
-
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/ansible/shared.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/ansible/shared.yml
-new file mode 100644
-index 0000000000..b9e8fa87fa
---- /dev/null
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/ansible/shared.yml
-@@ -0,0 +1,28 @@
-+# platform = multi_platform_all
-+# reboot = true
-+# strategy = restrict
-+# complexity = low
-+# disruption = low
-+
-+- name: Collect all files from /etc/audit/rules.d with .rules extension
-+  find:
-+    paths: "/etc/audit/rules.d/"
-+    patterns: "*.rules"
-+  register: find_rules_d
-+
-+- name: Remove the -f option from all Audit config files
-+  lineinfile:
-+    path: "{{ item }}"
-+    regexp: '^\s*(?:-f)\s+.*$'
-+    state: absent
-+  loop: "{{ find_rules_d.files | map(attribute='path') | list + ['/etc/audit/audit.rules'] }}"
-+
-+- name: Add Audit -f option into /etc/audit/rules.d/immutable.rules and /etc/audit/audit.rules
-+  lineinfile:
-+    path: "{{ item }}"
-+    create: True
-+    line: "-f 2"
-+  loop:
-+    - "/etc/audit/audit.rules"
-+    - "/etc/audit/rules.d/immutable.rules"
-+
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_correct.pass.sh b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_correct.pass.sh
-new file mode 100644
-index 0000000000..0587b937e0
---- /dev/null
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_correct.pass.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+echo "-e 2" > /etc/audit/rules.d/immutable.rules
-+echo "-f 2" >> /etc/audit/rules.d/immutable.rules
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_e_2_immutable.fail.sh b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_e_2_immutable.fail.sh
-new file mode 100644
-index 0000000000..fa5b7231df
---- /dev/null
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/tests/augen_e_2_immutable.fail.sh
-@@ -0,0 +1,3 @@
-+#!/bin/bash
-+
-+echo "-e 2" > /etc/audit/rules.d/immutable.rules
-
-From d693af1e00521d85b5745001aa13860bdac16632 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 14:06:08 +0200
-Subject: [PATCH 3/4] Clarify audit_rules_immutable Ansible task name
-
----
- .../audit_rules_immutable/ansible/shared.yml                    | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/ansible/shared.yml b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/ansible/shared.yml
-index 5ac7b3dabb..1cafb744cc 100644
---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/ansible/shared.yml
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_immutable/ansible/shared.yml
-@@ -17,7 +17,7 @@
-     state: absent
-   loop: "{{ find_rules_d.files | map(attribute='path') | list + ['/etc/audit/audit.rules'] }}"
- 
--- name: Insert configuration into /etc/audit/rules.d/immutable.rules and /etc/audit/audit.rules
-+- name: Add Audit -e option into /etc/audit/rules.d/immutable.rules and /etc/audit/audit.rules
-   lineinfile:
-     path: "{{ item }}"
-     create: True
-
-From 92d38c1968059e53e3ab20f46f5ce0885a989aee Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 11:02:56 +0200
-Subject: [PATCH 4/4] Remove misleading comments in system shutdown fix
-
----
- .../audit_rules_system_shutdown/bash/shared.sh            | 8 --------
- 1 file changed, 8 deletions(-)
-
-diff --git a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-index b56513cdcd..a349bb1ca1 100644
---- a/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-+++ b/linux_os/guide/system/auditing/auditd_configure_rules/audit_rules_system_shutdown/bash/shared.sh
-@@ -4,16 +4,8 @@
- #
- # /etc/audit/audit.rules,			(for auditctl case)
- # /etc/audit/rules.d/*.rules			(for augenrules case)
--#
--# files to check if '-f .*' setting is present in that '*.rules' file already.
--# If found, delete such occurrence since auditctl(8) manual page instructs the
--# '-f 2' rule should be placed as the last rule in the configuration
- find /etc/audit /etc/audit/rules.d -maxdepth 1 -type f -name '*.rules' -exec sed -i '/-f[[:space:]]\+.*/d' {} ';'
- 
--# Append '-f 2' requirement at the end of both:
--# * /etc/audit/audit.rules file 		(for auditctl case)
--# * /etc/audit/rules.d/immutable.rules		(for augenrules case)
--
- for AUDIT_FILE in "/etc/audit/audit.rules" "/etc/audit/rules.d/immutable.rules"
- do
- 	echo '' >> $AUDIT_FILE
diff --git a/SOURCES/scap-security-guide-0.1.51-add_cis_attributions_PR_5779.patch b/SOURCES/scap-security-guide-0.1.51-add_cis_attributions_PR_5779.patch
deleted file mode 100644
index 2b5acdc..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_cis_attributions_PR_5779.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-From 0cf31f2a9741533b98cc143ca35f589a712bd6a6 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 21 May 2020 18:16:43 +0200
-Subject: [PATCH] Attribute content to CIS
-
-And update the description a bit.
----
- rhel7/profiles/cis.profile | 8 +++++---
- rhel8/profiles/cis.profile | 8 +++++---
- 2 files changed, 10 insertions(+), 6 deletions(-)
-
-diff --git a/rhel7/profiles/cis.profile b/rhel7/profiles/cis.profile
-index 0826a49547..829c388133 100644
---- a/rhel7/profiles/cis.profile
-+++ b/rhel7/profiles/cis.profile
-@@ -3,9 +3,11 @@ documentation_complete: true
- title: 'CIS Red Hat Enterprise Linux 7 Benchmark'
- 
- description: |-
--    This baseline aligns to the Center for Internet Security
--    Red Hat Enterprise Linux 7 Benchmark, v2.2.0, released
--    12-27-2017.
-+    This profile defines a baseline that aligns to the Center for Internet Security®
-+    Red Hat Enterprise Linux 7 Benchmark™, v2.2.0, released 12-27-2017.
-+
-+    This profile includes Center for Internet Security®
-+    Red Hat Enterprise Linux 7 CIS Benchmarks™ content.
- 
- selections:
-     # Necessary for dconf rules
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index f332ee5462..868b9f21a6 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -3,9 +3,11 @@ documentation_complete: true
- title: 'CIS Red Hat Enterprise Linux 8 Benchmark'
- 
- description: |-
--    This baseline aligns to the Center for Internet Security
--    Red Hat Enterprise Linux 8 Benchmark, v1.0.0, released
--    09-30-2019.
-+    This profile defines a baseline that aligns to the Center for Internet Security®
-+    Red Hat Enterprise Linux 8 Benchmark™, v1.0.0, released 09-30-2019.
-+
-+    This profile includes Center for Internet Security®
-+    Red Hat Enterprise Linux 8 CIS Benchmarks™ content.
- 
- selections:
-     # Necessary for dconf rules
diff --git a/SOURCES/scap-security-guide-0.1.51-add_hipaa_kickstarts_PR_5783.patch b/SOURCES/scap-security-guide-0.1.51-add_hipaa_kickstarts_PR_5783.patch
deleted file mode 100644
index 3c4f3b1..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_hipaa_kickstarts_PR_5783.patch
+++ /dev/null
@@ -1,274 +0,0 @@
-From b23fc7fe3244128940f7b1f79ad4cde13d7b62eb Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 25 May 2020 12:17:48 +0200
-Subject: [PATCH] add hipaa kickstarts for rhel7 and rhel8
-
----
- rhel7/kickstart/ssg-rhel7-hipaa-ks.cfg | 125 +++++++++++++++++++++++++
- rhel8/kickstart/ssg-rhel8-hipaa-ks.cfg | 125 +++++++++++++++++++++++++
- 2 files changed, 250 insertions(+)
- create mode 100644 rhel7/kickstart/ssg-rhel7-hipaa-ks.cfg
- create mode 100644 rhel8/kickstart/ssg-rhel8-hipaa-ks.cfg
-
-diff --git a/rhel7/kickstart/ssg-rhel7-hipaa-ks.cfg b/rhel7/kickstart/ssg-rhel7-hipaa-ks.cfg
-new file mode 100644
-index 0000000000..14c82c4231
---- /dev/null
-+++ b/rhel7/kickstart/ssg-rhel7-hipaa-ks.cfg
-@@ -0,0 +1,125 @@
-+# SCAP Security Guide HIPAA profile kickstart for Red Hat Enterprise Linux 7 Server
-+# Version: 0.0.1
-+# Date: 2020-05-25
-+#
-+# Based on:
-+# http://fedoraproject.org/wiki/Anaconda/Kickstart
-+# https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html
-+
-+# Install a fresh new system (optional)
-+install
-+
-+# Specify installation method to use for installation
-+# To use a different one comment out the 'url' one below, update
-+# the selected choice with proper options & un-comment it
-+#
-+# Install from an installation tree on a remote server via FTP or HTTP:
-+# --url		the URL to install from
-+#
-+# Example:
-+#
-+# url --url=http://192.168.122.1/image
-+#
-+# Modify concrete URL in the above example appropriately to reflect the actual
-+# environment machine is to be installed in
-+#
-+# Other possible / supported installation methods:
-+# * install from the first CD-ROM/DVD drive on the system:
-+#
-+# cdrom
-+#
-+# * install from a directory of ISO images on a local drive:
-+#
-+# harddrive --partition=hdb2 --dir=/tmp/install-tree
-+#
-+# * install from provided NFS server:
-+#
-+# nfs --server= --dir= [--opts=]
-+#
-+
-+# Set language to use during installation and the default language to use on the installed system (required)
-+lang en_US.UTF-8
-+
-+# Set system keyboard type / layout (required)
-+keyboard us
-+
-+# Configure network information for target system and activate network devices in the installer environment (optional)
-+# --onboot	enable device at a boot time
-+# --device	device to be activated and / or configured with the network command
-+# --bootproto	method to obtain networking configuration for device (default dhcp)
-+# --noipv6	disable IPv6 on this device
-+#
-+# NOTE: Usage of DHCP will fail CCE-27021-5 (DISA FSO RHEL-06-000292). To use static IP configuration,
-+#       "--bootproto=static" must be used. For example:
-+# network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
-+#
-+network --onboot yes --device eth0 --bootproto dhcp --noipv6
-+
-+# Set the system's root password (required)
-+# Plaintext password is: server
-+# Refer to e.g. http://fedoraproject.org/wiki/Anaconda/Kickstart#rootpw to see how to create
-+# encrypted password form for different plaintext password
-+rootpw --iscrypted $6$rhel6usgcb$aS6oPGXcPKp3OtFArSrhRwu6sN8q2.yEGY7AIwDOQd23YCtiz9c5mXbid1BzX9bmXTEZi.hCzTEXFosVBI5ng0
-+
-+# The selected profile will restrict root login
-+# Add a user that can login and escalate privileges
-+# Plaintext password is: admin123
-+user --name=admin --groups=wheel --password=$6$Ga6ZnIlytrWpuCzO$q0LqT1USHpahzUafQM9jyHCY9BiE5/ahXLNWUMiVQnFGblu0WWGZ1e6icTaCGO4GNgZNtspp1Let/qpM7FMVB0 --iscrypted
-+
-+# Configure firewall settings for the system (optional)
-+# --enabled	reject incoming connections that are not in response to outbound requests
-+# --ssh		allow sshd service through the firewall
-+firewall --enabled --ssh
-+
-+# Set up the authentication options for the system (required)
-+# --enableshadow	enable shadowed passwords by default
-+# --passalgo		hash / crypt algorithm for new passwords
-+# See the manual page for authconfig for a complete list of possible options.
-+authconfig --enableshadow --passalgo=sha512
-+
-+# State of SELinux on the installed system (optional)
-+# Defaults to enforcing
-+selinux --enforcing
-+
-+# Set the system time zone (required)
-+timezone --utc America/New_York
-+
-+# Specify how the bootloader should be installed (required)
-+# Plaintext password is: password
-+# Refer to e.g. http://fedoraproject.org/wiki/Anaconda/Kickstart#rootpw to see how to create
-+# encrypted password form for different plaintext password
-+bootloader --location=mbr --append="crashkernel=auto rhgb quiet" --password=$6$rhel6usgcb$kOzIfC4zLbuo3ECp1er99NRYikN419wxYMmons8Vm/37Qtg0T8aB9dKxHwqapz8wWAFuVkuI/UJqQBU92bA5C0
-+
-+# Initialize (format) all disks (optional)
-+zerombr
-+
-+# The following partition layout scheme assumes disk of size 20GB or larger
-+# Modify size of partitions appropriately to reflect actual machine's hardware
-+#
-+# Remove Linux partitions from the system prior to creating new ones (optional)
-+# --linux	erase all Linux partitions
-+# --initlabel	initialize the disk label to the default based on the underlying architecture
-+clearpart --linux --initlabel
-+
-+# Create primary system partitions (required for installs)
-+autopart
-+
-+# Harden installation with HIPAA profile
-+# For more details and configuration options see command %addon org_fedora_oscap in
-+# https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-syntax#sect-kickstart-commands
-+%addon org_fedora_oscap
-+        content-type = scap-security-guide
-+        profile = xccdf_org.ssgproject.content_profile_hipaa
-+%end
-+
-+# Packages selection (%packages section is required)
-+%packages
-+
-+# Require @Base
-+@Base
-+
-+%end # End of %packages section
-+
-+# Reboot after the installation is complete (optional)
-+# --eject	attempt to eject CD or DVD media before rebooting
-+reboot --eject
-diff --git a/rhel8/kickstart/ssg-rhel8-hipaa-ks.cfg b/rhel8/kickstart/ssg-rhel8-hipaa-ks.cfg
-new file mode 100644
-index 0000000000..861db36f18
---- /dev/null
-+++ b/rhel8/kickstart/ssg-rhel8-hipaa-ks.cfg
-@@ -0,0 +1,125 @@
-+# SCAP Security Guide HIPAA profile kickstart for Red Hat Enterprise Linux 8 Server
-+# Version: 0.0.1
-+# Date: 2020-05-25
-+#
-+# Based on:
-+# http://fedoraproject.org/wiki/Anaconda/Kickstart
-+# https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index#performing_an_automated_installation_using_kickstart
-+
-+# Install a fresh new system (optional)
-+install
-+
-+# Specify installation method to use for installation
-+# To use a different one comment out the 'url' one below, update
-+# the selected choice with proper options & un-comment it
-+#
-+# Install from an installation tree on a remote server via FTP or HTTP:
-+# --url		the URL to install from
-+#
-+# Example:
-+#
-+# url --url=http://192.168.122.1/image
-+#
-+# Modify concrete URL in the above example appropriately to reflect the actual
-+# environment machine is to be installed in
-+#
-+# Other possible / supported installation methods:
-+# * install from the first CD-ROM/DVD drive on the system:
-+#
-+# cdrom
-+#
-+# * install from a directory of ISO images on a local drive:
-+#
-+# harddrive --partition=hdb2 --dir=/tmp/install-tree
-+#
-+# * install from provided NFS server:
-+#
-+# nfs --server= --dir= [--opts=]
-+#
-+
-+# Set language to use during installation and the default language to use on the installed system (required)
-+lang en_US.UTF-8
-+
-+# Set system keyboard type / layout (required)
-+keyboard us
-+
-+# Configure network information for target system and activate network devices in the installer environment (optional)
-+# --onboot	enable device at a boot time
-+# --device	device to be activated and / or configured with the network command
-+# --bootproto	method to obtain networking configuration for device (default dhcp)
-+# --noipv6	disable IPv6 on this device
-+#
-+# NOTE: Usage of DHCP will fail CCE-27021-5 (DISA FSO RHEL-06-000292). To use static IP configuration,
-+#       "--bootproto=static" must be used. For example:
-+# network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
-+#
-+network --onboot yes --device eth0 --bootproto dhcp --noipv6
-+
-+# Set the system's root password (required)
-+# Plaintext password is: server
-+# Refer to e.g. http://fedoraproject.org/wiki/Anaconda/Kickstart#rootpw to see how to create
-+# encrypted password form for different plaintext password
-+rootpw --iscrypted $6$rhel6usgcb$aS6oPGXcPKp3OtFArSrhRwu6sN8q2.yEGY7AIwDOQd23YCtiz9c5mXbid1BzX9bmXTEZi.hCzTEXFosVBI5ng0
-+
-+# The selected profile will restrict root login
-+# Add a user that can login and escalate privileges
-+# Plaintext password is: admin123
-+user --name=admin --groups=wheel --password=$6$Ga6ZnIlytrWpuCzO$q0LqT1USHpahzUafQM9jyHCY9BiE5/ahXLNWUMiVQnFGblu0WWGZ1e6icTaCGO4GNgZNtspp1Let/qpM7FMVB0 --iscrypted
-+
-+# Configure firewall settings for the system (optional)
-+# --enabled	reject incoming connections that are not in response to outbound requests
-+# --ssh		allow sshd service through the firewall
-+firewall --enabled --ssh
-+
-+# Set up the authentication options for the system (required)
-+# sssd profile sets sha512 to hash passwords
-+# passwords are shadowed by default
-+# See the manual page for authselect-profile for a complete list of possible options.
-+authselect select sssd
-+
-+# State of SELinux on the installed system (optional)
-+# Defaults to enforcing
-+selinux --enforcing
-+
-+# Set the system time zone (required)
-+timezone --utc America/New_York
-+
-+# Specify how the bootloader should be installed (required)
-+# Plaintext password is: password
-+# Refer to e.g. http://fedoraproject.org/wiki/Anaconda/Kickstart#rootpw to see how to create
-+# encrypted password form for different plaintext password
-+bootloader --location=mbr --append="crashkernel=auto rhgb quiet" --password=$6$rhel6usgcb$kOzIfC4zLbuo3ECp1er99NRYikN419wxYMmons8Vm/37Qtg0T8aB9dKxHwqapz8wWAFuVkuI/UJqQBU92bA5C0
-+
-+# Initialize (format) all disks (optional)
-+zerombr
-+
-+# The following partition layout scheme assumes disk of size 20GB or larger
-+# Modify size of partitions appropriately to reflect actual machine's hardware
-+# 
-+# Remove Linux partitions from the system prior to creating new ones (optional)
-+# --linux	erase all Linux partitions
-+# --initlabel	initialize the disk label to the default based on the underlying architecture
-+clearpart --linux --initlabel
-+
-+# Create primary system partitions (required for installs)
-+autopart
-+
-+# Harden installation with HIPAA profile
-+# For more details and configuration options see
-+# https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index#addon-org_fedora_oscap_kickstart-commands-for-addons-supplied-with-the-rhel-installation-program
-+%addon org_fedora_oscap
-+        content-type = scap-security-guide
-+        profile = xccdf_org.ssgproject.content_profile_hipaa
-+%end
-+
-+# Packages selection (%packages section is required)
-+%packages
-+
-+# Require @Base
-+@Base
-+
-+%end # End of %packages section
-+
-+# Reboot after the installation is complete (optional)
-+# --eject	attempt to eject CD or DVD media before rebooting
-+reboot --eject
diff --git a/SOURCES/scap-security-guide-0.1.51-add_missing_cis_cces_PR_5781.patch b/SOURCES/scap-security-guide-0.1.51-add_missing_cis_cces_PR_5781.patch
deleted file mode 100644
index e6dc9cb..0000000
--- a/SOURCES/scap-security-guide-0.1.51-add_missing_cis_cces_PR_5781.patch
+++ /dev/null
@@ -1,76 +0,0 @@
-From 1ee826c4b506fc4a349015e53a1c687c64423351 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 22 May 2020 14:12:18 +0200
-Subject: [PATCH] Add missing CCEs for RHEL8
-
----
- .../password_storage/no_netrc_files/rule.yml                   | 1 +
- .../accounts_user_interactive_home_directory_exists/rule.yml   | 1 +
- .../file_groupownership_home_directories/rule.yml              | 1 +
- shared/references/cce-redhat-avail.txt                         | 3 ---
- 4 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-index 8547893201..1bd1f5742e 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-@@ -18,6 +18,7 @@ severity: medium
- identifiers:
-     cce@rhel6: 27225-2
-     cce@rhel7: 80211-6
-+    cce@rhel8: 83444-0
-     cce@ocp4: 82667-7
- 
- references:
-diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-index bedf3a0b19..e69bc9d736 100644
---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-@@ -21,6 +21,7 @@ severity: medium
- 
- identifiers:
-     cce@rhel7: 80529-1
-+    cce@rhel8: 83424-2
- 
- references:
-     stigid@ol7: "020620"
-diff --git a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-index 1c5ac8d099..f931f6d160 100644
---- a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-@@ -20,6 +20,7 @@ severity: medium
- 
- identifiers:
-     cce@rhel7: 80532-5
-+    cce@rhel8: 83434-1
- 
- references:
-     stigid@ol7: "020650"
-diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt
-index 2f0d2a526b..45d03a2c1d 100644
---- a/shared/references/cce-redhat-avail.txt
-+++ b/shared/references/cce-redhat-avail.txt
-@@ -95,7 +95,6 @@ CCE-83411-9
- CCE-83421-8
- CCE-83422-6
- CCE-83423-4
--CCE-83424-2
- CCE-83425-9
- CCE-83426-7
- CCE-83427-5
-@@ -105,7 +104,6 @@ CCE-83430-9
- CCE-83431-7
- CCE-83432-5
- CCE-83433-3
--CCE-83434-1
- CCE-83435-8
- CCE-83436-6
- CCE-83437-4
-@@ -115,7 +113,6 @@ CCE-83440-8
- CCE-83441-6
- CCE-83442-4
- CCE-83443-2
--CCE-83444-0
- CCE-83445-7
- CCE-83446-5
- CCE-83447-3
diff --git a/SOURCES/scap-security-guide-0.1.51-cis_hipaa_ansible_fixes_PR_5777.patch b/SOURCES/scap-security-guide-0.1.51-cis_hipaa_ansible_fixes_PR_5777.patch
deleted file mode 100644
index b435b97..0000000
--- a/SOURCES/scap-security-guide-0.1.51-cis_hipaa_ansible_fixes_PR_5777.patch
+++ /dev/null
@@ -1,103 +0,0 @@
-From 31b216f0dbe9e7531f273fbbd618ff8905358497 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 21 May 2020 13:30:24 +0200
-Subject: [PATCH 1/3] simplify ansible remediation of no_direct_root_logins
-
----
- .../root_logins/no_direct_root_logins/ansible/shared.yml    | 6 +-----
- 1 file changed, 1 insertion(+), 5 deletions(-)
-
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/ansible/shared.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/ansible/shared.yml
-index e9a29a24d5..6fbb7c72a5 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/ansible/shared.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/ansible/shared.yml
-@@ -3,13 +3,9 @@
- # strategy = restrict
- # complexity = low
- # disruption = low
--- name: Test for existence of /etc/securetty
--  stat:
--    path: /etc/securetty
--  register: securetty_empty
-+
- 
- - name: "Direct root Logins Not Allowed"
-   copy:
-     dest: /etc/securetty
-     content: ""
--  when: securetty_empty.stat.size > 1
-
-From d12bcac36bac2a84ddf6162946b631c99fa86071 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 21 May 2020 14:21:38 +0200
-Subject: [PATCH 2/3] change name of libsemanage python bindings for rhel8
-
----
- shared/templates/template_ANSIBLE_sebool | 8 +++++++-
- 1 file changed, 7 insertions(+), 1 deletion(-)
-
-diff --git a/shared/templates/template_ANSIBLE_sebool b/shared/templates/template_ANSIBLE_sebool
-index 29f37081be..38d7c7c350 100644
---- a/shared/templates/template_ANSIBLE_sebool
-+++ b/shared/templates/template_ANSIBLE_sebool
-@@ -13,11 +13,17 @@
- {{% else %}}
- - (xccdf-var var_{{{ SEBOOLID }}})
- 
-+{{% if product == "rhel8" %}}
-+- name: Ensure python3-libsemanage installed
-+  package:
-+    name: python3-libsemanage
-+    state: present
-+{{% else %}}
- - name: Ensure libsemanage-python installed
-   package:
-     name: libsemanage-python
-     state: present
--
-+{{% endif %}}
- - name: Set SELinux boolean {{{ SEBOOLID }}} accordingly
-   seboolean:
-     name: {{{ SEBOOLID }}}
-
-From ccf902082fc4f5abd8fae702e4322c6089773012 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 21 May 2020 14:57:05 +0200
-Subject: [PATCH 3/3] add tests for no_direct_root_logins
-
----
- .../root_logins/no_direct_root_logins/tests/correct.pass.sh    | 3 +++
- .../root_logins/no_direct_root_logins/tests/missing.fail.sh    | 3 +++
- .../root_logins/no_direct_root_logins/tests/wrong.fail.sh      | 3 +++
- 3 files changed, 9 insertions(+)
- create mode 100644 linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/correct.pass.sh
- create mode 100644 linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/missing.fail.sh
- create mode 100644 linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/wrong.fail.sh
-
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/correct.pass.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/correct.pass.sh
-new file mode 100644
-index 0000000000..17251f6a98
---- /dev/null
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/correct.pass.sh
-@@ -0,0 +1,3 @@
-+#!/bin/bash
-+
-+echo > /etc/securetty
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/missing.fail.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/missing.fail.sh
-new file mode 100644
-index 0000000000..c764814b26
---- /dev/null
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/missing.fail.sh
-@@ -0,0 +1,3 @@
-+#!/bin/bash
-+
-+rm -f /etc/securetty
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/wrong.fail.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/wrong.fail.sh
-new file mode 100644
-index 0000000000..43ac341e87
---- /dev/null
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/tests/wrong.fail.sh
-@@ -0,0 +1,3 @@
-+#!/bin/bash
-+
-+echo "something" > /etc/securetty
diff --git a/SOURCES/scap-security-guide-0.1.51-create_macro_selinux_remediation_PR_5785.patch b/SOURCES/scap-security-guide-0.1.51-create_macro_selinux_remediation_PR_5785.patch
deleted file mode 100644
index 5c6664f..0000000
--- a/SOURCES/scap-security-guide-0.1.51-create_macro_selinux_remediation_PR_5785.patch
+++ /dev/null
@@ -1,308 +0,0 @@
-From a5281d8361dd26217e6ee1c97d5beaae02af34bc Mon Sep 17 00:00:00 2001
-From: Gabriel Becker 
-Date: Tue, 26 May 2020 17:49:21 +0200
-Subject: [PATCH 1/2] Create macro for selinux ansible/bash remediation.
-
-Affected rules:
- - selinux_policytype
- - selinux_state
----
- .../selinux/selinux_policytype/ansible/shared.yml |  9 ++-------
- .../selinux/selinux_policytype/bash/shared.sh     |  5 +++--
- .../tests/selinuxtype_minimum.fail.sh             | 10 ++++++++++
- .../selinux/selinux_state/ansible/shared.yml      |  9 ++-------
- .../system/selinux/selinux_state/bash/shared.sh   |  5 +++--
- .../selinux_state/tests/selinux_missing.fail.sh   |  5 +++++
- .../tests/selinux_permissive.fail.sh              | 10 ++++++++++
- shared/macros-ansible.jinja                       | 11 +++++++++++
- shared/macros-bash.jinja                          | 15 +++++++++++++++
- 9 files changed, 61 insertions(+), 18 deletions(-)
- create mode 100644 linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
- create mode 100644 linux_os/guide/system/selinux/selinux_state/tests/selinux_missing.fail.sh
- create mode 100644 linux_os/guide/system/selinux/selinux_state/tests/selinux_permissive.fail.sh
-
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml b/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-index 5c70cc9f7f..9f8cf66dfb 100644
---- a/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-+++ b/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-@@ -3,11 +3,6 @@
- # strategy = restrict
- # complexity = low
- # disruption = low
- - (xccdf-var var_selinux_policy_name)
- 
--- name: "{{{ rule_title }}}"
--  lineinfile:
--    path: /etc/sysconfig/selinux
--    regexp: '^SELINUXTYPE='
--    line: "SELINUXTYPE={{ var_selinux_policy_name }}"
--    create: yes
-+{{{ ansible_selinux_config_set(parameter="SELINUXTYPE", value="{{ var_selinux_policy_name }}") }}}
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh b/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-index d0fbbf4446..2b5ce31b12 100644
---- a/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-+++ b/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-@@ -1,7 +1,8 @@
- # platform = multi_platform_wrlinux,multi_platform_rhel,multi_platform_fedora,multi_platform_ol,multi_platform_rhv
--#
-+
- # Include source function library.
- . /usr/share/scap-security-guide/remediation_functions
-+
- populate var_selinux_policy_name
- 
--replace_or_append '/etc/sysconfig/selinux' '^SELINUXTYPE=' $var_selinux_policy_name '@CCENUM@' '%s=%s'
-+{{{ bash_selinux_config_set(parameter="SELINUXTYPE", value="$var_selinux_policy_name") }}}
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh b/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
-new file mode 100644
-index 0000000000..1a6eb94953
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
-@@ -0,0 +1,10 @@
-+#!/bin/bash
-+# profiles = xccdf_org.ssgproject.content_profile_C2S, xccdf_org.ssgproject.content_profile_ospp
-+
-+SELINUX_FILE='/etc/selinux/config'
-+
-+if grep -s '^[[:space:]]*SELINUXTYPE' $SELINUX_FILE; then
-+	sed -i 's/^\([[:space:]]*SELINUXTYPE[[:space:]]*=[[:space:]]*\).*/\minimum/' $SELINUX_FILE
-+else
-+	echo 'SELINUXTYPE=minimum' >> $SELINUX_FILE
-+fi
-diff --git a/linux_os/guide/system/selinux/selinux_state/ansible/shared.yml b/linux_os/guide/system/selinux/selinux_state/ansible/shared.yml
-index b465ac6729..1c1560a86c 100644
---- a/linux_os/guide/system/selinux/selinux_state/ansible/shared.yml
-+++ b/linux_os/guide/system/selinux/selinux_state/ansible/shared.yml
-@@ -3,11 +3,6 @@
- # strategy = restrict
- # complexity = low
- # disruption = low
- - (xccdf-var var_selinux_state)
- 
--- name: "{{{ rule_title }}}"
--  lineinfile:
--    path: /etc/sysconfig/selinux
--    regexp: '^SELINUX='
--    line: "SELINUX={{ var_selinux_state }}"
--    create: yes
-+{{{ ansible_selinux_config_set(parameter="SELINUX", value="{{ var_selinux_state }}") }}}
-diff --git a/linux_os/guide/system/selinux/selinux_state/bash/shared.sh b/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-index 58193b5504..a402a861d7 100644
---- a/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-+++ b/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-@@ -1,10 +1,11 @@
- # platform = multi_platform_wrlinux,multi_platform_rhel,multi_platform_fedora,multi_platorm_ol,multi_platform_rhv
--#
-+
- # Include source function library.
- . /usr/share/scap-security-guide/remediation_functions
-+
- populate var_selinux_state
- 
--replace_or_append '/etc/sysconfig/selinux' '^SELINUX=' $var_selinux_state '@CCENUM@' '%s=%s'
-+{{{ bash_selinux_config_set(parameter="SELINUX", value="$var_selinux_state") }}}
- 
- fixfiles onboot
- fixfiles -f relabel
-diff --git a/linux_os/guide/system/selinux/selinux_state/tests/selinux_missing.fail.sh b/linux_os/guide/system/selinux/selinux_state/tests/selinux_missing.fail.sh
-new file mode 100644
-index 0000000000..180dd80791
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_state/tests/selinux_missing.fail.sh
-@@ -0,0 +1,5 @@
-+#!/bin/bash
-+# profiles = xccdf_org.ssgproject.content_profile_C2S, xccdf_org.ssgproject.content_profile_ospp
-+
-+SELINUX_FILE='/etc/selinux/config'
-+sed -i '/^[[:space:]]*SELINUX/d' $SELINUX_FILE
-diff --git a/linux_os/guide/system/selinux/selinux_state/tests/selinux_permissive.fail.sh b/linux_os/guide/system/selinux/selinux_state/tests/selinux_permissive.fail.sh
-new file mode 100644
-index 0000000000..3db1e56b5f
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_state/tests/selinux_permissive.fail.sh
-@@ -0,0 +1,10 @@
-+#!/bin/bash
-+# profiles = xccdf_org.ssgproject.content_profile_C2S, xccdf_org.ssgproject.content_profile_ospp
-+
-+SELINUX_FILE='/etc/selinux/config'
-+
-+if grep -s '^[[:space:]]*SELINUX' $SELINUX_FILE; then
-+	sed -i 's/^\([[:space:]]*SELINUX[[:space:]]*=[[:space:]]*\).*/\permissive/' $SELINUX_FILE
-+else
-+	echo 'SELINUX=permissive' >> $SELINUX_FILE
-+fi
-diff --git a/shared/macros-ansible.jinja b/shared/macros-ansible.jinja
-index 6798a25d1f..01d3155b37 100644
---- a/shared/macros-ansible.jinja
-+++ b/shared/macros-ansible.jinja
-@@ -217,6 +217,17 @@ value: "Setting={{ varname1 }}"
- {{{ ansible_set_config_file(msg, "/etc/systemd/coredump.conf", parameter=parameter, value=value, create="no", separator="=", separator_regex="\s*=\s*") }}}
- {{%- endmacro %}}
- 
-+{{#
-+  High level macro to set a parameter in /etc/selinux/config.
-+  Parameters:
-+  - msg: the name for the Ansible task
-+  - parameter: parameter to be set in the configuration file
-+  - value: value of the parameter
-+#}}
-+{{%- macro ansible_selinux_config_set(msg='', parameter='', value='') %}}
-+{{{ ansible_set_config_file(msg, "/etc/selinux/config", parameter=parameter, value=value, create="no", separator="=", separator_regex="\s*=\s*") }}}
-+{{%- endmacro %}}
-+
- {{#
-   Generates an Ansible task that puts 'contents' into a file at 'filepath'
-   Parameters:
-diff --git a/shared/macros-bash.jinja b/shared/macros-bash.jinja
-index 3a94fe5dd8..2531d1c52d 100644
---- a/shared/macros-bash.jinja
-+++ b/shared/macros-bash.jinja
-@@ -86,6 +86,21 @@ populate {{{ name }}}
-     }}}
- {{%- endmacro -%}}
- 
-+{{%- macro bash_selinux_config_set(parameter, value) -%}}
-+{{{ set_config_file(
-+        path="/etc/selinux/config",
-+        parameter=parameter,
-+        value=value,
-+        create=true,
-+        insert_after="",
-+        insert_before="",
-+        insensitive=true,
-+        separator="=",
-+        separator_regex="\s*=\s*",
-+        prefix_regex="^\s*")
-+    }}}
-+{{%- endmacro -%}}
-+
- {{#
- # Install a package
- # Uses the right command based on pkg_manger proprerty defined in product.yaml.
-
-From 24c3c92007e6d3f8a684282b1351703523441389 Mon Sep 17 00:00:00 2001
-From: Gabriel Becker 
-Date: Wed, 27 May 2020 18:48:57 +0200
-Subject: [PATCH 2/2] Remediation requires reboot.
-
-Update OVAL check to disallow spaces.
-Removed selinuxtype_minimum test scenario since breaks the system.
----
- .../selinux/selinux_policytype/ansible/shared.yml      |  2 +-
- .../system/selinux/selinux_policytype/bash/shared.sh   |  4 ++++
- .../system/selinux/selinux_policytype/oval/shared.xml  |  2 +-
- .../tests/selinuxtype_minimum.fail.sh                  | 10 ----------
- .../guide/system/selinux/selinux_state/bash/shared.sh  |  4 ++++
- .../guide/system/selinux/selinux_state/oval/shared.xml |  2 +-
- shared/macros-ansible.jinja                            |  2 +-
- shared/macros-bash.jinja                               |  4 ++--
- 8 files changed, 14 insertions(+), 16 deletions(-)
- delete mode 100644 linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
-
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml b/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-index 9f8cf66dfb..73e6ec7cd4 100644
---- a/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-+++ b/linux_os/guide/system/selinux/selinux_policytype/ansible/shared.yml
-@@ -1,5 +1,5 @@
- # platform = multi_platform_rhel,multi_platform_fedora,multi_platform_ol,multi_platform_rhv
--# reboot = false
-+# reboot = true
- # strategy = restrict
- # complexity = low
- # disruption = low
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh b/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-index 2b5ce31b12..b4f79c97f9 100644
---- a/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-+++ b/linux_os/guide/system/selinux/selinux_policytype/bash/shared.sh
-@@ -1,4 +1,8 @@
- # platform = multi_platform_wrlinux,multi_platform_rhel,multi_platform_fedora,multi_platform_ol,multi_platform_rhv
-+# reboot = true
-+# strategy = restrict
-+# complexity = low
-+# disruption = low
- 
- # Include source function library.
- . /usr/share/scap-security-guide/remediation_functions
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml b/linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml
-index f1840a1290..3d69fff07f 100644
---- a/linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml
-+++ b/linux_os/guide/system/selinux/selinux_policytype/oval/shared.xml
-@@ -27,7 +27,7 @@
- 
-   
-     /etc/selinux/config
--    ^[\s]*SELINUXTYPE[\s]*=[\s]*([^\s]*)
-+    ^SELINUXTYPE=(.*)$
-     1
-   
- 
-diff --git a/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh b/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
-deleted file mode 100644
-index 1a6eb94953..0000000000
---- a/linux_os/guide/system/selinux/selinux_policytype/tests/selinuxtype_minimum.fail.sh
-+++ /dev/null
-@@ -1,10 +0,0 @@
--#!/bin/bash
--# profiles = xccdf_org.ssgproject.content_profile_C2S, xccdf_org.ssgproject.content_profile_ospp
--
--SELINUX_FILE='/etc/selinux/config'
--
--if grep -s '^[[:space:]]*SELINUXTYPE' $SELINUX_FILE; then
--	sed -i 's/^\([[:space:]]*SELINUXTYPE[[:space:]]*=[[:space:]]*\).*/\minimum/' $SELINUX_FILE
--else
--	echo 'SELINUXTYPE=minimum' >> $SELINUX_FILE
--fi
-diff --git a/linux_os/guide/system/selinux/selinux_state/bash/shared.sh b/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-index a402a861d7..645a7acab4 100644
---- a/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-+++ b/linux_os/guide/system/selinux/selinux_state/bash/shared.sh
-@@ -1,4 +1,8 @@
- # platform = multi_platform_wrlinux,multi_platform_rhel,multi_platform_fedora,multi_platorm_ol,multi_platform_rhv
-+# reboot = true
-+# strategy = restrict
-+# complexity = low
-+# disruption = low
- 
- # Include source function library.
- . /usr/share/scap-security-guide/remediation_functions
-diff --git a/linux_os/guide/system/selinux/selinux_state/oval/shared.xml b/linux_os/guide/system/selinux/selinux_state/oval/shared.xml
-index c0881696e1..8c328060af 100644
---- a/linux_os/guide/system/selinux/selinux_state/oval/shared.xml
-+++ b/linux_os/guide/system/selinux/selinux_state/oval/shared.xml
-@@ -18,7 +18,7 @@
- 
-   
-     /etc/selinux/config
--    ^[\s]*SELINUX[\s]*=[\s]*(.*)[\s]*$
-+    ^SELINUX=(.*)$
-     1
-   
- 
-diff --git a/shared/macros-ansible.jinja b/shared/macros-ansible.jinja
-index 01d3155b37..580a0b948e 100644
---- a/shared/macros-ansible.jinja
-+++ b/shared/macros-ansible.jinja
-@@ -225,7 +225,7 @@ value: "Setting={{ varname1 }}"
-   - value: value of the parameter
- #}}
- {{%- macro ansible_selinux_config_set(msg='', parameter='', value='') %}}
--{{{ ansible_set_config_file(msg, "/etc/selinux/config", parameter=parameter, value=value, create="no", separator="=", separator_regex="\s*=\s*") }}}
-+{{{ ansible_set_config_file(msg, "/etc/selinux/config", parameter=parameter, value=value, create="yes", separator="=", separator_regex="=", prefix_regex='^') }}}
- {{%- endmacro %}}
- 
- {{#
-diff --git a/shared/macros-bash.jinja b/shared/macros-bash.jinja
-index 2531d1c52d..8abcc914d3 100644
---- a/shared/macros-bash.jinja
-+++ b/shared/macros-bash.jinja
-@@ -96,8 +96,8 @@ populate {{{ name }}}
-         insert_before="",
-         insensitive=true,
-         separator="=",
--        separator_regex="\s*=\s*",
--        prefix_regex="^\s*")
-+        separator_regex="=",
-+        prefix_regex="^")
-     }}}
- {{%- endmacro -%}}
- 
diff --git a/SOURCES/scap-security-guide-0.1.51-fix-rhel6-cpe-dictionary_PR_5928.patch b/SOURCES/scap-security-guide-0.1.51-fix-rhel6-cpe-dictionary_PR_5928.patch
deleted file mode 100644
index 58339fa..0000000
--- a/SOURCES/scap-security-guide-0.1.51-fix-rhel6-cpe-dictionary_PR_5928.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From c7d49a79cffdbfb2e1231077f665cbb940b50a98 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= 
-Date: Mon, 13 Jul 2020 17:52:35 +0200
-Subject: [PATCH] Fix SCAPVAL error SRC-15
-
-The CPE `cpe:/a:grub2` is used in `xccdf-1.2:platform` element
-in group `bootloader-grub2`, but this CPE isn't defined in the
-RHEL 6 CPE dictionary. All used CPEs should be defined in the
-dictionary.
----
- rhel6/cpe/rhel6-cpe-dictionary.xml | 5 +++++
- 1 file changed, 5 insertions(+)
-
-diff --git a/rhel6/cpe/rhel6-cpe-dictionary.xml b/rhel6/cpe/rhel6-cpe-dictionary.xml
-index bca8986f7a..1b696b88d3 100644
---- a/rhel6/cpe/rhel6-cpe-dictionary.xml
-+++ b/rhel6/cpe/rhel6-cpe-dictionary.xml
-@@ -47,6 +47,11 @@
-             
-             installed_env_has_gdm_package
-       
-+      
-+            Package grub2 is installed
-+            
-+            installed_env_has_grub2_package
-+      
-       
-             Package libuser is installed
-             
diff --git a/SOURCES/scap-security-guide-0.1.51-fix-zipl-cpe-dictionary_PR_5912.patch b/SOURCES/scap-security-guide-0.1.51-fix-zipl-cpe-dictionary_PR_5912.patch
deleted file mode 100644
index 1f77753..0000000
--- a/SOURCES/scap-security-guide-0.1.51-fix-zipl-cpe-dictionary_PR_5912.patch
+++ /dev/null
@@ -1,250 +0,0 @@
-From d1b9040748605416220e09feb56fc5a6b6402f1e Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= 
-Date: Tue, 7 Jul 2020 16:37:30 +0200
-Subject: [PATCH] Add zipl to CPE dictionaries in all Linux products
-
-The CPE platform `cpe:/a:zipl` has been set as a platform for XCCDF
-group `bootloader-zipl` but the definition of the CPE was missing from
-the CPE dictionary in some datastreams, for example fedora datastream.
-This triggered error SRC-15 in NIST scapval tool.
----
- debian10/cpe/debian10-cpe-dictionary.xml       | 4 ++++
- debian8/cpe/debian8-cpe-dictionary.xml         | 4 ++++
- debian9/cpe/debian9-cpe-dictionary.xml         | 4 ++++
- fedora/cpe/fedora-cpe-dictionary.xml           | 4 ++++
- ol7/cpe/ol7-cpe-dictionary.xml                 | 4 ++++
- ol8/cpe/ol8-cpe-dictionary.xml                 | 4 ++++
- opensuse/cpe/opensuse-cpe-dictionary.xml       | 4 ++++
- rhel6/cpe/rhel6-cpe-dictionary.xml             | 4 ++++
- rhel7/cpe/rhel7-cpe-dictionary.xml             | 4 ++++
- rhv4/cpe/rhv4-cpe-dictionary.xml               | 4 ++++
- sle11/cpe/sle11-cpe-dictionary.xml             | 4 ++++
- sle12/cpe/sle12-cpe-dictionary.xml             | 4 ++++
- ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml   | 4 ++++
- ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml   | 4 ++++
- ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml   | 4 ++++
- wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml | 4 ++++
- wrlinux8/cpe/wrlinux8-cpe-dictionary.xml       | 4 ++++
- 19 files changed, 76 insertions(+)
-
-diff --git a/debian10/cpe/debian10-cpe-dictionary.xml b/debian10/cpe/debian10-cpe-dictionary.xml
-index f2dbd09cfc..ddb68c34bd 100644
---- a/debian10/cpe/debian10-cpe-dictionary.xml
-+++ b/debian10/cpe/debian10-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/debian8/cpe/debian8-cpe-dictionary.xml b/debian8/cpe/debian8-cpe-dictionary.xml
-index f385709052..24bbca69cd 100644
---- a/debian8/cpe/debian8-cpe-dictionary.xml
-+++ b/debian8/cpe/debian8-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/debian9/cpe/debian9-cpe-dictionary.xml b/debian9/cpe/debian9-cpe-dictionary.xml
-index bc90a12bae..d5595fd594 100644
---- a/debian9/cpe/debian9-cpe-dictionary.xml
-+++ b/debian9/cpe/debian9-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/fedora/cpe/fedora-cpe-dictionary.xml b/fedora/cpe/fedora-cpe-dictionary.xml
-index ff7cebc322..bef1337fc9 100644
---- a/fedora/cpe/fedora-cpe-dictionary.xml
-+++ b/fedora/cpe/fedora-cpe-dictionary.xml
-@@ -107,4 +107,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/ol7/cpe/ol7-cpe-dictionary.xml b/ol7/cpe/ol7-cpe-dictionary.xml
-index 613f853a6d..5d4691aaf6 100644
---- a/ol7/cpe/ol7-cpe-dictionary.xml
-+++ b/ol7/cpe/ol7-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/ol8/cpe/ol8-cpe-dictionary.xml b/ol8/cpe/ol8-cpe-dictionary.xml
-index 912fe01346..35167b1f70 100644
---- a/ol8/cpe/ol8-cpe-dictionary.xml
-+++ b/ol8/cpe/ol8-cpe-dictionary.xml
-@@ -67,4 +67,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/opensuse/cpe/opensuse-cpe-dictionary.xml b/opensuse/cpe/opensuse-cpe-dictionary.xml
-index 7f485b800e..6b95e46d3f 100644
---- a/opensuse/cpe/opensuse-cpe-dictionary.xml
-+++ b/opensuse/cpe/opensuse-cpe-dictionary.xml
-@@ -87,4 +87,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/rhel6/cpe/rhel6-cpe-dictionary.xml b/rhel6/cpe/rhel6-cpe-dictionary.xml
-index 2c8a82ebc5..bca8986f7a 100644
---- a/rhel6/cpe/rhel6-cpe-dictionary.xml
-+++ b/rhel6/cpe/rhel6-cpe-dictionary.xml
-@@ -87,4 +87,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/rhel7/cpe/rhel7-cpe-dictionary.xml b/rhel7/cpe/rhel7-cpe-dictionary.xml
-index f232b7ed29..bc2aa869e8 100644
---- a/rhel7/cpe/rhel7-cpe-dictionary.xml
-+++ b/rhel7/cpe/rhel7-cpe-dictionary.xml
-@@ -102,4 +102,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/rhv4/cpe/rhv4-cpe-dictionary.xml b/rhv4/cpe/rhv4-cpe-dictionary.xml
-index db1b4b239b..02450d6efc 100644
---- a/rhv4/cpe/rhv4-cpe-dictionary.xml
-+++ b/rhv4/cpe/rhv4-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/sle11/cpe/sle11-cpe-dictionary.xml b/sle11/cpe/sle11-cpe-dictionary.xml
-index 1b6b3e2518..b7cb4e1fd5 100644
---- a/sle11/cpe/sle11-cpe-dictionary.xml
-+++ b/sle11/cpe/sle11-cpe-dictionary.xml
-@@ -77,4 +77,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/sle12/cpe/sle12-cpe-dictionary.xml b/sle12/cpe/sle12-cpe-dictionary.xml
-index b1b66e1294..73cddd7740 100644
---- a/sle12/cpe/sle12-cpe-dictionary.xml
-+++ b/sle12/cpe/sle12-cpe-dictionary.xml
-@@ -77,4 +77,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml b/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml
-index 7f3ce4271b..3f5447741b 100644
---- a/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml
-+++ b/ubuntu1404/cpe/ubuntu1404-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml b/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml
-index 83f0c8c516..e3e842842b 100644
---- a/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml
-+++ b/ubuntu1604/cpe/ubuntu1604-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml b/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml
-index 77b78d74ec..897673c6f5 100644
---- a/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml
-+++ b/ubuntu1804/cpe/ubuntu1804-cpe-dictionary.xml
-@@ -72,4 +72,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml b/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml
-index cc4e806a4d..ef7e803505 100644
---- a/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml
-+++ b/wrlinux1019/cpe/wrlinux1019-cpe-dictionary.xml
-@@ -71,4 +71,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
-diff --git a/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml b/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml
-index 824c575a6a..7184ebfd0b 100644
---- a/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml
-+++ b/wrlinux8/cpe/wrlinux8-cpe-dictionary.xml
-@@ -71,4 +71,8 @@
-             
-             installed_env_has_yum_package
-       
-+      
-+            System uses zipl
-+            installed_env_has_zipl_package
-+      
- 
diff --git a/SOURCES/scap-security-guide-0.1.51-fix_ansible_template_mount_options_PR_5765.patch b/SOURCES/scap-security-guide-0.1.51-fix_ansible_template_mount_options_PR_5765.patch
deleted file mode 100644
index 1e028b7..0000000
--- a/SOURCES/scap-security-guide-0.1.51-fix_ansible_template_mount_options_PR_5765.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From 254cb60e722539032c6ea73616d6ab51eb1d4edf Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 23:36:18 +0200
-Subject: [PATCH] Ansible mount_option: split mount and option task
-
-Separate task that adds mount options mounts the mountpoint into two tasks.
-Conditioning the "mount" task on the absence of the target mount option
-caused the task to always be skipped when mount option was alredy present,
-and could result in the mount point not being mounted.
----
- shared/templates/template_ANSIBLE_mount_option | 11 ++++++++---
- 1 file changed, 8 insertions(+), 3 deletions(-)
-
-diff --git a/shared/templates/template_ANSIBLE_mount_option b/shared/templates/template_ANSIBLE_mount_option
-index 95bede25f9..a0cf8d6b7a 100644
---- a/shared/templates/template_ANSIBLE_mount_option
-+++ b/shared/templates/template_ANSIBLE_mount_option
-@@ -26,14 +26,19 @@
-     - device_name.stdout is defined and device_name.stdout_lines is defined
-     - (device_name.stdout | length > 0)
- 
--- name: Ensure permission {{{ MOUNTOPTION }}} are set on {{{ MOUNTPOINT }}}
-+- name: Make sure {{{ MOUNTOPTION }}} option is part of the to {{{ MOUNTPOINT }}} options
-+  set_fact:
-+    mount_info: "{{ mount_info | combine( {'options':''~mount_info.options~',{{{ MOUNTOPTION }}}' }) }}"
-+  when:
-+    - mount_info is defined and "{{{ MOUNTOPTION }}}" not in mount_info.options
-+
-+- name: Ensure {{{ MOUNTPOINT }}} is mounted with {{{ MOUNTOPTION }}} option
-   mount:
-     path: "{{{ MOUNTPOINT }}}"
-     src: "{{ mount_info.source }}"
--    opts: "{{ mount_info.options }},{{{ MOUNTOPTION }}}"
-+    opts: "{{ mount_info.options }}"
-     state: "mounted"
-     fstype: "{{ mount_info.fstype }}"
-   when:
--    - mount_info is defined and "{{{ MOUNTOPTION }}}" not in mount_info.options
-     - device_name.stdout is defined
-     - (device_name.stdout | length > 0)
diff --git a/SOURCES/scap-security-guide-0.1.51-fix_rpm_verify_permissions_conflict_PR_5770.patch b/SOURCES/scap-security-guide-0.1.51-fix_rpm_verify_permissions_conflict_PR_5770.patch
deleted file mode 100644
index 47b9cdb..0000000
--- a/SOURCES/scap-security-guide-0.1.51-fix_rpm_verify_permissions_conflict_PR_5770.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From bb039a92b4286c9090c0f40c82aefb967be2f5ba Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 14 May 2020 16:46:07 +0200
-Subject: [PATCH] reorder groups because of permissions verification
-
----
- ssg/build_yaml.py | 6 ++++++
- 1 file changed, 6 insertions(+)
-
-diff --git a/ssg/build_yaml.py b/ssg/build_yaml.py
-index e3e138283c..c9f3179c08 100644
---- a/ssg/build_yaml.py
-+++ b/ssg/build_yaml.py
-@@ -700,6 +700,11 @@ def to_xml_element(self):
-         # audit_rules_privileged_commands, othervise the rule
-         # does not catch newly installed screeen binary during remediation
-         # and report fail
-+        # the software group should come before the
-+        # bootloader-grub2 group because of conflict between
-+        # rules rpm_verify_permissions and file_permissions_grub2_cfg
-+        # specific rules concerning permissions should
-+        # be applied after the general rpm_verify_permissions
-         # The FIPS group should come before Crypto - if we want to set a different (stricter) Crypto Policy than FIPS.
-         # the firewalld_activation must come before ruleset_modifications, othervise
-         # remediations for ruleset_modifications won't work
-@@ -707,6 +712,7 @@ def to_xml_element(self):
-         # otherwise the remediation prints error although it is successful
-         priority_order = [
-             "accounts", "auditing",
-+            "software", "bootloader-grub2",
-             "fips", "crypto",
-             "firewalld_activation", "ruleset_modifications",
-             "disabling_ipv6", "configuring_ipv6"
diff --git a/SOURCES/scap-security-guide-0.1.51-fix_rsyslog_rules_PR_5763.patch b/SOURCES/scap-security-guide-0.1.51-fix_rsyslog_rules_PR_5763.patch
deleted file mode 100644
index 34531f1..0000000
--- a/SOURCES/scap-security-guide-0.1.51-fix_rsyslog_rules_PR_5763.patch
+++ /dev/null
@@ -1,171 +0,0 @@
-From 179cf6b43b8f10b4907267d976cb503066710e6f Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 14 May 2020 01:20:53 +0200
-Subject: [PATCH 1/4] Do not take paths from include or IncludeConfig
-
-All paths in /etc/rsyslog.conf were taken as log files, but paths
-in lines containing "include" or "$IncludeConfig" are config files.
-
-Let's not take them in as log files
----
- .../rsyslog_files_permissions/oval/shared.xml          | 10 ++++++++++
- 1 file changed, 10 insertions(+)
-
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-index a78cd69df2..c74f3da3f5 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-@@ -87,8 +87,18 @@
-     -->
-     ^[^\s#\$]+[\s]+.*[\s]+-?(/+[^:;\s]+);*.*$
-     1
-+    state_ignore_include_paths
-   
- 
-+  
-+    
-+    (?:file="[^\s;]+"|\$IncludeConfig[\s]+[^\s;]+)
-+  
-+
-   
-
-From 4a408d29313d8ea5aed4fa65cacad86f8078159c Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 14 May 2020 00:16:37 +0200
-Subject: [PATCH 2/4] Fix permissions of files referenced by include()
-
-The remediation script also needs to parse the files included via
-"include()".
-The awk also takes into consideration the multiline aspect.
----
- .../rsyslog_files_permissions/bash/shared.sh                  | 4 +++-
- 1 file changed, 3 insertions(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-index 6cbf0c6a24..dca35301e7 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-@@ -6,12 +6,14 @@ RSYSLOG_ETC_CONFIG="/etc/rsyslog.conf"
- # * And also the log file paths listed after rsyslog's $IncludeConfig directive
- #   (store the result into array for the case there's shell glob used as value of IncludeConfig)
- readarray -t RSYSLOG_INCLUDE_CONFIG < <(grep -e "\$IncludeConfig[[:space:]]\+[^[:space:];]\+" /etc/rsyslog.conf | cut -d ' ' -f 2)
-+readarray -t RSYSLOG_INCLUDE < <(awk '/)/{f=0} /include\(/{f=1} f{nf=gensub(".*file=\"(\\S+)\".*","\\1",1); if($0!=nf){print nf}}' /etc/rsyslog.conf)
-+
- # Declare an array to hold the final list of different log file paths
- declare -a LOG_FILE_PATHS
- 
- # Browse each file selected above as containing paths of log files
- # ('/etc/rsyslog.conf' and '/etc/rsyslog.d/*.conf' in the default configuration)
--for LOG_FILE in "${RSYSLOG_ETC_CONFIG}" "${RSYSLOG_INCLUDE_CONFIG[@]}"
-+for LOG_FILE in "${RSYSLOG_ETC_CONFIG}" "${RSYSLOG_INCLUDE_CONFIG[@]}" "${RSYSLOG_INCLUDE[@]}"
- do
- 	# From each of these files extract just particular log file path(s), thus:
- 	# * Ignore lines starting with space (' '), comment ('#"), or variable syntax ('$') characters,
-
-From 812e9b487e3c11a18e5e3a965ac23ec1a0d64e91 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 15:53:58 +0200
-Subject: [PATCH 3/4] Make regex for include file more strict
-
-For some reason gensub in awk doesn't support non capturing group.
-So the group with OR is capturing and we substitute everyting with the
-second group, witch matches the file path.
----
- .../rsyslog_files_permissions/bash/shared.sh                    | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-index dca35301e7..99d2d0e794 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/bash/shared.sh
-@@ -6,7 +6,7 @@ RSYSLOG_ETC_CONFIG="/etc/rsyslog.conf"
- # * And also the log file paths listed after rsyslog's $IncludeConfig directive
- #   (store the result into array for the case there's shell glob used as value of IncludeConfig)
- readarray -t RSYSLOG_INCLUDE_CONFIG < <(grep -e "\$IncludeConfig[[:space:]]\+[^[:space:];]\+" /etc/rsyslog.conf | cut -d ' ' -f 2)
--readarray -t RSYSLOG_INCLUDE < <(awk '/)/{f=0} /include\(/{f=1} f{nf=gensub(".*file=\"(\\S+)\".*","\\1",1); if($0!=nf){print nf}}' /etc/rsyslog.conf)
-+readarray -t RSYSLOG_INCLUDE < <(awk '/)/{f=0} /include\(/{f=1} f{nf=gensub("^(include\\(|\\s*)file=\"(\\S+)\".*","\\2",1); if($0!=nf){print nf}}' /etc/rsyslog.conf)
- 
- # Declare an array to hold the final list of different log file paths
- declare -a LOG_FILE_PATHS
-
-From c49f8aaf717313a41bbdfca188dd491a13d1133e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 15 May 2020 16:55:02 +0200
-Subject: [PATCH 4/4] Extend OVAL fix to groupownership and ownership
-
-These three files basically work the same way
----
- .../rsyslog_files_groupownership/oval/shared.xml       | 10 ++++++++++
- .../rsyslog_files_ownership/oval/shared.xml            | 10 ++++++++++
- .../rsyslog_files_permissions/oval/shared.xml          |  4 ++--
- 3 files changed, 22 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_groupownership/oval/shared.xml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_groupownership/oval/shared.xml
-index 5828f25321..9941e2b94f 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_groupownership/oval/shared.xml
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_groupownership/oval/shared.xml
-@@ -86,8 +86,18 @@
-     -->
-     ^[^(\s|#|\$)]+[\s]+.*[\s]+-?(/+[^:;\s]+);*.*$
-     1
-+    state_groupownership_ignore_include_paths
-   
- 
-+  
-+    
-+    (?:file="[^\s;]+"|\$IncludeConfig[\s]+[^\s;]+)
-+  
-+
-   
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_ownership/oval/shared.xml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_ownership/oval/shared.xml
-index 3c46eab6d6..29dd1a989e 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_ownership/oval/shared.xml
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_ownership/oval/shared.xml
-@@ -83,8 +83,18 @@
-     -->
-     ^[^(\s|#|\$)]+[\s]+.*[\s]+-?(/+[^:;\s]+);*.*$
-     1
-+    state_owner_ignore_include_paths
-   
- 
-+  
-+    
-+    (?:file="[^\s;]+"|\$IncludeConfig[\s]+[^\s;]+)
-+  
-+
-   
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-index c74f3da3f5..da37a15b8c 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/oval/shared.xml
-@@ -87,10 +87,10 @@
-     -->
-     ^[^\s#\$]+[\s]+.*[\s]+-?(/+[^:;\s]+);*.*$
-     1
--    state_ignore_include_paths
-+    state_permissions_ignore_include_paths
-   
- 
--  
-+  
-     
--  
--    
--  
--
-   
-   
--
--  
--  
--    
--    
--      
--      
--      
--      
--      
--        
--        
--        
--          -1
--          
--          
--            
--            
--            -1
--          
--        
--      
--    
--  
--
--  
--  
--    variable_default_range_quad_expr
--  
--
--  
--  
--    0
--  
--
-   
-   
--  
--    
--    
--  
-+    
-+    
-+    
-+  
-+
-+  
-+    0
-+  
-+  
-+    
-+  
- 
-   
-   
-   
- 
--  
--
--  
--  
--    
--    
--      
--      
--      
--      
--      
--        
--        
--        
--        
--          -1
--          
--        
--      
--    
--  
--
--  
--  
--    variable_reserved_range_quad_expr
--  
--
--  
--  
--    0
--  
--
-   
-   
--  
--    
--    
--  
--
--  
--
--  
--  
--    
--    
--      
--      
--        
--        
--        
--        
--          -1
--          
--        
--      
--      
--      
--        
--        
--        
--        
--          -1
--          
--        
--      
--    
--  
--
--  
--  
--    variable_dynalloc_range_quad_expr
--  
-+    
-+    
-+    
-+  
- 
--  
--  
--    0
--  
-+  
-+    
-+  
- 
-   
-   
--  
--    
--    
--  
-+    
-+    
-+    
-+  
- 
-+  
-+    
-+  
-+  
-+    
-+  
- 
-
-From 31654f72ee7cd30f937f84889c870fd330e7c366 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 4 Jun 2020 14:04:37 +0200
-Subject: [PATCH 3/3] no_shelllogin_for_systemaccounts: Fix text shebangs
-
----
- .../no_shelllogin_for_systemaccounts/tests/default.pass.sh     | 2 +-
- .../no_shelllogin_for_systemaccounts/tests/no_sys_uids.pass.sh | 3 +--
- .../tests/only_system_users.pass.sh                            | 3 +--
- .../tests/system_user_with_shell.fail.sh                       | 3 +--
- 4 files changed, 4 insertions(+), 7 deletions(-)
-
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/default.pass.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/default.pass.sh
-index 6d48ad78fd..833831f79d 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/default.pass.sh
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/default.pass.sh
-@@ -1,4 +1,4 @@
-+#!/bin/bash
- # remediation = none
- 
--#!/bin/bash
- true
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/no_sys_uids.pass.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/no_sys_uids.pass.sh
-index bc4f9cee8c..6769895eb2 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/no_sys_uids.pass.sh
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/no_sys_uids.pass.sh
-@@ -1,6 +1,5 @@
--# remediation = none
--
- #!/bin/bash
-+# remediation = none
- 
- # Force unset of SYS_UID values
- sed -i '/^SYS_UID_MIN/d' /etc/login.defs
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/only_system_users.pass.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/only_system_users.pass.sh
-index 0cdb820bbb..06edf671ce 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/only_system_users.pass.sh
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/only_system_users.pass.sh
-@@ -1,6 +1,5 @@
--# remediation = none
--
- #!/bin/bash
-+# remediation = none
- 
- # remove any non-system user
- sed -Ei '/^root|nologin$|halt$|sync$|shutdown$/!d' /etc/passwd
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/system_user_with_shell.fail.sh b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/system_user_with_shell.fail.sh
-index 7639a8809d..10312593b8 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/system_user_with_shell.fail.sh
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_shelllogin_for_systemaccounts/tests/system_user_with_shell.fail.sh
-@@ -1,6 +1,5 @@
--# remediation = none
--
- #!/bin/bash
-+# remediation = none
- 
- # change system user "mail" shell to bash
- usermod --shell /bin/bash mail
diff --git a/SOURCES/scap-security-guide-0.1.51-openssl_crypto_PR_5885.patch b/SOURCES/scap-security-guide-0.1.51-openssl_crypto_PR_5885.patch
deleted file mode 100644
index 218e89b..0000000
--- a/SOURCES/scap-security-guide-0.1.51-openssl_crypto_PR_5885.patch
+++ /dev/null
@@ -1,163 +0,0 @@
-From bf4da502abb91d3db88e76f7239880909f400604 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 25 Jun 2020 09:53:38 +0200
-Subject: [PATCH 1/3] fixed description, oval, ansible, bash
-
----
- .../configure_openssl_crypto_policy/ansible/shared.yml |  4 ++--
- .../configure_openssl_crypto_policy/bash/shared.sh     |  4 ++--
- .../configure_openssl_crypto_policy/oval/shared.xml    |  2 +-
- .../crypto/configure_openssl_crypto_policy/rule.yml    | 10 +++++-----
- 4 files changed, 10 insertions(+), 10 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-index e6318f221c..98fe134aca 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-@@ -15,7 +15,7 @@
-   lineinfile:
-     create: yes
-     insertafter: '^\s*\[\s*crypto_policy\s*]\s*'
--    line: ".include /etc/crypto-policies/back-ends/openssl.config"
-+    line: ".include /etc/crypto-policies/back-ends/opensslcnf.config"
-     path: /etc/pki/tls/openssl.cnf
-   when:
-     - test_crypto_policy_group.stdout is defined
-@@ -24,7 +24,7 @@
- - name: "Add crypto_policy group and set include openssl.config"
-   lineinfile:
-     create: yes
--    line: "[crypto_policy]\n.include /etc/crypto-policies/back-ends/openssl.config"
-+    line: "[crypto_policy]\n.include /etc/crypto-policies/back-ends/opensslcnf.config"
-     path: /etc/pki/tls/openssl.cnf
-   when:
-     - test_crypto_policy_group.stdout is defined
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/bash/shared.sh b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/bash/shared.sh
-index 0b3cbf3b46..a0b30cce96 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/bash/shared.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/bash/shared.sh
-@@ -2,8 +2,8 @@
- 
- OPENSSL_CRYPTO_POLICY_SECTION='[ crypto_policy ]'
- OPENSSL_CRYPTO_POLICY_SECTION_REGEX='\[\s*crypto_policy\s*\]'
--OPENSSL_CRYPTO_POLICY_INCLUSION='.include /etc/crypto-policies/back-ends/openssl.config'
--OPENSSL_CRYPTO_POLICY_INCLUSION_REGEX='^\s*\.include\s*/etc/crypto-policies/back-ends/openssl.config$'
-+OPENSSL_CRYPTO_POLICY_INCLUSION='.include /etc/crypto-policies/back-ends/opensslcnf.config'
-+OPENSSL_CRYPTO_POLICY_INCLUSION_REGEX='^\s*\.include\s*/etc/crypto-policies/back-ends/opensslcnf.config$'
- 
- function remediate_openssl_crypto_policy() {
- 	CONFIG_FILE="/etc/pki/tls/openssl.cnf"
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/oval/shared.xml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/oval/shared.xml
-index a9b3f7b6e9..2019769736 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/oval/shared.xml
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/oval/shared.xml
-@@ -20,7 +20,7 @@
-   
-     /etc/pki/tls/openssl.cnf
--    ^\s*\[\s*crypto_policy\s*\]\s*\n*\s*\.include\s*/etc/crypto-policies/back-ends/openssl.config\s*$
-+    ^\s*\[\s*crypto_policy\s*\]\s*\n*\s*\.include\s*/etc/crypto-policies/back-ends/opensslcnf.config\s*$
-     1
-   
- 
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml
-index 8c015bb3b2..1a66570a8c 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/rule.yml
-@@ -11,7 +11,7 @@ description: |-
-     To check that Crypto Policies settings are configured correctly, you have to examine the OpenSSL config file
-     available under /etc/pki/tls/openssl.cnf.
-     This file has the ini format, and it enables crypto policy support
--    if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/openssl.config directive.
-+    if there is a [ crypto_policy ] section that contains the .include /etc/crypto-policies/back-ends/opensslcnf.config directive.
- 
- rationale: |-
-     Overriding the system crypto policy makes the behavior of the Java runtime violates expectations,
-@@ -29,11 +29,11 @@ references:
- 
- ocil_clause: |-
-     the OpenSSL config file doesn't contain the whole section,
--    or that the section doesn't have the 
.include /etc/crypto-policies/back-ends/openssl.config
 directive
-+    or that the section doesn't have the 
.include /etc/crypto-policies/back-ends/opensslcnf.config
 directive
- 
- ocil: |-
--    To verify that OpenSSL uses the system crypro policy, check out that the OpenSSL config file
-+    To verify that OpenSSL uses the system crypto policy, check out that the OpenSSL config file
-     
/etc/pki/tls/openssl.cnf
 contains the 
[ crypto_policy ]
 section with the
--    
.include /etc/crypto-policies/back-ends/openssl.config
 directive:
--    
grep '\.include\s* /etc/crypto-policies/back-ends/openssl.config$' /etc/pki/tls/openssl.cnf
.
-+    
.include /etc/crypto-policies/back-ends/opensslcnf.config
 directive:
-+    
grep '\.include\s* /etc/crypto-policies/back-ends/opensslcnf.config$' /etc/pki/tls/openssl.cnf
.
- 
-
-From 5e4f19a3301fbdc74b199b418a435924089d6c30 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 25 Jun 2020 09:54:09 +0200
-Subject: [PATCH 2/3] updated tests
-
----
- .../configure_openssl_crypto_policy/tests/ok.pass.sh   |  2 +-
- .../tests/wrong.fail.sh                                | 10 ++++++++++
- 2 files changed, 11 insertions(+), 1 deletion(-)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/wrong.fail.sh
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/ok.pass.sh b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/ok.pass.sh
-index 5b8334735e..c56916883e 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/ok.pass.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/ok.pass.sh
-@@ -6,5 +6,5 @@
- 
- create_config_file_with "[ crypto_policy ]
- 
--.include /etc/crypto-policies/back-ends/openssl.config
-+.include /etc/crypto-policies/back-ends/opensslcnf.config
- "
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/wrong.fail.sh b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/wrong.fail.sh
-new file mode 100644
-index 0000000000..5b8334735e
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/tests/wrong.fail.sh
-@@ -0,0 +1,10 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp, xccdf_org.ssgproject.content_profile_standard
-+
-+. common.sh
-+
-+create_config_file_with "[ crypto_policy ]
-+
-+.include /etc/crypto-policies/back-ends/openssl.config
-+"
-
-From 73804523130ce02162b780b8811e79e6adcb51a6 Mon Sep 17 00:00:00 2001
-From: Gabriel Becker 
-Date: Thu, 25 Jun 2020 17:32:00 +0200
-Subject: [PATCH 3/3] Update task name to reflect correct opensslcnf.config
- file.
-
----
- .../crypto/configure_openssl_crypto_policy/ansible/shared.yml | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-index 98fe134aca..986543c10f 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_openssl_crypto_policy/ansible/shared.yml
-@@ -11,7 +11,7 @@
-   changed_when: False
-   check_mode: no
- 
--- name: "Add .include for openssl.config to crypto_policy section"
-+- name: "Add .include for opensslcnf.config to crypto_policy section"
-   lineinfile:
-     create: yes
-     insertafter: '^\s*\[\s*crypto_policy\s*]\s*'
-@@ -21,7 +21,7 @@
-     - test_crypto_policy_group.stdout is defined
-     - test_crypto_policy_group.stdout | length > 0
- 
--- name: "Add crypto_policy group and set include openssl.config"
-+- name: "Add crypto_policy group and set include opensslcnf.config"
-   lineinfile:
-     create: yes
-     line: "[crypto_policy]\n.include /etc/crypto-policies/back-ends/opensslcnf.config"
diff --git a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5772.patch b/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5772.patch
deleted file mode 100644
index 77a9e01..0000000
--- a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5772.patch
+++ /dev/null
@@ -1,383 +0,0 @@
-From 91c7ff65572b51b52eaf14f3b147b118dc85cc9f Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Tue, 19 May 2020 15:49:34 +0200
-Subject: [PATCH 1/5] Made the rule sshd_rekey_limit parametrized.
-
-Introduce the rekey_limit_size and rekey_limit_time XCCDF values
-to make the rule more flexible.
----
- .../sshd_rekey_limit/bash/shared.sh           |  9 ++++
- .../sshd_rekey_limit/oval/shared.xml          | 43 +++++++++++++++++++
- .../ssh/ssh_server/sshd_rekey_limit/rule.yml  | 12 +-----
- .../sshd_rekey_limit/tests/bad_size.fail.sh   |  4 ++
- .../sshd_rekey_limit/tests/bad_time.fail.sh   |  4 ++
- .../sshd_rekey_limit/tests/no_line.fail.sh    |  3 ++
- .../sshd_rekey_limit/tests/ok.pass.sh         |  4 ++
- .../ssh/ssh_server/var_rekey_limit_size.var   | 14 ++++++
- .../ssh/ssh_server/var_rekey_limit_time.var   | 14 ++++++
- rhel8/profiles/ospp.profile                   |  2 +
- 10 files changed, 99 insertions(+), 10 deletions(-)
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_size.fail.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_time.fail.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/no_line.fail.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/ok.pass.sh
- create mode 100644 linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
- create mode 100644 linux_os/guide/services/ssh/ssh_server/var_rekey_limit_time.var
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
-new file mode 100644
-index 0000000000..2620c2d49e
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
-@@ -0,0 +1,9 @@
-+# platform = multi_platform_all
-+
-+# Include source function library.
-+. /usr/share/scap-security-guide/remediation_functions
-+
-+populate var_rekey_limit_size
-+populate var_rekey_limit_time
-+
-+{{{ bash_sshd_config_set(parameter='RekeyLimit', value="$var_rekey_limit_size $var_rekey_limit_time") }}}
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
-new file mode 100644
-index 0000000000..57aa090948
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
-@@ -0,0 +1,43 @@
-+{{% set filepath = "/etc/ssh/sshd_config" %}}
-+{{% set parameter = "RekeyLimit" %}}
-+
-+
-+
-+  
-+    
-+      {{{ rule_title }}}
-+      {{{- oval_affected(products) }}}
-+      Ensure '{{{ RekeyLimit }}}' is configured with the correct value in '{{{ filepath }}}'
-+    
-+    
-+        {{{- application_not_required_or_requirement_unset() }}}
-+        {{{- application_required_or_requirement_unset() }}}
-+        {{{- oval_line_in_file_criterion(filepath, "RekeyLimit") }}}
-+    
-+    
-+  
-+
-+  
-+     
-+  
-+
-+  
-+     {{{ filepath }}}
-+     
-+     1
-+  
-+
-+  
-+    
-+      ^[\s]*RekeyLimit[\s]+
-+      
-+      [\s]+
-+      
-+      [\s]*$
-+    
-+  
-+
-+  
-+  
-+
-+
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml
-index e11678faa0..4936a381f5 100644
---- a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/rule.yml
-@@ -7,7 +7,7 @@ description: |-
-     the session key of the is renegotiated, both in terms of
-     amount of data that may be transmitted and the time
-     elapsed. To decrease the default limits, put line
--    RekeyLimit 512M 1h to file /etc/ssh/sshd_config.
-+    RekeyLimit {{{ sub_var_value("var_rekey_limit_size") }}} {{{ sub_var_value("var_rekey_limit_time") }}} to file /etc/ssh/sshd_config.
- 
- rationale: |-
-     By decreasing the limit based on the amount of data and enabling
-@@ -30,12 +30,4 @@ ocil: |-
-     following command:
-     
$ sudo grep RekeyLimit /etc/ssh/sshd_config

-     If configured properly, output should be
--    
RekeyLimit 512M 1h

--
--template:
--    name: sshd_lineinfile
--    vars:
--        missing_parameter_pass: 'false'
--        parameter: RekeyLimit
--        rule_id: sshd_rekey_limit
--        value: 512M 1h
-+    
RekeyLimit {{{ sub_var_value("var_rekey_limit_size") }}} {{{ sub_var_value("var_rekey_limit_time") }}}

-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_size.fail.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_size.fail.sh
-new file mode 100644
-index 0000000000..2ac0bbf350
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_size.fail.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 812M 1h" >> /etc/ssh/sshd_config
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_time.fail.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_time.fail.sh
-new file mode 100644
-index 0000000000..fec859fe05
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/bad_time.fail.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 512M 2h" >> /etc/ssh/sshd_config
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/no_line.fail.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/no_line.fail.sh
-new file mode 100644
-index 0000000000..a6cd10163f
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/no_line.fail.sh
-@@ -0,0 +1,3 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/ok.pass.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/ok.pass.sh
-new file mode 100644
-index 0000000000..a6a2ba7adf
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/tests/ok.pass.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/sshd_config
-diff --git a/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
-new file mode 100644
-index 0000000000..16dc376508
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
-@@ -0,0 +1,14 @@
-+documentation_complete: true
-+
-+title: 'SSH RekeyLimit - size'
-+
-+description: 'Specify the size component of the rekey limit.'
-+
-+type: string
-+
-+operator: equals
-+
-+options:
-+    sshd_default: "default"
-+    default: "512M"
-+    "512M": "512M"
-diff --git a/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_time.var b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_time.var
-new file mode 100644
-index 0000000000..8801fbbf6f
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_time.var
-@@ -0,0 +1,14 @@
-+documentation_complete: true
-+
-+title: 'SSH RekeyLimit - size'
-+
-+description: 'Specify the size component of the rekey limit.'
-+
-+type: string
-+
-+operator: equals
-+
-+options:
-+    sshd_default: "none"
-+    default: "1h"
-+    "1hour": "1h"
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index c672066050..a5223a187f 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -58,6 +58,8 @@ selections:
-     - sshd_set_keepalive
-     - sshd_enable_warning_banner
-     - sshd_rekey_limit
-+    - var_rekey_limit_size=512M
-+    - var_rekey_limit_time=1hour
-     - sshd_use_strong_rng
-     - openssl_use_strong_entropy
- 
-
-From 85efae481db88792de138916c242fbbf0a7adeb1 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Tue, 19 May 2020 17:57:12 +0200
-Subject: [PATCH 2/5] Updated stable profile definitions.
-
----
- tests/data/profile_stability/rhel8/ospp.profile | 2 ++
- tests/data/profile_stability/rhel8/stig.profile | 3 ++-
- 2 files changed, 4 insertions(+), 1 deletion(-)
-
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index 23039c82b4..bdda39a903 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -214,6 +214,8 @@ selections:
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
- - var_sshd_set_keepalive=0
-+- var_rekey_limit_size=512M
-+- var_rekey_limit_time=1hour
- - var_accounts_user_umask=027
- - var_password_pam_difok=4
- - var_password_pam_maxrepeat=3
-diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
-index cd31b73700..ebef541921 100644
---- a/tests/data/profile_stability/rhel8/stig.profile
-+++ b/tests/data/profile_stability/rhel8/stig.profile
-@@ -21,7 +21,6 @@ description: 'This profile contains configuration checks that align to the
- 
-     - Red Hat Containers with a Red Hat Enterprise Linux 8 image'
- documentation_complete: true
--extends: ospp
- selections:
- - account_disable_post_pw_expiration
- - account_temp_expire_date
-@@ -243,6 +242,8 @@ selections:
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
- - var_sshd_set_keepalive=0
-+- var_rekey_limit_size=512M
-+- var_rekey_limit_time=1hour
- - var_accounts_user_umask=027
- - var_password_pam_difok=4
- - var_password_pam_maxrepeat=3
-
-From d75161c4f7232380a1b46aa8d99fa5d562503c80 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Fri, 22 May 2020 11:43:36 +0200
-Subject: [PATCH 3/5] Improved how variables are handled in remediations.
-
----
- shared/macros-ansible.jinja | 14 ++++++++++++++
- shared/macros-bash.jinja    | 15 +++++++++++++++
- 2 files changed, 29 insertions(+)
-
-diff --git a/shared/macros-ansible.jinja b/shared/macros-ansible.jinja
-index 56a3f5f3ec..6798a25d1f 100644
---- a/shared/macros-ansible.jinja
-+++ b/shared/macros-ansible.jinja
-@@ -1,3 +1,17 @@
-+{{#
-+Pass strings that correspond to XCCDF value names as arguments to this macro:
-+ansible_instantiate_variables("varname1", "varname2")
-+
-+Then, assume that the task that follows can work with the variable by referencing it, e.g.
-+value: "Setting={{ varname1 }}"
-+
-+#}}
-+{{%- macro ansible_instantiate_variables() -%}}
-+{{%- for name in varargs -%}}
-+- (xccdf-var {{{ name }}})
-+{{% endfor -%}}
-+{{%- endmacro -%}}
-+
- {{#
-   A wrapper over the Ansible lineinfile module. This handles the most common
-   options for us. regex is optional and when blank, it won't be included in
-diff --git a/shared/macros-bash.jinja b/shared/macros-bash.jinja
-index 01b9e62e7b..3a94fe5dd8 100644
---- a/shared/macros-bash.jinja
-+++ b/shared/macros-bash.jinja
-@@ -1,5 +1,20 @@
- {{# ##### High level macros ##### #}}
- 
-+{{#
-+Pass strings that correspond to XCCDF value names as arguments to this macro:
-+bash_instantiate_variables("varname1", "varname2")
-+
-+Then, assume that variables of that names are defined and contain the correct value, e.g.
-+echo "Setting=$varname1" >> config_file
-+
-+#}}
-+{{%- macro bash_instantiate_variables() -%}}
-+{{%- for name in varargs -%}}
-+populate {{{ name }}}
-+{{# this line is intentionally left blank #}}
-+{{% endfor -%}}
-+{{%- endmacro -%}}
-+
- {{%- macro bash_shell_file_set(path, parameter, value, no_quotes=false) -%}}
- {{% if no_quotes -%}}
-   {{% if "$" in value %}}
-
-From 912ce0a4ade9aa335c044314a6cc018f1ead1abe Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Fri, 22 May 2020 11:44:08 +0200
-Subject: [PATCH 4/5] Fixed Bash and Ansible remediations.
-
----
- .../ssh/ssh_server/sshd_rekey_limit/ansible/shared.yml    | 8 ++++++++
- .../ssh/ssh_server/sshd_rekey_limit/bash/shared.sh        | 3 +--
- 2 files changed, 9 insertions(+), 2 deletions(-)
- create mode 100644 linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/ansible/shared.yml
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/ansible/shared.yml b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/ansible/shared.yml
-new file mode 100644
-index 0000000000..43a2d4521f
---- /dev/null
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/ansible/shared.yml
-@@ -0,0 +1,8 @@
-+# platform = multi_platform_all                                                                                                                                                                                                                                                                                        [0/453]
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+{{{ ansible_instantiate_variables("var_rekey_limit_size", "var_rekey_limit_time") }}}
-+
-+{{{ ansible_sshd_set(parameter="RekeyLimit", value="{{ var_rekey_limit_size}} {{var_rekey_limit_time}}") }}}
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
-index 2620c2d49e..0277f31392 100644
---- a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/bash/shared.sh
-@@ -3,7 +3,6 @@
- # Include source function library.
- . /usr/share/scap-security-guide/remediation_functions
- 
--populate var_rekey_limit_size
--populate var_rekey_limit_time
-+{{{ bash_instantiate_variables("var_rekey_limit_size", "var_rekey_limit_time") }}}
- 
- {{{ bash_sshd_config_set(parameter='RekeyLimit', value="$var_rekey_limit_size $var_rekey_limit_time") }}}
-
-From d0ac47945e14017e522d523267d3a4bfb5ecdf71 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Fri, 22 May 2020 11:49:04 +0200
-Subject: [PATCH 5/5] Improved the OVAL according to the review feedback.
-
----
- .../services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml | 5 ++---
- 1 file changed, 2 insertions(+), 3 deletions(-)
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
-index 57aa090948..47796e5332 100644
---- a/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
-+++ b/linux_os/guide/services/ssh/ssh_server/sshd_rekey_limit/oval/shared.xml
-@@ -1,5 +1,4 @@
--{{% set filepath = "/etc/ssh/sshd_config" %}}
--{{% set parameter = "RekeyLimit" %}}
-+{{% set filepath = "/etc/ssh/sshd_config" -%}}
- 
- 
- 
-@@ -7,7 +6,7 @@
-     
-       {{{ rule_title }}}
-       {{{- oval_affected(products) }}}
--      Ensure '{{{ RekeyLimit }}}' is configured with the correct value in '{{{ filepath }}}'
-+      Ensure 'RekeyLimit' is configured with the correct value in '{{{ filepath }}}'
-     
-     
-         {{{- application_not_required_or_requirement_unset() }}}
diff --git a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5782.patch b/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5782.patch
deleted file mode 100644
index 2b758fb..0000000
--- a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5782.patch
+++ /dev/null
@@ -1,102 +0,0 @@
-From 279b1d8b585d3521d4910ec8aa69583f9b7031ac Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 25 May 2020 10:51:24 +0200
-Subject: [PATCH 1/3] change rekey limit to 1G 1h in rhel8 ospp
-
----
- .../guide/services/ssh/ssh_server/var_rekey_limit_size.var     | 1 +
- rhel8/profiles/ospp.profile                                    | 2 +-
- rhel8/profiles/stig.profile                                    | 3 +++
- 3 files changed, 5 insertions(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
-index 16dc376508..395a087a68 100644
---- a/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
-+++ b/linux_os/guide/services/ssh/ssh_server/var_rekey_limit_size.var
-@@ -12,3 +12,4 @@ options:
-     sshd_default: "default"
-     default: "512M"
-     "512M": "512M"
-+    "1G": "1G"
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index a5223a187f..0dca8350f9 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -58,7 +58,7 @@ selections:
-     - sshd_set_keepalive
-     - sshd_enable_warning_banner
-     - sshd_rekey_limit
--    - var_rekey_limit_size=512M
-+    - var_rekey_limit_size=1G
-     - var_rekey_limit_time=1hour
-     - sshd_use_strong_rng
-     - openssl_use_strong_entropy
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index 2bb81cf9dc..a156857647 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -44,3 +44,6 @@ selections:
-     - package_rsyslog-gnutls_installed
-     - rsyslog_remote_tls
-     - rsyslog_remote_tls_cacert
-+    - sshd_rekey_limit
-+    - var_rekey_limit_size=512M
-+    - var_rekey_limit_time=1hour
-
-From d8ce7bb5f47665e40b6ec2c47e565bb7c46164a9 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 25 May 2020 10:51:54 +0200
-Subject: [PATCH 2/3] update stable ospp profile
-
----
- tests/data/profile_stability/rhel8/ospp.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index bdda39a903..25f7922bf3 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -214,7 +214,7 @@ selections:
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
- - var_sshd_set_keepalive=0
--- var_rekey_limit_size=512M
-+- var_rekey_limit_size=1G
- - var_rekey_limit_time=1hour
- - var_accounts_user_umask=027
- - var_password_pam_difok=4
-
-From 6623ece14b6534164a3b953fd43111cae4a3eeea Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 28 May 2020 09:30:58 +0200
-Subject: [PATCH 3/3] propagate change also into stig profile
-
----
- rhel8/profiles/stig.profile                     | 3 ---
- tests/data/profile_stability/rhel8/stig.profile | 2 +-
- 2 files changed, 1 insertion(+), 4 deletions(-)
-
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index a156857647..2bb81cf9dc 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -44,6 +44,3 @@ selections:
-     - package_rsyslog-gnutls_installed
-     - rsyslog_remote_tls
-     - rsyslog_remote_tls_cacert
--    - sshd_rekey_limit
--    - var_rekey_limit_size=512M
--    - var_rekey_limit_time=1hour
-diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
-index ebef541921..6c4270925f 100644
---- a/tests/data/profile_stability/rhel8/stig.profile
-+++ b/tests/data/profile_stability/rhel8/stig.profile
-@@ -242,7 +242,7 @@ selections:
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
- - var_sshd_set_keepalive=0
--- var_rekey_limit_size=512M
-+- var_rekey_limit_size=1G
- - var_rekey_limit_time=1hour
- - var_accounts_user_umask=027
- - var_password_pam_difok=4
diff --git a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5788.patch b/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5788.patch
deleted file mode 100644
index 8ebfb97..0000000
--- a/SOURCES/scap-security-guide-0.1.51-parametrize-ssh-PR5788.patch
+++ /dev/null
@@ -1,798 +0,0 @@
-From 604f70aa2d0cce64aed5d699178394523969ba37 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 27 May 2020 14:34:50 +0200
-Subject: [PATCH 01/11] add rule, variables, check, remediations
-
----
- .../ssh_client_rekey_limit/ansible/shared.yml |  8 ++++
- .../ssh_client_rekey_limit/bash/shared.sh     |  8 ++++
- .../ssh_client_rekey_limit/oval/shared.xml    | 39 +++++++++++++++++++
- .../crypto/ssh_client_rekey_limit/rule.yml    | 34 ++++++++++++++++
- .../var_ssh_client_rekey_limit_size.var       | 15 +++++++
- .../var_ssh_client_rekey_limit_time.var       | 14 +++++++
- shared/references/cce-redhat-avail.txt        |  1 -
- 7 files changed, 118 insertions(+), 1 deletion(-)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
- create mode 100644 linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
- create mode 100644 linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-new file mode 100644
-index 0000000000..6d2bcbbd44
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-@@ -0,0 +1,8 @@
-+# platform = multi_platform_all                                                                                                                                                                                                                                                                                        [0/453]
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+{{{ ansible_instantiate_variables("var_ssh_client_rekey_limit_size", "var_ssh_client_rekey_limit_time") }}}
-+
-+{{{ ansible_lineinfile(msg='Ensure that rekey limit is set to {{ var_ssh_client_rekey_limit_size }} {{ var_ssh_client_rekey_limit_time }} in /etc/ssh/ssh_config.d/02-rekey-limit.conf', path='/etc/ssh/ssh_config.d/02-rekey-limit.conf', regex='^\s*RekeyLimit.*$', new_line='RekeyLimit {{ var_ssh_client_rekey_limit_size }} {{ var_ssh_client_rekey_limit_time }}', create='yes', state='present') }}}
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
-new file mode 100644
-index 0000000000..43d0971ffc
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
-@@ -0,0 +1,8 @@
-+# platform = multi_platform_all
-+
-+# Include source function library.
-+. /usr/share/scap-security-guide/remediation_functions
-+
-+{{{ bash_instantiate_variables("var_ssh_client_rekey_limit_size", "var_ssh_client_rekey_limit_time") }}}
-+
-+{{{ set_config_file(path="/etc/ssh/ssh_config.d/02-rekey-limit.conf", parameter="RekeyLimit", value='$var_ssh_client_rekey_limit_size $var_ssh_client_rekey_limit_time', create=true, insert_before="", insert_after="", insensitive=false, separator=" ", separator_regex="\s\+", prefix_regex="^\s*") }}}
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
-new file mode 100644
-index 0000000000..2412763e3f
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
-@@ -0,0 +1,39 @@
-+{{% set filepath = "/etc/ssh/ssh_config.d/02-rekey-limit.conf" -%}}
-+
-+
-+
-+  
-+    
-+      {{{ rule_title }}}
-+      {{{- oval_affected(products) }}}
-+      Ensure 'RekeyLimit' is configured with the correct value in '{{{ filepath }}}'
-+    
-+    
-+      {{{- oval_line_in_file_criterion(filepath, "RekeyLimit") }}}
-+    
-+  
-+
-+  
-+     
-+  
-+
-+  
-+     {{{ filepath }}}
-+     
-+     1
-+  
-+
-+  
-+    
-+      ^[\s]*RekeyLimit[\s]+
-+      
-+      [\s]+
-+      
-+      [\s]*$
-+    
-+  
-+
-+  
-+  
-+
-+
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-new file mode 100644
-index 0000000000..a1b85b0ee5
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-@@ -0,0 +1,34 @@
-+documentation_complete: true
-+
-+prodtype: rhel8
-+
-+title: 'Configure session renegotiation for SSH client'
-+
-+description: |-
-+    The RekeyLimit parameter specifies how often
-+    the session key is renegotiated, both in terms of
-+    amount of data that may be transmitted and the time
-+    elapsed. To decrease the default limits, put line
-+    RekeyLimit {{{ sub_var_value("var_ssh_client_rekey_limit_size") }}} {{{ sub_var_value("var_ssh_client_rekey_limit_time") }}} to file /etc/ssh/ssh_config.d/02-rekey-limit.conf.
-+
-+rationale: |-
-+    By decreasing the limit based on the amount of data and enabling
-+    time-based limit, effects of potential attacks against
-+    encryption keys are limited.
-+
-+severity: medium
-+
-+identifiers:
-+    cce@rhel8: 82880-6
-+
-+references:
-+    ospp: FCS_SSHS_EXT.1
-+
-+ocil_clause: 'it is commented out or is not set'
-+
-+ocil: |-
-+    To check if RekeyLimit is set correctly, run the
-+    following command:
-+    
$ sudo grep RekeyLimit /etc/ssh/ssh_config.d/02-rekey-limit.conf

-+    If configured properly, output should be
-+    
RekeyLimit {{{ sub_var_value("var_ssh_client_rekey_limit_size") }}} {{{ sub_var_value("var_ssh_client_rekey_limit_time") }}}

-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-new file mode 100644
-index 0000000000..bcf051fd97
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-@@ -0,0 +1,15 @@
-+documentation_complete: true
-+
-+title: 'SSH client RekeyLimit - size'
-+
-+description: 'Specify the size component of the rekey limit.'
-+
-+type: string
-+
-+operator: equals
-+
-+options:
-+    ssh_client_default: "default"
-+    default: "512M"
-+    "512M": "512M"
-+    "1G": "1G"
-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-new file mode 100644
-index 0000000000..31c76f9ab5
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-@@ -0,0 +1,14 @@
-+documentation_complete: true
-+
-+title: 'SSH client RekeyLimit - size'
-+
-+description: 'Specify the size component of the rekey limit.'
-+
-+type: string
-+
-+operator: equals
-+
-+options:
-+    ssh_client_default: "none"
-+    default: "1h"
-+    "1hour": "1h"
-diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt
-index 45d03a2c1d..e060d2fb1c 100644
---- a/shared/references/cce-redhat-avail.txt
-+++ b/shared/references/cce-redhat-avail.txt
-@@ -1,4 +1,3 @@
--CCE-82880-6
- CCE-82882-2
- CCE-82883-0
- CCE-82888-9
-
-From a0d54462b9a1e65de3598d7fc262f61a8e3a06ea Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 27 May 2020 14:35:24 +0200
-Subject: [PATCH 02/11] add tests
-
----
- .../crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh      | 4 ++++
- .../crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh      | 4 ++++
- .../crypto/ssh_client_rekey_limit/tests/no_line.fail.sh       | 3 +++
- .../integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh  | 4 ++++
- 4 files changed, 15 insertions(+)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-new file mode 100644
-index 0000000000..2ac0bbf350
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 812M 1h" >> /etc/ssh/sshd_config
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-new file mode 100644
-index 0000000000..fec859fe05
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 512M 2h" >> /etc/ssh/sshd_config
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-new file mode 100644
-index 0000000000..a6cd10163f
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-@@ -0,0 +1,3 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-new file mode 100644
-index 0000000000..a6a2ba7adf
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-@@ -0,0 +1,4 @@
-+# platform = multi_platform_all
-+
-+sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/sshd_config
-
-From 6ce9e9d55eab07f1c2a3a8d0b28f104d0b5992da Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 27 May 2020 14:35:43 +0200
-Subject: [PATCH 03/11] add rule to rhel8 ospp, update stable profiles
-
----
- rhel8/profiles/ospp.profile                     | 5 +++++
- tests/data/profile_stability/rhel8/ospp.profile | 3 +++
- tests/data/profile_stability/rhel8/stig.profile | 3 +++
- 3 files changed, 11 insertions(+)
-
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index 0dca8350f9..07d32b814d 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -410,3 +410,8 @@ selections:
- 
-     # Prevent Kerberos use by system daemons
-     - kerberos_disable_no_keytab
-+
-+    # set ssh client rekey limit
-+    - ssh_client_rekey_limit
-+    - var_ssh_client_rekey_limit_size=1G
-+    - var_ssh_client_rekey_limit_time=1hour
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index 25f7922bf3..b0d7672c36 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -240,4 +240,7 @@ selections:
- - grub2_vsyscall_argument.severity=info
- - sysctl_user_max_user_namespaces.role=unscored
- - sysctl_user_max_user_namespaces.severity=info
-+- ssh_client_rekey_limit
-+- var_ssh_client_rekey_limit_size=1G
-+- var_ssh_client_rekey_limit_time=1hour
- title: Protection Profile for General Purpose Operating Systems
-diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
-index 6c4270925f..330ecc7e1e 100644
---- a/tests/data/profile_stability/rhel8/stig.profile
-+++ b/tests/data/profile_stability/rhel8/stig.profile
-@@ -269,4 +269,7 @@ selections:
- - grub2_vsyscall_argument.severity=info
- - sysctl_user_max_user_namespaces.role=unscored
- - sysctl_user_max_user_namespaces.severity=info
-+- ssh_client_rekey_limit
-+- var_ssh_client_rekey_limit_size=1G
-+- var_ssh_client_rekey_limit_time=1hour
- title: '[DRAFT] DISA STIG for Red Hat Enterprise Linux 8'
-
-From 763a79e337eecb24c640d1ac189edf02d20e53ad Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 28 May 2020 14:25:41 +0200
-Subject: [PATCH 04/11] improve description of variables
-
----
- .../crypto/var_ssh_client_rekey_limit_size.var       | 10 ++++++++--
- .../crypto/var_ssh_client_rekey_limit_time.var       | 12 +++++++++---
- 2 files changed, 17 insertions(+), 5 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-index bcf051fd97..4e20104cba 100644
---- a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-@@ -2,14 +2,20 @@ documentation_complete: true
- 
- title: 'SSH client RekeyLimit - size'
- 
--description: 'Specify the size component of the rekey limit.'
-+description: |-
-+    Specify the size component of the rekey limit. This limit signifies amount
-+    of data. After this amount of data is transferred through the connection,
-+    the session key is renegotiated. The number is followed by K, M or G for
-+    kilobytes, megabytes or gigabytes. Note that the RekeyLimit can be also
-+    configured according to ellabsed time.
-+
-+interactive: true
- 
- type: string
- 
- operator: equals
- 
- options:
--    ssh_client_default: "default"
-     default: "512M"
-     "512M": "512M"
-     "1G": "1G"
-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-index 31c76f9ab5..6143a5448c 100644
---- a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-@@ -1,14 +1,20 @@
- documentation_complete: true
- 
--title: 'SSH client RekeyLimit - size'
-+title: 'SSH client RekeyLimit - time'
- 
--description: 'Specify the size component of the rekey limit.'
-+description: |-
-+    Specify the time component of the rekey limit. This limit signifies amount
-+    of data. The session key is renegotiated after the defined amount of time
-+    passes. The number is followed by units such as H or M for hours or minutes.
-+    Note that the RekeyLimit can be also configured according to amount of
-+    transfered data.
-+
-+interactive: true
- 
- type: string
- 
- operator: equals
- 
- options:
--    ssh_client_default: "none"
-     default: "1h"
-     "1hour": "1h"
-
-From 0800fcaff037a1b012b75e59d6771f5e7763e1de Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 28 May 2020 14:26:12 +0200
-Subject: [PATCH 05/11] fix tests and ansible
-
----
- .../crypto/ssh_client_rekey_limit/ansible/shared.yml         | 2 +-
- .../crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh     | 4 ++--
- .../crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh     | 4 ++--
- .../crypto/ssh_client_rekey_limit/tests/no_line.fail.sh      | 2 +-
- .../integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh | 5 +++--
- 5 files changed, 9 insertions(+), 8 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-index 6d2bcbbd44..bb6544a0a0 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-@@ -1,4 +1,4 @@
--# platform = multi_platform_all                                                                                                                                                                                                                                                                                        [0/453]
-+# platform = multi_platform_all
- # reboot = false
- # strategy = configure
- # complexity = low
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-index 2ac0bbf350..22c465b08f 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-@@ -1,4 +1,4 @@
- # platform = multi_platform_all
- 
--sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
--echo "RekeyLimit 812M 1h" >> /etc/ssh/sshd_config
-+
-+echo "RekeyLimit 812M 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-index fec859fe05..0dc621b1da 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-@@ -1,4 +1,4 @@
- # platform = multi_platform_all
- 
--sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
--echo "RekeyLimit 512M 2h" >> /etc/ssh/sshd_config
-+
-+echo "RekeyLimit 512M 2h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-index a6cd10163f..f6abf711da 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-@@ -1,3 +1,3 @@
- # platform = multi_platform_all
- 
--sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
-+echo "some line" > /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-index a6a2ba7adf..e64e4191bc 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-@@ -1,4 +1,5 @@
- # platform = multi_platform_all
- 
--sed -e '/RekeyLimit/d' /etc/ssh/sshd_config
--echo "RekeyLimit 512M 1h" >> /etc/ssh/sshd_config
-+
-+rm -f /etc/ssh/ssh_config.d/02-rekey-limit.conf
-+echo "RekeyLimit 1G 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-
-From 9451e6d91c9975a3e9ecd4c627cbb0f9afce4c92 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 1 Jun 2020 14:29:47 +0200
-Subject: [PATCH 06/11] fix test to use default value, remove rule from stig
-
----
- .../integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh    | 2 +-
- rhel8/profiles/stig.profile                                     | 1 +
- tests/data/profile_stability/rhel8/stig.profile                 | 1 -
- 3 files changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-index e64e4191bc..89d7069687 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-@@ -2,4 +2,4 @@
- 
- 
- rm -f /etc/ssh/ssh_config.d/02-rekey-limit.conf
--echo "RekeyLimit 1G 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index 2bb81cf9dc..8f12852e26 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -44,3 +44,4 @@ selections:
-     - package_rsyslog-gnutls_installed
-     - rsyslog_remote_tls
-     - rsyslog_remote_tls_cacert
-+    - "!ssh_client_rekey_limit"
-diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
-index 330ecc7e1e..9b164eb5c2 100644
---- a/tests/data/profile_stability/rhel8/stig.profile
-+++ b/tests/data/profile_stability/rhel8/stig.profile
-@@ -269,7 +269,6 @@ selections:
- - grub2_vsyscall_argument.severity=info
- - sysctl_user_max_user_namespaces.role=unscored
- - sysctl_user_max_user_namespaces.severity=info
--- ssh_client_rekey_limit
- - var_ssh_client_rekey_limit_size=1G
- - var_ssh_client_rekey_limit_time=1hour
- title: '[DRAFT] DISA STIG for Red Hat Enterprise Linux 8'
-
-From bd47b1145f17c97de719c887db6146d5e7b59616 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 3 Jun 2020 12:38:19 +0200
-Subject: [PATCH 07/11] rewrite oval to check for multiple locations
-
----
- .../ssh_client_rekey_limit/oval/shared.xml    | 42 ++++++++++++-------
- 1 file changed, 26 insertions(+), 16 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
-index 2412763e3f..41fa0497ae 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/oval/shared.xml
-@@ -1,28 +1,17 @@
--{{% set filepath = "/etc/ssh/ssh_config.d/02-rekey-limit.conf" -%}}
--
- 
- 
-   
-     
-       {{{ rule_title }}}
-       {{{- oval_affected(products) }}}
--      Ensure 'RekeyLimit' is configured with the correct value in '{{{ filepath }}}'
-+      Ensure 'RekeyLimit' is configured with the correct value in /etc/ssh/ssh_config and /etc/ssh/ssh_config.d/*.conf
-     
--    
--      {{{- oval_line_in_file_criterion(filepath, "RekeyLimit") }}}
-+    
-+      
-+      
-     
-   
- 
--  
--     
--  
--
--  
--     {{{ filepath }}}
--     
--     1
--  
--
-   
-     
-       ^[\s]*RekeyLimit[\s]+
-@@ -35,5 +24,26 @@
- 
-   
-   
--
- 
-+
-+  
-+     
-+  
-+
-+  
-+     /etc/ssh/ssh_config
-+     ^[\s]*RekeyLimit.*$
-+     1
-+  
-+
-+  
-+     
-+  
-+
-+  
-+     ^/etc/ssh/ssh_config\.d/.*\.conf$
-+     
-+     1
-+  
-+
-+
-
-From c090301ab1cf43a83994b654ccb2ab0b967d05b4 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 4 Jun 2020 08:24:54 +0200
-Subject: [PATCH 08/11] reqrite remediations
-
----
- .../ssh_client_rekey_limit/ansible/shared.yml    | 16 ++++++++++++++++
- .../crypto/ssh_client_rekey_limit/bash/shared.sh | 13 +++++++++++++
- 2 files changed, 29 insertions(+)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-index bb6544a0a0..36de503806 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/ansible/shared.yml
-@@ -5,4 +5,20 @@
- # disruption = low
- {{{ ansible_instantiate_variables("var_ssh_client_rekey_limit_size", "var_ssh_client_rekey_limit_time") }}}
- 
-+{{{ ansible_lineinfile(msg='Ensure RekeyLimit is not configured in /etc/ssh/ssh_config', path='/etc/ssh/ssh_config', regex='^\s*RekeyLimit.*$', create='no', state='absent') }}}
-+
-+- name: Collect all include config files for ssh client which configure RekeyLimit
-+  find:
-+    paths: "/etc/ssh/ssh_config.d/"
-+    contains: '^[\s]*RekeyLimit.*$'
-+    patterns: "*.config"
-+  register: ssh_config_include_files
-+
-+- name: Remove all occurences of RekeyLimit configuration from include config files of ssh client
-+  lineinfile:
-+    path: "{{ item }}"
-+    regexp: '^[\s]*RekeyLimit.*$'
-+    state: "absent"
-+  loop: "{{ ssh_config_include_files.files }}"
-+
- {{{ ansible_lineinfile(msg='Ensure that rekey limit is set to {{ var_ssh_client_rekey_limit_size }} {{ var_ssh_client_rekey_limit_time }} in /etc/ssh/ssh_config.d/02-rekey-limit.conf', path='/etc/ssh/ssh_config.d/02-rekey-limit.conf', regex='^\s*RekeyLimit.*$', new_line='RekeyLimit {{ var_ssh_client_rekey_limit_size }} {{ var_ssh_client_rekey_limit_time }}', create='yes', state='present') }}}
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
-index 43d0971ffc..99f6f63c92 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/bash/shared.sh
-@@ -5,4 +5,17 @@
- 
- {{{ bash_instantiate_variables("var_ssh_client_rekey_limit_size", "var_ssh_client_rekey_limit_time") }}}
- 
-+main_config="/etc/ssh/ssh_config"
-+include_directory="/etc/ssh/ssh_config.d"
-+
-+if grep -q '^[\s]*RekeyLimit.*$' "$main_config"; then
-+  sed -i '/^[\s]*RekeyLimit.*/d' "$main_config"
-+fi
-+
-+for file in "$include_directory"/*.conf; do
-+  if grep -q '^[\s]*RekeyLimit.*$' "$file"; then
-+    sed -i '/^[\s]*RekeyLimit.*/d' "$file"
-+  fi
-+done
-+
- {{{ set_config_file(path="/etc/ssh/ssh_config.d/02-rekey-limit.conf", parameter="RekeyLimit", value='$var_ssh_client_rekey_limit_size $var_ssh_client_rekey_limit_time', create=true, insert_before="", insert_after="", insensitive=false, separator=" ", separator_regex="\s\+", prefix_regex="^\s*") }}}
-
-From 22b8cb067cfc9d6d48065233973d1dba223ef5a4 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 4 Jun 2020 08:25:14 +0200
-Subject: [PATCH 09/11] add more tests
-
----
- .../tests/bad_main_config_good_include_config.fail.sh         | 4 ++++
- .../ssh_client_rekey_limit/tests/line_in_main_config.fail.sh  | 4 ++++
- .../tests/ok_different_config_file.pass.sh                    | 3 +++
- 3 files changed, 11 insertions(+)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/line_in_main_config.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok_different_config_file.pass.sh
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
-new file mode 100644
-index 0000000000..90314712af
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
-@@ -0,0 +1,4 @@
-+#!/bin/basdh
-+
-+echo "RekeyLimit 2G 1h" >> /etc/ssh/ssh_config
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/line_in_main_config.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/line_in_main_config.fail.sh
-new file mode 100644
-index 0000000000..9ba20b0290
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/line_in_main_config.fail.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+rm -rf /etc/ssh/ssh_config.d/*
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/ssh_config
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok_different_config_file.pass.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok_different_config_file.pass.sh
-new file mode 100644
-index 0000000000..f725f6936f
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok_different_config_file.pass.sh
-@@ -0,0 +1,3 @@
-+#!/bin/bash
-+
-+echo "RekeyLimit 512M 1h" >> /etc/ssh/ssh_config.d/05-some-file.conf
-
-From 78904a0cc4461cc26786289095fd76e8ce15843e Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 4 Jun 2020 08:25:29 +0200
-Subject: [PATCH 10/11] extend description and ocil
-
----
- .../crypto/ssh_client_rekey_limit/rule.yml    | 19 ++++++++++++++-----
- 1 file changed, 14 insertions(+), 5 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-index a1b85b0ee5..76f5f84090 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-@@ -10,6 +10,12 @@ description: |-
-     amount of data that may be transmitted and the time
-     elapsed. To decrease the default limits, put line
-     RekeyLimit {{{ sub_var_value("var_ssh_client_rekey_limit_size") }}} {{{ sub_var_value("var_ssh_client_rekey_limit_time") }}} to file /etc/ssh/ssh_config.d/02-rekey-limit.conf.
-+    Make sure that there is no other RekeyLimit configuration preceding
-+    the include directive in the main config file
-+    /etc/ssh/ssh_config. Check also other files in
-+    /etc/ssh/ssh_config.d directory. Files are processed according to
-+    their names. Make sure that there is no file processed before
-+    02-rekey-limit.conf containing definition of RekeyLimit.
- 
- rationale: |-
-     By decreasing the limit based on the amount of data and enabling
-@@ -27,8 +33,11 @@ references:
- ocil_clause: 'it is commented out or is not set'
- 
- ocil: |-
--    To check if RekeyLimit is set correctly, run the
--    following command:
--    
$ sudo grep RekeyLimit /etc/ssh/ssh_config.d/02-rekey-limit.conf

--    If configured properly, output should be
--    
RekeyLimit {{{ sub_var_value("var_ssh_client_rekey_limit_size") }}} {{{ sub_var_value("var_ssh_client_rekey_limit_time") }}}

-+    To check if RekeyLimit is set correctly, run the following command: 
$
-+    sudo grep RekeyLimit /etc/ssh/ssh_config.d/*.conf
 If configured
-+    properly, output should be 
/etc/ssh/ssh_config.d/02-rekey-limit.conf:
-+    RekeyLimit {{{ sub_var_value("var_ssh_client_rekey_limit_size") }}} {{{
-+    sub_var_value("var_ssh_client_rekey_limit_time") }}}
 Check also the
-+    main configuration file with the following command: 
sudo grep
-+    RekeyLimit /etc/ssh/ssh_config
 The command should not return any
-+    output.
-
-From 854d5c9d1e1a44e97fe59aeaace687adcff620d5 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 8 Jun 2020 11:44:44 +0200
-Subject: [PATCH 11/11] fix typos and wording
-
----
- .../integrity/crypto/ssh_client_rekey_limit/rule.yml     | 5 +++--
- .../tests/bad_main_config_good_include_config.fail.sh    | 2 +-
- .../crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh | 1 +
- .../crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh | 1 +
- .../crypto/ssh_client_rekey_limit/tests/no_line.fail.sh  | 1 +
- .../crypto/ssh_client_rekey_limit/tests/ok.pass.sh       | 1 +
- .../integrity/crypto/var_ssh_client_rekey_limit_size.var | 2 +-
- .../integrity/crypto/var_ssh_client_rekey_limit_time.var | 9 ++++-----
- 8 files changed, 13 insertions(+), 9 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-index 76f5f84090..b054d9d221 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/rule.yml
-@@ -14,8 +14,9 @@ description: |-
-     the include directive in the main config file
-     /etc/ssh/ssh_config. Check also other files in
-     /etc/ssh/ssh_config.d directory. Files are processed according to
--    their names. Make sure that there is no file processed before
--    02-rekey-limit.conf containing definition of RekeyLimit.
-+    lexicographical order of file names. Make sure that there is no file
-+    processed before 02-rekey-limit.conf containing definition of
-+    RekeyLimit.
- 
- rationale: |-
-     By decreasing the limit based on the amount of data and enabling
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
-index 90314712af..58befb0107 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_main_config_good_include_config.fail.sh
-@@ -1,4 +1,4 @@
--#!/bin/basdh
-+#!/bin/bash
- 
- echo "RekeyLimit 2G 1h" >> /etc/ssh/ssh_config
- echo "RekeyLimit 512M 1h" >> /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-index 22c465b08f..1803c26629 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_size.fail.sh
-@@ -1,3 +1,4 @@
-+#!/bin/bash
- # platform = multi_platform_all
- 
- 
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-index 0dc621b1da..2c9e839255 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/bad_time.fail.sh
-@@ -1,3 +1,4 @@
-+#!/bin/bash
- # platform = multi_platform_all
- 
- 
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-index f6abf711da..7de108eafd 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/no_line.fail.sh
-@@ -1,3 +1,4 @@
-+#!/bin/bash
- # platform = multi_platform_all
- 
- echo "some line" > /etc/ssh/ssh_config.d/02-rekey-limit.conf
-diff --git a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-index 89d7069687..4c047ed179 100644
---- a/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/ssh_client_rekey_limit/tests/ok.pass.sh
-@@ -1,3 +1,4 @@
-+#!/bin/bash
- # platform = multi_platform_all
- 
- 
-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-index 4e20104cba..c8dd8ef10e 100644
---- a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_size.var
-@@ -7,7 +7,7 @@ description: |-
-     of data. After this amount of data is transferred through the connection,
-     the session key is renegotiated. The number is followed by K, M or G for
-     kilobytes, megabytes or gigabytes. Note that the RekeyLimit can be also
--    configured according to ellabsed time.
-+    configured according to elapsed time.
- 
- interactive: true
- 
-diff --git a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-index 6143a5448c..6223e8e38f 100644
---- a/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-+++ b/linux_os/guide/system/software/integrity/crypto/var_ssh_client_rekey_limit_time.var
-@@ -3,11 +3,10 @@ documentation_complete: true
- title: 'SSH client RekeyLimit - time'
- 
- description: |-
--    Specify the time component of the rekey limit. This limit signifies amount
--    of data. The session key is renegotiated after the defined amount of time
--    passes. The number is followed by units such as H or M for hours or minutes.
--    Note that the RekeyLimit can be also configured according to amount of
--    transfered data.
-+    Specify the time component of the rekey limit. The session key is
-+    renegotiated after the defined amount of time passes. The number is followed
-+    by units such as H or M for hours or minutes. Note that the RekeyLimit can
-+    be also configured according to amount of transfered data.
- 
- interactive: true
- 
diff --git a/SOURCES/scap-security-guide-0.1.51-remove_grub_doc_links-PR_5851.patch b/SOURCES/scap-security-guide-0.1.51-remove_grub_doc_links-PR_5851.patch
deleted file mode 100644
index d80f19e..0000000
--- a/SOURCES/scap-security-guide-0.1.51-remove_grub_doc_links-PR_5851.patch
+++ /dev/null
@@ -1,65 +0,0 @@
-From 713bc3b17929d0c73b7898f42fe7935806a3bfff Mon Sep 17 00:00:00 2001
-From: Gabe 
-Date: Tue, 16 Jun 2020 16:04:10 -0600
-Subject: [PATCH] Remove grub documentation links from RHEL7 rationale
-
----
- .../system/bootloader-grub2/grub2_admin_username/rule.yml  | 7 -------
- .../guide/system/bootloader-grub2/grub2_password/rule.yml  | 7 -------
- .../system/bootloader-grub2/grub2_uefi_password/rule.yml   | 7 -------
- 3 files changed, 21 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml
-index 2042a17806..63a6a7a83c 100644
---- a/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml
-+++ b/linux_os/guide/system/bootloader-grub2/grub2_admin_username/rule.yml
-@@ -24,13 +24,6 @@ description: |-
- 
- rationale: |-
-     Having a non-default grub superuser username makes password-guessing attacks less effective.
--    {{% if product == "rhel7" %}}
--    For more information on how to configure the grub2 superuser account and password,
--    please refer to
--    
    
--    
  • {{{ weblink(link="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Protecting_GRUB_2_with_a_Password.html") }}}
    • .
--    

--    {{% endif %}}
- 
- severity: low
- 
-diff --git a/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml
-index 00cec58c77..985b8727d7 100644
---- a/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml
-+++ b/linux_os/guide/system/bootloader-grub2/grub2_password/rule.yml
-@@ -23,13 +23,6 @@ rationale: |-
-     users with physical access cannot trivially alter
-     important bootloader settings. These include which kernel to use,
-     and whether to enter single-user mode.
--    {{% if product == "rhel7" %}}
--    For more information on how to configure the grub2 superuser account and password,
--    please refer to
--    
    
--    
  • {{{ weblink(link="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Protecting_GRUB_2_with_a_Password.html") }}}
    • .
--    

--    {{% endif %}}
- 
- severity: high
- 
-diff --git a/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml
-index 954d6f21d0..3ce5a2df13 100644
---- a/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml
-+++ b/linux_os/guide/system/bootloader-grub2/grub2_uefi_password/rule.yml
-@@ -23,13 +23,6 @@ rationale: |-
-     users with physical access cannot trivially alter
-     important bootloader settings. These include which kernel to use,
-     and whether to enter single-user mode.
--    {{% if product == "rhel7" %}}
--    For more information on how to configure the grub2 superuser account and password,
--    please refer to
--    
    
--    
  • {{{ weblink(link="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Protecting_GRUB_2_with_a_Password.html") }}}
    • .
--    

--    {{% endif %}}
- 
- severity: medium
- 
diff --git a/SOURCES/scap-security-guide-0.1.51-update_rhel8_cis_PR_5771.patch b/SOURCES/scap-security-guide-0.1.51-update_rhel8_cis_PR_5771.patch
deleted file mode 100644
index 4b69221..0000000
--- a/SOURCES/scap-security-guide-0.1.51-update_rhel8_cis_PR_5771.patch
+++ /dev/null
@@ -1,1216 +0,0 @@
-From 29eb0f64454f275085015b481a59184e73ebe7f6 Mon Sep 17 00:00:00 2001
-From: Shawn Wells 
-Date: Sun, 29 Mar 2020 00:58:02 -0400
-Subject: [PATCH 01/20] update CIS RHEL8 profile
-
----
- .../service_crond_enabled/rule.yml            |   2 +-
- .../r_services/no_rsh_trust_files/rule.yml    |   8 +-
- .../rule.yml                                  |   2 +-
- .../account_unique_name/rule.yml              |  11 +-
- .../accounts_maximum_age_login_defs/rule.yml  |   2 +-
- .../accounts_minimum_age_login_defs/rule.yml  |   1 +
- .../rule.yml                                  |   1 +
- .../var_accounts_maximum_age_login_defs.var   |   1 +
- .../password_storage/no_netrc_files/rule.yml  |   4 +-
- .../accounts_no_uid_except_zero/rule.yml      |   2 +-
- .../no_direct_root_logins/rule.yml            |   2 +-
- .../rule.yml                                  |   1 +
- .../accounts-session/accounts_tmout/rule.yml  |   1 +
- .../rule.yml                                  |   1 +
- .../rule.yml                                  |   1 +
- .../file_permissions_home_dirs/rule.yml       |   4 +-
- .../rsyslog_files_permissions/rule.yml        |   2 +-
- .../ensure_logrotate_activated/rule.yml       |   1 +
- .../package_rsyslog_installed/rule.yml        |   2 +-
- .../rsyslog_nolisten/rule.yml                 |   2 +
- .../rsyslog_remote_loghost/rule.yml           |   4 +-
- .../logging/service_rsyslog_enabled/rule.yml  |   2 +-
- rhel8/profiles/cis.profile                    | 141 ++++++++++++------
- shared/references/cce-redhat-avail.txt        |   2 -
- 24 files changed, 137 insertions(+), 63 deletions(-)
-
-diff --git a/linux_os/guide/services/cron_and_at/service_crond_enabled/rule.yml b/linux_os/guide/services/cron_and_at/service_crond_enabled/rule.yml
-index a1f82cf5c9..09d1a92a55 100644
---- a/linux_os/guide/services/cron_and_at/service_crond_enabled/rule.yml
-+++ b/linux_os/guide/services/cron_and_at/service_crond_enabled/rule.yml
-@@ -24,7 +24,7 @@ identifiers:
- references:
-     stigid@rhel6: "000224"
-     srg@rhel6: SRG-OS-999999
--    cis: 5.1.1
-+    cis@rhel8: 5.1.1
-     hipaa: 164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii)
-     nist: CM-6(a)
-     nist-csf: PR.IP-1,PR.PT-3
-diff --git a/linux_os/guide/services/obsolete/r_services/no_rsh_trust_files/rule.yml b/linux_os/guide/services/obsolete/r_services/no_rsh_trust_files/rule.yml
-index 2ccf4127b7..ec2fa6c012 100644
---- a/linux_os/guide/services/obsolete/r_services/no_rsh_trust_files/rule.yml
-+++ b/linux_os/guide/services/obsolete/r_services/no_rsh_trust_files/rule.yml
-@@ -12,9 +12,9 @@ description: |-
-     
$ rm ~/.rhosts

- 
- rationale: |-
--    Trust files are convenient, but when
--    used in conjunction with the R-services, they can allow
--    unauthenticated access to a system.
-+    This action is only meaningful if .rhosts support is permitted
-+    through PAM. Trust files are convenient, but when used in conjunction with
-+    the R-services, they can allow unauthenticated access to a system.
- 
- severity: high
- 
-@@ -26,7 +26,7 @@ identifiers:
- references:
-     stigid@rhel6: "000019"
-     srg@rhel6: SRG-OS-000248
--    cis: 6.2.14
-+    cis@rhel8: 6.2.13
-     disa: "1436"
-     hipaa: 164.308(a)(4)(i),164.308(b)(1),164.308(b)(3),164.310(b),164.312(e)(1),164.312(e)(2)(ii)
-     nist: CM-7(a),CM-7(b),CM-6(a)
-diff --git a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_systemauth/rule.yml b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_systemauth/rule.yml
-index fff30d70c7..7a1538392a 100644
---- a/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_systemauth/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-pam/set_password_hashing_algorithm/set_password_hashing_algorithm_systemauth/rule.yml
-@@ -43,7 +43,7 @@ references:
-     stigid@rhel6: "000062"
-     srg@rhel6: SRG-OS-000120
-     disa@rhel6: '803'
--    cis: 6.3.1
-+    cis@rhel8: 5.4.4
-     cjis: 5.6.2.2
-     cui: 3.13.11
-     disa: "196"
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-index 2cdafc0609..35652a410b 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-@@ -2,9 +2,15 @@ documentation_complete: true
- 
- title: 'Ensure All Accounts on the System Have Unique Names'
- 
--description: 'Change usernames, or delete accounts, so each has a unique name.'
-+description: |-
-+    Although the useradd utility prevents creation of duplicate user
-+    names, it is possible for a malicious administrator to manually edit the
-+    /etc/passwd file and change the user name.
- 
--rationale: 'Unique usernames allow for accountability on the system.'
-+rationale: |-
-+    If a user is assigned a duplicate user name, the new user will be able to
-+    create and have access to files with the first UID for that username as
-+    defined in /etc/passwd.
- 
- severity: medium
- 
-@@ -19,6 +25,7 @@ references:
-     cjis: 5.5.2
-     disa: 770,804
-     pcidss: Req-8.1.1
-+    cis@rhel8: 6.2.17
- 
- ocil_clause: 'a line is returned'
- 
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml
-index af1ea13d8f..c2c4aa11bc 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_maximum_age_login_defs/rule.yml
-@@ -34,7 +34,7 @@ references:
-     stigid@rhel6: "000053"
-     srg@rhel6: SRG-OS-000076
-     disa@rhel6: '180'
--    cis: 5.4.1.1
-+    cis@rhel8: 5.5.1.1
-     cjis: 5.6.2.1
-     cui: 3.5.6
-     disa: "199"
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml
-index 2de12efb3e..6147d672a4 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_minimum_age_login_defs/rule.yml
-@@ -44,6 +44,7 @@ references:
-     cobit5: DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10
-     iso27001-2013: A.18.1.4,A.7.1.1,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.2,A.9.4.3
-     cis-csc: 1,12,15,16,5
-+    cis@rhel8: 5.5.1.2
- 
- ocil_clause: 'it is not equal to or greater than the required value'
- 
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_warn_age_login_defs/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_warn_age_login_defs/rule.yml
-index 3a5c00708d..2a1005bd20 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_warn_age_login_defs/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/accounts_password_warn_age_login_defs/rule.yml
-@@ -33,6 +33,7 @@ references:
-     cobit5: DSS01.03,DSS03.05,DSS05.04,DSS05.05,DSS05.07,DSS05.10,DSS06.03,DSS06.10
-     iso27001-2013: A.12.4.1,A.12.4.3,A.18.1.4,A.6.1.2,A.7.1.1,A.9.1.2,A.9.2.1,A.9.2.2,A.9.2.3,A.9.2.4,A.9.2.6,A.9.3.1,A.9.4.1,A.9.4.2,A.9.4.3,A.9.4.4,A.9.4.5
-     cis-csc: 1,12,13,14,15,16,18,3,5,7,8
-+    cis@rhel8: 5.5.1.3
- 
- ocil_clause: 'it is not set to the required value'
- 
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/var_accounts_maximum_age_login_defs.var b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/var_accounts_maximum_age_login_defs.var
-index 731f8f475f..11eb238c5d 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/var_accounts_maximum_age_login_defs.var
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_expiration/var_accounts_maximum_age_login_defs.var
-@@ -9,6 +9,7 @@ type: number
- interactive: false
- 
- options:
-+    365: 365
-     120: 120
-     180: 180
-     60: 60
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-index 01454a7274..8547893201 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_netrc_files/rule.yml
-@@ -11,8 +11,7 @@ description: |-
- 
- rationale: |-
-     Unencrypted passwords for remote FTP servers may be stored in .netrc
--    files. DoD policy requires passwords be encrypted in storage and not used
--    in access scripts.
-+    files. 
- 
- severity: medium
- 
-@@ -24,6 +23,7 @@ identifiers:
- references:
-     stigid@rhel6: "000347"
-     srg@rhel6: SRG-OS-000073
-+    cis@rhel8: 6.2.11
-     disa: "196"
-     nist: IA-5(h),IA-5(1)(c),CM-6(a),IA-5(7)
-     nist-csf: PR.AC-1,PR.AC-4,PR.AC-6,PR.AC-7,PR.PT-3
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml
-index 0b61daf925..14f9140687 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/accounts_no_uid_except_zero/rule.yml
-@@ -31,7 +31,7 @@ references:
-     stigid@ol7: "020310"
-     stigid@rhel6: "000032"
-     srg@rhel6: SRG-OS-999999
--    cis: 6.2.5
-+    cis@rhel8: 6.2.6
-     cui: 3.1.1,3.1.5
-     disa: "366"
-     nist: IA-2,AC-6(5),IA-4(b)
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/rule.yml
-index 1d08bde4d9..9e00f3aad6 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/no_direct_root_logins/rule.yml
-@@ -33,7 +33,7 @@ identifiers:
-     cce@ocp4: 82698-2
- 
- references:
--    cis: "5.5"
-+    cis@rhel8: "5.6"
-     cui: 3.1.1,3.1.6
-     hipaa: 164.308(a)(1)(ii)(B),164.308(a)(7)(i),164.308(a)(7)(ii)(A),164.310(a)(1),164.310(a)(2)(i),164.310(a)(2)(ii),164.310(a)(2)(iii),164.310(b),164.310(c),164.310(d)(1),164.310(d)(2)(iii)
-     nist: IA-2,CM-6(a)
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/securetty_root_login_console_only/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/securetty_root_login_console_only/rule.yml
-index ae8ba133b7..0c26ac3240 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/root_logins/securetty_root_login_console_only/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/root_logins/securetty_root_login_console_only/rule.yml
-@@ -35,6 +35,7 @@ references:
-     cobit5: APO01.06,DSS05.04,DSS05.07,DSS06.02
-     iso27001-2013: A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5
-     cis-csc: 12,13,14,15,16,18,3,5
-+    cis@rhel8: "5.6"
-     srg: SRG-OS-000324-GPOS-00125
- 
- ocil_clause: 'root login over virtual console devices is permitted'
-diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml
-index 787f2264de..f09006b72b 100644
---- a/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/accounts_tmout/rule.yml
-@@ -38,6 +38,7 @@ references:
-     cobit5: DSS05.04,DSS05.10,DSS06.10
-     iso27001-2013: A.18.1.4,A.9.2.1,A.9.2.4,A.9.3.1,A.9.4.2,A.9.4.3
-     cis-csc: 1,12,15,16
-+    cis@rhel8: 5.5.3
-     anssi: NT28(R29)
- 
- ocil_clause: 'value of TMOUT is not less than or equal to expected setting'
-diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-index e7e9a751a4..bedf3a0b19 100644
---- a/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/accounts_user_interactive_home_directory_exists/rule.yml
-@@ -27,6 +27,7 @@ references:
-     disa: "366"
-     srg: SRG-OS-000480-GPOS-00227
-     stigid@rhel7: "020620"
-+    cis@rhel8: 6.2.20
- 
- ocil_clause: 'users home directory does not exist'
- 
-diff --git a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-index d58884235e..1c5ac8d099 100644
---- a/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/file_groupownership_home_directories/rule.yml
-@@ -26,6 +26,7 @@ references:
-     disa: "366"
-     srg: SRG-OS-000480-GPOS-00227
-     stigid@rhel7: "020650"
-+    cis@rhel8: 6.2.8
- 
- ocil_clause: 'the group ownership is incorrect'
- 
-diff --git a/linux_os/guide/system/accounts/accounts-session/file_permissions_home_dirs/rule.yml b/linux_os/guide/system/accounts/accounts-session/file_permissions_home_dirs/rule.yml
-index 8812f9d123..27c190b5b1 100644
---- a/linux_os/guide/system/accounts/accounts-session/file_permissions_home_dirs/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/file_permissions_home_dirs/rule.yml
-@@ -22,11 +22,12 @@ rationale: |-
-     to one another's home directories, this can be provided using
-     groups or ACLs.
- 
--severity: unknown
-+severity: medium
- 
- identifiers:
-     cce@rhel6: 26981-1
-     cce@rhel7: 80201-7
-+    cce@rhel8: 84274-0
- 
- references:
-     disa: "225"
-@@ -37,6 +38,7 @@ references:
-     cobit5: APO01.06,DSS05.04,DSS05.07,DSS06.02
-     iso27001-2013: A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.13.1.1,A.13.1.3,A.13.2.1,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5
-     cis-csc: 12,13,14,15,16,18,3,5
-+    cis@rhel8: 6.2.7
- 
- ocil_clause: 'the user home directory is group-writable or world-readable'
- 
-diff --git a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/rule.yml b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/rule.yml
-index 4c1e69020b..aa6e0905ae 100644
---- a/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/rule.yml
-+++ b/linux_os/guide/system/logging/ensure_rsyslog_log_file_configuration/rsyslog_files_permissions/rule.yml
-@@ -31,7 +31,7 @@ references:
-     anssi: NT28(R36)
-     stigid@rhel6: "000135"
-     srg@rhel6: SRG-OS-000206
--    cis: 4.2.1.3
-+    cis@rhel8: 4.2.1.3
-     disa: "1314"
-     nist: CM-6(a),AC-6(1)
-     pcidss: Req-10.5.1,Req-10.5.2
-diff --git a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-index def9566692..2c41a3b9ef 100644
---- a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-+++ b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-@@ -35,6 +35,7 @@ references:
-     cobit5: APO11.04,BAI03.05,DSS05.04,DSS05.07,MEA02.01
-     iso27001-2013: A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1
-     cis-csc: 1,14,15,16,3,5,6
-+    cis@rhel8: 4.3
-     anssi: NT28(R43),NT12(R18)
- 
- ocil_clause: 'logrotate is not configured to run daily'
-diff --git a/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml b/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml
-index 9f00dd9704..00fecf8a3c 100644
---- a/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml
-+++ b/linux_os/guide/system/logging/package_rsyslog_installed/rule.yml
-@@ -18,7 +18,7 @@ identifiers:
- references:
-     cis@debian8: 5.1.1
-     anssi: NT28(R5),NT28(R46)
--    cis: 4.2.3
-+    cis@rhel8: 4.2.1.1
-     disa: 1311,1312
-     hipaa: 164.312(a)(2)(ii)
-     iso27001-2013: A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1
-diff --git a/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml b/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml
-index 8a5a15e1da..14e729252c 100644
---- a/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml
-+++ b/linux_os/guide/system/logging/rsyslog_accepting_remote_messages/rsyslog_nolisten/rule.yml
-@@ -26,6 +26,7 @@ severity: medium
- identifiers:
-     cce@rhel6: 26803-7
-     cce@rhel7: 80192-8
-+    cce@rhel8: 84275-7
- 
- references:
-     stigid@ol7: "031010"
-@@ -39,3 +40,4 @@ references:
-     iso27001-2013: A.10.1.1,A.11.1.4,A.11.1.5,A.11.2.1,A.12.1.1,A.12.1.2,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.5.1,A.12.6.2,A.12.7.1,A.13.1.1,A.13.1.2,A.13.1.3,A.13.2.1,A.13.2.2,A.13.2.3,A.13.2.4,A.14.1.2,A.14.1.3,A.14.2.2,A.14.2.3,A.14.2.4,A.6.1.2,A.7.1.1,A.7.1.2,A.7.3.1,A.8.2.2,A.8.2.3,A.9.1.1,A.9.1.2,A.9.2.3,A.9.4.1,A.9.4.4,A.9.4.5
-     cis-csc: 1,11,12,13,14,15,16,18,3,4,5,6,8,9
-     stigid@rhel7: "031010"
-+    cis@rhel8: 4.2.1.6
-diff --git a/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml b/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml
-index 7b70b0c186..da28b99561 100644
---- a/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml
-+++ b/linux_os/guide/system/logging/rsyslog_sending_messages/rsyslog_remote_loghost/rule.yml
-@@ -46,8 +46,8 @@ references:
-     anssi: NT28(R7),NT28(R43),NT12(R5)
-     stigid@rhel6: "000136"
-     srg@rhel6: SRG-OS-000043,SRG-OS-000215
--    cis: 4.2.1.4
--    disa: 136,366,1348,1851
-+    cis@rhel8: 4.2.1.5
-+    disa: 366,1348,136,1851
-     hipaa: 164.308(a)(1)(ii)(D),164.308(a)(5)(ii)(B),164.308(a)(5)(ii)(C),164.308(a)(6)(ii),164.308(a)(8),164.310(d)(2)(iii),164.312(b),164.314(a)(2)(i)(C),164.314(a)(2)(iii)
-     iso27001-2013: A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.17.2.1
-     nist: CM-6(a),AU-4(1),AU-9(2)
-diff --git a/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml b/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml
-index ce8347c686..92fd6bc4d8 100644
---- a/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml
-+++ b/linux_os/guide/system/logging/service_rsyslog_enabled/rule.yml
-@@ -20,7 +20,7 @@ identifiers:
- references:
-     cis@debian8: 5.1.2
-     anssi: NT28(R5),NT28(R46)
--    cis: 4.2.1.1
-+    cis@rhel8: 4.2.1.2
-     disa: 1311,1312,1557,1851
-     hipaa: 164.312(a)(2)(ii)
-     iso27001-2013: A.12.1.3,A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1,A.14.2.7,A.15.2.1,A.15.2.2,A.17.2.1
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index cc0c2a5b9a..528f17d696 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -602,87 +602,88 @@ selections:
- 
-     ### 4.1.9 Ensure discretionary access control permission modification
-     ###       events are collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5509
-     
-     ### 4.1.10 Ensure unsuccessful unauthorized file access attempts are
-     ###        collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5510
- 
-     ### 4.1.11 Ensure events that modify user/group information are
-     ###        collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5511
- 
-     ### 4.1.12 Ensure successful file system mounts are collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5512
- 
-     ### 4.1.13 Ensure use of privileged commands is collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5513
- 
-     ### 4.1.14 Ensure file deletion events by users are collected
-     ###        (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5514
- 
-     ### 4.1.15 Ensure kernel module loading and unloading is collected
-     ###        (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5515
- 
-     ### 4.1.16 Ensure system administrator actions (sudolog) are
-     ###        collected (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5516
- 
-     ### 4.1.17 Ensure the audit configuration is immutable (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5517
- 
-     ## 4.2 Configure Logging
- 
-     ### 4.2.1 Configure rsyslog
- 
-     #### 4.2.1.1 Ensure rsyslog is installed (Scored)
--
-+    - package_rsyslog_installed
- 
-     #### 4.2.1.2 Ensure rsyslog Service is enabled (Scored)
--
-+    - service_rsyslog_enabled
- 
-     #### 4.2.1.3 Ensure rsyslog default file permissions configured (Scored)
--
-+    - rsyslog_files_permissions
- 
-     #### 4.2.1.4 Ensure logging is configured (Not Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5519
- 
-     #### 4.2.1.5 Ensure rsyslog is configured to send logs to a remote
-     ####         log host (Scored)   
--
-+    - rsyslog_remote_loghost
- 
-     #### 4.2.1.6 Ensure remote rsyslog messages are only accepted on
-     ####         designated log hosts (Not Scored)
--
-+    - rsyslog_nolisten
- 
-     ### 4.2.2 Configure journald
- 
-     #### 4.2.2.1 Ensure journald is configured to send logs to
-     ####         rsyslog (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5520
- 
-     #### 4.2.2.2 Ensure journald is configured to compress large
-     ####         log files (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5521
- 
- 
-     #### 4.2.2.3 Ensure journald is configured to write logfiles to
-     ####         persistent disk (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5522
- 
-     ### 4.2.3 Ensure permissions on all logfiles are configured (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5523
- 
-     ## 4.3 Ensure logrotate is conifgured (Not Scored)
--
-+    - ensure_logrotate_activated
- 
-     # 5 Access, Authentication and Authorization
- 
-     ## 5.1 Configure cron
- 
--
-     ### 5.1.1 Ensure cron daemon is enabled (Scored)
-+    - service_crond_enabled
- 
- 
-     ### 5.1.2 Ensure permissions on /etc/crontab are configured (Scored)
-@@ -790,19 +791,19 @@ selections:
- 
-     ### 5.2.14 Ensure SSH LoginGraceTime is set to one minute
-     ###        or less (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5525
- 
-     ### 5.2.15 Ensure SSH warning banner is configured (Scored)
-     - sshd_enable_warning_banner
- 
-     ### 5.2.16 Ensure SSH PAM is enabled (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5526
- 
-     ### 5.2.17 Ensure SSH AllowTcpForwarding is disabled (Scored)
-     - sshd_disable_tcp_forwarding
- 
-     ### 5.2.18 Ensure SSH MaxStarups is configured (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5528
- 
-     ### 5.2.19 Ensure SSH MaxSessions is set to 4 or less (Scored)
-     - sshd_set_max_sessions
-@@ -815,69 +816,75 @@ selections:
- 
- 
-     ### 5.3.1 Create custom authselectet profile (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5530
- 
-     ### 5.3.2 Select authselect profile (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5531
- 
-     ### 5.3.3 Ensure authselect includes with-faillock (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5532
- 
-     ## 5.4 Configure PAM
- 
-     ### 5.4.1 Ensure password creation requirements are configured (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5533
- 
-     ### 5.4.2 Ensure lockout for failed password attempts is
-     ###       configured (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5534
- 
-     ### 5.4.3 Ensure password reuse is limited (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5535
- 
-     ### 5.4.4 Ensure password hashing algorithm is SHA-512 (Scored)
--
-+    - set_password_hashing_algorithm_systemauth
- 
-     ## 5.5 User Accounts and Environment
- 
-     ### 5.5.1 Set Shadow Password Suite Parameters
- 
-     #### 5.5.1 Ensure password expiration is 365 days or less (Scored)
--
-+    - var_accounts_maximum_age_login_defs=365
-+    - accounts_maximum_age_login_defs
- 
-     #### 5.5.1.2 Ensure minimum days between password changes is 7
-     ####         or more (Scored)
--
-+    - var_accounts_minimum_age_login_defs=7
-+    - accounts_minimum_age_login_defs
- 
-     #### 5.5.1.3 Ensure password expiration warning days is
-     ####         7 or more (Scored)
--
-+    - var_accounts_password_warn_age_login_defs=7
-+    - accounts_password_warn_age_login_defs
- 
-     #### 5.5.1.4 Ensure inactive password lock is 30 days or less (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5536
- 
-     #### 5.5.1.5 Ensure all users last password change date is
-     ####         in the past (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5537
- 
-     ### 5.5.2 Ensure system accounts are secured (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5538
- 
-     ### 5.5.3 Ensure default user shell timeout is 900 seconds
-     ###       or less (Scored)
--
-+    - var_accounts_tmout=15_min
-+    - accounts_tmout
- 
-     ### 5.5.4 Ensure default group for the root account is
-     ###       GID 0 (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5539
- 
-     ### 5.5.5 Ensure default user mask is 027 or more restrictive (Scored)
--
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5540
- 
-     ## 5.6 Ensure root login is restricted to system console (Not Scored)
--
-+    - securetty_root_login_console_only
-+    - no_direct_root_logins
- 
-     ## 5.7 Ensure access to the su command is restricted (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5541
- 
-     # System Maintenance
- 
-@@ -971,8 +978,58 @@ selections:
-     ### 6.2.2 Ensure no legacy "+" entries exist in /etc/passwd (Scored)
-     - no_legacy_plus_entries_etc_passwd
- 
--    ## 6.2.4 Ensure no legacy "+" entries exist in /etc/shadow (Scored)
-+    ### 6.2.4 Ensure no legacy "+" entries exist in /etc/shadow (Scored)
-     - no_legacy_plus_entries_etc_shadow
- 
--    ###6.2.5 Ensure no legacy "+" entries exist in /etc/group (Scored)
-+    ### 6.2.5 Ensure no legacy "+" entries exist in /etc/group (Scored)
-     - no_legacy_plus_entries_etc_group
-+
-+    ### 6.2.6 Ensure root is the only UID 0 account (Scored)
-+    - accounts_no_uid_except_zero
-+
-+    ### 6.2.7 Ensure users' home directories permissions are 750
-+    ###       or more restrictive (Scored)
-+    - file_permissions_home_dirs
-+
-+    ### 6.2.8 Ensure users own their home directories (Scored)
-+    # NEEDS RULE for user owner @ https://github.com/ComplianceAsCode/content/issues/5507
-+    - file_groupownership_home_directories
-+
-+    ### 6.2.9 Ensure users' dot files are not group or world
-+    ###       writable (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5506
-+
-+    ### 6.2.10 Ensure no users have .forward files (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5505
-+
-+    ### 6.2.11 Ensure no users have .netrc files (Scored)
-+    - no_netrc_files
-+
-+    ### 6.2.12 Ensure users' .netrc Files are not group or
-+    ###        world accessible (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5504
-+
-+    ### 6.2.13 Ensure no users have .rhosts files (Scored)
-+    - no_rsh_trust_files
-+
-+    ### 6.2.14 Ensure all groups in /etc/passwd exist in
-+    ###        /etc/group (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5503
-+
-+    ### 6.2.15 Ensure no duplicate UIDs exist (Scored)
-+    # NEEDS RULE -  https://github.com/ComplianceAsCode/content/issues/5502
-+
-+    ### 6.2.16 Ensure no duplicate GIDs exist (Scored)
-+    # NEEDS RULE -  https://github.com/ComplianceAsCode/content/issues/5501
-+
-+    ### 6.2.17 Ensure no duplicate user names exist (Scored)
-+    - account_unique_name
-+
-+    ### 6.2.18 Ensure no duplicate group names exist (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5500
-+
-+    ### 6.2.19 Ensure shadow group is empty (Scored)
-+    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5499
-+
-+    ### 6.2.20 Ensure all users' home directories exist (Scored)
-+    - accounts_user_interactive_home_directory_exists
-diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt
-index feb31b0395..9e7bd35178 100644
---- a/shared/references/cce-redhat-avail.txt
-+++ b/shared/references/cce-redhat-avail.txt
-@@ -901,8 +901,6 @@ CCE-84270-8
- CCE-84271-6
- CCE-84272-4
- CCE-84273-2
--CCE-84274-0
--CCE-84275-7
- CCE-84276-5
- CCE-84277-3
- CCE-84278-1
-
-From c8a19c84dad5165ece50f6148646f9bbc8c4c3fd Mon Sep 17 00:00:00 2001
-From: Shawn Wells 
-Date: Sat, 25 Apr 2020 18:52:21 -0400
-Subject: [PATCH 02/20] misc cis8 updates
-
----
- .../accounts_users_home_files_ownership/rule.yml                | 1 +
- .../logging/log_rotation/ensure_logrotate_activated/rule.yml    | 2 +-
- 2 files changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/accounts/accounts-session/accounts_users_home_files_ownership/rule.yml b/linux_os/guide/system/accounts/accounts-session/accounts_users_home_files_ownership/rule.yml
-index a9c73e46ac..8e225cdc64 100644
---- a/linux_os/guide/system/accounts/accounts-session/accounts_users_home_files_ownership/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-session/accounts_users_home_files_ownership/rule.yml
-@@ -24,6 +24,7 @@ references:
-     stigid@ol7: "020660"
-     disa: "366"
-     srg: SRG-OS-000480-GPOS-00227
-+    cis@rhel8: 6.2.8
-     stigid@rhel7: "020660"
- 
- ocil_clause: 'the user ownership is incorrect'
-diff --git a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-index 2c41a3b9ef..6e569edfa9 100644
---- a/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-+++ b/linux_os/guide/system/logging/log_rotation/ensure_logrotate_activated/rule.yml
-@@ -35,7 +35,7 @@ references:
-     cobit5: APO11.04,BAI03.05,DSS05.04,DSS05.07,MEA02.01
-     iso27001-2013: A.12.4.1,A.12.4.2,A.12.4.3,A.12.4.4,A.12.7.1
-     cis-csc: 1,14,15,16,3,5,6
--    cis@rhel8: 4.3
-+    cis@rhel8: "4.3"
-     anssi: NT28(R43),NT12(R18)
- 
- ocil_clause: 'logrotate is not configured to run daily'
-
-From f8d80a55f0cd6bf3b9bf5b75ba037466b7fc89c8 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 22:32:44 +0200
-Subject: [PATCH 03/20] Add auxiliary rule for dconf settings
-
----
- rhel8/profiles/cis.profile | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 528f17d696..202db7f693 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -8,6 +8,8 @@ description: |-
-     09-30-2019.
- 
- selections:
-+    # Necessary for dconf rules
-+    - dconf_db_up_to_date
- 
-     ### Partitioning
-     - mount_option_home_nodev
-
-From 865fe310e82a1eb0fc0c37c8de253dc7171abae7 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 22:43:20 +0200
-Subject: [PATCH 04/20] Update time synchonization rule selections
-
-In RHEL8, only chrony is available
----
- rhel8/profiles/cis.profile | 6 ++++--
- 1 file changed, 4 insertions(+), 2 deletions(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 202db7f693..762d4a04e3 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -256,10 +256,12 @@ selections:
-     ### 2.2.1 Time Synchronization
- 
-     #### 2.2.1.1 Ensure time synchronization is in use (Not Scored)
--    - service_chronyd_or_ntpd_enabled
-+    - package_chrony_installed
- 
-     #### 2.2.1.2 Ensure chrony is configured (Scored)
--    - chronyd_or_ntpd_specify_remote_server
-+    - service_chronyd_enabled
-+    - chronyd_specify_remote_server
-+    - chronyd_run_as_chrony_user
- 
-     ### 2.2.2 Ensure X Window System is not installed (Scored)
-     - package_xorg-x11-server-common_removed
-
-From a515b26c5af850dbc7917807397668df8a076249 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 22:49:55 +0200
-Subject: [PATCH 05/20] Select sysctl rules for secure ICMp redirects
-
-Fixes: #5234
-Fixes: #5235
----
- rhel8/profiles/cis.profile | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 762d4a04e3..3a8e19259b 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -371,14 +371,14 @@ selections:
-     - sysctl_net_ipv6_conf_all_accept_redirects
- 
-     #### net.ipv6.conf.defaults.accept_redirects = 0
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5234
-+    - sysctl_net_ipv6_conf_default_accept_redirects
- 
-     ### 3.2.3 Ensure secure ICMP redirects are not accepted (Scored)
-     #### net.ipv4.conf.all.secure_redirects = 0
-     - sysctl_net_ipv4_conf_all_secure_redirects
- 
-     #### net.ipv4.cof.default.secure_redirects = 0
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5235
-+    - sysctl_net_ipv4_conf_default_secure_redirects
- 
-     ### 3.2.4 Ensure suspicious packets are logged (Scored)
-     #### net.ipv4.conf.all.log_martians = 1
-
-From d14ce8e0ab8c39282883520bb141919af379d0fa Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:02:09 +0200
-Subject: [PATCH 06/20] Select Audit DAC rules for RHEL8 CIS
-
-Fixes: #5509
----
- rhel8/profiles/cis.profile | 14 +++++++++++++-
- 1 file changed, 13 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 3a8e19259b..a990de4565 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -606,7 +606,19 @@ selections:
- 
-     ### 4.1.9 Ensure discretionary access control permission modification
-     ###       events are collected (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5509
-+    - audit_rules_dac_modification_chmod
-+    - audit_rules_dac_modification_fchmod
-+    - audit_rules_dac_modification_fchmodat
-+    - audit_rules_dac_modification_chown
-+    - audit_rules_dac_modification_fchown
-+    - audit_rules_dac_modification_fchownat
-+    - audit_rules_dac_modification_lchown
-+    - audit_rules_dac_modification_setxattr
-+    - audit_rules_dac_modification_lsetxattr
-+    - audit_rules_dac_modification_fsetxattr
-+    - audit_rules_dac_modification_removexattr
-+    - audit_rules_dac_modification_lremovexattr
-+    - audit_rules_dac_modification_fremovexattr
-     
-     ### 4.1.10 Ensure unsuccessful unauthorized file access attempts are
-     ###        collected (Scored)
-
-From aec372e7bd05b3ed470f188952dbf11a6ae123ad Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:07:34 +0200
-Subject: [PATCH 07/20] Select rules for unsuccessful modification
-
-Fixes: #5510
----
- rhel8/profiles/cis.profile | 8 +++++++-
- 1 file changed, 7 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index a990de4565..db54d9ece5 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -622,7 +622,13 @@ selections:
-     
-     ### 4.1.10 Ensure unsuccessful unauthorized file access attempts are
-     ###        collected (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5510
-+    - audit_rules_unsuccessful_file_modification_creat
-+    - audit_rules_unsuccessful_file_modification_open
-+    - audit_rules_unsuccessful_file_modification_openat
-+    - audit_rules_unsuccessful_file_modification_truncate
-+    - audit_rules_unsuccessful_file_modification_ftruncate
-+    # Opinionated selection
-+    - audit_rules_unsuccessful_file_modification_open_by_handle_at
- 
-     ### 4.1.11 Ensure events that modify user/group information are
-     ###        collected (Scored)
-
-From 69493775c8a5b140f55802f7dca84c659662039c Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:10:45 +0200
-Subject: [PATCH 08/20] Select rules for user/group modification
-
-Fixes: #5511
----
- rhel8/profiles/cis.profile | 6 +++++-
- 1 file changed, 5 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index db54d9ece5..f8ec16b9a8 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -632,7 +632,11 @@ selections:
- 
-     ### 4.1.11 Ensure events that modify user/group information are
-     ###        collected (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5511
-+    - audit_rules_usergroup_modification_passwd
-+    - audit_rules_usergroup_modification_group
-+    - audit_rules_usergroup_modification_gshadow
-+    - audit_rules_usergroup_modification_shadow
-+    - audit_rules_usergroup_modification_opasswd
- 
-     ### 4.1.12 Ensure successful file system mounts are collected (Scored)
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5512
-
-From 86c35876312882a861d253e13d31ff5bfc32630b Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:12:58 +0200
-Subject: [PATCH 09/20] Audit successful system mounts
-
-Fixes: #5512
----
- rhel8/profiles/cis.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index f8ec16b9a8..e4f5313e3e 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -639,7 +639,7 @@ selections:
-     - audit_rules_usergroup_modification_opasswd
- 
-     ### 4.1.12 Ensure successful file system mounts are collected (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5512
-+    - audit_rules_media_export
- 
-     ### 4.1.13 Ensure use of privileged commands is collected (Scored)
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5513
-
-From ea7ef606c881fdddecfef036383fbd0718950162 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:14:21 +0200
-Subject: [PATCH 10/20] Audit privileged commands
-
-Fixes: #5513
----
- rhel8/profiles/cis.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index e4f5313e3e..087dd79bb5 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -642,7 +642,7 @@ selections:
-     - audit_rules_media_export
- 
-     ### 4.1.13 Ensure use of privileged commands is collected (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5513
-+    - audit_rules_privileged_commands
- 
-     ### 4.1.14 Ensure file deletion events by users are collected
-     ###        (Scored)
-
-From 16d84540566c8fa6d9f6880f3f1fe04edf97b822 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:15:49 +0200
-Subject: [PATCH 11/20] Audit file deletion events
-
-Fixes: #5514
----
- rhel8/profiles/cis.profile | 7 ++++++-
- 1 file changed, 6 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 087dd79bb5..ca42f24190 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -646,7 +646,12 @@ selections:
- 
-     ### 4.1.14 Ensure file deletion events by users are collected
-     ###        (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5514
-+    - audit_rules_file_deletion_events_unlink
-+    - audit_rules_file_deletion_events_unlinkat
-+    - audit_rules_file_deletion_events_rename
-+    - audit_rules_file_deletion_events_renameat
-+    # Opinionated selection
-+    - audit_rules_file_deletion_events_rmdir
- 
-     ### 4.1.15 Ensure kernel module loading and unloading is collected
-     ###        (Scored)
-
-From 8377e1d574a9d0388c0847177f11afe83af3a30f Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:16:33 +0200
-Subject: [PATCH 12/20] Audit kernel module loads
-
-Fixes: #5515
----
- rhel8/profiles/cis.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index ca42f24190..5e214941ec 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -655,7 +655,7 @@ selections:
- 
-     ### 4.1.15 Ensure kernel module loading and unloading is collected
-     ###        (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5515
-+    - audit_rules_kernel_module_loading
- 
-     ### 4.1.16 Ensure system administrator actions (sudolog) are
-     ###        collected (Scored)
-
-From 7d62c009987be550d074f8e7cacd2e843d1e3061 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:17:52 +0200
-Subject: [PATCH 13/20] Audit rules should be immutable
-
-Fixes: #5517
----
- rhel8/profiles/cis.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 5e214941ec..a0fdd69869 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -662,7 +662,7 @@ selections:
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5516
- 
-     ### 4.1.17 Ensure the audit configuration is immutable (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5517
-+    - audit_rules_immutable
- 
-     ## 4.2 Configure Logging
- 
-
-From 02e2a9744bd9eb969b46b18d4824fae65d5764f3 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:31:10 +0200
-Subject: [PATCH 14/20] Select rules for password requirements
-
-Related to: #5533
----
- rhel8/profiles/cis.profile | 7 ++++++-
- 1 file changed, 6 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index a0fdd69869..a55c3291a9 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -858,7 +858,12 @@ selections:
-     ## 5.4 Configure PAM
- 
-     ### 5.4.1 Ensure password creation requirements are configured (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5533
-+    # NEEDS RULE: try_first_pass - https://github.com/ComplianceAsCode/content/issues/5533
-+    - accounts_password_pam_retry
-+    - var_password_pam_minlen=14
-+    - accounts_password_pam_minlen
-+    - var_password_pam_minclass=4
-+    - accounts_password_pam_minclass
- 
-     ### 5.4.2 Ensure lockout for failed password attempts is
-     ###       configured (Scored)
-
-From bec97effc13e0056cbcdc939620e78669558f9a4 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:35:50 +0200
-Subject: [PATCH 15/20] Configure password lockout
-
-Fixes: #5534
----
- rhel8/profiles/cis.profile | 5 ++++-
- 1 file changed, 4 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index a55c3291a9..6e10c2efcb 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -867,7 +867,10 @@ selections:
- 
-     ### 5.4.2 Ensure lockout for failed password attempts is
-     ###       configured (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5534
-+    - var_accounts_passwords_pam_faillock_unlock_time=900
-+    - var_accounts_passwords_pam_faillock_deny=5
-+    - accounts_passwords_pam_faillock_unlock_time
-+    - accounts_passwords_pam_faillock_deny
- 
-     ### 5.4.3 Ensure password reuse is limited (Scored)
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5535
-
-From 73a087ed0b13bb73f1e60792c4d2e3c3aa944cd9 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:38:58 +0200
-Subject: [PATCH 16/20] Configure password reuse
-
-Fixes: #5535
----
- rhel8/profiles/cis.profile | 3 ++-
- 1 file changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 6e10c2efcb..2fa85d8676 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -873,7 +873,8 @@ selections:
-     - accounts_passwords_pam_faillock_deny
- 
-     ### 5.4.3 Ensure password reuse is limited (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5535
-+    - var_password_pam_unix_remember=5
-+    - accounts_password_pam_unix_remember
- 
-     ### 5.4.4 Ensure password hashing algorithm is SHA-512 (Scored)
-     - set_password_hashing_algorithm_systemauth
-
-From 4307123e1889359b1c444d55a9b221bc5b3f7970 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:43:04 +0200
-Subject: [PATCH 17/20] Select rule to check useradd INACTIVE setting
-
-Related to: #5536
----
- rhel8/profiles/cis.profile | 5 ++++-
- 1 file changed, 4 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 2fa85d8676..e0fd5e1492 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -898,7 +898,10 @@ selections:
-     - accounts_password_warn_age_login_defs
- 
-     #### 5.5.1.4 Ensure inactive password lock is 30 days or less (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5536
-+    # TODO: Rule doesn't check list of users
-+    # https://github.com/ComplianceAsCode/content/issues/5536
-+    - var_account_disable_post_pw_expiration=30
-+    - account_disable_post_pw_expiration
- 
-     #### 5.5.1.5 Ensure all users last password change date is
-     ####         in the past (Scored)
-
-From 07752fbac033400946c29fe6cbfe553913e4a96c Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:46:48 +0200
-Subject: [PATCH 18/20] No shelllogin for system accounts
-
-Fixes: #5538
----
- rhel8/profiles/cis.profile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index e0fd5e1492..0431fb0d45 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -908,7 +908,7 @@ selections:
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5537
- 
-     ### 5.5.2 Ensure system accounts are secured (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5538
-+    - no_shelllogin_for_systemaccounts
- 
-     ### 5.5.3 Ensure default user shell timeout is 900 seconds
-     ###       or less (Scored)
-
-From e46c2cfb8541f559b234df9a8a478494db46e785 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 23:54:07 +0200
-Subject: [PATCH 19/20] Partially cover umask requirements
-
-Related to: #5540
----
- rhel8/profiles/cis.profile | 4 +++-
- 1 file changed, 3 insertions(+), 1 deletion(-)
-
-diff --git a/rhel8/profiles/cis.profile b/rhel8/profiles/cis.profile
-index 0431fb0d45..f332ee5462 100644
---- a/rhel8/profiles/cis.profile
-+++ b/rhel8/profiles/cis.profile
-@@ -920,7 +920,9 @@ selections:
-     # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5539
- 
-     ### 5.5.5 Ensure default user mask is 027 or more restrictive (Scored)
--    # NEEDS RULE - https://github.com/ComplianceAsCode/content/issues/5540
-+    - var_accounts_user_umask=027
-+    - accounts_umask_etc_bashrc
-+    - accounts_umask_etc_profile
- 
-     ## 5.6 Ensure root login is restricted to system console (Not Scored)
-     - securetty_root_login_console_only
-
-From 586cedfb95523acbe0c0c92953851d6536c29230 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 19 May 2020 22:31:16 +0200
-Subject: [PATCH 20/20] account_unique_name: Improve description, rationale and
- OCIL
-
----
- .../account_unique_name/rule.yml              | 19 +++++++++----------
- 1 file changed, 9 insertions(+), 10 deletions(-)
-
-diff --git a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-index 35652a410b..909f1b6657 100644
---- a/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-+++ b/linux_os/guide/system/accounts/accounts-restrictions/account_expiration/account_unique_name/rule.yml
-@@ -3,14 +3,13 @@ documentation_complete: true
- title: 'Ensure All Accounts on the System Have Unique Names'
- 
- description: |-
--    Although the useradd utility prevents creation of duplicate user
--    names, it is possible for a malicious administrator to manually edit the
--    /etc/passwd file and change the user name.
-+    Ensure accounts on the system have unique names.
- 
--rationale: |-
--    If a user is assigned a duplicate user name, the new user will be able to
--    create and have access to files with the first UID for that username as
--    defined in /etc/passwd.
-+    To ensure all accounts have unique names, run the following command:
-+    
$ sudo getent passwd | awk -F: '{ print $1}' | uniq -d

-+    If a username is returned, change or delete the username.
-+
-+rationale: 'Unique usernames allow for accountability on the system.'
- 
- severity: medium
- 
-@@ -30,6 +29,6 @@ references:
- ocil_clause: 'a line is returned'
- 
- ocil: |-
--    Run the following command to check for duplicate account names:
--    
$ sudo pwck -qr

--    If there are no duplicate names, no line will be returned.
-+    To verify all accounts have unique names, run the following command:
-+    
$ sudo getent passwd | awk -F: '{ print $1}' | uniq -d

-+    No output should be returned.
diff --git a/SOURCES/scap-security-guide-0.1.52-add-grub2-platform-to-more-rules_PR_5952.patch b/SOURCES/scap-security-guide-0.1.52-add-grub2-platform-to-more-rules_PR_5952.patch
deleted file mode 100644
index 398abcc..0000000
--- a/SOURCES/scap-security-guide-0.1.52-add-grub2-platform-to-more-rules_PR_5952.patch
+++ /dev/null
@@ -1,88 +0,0 @@
-From d455dc468ef51dd595ce6184f1d31ebf4c20ab9c Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 22 Jul 2020 09:52:50 +0200
-Subject: [PATCH] Add grub2 platform to grub2 kernel option rules
-
-This will make sure these rules are applicable only when grub2
-(grub2-pc) is installed.
----
- linux_os/guide/system/auditing/grub2_audit_argument/rule.yml    | 2 ++
- .../system/auditing/grub2_audit_backlog_limit_argument/rule.yml | 2 +-
- .../system/permissions/mounting/grub2_nousb_argument/rule.yml   | 2 ++
- .../guide/system/permissions/restrictions/poisoning/group.yml   | 2 ++
- .../restrictions/poisoning/grub2_page_poison_argument/rule.yml  | 2 +-
- .../restrictions/poisoning/grub2_slub_debug_argument/rule.yml   | 2 +-
- 7 files changed, 11 insertions(+), 3 deletions(-)
-
-diff --git a/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml b/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml
-index 00cb7f9b6c..5f3a47a776 100644
---- a/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml
-+++ b/linux_os/guide/system/auditing/grub2_audit_argument/rule.yml
-@@ -102,6 +102,8 @@ warnings:
- {{% endif %}}
-         
- 
-+platform: grub2
-+
- template:
-     name: grub2_bootloader_argument
-     vars:
-diff --git a/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml
-index 6cab6f7bfe..aa95957b58 100644
---- a/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/auditing/grub2_audit_backlog_limit_argument/rule.yml
-@@ -60,7 +60,7 @@ warnings:
- {{% endif %}}
-         
- 
--platform: machine
-+platform: grub2
- 
- template:
-     name: grub2_bootloader_argument
-diff --git a/linux_os/guide/system/permissions/mounting/grub2_nousb_argument/rule.yml b/linux_os/guide/system/permissions/mounting/grub2_nousb_argument/rule.yml
-index a3c1f48231..407ba2c069 100644
---- a/linux_os/guide/system/permissions/mounting/grub2_nousb_argument/rule.yml
-+++ b/linux_os/guide/system/permissions/mounting/grub2_nousb_argument/rule.yml
-@@ -37,3 +37,5 @@ warnings:
-         Disabling all kernel support for USB will cause problems for systems
-         with USB-based keyboards, mice, or printers. This configuration is
-         infeasible for systems which require USB devices, which is common.
-+
-+platform: grub2
-diff --git a/linux_os/guide/system/permissions/restrictions/poisoning/group.yml b/linux_os/guide/system/permissions/restrictions/poisoning/group.yml
-index 6a7a370f2b..030a3e9918 100644
---- a/linux_os/guide/system/permissions/restrictions/poisoning/group.yml
-+++ b/linux_os/guide/system/permissions/restrictions/poisoning/group.yml
-@@ -6,3 +6,5 @@ description: |-
-     Memory Poisoning consists of writing a special value to uninitialized or freed memory.
-     Poisoning can be used as a mechanism to prevent leak of information and detection of
-     corrupted memory.
-+
-+platform: machine
-diff --git a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml
-index e3047ef223..2d97ec75ea 100644
---- a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_page_poison_argument/rule.yml
-@@ -60,7 +60,7 @@ warnings:
- {{% endif %}}
-         
- 
--platform: machine
-+platform: grub2
- 
- template:
-     name: grub2_bootloader_argument
-diff --git a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml
-index 024c93f18b..39ca33b77a 100644
---- a/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/permissions/restrictions/poisoning/grub2_slub_debug_argument/rule.yml
-@@ -60,7 +60,7 @@ warnings:
- {{% endif %}}
-         
- 
--platform: machine
-+platform: grub2
- 
- template:
-     name: grub2_bootloader_argument
diff --git a/SOURCES/scap-security-guide-0.1.52-add-zipl-boot-options-template_PR_5908.patch b/SOURCES/scap-security-guide-0.1.52-add-zipl-boot-options-template_PR_5908.patch
deleted file mode 100644
index 3e89401..0000000
--- a/SOURCES/scap-security-guide-0.1.52-add-zipl-boot-options-template_PR_5908.patch
+++ /dev/null
@@ -1,954 +0,0 @@
-From f37e40e3de5ff493c60c61a054026dabf7b79032 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 1 Jul 2020 16:12:35 +0200
-Subject: [PATCH 01/18] Kickstart zipl_bls_entries_option template
-
-Create initial version of zIPL specific BLS entries
-template by copying bls_entries_option template.
----
- .../template_OVAL_zipl_bls_entries_option     | 32 +++++++++++++++++++
- ssg/templates.py                              |  5 +++
- 2 files changed, 37 insertions(+)
- create mode 100644 shared/templates/template_OVAL_zipl_bls_entries_option
-
-diff --git a/shared/templates/template_OVAL_zipl_bls_entries_option b/shared/templates/template_OVAL_zipl_bls_entries_option
-new file mode 100644
-index 0000000000..a19bd5a89c
---- /dev/null
-+++ b/shared/templates/template_OVAL_zipl_bls_entries_option
-@@ -0,0 +1,32 @@
-+
-+  
-+    
-+      Ensure that BLS-compatible boot loader is configured to run Linux operating system with argument {{{ ARG_NAME_VALUE }}}
-+      {{{- oval_affected(products) }}}
-+      Ensure {{{ ARG_NAME_VALUE }}} option is configured in the 'options' line in /boot/loader/entries/*.conf.
-+    
-+    
-+        
-+    
-+  
-+
-+  
-+    
-+    
-+  
-+
-+  
-+    ^/boot/loader/entries/.*\.conf$
-+    ^options (.*)$
-+    1
-+  
-+
-+  
-+    ^(?:.*\s)?{{{ ESCAPED_ARG_NAME_VALUE }}}(?:\s.*)?$
-+  
-+
-diff --git a/ssg/templates.py b/ssg/templates.py
-index 2795267abd..fc09416abe 100644
---- a/ssg/templates.py
-+++ b/ssg/templates.py
-@@ -340,6 +340,22 @@ def bls_entries_option(data, lang):
-     return data
- 
- 
-+@template(["oval"])
-+def bls_entries_option(data, lang):
-+    data["arg_name_value"] = data["arg_name"] + "=" + data["arg_value"]
-+    if lang == "oval":
-+        # escape dot, this is used in oval regex
-+        data["escaped_arg_name_value"] = data["arg_name_value"].replace(".", "\\.")
-+        # replace . with _, this is used in test / object / state ids
-+        data["sanitized_arg_name"] = data["arg_name"].replace(".", "_")
-+    return data
-+
-+
-+@template(["oval"])
-+def zipl_bls_entries_option(data, lang):
-+    return bls_entries_option(data, lang)
-+
-+
- class Builder(object):
-     """
-     Class for building all templated content for a given product.
-
-From f54c3c974b6a3ce6d40533a51f867d2e8985b688 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 14:11:04 +0200
-Subject: [PATCH 02/18] zipl_bls_entries_option: check opts after install
-
-Extend zipl_bls_entries_option template to check that the kernel option
-is also configure in /etc/kernel/cmdline.
-The presence of the argument in /etc/kernel/cmdline ensures that newly
-installed kernels will be configure if the option.
----
- .../template_OVAL_zipl_bls_entries_option     | 19 +++++++++++++++++--
- 1 file changed, 17 insertions(+), 2 deletions(-)
-
-diff --git a/shared/templates/template_OVAL_zipl_bls_entries_option b/shared/templates/template_OVAL_zipl_bls_entries_option
-index a19bd5a89c..9af1bcfbee 100644
---- a/shared/templates/template_OVAL_zipl_bls_entries_option
-+++ b/shared/templates/template_OVAL_zipl_bls_entries_option
-@@ -6,8 +6,10 @@
-       Ensure {{{ ARG_NAME_VALUE }}} option is configured in the 'options' line in /boot/loader/entries/*.conf.
-     
-     
--        
-+      
-+      
-     
-   
- 
-@@ -25,6 +27,19 @@
-     1
-   
- 
-+  
-+    
-+    
-+  
-+  
-+    /etc/kernel/cmdline
-+    ^(.*)$
-+    1
-+  
-+
-   
-     ^(?:.*\s)?{{{ ESCAPED_ARG_NAME_VALUE }}}(?:\s.*)?$
-
-From 5b66eff84794b99a4ba7a626c46f1970715b1bcd Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 14:12:32 +0200
-Subject: [PATCH 03/18] zipl_bls_entries_option: Add Ansible and Bash
-
----
- .../template_ANSIBLE_zipl_bls_entries_option  | 48 +++++++++++++++++++
- .../template_BASH_zipl_bls_entries_option     | 12 +++++
- ssg/templates.py                              |  2 +-
- 3 files changed, 61 insertions(+), 1 deletion(-)
- create mode 100644 shared/templates/template_ANSIBLE_zipl_bls_entries_option
- create mode 100644 shared/templates/template_BASH_zipl_bls_entries_option
-
-diff --git a/shared/templates/template_ANSIBLE_zipl_bls_entries_option b/shared/templates/template_ANSIBLE_zipl_bls_entries_option
-new file mode 100644
-index 0000000000..c0cb131b82
---- /dev/null
-+++ b/shared/templates/template_ANSIBLE_zipl_bls_entries_option
-@@ -0,0 +1,48 @@
-+# platform = Red Hat Enterprise Linux 8
-+# reboot = true
-+# strategy = configure
-+# complexity = medium
-+# disruption = low
-+
-+- name: "Ensure BLS boot entries options contain {{{ ARG_NAME_VALUE }}}"
-+  block:
-+    - name: "Check if any boot entry misses {{{ ARG_NAME_VALUE }}}"
-+      find:
-+        paths: "/boot/loader/entries/"
-+        contains: "^options .*{{{ ARG_NAME_VALUE }}}.*$"
-+        patterns: "*.conf"
-+      register: entries_options
-+
-+    - name: "Update boot entries options"
-+      command: grubby --update-kernel=ALL --args="{{{ ARG_NAME_VALUE }}}"
-+      when: entries_options is defined and entries_options.examined != entries_options.matched
-+      # The conditional above assumes that only *.conf files are present in /boot/loader/entries
-+      # Then, the number of conf files is the same as examined files
-+
-+    - name: "Check if /etc/kernel/cmdline exists"
-+      stat:
-+        path: /etc/kernel/cmdline
-+      register: cmdline_stat
-+
-+    - name: "Check if /etc/kernel/cmdline contains {{{ ARG_NAME_VALUE }}}"
-+      find:
-+        paths: "/etc/kernel/"
-+        patterns: "cmdline"
-+        contains: "^.*{{{ ARG_NAME_VALUE }}}.*$"
-+      register: cmdline_find
-+
-+    - name: "Add /etc/kernel/cmdline contains {{{ ARG_NAME_VALUE }}}"
-+      lineinfile:
-+        create: yes
-+        path: "/etc/kernel/cmdline"
-+        line: '{{{ ARG_NAME_VALUE }}}'
-+      when: cmdline_stat is defined and not cmdline_stat.stat.exists
-+
-+    - name: "Append /etc/kernel/cmdline contains {{{ ARG_NAME_VALUE }}}"
-+      lineinfile:
-+        path: "/etc/kernel/cmdline"
-+        backrefs: yes
-+        regexp: "^(.*)$"
-+        line: '\1 {{{ ARG_NAME_VALUE }}}'
-+      when: cmdline_stat is defined and cmdline_stat.stat.exists and cmdline_find is defined and cmdline_find.matched == 0
-+
-diff --git a/shared/templates/template_BASH_zipl_bls_entries_option b/shared/templates/template_BASH_zipl_bls_entries_option
-new file mode 100644
-index 0000000000..9fc8865486
---- /dev/null
-+++ b/shared/templates/template_BASH_zipl_bls_entries_option
-@@ -0,0 +1,12 @@
-+# platform = Red Hat Enterprise Linux 8
-+
-+# Correct BLS option using grubby, which is a thin wrapper around BLS operations
-+grubby --update-kernel=ALL --args="{{{ ARG_NAME_VALUE }}}"
-+
-+# Ensure new kernels and boot entries retain the boot option
-+if [ ! -f /etc/kernel/cmdline ]; then
-+    echo "{{{ ARG_NAME_VALUE }}}" >> /etc/kernel/cmdline
-+elif ! grep -q '^(.*\s)?{{{ ARG_NAME_VALUE }}}(\s.*)?$' /etc/kernel/cmdline; then
-+    echo " audit=1" >> /etc/kernel/cmdline
-+    sed -Ei 's/^(.*)$/\1 audit=1/' /etc/kernel/cmdline
-+fi
-diff --git a/ssg/templates.py b/ssg/templates.py
-index fc09416abe..a27fbb6cb6 100644
---- a/ssg/templates.py
-+++ b/ssg/templates.py
-@@ -340,7 +340,7 @@ def bls_entries_option(data, lang):
-     return data
- 
- 
--@template(["oval"])
-+@template(["ansible", "bash", "oval"])
- def zipl_bls_entries_option(data, lang):
-     return bls_entries_option(data, lang)
- 
-
-From fd2d807f60a4a36ad96f5ac37df9b4651fe3480e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 3 Jul 2020 15:50:56 +0200
-Subject: [PATCH 04/18] Enable zIPL in argument rules
-
----
- .../system/bootloader-zipl/zipl_audit_argument/rule.yml     | 6 ++++++
- .../zipl_audit_backlog_limit_argument/rule.yml              | 6 ++++++
- .../bootloader-zipl/zipl_page_poison_argument/rule.yml      | 6 ++++++
- .../guide/system/bootloader-zipl/zipl_pti_argument/rule.yml | 6 ++++++
- .../bootloader-zipl/zipl_slub_debug_argument/rule.yml       | 6 ++++++
- .../system/bootloader-zipl/zipl_vsyscall_argument/rule.yml  | 6 ++++++
- 6 files changed, 36 insertions(+)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-index 624b4e7041..894bf7995f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-@@ -28,3 +28,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that doesn't enable audit.
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: audit
-+    arg_value: '1'
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index faf114591a..12334c9905 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -28,3 +28,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that does not extend the log events queue.
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: audit_backlog_limit
-+    arg_value: '8192'
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-index 866664c01b..f5a36ee1b3 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-@@ -28,3 +28,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that doesn't enable page poisoning.
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: page_poison
-+    arg_value: '1'
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-index 2f02d9668c..168dae46a1 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-@@ -27,3 +27,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that doesn't enable page-table isolation .
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: pti
-+    arg_value: 'on'
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index 0cb10d3cd8..84a374e36f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -28,3 +28,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that does not enable poisoning.
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: slub_debug
-+    arg_value: 'P'
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index f79adeb083..c37e8bbefd 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -25,3 +25,9 @@ ocil: |-
-   No line should be returned, each line returned is a boot entry that doesn't disable virtual syscalls.
- 
- platform: machine
-+
-+template:
-+  name: zipl_bls_entries_option
-+  vars:
-+    arg_name: vsyscall
-+    arg_value: 'none'
-
-From 08db1a1d4bb3362195c34e266feb9bac31ba4be8 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Sat, 4 Jul 2020 01:15:49 +0200
-Subject: [PATCH 05/18] zipl_audit_backlog_limit_argument: Fix OCIL typo
-
-Fix typo
----
- .../bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml  | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index 12334c9905..15729dc6b6 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -24,7 +24,7 @@ ocil_clause: 'audit backlog limit is not configured'
- ocil: |-
-   To check that all boot entries extend the backlog limit;
-   Check that all boot entries extend the log events queue:
--  
sudo grep -L "^options\s+.*\baudit_backlog_limit=0\b" /boot/loader/entries/*.conf

-+  
sudo grep -L "^options\s+.*\baudit_backlog_limit=8192\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that does not extend the log events queue.
- 
- platform: machine
-
-From 779506348675557e204e1d88f214833b313c0f20 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 12:00:10 +0200
-Subject: [PATCH 06/18] zipl_slub_debug_argument: Fix description
-
-Description about how to ensure that new boot entries continue compliant
-was incorrect due to copy-pasta mistake.
----
- .../system/bootloader-zipl/zipl_slub_debug_argument/rule.yml    | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index 84a374e36f..83e043179d 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -8,7 +8,7 @@ description: |-
-     To enable poisoning of SLUB/SLAB objects,
-     check that all boot entries in /boot/loader/entries/*.conf have slub_debug=P
-     included in its options.

--    To ensure that new kernels and boot entries continue to extend the audit log events queue,
-+    To ensure that new kernels and boot entries continue to enable poisoning of SLUB/SLAB objects,
-     add slub_debug=P to /etc/kernel/cmdline.
- 
- rationale: |-
-
-From 6a3f2f6bdc13188e780f0f3e4f829f6fa79351b2 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 12:06:56 +0200
-Subject: [PATCH 07/18] Add CCEs to zIPL argument rules
-
----
- .../system/bootloader-zipl/zipl_audit_argument/rule.yml     | 3 +++
- .../zipl_audit_backlog_limit_argument/rule.yml              | 3 +++
- .../bootloader-zipl/zipl_page_poison_argument/rule.yml      | 3 +++
- .../guide/system/bootloader-zipl/zipl_pti_argument/rule.yml | 3 +++
- .../bootloader-zipl/zipl_slub_debug_argument/rule.yml       | 3 +++
- .../system/bootloader-zipl/zipl_vsyscall_argument/rule.yml  | 3 +++
- 7 files changed, 18 insertions(+), 6 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-index 894bf7995f..b1307ef3f2 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-@@ -20,6 +20,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83321-0
-+
- ocil_clause: 'auditing is not enabled at boot time'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index 15729dc6b6..18391bee6c 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -19,6 +19,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83341-8
-+
- ocil_clause: 'audit backlog limit is not configured'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-index f5a36ee1b3..7ffea8ce6a 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-@@ -20,6 +20,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83351-7
-+
- ocil_clause: 'page allocator poisoning is not enabled'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-index 168dae46a1..6fd1082292 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-@@ -19,6 +19,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83361-6
-+
- ocil_clause: 'Kernel page-table isolation is not enabled'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index 83e043179d..c499140c35 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -20,6 +20,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83371-5
-+
- ocil_clause: 'SLUB/SLAB poisoning is not enabled'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index c37e8bbefd..7edd43074f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -17,6 +17,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83381-4
-+
- ocil_clause: 'vsyscalls are enabled'
- 
- ocil: |-
-
-From a7c33132a8d5f8cdf9c0d5f38b4910376ff1330b Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 14:36:28 +0200
-Subject: [PATCH 08/18] Select zipl BLS option rules in OSPP Profile
-
-These rules check and ensure configuration of BLS boot options used by
-zIPL.
----
- rhel8/profiles/ospp.profile | 8 ++++++++
- rhel8/profiles/stig.profile | 6 ++++++
- 2 files changed, 14 insertions(+)
-
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index 80e4b71fff..d3732fa805 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -419,3 +419,11 @@ selections:
-     # zIPl specific rules
-     - zipl_bls_entries_only
-     - zipl_bootmap_is_up_to_date
-+    - zipl_audit_argument
-+    - zipl_audit_backlog_limit_argument
-+    - zipl_slub_debug_argument
-+    - zipl_page_poison_argument
-+    - zipl_vsyscall_argument
-+    - zipl_vsyscall_argument.role=unscored
-+    - zipl_vsyscall_argument.severity=info
-+    - zipl_pti_argument
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index cfc2160be1..69d5222a32 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -49,3 +49,9 @@ selections:
-     # Unselect zIPL rules from OSPP
-     - "!zipl_bls_entries_only"
-     - "!zipl_bootmap_is_up_to_date"
-+    - "!zipl_audit_argument"
-+    - "!zipl_audit_backlog_limit_argument"
-+    - "!zipl_page_poison_argument"
-+    - "!zipl_pti_argument"
-+    - "!zipl_slub_debug_argument"
-+    - "!zipl_vsyscall_argument"
-
-From be070d56abed9efc9244b6c989d0a0df1f78b5ff Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 22:30:25 +0200
-Subject: [PATCH 09/18] Extend Profile resolution to undo rule refinements
-
-Just like rule selection, allows rule refinements to be unselected, or "undone".
----
- build-scripts/compile_profiles.py | 16 +++++++++++++++-
- 1 file changed, 15 insertions(+), 1 deletion(-)
-
-diff --git a/build-scripts/compile_profiles.py b/build-scripts/compile_profiles.py
-index 0967252348..d1ce8984b2 100644
---- a/build-scripts/compile_profiles.py
-+++ b/build-scripts/compile_profiles.py
-@@ -3,6 +3,7 @@
- import argparse
- import sys
- import os.path
-+from copy import deepcopy
- from glob import glob
- 
- import ssg.build_yaml
-@@ -36,7 +37,8 @@ def resolve(self, all_profiles):
-             updated_variables.update(self.variables)
-             self.variables = updated_variables
- 
--            updated_refinements = dict(extended_profile.refine_rules)
-+            extended_refinements = deepcopy(extended_profile.refine_rules)
-+            updated_refinements = self._subtract_refinements(extended_refinements)
-             updated_refinements.update(self.refine_rules)
-             self.refine_rules = updated_refinements
- 
-@@ -50,6 +52,18 @@ def resolve(self, all_profiles):
- 
-         self.resolved = True
- 
-+    def _subtract_refinements(self, extended_refinements):
-+        """
-+        Given a dict of rule refinements from the extended profile,
-+        "undo" every refinement prefixed with '!' in this profile.
-+        """
-+        for rule, refinements in list(self.refine_rules.items()):
-+            if rule.startswith("!"):
-+                for prop, val in refinements:
-+                    extended_refinements[rule[1:]].remove((prop, val))
-+                del self.refine_rules[rule]
-+        return extended_refinements
-+
- 
- def create_parser():
-     parser = argparse.ArgumentParser()
-
-From 2ea270b1796139f42a1d56cbb31351b3f6ad3a6e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 9 Jul 2020 22:32:32 +0200
-Subject: [PATCH 10/18] Undo rule refinements done to zIPL rules
-
-Remove the zIPl rule refinementes from STIG profile
----
- rhel8/profiles/stig.profile | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index 69d5222a32..53647475aa 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -55,3 +55,5 @@ selections:
-     - "!zipl_pti_argument"
-     - "!zipl_slub_debug_argument"
-     - "!zipl_vsyscall_argument"
-+    - "!zipl_vsyscall_argument.role=unscored"
-+    - "!zipl_vsyscall_argument.severity=info"
-
-From 90d62ba0cd088eb95aa151fe08a9c3c9fd959a00 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 09:38:57 +0200
-Subject: [PATCH 11/18] Update stable test for OSPP Profile
-
-I just copied the resolved profile to profile_stability directory.
----
- tests/data/profile_stability/rhel8/ospp.profile | 14 +++++++++++---
- 1 file changed, 11 insertions(+), 3 deletions(-)
-
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index 08dcccf24c..5aa3592496 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -168,6 +168,7 @@ selections:
- - service_rngd_enabled
- - service_systemd-coredump_disabled
- - service_usbguard_enabled
-+- ssh_client_rekey_limit
- - sshd_disable_empty_passwords
- - sshd_disable_gssapi_auth
- - sshd_disable_kerb_auth
-@@ -213,8 +214,14 @@ selections:
- - sysctl_user_max_user_namespaces
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
-+- zipl_audit_argument
-+- zipl_audit_backlog_limit_argument
- - zipl_bls_entries_only
- - zipl_bootmap_is_up_to_date
-+- zipl_page_poison_argument
-+- zipl_pti_argument
-+- zipl_slub_debug_argument
-+- zipl_vsyscall_argument
- - var_sshd_set_keepalive=0
- - var_rekey_limit_size=1G
- - var_rekey_limit_time=1hour
-@@ -238,11 +245,12 @@ selections:
- - var_accounts_passwords_pam_faillock_deny=3
- - var_accounts_passwords_pam_faillock_fail_interval=900
- - var_accounts_passwords_pam_faillock_unlock_time=never
-+- var_ssh_client_rekey_limit_size=1G
-+- var_ssh_client_rekey_limit_time=1hour
- - grub2_vsyscall_argument.role=unscored
- - grub2_vsyscall_argument.severity=info
- - sysctl_user_max_user_namespaces.role=unscored
- - sysctl_user_max_user_namespaces.severity=info
--- ssh_client_rekey_limit
--- var_ssh_client_rekey_limit_size=1G
--- var_ssh_client_rekey_limit_time=1hour
-+- zipl_vsyscall_argument.role=unscored
-+- zipl_vsyscall_argument.severity=info
- title: Protection Profile for General Purpose Operating Systems
-
-From b5d5b0f1d4319663aba9f051fc01f5209234da6f Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 15:15:25 +0200
-Subject: [PATCH 12/18] zipl_bls_entries_option: Add test scenarios
-
----
- .../tests/correct_option.pass.sh                 | 16 ++++++++++++++++
- .../tests/missing_in_cmdline.fail.sh             | 14 ++++++++++++++
- .../tests/missing_in_entry.fail.sh               | 14 ++++++++++++++
- 3 files changed, 44 insertions(+)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-new file mode 100644
-index 0000000000..a9bd49dd0b
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-@@ -0,0 +1,16 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+# Make sure boot loader entries contain audit=1
-+for file in /boot/loader/entries/*.conf
-+do
-+    if ! grep -q '^options.*audit=1.*$' "$file" ; then
-+        sed -i '/^options / s/$/audit=1/' "$file"
-+    fi
-+done
-+
-+# Make sure /etc/kernel/cmdline contains audit=1
-+if ! grep -q '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-+    echo "audit=1" >> /etc/kernel/cmdline
-+fi
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-new file mode 100644
-index 0000000000..d4d1d978c8
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-@@ -0,0 +1,14 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+# Make sure boot loader entries contain audit=1
-+for file in /boot/loader/entries/*.conf
-+do
-+    if ! grep -q '^options.*audit=1.*$' "$file" ; then
-+        sed -i '/^options / s/$/audit=1/' "$file"
-+    fi
-+done
-+
-+# Make sure /etc/kernel/cmdline doesn't contain audit=1
-+sed -Ei 's/(^.*)audit=1(.*?)$/\1\2/' /etc/kernel/cmdline || true
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-new file mode 100644
-index 0000000000..3e412c0542
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-@@ -0,0 +1,14 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+# Remove audit=1 from all boot entries
-+sed -Ei 's/(^options.*\s)audit=1(.*?)$/\1\2/' /boot/loader/entries/*
-+# But make sure one boot loader entry contains audit=1
-+sed -i '/^options / s/$/audit=1/' /boot/loader/entries/*rescue.conf
-+sed -Ei 's/(^options.*\s)\$kernelopts(.*?)$/\1\2/' /boot/loader/entries/*rescue.conf
-+
-+# Make sure /etc/kernel/cmdline contains audit=1
-+if ! grep -q '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-+    echo "audit=1" >> /etc/kernel/cmdline
-+fi
-
-From 3b52ab44e043adb289ef0a96798cffaf3e1f35a1 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 15:34:52 +0200
-Subject: [PATCH 13/18] zipl_bls_entries_option: Remove hardcoded values
-
-The template shouldn't have any hardcoded values.
----
- shared/templates/template_BASH_zipl_bls_entries_option | 3 +--
- 1 file changed, 1 insertion(+), 2 deletions(-)
-
-diff --git a/shared/templates/template_BASH_zipl_bls_entries_option b/shared/templates/template_BASH_zipl_bls_entries_option
-index 9fc8865486..dde8c948f7 100644
---- a/shared/templates/template_BASH_zipl_bls_entries_option
-+++ b/shared/templates/template_BASH_zipl_bls_entries_option
-@@ -7,6 +7,5 @@ grubby --update-kernel=ALL --args="{{{ ARG_NAME_VALUE }}}"
- if [ ! -f /etc/kernel/cmdline ]; then
-     echo "{{{ ARG_NAME_VALUE }}}" >> /etc/kernel/cmdline
- elif ! grep -q '^(.*\s)?{{{ ARG_NAME_VALUE }}}(\s.*)?$' /etc/kernel/cmdline; then
--    echo " audit=1" >> /etc/kernel/cmdline
--    sed -Ei 's/^(.*)$/\1 audit=1/' /etc/kernel/cmdline
-+    sed -Ei 's/^(.*)$/\1 {{{ ARG_NAME_VALUE }}}/' /etc/kernel/cmdline
- fi
-
-From 68bff71c7f60a7c68cf0bd9aa153f8a78ec02b7d Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 16:08:26 +0200
-Subject: [PATCH 14/18] Improve conditional check for the grubby command
-
-Let's not trust that /boot/loader/entries/ only contains *.conf files.
-Count the number of conf files and how many set the propper options.
----
- .../template_ANSIBLE_zipl_bls_entries_option       | 14 +++++++++-----
- 1 file changed, 9 insertions(+), 5 deletions(-)
-
-diff --git a/shared/templates/template_ANSIBLE_zipl_bls_entries_option b/shared/templates/template_ANSIBLE_zipl_bls_entries_option
-index c0cb131b82..bccad2267c 100644
---- a/shared/templates/template_ANSIBLE_zipl_bls_entries_option
-+++ b/shared/templates/template_ANSIBLE_zipl_bls_entries_option
-@@ -6,18 +6,22 @@
- 
- - name: "Ensure BLS boot entries options contain {{{ ARG_NAME_VALUE }}}"
-   block:
--    - name: "Check if any boot entry misses {{{ ARG_NAME_VALUE }}}"
-+    - name: "Check how many boot entries exist "
-+      find:
-+        paths: "/boot/loader/entries/"
-+        patterns: "*.conf"
-+      register: n_entries
-+
-+    - name: "Check how many boot entries set {{{ ARG_NAME_VALUE }}}"
-       find:
-         paths: "/boot/loader/entries/"
-         contains: "^options .*{{{ ARG_NAME_VALUE }}}.*$"
-         patterns: "*.conf"
--      register: entries_options
-+      register: n_entries_options
- 
-     - name: "Update boot entries options"
-       command: grubby --update-kernel=ALL --args="{{{ ARG_NAME_VALUE }}}"
--      when: entries_options is defined and entries_options.examined != entries_options.matched
--      # The conditional above assumes that only *.conf files are present in /boot/loader/entries
--      # Then, the number of conf files is the same as examined files
-+      when: n_entries is defined and n_entries_options is defined and n_entries.matched != n_entries_options.matched
- 
-     - name: "Check if /etc/kernel/cmdline exists"
-       stat:
-
-From 79c60bb40288c17381bf1e4a84e6cfd300bd8446 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 16:17:27 +0200
-Subject: [PATCH 15/18] zipl_bls_entries_option: Fix sed in test scenario
-
-Append "audit=1" space from last option.
----
- .../zipl_audit_argument/tests/correct_option.pass.sh            | 2 +-
- .../zipl_audit_argument/tests/missing_in_cmdline.fail.sh        | 2 +-
- .../zipl_audit_argument/tests/missing_in_entry.fail.sh          | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-index a9bd49dd0b..5fcbcc5667 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-@@ -6,7 +6,7 @@
- for file in /boot/loader/entries/*.conf
- do
-     if ! grep -q '^options.*audit=1.*$' "$file" ; then
--        sed -i '/^options / s/$/audit=1/' "$file"
-+        sed -i '/^options / s/$/ audit=1/' "$file"
-     fi
- done
- 
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-index d4d1d978c8..b75165f904 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-@@ -6,7 +6,7 @@
- for file in /boot/loader/entries/*.conf
- do
-     if ! grep -q '^options.*audit=1.*$' "$file" ; then
--        sed -i '/^options / s/$/audit=1/' "$file"
-+        sed -i '/^options / s/$/ audit=1/' "$file"
-     fi
- done
- 
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-index 3e412c0542..e3d342d533 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-@@ -5,7 +5,7 @@
- # Remove audit=1 from all boot entries
- sed -Ei 's/(^options.*\s)audit=1(.*?)$/\1\2/' /boot/loader/entries/*
- # But make sure one boot loader entry contains audit=1
--sed -i '/^options / s/$/audit=1/' /boot/loader/entries/*rescue.conf
-+sed -i '/^options / s/$/ audit=1/' /boot/loader/entries/*rescue.conf
- sed -Ei 's/(^options.*\s)\$kernelopts(.*?)$/\1\2/' /boot/loader/entries/*rescue.conf
- 
- # Make sure /etc/kernel/cmdline contains audit=1
-
-From d513177d2cea39db364a0ff39a599ded36a25395 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 16:29:06 +0200
-Subject: [PATCH 16/18] Extend scenarios platform and allow remediation
-
-These test scenarios can be run on any OS that supports BLS and provides
-grubby.
-But it will evaluate to not applicable if the OS doesn't use zIPL (i.e.:
-has s390utils-base installed).
----
- .../zipl_audit_argument/tests/correct_option.pass.sh           | 3 +--
- .../zipl_audit_argument/tests/missing_in_cmdline.fail.sh       | 3 +--
- .../zipl_audit_argument/tests/missing_in_entry.fail.sh         | 3 +--
- 3 files changed, 3 insertions(+), 6 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-index 5fcbcc5667..73ed0eae0f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-@@ -1,6 +1,5 @@
- #!/bin/bash
--# platform = Red Hat Enterprise Linux 8
--# remediation = none
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
- 
- # Make sure boot loader entries contain audit=1
- for file in /boot/loader/entries/*.conf
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-index b75165f904..3af83d30d8 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_cmdline.fail.sh
-@@ -1,6 +1,5 @@
- #!/bin/bash
--# platform = Red Hat Enterprise Linux 8
--# remediation = none
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
- 
- # Make sure boot loader entries contain audit=1
- for file in /boot/loader/entries/*.conf
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-index e3d342d533..142f75ba60 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-@@ -1,6 +1,5 @@
- #!/bin/bash
--# platform = Red Hat Enterprise Linux 8
--# remediation = none
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
- 
- # Remove audit=1 from all boot entries
- sed -Ei 's/(^options.*\s)audit=1(.*?)$/\1\2/' /boot/loader/entries/*
-
-From 2e841722d30551c86f14558ff39bdaa5dda55711 Mon Sep 17 00:00:00 2001
-From: Watson Yuuma Sato 
-Date: Fri, 10 Jul 2020 16:35:55 +0200
-Subject: [PATCH 17/18] Update comment in OVAL zipl_bls_entries_option
-
-Co-authored-by: vojtapolasek 
----
- shared/templates/template_OVAL_zipl_bls_entries_option | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/shared/templates/template_OVAL_zipl_bls_entries_option b/shared/templates/template_OVAL_zipl_bls_entries_option
-index 9af1bcfbee..502d5e7d9a 100644
---- a/shared/templates/template_OVAL_zipl_bls_entries_option
-+++ b/shared/templates/template_OVAL_zipl_bls_entries_option
-@@ -7,7 +7,7 @@
-     
-     
-       
-+      comment="Check if {{{ ARG_NAME_VALUE }}} is present in the 'options' line in /boot/loader/entries/*.conf" />
-       
-     
-
-From 9bd0afbde47ef368444ba1785da593980e6e00aa Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 10 Jul 2020 17:15:46 +0200
-Subject: [PATCH 18/18] zipl_bls_entries_option: Supress grep error messages
-
-/etc/kernel/cmdline is not always present. Lest suppress any error
-message about absent file in the test scenarios.
----
- .../zipl_audit_argument/tests/correct_option.pass.sh            | 2 +-
- .../zipl_audit_argument/tests/missing_in_entry.fail.sh          | 2 +-
- 2 files changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-index 73ed0eae0f..7a828837fe 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/correct_option.pass.sh
-@@ -10,6 +10,6 @@ do
- done
- 
- # Make sure /etc/kernel/cmdline contains audit=1
--if ! grep -q '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-+if ! grep -qs '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-     echo "audit=1" >> /etc/kernel/cmdline
- fi
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-index 142f75ba60..5650cc0a74 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/tests/missing_in_entry.fail.sh
-@@ -8,6 +8,6 @@ sed -i '/^options / s/$/ audit=1/' /boot/loader/entries/*rescue.conf
- sed -Ei 's/(^options.*\s)\$kernelopts(.*?)$/\1\2/' /boot/loader/entries/*rescue.conf
- 
- # Make sure /etc/kernel/cmdline contains audit=1
--if ! grep -q '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-+if ! grep -qs '^(.*\s)?audit=1(\s.*)?$' /etc/kernel/cmdline ; then
-     echo "audit=1" >> /etc/kernel/cmdline
- fi
diff --git a/SOURCES/scap-security-guide-0.1.52-fix_hipaa_description.patch b/SOURCES/scap-security-guide-0.1.52-fix_hipaa_description.patch
deleted file mode 100644
index 801edff..0000000
--- a/SOURCES/scap-security-guide-0.1.52-fix_hipaa_description.patch
+++ /dev/null
@@ -1,43 +0,0 @@
-From 5a5b3bdead44bd24fb138bd7b9785d4e0809ff4b Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Tue, 28 Jul 2020 13:22:58 +0200
-Subject: [PATCH 1/2] update wording for rhel7 profile
-
----
- rhel7/profiles/hipaa.profile | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/rhel7/profiles/hipaa.profile b/rhel7/profiles/hipaa.profile
-index 4310561323..000441de52 100644
---- a/rhel7/profiles/hipaa.profile
-+++ b/rhel7/profiles/hipaa.profile
-@@ -12,6 +12,7 @@ description: |-
- 
-     This profile configures Red Hat Enterprise Linux 7 to the HIPAA Security
-     Rule identified for securing of electronic protected health information.
-+    Use of this profile in no way guarantees or makes claims against legal compliance against the HIPAA Security Rule(s).
- 
- selections:
-     - grub2_password
-
-From 0c5cc87c4f8aaed8eb199b77440ae0dc64658e4a Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Tue, 28 Jul 2020 13:23:18 +0200
-Subject: [PATCH 2/2] update wording for rhel8 profile
-
----
- rhel8/profiles/hipaa.profile | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/rhel8/profiles/hipaa.profile b/rhel8/profiles/hipaa.profile
-index 8d20f9019c..0cb7fbed1f 100644
---- a/rhel8/profiles/hipaa.profile
-+++ b/rhel8/profiles/hipaa.profile
-@@ -12,6 +12,7 @@ description: |-
- 
-     This profile configures Red Hat Enterprise Linux 8 to the HIPAA Security
-     Rule identified for securing of electronic protected health information.
-+    Use of this profile in no way guarantees or makes claims against legal compliance against the HIPAA Security Rule(s).   
- 
- selections:
-     - grub2_password
diff --git a/SOURCES/scap-security-guide-0.1.52-fix_scapval_call_PR_6005.patch b/SOURCES/scap-security-guide-0.1.52-fix_scapval_call_PR_6005.patch
deleted file mode 100644
index 36b46ee..0000000
--- a/SOURCES/scap-security-guide-0.1.52-fix_scapval_call_PR_6005.patch
+++ /dev/null
@@ -1,52 +0,0 @@
-From 4c54b1cfb05961bde8248e03d27cabeca967e211 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 17 Aug 2020 10:59:15 +0200
-Subject: [PATCH] Remove SCAP-1.3 SCAPVAL workarounds
-
-These changes to the DS cause SRC-330 to fail in SCAPVAL-1.3.5.
-In SCAPVAL-1.3.5 was fixed and these false positive workarounds are not
-necessary anymore.
----
- tests/run_scapval.py | 26 --------------------------
- 1 file changed, 26 deletions(-)
-
-diff --git a/tests/run_scapval.py b/tests/run_scapval.py
-index e1dd806ca1..bc2655b9fd 100755
---- a/tests/run_scapval.py
-+++ b/tests/run_scapval.py
-@@ -46,35 +46,9 @@ def process_results(result_path):
-     return ret_val
- 
- 
--def workaround_datastream(datastream_path):
--    tree = ET.parse(datastream_path)
--    root = tree.getroot()
--    # group_id and user_id cannot be zero
--    # tracked at https://github.com/OVAL-Community/OVAL/issues/23
--    for group_id_element in root.findall(".//{%s}group_id" % oval_unix_ns):
--        if group_id_element.text is not None:
--            group_id_element.text = "-1"
--    for user_id_element in root.findall(".//{%s}user_id" % oval_unix_ns):
--        if user_id_element.text is not None:
--            user_id_element.text = "-1"
--    # OCIL checks for security_patches_up_to_date is causing fail
--    # of SRC-377, when requirement is about OVAL checks.
--    rule_id = "xccdf_org.ssgproject.content_rule_security_patches_up_to_date"
--    for rule in root.findall(".//{%s}Rule[@id=\"%s\"]" % (xccdf_ns, rule_id)):
--        for check in rule.findall("{%s}check" % xccdf_ns):
--            system = check.get("system")
--            if system == "http://scap.nist.gov/schema/ocil/2":
--                rule.remove(check)
--    output_path = datastream_path + ".workaround.xml"
--    tree.write(output_path)
--    return output_path
--
--
- def test_datastream(datastream_path,  scapval_path, scap_version):
-     result_path = datastream_path + ".result.xml"
-     report_path = datastream_path + ".report.html"
--    if scap_version == "1.3":
--        datastream_path = workaround_datastream(datastream_path)
-     scapval_command = [
-             "java",
-             "-Xmx1024m",
diff --git a/SOURCES/scap-security-guide-0.1.52-harden-openssl-crypto-policy_PR_5925.patch b/SOURCES/scap-security-guide-0.1.52-harden-openssl-crypto-policy_PR_5925.patch
deleted file mode 100644
index 4f0e114..0000000
--- a/SOURCES/scap-security-guide-0.1.52-harden-openssl-crypto-policy_PR_5925.patch
+++ /dev/null
@@ -1,408 +0,0 @@
-From 94ace689f800fde1453b986de02c1d0581174451 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 8 Jul 2020 17:37:50 +0200
-Subject: [PATCH 1/9] create rule, check, bash remediation
-
----
- .../bash/shared.sh                            |  9 +++++
- .../oval/shared.xml                           |  1 +
- .../harden_openssl_crypto_policy/rule.yml     | 33 +++++++++++++++++++
- shared/references/cce-redhat-avail.txt        |  2 --
- 4 files changed, 43 insertions(+), 2 deletions(-)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
-new file mode 100644
-index 0000000000..9838a13c95
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
-@@ -0,0 +1,9 @@
-+# platform = Oracle Linux 8,Red Hat Enterprise Linux 8,Red Hat Virtualization 4,multi_platform_fedora
-+
-+cp="Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256"
-+file=/etc/crypto-policies/local.d/opensslcnf-ospp.config
-+
-+#blank line at the begining to ease later readibility
-+echo '' > "$file"
-+echo "$cp" >> "$file"
-+update-crypto-policies
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
-new file mode 100644
-index 0000000000..09199ce4da
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
-@@ -0,0 +1 @@
-+{{{ oval_check_config_file(path="/etc/crypto-policies/back-ends/opensslcnf.config", prefix_regex="^(?:.*\\n)*\s*", parameter="Ciphersuites", value="TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256", separator_regex="=", ) }}}
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-new file mode 100644
-index 0000000000..afbdb36a23
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-@@ -0,0 +1,32 @@
-+documentation_complete: true
-+
-+prodtype: rhel8
-+
-+title: 'Harden OpenSSL Crypto Policy'
-+
-+description: |-
-+    Crypto Policies are means of enforcing certain cryptographic settings for selected applications including OpenSSL.
-+    OPenSSL is by default configured to modify its configuration based on currently configured Crypto-Policy. However, in certain cases it might be needed to override the Crypto Policy specific to OpenSSL r and leave rest of the Crypto Policy intact.
-+    This can be done by dropping a file named opensslcnf-xxx.config, replacing xxx with arbitrary identifier, into /etc/crypto-policies/local.d. This has to be followed by running update-crypto-policies so that changes are applied.
-+    Changes are propagated into /etc/crypto-policies/back-ends/opensslcnf.config. This rule checks if this file contains predefined Ciphersuites  variable configured with predefined value.
-+
-+rationale: |-
-+    The Common Criteria requirements specify that certain parameters for OpenSSL are configured e.g. cipher suites. Currently particular requirements specified by CC are stricter compared to any existing Crypto Policy.
-+
-+severity: medium
-+
-+identifiers:
-+    cce@rhel8: 84286-4
-+
-+references:
-+    nist: AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13,SC-12(2),SC-12(3)
-+    ospp : FCS_SSHS_EXT.1
-+    srg: SRG-OS-000250-GPOS-00093,SRG-OS-000033-GPOS-00014,SRG-OS-000120-GPOS-00061
-+
-+ocil_clause: 'Crypto Policy for OpenSSL is not configured according to CC requirements'
-+
-+ocil: |-
-+    To verify if the OpenSSL uses defined Crypto Policy, run:
-+    
$ grep 'Ciphersuites' /etc/crypto-policies/back-ends/opensslcnf.config | tail -n 1

-+    and verify that the line matches
-+    
84285-6

-diff --git a/shared/references/cce-redhat-avail.txt b/shared/references/cce-redhat-avail.txt
-index afc0d80417..01b321b6d5 100644
---- a/shared/references/cce-redhat-avail.txt
-+++ b/shared/references/cce-redhat-avail.txt
-@@ -904,8 +904,6 @@ CCE-84281-5
- CCE-84282-3
- CCE-84283-1
- CCE-84284-9
--CCE-84285-6
--CCE-84286-4
- CCE-84287-2
- CCE-84288-0
- CCE-84289-8
-
-From ddc8380b44f907872f6f3b9b0d10421329e3c0a1 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 8 Jul 2020 17:38:32 +0200
-Subject: [PATCH 2/9] add tests
-
----
- .../harden_openssl_crypto_policy/tests/correct.pass.sh    | 7 +++++++
- .../tests/correct_commented.fail.sh                       | 7 +++++++
- .../tests/correct_followed_by_incorrect.fail.sh           | 8 ++++++++
- .../tests/empty_policy.fail.sh                            | 7 +++++++
- .../tests/incorrect_followed_by_correct.pass.sh           | 8 ++++++++
- .../tests/incorrect_policy.fail.sh                        | 7 +++++++
- .../tests/missing_file.fail.sh                            | 7 +++++++
- 7 files changed, 51 insertions(+)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct.pass.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_commented.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_followed_by_incorrect.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/empty_policy.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_followed_by_correct.pass.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_policy.fail.sh
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/missing_file.fail.sh
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct.pass.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct.pass.sh
-new file mode 100644
-index 0000000000..9e59b30bd2
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct.pass.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" > "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_commented.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_commented.fail.sh
-new file mode 100644
-index 0000000000..91863849b3
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_commented.fail.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "#Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" > "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_followed_by_incorrect.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_followed_by_incorrect.fail.sh
-new file mode 100644
-index 0000000000..f44957d3e1
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/correct_followed_by_incorrect.fail.sh
-@@ -0,0 +1,8 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" > "$configfile"
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256" >> "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/empty_policy.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/empty_policy.fail.sh
-new file mode 100644
-index 0000000000..5b14fe8ef4
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/empty_policy.fail.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "Ciphersuites=" > "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_followed_by_correct.pass.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_followed_by_correct.pass.sh
-new file mode 100644
-index 0000000000..6be3bb2ffa
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_followed_by_correct.pass.sh
-@@ -0,0 +1,8 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256" > "$configfile"
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" >> "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_policy.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_policy.fail.sh
-new file mode 100644
-index 0000000000..b4fd0f97be
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/incorrect_policy.fail.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+echo "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256" > "$configfile"
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/missing_file.fail.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/missing_file.fail.sh
-new file mode 100644
-index 0000000000..2d11d227cb
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/tests/missing_file.fail.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = multi_platform_fedora,Red Hat Enterprise Linux 8
-+# profiles = xccdf_org.ssgproject.content_profile_ospp
-+
-+configfile=/etc/crypto-policies/back-ends/opensslcnf.config
-+
-+rm -f "$configfile"
-
-From b08a7f3889e4592dc54a431aa4cfb6983990daba Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 9 Jul 2020 09:05:38 +0200
-Subject: [PATCH 3/9] remove blank line from remediation
-
----
- .../crypto/harden_openssl_crypto_policy/bash/shared.sh         | 3 +--
- 1 file changed, 1 insertion(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
-index 9838a13c95..be6f84f83d 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/bash/shared.sh
-@@ -3,7 +3,6 @@
- cp="Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256"
- file=/etc/crypto-policies/local.d/opensslcnf-ospp.config
- 
--#blank line at the begining to ease later readibility
--echo '' > "$file"
-+
- echo "$cp" >> "$file"
- update-crypto-policies
-
-From d249fbe6f2b0cc8b6cd8a0bb02b03ead04e1dd12 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 9 Jul 2020 09:06:02 +0200
-Subject: [PATCH 4/9] fix separator regex in oval
-
----
- .../crypto/harden_openssl_crypto_policy/oval/shared.xml         | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
-index 09199ce4da..37be62ee39 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/oval/shared.xml
-@@ -1 +1 @@
--{{{ oval_check_config_file(path="/etc/crypto-policies/back-ends/opensslcnf.config", prefix_regex="^(?:.*\\n)*\s*", parameter="Ciphersuites", value="TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256", separator_regex="=", ) }}}
-+{{{ oval_check_config_file(path="/etc/crypto-policies/back-ends/opensslcnf.config", prefix_regex="^(?:.*\\n)*\s*", parameter="Ciphersuites", value="TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256", separator_regex="\s*=\s*", ) }}}
-
-From 0b203279dde378cd45f05ec93a9653e1bc3b6002 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Thu, 9 Jul 2020 09:06:29 +0200
-Subject: [PATCH 5/9] reformat rule, fix wrong ocil
-
----
- .../harden_openssl_crypto_policy/rule.yml     | 22 ++++++++++++++-----
- 1 file changed, 16 insertions(+), 6 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-index afbdb36a23..d019d6cd32 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-@@ -5,13 +5,23 @@ prodtype: rhel8
- title: 'Harden OpenSSL Crypto Policy'
- 
- description: |-
--    Crypto Policies are means of enforcing certain cryptographic settings for selected applications including OpenSSL.
--    OPenSSL is by default configured to modify its configuration based on currently configured Crypto-Policy. However, in certain cases it might be needed to override the Crypto Policy specific to OpenSSL r and leave rest of the Crypto Policy intact.
--    This can be done by dropping a file named opensslcnf-xxx.config, replacing xxx with arbitrary identifier, into /etc/crypto-policies/local.d. This has to be followed by running update-crypto-policies so that changes are applied.
--    Changes are propagated into /etc/crypto-policies/back-ends/opensslcnf.config. This rule checks if this file contains predefined Ciphersuites  variable configured with predefined value.
-+    Crypto Policies are means of enforcing certain cryptographic settings for
-+    selected applications including OpenSSL. OPenSSL is by default configured to
-+    modify its configuration based on currently configured Crypto-Policy.
-+    However, in certain cases it might be needed to override the Crypto Policy
-+    specific to OpenSSL r and leave rest of the Crypto Policy intact. This can
-+    be done by dropping a file named opensslcnf-xxx.config, replacing
-+    xxx with arbitrary identifier, into
-+    /etc/crypto-policies/local.d. This has to be followed by running
-+    update-crypto-policies so that changes are applied. Changes are
-+    propagated into /etc/crypto-policies/back-ends/opensslcnf.config.
-+    This rule checks if this file contains predefined Ciphersuites
-+    variable configured with predefined value.
- 
- rationale: |-
--    The Common Criteria requirements specify that certain parameters for OpenSSL are configured e.g. cipher suites. Currently particular requirements specified by CC are stricter compared to any existing Crypto Policy.
-+    The Common Criteria requirements specify that certain parameters for OpenSSL
-+    are configured e.g. cipher suites. Currently particular requirements
-+    specified by CC are stricter compared to any existing Crypto Policy.
- 
- severity: medium
- 
-@@ -30,4 +40,4 @@ ocil: |-
-     To verify if the OpenSSL uses defined Crypto Policy, run:
-     
$ grep 'Ciphersuites' /etc/crypto-policies/back-ends/opensslcnf.config | tail -n 1

-     and verify that the line matches
--    
84285-6

-+    
Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256

-
-From aa2555bdfe67ab41978ae92924580527c7a725eb Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 13 Jul 2020 09:49:34 +0200
-Subject: [PATCH 6/9] update references
-
----
- .../integrity/crypto/harden_openssl_crypto_policy/rule.yml    | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-index d019d6cd32..075e381906 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-@@ -31,8 +31,8 @@ identifiers:
- 
- references:
-     nist: AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13,SC-12(2),SC-12(3)
--    ospp : FCS_SSHS_EXT.1
--    srg: SRG-OS-000250-GPOS-00093,SRG-OS-000033-GPOS-00014,SRG-OS-000120-GPOS-00061
-+    ospp: FCS_TLSC_EXT.1.1
-+    srg: SRG-OS-000250-GPOS-00093
- 
- ocil_clause: 'Crypto Policy for OpenSSL is not configured according to CC requirements'
- 
-
-From c4e0e35f3dc4abb1cea952aed4216499c622f1cf Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Mon, 13 Jul 2020 09:49:48 +0200
-Subject: [PATCH 7/9] add ansible remediation
-
----
- .../ansible/shared.yml                           | 16 ++++++++++++++++
- 1 file changed, 16 insertions(+)
- create mode 100644 linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/ansible/shared.yml
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/ansible/shared.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/ansible/shared.yml
-new file mode 100644
-index 0000000000..d5c2c2b9f7
---- /dev/null
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/ansible/shared.yml
-@@ -0,0 +1,16 @@
-+# platform = Red Hat Enterprise Linux 8
-+# reboot = true
-+# strategy = restrict
-+# complexity = low
-+# disruption = low
-+
-+- name: "Ensure that the correct crypto policy configuration exists in /etc/crypto-policies/local.d/opensslcnf-ospp.config"
-+  lineinfile:
-+    path: "/etc/crypto-policies/local.d/opensslcnf-ospp.config"
-+    line: "Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256"
-+    create: yes
-+    insertafter: EOF
-+
-+- name: "Update system crypto policy for changes to take effect"
-+  command:
-+    cmd: "update-crypto-policies"
-
-From 3a33b284dc3da993b1b98e75f805ebf018d7f2e9 Mon Sep 17 00:00:00 2001
-From: vojtapolasek 
-Date: Wed, 15 Jul 2020 09:26:11 +0200
-Subject: [PATCH 8/9] fix typos
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Co-authored-by: Jan Černý 
----
- .../integrity/crypto/harden_openssl_crypto_policy/rule.yml  | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-index 075e381906..ce0351aa34 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-@@ -6,10 +6,10 @@ title: 'Harden OpenSSL Crypto Policy'
- 
- description: |-
-     Crypto Policies are means of enforcing certain cryptographic settings for
--    selected applications including OpenSSL. OPenSSL is by default configured to
--    modify its configuration based on currently configured Crypto-Policy.
-+    selected applications including OpenSSL. OpenSSL is by default configured to
-+    modify its configuration based on currently configured Crypto Policy.
-     However, in certain cases it might be needed to override the Crypto Policy
--    specific to OpenSSL r and leave rest of the Crypto Policy intact. This can
-+    specific to OpenSSL and leave rest of the Crypto Policy intact. This can
-     be done by dropping a file named opensslcnf-xxx.config, replacing
-     xxx with arbitrary identifier, into
-     /etc/crypto-policies/local.d. This has to be followed by running
-
-From e5fa539ea5274e723a428a835673598899a301fa Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 15 Jul 2020 09:36:06 +0200
-Subject: [PATCH 9/9] update rule references
-
----
- .../integrity/crypto/harden_openssl_crypto_policy/rule.yml    | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-index ce0351aa34..0cbead2a6d 100644
---- a/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/harden_openssl_crypto_policy/rule.yml
-@@ -30,8 +30,8 @@ identifiers:
- 
- references:
--    nist: AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13,SC-12(2),SC-12(3)
-+    nist: SC-8(1),SC-13
-     ospp: FCS_TLSC_EXT.1.1
--    srg: SRG-OS-000250-GPOS-00093
-+    srg: SRG-OS-000396-GPOS-00176,SRG-OS-000424-GPOS-00188,SRG-OS-000478-GPOS-00223
- 
- ocil_clause: 'Crypto Policy for OpenSSL is not configured according to CC requirements'
- 
diff --git a/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_PR_6007.patch b/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_PR_6007.patch
deleted file mode 100644
index 88f8237..0000000
--- a/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_PR_6007.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From eb3a18cea5776038d0aeef0299083fcd282a0177 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Mon, 17 Aug 2020 15:56:40 +0200
-Subject: [PATCH] Add a missing Crypto Policy rule to OSPP.
-
-The rule fell out by mistake, this addition complements #4682
----
- rhel8/profiles/ospp.profile                     | 1 +
- tests/data/profile_stability/rhel8/ospp.profile | 1 +
- tests/data/profile_stability/rhel8/stig.profile | 5 +++--
- 3 files changed, 5 insertions(+), 2 deletions(-)
-
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index 5b5b5b711a..a651885eef 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -235,6 +235,7 @@ selections:
-     - enable_fips_mode
-     - var_system_crypto_policy=fips_ospp
-     - configure_crypto_policy
-+    - configure_ssh_crypto_policy
-     - configure_bind_crypto_policy
-     - configure_openssl_crypto_policy
-     - configure_libreswan_crypto_policy
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index 5aa3592496..13c4e6b08d 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -62,6 +62,7 @@ selections:
- - configure_kerberos_crypto_policy
- - configure_libreswan_crypto_policy
- - configure_openssl_crypto_policy
-+- configure_ssh_crypto_policy
- - configure_tmux_lock_after_time
- - configure_tmux_lock_command
- - configure_usbguard_auditbackend
-diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
-index 9b164eb5c2..c7fe02169a 100644
---- a/tests/data/profile_stability/rhel8/stig.profile
-+++ b/tests/data/profile_stability/rhel8/stig.profile
-@@ -77,6 +77,7 @@ selections:
- - configure_kerberos_crypto_policy
- - configure_libreswan_crypto_policy
- - configure_openssl_crypto_policy
-+- configure_ssh_crypto_policy
- - configure_tmux_lock_after_time
- - configure_tmux_lock_command
- - configure_usbguard_auditbackend
diff --git a/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_srg-PR_6008.patch b/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_srg-PR_6008.patch
deleted file mode 100644
index c469fe6..0000000
--- a/SOURCES/scap-security-guide-0.1.52-ospp_missing_ssh_srg-PR_6008.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-From 87e62e90df9995de6aca436e9242c0ac4d72e136 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Mat=C4=9Bj=20T=C3=BD=C4=8D?= 
-Date: Tue, 18 Aug 2020 13:55:12 +0200
-Subject: [PATCH] Added SRG to configure_ssh_crypto_policy
-
-https://www.stigviewer.com/stig/general_purpose_operating_system_srg/2016-04-25/finding/V-56935
----
- .../integrity/crypto/configure_ssh_crypto_policy/rule.yml        | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml b/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml
-index e2dd99dbb5..51788a3226 100644
---- a/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml
-+++ b/linux_os/guide/system/software/integrity/crypto/configure_ssh_crypto_policy/rule.yml
-@@ -24,6 +24,7 @@ identifiers:
- references:
-     nist: AC-17(a),AC-17(2),CM-6(a),MA-4(6),SC-13
-     cis@rhel8: 5.2.20
-+    srg: SRG-OS-000250-GPOS-00093
- 
- ocil_clause: 'the CRYPTO_POLICY variable is not set or is commented in the /etc/sysconfig/sshd'
- 
diff --git a/SOURCES/scap-security-guide-0.1.52-reorganize-zipl-rules_PR_5888.patch b/SOURCES/scap-security-guide-0.1.52-reorganize-zipl-rules_PR_5888.patch
deleted file mode 100644
index 81d85cc..0000000
--- a/SOURCES/scap-security-guide-0.1.52-reorganize-zipl-rules_PR_5888.patch
+++ /dev/null
@@ -1,884 +0,0 @@
-From 8cbec60a51b54df386bad72cdd82b83fbf9482fa Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 25 Jun 2020 18:29:31 +0200
-Subject: [PATCH 01/14] Add rule to check for zIPL conformance to BLS
-
-Instead of having each zIPL argument rule check for BLS compliance,
-let's split into its own rule.
----
- .../zipl_audit_argument/rule.yml              |  6 -----
- .../rule.yml                                  |  6 -----
- .../zipl_bls_entries_only/rule.yml            | 24 +++++++++++++++++++
- .../zipl_enable_selinux/rule.yml              |  6 -----
- .../zipl_page_poison_argument/rule.yml        |  6 -----
- .../zipl_pti_argument/rule.yml                |  6 -----
- .../zipl_slub_debug_argument/rule.yml         |  6 -----
- .../zipl_vsyscall_argument/rule.yml           |  6 -----
- 8 files changed, 24 insertions(+), 42 deletions(-)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-index 2d31ef8ee7..1211a53295 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To ensure all processes can be audited, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit=1
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to enable audit,
-@@ -30,10 +28,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\baudit=1\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable audit.
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index 40db232257..7d88e38686 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To improve the kernel capacity to queue all log events, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit_backlog_limit=8192
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
-@@ -31,10 +29,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\baudit_backlog_limit=0\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that does not extend the log events queue.
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-new file mode 100644
-index 0000000000..b6ccbb5343
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-@@ -0,0 +1,24 @@
-+documentation_complete: true
-+
-+prodtype: rhel8
-+
-+title: 'Ensure all zIPL boot entries are BLS compliant'
-+
-+description: |-
-+    Ensure that zIPL boot entries fully adheres to Boot Loader Specification (BLS)
-+    by checking that /etc/zipl.conf doesn't contain image = .
-+
-+rationale: |-
-+    {{{ full_name }}} adheres to Boot Loader Specification (BLS) and is the prefered method of
-+    configuration.
-+
-+severity: medium
-+
-+ocil_clause: 'a non BLS boot entry is configured'
-+
-+ocil: |-
-+  Check that no boot image file is specified in /etc/zipl.conf:
-+  
grep -R "^image\s*=" /etc/zipl.conf

-+  No line should be returned, if a line is returned non BLS compliant boot entries are configured for zIPL.
-+
-+platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-index 8d28d5495f..1c3bfeb246 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To ensure SELinux is not disabled at boot time,
-     check that no boot entry in /boot/loader/entries/*.conf has selinux=0
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
- rationale: |-
-@@ -27,10 +25,6 @@ ocil: |-
-     
sudo grep -L "^options\s+.*\bselinux=0\b" /boot/loader/entries/*.conf

-     No line should be returned, each line returned is a boot entry that disables SELinux.
- 
--    Check that no image file is specified in /etc/zipl.conf:
--    
grep -R "^image\s*=" /etc/zipl.conf

--    No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-     And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-     and /etc/zipl.conf:
-     
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-index 0a8e9a41e2..6dbfd501b7 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable poisoning of free pages,
-     check that all boot entries in /boot/loader/entries/*.conf have page_poison=1
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.

- 
-     To ensure that new kernels and boot entries continue to enable page poisoning,
-@@ -31,10 +29,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bpage_poison=1\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable page poisoning.
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-index 20c1448cc8..555fdf2b66 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable Kernel page-table isolation,
-     check that all boot entries in /boot/loader/entries/*.conf have pti=on
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to enable page-table isolation,
-@@ -30,10 +28,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bpti=on\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable page-table isolation .
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index 54ac688ea0..dd7865bf81 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable poisoning of SLUB/SLAB objects,
-     check that all boot entries in /boot/loader/entries/*.conf have slub_debug=P
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
-@@ -31,10 +29,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bslub_debug=P\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that does not enable poisoning.
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index c5979a2016..18b7ade460 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To disable use of virtual syscalls,
-     check that all boot entries in /boot/loader/entries/*.conf have vsyscall=none
-     included in its options.

--    Make sure /etc/zipl.conf doesn't contain image =  setting,
--    as {{{ full_name }}} adheres to Boot Loader Specification (BLS).

-     And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to disable virtual syscalls,
-@@ -28,10 +26,6 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bvsyscall=none\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't disable virtual syscalls.
- 
--  Check that no image file is specified in /etc/zipl.conf:
--  
grep -R "^image\s*=" /etc/zipl.conf

--  No line should be returned, if a line is returned zipl may load a different kernel than intended.
--
-   And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-   and /etc/zipl.conf:
-   
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-
-From 5e3b19077d781d0441595019429c653efafede8e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 2 Jul 2020 09:52:39 +0200
-Subject: [PATCH 02/14] zipl_bls_entries_only: Add OVAL and tests
-
----
- .../zipl_bls_entries_only/oval/shared.xml     | 27 +++++++++++++++++++
- .../tests/image_configured.fail.sh            |  6 +++++
- .../tests/no_image.pass.sh                    |  7 +++++
- 3 files changed, 40 insertions(+)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/image_configured.fail.sh
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/no_image.pass.sh
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-new file mode 100644
-index 0000000000..41e9773814
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-@@ -0,0 +1,27 @@
-+
-+  
-+    
-+      Ensure zIPL entries are BLS compliant
-+      {{{- oval_affected(products) }}}
-+      Check if /etc/zipl.conf configures any boot entry
-+    
-+    
-+      
-+    
-+  
-+
-+  
-+    
-+  
-+
-+  
-+    ^/etc/zipl.conf$
-+    ^image\s*=.*$
-+    1
-+  
-+
-+
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/image_configured.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/image_configured.fail.sh
-new file mode 100644
-index 0000000000..e3adb99638
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/image_configured.fail.sh
-@@ -0,0 +1,6 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+# Make sure no image configured in zipl config file
-+echo 'image = /boot/image' >> /etc/zipl.conf
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/no_image.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/no_image.pass.sh
-new file mode 100644
-index 0000000000..47626442f6
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/tests/no_image.pass.sh
-@@ -0,0 +1,7 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+# Make sure no image configured in zipl config file
-+sed -Ei '/^image\s*=/d' /etc/zipl.conf
-+true
-
-From 05e5b05b41080b7fbfaf42469cbb366eeffe35ec Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 2 Jul 2020 11:09:08 +0200
-Subject: [PATCH 03/14] zipl_bls_entries_only: Add no-remediation warning
-
-Automated remediation to remove non-BLS boot entries from /etc/zipl.conf
-is tricky and can lead to broken entries or removal of all of them.
----
- .../system/bootloader-zipl/zipl_bls_entries_only/rule.yml    | 5 +++++
- 1 file changed, 5 insertions(+)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-index b6ccbb5343..f792c5257f 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-@@ -22,3 +22,8 @@ ocil: |-
-   No line should be returned, if a line is returned non BLS compliant boot entries are configured for zIPL.
- 
- platform: machine
-+
-+warnings:
-+  - general: |-
-+      To prevent breakage or removal of all boot entries oconfigured in /etc/zipl.conf
-+      automated remediation for this rule is not available.
-
-From 53d811ed09cd63d4472a2133f3d9dc465dbd2962 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 25 Jun 2020 18:51:04 +0200
-Subject: [PATCH 04/14] Add rule to check hotness of zIPL bootmap
-
-Instead of having each zIPL argument rule check if zIPL bootmap is up to
-date, let's split it into its own rule.
----
- .../zipl_audit_argument/rule.yml              |  6 -----
- .../rule.yml                                  |  7 -----
- .../zipl_bootmap_is_up_to_date/rule.yml       | 27 +++++++++++++++++++
- .../zipl_enable_selinux/rule.yml              |  6 -----
- .../zipl_page_poison_argument/rule.yml        |  7 -----
- .../zipl_pti_argument/rule.yml                |  7 -----
- .../zipl_slub_debug_argument/rule.yml         |  7 -----
- .../zipl_vsyscall_argument/rule.yml           |  7 -----
- 8 files changed, 27 insertions(+), 47 deletions(-)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-index 1211a53295..624b4e7041 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_argument/rule.yml
-@@ -8,7 +8,6 @@ description: |-
-     To ensure all processes can be audited, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit=1
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


- 
-     To ensure that new kernels and boot entries continue to enable audit,
-     add audit=1 to /etc/kernel/cmdline.
-@@ -28,9 +27,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\baudit=1\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable audit.
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-index 7d88e38686..faf114591a 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_audit_backlog_limit_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To improve the kernel capacity to queue all log events, even those which start prior to the audit daemon,
-     check that all boot entries in /boot/loader/entries/*.conf have audit_backlog_limit=8192
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


--
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
-     add audit_backlog_limit=8192 to /etc/kernel/cmdline.
- 
-@@ -29,9 +27,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\baudit_backlog_limit=0\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that does not extend the log events queue.
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-new file mode 100644
-index 0000000000..082562d11e
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-@@ -0,0 +1,27 @@
-+documentation_complete: true
-+
-+prodtype: rhel8
-+
-+title: 'Ensure zIPL bootmap is up to date'
-+
-+description: |-
-+    Make sure that /boot/bootmap is up to date.

-+    Every time a boot entry or zIPL configuration is changed /boot/bootmap needs to
-+    be updated to reflect the changes.

-+    Run zipl command to generate an updated /boot/bootmap.
-+
-+rationale: |-
-+    The file /boot/bootmap contains all boot data, keeping it up to date is crucial to
-+    boot correct kernel and options.
-+
-+severity: medium
-+
-+ocil_clause: 'the bootmap is outdated'
-+
-+ocil: |-
-+  Make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
-+  and /etc/zipl.conf:
-+  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

-+  No line should be returned, if a line is returned /boot/bootmap is outdated and needs to be regenerated.
-+
-+platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-index 1c3bfeb246..b0bc0fc374 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_enable_selinux/rule.yml
-@@ -8,7 +8,6 @@ description: |-
-     To ensure SELinux is not disabled at boot time,
-     check that no boot entry in /boot/loader/entries/*.conf has selinux=0
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


- 
- rationale: |-
-     Disabling a major host protection feature, such as SELinux, at boot time prevents
-@@ -25,9 +24,4 @@ ocil: |-
-     
sudo grep -L "^options\s+.*\bselinux=0\b" /boot/loader/entries/*.conf

-     No line should be returned, each line returned is a boot entry that disables SELinux.
- 
--    And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--    and /etc/zipl.conf:
--    
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--    No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-index 6dbfd501b7..866664c01b 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_page_poison_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable poisoning of free pages,
-     check that all boot entries in /boot/loader/entries/*.conf have page_poison=1
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.

--
-     To ensure that new kernels and boot entries continue to enable page poisoning,
-     add page_poison=1 to /etc/kernel/cmdline.
- 
-@@ -29,9 +27,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bpage_poison=1\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable page poisoning.
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-index 555fdf2b66..2f02d9668c 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable Kernel page-table isolation,
-     check that all boot entries in /boot/loader/entries/*.conf have pti=on
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


--
-     To ensure that new kernels and boot entries continue to enable page-table isolation,
-     add pti=on to /etc/kernel/cmdline.
- 
-@@ -28,9 +26,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bpti=on\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't enable page-table isolation .
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-index dd7865bf81..0cb10d3cd8 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_slub_debug_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To enable poisoning of SLUB/SLAB objects,
-     check that all boot entries in /boot/loader/entries/*.conf have slub_debug=P
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


--
-     To ensure that new kernels and boot entries continue to extend the audit log events queue,
-     add slub_debug=P to /etc/kernel/cmdline.
- 
-@@ -29,9 +27,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bslub_debug=P\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that does not enable poisoning.
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-index 18b7ade460..f79adeb083 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_vsyscall_argument/rule.yml
-@@ -8,8 +8,6 @@ description: |-
-     To disable use of virtual syscalls,
-     check that all boot entries in /boot/loader/entries/*.conf have vsyscall=none
-     included in its options.

--    And run zipl command so that /boot/bootmap is updated.


--
-     To ensure that new kernels and boot entries continue to disable virtual syscalls,
-     add vsyscall=none to /etc/kernel/cmdline.
- 
-@@ -26,9 +24,4 @@ ocil: |-
-   
sudo grep -L "^options\s+.*\bvsyscall=none\b" /boot/loader/entries/*.conf

-   No line should be returned, each line returned is a boot entry that doesn't disable virtual syscalls.
- 
--  And make sure that /boot/bootmap is newer than /boot/loader/entries/*.conf
--  and /etc/zipl.conf:
--  
find /boot/loader/entries/*.conf /etc/zipl.conf -newer /boot/bootmap

--  No line should be returned, if a line is returned /boot/bootmap needs to be regenerated.
--
- platform: machine
-
-From b9f27383a09afbc6cef61bbbaad0f18f9ebec075 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 2 Jul 2020 15:59:31 +0200
-Subject: [PATCH 05/14] zipl_bootmap_is_up_to_date: Add OVAL check
-
----
- .../oval/shared.xml                           | 46 +++++++++++++++++++
- 1 file changed, 46 insertions(+)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/oval/shared.xml
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/oval/shared.xml b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/oval/shared.xml
-new file mode 100644
-index 0000000000..6c446cbe59
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/oval/shared.xml
-@@ -0,0 +1,46 @@
-+
-+  
-+    
-+      Ensure zIPL bootmap is up to date
-+      {{{- oval_affected(products) }}}
-+      Check if /boot/bootmap is up to date
-+    
-+    
-+      
-+    
-+  
-+
-+  
-+    
-+    
-+    
-+  
-+
-+  
-+    /boot/bootmap
-+  
-+
-+  
-+  
-+    
-+  
-+  
-+    
-+  
-+  
-+    /etc/zipl.conf
-+  
-+
-+  
-+    
-+  
-+  
-+    
-+  
-+  
-+    ^/boot/loader/entries/.*\.conf$
-+  
-+
-
-From 97aff87a403f9b319e87967561c43dc99e8a672e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 2 Jul 2020 16:15:35 +0200
-Subject: [PATCH 06/14] zipl_bootmap_is_up_to_date: Add mock tests
-
-These tests mock existence of zIPL files.
----
- .../tests/newer_boot_entry.fail.sh                     | 10 ++++++++++
- .../tests/newer_zipl_conf.fail.sh                      | 10 ++++++++++
- .../tests/up_to_date.pass.sh                           |  9 +++++++++
- 3 files changed, 29 insertions(+)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_boot_entry.fail.sh
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_zipl_conf.fail.sh
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/up_to_date.pass.sh
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_boot_entry.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_boot_entry.fail.sh
-new file mode 100644
-index 0000000000..728c6b7bdb
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_boot_entry.fail.sh
-@@ -0,0 +1,10 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+touch /etc/zipl.conf
-+touch /boot/loader/entries/*.conf # Update current existing entries
-+touch /boot/loader/entries/zipl-entry-1.conf
-+touch /boot/bootmap
-+sleep 2
-+touch /boot/loader/entries/zipl-entry-2.conf
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_zipl_conf.fail.sh b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_zipl_conf.fail.sh
-new file mode 100644
-index 0000000000..1ae4d631ee
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/newer_zipl_conf.fail.sh
-@@ -0,0 +1,10 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+touch /boot/loader/entries/*.conf # Update current existing entries
-+touch /boot/loader/entries/zipl-entry-1.conf
-+touch /boot/loader/entries/zipl-entry-2.conf
-+touch /boot/bootmap
-+sleep 2
-+touch /etc/zipl.conf
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/up_to_date.pass.sh b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/up_to_date.pass.sh
-new file mode 100644
-index 0000000000..7981ba8c5c
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/tests/up_to_date.pass.sh
-@@ -0,0 +1,9 @@
-+#!/bin/bash
-+# platform = Red Hat Enterprise Linux 8
-+# remediation = none
-+
-+touch /etc/zipl.conf
-+touch /boot/loader/entries/*.conf # Update current existing entries
-+touch /boot/loader/entries/zipl-entry-1.conf
-+touch /boot/loader/entries/zipl-entry-2.conf
-+touch /boot/bootmap
-
-From 180e57bd23154c1ed8dc2575fbf9660c2f83a803 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 3 Jul 2020 18:35:06 +0200
-Subject: [PATCH 07/14] zipl_bootmap_is_up_to_date: Add remediations
-
----
- .../ansible/shared.yml                        | 24 +++++++++++++++++++
- .../zipl_bootmap_is_up_to_date/bash/shared.sh |  3 +++
- 2 files changed, 27 insertions(+)
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/ansible/shared.yml
- create mode 100644 linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/ansible/shared.yml b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/ansible/shared.yml
-new file mode 100644
-index 0000000000..e545eacc13
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/ansible/shared.yml
-@@ -0,0 +1,24 @@
-+# platform = Red Hat Enterprise Linux 8
-+# reboot = false
-+# strategy = configure
-+# complexity = low
-+# disruption = low
-+
-+- name: "Ensure zIPL bootmap is up to date"
-+  block:
-+    - name: "Obtain stats of /boot/bootmap"
-+      stat:
-+        path: /boot/bootmap
-+      register: boot_bootmap
-+
-+    - name: "Obtain stats of /etc/zipl.conf"
-+      stat:
-+        path: /etc/zipl.conf
-+      register: zipl_conf
-+
-+    # TODO: handle /boot/loader/entries/*.conf
-+
-+    - name: "Update zIPL bootmap"
-+      command: /usr/sbin/zipl
-+      changed_when: True
-+      when: boot_bootmap.stat.mtime < zipl_conf.stat.mtime
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-new file mode 100644
-index 0000000000..2cf7e388f0
---- /dev/null
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-@@ -0,0 +1,3 @@
-+# platform = Red Hat Enterprise Linux 8
-+
-+/usr/bin/zipl
-
-From 93703727b12a34edb26de25410bf23ff72fead2a Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 1 Jul 2020 17:16:41 +0200
-Subject: [PATCH 08/14] Select zIPL specific rules in OSPP profile
-
----
- rhel8/profiles/ospp.profile | 4 ++++
- 1 file changed, 4 insertions(+)
-
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index 07d32b814d..80e4b71fff 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -415,3 +415,7 @@ selections:
-     - ssh_client_rekey_limit
-     - var_ssh_client_rekey_limit_size=1G
-     - var_ssh_client_rekey_limit_time=1hour
-+
-+    # zIPl specific rules
-+    - zipl_bls_entries_only
-+    - zipl_bootmap_is_up_to_date
-
-From 260891e9b2f38d50fadf9eaacd9ee9ca98c977ee Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 14:03:21 +0200
-Subject: [PATCH 09/14] Fix path to zipl binary in Bash remediation
-
----
- .../bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh   | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-index 2cf7e388f0..2310ca060d 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/bash/shared.sh
-@@ -1,3 +1,3 @@
- # platform = Red Hat Enterprise Linux 8
- 
--/usr/bin/zipl
-+/usr/sbin/zipl
-
-From 46d2b1584cf769ae8dbaaa2657541bd0db056a9c Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 14:06:22 +0200
-Subject: [PATCH 10/14] zipl_bls_entries_only: there can be leading spaces
-
-There can be leading spaces before 'image'.
----
- .../bootloader-zipl/zipl_bls_entries_only/oval/shared.xml       | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-index 41e9773814..f68d91c128 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-@@ -20,7 +20,7 @@
-   
-     ^/etc/zipl.conf$
--    ^image\s*=.*$
-+    ^\s*image\s*=.*$
-     1
-   
- 
-
-From 0a89ed181803c15e3b73cfb2e13f0ec1cb7689ad Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 14:10:22 +0200
-Subject: [PATCH 11/14] zipl_bls_entries_only: check file /etc/zipl.conf
-
-There is no need to perform pattern match, the check just needs to
-examine /etc/zipl.conf file.
----
- .../bootloader-zipl/zipl_bls_entries_only/oval/shared.xml       | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-index f68d91c128..1ebf03ee37 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/oval/shared.xml
-@@ -19,7 +19,7 @@
- 
-   
--    ^/etc/zipl.conf$
-+    /etc/zipl.conf
-     ^\s*image\s*=.*$
-     1
-   
-
-From 699d5f5bd3075e019387e6fb6b3af81182987c43 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 14:13:26 +0200
-Subject: [PATCH 12/14] Add CCE identifiers to bootmap and bls only rules
-
-Add RHEL-8 CCE identifiers for:
-- zipl_bls_entries_only
-- zipl_bootmap_is_up_to_date
----
- .../system/bootloader-zipl/zipl_bls_entries_only/rule.yml      | 3 +++
- .../system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml | 3 +++
- 3 files changed, 6 insertions(+), 2 deletions(-)
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-index f792c5257f..67cc061ce3 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bls_entries_only/rule.yml
-@@ -14,6 +14,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83485-3
-+
- ocil_clause: 'a non BLS boot entry is configured'
- 
- ocil: |-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-index 082562d11e..da9411d00b 100644
---- a/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-+++ b/linux_os/guide/system/bootloader-zipl/zipl_bootmap_is_up_to_date/rule.yml
-@@ -16,6 +16,9 @@ rationale: |-
- 
- severity: medium
- 
-+identifiers:
-+    cce@rhel8: 83486-1
-+
- ocil_clause: 'the bootmap is outdated'
- 
- ocil: |-
-
-From 2ebc3d188e4c243d8e60a9e669d5b661b77f2301 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 14:16:58 +0200
-Subject: [PATCH 13/14] Incorporate OSPP selection changes to profile test
-
-Update the profile reference file.
----
- tests/data/profile_stability/rhel8/ospp.profile | 2 ++
- 1 file changed, 2 insertions(+)
-
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index b0d7672c36..08dcccf24c 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -213,6 +213,8 @@ selections:
- - sysctl_user_max_user_namespaces
- - timer_dnf-automatic_enabled
- - usbguard_allow_hid_and_hub
-+- zipl_bls_entries_only
-+- zipl_bootmap_is_up_to_date
- - var_sshd_set_keepalive=0
- - var_rekey_limit_size=1G
- - var_rekey_limit_time=1hour
-
-From 33bae25bd543880315433925214868917ec8e399 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Wed, 8 Jul 2020 15:28:09 +0200
-Subject: [PATCH 14/14] Unselect zIPL rules from STIG Profile
-
-The zIPL rules are inherited from OSPP profile
----
- rhel8/profiles/stig.profile | 4 ++++
- 1 file changed, 4 insertions(+)
-
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index 8f12852e26..cfc2160be1 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -45,3 +45,7 @@ selections:
-     - rsyslog_remote_tls
-     - rsyslog_remote_tls_cacert
-     - "!ssh_client_rekey_limit"
-+
-+    # Unselect zIPL rules from OSPP
-+    - "!zipl_bls_entries_only"
-+    - "!zipl_bootmap_is_up_to_date"
diff --git a/SOURCES/scap-security-guide-0.1.52-selinux_all_devicefiles_labeled_fix-PR_5911.patch b/SOURCES/scap-security-guide-0.1.52-selinux_all_devicefiles_labeled_fix-PR_5911.patch
deleted file mode 100644
index e734ce1..0000000
--- a/SOURCES/scap-security-guide-0.1.52-selinux_all_devicefiles_labeled_fix-PR_5911.patch
+++ /dev/null
@@ -1,209 +0,0 @@
-From 60f82f8d33cef82f3ff5e90073803c199bad02fb Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Tue, 7 Jul 2020 11:31:59 +0200
-Subject: [PATCH 1/3] modify rule description and ocil
-
----
- .../selinux_all_devicefiles_labeled/rule.yml  | 19 +++++++++++--------
- 1 file changed, 11 insertions(+), 8 deletions(-)
-
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml
-index 765fca583e..1667557740 100644
---- a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/rule.yml
-@@ -6,18 +6,20 @@ title: 'Ensure No Device Files are Unlabeled by SELinux'
- 
- description: |-
-     Device files, which are used for communication with important system
--    resources, should be labeled with proper SELinux types. If any device
--    files do not carry the SELinux type device_t, report the bug so
--    that policy can be corrected. Supply information about what the device is
--    and what programs use it.
-+    resources, should be labeled with proper SELinux types. If any device files
-+    carry the SELinux type device_t or unlabeled_t, report the
-+    bug so that policy can be corrected. Supply information about what the
-+    device is and what programs use it.
-     


--    To check for unlabeled device files, run the following command:
-+    To check for incorrectly labeled device files, run following commands:
-     
$ sudo find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n"

-+    
$ sudo find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"

-     It should produce no output in a well-configured system.
- 
- rationale: |-
--    If a device file carries the SELinux type device_t, then SELinux
--    cannot properly restrict access to the device file.
-+    If a device file carries the SELinux type device_t or
-+    unlabeled_t, then SELinux cannot properly restrict access to the
-+    device file.
- 
- severity: medium
- 
-@@ -45,8 +47,9 @@ references:
- ocil_clause: 'there is output'
- 
- ocil: |-
--    To check for unlabeled device files, run the following command:
-+    To check for incorrectly labeled device files, run following commands:
-     
$ sudo find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n"

-+    
$ sudo find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"

-     It should produce no output in a well-configured system.
- 
- warnings:
-
-From e0cb2d04a9d95967e4adb3e05cc93a4a834a90b5 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Tue, 7 Jul 2020 11:32:57 +0200
-Subject: [PATCH 2/3] updated oval to check only device files
-
----
- .../oval/shared.xml                           | 64 +++++++++++++------
- 1 file changed, 43 insertions(+), 21 deletions(-)
-
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/oval/shared.xml b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/oval/shared.xml
-index 51b68008af..7dcfb98577 100644
---- a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/oval/shared.xml
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/oval/shared.xml
-@@ -2,32 +2,54 @@
-   
-     
-       Device Files Have Proper SELinux Context
--      
--        Red Hat Enterprise Linux 6
--        Red Hat Enterprise Linux 7
--        Red Hat Enterprise Linux 8
--        Red Hat Virtualization 4
--        multi_platform_fedora
--        multi_platform_ol
--        multi_platform_wrlinux
--      
--      All device files in /dev should be assigned an SELinux security context other than 'device_t'.
-+      {{{- oval_affected(products) }}}
-+      All device files in /dev should be assigned an SELinux security context other than 'device_t' and 'unlabeled_t'.
-     
--    
--      
-+    
-+      
-+      
-     
-   
--  
--    
--    
-+
-+  
-+  
-+    
-+    /dev
-+    ^.*$
-+    state_block_or_char_device_file
-+  
-+
-+  
-+    ^(block|character) special$
-+  
-+
-+  
-+    
-+  
-+
-+
-+  
-+    
-+    
-   
--  
--    
--    /dev
--    ^.*$
--    state_selinux_all_devicefiles_labeled
-+  
-+    
-+    state_selinux_dev_device_t
-   
--  
-+  
-     device_t
-   
-+
-+  
-+    
-+    
-+  
-+  
-+    
-+    state_selinux_dev_unlabeled_t
-+  
-+  
-+    unlabeled_t
-+  
-+
- 
-
-From 0bd95e6dbe3684524c86150cdb6beb0af05ff119 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Tue, 7 Jul 2020 11:33:26 +0200
-Subject: [PATCH 3/3] add tests
-
----
- .../tests/block_device_device_t.fail.sh            |  4 ++++
- .../tests/char_device_unlabeled_t.fail.sh          | 14 ++++++++++++++
- .../tests/regular_file_device_t.pass.sh            |  4 ++++
- .../tests/symlink_with_wrong_label.pass.sh         |  4 ++++
- 4 files changed, 26 insertions(+)
- create mode 100644 linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/block_device_device_t.fail.sh
- create mode 100644 linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/char_device_unlabeled_t.fail.sh
- create mode 100644 linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/regular_file_device_t.pass.sh
- create mode 100644 linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/symlink_with_wrong_label.pass.sh
-
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/block_device_device_t.fail.sh b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/block_device_device_t.fail.sh
-new file mode 100644
-index 0000000000..08c4142e5b
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/block_device_device_t.fail.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+mknod /dev/foo b 1 5
-+chcon -t device_t /dev/foo
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/char_device_unlabeled_t.fail.sh b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/char_device_unlabeled_t.fail.sh
-new file mode 100644
-index 0000000000..1da85c2034
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/char_device_unlabeled_t.fail.sh
-@@ -0,0 +1,14 @@
-+#!/bin/bash
-+
-+# selinux does not allow unlabeled_t in /dev
-+# we have to modify the selinux policy to allow that
-+
-+echo '(allow unlabeled_t device_t (filesystem (associate)))' > /tmp/unlabeled_t.cil
-+semodule -i /tmp/unlabeled_t.cil
-+
-+mknod /dev/foo c 1 5
-+chcon -t unlabeled_t /dev/foo
-+
-+
-+mknod /dev/foo c 1 5
-+chcon -t device_t /dev/foo
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/regular_file_device_t.pass.sh b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/regular_file_device_t.pass.sh
-new file mode 100644
-index 0000000000..d161951d7a
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/regular_file_device_t.pass.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+touch /dev/foo
-+restorecon -F /dev/foo
-diff --git a/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/symlink_with_wrong_label.pass.sh b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/symlink_with_wrong_label.pass.sh
-new file mode 100644
-index 0000000000..a8280bf37e
---- /dev/null
-+++ b/linux_os/guide/system/selinux/selinux_all_devicefiles_labeled/tests/symlink_with_wrong_label.pass.sh
-@@ -0,0 +1,4 @@
-+#!/bin/bash
-+
-+ln -s /dev/cpu /dev/foo
-+restorecon -F /dev/foo
diff --git a/SOURCES/scap-security-guide-0.1.53-add-ansible-platform_PR_6025.patch b/SOURCES/scap-security-guide-0.1.53-add-ansible-platform_PR_6025.patch
deleted file mode 100644
index 9154e40..0000000
--- a/SOURCES/scap-security-guide-0.1.53-add-ansible-platform_PR_6025.patch
+++ /dev/null
@@ -1,280 +0,0 @@
-From 844be904d8de624abe9bbe620d7a06417dfff842 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 27 Aug 2020 13:19:01 +0200
-Subject: [PATCH 1/5] Align Ansible task applicability with CPE platform
-
-Adds a when clause to Ansible snippets of rules with Package CPE platform.
-
-If the when clause is added, a fact_packages Task needs to added as
-well.
----
- ssg/build_remediations.py | 52 ++++++++++++++++++++++++++++++++++++---
- 1 file changed, 49 insertions(+), 3 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index a9ef3014ac..597aed5889 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -6,8 +6,7 @@
- import os.path
- import re
- import codecs
--from collections import defaultdict, namedtuple
--
-+from collections import defaultdict, namedtuple, OrderedDict
- 
- import ssg.yaml
- from . import build_yaml
-@@ -343,11 +342,46 @@ def _get_rule_reference(self, ref_class):
-         else:
-             return []
- 
-+    def inject_package_facts_task(self, parsed_snippet):
-+        """ Injects a package_facts task only if
-+            the snippet has a task with a when clause with ansible_facts.packages,
-+            and the snippet doesn't already have an package_facts task
-+        """
-+        has_package_facts_task = False
-+        has_ansible_facts_packages_clause = False
-+
-+        for p_task in parsed_snippet:
-+            # We are only interested in the OrderedDicts, which represent Ansible tasks
-+            if not isinstance(p_task, dict):
-+                continue
-+
-+            if "package_facts" in p_task:
-+                has_package_facts_task = True
-+
-+            if "ansible_facts.packages" in p_task.get("when", ""):
-+                has_ansible_facts_packages_clause = True
-+
-+        if has_ansible_facts_packages_clause and not has_package_facts_task:
-+            facts_task = OrderedDict({'name': 'Gather the package facts',
-+                                      'package_facts': {'manager': 'auto'}})
-+            parsed_snippet.insert(0, facts_task)
-+
-     def update_when_from_rule(self, to_update):
-         additional_when = ""
--        if self.associated_rule.platform == "machine":
--            additional_when = ('ansible_virtualization_role != "guest" '
--                               'or ansible_virtualization_type != "docker"')
-+        rule_platform = self.associated_rule.platform
-+        if rule_platform == "machine":
-+            additional_when = 'ansible_virtualization_type not in ["docker", "lxc", "openvz"]'
-+        elif rule_platform is not None:
-+            # Assume any other platform is a Package CPE
-+
-+            # It doesn't make sense to add a conditional on the task that
-+            # gathers data for the conditional
-+            if "package_facts" in to_update:
-+                return
-+
-+            additional_when = '"' + rule_platform + '" in ansible_facts.packages'
-+            # After adding the conditional, we need to make sure package_facts are collected.
-+            # This is done via inject_package_facts_task()
-         to_update.setdefault("when", "")
-         new_when = ssg.yaml.update_yaml_list_or_string(to_update["when"], additional_when)
-         if not new_when:
-@@ -355,10 +390,21 @@ def update_when_from_rule(self, to_update):
-             to_update["when"] = new_when
- 
-     def update(self, parsed, config):
-+        # We split the remediation update in three steps
-+
-+        # 1. Update the when clause
-         for p in parsed:
-             if not isinstance(p, dict):
-                 continue
-             self.update_when_from_rule(p)
-+
-+        # 2. Inject any extra task necessary
-+        self.inject_package_facts_task(parsed)
-+
-+        # 3. Add tags to all tasks, including the ones we have injected
-+        for p in parsed:
-+            if not isinstance(p, dict):
-+                continue
-             self.update_tags_from_config(p, config)
-             self.update_tags_from_rule(p)
- 
-
-From 60e5723e0e35ec8d79bafdd113f04691e61738e7 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 27 Aug 2020 17:09:06 +0200
-Subject: [PATCH 2/5] Add inherited_platform to Rule
-
-This field is exported to the rule when it is resolved.
----
- ssg/build_yaml.py | 5 +++++
- 1 file changed, 5 insertions(+)
-
-diff --git a/ssg/build_yaml.py b/ssg/build_yaml.py
-index 4ba114eee4..fe290ffc05 100644
---- a/ssg/build_yaml.py
-+++ b/ssg/build_yaml.py
-@@ -832,6 +832,7 @@ class Rule(object):
-         "conflicts": lambda: list(),
-         "requires": lambda: list(),
-         "platform": lambda: None,
-+        "inherited_platforms": lambda: list(),
-         "template": lambda: None,
-     }
- 
-@@ -851,6 +852,7 @@ def __init__(self, id_):
-         self.requires = []
-         self.conflicts = []
-         self.platform = None
-+        self.inherited_platforms = [] # platforms inherited from the group
-         self.template = None
- 
-     @classmethod
-@@ -1293,6 +1295,9 @@ def _process_rules(self):
-                 continue
-             self.all_rules.add(rule)
-             self.loaded_group.add_rule(rule)
-+
-+            rule.inherited_platforms.append(self.loaded_group.platform)
-+
-             if self.resolved_rules_dir:
-                 output_for_rule = os.path.join(
-                     self.resolved_rules_dir, "{id_}.yml".format(id_=rule.id_))
-
-From 3a0bb0d2981670e90a8eaca53b28e1a6f7cc29d6 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 27 Aug 2020 17:21:35 +0200
-Subject: [PATCH 3/5] Add when clauses for inherited platforms too
-
-Consider the Rule's Group platform while including 'when' clauses to
-Ansible snippets.
-
-Some rules have two platforms, a machine platform and a package
-platform. One of them is represented of the Rule, and the other is
-represented in the Rule's Group.
-
-The platforms are organized like this to due limiation in XCCDF,
-multiple platforms in a Rule are ORed, not ANDed.
----
- ssg/build_remediations.py | 44 ++++++++++++++++++++++++---------------
- 1 file changed, 27 insertions(+), 17 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 597aed5889..a2a996d0af 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -358,8 +358,13 @@ def inject_package_facts_task(self, parsed_snippet):
-             if "package_facts" in p_task:
-                 has_package_facts_task = True
- 
--            if "ansible_facts.packages" in p_task.get("when", ""):
--                has_ansible_facts_packages_clause = True
-+            # When clause of the task can be string or a list, lets normalize to list
-+            task_when = p_task.get("when", "")
-+            if type(task_when) is str:
-+                task_when = [ task_when ]
-+            for when in task_when:
-+                if "ansible_facts.packages" in when:
-+                    has_ansible_facts_packages_clause = True
- 
-         if has_ansible_facts_packages_clause and not has_package_facts_task:
-             facts_task = OrderedDict({'name': 'Gather the package facts',
-@@ -367,21 +372,26 @@ def inject_package_facts_task(self, parsed_snippet):
-             parsed_snippet.insert(0, facts_task)
- 
-     def update_when_from_rule(self, to_update):
--        additional_when = ""
--        rule_platform = self.associated_rule.platform
--        if rule_platform == "machine":
--            additional_when = 'ansible_virtualization_type not in ["docker", "lxc", "openvz"]'
--        elif rule_platform is not None:
--            # Assume any other platform is a Package CPE
--
--            # It doesn't make sense to add a conditional on the task that
--            # gathers data for the conditional
--            if "package_facts" in to_update:
--                return
--
--            additional_when = '"' + rule_platform + '" in ansible_facts.packages'
--            # After adding the conditional, we need to make sure package_facts are collected.
--            # This is done via inject_package_facts_task()
-+        additional_when = []
-+
-+        rule_platforms = set([self.associated_rule.platform] +
-+                              self.associated_rule.inherited_platforms)
-+
-+        for platform in rule_platforms:
-+            if platform == "machine":
-+                additional_when.append('ansible_virtualization_type not in ["docker", "lxc", "openvz"]')
-+            elif platform is not None:
-+                # Assume any other platform is a Package CPE
-+
-+                # It doesn't make sense to add a conditional on the task that
-+                # gathers data for the conditional
-+                if "package_facts" in to_update:
-+                    continue
-+
-+                additional_when.append('"' + platform + '" in ansible_facts.packages')
-+                # After adding the conditional, we need to make sure package_facts are collected.
-+                # This is done via inject_package_facts_task()
-+
-         to_update.setdefault("when", "")
-         new_when = ssg.yaml.update_yaml_list_or_string(to_update["when"], additional_when)
-         if not new_when:
-
-From 99c92e39bccc3fcfadca41096e66ca146137b207 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 31 Aug 2020 16:06:14 +0200
-Subject: [PATCH 4/5] Improve inherihted and rule's platforms handling
-
-Add a quick comment too.
----
- ssg/build_remediations.py | 5 +++--
- 1 file changed, 3 insertions(+), 2 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index a2a996d0af..9e622ef740 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -374,8 +374,9 @@ def inject_package_facts_task(self, parsed_snippet):
-     def update_when_from_rule(self, to_update):
-         additional_when = []
- 
--        rule_platforms = set([self.associated_rule.platform] +
--                              self.associated_rule.inherited_platforms)
-+        # There can be repeated inherited platforms and rule platforms
-+        rule_platforms = set(self.associated_rule.inherited_platforms)
-+        rule_platforms.add(self.associated_rule.platform)
- 
-         for platform in rule_platforms:
-             if platform == "machine":
-
-From 596da9993edfbd244cbaa6d797abbd68b2e82185 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 31 Aug 2020 16:10:53 +0200
-Subject: [PATCH 5/5] Code style and grammar changes
-
----
- ssg/build_remediations.py | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 9e622ef740..866450dd8c 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -345,7 +345,7 @@ def _get_rule_reference(self, ref_class):
-     def inject_package_facts_task(self, parsed_snippet):
-         """ Injects a package_facts task only if
-             the snippet has a task with a when clause with ansible_facts.packages,
--            and the snippet doesn't already have an package_facts task
-+            and the snippet doesn't already have a package_facts task
-         """
-         has_package_facts_task = False
-         has_ansible_facts_packages_clause = False
-@@ -361,7 +361,7 @@ def inject_package_facts_task(self, parsed_snippet):
-             # When clause of the task can be string or a list, lets normalize to list
-             task_when = p_task.get("when", "")
-             if type(task_when) is str:
--                task_when = [ task_when ]
-+                task_when = [task_when]
-             for when in task_when:
-                 if "ansible_facts.packages" in when:
-                     has_ansible_facts_packages_clause = True
diff --git a/SOURCES/scap-security-guide-0.1.53-add-bash-platform_PR_6061.patch b/SOURCES/scap-security-guide-0.1.53-add-bash-platform_PR_6061.patch
deleted file mode 100644
index f1510d8..0000000
--- a/SOURCES/scap-security-guide-0.1.53-add-bash-platform_PR_6061.patch
+++ /dev/null
@@ -1,241 +0,0 @@
-From c05cce1a4a5eb95be857b07948fda0c95cdaa106 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 8 Sep 2020 14:36:07 +0200
-Subject: [PATCH 1/5] Align Bash applicability with CPE platform
-
-Wraps the remediation of rules with Packager CPE Platform
-with an if condition that checks for the respective
-platforms's package.
----
- ssg/build_remediations.py | 45 +++++++++++++++++++++++++++++++++++++++
- 1 file changed, 45 insertions(+)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index ccbdf9fc1f..2d4a805e78 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -27,6 +27,13 @@
-     'kubernetes': '.yml'
- }
- 
-+PKG_MANAGER_TO_PACKAGE_CHECK_COMMAND = {
-+    'apt_get': 'dpkg-query -s {} &>/dev/null',
-+    'dnf': 'rpm --quiet -q {}',
-+    'yum': 'rpm --quiet -q {}',
-+    'zypper': 'rpm --quiet -q {}',
-+}
-+
- FILE_GENERATED_HASH_COMMENT = '# THIS FILE IS GENERATED'
- 
- REMEDIATION_CONFIG_KEYS = ['complexity', 'disruption', 'platform', 'reboot',
-@@ -262,6 +269,44 @@ class BashRemediation(Remediation):
-     def __init__(self, file_path):
-         super(BashRemediation, self).__init__(file_path, "bash")
- 
-+    def parse_from_file_with_jinja(self, env_yaml):
-+        self.local_env_yaml.update(env_yaml)
-+        result = super(BashRemediation, self).parse_from_file_with_jinja(self.local_env_yaml)
-+
-+        # There can be repeated inherited platforms and rule platforms
-+        rule_platforms = set(self.associated_rule.inherited_platforms)
-+        rule_platforms.add(self.associated_rule.platform)
-+
-+        platform_conditionals = []
-+        for platform in rule_platforms:
-+            if platform == "machine":
-+                # Based on check installed_env_is_a_container
-+                platform_conditionals.append('[ ! -f /.dockerenv -a ! -f /run/.containerenv ]')
-+            elif platform is not None:
-+                # Assume any other platform is a Package CPE
-+
-+                # Some package names are different from the platform names
-+                if platform in self.local_env_yaml["platform_package_overrides"]:
-+                    platform = self.local_env_yaml["platform_package_overrides"].get(platform)
-+
-+                # Adjust package check command according to the pkg_manager
-+                pkg_manager = self.local_env_yaml["pkg_manager"]
-+                pkg_check_command = PKG_MANAGER_TO_PACKAGE_CHECK_COMMAND[pkg_manager]
-+                platform_conditionals.append(pkg_check_command.format(platform))
-+
-+        if platform_conditionals:
-+            platform_fix_text = "# Remediation is applicable only in certain platforms\n"
-+
-+            cond = platform_conditionals.pop(0)
-+            platform_fix_text += "if {}".format(cond)
-+            for cond in platform_conditionals:
-+                platform_fix_text += " && {}".format(cond)
-+            platform_fix_text += '; then\n{}\nelse\necho "Remediation is not applicable, nothing was done"\nfi'.format(result.contents)
-+
-+            remediation = namedtuple('remediation', ['contents', 'config'])
-+            result = remediation(contents=platform_fix_text, config=result.config)
-+
-+        return result
- 
- class AnsibleRemediation(Remediation):
-     def __init__(self, file_path):
-
-From 19e0c3b709e091159655d37b8ce5d693750f0a81 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 8 Sep 2020 14:41:01 +0200
-Subject: [PATCH 2/5] Handle Bash platform wrapping in xccdf expansion
-
-Adjust expansion of subs and variables not to remove the whole beginning
-of the fix test. This was removing the package conditional wrapping.
----
- ssg/build_remediations.py | 21 ++++++++++++---------
- 1 file changed, 12 insertions(+), 9 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 2d4a805e78..49ec557000 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -736,14 +736,16 @@ def expand_xccdf_subs(fix, remediation_type, remediation_functions):
-         patcomp = re.compile(pattern, re.DOTALL)
-         fixparts = re.split(patcomp, fix.text)
-         if fixparts[0] is not None:
--            # Split the portion of fix.text from fix start to first call of
--            # remediation function, keeping only the third part:
--            # * tail        to hold part of the fix.text after inclusion,
--            #               but before first call of remediation function
-+            # Split the portion of fix.text at the string remediation_functions,
-+            # and remove preceeding comment whenever it is there.
-+            # * head        holds part of the fix.text before
-+            #               remediation_functions string
-+            # * tail        holds part of the fix.text after the
-+            #               remediation_functions string
-             try:
--                rfpattern = '(.*remediation_functions)(.*)'
--                rfpatcomp = re.compile(rfpattern, re.DOTALL)
--                _, _, tail, _ = re.split(rfpatcomp, fixparts[0], maxsplit=2)
-+                rfpattern = r'((?:# Include source function library\.\n)?.*remediation_functions)'
-+                rfpatcomp = re.compile(rfpattern)
-+                head, _, tail = re.split(rfpatcomp, fixparts[0], maxsplit=1)
-             except ValueError:
-                 sys.stderr.write("Processing fix.text for: %s rule\n"
-                                  % fix.get('rule'))
-@@ -751,9 +753,10 @@ def expand_xccdf_subs(fix, remediation_type, remediation_functions):
-                                  "after inclusion of remediation functions."
-                                  " Aborting..\n")
-                 sys.exit(1)
--            # If the 'tail' is not empty, make it new fix.text.
-+            # If the 'head' is not empty, make it new fix.text.
-             # Otherwise use ''
--            fix.text = tail if tail is not None else ''
-+            fix.text = head if head is not None else ''
-+            fix.text += tail if tail is not None else ''
-             # Drop the first element of 'fixparts' since it has been processed
-             fixparts.pop(0)
-             # Perform sanity check on new 'fixparts' list content (to continue
-
-From 1292b93dc35a9a308464f1effb7f10f8de6db457 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 8 Sep 2020 20:56:17 +0200
-Subject: [PATCH 3/5] Check if remediation has associated rule before use
-
----
- ssg/build_remediations.py | 8 +++++---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 49ec557000..85f7139d8f 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -273,9 +273,11 @@ def parse_from_file_with_jinja(self, env_yaml):
-         self.local_env_yaml.update(env_yaml)
-         result = super(BashRemediation, self).parse_from_file_with_jinja(self.local_env_yaml)
- 
--        # There can be repeated inherited platforms and rule platforms
--        rule_platforms = set(self.associated_rule.inherited_platforms)
--        rule_platforms.add(self.associated_rule.platform)
-+        rule_platforms = set()
-+        if self.associated_rule:
-+            # There can be repeated inherited platforms and rule platforms
-+            rule_platforms.update(self.associated_rule.inherited_platforms)
-+            rule_platforms.add(self.associated_rule.platform)
- 
-         platform_conditionals = []
-         for platform in rule_platforms:
-
-From 7953a02e61bb56b501c56f46972247751292dcbb Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 10 Sep 2020 10:59:43 +0200
-Subject: [PATCH 4/5] Fix python2 compat and improve code readability
-
----
- ssg/build_remediations.py | 29 ++++++++++++++++++-----------
- 1 file changed, 18 insertions(+), 11 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 85f7139d8f..673d6d0cc6 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -28,10 +28,10 @@
- }
- 
- PKG_MANAGER_TO_PACKAGE_CHECK_COMMAND = {
--    'apt_get': 'dpkg-query -s {} &>/dev/null',
--    'dnf': 'rpm --quiet -q {}',
--    'yum': 'rpm --quiet -q {}',
--    'zypper': 'rpm --quiet -q {}',
-+    'apt_get': 'dpkg-query -s {0} &>/dev/null',
-+    'dnf': 'rpm --quiet -q {0}',
-+    'yum': 'rpm --quiet -q {0}',
-+    'zypper': 'rpm --quiet -q {0}',
- }
- 
- FILE_GENERATED_HASH_COMMENT = '# THIS FILE IS GENERATED'
-@@ -297,16 +297,23 @@ def parse_from_file_with_jinja(self, env_yaml):
-                 platform_conditionals.append(pkg_check_command.format(platform))
- 
-         if platform_conditionals:
--            platform_fix_text = "# Remediation is applicable only in certain platforms\n"
-+            wrapped_fix_text = ["# Remediation is applicable only in certain platforms"]
- 
--            cond = platform_conditionals.pop(0)
--            platform_fix_text += "if {}".format(cond)
--            for cond in platform_conditionals:
--                platform_fix_text += " && {}".format(cond)
--            platform_fix_text += '; then\n{}\nelse\necho "Remediation is not applicable, nothing was done"\nfi'.format(result.contents)
-+            all_conditions = " && ".join(platform_conditionals)
-+            wrapped_fix_text.append("if {0}; then".format(all_conditions))
-+
-+            # Avoid adding extra blank line
-+            if not result.contents.startswith("\n"):
-+                wrapped_fix_text.append("")
-+
-+            wrapped_fix_text.append("{0}".format(result.contents))
-+            wrapped_fix_text.append("")
-+            wrapped_fix_text.append("else")
-+            wrapped_fix_text.append("    >&2 echo 'Remediation is not applicable, nothing was done'")
-+            wrapped_fix_text.append("fi")
- 
-             remediation = namedtuple('remediation', ['contents', 'config'])
--            result = remediation(contents=platform_fix_text, config=result.config)
-+            result = remediation(contents="\n".join(wrapped_fix_text), config=result.config)
- 
-         return result
- 
-
-From 0bd3912651367c64789bb3d67b44c3b8848708c0 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Thu, 10 Sep 2020 17:25:27 +0200
-Subject: [PATCH 5/5] Document the perils of indenting wrapped Bash fixes
-
----
- ssg/build_remediations.py | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 673d6d0cc6..f269d4d2d6 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -306,6 +306,9 @@ def parse_from_file_with_jinja(self, env_yaml):
-             if not result.contents.startswith("\n"):
-                 wrapped_fix_text.append("")
- 
-+            # It is possible to indent the original body of the remediation with textwrap.indent(),
-+            # however, it is not supported by python2, and there is a risk of breaking remediations
-+            # For example, remediations with a here-doc block could be affected.
-             wrapped_fix_text.append("{0}".format(result.contents))
-             wrapped_fix_text.append("")
-             wrapped_fix_text.append("else")
diff --git a/SOURCES/scap-security-guide-0.1.53-add-platform-to-package-mapping_PR_6047.patch b/SOURCES/scap-security-guide-0.1.53-add-platform-to-package-mapping_PR_6047.patch
deleted file mode 100644
index d8fc95c..0000000
--- a/SOURCES/scap-security-guide-0.1.53-add-platform-to-package-mapping_PR_6047.patch
+++ /dev/null
@@ -1,203 +0,0 @@
-From 7c0b04c157374e9251360d1d5e12a9e00dd4375e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 4 Sep 2020 09:50:54 +0200
-Subject: [PATCH 1/3] Introduce platform_package_overrides
-
-Introduce a mapping of CPE package platform name to a package name.
-
-Each linux distro or version may have its specific name for a package,
-this mapping allows a product to override the package name of a
-platorm.
-
-By default, it assumes that the package name will be the same as the
-platform name.
----
- rhel8/product.yml         | 7 +++++++
- ssg/build_remediations.py | 3 +++
- 2 files changed, 10 insertions(+)
-
-diff --git a/rhel8/product.yml b/rhel8/product.yml
-index 6cdc51919e..6b5b4e2748 100644
---- a/rhel8/product.yml
-+++ b/rhel8/product.yml
-@@ -18,3 +18,10 @@ aux_pkg_version: "d4082792"
- 
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "6A6AA7C97C8890AEC6AEBFE2F76F66C3D4082792"
-+
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  grub2: "grub2-pc"
-+  login_defs: "shadow-utils"
-+  sssd: "sssd-common"
-+  zipl: "s390x-utils"
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index 866450dd8c..ccbdf9fc1f 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -389,6 +389,9 @@ def update_when_from_rule(self, to_update):
-                 if "package_facts" in to_update:
-                     continue
- 
-+                if platform in self.local_env_yaml["platform_package_overrides"]:
-+                    platform = self.local_env_yaml["platform_package_overrides"].get(platform)
-+
-                 additional_when.append('"' + platform + '" in ansible_facts.packages')
-                 # After adding the conditional, we need to make sure package_facts are collected.
-                 # This is done via inject_package_facts_task()
-
-From 10dc62084cf8e38be9189b527c3b99b545826091 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 4 Sep 2020 14:42:57 +0200
-Subject: [PATCH 2/3] Move platform to cpe mappings to ssg/constants
-
----
- rhel8/product.yml | 6 ------
- ssg/constants.py  | 8 ++++++++
- 2 files changed, 8 insertions(+), 6 deletions(-)
-
-diff --git a/rhel8/product.yml b/rhel8/product.yml
-index 6b5b4e2748..d839b23231 100644
---- a/rhel8/product.yml
-+++ b/rhel8/product.yml
-@@ -19,9 +19,3 @@ aux_pkg_version: "d4082792"
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "6A6AA7C97C8890AEC6AEBFE2F76F66C3D4082792"
- 
--# Mapping of CPE platform to package
--platform_package_overrides:
--  grub2: "grub2-pc"
--  login_defs: "shadow-utils"
--  sssd: "sssd-common"
--  zipl: "s390x-utils"
-diff --git a/ssg/constants.py b/ssg/constants.py
-index 3f9d7d37ce..7e9678241c 100644
---- a/ssg/constants.py
-+++ b/ssg/constants.py
-@@ -501,6 +501,14 @@
-     "zipl": "cpe:/a:zipl",
- }
- 
-+# Default platform to package mapping
-+XCCDF_PLATFORM_TO_PACKAGE = {
-+  "grub2": "grub2-pc",
-+  "login_defs": "login",
-+  "sssd": "sssd-common",
-+  "zipl": "s390x-utils",
-+}
-+
- # _version_name_map = {
- MAKEFILE_ID_TO_PRODUCT_MAP = {
-     'chromium': 'Google Chromium Browser',
-
-From feb012f06adae989138be15431020f2c174becc4 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 4 Sep 2020 14:47:29 +0200
-Subject: [PATCH 3/3] Allow override of default platform package mapping
-
-With default platform to package mappings defined, we need to allow a
-product to override it if needed.
----
- rhel6/product.yml   | 4 ++++
- rhel7/product.yml   | 4 ++++
- rhel8/product.yml   | 3 +++
- rhosp10/product.yml | 3 +++
- rhosp13/product.yml | 4 ++++
- rhv4/product.yml    | 4 ++++
- ssg/yaml.py         | 6 +++++-
- 8 files changed, 31 insertions(+), 1 deletion(-)
-
-diff --git a/rhel6/product.yml b/rhel6/product.yml
-index cc8fa4f8ed..eab9b80c47 100644
---- a/rhel6/product.yml
-+++ b/rhel6/product.yml
-@@ -20,3 +20,7 @@ aux_pkg_version: "2fa658e0"
- 
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "43A6E49C4A38F4BE9ABF2A5345689C882FA658E0"
-+
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/rhel7/product.yml b/rhel7/product.yml
-index f03c928b8f..3ff996b8cc 100644
---- a/rhel7/product.yml
-+++ b/rhel7/product.yml
-@@ -18,3 +18,7 @@ aux_pkg_version: "2fa658e0"
- 
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "43A6E49C4A38F4BE9ABF2A5345689C882FA658E0"
-+
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/rhel8/product.yml b/rhel8/product.yml
-index d839b23231..f3aa59faec 100644
---- a/rhel8/product.yml
-+++ b/rhel8/product.yml
-@@ -19,3 +19,6 @@ aux_pkg_version: "d4082792"
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "6A6AA7C97C8890AEC6AEBFE2F76F66C3D4082792"
- 
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/rhosp10/product.yml b/rhosp10/product.yml
-index 51d0a932a5..af42ca998d 100644
---- a/rhosp10/product.yml
-+++ b/rhosp10/product.yml
-@@ -10,3 +10,6 @@ pkg_manager: "yum"
- 
- init_system: "systemd"
- 
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/rhosp13/product.yml b/rhosp13/product.yml
-index 5e849ff609..ba42a31cd7 100644
---- a/rhosp13/product.yml
-+++ b/rhosp13/product.yml
-@@ -9,3 +9,7 @@ profiles_root: "./profiles"
- pkg_manager: "yum"
- 
- init_system: "systemd"
-+
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/rhv4/product.yml b/rhv4/product.yml
-index 10a2eda079..a61bf1588d 100644
---- a/rhv4/product.yml
-+++ b/rhv4/product.yml
-@@ -18,3 +18,7 @@ aux_pkg_version: "d4082792"
- 
- release_key_fingerprint: "567E347AD0044ADE55BA8A5F199E2F91FD431D51"
- auxiliary_key_fingerprint: "6A6AA7C97C8890AEC6AEBFE2F76F66C3D4082792"
-+
-+# Mapping of CPE platform to package
-+platform_package_overrides:
-+  login_defs: "shadow-utils"
-diff --git a/ssg/yaml.py b/ssg/yaml.py
-index cefbba374c..22cf5bad66 100644
---- a/ssg/yaml.py
-+++ b/ssg/yaml.py
-@@ -10,7 +10,8 @@
- 
- from .jinja import load_macros, process_file
- from .constants import (PKG_MANAGER_TO_SYSTEM,
--                        PKG_MANAGER_TO_CONFIG_FILE)
-+                        PKG_MANAGER_TO_CONFIG_FILE,
-+                        XCCDF_PLATFORM_TO_PACKAGE)
- from .constants import DEFAULT_UID_MIN
- 
- try:
-@@ -138,6 +139,9 @@ def open_raw(yaml_file):
- 
- def open_environment(build_config_yaml, product_yaml):
-     contents = open_raw(build_config_yaml)
-+    # Load common platform package mappings,
-+    # any specific mapping in product_yaml will override the default
-+    contents["platform_package_overrides"] = XCCDF_PLATFORM_TO_PACKAGE
-     contents.update(open_raw(product_yaml))
-     contents.update(_get_implied_properties(contents))
-     return contents
diff --git a/SOURCES/scap-security-guide-0.1.53-cui_kickstart-PR_6035.patch b/SOURCES/scap-security-guide-0.1.53-cui_kickstart-PR_6035.patch
deleted file mode 100644
index 927acb5..0000000
--- a/SOURCES/scap-security-guide-0.1.53-cui_kickstart-PR_6035.patch
+++ /dev/null
@@ -1,183 +0,0 @@
-From 8a6e3fcbe387e6b5476375448964dab198d94959 Mon Sep 17 00:00:00 2001
-From: Vojtech Polasek 
-Date: Wed, 2 Sep 2020 10:01:45 +0200
-Subject: [PATCH] add CUI kickstart for rhel8
-
----
- rhel8/kickstart/ssg-rhel8-cui-ks.cfg | 167 +++++++++++++++++++++++++++
- 1 file changed, 167 insertions(+)
- create mode 100644 rhel8/kickstart/ssg-rhel8-cui-ks.cfg
-
-diff --git a/rhel8/kickstart/ssg-rhel8-cui-ks.cfg b/rhel8/kickstart/ssg-rhel8-cui-ks.cfg
-new file mode 100644
-index 0000000000..0957fded96
---- /dev/null
-+++ b/rhel8/kickstart/ssg-rhel8-cui-ks.cfg
-@@ -0,0 +1,167 @@
-+# SCAP Security Guide CUI profile kickstart for Red Hat Enterprise Linux 8
-+#
-+# Based on:
-+# http://fedoraproject.org/wiki/Anaconda/Kickstart
-+# http://usgcb.nist.gov/usgcb/content/configuration/workstation-ks.cfg
-+
-+# Install a fresh new system (optional)
-+install
-+
-+# Specify installation method to use for installation
-+# To use a different one comment out the 'url' one below, update
-+# the selected choice with proper options & un-comment it
-+#
-+# Install from an installation tree on a remote server via FTP or HTTP:
-+# --url		the URL to install from
-+#
-+# Example:
-+#
-+# url --url=http://192.168.122.1/image
-+#
-+# Modify concrete URL in the above example appropriately to reflect the actual
-+# environment machine is to be installed in
-+#
-+# Other possible / supported installation methods:
-+# * install from the first CD-ROM/DVD drive on the system:
-+#
-+# cdrom
-+#
-+# * install from a directory of ISO images on a local drive:
-+#
-+# harddrive --partition=hdb2 --dir=/tmp/install-tree
-+#
-+# * install from provided NFS server:
-+#
-+# nfs --server= --dir= [--opts=]
-+#
-+# Set language to use during installation and the default language to use on the installed system (required)
-+lang en_US.UTF-8
-+
-+# Set system keyboard type / layout (required)
-+keyboard us
-+
-+# Configure network information for target system and activate network devices in the installer environment (optional)
-+# --onboot	enable device at a boot time
-+# --device	device to be activated and / or configured with the network command
-+# --bootproto	method to obtain networking configuration for device (default dhcp)
-+# --noipv6	disable IPv6 on this device
-+#
-+# NOTE: Usage of DHCP will fail CCE-27021-5 (DISA FSO RHEL-06-000292). To use static IP configuration,
-+#       "--bootproto=static" must be used. For example:
-+# network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
-+#
-+network --onboot yes --bootproto dhcp
-+
-+# Set the system's root password (required)
-+# Plaintext password is: server
-+# Refer to e.g.
-+#   https://pykickstart.readthedocs.io/en/latest/commands.html#rootpw
-+# to see how to create encrypted password form for different plaintext password
-+rootpw --iscrypted $6$0WWGZ1e6icT$1KiHZK.Nzp3HQerfiy8Ic3pOeCWeIzA.zkQ7mkvYT3bNC5UeGK2ceE5b6TkSg4D/kiSudkT04QlSKknsrNE220
-+
-+# The selected profile will restrict root login
-+# Add a user that can login and escalate privileges
-+# Plaintext password is: admin123
-+user --name=admin --groups=wheel --password=$6$Ga6ZnIlytrWpuCzO$q0LqT1USHpahzUafQM9jyHCY9BiE5/ahXLNWUMiVQnFGblu0WWGZ1e6icTaCGO4GNgZNtspp1Let/qpM7FMVB0 --iscrypted
-+
-+# Configure firewall settings for the system (optional)
-+# --enabled	reject incoming connections that are not in response to outbound requests
-+# --ssh		allow sshd service through the firewall
-+firewall --enabled --ssh
-+
-+# Set up the authentication options for the system (required)
-+# --enableshadow	enable shadowed passwords by default
-+# --passalgo		hash / crypt algorithm for new passwords
-+# See the manual page for authconfig for a complete list of possible options.
-+authconfig --enableshadow --passalgo=sha512
-+
-+# State of SELinux on the installed system (optional)
-+# Defaults to enforcing
-+selinux --enforcing
-+
-+# Set the system time zone (required)
-+timezone --utc America/New_York
-+
-+# Specify how the bootloader should be installed (required)
-+# Refer to e.g.
-+#   https://pykickstart.readthedocs.io/en/latest/commands.html#rootpw
-+# to see how to create encrypted password form for different plaintext password
-+bootloader --location=mbr --append="audit=1 audit_backlog_limit=8192 slub_debug=P page_poison=1 vsyscall=none"
-+
-+# Initialize (format) all disks (optional)
-+zerombr
-+
-+# The following partition layout scheme assumes disk of size 20GB or larger
-+# Modify size of partitions appropriately to reflect actual machine's hardware
-+# 
-+# Remove Linux partitions from the system prior to creating new ones (optional)
-+# --linux	erase all Linux partitions
-+# --initlabel	initialize the disk label to the default based on the underlying architecture
-+clearpart --linux --initlabel
-+
-+# Create primary system partitions (required for installs)
-+part /boot --fstype=xfs --size=512
-+part pv.01 --grow --size=1
-+
-+# Create a Logical Volume Management (LVM) group (optional)
-+volgroup VolGroup --pesize=4096 pv.01
-+
-+# Create particular logical volumes (optional)
-+logvol / --fstype=xfs --name=root --vgname=VolGroup --size=11264 --grow
-+# Ensure /home Located On Separate Partition
-+logvol /home --fstype=xfs --name=home --vgname=VolGroup --size=1024 --fsoptions="nodev"
-+# Ensure /tmp Located On Separate Partition
-+logvol /tmp --fstype=xfs --name=tmp --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec"
-+# Ensure /var/tmp Located On Separate Partition
-+logvol /var/tmp --fstype=xfs --name=vartmp --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec"
-+# Ensure /var Located On Separate Partition
-+logvol /var --fstype=xfs --name=var --vgname=VolGroup --size=2048 --fsoptions="nodev"
-+# Ensure /var/log Located On Separate Partition
-+logvol /var/log --fstype=xfs --name=log --vgname=VolGroup --size=1024 --fsoptions="nodev,nosuid,noexec"
-+# Ensure /var/log/audit Located On Separate Partition
-+logvol /var/log/audit --fstype=xfs --name=audit --vgname=VolGroup --size=512 --fsoptions="nodev,nosuid,noexec"
-+logvol swap --name=swap --vgname=VolGroup --size=2016
-+
-+# The OpenSCAP installer add-on is used to apply SCAP (Security Content Automation Protocol)
-+# content - security policies - on the installed system.This add-on has been enabled by default
-+# since Red Hat Enterprise Linux 7.2. When enabled, the packages necessary to provide this 
-+# functionality will automatically be installed. However, by default, no policies are enforced,
-+# meaning that no checks are performed during or after installation unless specifically configured.
-+#  
-+#  Important
-+#   Applying a security policy is not necessary on all systems. This screen should only be used
-+#   when a specific policy is mandated by your organization rules or government regulations.
-+#   Unlike most other commands, this add-on does not accept regular options, but uses key-value
-+#   pairs in the body of the %addon definition instead. These pairs are whitespace-agnostic.
-+#   Values can be optionally enclosed in single quotes (') or double quotes (").
-+#   
-+#  The following keys are recognized by the add-on:
-+#    content-type - Type of the security content. Possible values are datastream, archive, rpm, and scap-security-guide.
-+#      - If the content-type is scap-security-guide, the add-on will use content provided by the
-+#        scap-security-guide package, which is present on the boot media. This means that all other keys except profile will have no effect.
-+#    content-url - Location of the security content. The content must be accessible using HTTP, HTTPS, or FTP; local storage is currently not supported. A network connection must be available to reach content definitions in a remote location.
-+#    datastream-id - ID of the data stream referenced in the content-url value. Used only if content-type is datastream.
-+#    xccdf-id - ID of the benchmark you want to use.
-+#    xccdf-path - Path to the XCCDF file which should be used; given as a relative path in the archive.
-+#    profile - ID of the profile to be applied. Use default to apply the default profile.
-+#    fingerprint - A MD5, SHA1 or SHA2 checksum of the content referenced by content-url.
-+#    tailoring-path - Path to a tailoring file which should be used, given as a relative path in the archive.
-+#
-+#  The following is an example %addon org_fedora_oscap section which uses content from the
-+#  scap-security-guide on the installation media: 
-+%addon org_fedora_oscap
-+	content-type = scap-security-guide
-+	profile = xccdf_org.ssgproject.content_profile_cui
-+%end
-+
-+# Packages selection (%packages section is required)
-+%packages
-+
-+# Require @Base
-+@Base
-+
-+%end # End of %packages section
-+
-+# Reboot after the installation is complete (optional)
-+# --eject	attempt to eject CD or DVD media before rebooting
-+reboot --eject
diff --git a/SOURCES/scap-security-guide-0.1.53-drop-zipl-pti-rule_PR_6065.patch b/SOURCES/scap-security-guide-0.1.53-drop-zipl-pti-rule_PR_6065.patch
deleted file mode 100644
index 2023459..0000000
--- a/SOURCES/scap-security-guide-0.1.53-drop-zipl-pti-rule_PR_6065.patch
+++ /dev/null
@@ -1,92 +0,0 @@
-From fbcd3e42106b95efd8a63914a558c04c76487783 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 21 Sep 2020 10:26:53 +0200
-Subject: [PATCH] Remove zIPL rule for PTI bootloader option
-
-This setting is to mitigate a problem specific for intel archs.
-Also returns the CCE to the pool.
----
- .../zipl_pti_argument/rule.yml                | 38 -------------------
- rhel8/profiles/ospp.profile                   |  1 -
- rhel8/profiles/stig.profile                   |  1 -
- .../data/profile_stability/rhel8/ospp.profile |  1 -
- 4 files changed, 41 deletions(-)
- delete mode 100644 linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-
-diff --git a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml b/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-deleted file mode 100644
-index 96170e6d85..0000000000
---- a/linux_os/guide/system/bootloader-zipl/zipl_pti_argument/rule.yml
-+++ /dev/null
-@@ -1,38 +0,0 @@
--documentation_complete: true
--
--prodtype: rhel8
--
--title: 'Enable Kernel Page-Table Isolation (KPTI) in zIPL'
--
--description: |-
--    To enable Kernel page-table isolation,
--    check that all boot entries in /boot/loader/entries/*.conf have pti=on
--    included in its options.

--    To ensure that new kernels and boot entries continue to enable page-table isolation,
--    add pti=on to /etc/kernel/cmdline.
--
--rationale: |-
--    Kernel page-table isolation is a kernel feature that mitigates
--    the Meltdown security vulnerability and hardens the kernel
--    against attempts to bypass kernel address space layout
--    randomization (KASLR).
--
--severity: medium
--
--identifiers:
--    cce@rhel8: 83361-6
--
--ocil_clause: 'Kernel page-table isolation is not enabled'
--
--ocil: |-
--  To check that page-table isolation is enabled at boot time, check all boot entries with following command:
--  
sudo grep -L "^options\s+.*\bpti=on\b" /boot/loader/entries/*.conf

--  No line should be returned, each line returned is a boot entry that doesn't enable page-table isolation .
--
--platform: machine
--
--template:
--  name: zipl_bls_entries_option
--  vars:
--    arg_name: pti
--    arg_value: 'on'
-diff --git a/rhel8/profiles/ospp.profile b/rhel8/profiles/ospp.profile
-index 5e81e4a92a..46f00c89f1 100644
---- a/rhel8/profiles/ospp.profile
-+++ b/rhel8/profiles/ospp.profile
-@@ -426,4 +426,3 @@ selections:
-     - zipl_vsyscall_argument
-     - zipl_vsyscall_argument.role=unscored
-     - zipl_vsyscall_argument.severity=info
--    - zipl_pti_argument
-diff --git a/rhel8/profiles/stig.profile b/rhel8/profiles/stig.profile
-index 53647475aa..817d5dbadd 100644
---- a/rhel8/profiles/stig.profile
-+++ b/rhel8/profiles/stig.profile
-@@ -52,7 +52,6 @@ selections:
-     - "!zipl_audit_argument"
-     - "!zipl_audit_backlog_limit_argument"
-     - "!zipl_page_poison_argument"
--    - "!zipl_pti_argument"
-     - "!zipl_slub_debug_argument"
-     - "!zipl_vsyscall_argument"
-     - "!zipl_vsyscall_argument.role=unscored"
-diff --git a/tests/data/profile_stability/rhel8/ospp.profile b/tests/data/profile_stability/rhel8/ospp.profile
-index 7b7307cba8..223b1423cd 100644
---- a/tests/data/profile_stability/rhel8/ospp.profile
-+++ b/tests/data/profile_stability/rhel8/ospp.profile
-@@ -219,7 +219,6 @@ selections:
- - zipl_bls_entries_only
- - zipl_bootmap_is_up_to_date
- - zipl_page_poison_argument
--- zipl_pti_argument
- - zipl_slub_debug_argument
- - zipl_vsyscall_argument
- - var_sshd_set_keepalive=0
diff --git a/SOURCES/scap-security-guide-0.1.53-fix-empty-bash-wrapping-PR_6173.patch b/SOURCES/scap-security-guide-0.1.53-fix-empty-bash-wrapping-PR_6173.patch
deleted file mode 100644
index 0199bf4..0000000
--- a/SOURCES/scap-security-guide-0.1.53-fix-empty-bash-wrapping-PR_6173.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-From 08d5fb8355020856282eecfcdd09e96d9850cd62 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Fri, 9 Oct 2020 09:30:35 +0200
-Subject: [PATCH] Do not platform wrap empty Bash remediation
-
-The fix text for a rule can end up empty if a Jinja macro or conditional
-doesn't render any text.
-In these cases, avoid wrapping empty lines in an if-else, as this causes
-syntax error.
----
- ssg/build_remediations.py | 15 +++++++++------
- 1 file changed, 9 insertions(+), 6 deletions(-)
-
-diff --git a/ssg/build_remediations.py b/ssg/build_remediations.py
-index f269d4d2d6..572db61701 100644
---- a/ssg/build_remediations.py
-+++ b/ssg/build_remediations.py
-@@ -273,6 +273,13 @@ def parse_from_file_with_jinja(self, env_yaml):
-         self.local_env_yaml.update(env_yaml)
-         result = super(BashRemediation, self).parse_from_file_with_jinja(self.local_env_yaml)
- 
-+        # Avoid platform wrapping empty fix text
-+        # Remediations can be empty when a Jinja macro or conditional
-+        # renders no fix text for a product
-+        stripped_fix_text = result.contents.strip()
-+        if stripped_fix_text == "":
-+            return result
-+
-         rule_platforms = set()
-         if self.associated_rule:
-             # There can be repeated inherited platforms and rule platforms
-@@ -301,15 +308,11 @@ def parse_from_file_with_jinja(self, env_yaml):
- 
-             all_conditions = " && ".join(platform_conditionals)
-             wrapped_fix_text.append("if {0}; then".format(all_conditions))
--
--            # Avoid adding extra blank line
--            if not result.contents.startswith("\n"):
--                wrapped_fix_text.append("")
--
-+            wrapped_fix_text.append("")
-             # It is possible to indent the original body of the remediation with textwrap.indent(),
-             # however, it is not supported by python2, and there is a risk of breaking remediations
-             # For example, remediations with a here-doc block could be affected.
--            wrapped_fix_text.append("{0}".format(result.contents))
-+            wrapped_fix_text.append("{0}".format(stripped_fix_text))
-             wrapped_fix_text.append("")
-             wrapped_fix_text.append("else")
-             wrapped_fix_text.append("    >&2 echo 'Remediation is not applicable, nothing was done'")
diff --git a/SOURCES/scap-security-guide-0.1.53-fix-grub2-applicability-in-aarch64-ppc64le-PR_6153.patch b/SOURCES/scap-security-guide-0.1.53-fix-grub2-applicability-in-aarch64-ppc64le-PR_6153.patch
deleted file mode 100644
index 83df4d6..0000000
--- a/SOURCES/scap-security-guide-0.1.53-fix-grub2-applicability-in-aarch64-ppc64le-PR_6153.patch
+++ /dev/null
@@ -1,116 +0,0 @@
-From cf1d85924b5945506e57f8701be066c83a894378 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 5 Oct 2020 16:40:39 +0200
-Subject: [PATCH 1/2] Check for grub2-common instead of grub2-pc
-
-Check for grub2 intallation based on grub2-common.
-grub2-pc is a x86_64 package, but other arches use grub2 as well.
----
- .../checks/oval/installed_env_has_grub2_package.xml  | 12 ++++++------
- ssg/constants.py                                     |  2 +-
- 2 files changed, 7 insertions(+), 7 deletions(-)
-
-diff --git a/shared/checks/oval/installed_env_has_grub2_package.xml b/shared/checks/oval/installed_env_has_grub2_package.xml
-index e83f45bc3b..2a170d668e 100644
---- a/shared/checks/oval/installed_env_has_grub2_package.xml
-+++ b/shared/checks/oval/installed_env_has_grub2_package.xml
-@@ -6,31 +6,31 @@
-       
-         multi_platform_all
-       
--      Checks if package grub2-pc is installed.
-+      Checks if package grub2-common is installed.
-       
-     
-     
--      
-+      
-     
-   
- 
- {{% if pkg_system == "rpm" %}}
-   
-+  comment="system has package grub2-common installed">
-     
-   
-   
--    grub2-pc
-+    grub2-common
-   
- {{% elif pkg_system == "dpkg" %}}
-   
-+  comment="system has package grub2-common installed">
-     
-   
-   
--    grub2-pc
-+    grub2-common
-   
- {{% endif %}}
- 
-diff --git a/ssg/constants.py b/ssg/constants.py
-index b07fe5f0fe..88316374b5 100644
---- a/ssg/constants.py
-+++ b/ssg/constants.py
-@@ -468,7 +468,7 @@
- 
- # Default platform to package mapping
- XCCDF_PLATFORM_TO_PACKAGE = {
--  "grub2": "grub2-pc",
-+  "grub2": "grub2-common",
-   "login_defs": "login",
-   "sssd": "sssd-common",
-   "zipl": "s390utils-base",
-
-From fba876cfc7f85f5b9a696d0f5fa1177299b7c6bb Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Mon, 5 Oct 2020 16:49:15 +0200
-Subject: [PATCH 2/2] Handle exception of grub2-coomon in ppc64le
-
-ppc64le systems can use Grub2 or OPAL and the package set will be the
-same in both cases.
-Add a few more checks to make sure ppc64le arch is handled correctly.
----
- .../oval/installed_env_has_grub2_package.xml  | 19 ++++++++++++++++++-
- 1 file changed, 18 insertions(+), 1 deletion(-)
-
-diff --git a/shared/checks/oval/installed_env_has_grub2_package.xml b/shared/checks/oval/installed_env_has_grub2_package.xml
-index 2a170d668e..fb2c9cc784 100644
---- a/shared/checks/oval/installed_env_has_grub2_package.xml
-+++ b/shared/checks/oval/installed_env_has_grub2_package.xml
-@@ -9,8 +9,18 @@
-       Checks if package grub2-common is installed.
-       
-     
--    
-+    
-       
-+      
-+        
-+        
-+        
-+        
-+        
-+      
-     
-   
- 
-@@ -34,4 +44,11 @@
-   
- {{% endif %}}
- 
-+  
-+    
-+  
-+  
-+    /sys/firmware/opal
-+  
-+
- 
diff --git a/SOURCES/scap-security-guide-0.1.53-fix-platform-to-package-mapping_PR_6059.patch b/SOURCES/scap-security-guide-0.1.53-fix-platform-to-package-mapping_PR_6059.patch
deleted file mode 100644
index 8c84ee4..0000000
--- a/SOURCES/scap-security-guide-0.1.53-fix-platform-to-package-mapping_PR_6059.patch
+++ /dev/null
@@ -1,38 +0,0 @@
-From 7dfeb5ec0513a58502eb83aa2900e7c5fb0d478e Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 8 Sep 2020 11:29:57 +0200
-Subject: [PATCH] Fix load of product platform mapping
-
-The product specific mappings were overriding the common mappings,
-instead of being merged with them.
----
- ssg/yaml.py | 8 +++++---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/ssg/yaml.py b/ssg/yaml.py
-index 22cf5bad66..d8856e52c9 100644
---- a/ssg/yaml.py
-+++ b/ssg/yaml.py
-@@ -13,6 +13,7 @@
-                         PKG_MANAGER_TO_CONFIG_FILE,
-                         XCCDF_PLATFORM_TO_PACKAGE)
- from .constants import DEFAULT_UID_MIN
-+from .utils import merge_dicts
- 
- try:
-     from yaml import CSafeLoader as yaml_SafeLoader
-@@ -139,10 +140,11 @@ def open_raw(yaml_file):
- 
- def open_environment(build_config_yaml, product_yaml):
-     contents = open_raw(build_config_yaml)
--    # Load common platform package mappings,
--    # any specific mapping in product_yaml will override the default
--    contents["platform_package_overrides"] = XCCDF_PLATFORM_TO_PACKAGE
-     contents.update(open_raw(product_yaml))
-+    platform_package_overrides = contents.get("platform_package_overrides", {})
-+    # Merge common platform package mappings, while keeping product specific mappings
-+    contents["platform_package_overrides"] = merge_dicts(XCCDF_PLATFORM_TO_PACKAGE,
-+                                                         platform_package_overrides)
-     contents.update(_get_implied_properties(contents))
-     return contents
- 
diff --git a/SOURCES/scap-security-guide-0.1.53-fix-zipl-package-mapping_PR_6130.patch b/SOURCES/scap-security-guide-0.1.53-fix-zipl-package-mapping_PR_6130.patch
deleted file mode 100644
index fc1fecd..0000000
--- a/SOURCES/scap-security-guide-0.1.53-fix-zipl-package-mapping_PR_6130.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-From 570dc073739e9044b54e872c8368125bccadb704 Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 29 Sep 2020 15:28:02 +0200
-Subject: [PATCH] Fix zIPL package mapping
-
----
- ssg/constants.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/ssg/constants.py b/ssg/constants.py
-index 0eca2f4f95..fa6c756ff6 100644
---- a/ssg/constants.py
-+++ b/ssg/constants.py
-@@ -470,7 +470,7 @@
-   "grub2": "grub2-pc",
-   "login_defs": "login",
-   "sssd": "sssd-common",
--  "zipl": "s390x-utils",
-+  "zipl": "s390utils-base",
- }
- 
- # _version_name_map = {
diff --git a/SOURCES/scap-security-guide-0.1.53-move-grub2-vsyscall-rule_PR_6129.patch b/SOURCES/scap-security-guide-0.1.53-move-grub2-vsyscall-rule_PR_6129.patch
deleted file mode 100644
index 20310cb..0000000
--- a/SOURCES/scap-security-guide-0.1.53-move-grub2-vsyscall-rule_PR_6129.patch
+++ /dev/null
@@ -1,16 +0,0 @@
-From 7a069a2deb4d1ce69b02b7615523424f2ecf281f Mon Sep 17 00:00:00 2001
-From: Watson Sato 
-Date: Tue, 29 Sep 2020 15:04:39 +0200
-Subject: [PATCH] Move grub2_vsyscall_argument to grub2 group
-
-This will put the rule under grub2 platform, so the rule is only
-applicable on a machine system with grub2.
----
- .../grub2_vsyscall_argument/rule.yml                              | 0
- 1 file changed, 0 insertions(+), 0 deletions(-)
- rename linux_os/guide/system/{permissions/restrictions => bootloader-grub2}/grub2_vsyscall_argument/rule.yml (100%)
-
-diff --git a/linux_os/guide/system/permissions/restrictions/grub2_vsyscall_argument/rule.yml b/linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml
-similarity index 100%
-rename from linux_os/guide/system/permissions/restrictions/grub2_vsyscall_argument/rule.yml
-rename to linux_os/guide/system/bootloader-grub2/grub2_vsyscall_argument/rule.yml
diff --git a/SOURCES/scap-security-guide-0.1.55-OL7_DISA_STIG_v2r1_update-PR_6538.patch b/SOURCES/scap-security-guide-0.1.55-OL7_DISA_STIG_v2r1_update-PR_6538.patch
new file mode 100644
index 0000000..6ab80bd
--- /dev/null
+++ b/SOURCES/scap-security-guide-0.1.55-OL7_DISA_STIG_v2r1_update-PR_6538.patch
@@ -0,0 +1,11626 @@
+From 47656aab42dbd366b4d0602ffa64eff9b0ce1985 Mon Sep 17 00:00:00 2001
+From: Federico Ramirez 
+Date: Fri, 15 Jan 2021 09:49:13 -0600
+Subject: [PATCH 1/3] OL7 DISA STIG v2r1 update
+
+Signed-off-by: Federico Ramirez 
+---
+ .../accounts_passwords_pam_faillock_deny/rule.yml        | 2 +-
+ .../accounts_passwords_pam_faillock_interval/rule.yml    | 2 +-
+ .../accounts_passwords_pam_faillock_unlock_time/rule.yml | 2 +-
+ .../smart_card_login/install_smartcard_packages/rule.yml | 2 +-
+ .../partitions/mount_option_dev_shm_nodev/rule.yml       | 2 +-
+ .../partitions/mount_option_dev_shm_nosuid/rule.yml      | 2 +-
+ .../guide/system/selinux/selinux_policytype/rule.yml     | 3 ++-
+ .../system/selinux/selinux_user_login_roles/rule.yml     | 2 +-
+ .../dconf_gnome_disable_ctrlaltdel_reboot/rule.yml       | 3 ++-
+ .../rpm_verification/rpm_verify_ownership/rule.yml       | 2 +-
+ .../software/sudo/sudo_remove_no_authenticate/rule.yml   | 1 +
+ ol7/profiles/stig.profile                                | 9 ++++-----
+ 12 files changed, 17 insertions(+), 15 deletions(-)
+
+diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml
+index e09367be0a..ccee5dd048 100644
+--- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml
++++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_deny/rule.yml
+@@ -33,7 +33,7 @@ references:
+     cis: 5.3.2
+     cjis: 5.5.3
+     cui: 3.1.8
+-    disa: CCI-000044,CCI-002238
++    disa: CCI-000044,CCI-002236,CCI-002237,CCI-002238
+     nist: CM-6(a),AC-7(a)
+     nist-csf: PR.AC-7
+     ospp: FIA_AFL.1
+diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml
+index 14aad917bd..d1b9c396ae 100644
+--- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml
++++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_interval/rule.yml
+@@ -40,7 +40,7 @@ identifiers:
+ 
+ references:
+     stigid@ol7: OL07-00-010320
+-    disa: CCI-000044,CCI-002238
++    disa: CCI-000044,CCI-002236,CCI-002237,CCI-002238
+     nist: CM-6(a),AC-7(a)
+     nist-csf: PR.AC-7
+     ospp: FIA_AFL.1
+diff --git a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml
+index 2888c9ab9a..2fff1c6011 100644
+--- a/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml
++++ b/linux_os/guide/system/accounts/accounts-pam/locking_out_password_attempts/accounts_passwords_pam_faillock_unlock_time/rule.yml
+@@ -36,7 +36,7 @@ references:
+     cis: 5.3.2
+     cjis: 5.5.3
+     cui: 3.1.8
+-    disa: CCI-000044,CCI-002238
++    disa: CCI-000044,CCI-002236,CCI-002237,CCI-002238
+     nist: CM-6(a),AC-7(b)
+     nist-csf: PR.AC-7
+     ospp: FIA_AFL.1
+diff --git a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml
+index 8bb91bd3e4..b3210d6adc 100644
+--- a/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml
++++ b/linux_os/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/install_smartcard_packages/rule.yml
+@@ -30,7 +30,7 @@ references:
+     stigid@ol7: OL07-00-041001
+     disa: CCI-000765,CCI-001948,CCI-001953,CCI-001954
+     nist: CM-6(a)
+-    srg: SRG-OS-000105-GPOS-00052,SRG-OS-000375-GPOS-00160,SRG-OS-000376-GPOS-00161,SRG-OS-000377-GPOS-00162
++    srg: SRG-OS-000105-GPOS-00052,SRG-OS-000375-GPOS-00160,SRG-OS-000375-GPOS-00161,SRG-OS-000377-GPOS-00162
+     stigid@rhel7: RHEL-07-041001
+ 
+ ocil_clause: 'smartcard software is not installed'
+diff --git a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml
+index 140a2eafc0..f8359dc122 100644
+--- a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml
++++ b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nodev/rule.yml
+@@ -24,7 +24,7 @@ identifiers:
+ references:
+     cis@rhel8: 1.1.5
+     cis@ubuntu1804: 1.1.14
+-    stigid@ol7: OL07-00-021022
++    stigid@ol7: OL07-00-021024
+     stigid@rhel7: RHEL-07-021022
+     disa: CCI-001764
+     nist: CM-7(a),CM-7(b),CM-6(a),AC-6,AC-6(1),MP-7
+diff --git a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml
+index be127be367..8dc400965b 100644
+--- a/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml
++++ b/linux_os/guide/system/permissions/partitions/mount_option_dev_shm_nosuid/rule.yml
+@@ -24,7 +24,7 @@ identifiers:
+ references:
+     cis@rhel8: 1.1.16
+     cis@ubuntu1804: 1.1.15
+-    stigid@ol7: OL07-00-021023
++    stigid@ol7: OL07-00-021024
+     stigid@rhel7: RHEL-07-021023
+     disa: CCI-001764
+     nist: CM-7(a),CM-7(b),CM-6(a),AC-6,AC-6(1),MP-7
+diff --git a/linux_os/guide/system/selinux/selinux_policytype/rule.yml b/linux_os/guide/system/selinux/selinux_policytype/rule.yml
+index ee2a6054b2..ba2b9dc94f 100644
+--- a/linux_os/guide/system/selinux/selinux_policytype/rule.yml
++++ b/linux_os/guide/system/selinux/selinux_policytype/rule.yml
+@@ -33,10 +33,11 @@ identifiers:
+     cce@rhcos4: CCE-82532-3
+ 
+ references:
++    stigid@ol7: OL07-00-020220
+     anssi: BP28(R66)
+     cis@rhel8: 1.7.1.3
+     cui: 3.1.2,3.7.2
+-    disa: CCI-002696
++    disa: CCI-002165,CCI-002696
+     hipaa: 164.308(a)(1)(ii)(D),164.308(a)(3),164.308(a)(4),164.310(b),164.310(c),164.312(a),164.312(e)
+     nist: AC-3,AC-3(3)(a),AU-9,SC-7(21)
+     nist-csf: DE.AE-1,ID.AM-3,PR.AC-4,PR.AC-5,PR.AC-6,PR.DS-5,PR.PT-1,PR.PT-3,PR.PT-4
+diff --git a/linux_os/guide/system/selinux/selinux_user_login_roles/rule.yml b/linux_os/guide/system/selinux/selinux_user_login_roles/rule.yml
+index 58500a63f8..1a02b545d3 100644
+--- a/linux_os/guide/system/selinux/selinux_user_login_roles/rule.yml
++++ b/linux_os/guide/system/selinux/selinux_user_login_roles/rule.yml
+@@ -37,7 +37,7 @@ identifiers:
+ 
+ references:
+     stigid@ol7: OL07-00-020020
+-    disa: CCI-002235
++    disa: CCI-002165,CCI-002235
+     srg: SRG-OS-000324-GPOS-00125
+     stigid@rhel7: RHEL-07-020020
+ 
+diff --git a/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml b/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml
+index c1a86bf4c8..d666768bce 100644
+--- a/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml
++++ b/linux_os/guide/system/software/gnome/gnome_system_settings/dconf_gnome_disable_ctrlaltdel_reboot/rule.yml
+@@ -1,6 +1,6 @@
+ documentation_complete: true
+ 
+-prodtype: fedora,rhel7,rhel8
++prodtype: fedora,ol7,rhel7,rhel8
+ 
+ title: 'Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3'
+ 
+@@ -32,6 +32,7 @@ identifiers:
+     cce@rhel7: CCE-80124-1
+ 
+ references:
++    stigid@ol7: OL07-00-020231
+     cui: 3.1.2
+     disa: CCI-000366
+     nist: CM-6(a),AC-6(1),CM-7(b)
+diff --git a/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_ownership/rule.yml b/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_ownership/rule.yml
+index 24c4517aa7..d4f76c4ebd 100644
+--- a/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_ownership/rule.yml
++++ b/linux_os/guide/system/software/integrity/software-integrity/rpm_verification/rpm_verify_ownership/rule.yml
+@@ -41,7 +41,7 @@ references:
+     nist: CM-6(d),CM-6(c),SI-7,SI-7(1),SI-7(6),AU-9(3)
+     nist-csf: PR.AC-4,PR.DS-5,PR.IP-1,PR.PT-1
+     pcidss: Req-11.5
+-    srg: SRG-OS-000257-GPOS-00098,SRG-OS-000278-GPOS-00108
++    srg: SRG-OS-000256-GPOS-00097,SRG-OS-000257-GPOS-00098,SRG-OS-000278-GPOS-00108
+     isa-62443-2013: 'SR 2.1,SR 2.10,SR 2.11,SR 2.12,SR 2.8,SR 2.9,SR 5.2,SR 7.6'
+     isa-62443-2009: 4.3.3.3.9,4.3.3.5.8,4.3.3.7.3,4.3.4.3.2,4.3.4.3.3,4.3.4.4.7,4.4.2.1,4.4.2.2,4.4.2.4
+     cobit5: APO01.06,APO11.04,BAI03.05,BAI10.01,BAI10.02,BAI10.03,BAI10.05,DSS05.04,DSS05.07,DSS06.02,MEA02.01
+diff --git a/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml b/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml
+index db826d1123..e704df8983 100644
+--- a/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml
++++ b/linux_os/guide/system/software/sudo/sudo_remove_no_authenticate/rule.yml
+@@ -23,6 +23,7 @@ identifiers:
+     cce@sle12: CCE-83013-3
+ 
+ references:
++    stigid@ol7: OL07-00-010350
+     anssi: BP28(R5),BP28(R59)
+     disa: CCI-002038
+     nist: IA-11,CM-6(a)
+diff --git a/ol7/profiles/stig.profile b/ol7/profiles/stig.profile
+index 1cfad16c08..ecb6cccce4 100644
+--- a/ol7/profiles/stig.profile
++++ b/ol7/profiles/stig.profile
+@@ -4,7 +4,7 @@ title: 'DISA STIG for Oracle Linux 7'
+ 
+ description: |-
+     This profile contains configuration checks that align to the
+-    DISA STIG for Oracle Linux V1R1.
++    DISA STIG for Oracle Linux V2R1.
+ 
+ selections:
+     - login_banner_text=dod_banners
+@@ -55,7 +55,6 @@ selections:
+     - dconf_gnome_screensaver_lock_locked
+     - dconf_gnome_enable_smartcard_auth
+     - dconf_gnome_screensaver_idle_delay
+-    - package_screen_installed
+     - dconf_gnome_screensaver_idle_activation_enabled
+     - dconf_gnome_screensaver_idle_activation_locked
+     - dconf_gnome_screensaver_lock_delay
+@@ -115,7 +114,6 @@ selections:
+     - accounts_no_uid_except_zero
+     - no_files_unowned_by_user
+     - file_permissions_ungroupowned
+-    - accounts_user_interactive_home_directory_defined
+     - accounts_have_homedir_login_defs
+     - accounts_user_interactive_home_directory_exists
+     - file_permissions_home_directories
+@@ -144,7 +142,6 @@ selections:
+     - service_kdump_disabled
+     - partition_for_home
+     - partition_for_var
+-    - partition_for_var_log_audit
+     - partition_for_tmp
+     - grub2_enable_fips_mode
+     - aide_verify_acls
+@@ -159,7 +156,6 @@ selections:
+     - auditd_audispd_configure_remote_server
+     - auditd_audispd_encrypt_sent_records
+     - auditd_audispd_disk_full_action
+-    - auditd_name_format
+     - auditd_data_retention_space_left
+     - auditd_data_retention_space_left_action
+     - auditd_data_retention_action_mail_acct
+@@ -288,3 +284,6 @@ selections:
+     - audit_rules_usergroup_modification_opasswd
+     - sysctl_net_ipv4_conf_all_accept_redirects
+     - wireless_disable_interfaces
++    - sudo_remove_no_authenticate
++    - selinux_policytype
++    - dconf_gnome_disable_ctrlaltdel_reboot
+
+From 666826067d2b2bbaacd0fc6f32c93cfecdb8b010 Mon Sep 17 00:00:00 2001
+From: Federico Ramirez 
+Date: Fri, 15 Jan 2021 09:49:45 -0600
+Subject: [PATCH 2/3] Update OL7 stig overlay to match v2r1
+
+Signed-off-by: Federico Ramirez 
+---
+ ol7/overlays/stig_overlay.xml                 |  993 +++-
+ .../disa-stig-ol7-v1r1-xccdf-manual.xml       | 4928 ----------------
+ .../disa-stig-ol7-v2r1-xccdf-manual.xml       | 5072 +++++++++++++++++
+ 3 files changed, 6063 insertions(+), 4930 deletions(-)
+ delete mode 100644 shared/references/disa-stig-ol7-v1r1-xccdf-manual.xml
+ create mode 100644 shared/references/disa-stig-ol7-v2r1-xccdf-manual.xml
+
+diff --git a/ol7/overlays/stig_overlay.xml b/ol7/overlays/stig_overlay.xml
+index 92584b1b78..2345ff7494 100644
+--- a/ol7/overlays/stig_overlay.xml
++++ b/ol7/overlays/stig_overlay.xml
+@@ -1,2 +1,991 @@
+-
+-</overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010020" ruleid="rpm_verify_hashes" severity="high"><VMSinfo SVKey="108151" VKey="99047" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values." /></overlay><overlay disa="1388" owner="disastig" ownerid="OL07-00-010030" ruleid="dconf_gnome_banner_enabled" severity="medium"><VMSinfo SVKey="108153" VKey="99049" VRelease="r1" /><title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon." /></overlay><overlay disa="48" owner="disastig" ownerid="OL07-00-010040" ruleid="dconf_gnome_login_banner_text" severity="medium"><VMSinfo SVKey="108155" VKey="99051" VRelease="r1" /><title text="The Oracle Linux operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon." /></overlay><overlay disa="48" owner="disastig" ownerid="OL07-00-010050" ruleid="banner_etc_issue" severity="medium"><VMSinfo SVKey="108157" VKey="99053" VRelease="r1" /><title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon." /></overlay><overlay disa="58" owner="disastig" ownerid="OL07-00-010060" ruleid="dconf_gnome_screensaver_lock_enabled" severity="medium"><VMSinfo SVKey="108159" VKey="99055" VRelease="r1" /><title text="The Oracle Linux operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures." /></overlay><overlay disa="1948" owner="disastig" ownerid="OL07-00-010061" ruleid="dconf_gnome_enable_smartcard_auth" severity="medium"><VMSinfo SVKey="108161" VKey="99057" VRelease="r1" /><title text="The Oracle Linux operating system must uniquely identify and must authenticate users using multifactor authentication via a graphical user logon." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010062" ruleid="dconf_gnome_screensaver_lock_locked" severity="medium"><VMSinfo SVKey="108163" VKey="99059" VRelease="r1" /><title text="The Oracle Linux operating system must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010070" ruleid="dconf_gnome_screensaver_idle_delay" severity="medium"><VMSinfo SVKey="108165" VKey="99061" VRelease="r1" /><title text="The Oracle Linux operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010081" ruleid="dconf_gnome_screensaver_user_locks" severity="medium"><VMSinfo SVKey="108167" VKey="99063" VRelease="r1" /><title text="The Oracle Linux operating system must prevent a user from overriding the screensaver lock-delay setting for the graphical user interface." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010082" ruleid="dconf_gnome_session_idle_user_locks" severity="medium"><VMSinfo SVKey="108169" VKey="99065" VRelease="r1" /><title text="The Oracle Linux operating system must prevent a user from overriding the session idle-delay setting for the graphical user interface." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010090" ruleid="package_screen_installed" severity="medium"><VMSinfo SVKey="108171" VKey="99067" VRelease="r1" /><title text="The Oracle Linux operating system must have the screen package installed." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010100" ruleid="dconf_gnome_screensaver_idle_activation_enabled" severity="medium"><VMSinfo SVKey="108173" VKey="99069" VRelease="r1" /><title text="The Oracle Linux operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010101" ruleid="dconf_gnome_screensaver_idle_activation_locked" severity="medium"><VMSinfo SVKey="108175" VKey="99071" VRelease="r1" /><title text="The Oracle Linux operating system must prevent a user from overriding the screensaver idle-activation-enabled setting for the graphical user interface." /></overlay><overlay disa="57" owner="disastig" ownerid="OL07-00-010110" ruleid="dconf_gnome_screensaver_lock_delay" severity="medium"><VMSinfo SVKey="108177" VKey="99073" VRelease="r1" /><title text="The Oracle Linux operating system must initiate a session lock for graphical user interfaces when the screensaver is activated." /></overlay><overlay disa="192" owner="disastig" ownerid="OL07-00-010118" ruleid="accounts_password_pam_retry" severity="medium"><VMSinfo SVKey="108179" VKey="99075" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing passwords." /></overlay><overlay disa="192" owner="disastig" ownerid="OL07-00-010119" ruleid="accounts_password_pam_retry" severity="medium"><VMSinfo SVKey="108181" VKey="99077" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, pwquality must be used." /></overlay><overlay disa="192" owner="disastig" ownerid="OL07-00-010120" ruleid="accounts_password_pam_ucredit" severity="medium"><VMSinfo SVKey="108183" VKey="99079" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one upper-case character." /></overlay><overlay disa="193" owner="disastig" ownerid="OL07-00-010130" ruleid="accounts_password_pam_lcredit" severity="medium"><VMSinfo SVKey="108185" VKey="99081" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one lower-case character." /></overlay><overlay disa="194" owner="disastig" ownerid="OL07-00-010140" ruleid="accounts_password_pam_dcredit" severity="medium"><VMSinfo SVKey="108187" VKey="99083" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are assigned, the new password must contain at least one numeric character." /></overlay><overlay disa="1619" owner="disastig" ownerid="OL07-00-010150" ruleid="accounts_password_pam_ocredit" severity="medium"><VMSinfo SVKey="108189" VKey="99085" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one special character." /></overlay><overlay disa="195" owner="disastig" ownerid="OL07-00-010160" ruleid="accounts_password_pam_difok" severity="medium"><VMSinfo SVKey="108191" VKey="99087" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed a minimum of eight of the total number of characters must be changed." /></overlay><overlay disa="195" owner="disastig" ownerid="OL07-00-010170" ruleid="accounts_password_pam_minclass" severity="medium"><VMSinfo SVKey="108193" VKey="99089" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed a minimum of four character classes must be changed." /></overlay><overlay disa="195" owner="disastig" ownerid="OL07-00-010180" ruleid="accounts_password_pam_maxrepeat" severity="medium"><VMSinfo SVKey="108195" VKey="99091" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating consecutive characters must not be more than three characters." /></overlay><overlay disa="195" owner="disastig" ownerid="OL07-00-010190" ruleid="accounts_password_pam_maxclassrepeat" severity="medium"><VMSinfo SVKey="108197" VKey="99093" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating characters of the same character class must not be more than four characters." /></overlay><overlay disa="196" owner="disastig" ownerid="OL07-00-010200" ruleid="set_password_hashing_algorithm_systemauth" severity="medium"><VMSinfo SVKey="108199" VKey="99095" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the PAM system service is configured to store only encrypted representations of passwords." /></overlay><overlay disa="196" owner="disastig" ownerid="OL07-00-010210" ruleid="set_password_hashing_algorithm_logindefs" severity="medium"><VMSinfo SVKey="108201" VKey="99097" VRelease="r1" /><title text="The Oracle Linux operating system must be configured to use the shadow file to store only encrypted representations of passwords." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010219" ruleid="partition_for_var_log_audit" severity="low"><VMSinfo SVKey="108735" VKey="99631" VRelease="r1" /><title text="The Oracle Linux operating system must be integrated into a directory service infrastructure." /></overlay><overlay disa="196" owner="disastig" ownerid="OL07-00-010220" ruleid="set_password_hashing_algorithm_libuserconf" severity="medium"><VMSinfo SVKey="108203" VKey="99099" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords." /></overlay><overlay disa="198" owner="disastig" ownerid="OL07-00-010230" ruleid="accounts_minimum_age_login_defs" severity="medium"><VMSinfo SVKey="108205" VKey="99101" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 24 hours/1 day minimum lifetime." /></overlay><overlay disa="198" owner="disastig" ownerid="OL07-00-010240" ruleid="accounts_password_set_min_life_existing" severity="medium"><VMSinfo SVKey="108207" VKey="99103" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that passwords are restricted to a 24 hours/1 day minimum lifetime." /></overlay><overlay disa="199" owner="disastig" ownerid="OL07-00-010250" ruleid="accounts_maximum_age_login_defs" severity="medium"><VMSinfo SVKey="108209" VKey="99105" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 60-day maximum lifetime." /></overlay><overlay disa="199" owner="disastig" ownerid="OL07-00-010260" ruleid="accounts_password_set_max_life_existing" severity="medium"><VMSinfo SVKey="108211" VKey="99107" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that existing passwords are restricted to a 60-day maximum lifetime." /></overlay><overlay disa="200" owner="disastig" ownerid="OL07-00-010270" ruleid="accounts_password_pam_unix_remember" severity="medium"><VMSinfo SVKey="108213" VKey="99109" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that passwords are prohibited from reuse for a minimum of five generations." /></overlay><overlay disa="205" owner="disastig" ownerid="OL07-00-010280" ruleid="accounts_password_pam_minlen" severity="medium"><VMSinfo SVKey="108215" VKey="99111" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that passwords are a minimum of 15 characters in length." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010290" ruleid="no_empty_passwords" severity="high"><VMSinfo SVKey="108217" VKey="99113" VRelease="r1" /><title text="The Oracle Linux operating system must not have accounts configured with blank or null passwords." /></overlay><overlay disa="766" owner="disastig" ownerid="OL07-00-010300" ruleid="sshd_disable_empty_passwords" severity="high"><VMSinfo SVKey="108219" VKey="99115" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password." /></overlay><overlay disa="795" owner="disastig" ownerid="OL07-00-010310" ruleid="account_disable_post_pw_expiration" severity="medium"><VMSinfo SVKey="108221" VKey="99117" VRelease="r1" /><title text="The Oracle Linux operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires." /></overlay><overlay disa="2238" owner="disastig" ownerid="OL07-00-010320" ruleid="accounts_passwords_pam_faillock_deny" severity="medium"><VMSinfo SVKey="108223" VKey="99119" VRelease="r1" /><title text="Accounts on the Oracle Linux operating system subjected to three unsuccessful logon attempts within 15 minutes must be locked for the maximum configurable period." /></overlay><overlay disa="2238" owner="disastig" ownerid="OL07-00-010330" ruleid="accounts_passwords_pam_faillock_deny_root" severity="medium"><VMSinfo SVKey="108225" VKey="99121" VRelease="r1" /><title text="The Oracle Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period." /></overlay><overlay disa="2038" owner="disastig" ownerid="OL07-00-010340" ruleid="sudo_remove_nopasswd" severity="medium"><VMSinfo SVKey="108227" VKey="99123" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that users must provide a password for privilege escalation." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010430" ruleid="accounts_logon_fail_delay" severity="medium"><VMSinfo SVKey="108229" VKey="99125" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the delay between logon prompts following a failed console logon attempt is at least four seconds." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010440" ruleid="gnome_gdm_disable_automatic_login" severity="high"><VMSinfo SVKey="108231" VKey="99127" VRelease="r1" /><title text="The Oracle Linux operating system must not allow an unattended or automatic logon to the system via a graphical user interface." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010450" ruleid="gnome_gdm_disable_guest_login" severity="high"><VMSinfo SVKey="108233" VKey="99129" VRelease="r1" /><title text="The Oracle Linux operating system must not allow an unrestricted logon to the system." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010460" ruleid="sshd_do_not_permit_user_env" severity="medium"><VMSinfo SVKey="108235" VKey="99131" VRelease="r1" /><title text="The Oracle Linux operating system must not allow users to override SSH environment variables." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-010470" ruleid="disable_host_auth" severity="medium"><VMSinfo SVKey="108237" VKey="99133" VRelease="r1" /><title text="The Oracle Linux operating system must not allow a non-certificate trusted host SSH logon to the system." /></overlay><overlay disa="213" owner="disastig" ownerid="OL07-00-010480" ruleid="grub2_password" severity="high"><VMSinfo SVKey="108239" VKey="99135" VRelease="r1" /><title text="Oracle Linux operating systems prior to version 7.2 with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes." /></overlay><overlay disa="213" owner="disastig" ownerid="OL07-00-010481" ruleid="require_singleuser_auth" severity="medium"><VMSinfo SVKey="108241" VKey="99137" VRelease="r1" /><title text="The Oracle Linux operating system must require authentication upon booting into single-user and maintenance modes." /></overlay><overlay disa="213" owner="disastig" ownerid="OL07-00-010482" ruleid="XXXX" severity="high"><VMSinfo SVKey="108243" VKey="99139" VRelease="r1" /><title text="Oracle Linux operating systems version 7.2 or newer with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes." /></overlay><overlay disa="213" owner="disastig" ownerid="OL07-00-010490" ruleid="grub2_uefi_password" severity="high"><VMSinfo SVKey="108245" VKey="99141" VRelease="r1" /><title text="Oracle Linux operating systems prior to version 7.2 using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes." /></overlay><overlay disa="213" owner="disastig" ownerid="OL07-00-010491" ruleid="XXXX" severity="high"><VMSinfo SVKey="108247" VKey="99143" VRelease="r1" /><title text="Oracle Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes." /></overlay><overlay disa="770" owner="disastig" ownerid="OL07-00-010500" ruleid="smartcard_auth" severity="medium"><VMSinfo SVKey="108249" VKey="99145" VRelease="r1" /><title text="The Oracle Linux operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multifactor authentication." /></overlay><overlay disa="381" owner="disastig" ownerid="OL07-00-020000" ruleid="package_rsh-server_removed" severity="high"><VMSinfo SVKey="108251" VKey="99147" VRelease="r1" /><title text="The Oracle Linux operating system must not have the rsh-server package installed." /></overlay><overlay disa="381" owner="disastig" ownerid="OL07-00-020010" ruleid="package_ypserv_removed" severity="high"><VMSinfo SVKey="108253" VKey="99149" VRelease="r1" /><title text="The Oracle Linux operating system must not have the ypserv package installed." /></overlay><overlay disa="1233" owner="disastig" ownerid="OL07-00-020019" ruleid="XXXX" severity="medium"><VMSinfo SVKey="108255" VKey="99151" VRelease="r1" /><title text="The Oracle Linux operating system must have a host-based intrusion detection tool installed." /></overlay><overlay disa="2235" owner="disastig" ownerid="OL07-00-020020" ruleid="selinux_user_login_roles" severity="medium"><VMSinfo SVKey="108257" VKey="99153" VRelease="r1" /><title text="The Oracle Linux operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures." /></overlay><overlay disa="2699" owner="disastig" ownerid="OL07-00-020030" ruleid="aide_periodic_cron_checking" severity="medium"><VMSinfo SVKey="108259" VKey="99155" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that a file integrity tool verifies the baseline operating system configuration at least weekly." /></overlay><overlay disa="1744" owner="disastig" ownerid="OL07-00-020040" ruleid="aide_scan_notification" severity="low"><VMSinfo SVKey="108261" VKey="99157" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that designated personnel are notified if baseline configurations are changed in an unauthorized manner." /></overlay><overlay disa="1749" owner="disastig" ownerid="OL07-00-020050" ruleid="ensure_gpgcheck_globally_activated" severity="high"><VMSinfo SVKey="108263" VKey="99159" VRelease="r1" /><title text="The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization." /></overlay><overlay disa="1749" owner="disastig" ownerid="OL07-00-020060" ruleid="ensure_gpgcheck_local_packages" severity="high"><VMSinfo SVKey="108265" VKey="99161" VRelease="r1" /><title text="The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization." /></overlay><overlay disa="778" owner="disastig" ownerid="OL07-00-020100" ruleid="kernel_module_usb-storage_disabled" severity="medium"><VMSinfo SVKey="108267" VKey="99163" VRelease="r1" /><title text="The Oracle Linux operating system must be configured to disable USB mass storage." /></overlay><overlay disa="1958" owner="disastig" ownerid="OL07-00-020101" ruleid="kernel_module_dccp_disabled" severity="medium"><VMSinfo SVKey="108269" VKey="99165" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the Datagram Congestion Control Protocol (DCCP) kernel module is disabled unless required." /></overlay><overlay disa="778" owner="disastig" ownerid="OL07-00-020110" ruleid="service_autofs_disabled" severity="medium"><VMSinfo SVKey="108271" VKey="99167" VRelease="r1" /><title text="The Oracle Linux operating system must disable the file system automounter unless required." /></overlay><overlay disa="2617" owner="disastig" ownerid="OL07-00-020200" ruleid="clean_components_post_updating" severity="low"><VMSinfo SVKey="108273" VKey="99169" VRelease="r1" /><title text="The Oracle Linux operating system must remove all software components after updated versions have been installed." /></overlay><overlay disa="2696" owner="disastig" ownerid="OL07-00-020210" ruleid="selinux_state" severity="high"><VMSinfo SVKey="108643" VKey="99539" VRelease="r1" /><title text="The Oracle Linux operating system must enable SELinux." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020230" ruleid="disable_ctrlaltdel_reboot" severity="high"><VMSinfo SVKey="108275" VKey="99171" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the x86 Ctrl-Alt-Delete key sequence is disabled." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020240" ruleid="accounts_umask_etc_login_defs" severity="medium"><VMSinfo SVKey="108277" VKey="99173" VRelease="r1" /><title text="The Oracle Linux operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020250" ruleid="installed_OS_is_vendor_supported" severity="high"><VMSinfo SVKey="108279" VKey="99175" VRelease="r1" /><title text="The Oracle Linux operating system must be a vendor supported release." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020260" ruleid="security_patches_up_to_date" severity="medium"><VMSinfo SVKey="108281" VKey="99177" VRelease="r1" /><title text="The Oracle Linux operating system security patches and updates must be installed and up to date." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020270" ruleid="partition_for_var_log_audit" severity="medium"><VMSinfo SVKey="108283" VKey="99179" VRelease="r1" /><title text="The Oracle Linux operating system must not have unnecessary accounts." /></overlay><overlay disa="764" owner="disastig" ownerid="OL07-00-020300" ruleid="gid_passwd_group_same" severity="low"><VMSinfo SVKey="108285" VKey="99181" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all Group Identifiers (GIDs) referenced in the /etc/passwd file are defined in the /etc/group file." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020310" ruleid="accounts_no_uid_except_zero" severity="high"><VMSinfo SVKey="108289" VKey="99185" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the root account must be the only account having unrestricted access to the system." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020320" ruleid="no_files_unowned_by_user" severity="medium"><VMSinfo SVKey="108291" VKey="99187" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all files and directories have a valid owner." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020330" ruleid="file_permissions_ungroupowned" severity="medium"><VMSinfo SVKey="108293" VKey="99189" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all files and directories have a valid group owner." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020600" ruleid="accounts_user_interactive_home_directory_defined" severity="medium"><VMSinfo SVKey="108295" VKey="99191" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive users have a home directory assigned in the /etc/passwd file." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020610" ruleid="accounts_have_homedir_login_defs" severity="medium"><VMSinfo SVKey="108297" VKey="99193" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user accounts, upon creation, are assigned a home directory." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020620" ruleid="accounts_user_interactive_home_directory_exists" severity="medium"><VMSinfo SVKey="108299" VKey="99195" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user home directories are defined in the /etc/passwd file." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020630" ruleid="file_permissions_home_directories" severity="medium"><VMSinfo SVKey="108301" VKey="99197" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user home directories have mode 0750 or less permissive." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020640" ruleid="file_ownership_home_directories" severity="medium"><VMSinfo SVKey="108303" VKey="99199" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user home directories are owned by their respective users." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020650" ruleid="file_groupownership_home_directories" severity="medium"><VMSinfo SVKey="108305" VKey="99201" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user home directories are group-owned by the home directory owners primary group." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020660" ruleid="accounts_users_home_files_ownership" severity="medium"><VMSinfo SVKey="108307" VKey="99203" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are owned by the owner of the home directory." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020670" ruleid="accounts_users_home_files_groupownership" severity="medium"><VMSinfo SVKey="108309" VKey="99205" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020680" ruleid="accounts_users_home_files_permissions" severity="medium"><VMSinfo SVKey="108311" VKey="99207" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories have a mode of 0750 or less permissive." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020690" ruleid="accounts_user_dot_user_ownership" severity="medium"><VMSinfo SVKey="108313" VKey="99209" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local initialization files for interactive users are owned by the home directory user or root." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020700" ruleid="accounts_user_dot_group_ownership" severity="medium"><VMSinfo SVKey="108315" VKey="99211" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local initialization files for local interactive users are be group-owned by the users primary group or root." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020710" ruleid="file_permission_user_init_files" severity="medium"><VMSinfo SVKey="108317" VKey="99213" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local initialization files have mode 0740 or less permissive." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020720" ruleid="accounts_user_home_paths_only" severity="medium"><VMSinfo SVKey="108319" VKey="99215" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020730" ruleid="accounts_user_dot_no_world_writable_programs" severity="medium"><VMSinfo SVKey="108321" VKey="99217" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that local initialization files do not execute world-writable programs." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-020900" ruleid="selinux_all_devicefiles_labeled" severity="medium"><VMSinfo SVKey="108323" VKey="99219" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all system device files are correctly labeled to prevent unauthorized modification." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021000" ruleid="mount_option_home_nosuid" severity="medium"><VMSinfo SVKey="108325" VKey="99221" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that file systems containing user home directories are mounted to prevent files with the setuid and setgid bit set from being executed." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021010" ruleid="mount_option_nosuid_removable_partitions" severity="medium"><VMSinfo SVKey="108327" VKey="99223" VRelease="r1" /><title text="The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021020" ruleid="mount_option_nosuid_remote_filesystems" severity="medium"><VMSinfo SVKey="108329" VKey="99225" VRelease="r1" /><title text="The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are being imported via Network File System (NFS)." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021021" ruleid="mount_option_noexec_remote_filesystems" severity="medium"><VMSinfo SVKey="108331" VKey="99227" VRelease="r1" /><title text="The Oracle Linux operating system must prevent binary files from being executed on file systems that are being imported via Network File System (NFS)." /></overlay><overlay disa="1764" owner="disastig" ownerid="OL07-00-021022" ruleid="mount_option_dev_shm_nodev" severity="low"><VMSinfo SVKey="108333" VKey="99229" VRelease="r1" /><title text="The Oracle Linux operating system must mount /dev/shm with the nodev option." /></overlay><overlay disa="1764" owner="disastig" ownerid="OL07-00-021023" ruleid="mount_option_dev_shm_nosuid" severity="low"><VMSinfo SVKey="108335" VKey="99231" VRelease="r1" /><title text="The Oracle Linux operating system must mount /dev/shm with the nosuid option." /></overlay><overlay disa="1764" owner="disastig" ownerid="OL07-00-021024" ruleid="mount_option_dev_shm_noexec" severity="low"><VMSinfo SVKey="108337" VKey="99233" VRelease="r1" /><title text="The Oracle Linux operating system must mount /dev/shm with the noexec option." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021030" ruleid="dir_perms_world_writable_system_owned" severity="medium"><VMSinfo SVKey="108339" VKey="99235" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all world-writable directories are group-owned by root, sys, bin, or an application group." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021040" ruleid="accounts_umask_interactive_users" severity="medium"><VMSinfo SVKey="108341" VKey="99237" VRelease="r1" /><title text="The Oracle Linux operating system must set the umask value to 077 for all local interactive user accounts." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021100" ruleid="rsyslog_cron_logging" severity="medium"><VMSinfo SVKey="108343" VKey="99239" VRelease="r1" /><title text="The Oracle Linux operating system must have cron logging implemented." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021110" ruleid="file_owner_cron_allow" severity="medium"><VMSinfo SVKey="108345" VKey="99241" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is owned by root." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021120" ruleid="file_groupowner_cron_allow" severity="medium"><VMSinfo SVKey="108347" VKey="99243" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is group-owned by root." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021300" ruleid="service_kdump_disabled" severity="medium"><VMSinfo SVKey="108349" VKey="99245" VRelease="r1" /><title text="The Oracle Linux operating system must disable Kernel core dumps unless needed." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021310" ruleid="partition_for_home" severity="low"><VMSinfo SVKey="108351" VKey="99247" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that a separate file system is used for user home directories (such as /home or an equivalent)." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021320" ruleid="partition_for_var" severity="low"><VMSinfo SVKey="108353" VKey="99249" VRelease="r1" /><title text="The Oracle Linux operating system must use a separate file system for /var." /></overlay><overlay disa="1849" owner="disastig" ownerid="OL07-00-021330" ruleid="partition_for_var_log_audit" severity="low"><VMSinfo SVKey="108355" VKey="99251" VRelease="r1" /><title text="The Oracle Linux operating system must use a separate file system for the system audit data path large enough to hold at least one week of audit data." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021340" ruleid="partition_for_tmp" severity="low"><VMSinfo SVKey="108357" VKey="99253" VRelease="r1" /><title text="The Oracle Linux operating system must use a separate file system for /tmp (or equivalent)." /></overlay><overlay disa="2476" owner="disastig" ownerid="OL07-00-021350" ruleid="grub2_enable_fips_mode" severity="high"><VMSinfo SVKey="108359" VKey="99255" VRelease="r1" /><title text="The Oracle Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021600" ruleid="aide_verify_acls" severity="low"><VMSinfo SVKey="108361" VKey="99257" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify Access Control Lists (ACLs)." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021610" ruleid="aide_verify_ext_attributes" severity="low"><VMSinfo SVKey="108363" VKey="99259" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify extended attributes." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-021620" ruleid="aide_use_fips_hashes" severity="medium"><VMSinfo SVKey="108365" VKey="99261" VRelease="r1" /><title text="The Oracle Linux operating system must use a file integrity tool that is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories." /></overlay><overlay disa="1813" owner="disastig" ownerid="OL07-00-021700" ruleid="grub2_no_removeable_media" severity="medium"><VMSinfo SVKey="108367" VKey="99263" VRelease="r1" /><title text="The Oracle Linux operating system must not allow removable media to be used as the boot loader unless approved." /></overlay><overlay disa="381" owner="disastig" ownerid="OL07-00-021710" ruleid="package_telnet-server_removed" severity="high"><VMSinfo SVKey="108369" VKey="99265" VRelease="r1" /><title text="The Oracle Linux operating system must not have the telnet-server package installed." /></overlay><overlay disa="1814" owner="disastig" ownerid="OL07-00-030000" ruleid="service_auditd_enabled" severity="high"><VMSinfo SVKey="108371" VKey="99267" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that auditing is configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users." /></overlay><overlay disa="140" owner="disastig" ownerid="OL07-00-030010" ruleid="audit_rules_system_shutdown" severity="medium"><VMSinfo SVKey="108373" VKey="99269" VRelease="r1" /><title text="The Oracle Linux operating system must shut down upon audit processing failure unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) in the event of an audit processing failure." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030200" ruleid="auditd_name_format" severity="medium"><VMSinfo SVKey="108375" VKey="99271" VRelease="r1" /><title text="The Oracle Linux operating system must be configured to use the au-remote plugin." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030201" ruleid="auditd_name_format" severity="medium"><VMSinfo SVKey="108377" VKey="99273" VRelease="r1" /><title text="The Oracle Linux operating system must configure the au-remote plugin to off-load audit logs using the audisp-remote daemon." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030210" ruleid="auditd_name_format" severity="medium"><VMSinfo SVKey="108379" VKey="99275" VRelease="r1" /><title text="The Oracle Linux operating system must take appropriate action when the audisp-remote buffer is full." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030211" ruleid="auditd_name_format" severity="medium"><VMSinfo SVKey="108381" VKey="99277" VRelease="r1" /><title text="The Oracle Linux operating system must label all off-loaded audit logs before sending them to the central log server." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030300" ruleid="auditd_audispd_configure_remote_server" severity="medium"><VMSinfo SVKey="108383" VKey="99279" VRelease="r1" /><title text="The Oracle Linux operating system must off-load audit records onto a different system or media from the system being audited." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030310" ruleid="auditd_audispd_encrypt_sent_records" severity="medium"><VMSinfo SVKey="108385" VKey="99281" VRelease="r1" /><title text="The Oracle Linux operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030320" ruleid="auditd_audispd_disk_full_action" severity="medium"><VMSinfo SVKey="108387" VKey="99283" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the audit system takes appropriate action when the audit storage volume is full." /></overlay><overlay disa="1851" owner="disastig" ownerid="OL07-00-030321" ruleid="auditd_audispd_network_failure_action" severity="medium"><VMSinfo SVKey="108389" VKey="99285" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the audit system takes appropriate action when there is an error sending audit records to a remote system." /></overlay><overlay disa="1855" owner="disastig" ownerid="OL07-00-030330" ruleid="auditd_data_retention_space_left" severity="medium"><VMSinfo SVKey="108391" VKey="99287" VRelease="r1" /><title text="The Oracle Linux operating system must initiate an action to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity." /></overlay><overlay disa="1855" owner="disastig" ownerid="OL07-00-030340" ruleid="auditd_data_retention_space_left_action" severity="medium"><VMSinfo SVKey="108393" VKey="99289" VRelease="r1" /><title text="The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached." /></overlay><overlay disa="1855" owner="disastig" ownerid="OL07-00-030350" ruleid="auditd_data_retention_action_mail_acct" severity="medium"><VMSinfo SVKey="108395" VKey="99291" VRelease="r1" /><title text="The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached." /></overlay><overlay disa="2234" owner="disastig" ownerid="OL07-00-030360" ruleid="audit_rules_privileged_commands" severity="medium"><VMSinfo SVKey="108397" VKey="99293" VRelease="r1" /><title text="The Oracle Linux operating system must audit all executions of privileged functions." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030370" ruleid="audit_rules_dac_modification_chown" severity="medium"><VMSinfo SVKey="108399" VKey="99295" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the chown syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030380" ruleid="audit_rules_dac_modification_fchown" severity="medium"><VMSinfo SVKey="108401" VKey="99297" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fchown syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030390" ruleid="audit_rules_dac_modification_lchown" severity="medium"><VMSinfo SVKey="108403" VKey="99299" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the lchown syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030400" ruleid="audit_rules_dac_modification_fchownat" severity="medium"><VMSinfo SVKey="108405" VKey="99301" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fchownat syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030410" ruleid="audit_rules_dac_modification_chmod" severity="medium"><VMSinfo SVKey="108407" VKey="99303" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the chmod syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030420" ruleid="audit_rules_dac_modification_fchmod" severity="medium"><VMSinfo SVKey="108409" VKey="99305" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fchmod syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030430" ruleid="audit_rules_dac_modification_fchmodat" severity="medium"><VMSinfo SVKey="108411" VKey="99307" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fchmodat syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030440" ruleid="audit_rules_dac_modification_setxattr" severity="medium"><VMSinfo SVKey="108413" VKey="99309" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the setxattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030450" ruleid="audit_rules_dac_modification_fsetxattr" severity="medium"><VMSinfo SVKey="108415" VKey="99311" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fsetxattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030460" ruleid="audit_rules_dac_modification_lsetxattr" severity="medium"><VMSinfo SVKey="108417" VKey="99313" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the lsetxattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030470" ruleid="audit_rules_dac_modification_removexattr" severity="medium"><VMSinfo SVKey="108419" VKey="99315" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the removexattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030480" ruleid="audit_rules_dac_modification_fremovexattr" severity="medium"><VMSinfo SVKey="108421" VKey="99317" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the fremovexattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030490" ruleid="audit_rules_dac_modification_lremovexattr" severity="medium"><VMSinfo SVKey="108423" VKey="99319" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the lremovexattr syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030500" ruleid="audit_rules_unsuccessful_file_modification_creat" severity="medium"><VMSinfo SVKey="108425" VKey="99321" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the creat syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030510" ruleid="audit_rules_unsuccessful_file_modification_open" severity="medium"><VMSinfo SVKey="108427" VKey="99323" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the open syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030520" ruleid="audit_rules_unsuccessful_file_modification_openat" severity="medium"><VMSinfo SVKey="108429" VKey="99325" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the openat syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030530" ruleid="audit_rules_unsuccessful_file_modification_open_by_handle_at" severity="medium"><VMSinfo SVKey="108431" VKey="99327" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the open_by_handle_at syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030540" ruleid="audit_rules_unsuccessful_file_modification_truncate" severity="medium"><VMSinfo SVKey="108433" VKey="99329" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the truncate syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030550" ruleid="audit_rules_unsuccessful_file_modification_ftruncate" severity="medium"><VMSinfo SVKey="108435" VKey="99331" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the ftruncate syscall." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030560" ruleid="audit_rules_execution_semanage" severity="medium"><VMSinfo SVKey="108437" VKey="99333" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the semanage command." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030570" ruleid="audit_rules_execution_setsebool" severity="medium"><VMSinfo SVKey="108439" VKey="99335" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the setsebool command." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030580" ruleid="audit_rules_execution_chcon" severity="medium"><VMSinfo SVKey="108441" VKey="99337" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the chcon command." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030590" ruleid="audit_rules_execution_setfiles" severity="medium"><VMSinfo SVKey="108443" VKey="99339" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the setfiles command." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030610" ruleid="audit_rules_login_events_faillock" severity="medium"><VMSinfo SVKey="108445" VKey="99341" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all unsuccessful account access events." /></overlay><overlay disa="2884" owner="disastig" ownerid="OL07-00-030620" ruleid="audit_rules_login_events_lastlog" severity="medium"><VMSinfo SVKey="108447" VKey="99343" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all successful account access events." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030630" ruleid="audit_rules_privileged_commands_passwd" severity="medium"><VMSinfo SVKey="108449" VKey="99345" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the passwd command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030640" ruleid="audit_rules_privileged_commands_unix_chkpwd" severity="medium"><VMSinfo SVKey="108451" VKey="99347" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the unix_chkpwd command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030650" ruleid="audit_rules_privileged_commands_gpasswd" severity="medium"><VMSinfo SVKey="108453" VKey="99349" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the gpasswd command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030660" ruleid="audit_rules_privileged_commands_chage" severity="medium"><VMSinfo SVKey="108455" VKey="99351" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the chage command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030670" ruleid="audit_rules_privileged_commands_userhelper" severity="medium"><VMSinfo SVKey="108457" VKey="99353" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the userhelper command." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030680" ruleid="audit_rules_privileged_commands_su" severity="medium"><VMSinfo SVKey="108459" VKey="99355" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the su command." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030690" ruleid="audit_rules_privileged_commands_sudo" severity="medium"><VMSinfo SVKey="108461" VKey="99357" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the sudo command." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030700" ruleid="audit_rules_sysadmin_actions" severity="medium"><VMSinfo SVKey="108463" VKey="99359" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030710" ruleid="audit_rules_privileged_commands_newgrp" severity="medium"><VMSinfo SVKey="108465" VKey="99361" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the newgrp command." /></overlay><overlay disa="130" owner="disastig" ownerid="OL07-00-030720" ruleid="audit_rules_privileged_commands_chsh" severity="medium"><VMSinfo SVKey="108467" VKey="99363" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the chsh command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030740" ruleid="audit_rules_media_export" severity="medium"><VMSinfo SVKey="108469" VKey="99365" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the mount command and syscall." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030750" ruleid="audit_rules_privileged_commands_umount" severity="medium"><VMSinfo SVKey="108471" VKey="99367" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the umount command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030760" ruleid="audit_rules_privileged_commands_postdrop" severity="medium"><VMSinfo SVKey="108473" VKey="99369" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the postdrop command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030770" ruleid="audit_rules_privileged_commands_postqueue" severity="medium"><VMSinfo SVKey="108475" VKey="99371" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the postqueue command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030780" ruleid="audit_rules_privileged_commands_ssh_keysign" severity="medium"><VMSinfo SVKey="108477" VKey="99373" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the ssh-keysign command." /></overlay><overlay disa="135" owner="disastig" ownerid="OL07-00-030800" ruleid="audit_rules_privileged_commands_crontab" severity="medium"><VMSinfo SVKey="108479" VKey="99375" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the crontab command." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030810" ruleid="audit_rules_privileged_commands_pam_timestamp_check" severity="medium"><VMSinfo SVKey="108481" VKey="99377" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the pam_timestamp_check command." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030819" ruleid="audit_rules_kernel_module_loading_init" severity="medium"><VMSinfo SVKey="108483" VKey="99379" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the create_module syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030820" ruleid="audit_rules_kernel_module_loading_init" severity="medium"><VMSinfo SVKey="108485" VKey="99381" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the init_module syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030821" ruleid="audit_rules_kernel_module_loading_finit" severity="medium"><VMSinfo SVKey="108487" VKey="99383" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the finit_module syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030830" ruleid="audit_rules_kernel_module_loading_delete" severity="medium"><VMSinfo SVKey="108489" VKey="99385" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the delete_module syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030840" ruleid="audit_rules_kernel_module_loading_init" severity="medium"><VMSinfo SVKey="108491" VKey="99387" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the kmod command." /></overlay><overlay disa="2130" owner="disastig" ownerid="OL07-00-030870" ruleid="audit_rules_usergroup_modification_passwd" severity="medium"><VMSinfo SVKey="108493" VKey="99389" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd." /></overlay><overlay disa="18" owner="disastig" ownerid="OL07-00-030871" ruleid="audit_rules_usergroup_modification_group" severity="medium"><VMSinfo SVKey="108495" VKey="99391" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group." /></overlay><overlay disa="18" owner="disastig" ownerid="OL07-00-030872" ruleid="audit_rules_usergroup_modification_gshadow" severity="medium"><VMSinfo SVKey="108497" VKey="99393" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow." /></overlay><overlay disa="18" owner="disastig" ownerid="OL07-00-030873" ruleid="audit_rules_usergroup_modification_shadow" severity="medium"><VMSinfo SVKey="108499" VKey="99395" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow." /></overlay><overlay disa="18" owner="disastig" ownerid="OL07-00-030874" ruleid="audit_rules_usergroup_modification_opasswd" severity="medium"><VMSinfo SVKey="108501" VKey="99397" VRelease="r1" /><title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030880" ruleid="audit_rules_file_deletion_events_rename" severity="medium"><VMSinfo SVKey="108503" VKey="99399" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the rename syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030890" ruleid="audit_rules_file_deletion_events_renameat" severity="medium"><VMSinfo SVKey="108505" VKey="99401" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the renameat syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030900" ruleid="audit_rules_file_deletion_events_rmdir" severity="medium"><VMSinfo SVKey="108507" VKey="99403" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the rmdir syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030910" ruleid="audit_rules_file_deletion_events_unlink" severity="medium"><VMSinfo SVKey="108509" VKey="99405" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the unlink syscall." /></overlay><overlay disa="172" owner="disastig" ownerid="OL07-00-030920" ruleid="audit_rules_file_deletion_events_unlinkat" severity="medium"><VMSinfo SVKey="108511" VKey="99407" VRelease="r1" /><title text="The Oracle Linux operating system must audit all uses of the unlinkat syscall." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-031000" ruleid="rsyslog_remote_loghost" severity="medium"><VMSinfo SVKey="108513" VKey="99409" VRelease="r1" /><title text="The Oracle Linux operating system must send rsyslog output to a log aggregation server." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-031010" ruleid="rsyslog_nolisten" severity="medium"><VMSinfo SVKey="108515" VKey="99411" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-032000" ruleid="install_mcafee_antivirus" severity="high"><VMSinfo SVKey="108517" VKey="99413" VRelease="r1" /><title text="The Oracle Linux operating system must use a virus scan program." /></overlay><overlay disa="54" owner="disastig" ownerid="OL07-00-040000" ruleid="accounts_max_concurrent_login_sessions" severity="low"><VMSinfo SVKey="108519" VKey="99415" VRelease="r1" /><title text="The Oracle Linux operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types." /></overlay><overlay disa="2314" owner="disastig" ownerid="OL07-00-040100" ruleid="configure_firewalld_ports" severity="medium"><VMSinfo SVKey="108521" VKey="99417" VRelease="r1" /><title text="The Oracle Linux operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments." /></overlay><overlay disa="3123" owner="disastig" ownerid="OL07-00-040110" ruleid="sshd_use_approved_ciphers" severity="medium"><VMSinfo SVKey="108523" VKey="99419" VRelease="r1" /><title text="The Oracle Linux operating system must use a FIPS 140-2 approved cryptographic algorithm for SSH communications." /></overlay><overlay disa="1133" owner="disastig" ownerid="OL07-00-040160" ruleid="accounts_tmout" severity="medium"><VMSinfo SVKey="108525" VKey="99421" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all network connections associated with a communication session are terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements." /></overlay><overlay disa="48" owner="disastig" ownerid="OL07-00-040170" ruleid="sshd_enable_warning_banner" severity="medium"><VMSinfo SVKey="108527" VKey="99423" VRelease="r1" /><title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner immediately prior to, or as part of, remote access logon prompts." /></overlay><overlay disa="1453" owner="disastig" ownerid="OL07-00-040180" ruleid="sssd_ldap_start_tls" severity="medium"><VMSinfo SVKey="108529" VKey="99425" VRelease="r1" /><title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications." /></overlay><overlay disa="1453" owner="disastig" ownerid="OL07-00-040190" ruleid="sssd_ldap_configure_tls_ca_dir" severity="medium"><VMSinfo SVKey="108531" VKey="99427" VRelease="r1" /><title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications." /></overlay><overlay disa="1453" owner="disastig" ownerid="OL07-00-040200" ruleid="sssd_ldap_configure_tls_ca" severity="medium"><VMSinfo SVKey="108533" VKey="99429" VRelease="r1" /><title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications." /></overlay><overlay disa="2824" owner="disastig" ownerid="OL07-00-040201" ruleid="sysctl_kernel_randomize_va_space" severity="medium"><VMSinfo SVKey="108535" VKey="99431" VRelease="r1" /><title text="The Oracle Linux operating system must implement virtual address space randomization." /></overlay><overlay disa="2422" owner="disastig" ownerid="OL07-00-040300" ruleid="package_openssh-server_installed" severity="medium"><VMSinfo SVKey="108537" VKey="99433" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all networked systems have SSH installed." /></overlay><overlay disa="2418" owner="disastig" ownerid="OL07-00-040310" ruleid="service_sshd_enabled" severity="medium"><VMSinfo SVKey="108539" VKey="99435" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all networked systems use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission." /></overlay><overlay disa="2361" owner="disastig" ownerid="OL07-00-040320" ruleid="sshd_set_idle_timeout" severity="medium"><VMSinfo SVKey="108541" VKey="99437" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040330" ruleid="sshd_disable_rhosts_rsa" severity="medium"><VMSinfo SVKey="108543" VKey="99439" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using RSA rhosts authentication." /></overlay><overlay disa="1133" owner="disastig" ownerid="OL07-00-040340" ruleid="sshd_set_keepalive" severity="medium"><VMSinfo SVKey="108545" VKey="99441" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic terminate after a period of inactivity." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040350" ruleid="sshd_disable_rhosts" severity="medium"><VMSinfo SVKey="108547" VKey="99443" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using rhosts authentication." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040360" ruleid="sshd_print_last_log" severity="medium"><VMSinfo SVKey="108549" VKey="99445" VRelease="r1" /><title text="The Oracle Linux operating system must display the date and time of the last successful account logon upon an SSH logon." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040370" ruleid="sshd_disable_root_login" severity="medium"><VMSinfo SVKey="108551" VKey="99447" VRelease="r1" /><title text="The Oracle Linux operating system must not permit direct logons to the root account using remote access via SSH." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040380" ruleid="sshd_disable_user_known_hosts" severity="medium"><VMSinfo SVKey="108553" VKey="99449" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using known hosts authentication." /></overlay><overlay disa="197" owner="disastig" ownerid="OL07-00-040390" ruleid="sshd_allow_only_protocol2" severity="high"><VMSinfo SVKey="108555" VKey="99451" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use the SSHv2 protocol." /></overlay><overlay disa="1453" owner="disastig" ownerid="OL07-00-040400" ruleid="sshd_use_approved_macs" severity="medium"><VMSinfo SVKey="108557" VKey="99453" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040410" ruleid="file_permissions_sshd_pub_key" severity="medium"><VMSinfo SVKey="108559" VKey="99455" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH public host key files have mode 0644 or less permissive." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040420" ruleid="file_permissions_sshd_private_key" severity="medium"><VMSinfo SVKey="108561" VKey="99457" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH private host key files have mode 0640 or less permissive." /></overlay><overlay disa="1813" owner="disastig" ownerid="OL07-00-040430" ruleid="sshd_disable_gssapi_auth" severity="medium"><VMSinfo SVKey="108563" VKey="99459" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed." /></overlay><overlay disa="1813" owner="disastig" ownerid="OL07-00-040440" ruleid="sshd_disable_kerb_auth" severity="medium"><VMSinfo SVKey="108565" VKey="99461" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not permit Kerberos authentication unless needed." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040450" ruleid="sshd_enable_strictmodes" severity="medium"><VMSinfo SVKey="108567" VKey="99463" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon performs strict mode checking of home directory configuration files." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040460" ruleid="sshd_use_priv_separation" severity="medium"><VMSinfo SVKey="108569" VKey="99465" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon uses privilege separation." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040470" ruleid="sshd_disable_compression" severity="medium"><VMSinfo SVKey="108571" VKey="99467" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow compression or only allows compression after successful authentication." /></overlay><overlay disa="2468" owner="disastig" ownerid="OL07-00-040480" ruleid="XXXX" severity="medium"><VMSinfo SVKey="108573" VKey="99469" VRelease="r1" /><title text="The operating system must request and perform data origin authentication verification and data integrity verification on the name/address resolution responses the system receives from authoritative sources." /></overlay><overlay disa="2046" owner="disastig" ownerid="OL07-00-040500" ruleid="chronyd_or_ntpd_set_maxpoll" severity="medium"><VMSinfo SVKey="108575" VKey="99471" VRelease="r1" /><title text="The Oracle Linux operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS)." /></overlay><overlay disa="2385" owner="disastig" ownerid="OL07-00-040510" ruleid="sysctl_net_ipv4_tcp_invalid_ratelimit" severity="medium"><VMSinfo SVKey="108577" VKey="99473" VRelease="r1" /><title text="The Oracle Linux operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040520" ruleid="service_firewalld_enabled" severity="medium"><VMSinfo SVKey="108579" VKey="99475" VRelease="r1" /><title text="The Oracle Linux operating system must enable an application firewall, if available." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040530" ruleid="display_login_attempts" severity="low"><VMSinfo SVKey="108581" VKey="99477" VRelease="r1" /><title text="The Oracle Linux operating system must display the date and time of the last successful account logon upon logon." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040540" ruleid="no_user_host_based_files" severity="high"><VMSinfo SVKey="108583" VKey="99479" VRelease="r1" /><title text="The Oracle Linux operating system must not contain .shosts files." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040550" ruleid="no_host_based_files" severity="high"><VMSinfo SVKey="108585" VKey="99481" VRelease="r1" /><title text="The Oracle Linux operating system must not contain shosts.equiv files." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040600" ruleid="network_configure_name_resolution" severity="low"><VMSinfo SVKey="108587" VKey="99483" VRelease="r1" /><title text="At least two name servers must be configured for Oracle Linux operating systems using DNS resolution." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040610" ruleid="sysctl_net_ipv4_conf_all_accept_source_route" severity="medium"><VMSinfo SVKey="108589" VKey="99485" VRelease="r1" /><title text="The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040611" ruleid="sysctl_net_ipv4_conf_all_rp_filter" severity="medium"><VMSinfo SVKey="108591" VKey="99487" VRelease="r1" /><title text="The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible on all interfaces." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040612" ruleid="sysctl_net_ipv4_conf_default_rp_filter" severity="medium"><VMSinfo SVKey="108593" VKey="99489" VRelease="r1" /><title text="The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible by default." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040620" ruleid="sysctl_net_ipv4_conf_default_accept_source_route" severity="medium"><VMSinfo SVKey="108595" VKey="99491" VRelease="r1" /><title text="The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040630" ruleid="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" severity="medium"><VMSinfo SVKey="108597" VKey="99493" VRelease="r1" /><title text="The Oracle Linux operating system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040640" ruleid="sysctl_net_ipv4_conf_default_accept_redirects" severity="medium"><VMSinfo SVKey="108599" VKey="99495" VRelease="r1" /><title text="The Oracle Linux operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040641" ruleid="sysctl_net_ipv4_conf_all_accept_redirects" severity="medium"><VMSinfo SVKey="108601" VKey="99497" VRelease="r1" /><title text="The Oracle Linux operating system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040650" ruleid="sysctl_net_ipv4_conf_default_send_redirects" severity="medium"><VMSinfo SVKey="108603" VKey="99499" VRelease="r1" /><title text="The Oracle Linux operating system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040660" ruleid="sysctl_net_ipv4_conf_all_send_redirects" severity="medium"><VMSinfo SVKey="108605" VKey="99501" VRelease="r1" /><title text="The Oracle Linux operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040670" ruleid="network_sniffer_disabled" severity="medium"><VMSinfo SVKey="108607" VKey="99503" VRelease="r1" /><title text="Network interfaces configured on The Oracle Linux operating system must not be in promiscuous mode." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040680" ruleid="postfix_prevent_unrestricted_relay" severity="medium"><VMSinfo SVKey="108609" VKey="99505" VRelease="r1" /><title text="The Oracle Linux operating system must be configured to prevent unrestricted mail relaying." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040690" ruleid="package_vsftpd_removed" severity="high"><VMSinfo SVKey="108611" VKey="99507" VRelease="r1" /><title text="The Oracle Linux operating system must not have a File Transfer Protocol (FTP) server package installed unless needed." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040700" ruleid="package_tftp-server_removed" severity="high"><VMSinfo SVKey="108613" VKey="99509" VRelease="r1" /><title text="The Oracle Linux operating system must not have the Trivial File Transfer Protocol (TFTP) server package installed if not required for operational support." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040710" ruleid="sshd_enable_x11_forwarding" severity="high"><VMSinfo SVKey="108615" VKey="99511" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that remote X connections for interactive users are encrypted." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040720" ruleid="tftpd_uses_secure_mode" severity="medium"><VMSinfo SVKey="108617" VKey="99513" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon is configured to operate in secure mode." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040730" ruleid="package_xorg-x11-server-common_removed" severity="medium"><VMSinfo SVKey="108619" VKey="99515" VRelease="r1" /><title text="The Oracle Linux operating system must not have an X Windows display manager installed unless approved." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040740" ruleid="sysctl_net_ipv4_ip_forward" severity="medium"><VMSinfo SVKey="108621" VKey="99517" VRelease="r1" /><title text="The Oracle Linux operating system must not be performing packet forwarding unless the system is a router." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040750" ruleid="mount_option_krb_sec_remote_filesystems" severity="medium"><VMSinfo SVKey="108623" VKey="99519" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040800" ruleid="snmpd_not_default_password" severity="high"><VMSinfo SVKey="108625" VKey="99521" VRelease="r1" /><title text="SNMP community strings on the Oracle Linux operating system must be changed from the default." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040810" ruleid="set_firewalld_default_zone" severity="medium"><VMSinfo SVKey="108627" VKey="99523" VRelease="r1" /><title text="The Oracle Linux operating system access control program must be configured to grant or deny system access to specific hosts and services." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040820" ruleid="libreswan_approved_tunnels" severity="medium"><VMSinfo SVKey="108629" VKey="99525" VRelease="r1" /><title text="The Oracle Linux operating system must not have unauthorized IP tunnels configured." /></overlay><overlay disa="366" owner="disastig" ownerid="OL07-00-040830" ruleid="sysctl_net_ipv6_conf_all_accept_source_route" severity="medium"><VMSinfo SVKey="108631" VKey="99527" VRelease="r1" /><title text="The Oracle Linux operating system must not forward IPv6 source-routed packets." /></overlay><overlay disa="1953" owner="disastig" ownerid="OL07-00-041001" ruleid="install_smartcard_packages" severity="medium"><VMSinfo SVKey="108633" VKey="99529" VRelease="r1" /><title text="The Oracle Linux operating system must have the required packages for multifactor authentication installed." /></overlay><overlay disa="1954" owner="disastig" ownerid="OL07-00-041002" ruleid="sssd_enable_pam_services" severity="medium"><VMSinfo SVKey="108635" VKey="99531" VRelease="r1" /><title text="The Oracle Linux operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM)." /></overlay><overlay disa="1954" owner="disastig" ownerid="OL07-00-041003" ruleid="smartcard_configure_cert_checking" severity="medium"><VMSinfo SVKey="108637" VKey="99533" VRelease="r1" /><title text="The Oracle Linux operating system must implement certificate status checking for PKI authentication." /></overlay><overlay disa="2421" owner="disastig" ownerid="OL07-00-041010" ruleid="wireless_disable_interfaces" severity="medium"><VMSinfo SVKey="108639" VKey="99535" VRelease="r1" /><title text="The Oracle Linux operating system must be configured so that all wireless network adapters are disabled." /></overlay><overlay disa="1314" owner="disastig" ownerid="OL07-00-910055" ruleid="file_permissions_var_log_audit" severity="medium"><VMSinfo SVKey="108641" VKey="99537" VRelease="r1" /><title text="The Oracle Linux operating system must protect audit information from unauthorized read, modification, or deletion." /></overlay></overlays>
+\ No newline at end of file
++<?xml version="1.0" encoding="UTF-8"?>
++<overlays xmlns="http://checklists.nist.gov/xccdf/1.1">
++  <overlay owner="disastig" ruleid="rpm_verify_ownership" ownerid="OL07-00-010010" disa="1496" severity="high">
++    <VMSinfo VKey="221652" SVKey="221652r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="rpm_verify_hashes" ownerid="OL07-00-010020" disa="1749" severity="high">
++    <VMSinfo VKey="221653" SVKey="221653r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_banner_enabled" ownerid="OL07-00-010030" disa="1388" severity="medium">
++    <VMSinfo VKey="221654" SVKey="221654r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_login_banner_text" ownerid="OL07-00-010040" disa="48" severity="medium">
++    <VMSinfo VKey="221655" SVKey="221655r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="banner_etc_issue" ownerid="OL07-00-010050" disa="48" severity="medium">
++    <VMSinfo VKey="221656" SVKey="221656r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_lock_enabled" ownerid="OL07-00-010060" disa="56" severity="medium">
++    <VMSinfo VKey="221657" SVKey="221657r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_enable_smartcard_auth" ownerid="OL07-00-010061" disa="1948" severity="medium">
++    <VMSinfo VKey="221658" SVKey="221658r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must uniquely identify and must authenticate users using multifactor authentication via a graphical user logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_lock_locked" ownerid="OL07-00-010062" disa="57" severity="medium">
++    <VMSinfo VKey="221659" SVKey="221659r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_idle_delay" ownerid="OL07-00-010070" disa="57" severity="medium">
++    <VMSinfo VKey="221660" SVKey="221660r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_user_locks" ownerid="OL07-00-010081" disa="57" severity="medium">
++    <VMSinfo VKey="221661" SVKey="221661r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent a user from overriding the screensaver lock-delay setting for the graphical user interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_session_idle_user_locks" ownerid="OL07-00-010082" disa="57" severity="medium">
++    <VMSinfo VKey="221662" SVKey="221662r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent a user from overriding the session idle-delay setting for the graphical user interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_idle_activation_enabled" ownerid="OL07-00-010100" disa="57" severity="medium">
++    <VMSinfo VKey="221664" SVKey="221664r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_idle_activation_locked" ownerid="OL07-00-010101" disa="57" severity="medium">
++    <VMSinfo VKey="221665" SVKey="221665r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent a user from overriding the screensaver idle-activation-enabled setting for the graphical user interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_screensaver_lock_delay" ownerid="OL07-00-010110" disa="57" severity="medium">
++    <VMSinfo VKey="221666" SVKey="221666r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must initiate a session lock for graphical user interfaces when the screensaver is activated."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="XXXX" ownerid="OL07-00-010118" disa="192" severity="medium">
++    <VMSinfo VKey="221667" SVKey="221667r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing passwords."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_retry" ownerid="OL07-00-010119" disa="192" severity="medium">
++    <VMSinfo VKey="221668" SVKey="221668r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, pwquality must be used."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_ucredit" ownerid="OL07-00-010120" disa="192" severity="medium">
++    <VMSinfo VKey="221669" SVKey="221669r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one upper-case character."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_lcredit" ownerid="OL07-00-010130" disa="193" severity="medium">
++    <VMSinfo VKey="221670" SVKey="221670r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one lower-case character."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_dcredit" ownerid="OL07-00-010140" disa="194" severity="medium">
++    <VMSinfo VKey="221671" SVKey="221671r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are assigned, the new password must contain at least one numeric character."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_ocredit" ownerid="OL07-00-010150" disa="1619" severity="medium">
++    <VMSinfo VKey="221672" SVKey="221672r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one special character."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_difok" ownerid="OL07-00-010160" disa="195" severity="medium">
++    <VMSinfo VKey="221673" SVKey="221673r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed a minimum of eight of the total number of characters must be changed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_minclass" ownerid="OL07-00-010170" disa="195" severity="medium">
++    <VMSinfo VKey="221674" SVKey="221674r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed a minimum of four character classes must be changed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_maxrepeat" ownerid="OL07-00-010180" disa="195" severity="medium">
++    <VMSinfo VKey="221675" SVKey="221675r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating consecutive characters must not be more than three characters."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_maxclassrepeat" ownerid="OL07-00-010190" disa="195" severity="medium">
++    <VMSinfo VKey="221676" SVKey="221676r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating characters of the same character class must not be more than four characters."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="set_password_hashing_algorithm_systemauth" ownerid="OL07-00-010200" disa="196" severity="medium">
++    <VMSinfo VKey="221677" SVKey="221677r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the PAM system service is configured to store only encrypted representations of passwords."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="set_password_hashing_algorithm_logindefs" ownerid="OL07-00-010210" disa="196" severity="medium">
++    <VMSinfo VKey="221678" SVKey="221678r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to use the shadow file to store only encrypted representations of passwords."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="set_password_hashing_algorithm_libuserconf" ownerid="OL07-00-010220" disa="196" severity="medium">
++    <VMSinfo VKey="221680" SVKey="221680r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_minimum_age_login_defs" ownerid="OL07-00-010230" disa="198" severity="medium">
++    <VMSinfo VKey="221681" SVKey="221681r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 24 hours/1 day minimum lifetime."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_set_min_life_existing" ownerid="OL07-00-010240" disa="198" severity="medium">
++    <VMSinfo VKey="221682" SVKey="221682r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that passwords are restricted to a 24 hours/1 day minimum lifetime."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_maximum_age_login_defs" ownerid="OL07-00-010250" disa="199" severity="medium">
++    <VMSinfo VKey="221683" SVKey="221683r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 60-day maximum lifetime."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_set_max_life_existing" ownerid="OL07-00-010260" disa="199" severity="medium">
++    <VMSinfo VKey="221684" SVKey="221684r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that existing passwords are restricted to a 60-day maximum lifetime."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_unix_remember" ownerid="OL07-00-010270" disa="200" severity="medium">
++    <VMSinfo VKey="221685" SVKey="221685r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that passwords are prohibited from reuse for a minimum of five generations."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_password_pam_minlen" ownerid="OL07-00-010280" disa="205" severity="medium">
++    <VMSinfo VKey="221686" SVKey="221686r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that passwords are a minimum of 15 characters in length."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="no_empty_passwords" ownerid="OL07-00-010290" disa="366" severity="high">
++    <VMSinfo VKey="221687" SVKey="221687r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have accounts configured with blank or null passwords."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_empty_passwords" ownerid="OL07-00-010300" disa="766" severity="high">
++    <VMSinfo VKey="221688" SVKey="221688r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="account_disable_post_pw_expiration" ownerid="OL07-00-010310" disa="795" severity="medium">
++    <VMSinfo VKey="221689" SVKey="221689r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_passwords_pam_faillock_deny" ownerid="OL07-00-010320" disa="44" severity="medium">
++    <VMSinfo VKey="221690" SVKey="221690r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_passwords_pam_faillock_deny_root" ownerid="OL07-00-010330" disa="2238" severity="medium">
++    <VMSinfo VKey="221691" SVKey="221691r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sudo_remove_nopasswd" ownerid="OL07-00-010340" disa="2038" severity="medium">
++    <VMSinfo VKey="221692" SVKey="221692r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that users must provide a password for privilege escalation."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sudo_remove_no_authenticate" ownerid="OL07-00-010350" disa="2038" severity="medium">
++    <VMSinfo VKey="228569" SVKey="228569r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so users must re-authenticate for privilege escalation."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_logon_fail_delay" ownerid="OL07-00-010430" disa="366" severity="medium">
++    <VMSinfo VKey="221693" SVKey="221693r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the delay between logon prompts following a failed console logon attempt is at least four seconds."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="gnome_gdm_disable_automatic_login" ownerid="OL07-00-010440" disa="366" severity="high">
++    <VMSinfo VKey="221694" SVKey="221694r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow an unattended or automatic logon to the system via a graphical user interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="gnome_gdm_disable_guest_login" ownerid="OL07-00-010450" disa="366" severity="high">
++    <VMSinfo VKey="221695" SVKey="221695r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow an unrestricted logon to the system."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_do_not_permit_user_env" ownerid="OL07-00-010460" disa="366" severity="medium">
++    <VMSinfo VKey="221696" SVKey="221696r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow users to override SSH environment variables."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="disable_host_auth" ownerid="OL07-00-010470" disa="366" severity="medium">
++    <VMSinfo VKey="221697" SVKey="221697r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow a non-certificate trusted host SSH logon to the system."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="grub2_password" ownerid="OL07-00-010480" disa="213" severity="high">
++    <VMSinfo VKey="221698" SVKey="221698r5059" VRelease="r505922"/>
++    <title text="Oracle Linux operating systems prior to version 7.2 with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="require_singleuser_auth" ownerid="OL07-00-010481" disa="213" severity="medium">
++    <VMSinfo VKey="221699" SVKey="221699r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must require authentication upon booting into single-user and maintenance modes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="XXXX" ownerid="OL07-00-010482" disa="213" severity="high">
++    <VMSinfo VKey="221700" SVKey="221700r5059" VRelease="r505922"/>
++    <title text="Oracle Linux operating systems version 7.2 or newer with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="grub2_uefi_password" ownerid="OL07-00-010490" disa="213" severity="high">
++    <VMSinfo VKey="221701" SVKey="221701r5059" VRelease="r505922"/>
++    <title text="Oracle Linux operating systems prior to version 7.2 using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="XXXX" ownerid="OL07-00-010491" disa="213" severity="high">
++    <VMSinfo VKey="221702" SVKey="221702r5059" VRelease="r505922"/>
++    <title text="Oracle Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="smartcard_auth" ownerid="OL07-00-010500" disa="764" severity="medium">
++    <VMSinfo VKey="221703" SVKey="221703r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multifactor authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_rsh-server_removed" ownerid="OL07-00-020000" disa="381" severity="high">
++    <VMSinfo VKey="221704" SVKey="221704r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have the rsh-server package installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_ypserv_removed" ownerid="OL07-00-020010" disa="381" severity="high">
++    <VMSinfo VKey="221705" SVKey="221705r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have the ypserv package installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="XXXX" ownerid="OL07-00-020019" disa="1233" severity="medium">
++    <VMSinfo VKey="221706" SVKey="221706r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must have a host-based intrusion detection tool installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="selinux_user_login_roles" ownerid="OL07-00-020020" disa="2235" severity="medium">
++    <VMSinfo VKey="221707" SVKey="221707r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="aide_periodic_cron_checking" ownerid="OL07-00-020030" disa="2699" severity="medium">
++    <VMSinfo VKey="221708" SVKey="221708r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that a file integrity tool verifies the baseline operating system configuration at least weekly."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="aide_scan_notification" ownerid="OL07-00-020040" disa="1744" severity="medium">
++    <VMSinfo VKey="221709" SVKey="221709r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that designated personnel are notified if baseline configurations are changed in an unauthorized manner."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="ensure_gpgcheck_globally_activated" ownerid="OL07-00-020050" disa="1749" severity="high">
++    <VMSinfo VKey="221710" SVKey="221710r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="ensure_gpgcheck_local_packages" ownerid="OL07-00-020060" disa="1749" severity="high">
++    <VMSinfo VKey="221711" SVKey="221711r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="kernel_module_usb-storage_disabled" ownerid="OL07-00-020100" disa="1958" severity="medium">
++    <VMSinfo VKey="221712" SVKey="221712r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to disable USB mass storage."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="kernel_module_dccp_disabled" ownerid="OL07-00-020101" disa="1958" severity="medium">
++    <VMSinfo VKey="221713" SVKey="221713r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the Datagram Congestion Control Protocol (DCCP) kernel module is disabled unless required."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="service_autofs_disabled" ownerid="OL07-00-020110" disa="778" severity="medium">
++    <VMSinfo VKey="221714" SVKey="221714r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must disable the file system automounter unless required."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="kernel_module_usb-storage_disabled" ownerid="OL07-00-020111" disa="1958" severity="medium">
++    <VMSinfo VKey="228567" SVKey="228567r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must disable the graphical user interface automounter unless required."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="clean_components_post_updating" ownerid="OL07-00-020200" disa="2617" severity="low">
++    <VMSinfo VKey="221715" SVKey="221715r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must remove all software components after updated versions have been installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="selinux_state" ownerid="OL07-00-020210" disa="2165" severity="medium">
++    <VMSinfo VKey="221716" SVKey="221716r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must enable SELinux."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="selinux_policytype" ownerid="OL07-00-020220" disa="2165" severity="medium">
++    <VMSinfo VKey="228570" SVKey="228570r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must enable the SELinux targeted policy."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="disable_ctrlaltdel_reboot" ownerid="OL07-00-020230" disa="366" severity="high">
++    <VMSinfo VKey="221717" SVKey="221717r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the x86 Ctrl-Alt-Delete key sequence is disabled on the command line."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dconf_gnome_disable_ctrlaltdel_reboot" ownerid="OL07-00-020231" disa="366" severity="high">
++    <VMSinfo VKey="228565" SVKey="228565r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so the x86 Ctrl-Alt-Delete key sequence is disabled in the Graphical User Interface."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_umask_etc_login_defs" ownerid="OL07-00-020240" disa="366" severity="medium">
++    <VMSinfo VKey="221718" SVKey="221718r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="installed_OS_is_vendor_supported" ownerid="OL07-00-020250" disa="366" severity="high">
++    <VMSinfo VKey="221719" SVKey="221719r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be a vendor supported release."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="security_patches_up_to_date" ownerid="OL07-00-020260" disa="366" severity="medium">
++    <VMSinfo VKey="221720" SVKey="221720r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system security patches and updates must be installed and up to date."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_root_login" ownerid="OL07-00-020270" disa="366" severity="medium">
++    <VMSinfo VKey="221721" SVKey="221721r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have unnecessary accounts."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="gid_passwd_group_same" ownerid="OL07-00-020300" disa="764" severity="low">
++    <VMSinfo VKey="221722" SVKey="221722r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all Group Identifiers (GIDs) referenced in the /etc/passwd file are defined in the /etc/group file."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_no_uid_except_zero" ownerid="OL07-00-020310" disa="366" severity="high">
++    <VMSinfo VKey="221723" SVKey="221723r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the root account must be the only account having unrestricted access to the system."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="no_files_unowned_by_user" ownerid="OL07-00-020320" disa="366" severity="medium">
++    <VMSinfo VKey="221724" SVKey="221724r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all files and directories have a valid owner."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permissions_ungroupowned" ownerid="OL07-00-020330" disa="366" severity="medium">
++    <VMSinfo VKey="221725" SVKey="221725r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all files and directories have a valid group owner."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_have_homedir_login_defs" ownerid="OL07-00-020610" disa="366" severity="medium">
++    <VMSinfo VKey="221727" SVKey="221727r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive user accounts, upon creation, are assigned a home directory."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_user_interactive_home_directory_exists" ownerid="OL07-00-020620" disa="366" severity="medium">
++    <VMSinfo VKey="221728" SVKey="221728r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive users have a home directory assigned and defined in the /etc/passwd file."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permissions_home_directories" ownerid="OL07-00-020630" disa="366" severity="medium">
++    <VMSinfo VKey="221729" SVKey="221729r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive user home directories have mode 0750 or less permissive."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_ownership_home_directories" ownerid="OL07-00-020640" disa="366" severity="medium">
++    <VMSinfo VKey="221730" SVKey="221730r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive user home directories are owned by their respective users."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_groupownership_home_directories" ownerid="OL07-00-020650" disa="366" severity="medium">
++    <VMSinfo VKey="221731" SVKey="221731r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive user home directories are group-owned by the home directory owners primary group."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_users_home_files_ownership" ownerid="OL07-00-020660" disa="366" severity="medium">
++    <VMSinfo VKey="221732" SVKey="221732r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are owned by the owner of the home directory."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_users_home_files_groupownership" ownerid="OL07-00-020670" disa="366" severity="medium">
++    <VMSinfo VKey="221733" SVKey="221733r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_users_home_files_permissions" ownerid="OL07-00-020680" disa="366" severity="medium">
++    <VMSinfo VKey="221734" SVKey="221734r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories have a mode of 0750 or less permissive."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_user_dot_user_ownership" ownerid="OL07-00-020690" disa="366" severity="medium">
++    <VMSinfo VKey="221735" SVKey="221735r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local initialization files for interactive users are owned by the home directory user or root."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_user_dot_group_ownership" ownerid="OL07-00-020700" disa="366" severity="medium">
++    <VMSinfo VKey="221736" SVKey="221736r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local initialization files for local interactive users are be group-owned by the users primary group or root."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permission_user_init_files" ownerid="OL07-00-020710" disa="366" severity="medium">
++    <VMSinfo VKey="221737" SVKey="221737r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local initialization files have mode 0740 or less permissive."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_user_home_paths_only" ownerid="OL07-00-020720" disa="366" severity="medium">
++    <VMSinfo VKey="221738" SVKey="221738r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_user_dot_no_world_writable_programs" ownerid="OL07-00-020730" disa="366" severity="medium">
++    <VMSinfo VKey="221739" SVKey="221739r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that local initialization files do not execute world-writable programs."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="selinux_all_devicefiles_labeled" ownerid="OL07-00-020900" disa="366" severity="medium">
++    <VMSinfo VKey="221740" SVKey="221740r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all system device files are correctly labeled to prevent unauthorized modification."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_home_nosuid" ownerid="OL07-00-021000" disa="366" severity="medium">
++    <VMSinfo VKey="221741" SVKey="221741r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that file systems containing user home directories are mounted to prevent files with the setuid and setgid bit set from being executed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_nosuid_removable_partitions" ownerid="OL07-00-021010" disa="366" severity="medium">
++    <VMSinfo VKey="221742" SVKey="221742r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_nosuid_remote_filesystems" ownerid="OL07-00-021020" disa="366" severity="medium">
++    <VMSinfo VKey="221743" SVKey="221743r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are being imported via Network File System (NFS)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_noexec_remote_filesystems" ownerid="OL07-00-021021" disa="366" severity="medium">
++    <VMSinfo VKey="221744" SVKey="221744r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent binary files from being executed on file systems that are being imported via Network File System (NFS)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_dev_shm_nosuid" ownerid="OL07-00-021024" disa="1764" severity="low">
++    <VMSinfo VKey="221747" SVKey="221747r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must mount /dev/shm with secure options."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dir_perms_world_writable_system_owned_group" ownerid="OL07-00-021030" disa="366" severity="medium">
++    <VMSinfo VKey="221748" SVKey="221748r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all world-writable directories are group-owned by root, sys, bin, or an application group."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="dir_perms_world_writable_system_owned" ownerid="OL07-00-021031" disa="366" severity="medium">
++    <VMSinfo VKey="228566" SVKey="228566r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all world-writable directories are owned by root, sys, bin, or an application user."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_umask_interactive_users" ownerid="OL07-00-021040" disa="366" severity="medium">
++    <VMSinfo VKey="221749" SVKey="221749r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must set the umask value to 077 for all local interactive user accounts."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="rsyslog_cron_logging" ownerid="OL07-00-021100" disa="366" severity="medium">
++    <VMSinfo VKey="221750" SVKey="221750r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must have cron logging implemented."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_owner_cron_allow" ownerid="OL07-00-021110" disa="366" severity="medium">
++    <VMSinfo VKey="221751" SVKey="221751r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is owned by root."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_groupowner_cron_allow" ownerid="OL07-00-021120" disa="366" severity="medium">
++    <VMSinfo VKey="221752" SVKey="221752r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is group-owned by root."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="service_kdump_disabled" ownerid="OL07-00-021300" disa="366" severity="medium">
++    <VMSinfo VKey="221753" SVKey="221753r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must disable Kernel core dumps unless needed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="partition_for_home" ownerid="OL07-00-021310" disa="366" severity="low">
++    <VMSinfo VKey="221754" SVKey="221754r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that a separate file system is used for user home directories (such as /home or an equivalent)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="partition_for_var" ownerid="OL07-00-021320" disa="366" severity="low">
++    <VMSinfo VKey="221755" SVKey="221755r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a separate file system for /var."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="partition_for_var_log_audit" ownerid="OL07-00-021330" disa="1849" severity="low">
++    <VMSinfo VKey="221756" SVKey="221756r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a separate file system for the system audit data path large enough to hold at least one week of audit data."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="partition_for_tmp" ownerid="OL07-00-021340" disa="366" severity="low">
++    <VMSinfo VKey="221757" SVKey="221757r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a separate file system for /tmp (or equivalent)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="grub2_enable_fips_mode" ownerid="OL07-00-021350" disa="2476" severity="high">
++    <VMSinfo VKey="221758" SVKey="221758r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="aide_verify_acls" ownerid="OL07-00-021600" disa="366" severity="low">
++    <VMSinfo VKey="221759" SVKey="221759r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify Access Control Lists (ACLs)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="aide_verify_ext_attributes" ownerid="OL07-00-021610" disa="366" severity="low">
++    <VMSinfo VKey="221760" SVKey="221760r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify extended attributes."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="aide_use_fips_hashes" ownerid="OL07-00-021620" disa="366" severity="medium">
++    <VMSinfo VKey="221761" SVKey="221761r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a file integrity tool that is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="grub2_no_removeable_media" ownerid="OL07-00-021700" disa="1813" severity="medium">
++    <VMSinfo VKey="221762" SVKey="221762r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow removable media to be used as the boot loader unless approved."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_telnet-server_removed" ownerid="OL07-00-021710" disa="381" severity="high">
++    <VMSinfo VKey="221763" SVKey="221763r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have the telnet-server package installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="service_auditd_enabled" ownerid="OL07-00-030000" disa="1814" severity="medium">
++    <VMSinfo VKey="221764" SVKey="221764r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that auditing is configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_system_shutdown" ownerid="OL07-00-030010" disa="139" severity="medium">
++    <VMSinfo VKey="221765" SVKey="221765r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must shut down upon audit processing failure, unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) in the event of an audit processing failure."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_name_format" ownerid="OL07-00-030201" disa="1851" severity="medium">
++    <VMSinfo VKey="221767" SVKey="221767r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to off-load audit logs onto a different system or storage media from the system being audited."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_name_format" ownerid="OL07-00-030210" disa="1851" severity="medium">
++    <VMSinfo VKey="221768" SVKey="221768r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must take appropriate action when the remote logging buffer is full."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_name_format" ownerid="OL07-00-030211" disa="1851" severity="medium">
++    <VMSinfo VKey="221769" SVKey="221769r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must label all off-loaded audit logs before sending them to the central log server."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_audispd_configure_remote_server" ownerid="OL07-00-030300" disa="1851" severity="medium">
++    <VMSinfo VKey="221770" SVKey="221770r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must off-load audit records onto a different system or media from the system being audited."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_audispd_encrypt_sent_records" ownerid="OL07-00-030310" disa="1851" severity="medium">
++    <VMSinfo VKey="221771" SVKey="221771r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_audispd_disk_full_action" ownerid="OL07-00-030320" disa="1851" severity="medium">
++    <VMSinfo VKey="221772" SVKey="221772r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the audit system takes appropriate action when the audit storage volume is full."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_audispd_network_failure_action" ownerid="OL07-00-030321" disa="1851" severity="medium">
++    <VMSinfo VKey="221773" SVKey="221773r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the audit system takes appropriate action when there is an error sending audit records to a remote system."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_data_retention_space_left" ownerid="OL07-00-030330" disa="1855" severity="medium">
++    <VMSinfo VKey="221774" SVKey="221774r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must initiate an action to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_data_retention_space_left_action" ownerid="OL07-00-030340" disa="1855" severity="medium">
++    <VMSinfo VKey="221775" SVKey="221775r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="auditd_data_retention_action_mail_acct" ownerid="OL07-00-030350" disa="1855" severity="medium">
++    <VMSinfo VKey="221776" SVKey="221776r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands" ownerid="OL07-00-030360" disa="2234" severity="medium">
++    <VMSinfo VKey="221777" SVKey="221777r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all executions of privileged functions."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_chown" ownerid="OL07-00-030370" disa="172" severity="medium">
++    <VMSinfo VKey="221778" SVKey="221778r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the chown syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fchown" ownerid="OL07-00-030380" disa="172" severity="medium">
++    <VMSinfo VKey="221779" SVKey="221779r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fchown syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_lchown" ownerid="OL07-00-030390" disa="172" severity="medium">
++    <VMSinfo VKey="221780" SVKey="221780r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the lchown syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fchownat" ownerid="OL07-00-030400" disa="172" severity="medium">
++    <VMSinfo VKey="221781" SVKey="221781r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fchownat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_chmod" ownerid="OL07-00-030410" disa="172" severity="medium">
++    <VMSinfo VKey="221782" SVKey="221782r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the chmod syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fchmod" ownerid="OL07-00-030420" disa="172" severity="medium">
++    <VMSinfo VKey="221783" SVKey="221783r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fchmod syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fchmodat" ownerid="OL07-00-030430" disa="172" severity="medium">
++    <VMSinfo VKey="221784" SVKey="221784r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fchmodat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_setxattr" ownerid="OL07-00-030440" disa="172" severity="medium">
++    <VMSinfo VKey="221785" SVKey="221785r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the setxattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fsetxattr" ownerid="OL07-00-030450" disa="172" severity="medium">
++    <VMSinfo VKey="221786" SVKey="221786r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fsetxattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_lsetxattr" ownerid="OL07-00-030460" disa="172" severity="medium">
++    <VMSinfo VKey="221787" SVKey="221787r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the lsetxattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_removexattr" ownerid="OL07-00-030470" disa="172" severity="medium">
++    <VMSinfo VKey="221788" SVKey="221788r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the removexattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_fremovexattr" ownerid="OL07-00-030480" disa="172" severity="medium">
++    <VMSinfo VKey="221789" SVKey="221789r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the fremovexattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_dac_modification_lremovexattr" ownerid="OL07-00-030490" disa="172" severity="medium">
++    <VMSinfo VKey="221790" SVKey="221790r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the lremovexattr syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_creat" ownerid="OL07-00-030500" disa="2884" severity="medium">
++    <VMSinfo VKey="221791" SVKey="221791r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the creat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_open" ownerid="OL07-00-030510" disa="2884" severity="medium">
++    <VMSinfo VKey="221792" SVKey="221792r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the open syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_openat" ownerid="OL07-00-030520" disa="2884" severity="medium">
++    <VMSinfo VKey="221793" SVKey="221793r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the openat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_open_by_handle_at" ownerid="OL07-00-030530" disa="2884" severity="medium">
++    <VMSinfo VKey="221794" SVKey="221794r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the open_by_handle_at syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_truncate" ownerid="OL07-00-030540" disa="2884" severity="medium">
++    <VMSinfo VKey="221795" SVKey="221795r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the truncate syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_unsuccessful_file_modification_ftruncate" ownerid="OL07-00-030550" disa="2884" severity="medium">
++    <VMSinfo VKey="221796" SVKey="221796r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the ftruncate syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_execution_semanage" ownerid="OL07-00-030560" disa="2884" severity="medium">
++    <VMSinfo VKey="221797" SVKey="221797r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the semanage command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_execution_setsebool" ownerid="OL07-00-030570" disa="2884" severity="medium">
++    <VMSinfo VKey="221798" SVKey="221798r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the setsebool command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_execution_chcon" ownerid="OL07-00-030580" disa="2884" severity="medium">
++    <VMSinfo VKey="221799" SVKey="221799r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the chcon command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_execution_setfiles" ownerid="OL07-00-030590" disa="2884" severity="medium">
++    <VMSinfo VKey="221800" SVKey="221800r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the setfiles command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_login_events_faillock" ownerid="OL07-00-030610" disa="2884" severity="medium">
++    <VMSinfo VKey="221801" SVKey="221801r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all unsuccessful account access events."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_login_events_lastlog" ownerid="OL07-00-030620" disa="2884" severity="medium">
++    <VMSinfo VKey="221802" SVKey="221802r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all successful account access events."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_passwd" ownerid="OL07-00-030630" disa="135" severity="medium">
++    <VMSinfo VKey="221803" SVKey="221803r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the passwd command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_unix_chkpwd" ownerid="OL07-00-030640" disa="135" severity="medium">
++    <VMSinfo VKey="221804" SVKey="221804r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the unix_chkpwd command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_gpasswd" ownerid="OL07-00-030650" disa="135" severity="medium">
++    <VMSinfo VKey="221805" SVKey="221805r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the gpasswd command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_chage" ownerid="OL07-00-030660" disa="135" severity="medium">
++    <VMSinfo VKey="221806" SVKey="221806r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the chage command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_userhelper" ownerid="OL07-00-030670" disa="135" severity="medium">
++    <VMSinfo VKey="221807" SVKey="221807r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the userhelper command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_su" ownerid="OL07-00-030680" disa="130" severity="medium">
++    <VMSinfo VKey="221808" SVKey="221808r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the su command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_sudo" ownerid="OL07-00-030690" disa="172" severity="medium">
++    <VMSinfo VKey="221809" SVKey="221809r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the sudo command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_sysadmin_actions" ownerid="OL07-00-030700" disa="130" severity="medium">
++    <VMSinfo VKey="221810" SVKey="221810r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_newgrp" ownerid="OL07-00-030710" disa="130" severity="medium">
++    <VMSinfo VKey="221811" SVKey="221811r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the newgrp command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_chsh" ownerid="OL07-00-030720" disa="130" severity="medium">
++    <VMSinfo VKey="221812" SVKey="221812r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the chsh command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_media_export" ownerid="OL07-00-030740" disa="2884" severity="medium">
++    <VMSinfo VKey="221813" SVKey="221813r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the mount command and syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_umount" ownerid="OL07-00-030750" disa="135" severity="medium">
++    <VMSinfo VKey="221814" SVKey="221814r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the umount command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_postdrop" ownerid="OL07-00-030760" disa="135" severity="medium">
++    <VMSinfo VKey="221815" SVKey="221815r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the postdrop command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_postqueue" ownerid="OL07-00-030770" disa="135" severity="medium">
++    <VMSinfo VKey="221816" SVKey="221816r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the postqueue command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_ssh_keysign" ownerid="OL07-00-030780" disa="135" severity="medium">
++    <VMSinfo VKey="221817" SVKey="221817r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the ssh-keysign command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_crontab" ownerid="OL07-00-030800" disa="135" severity="medium">
++    <VMSinfo VKey="221818" SVKey="221818r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the crontab command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_privileged_commands_pam_timestamp_check" ownerid="OL07-00-030810" disa="172" severity="medium">
++    <VMSinfo VKey="221819" SVKey="221819r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the pam_timestamp_check command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_kernel_module_loading_delete" ownerid="OL07-00-030819" disa="172" severity="medium">
++    <VMSinfo VKey="221820" SVKey="221820r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the create_module syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_kernel_module_loading_init" ownerid="OL07-00-030820" disa="172" severity="medium">
++    <VMSinfo VKey="221821" SVKey="221821r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the init_module syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_kernel_module_loading_finit" ownerid="OL07-00-030821" disa="172" severity="medium">
++    <VMSinfo VKey="221822" SVKey="221822r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the finit_module syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_kernel_module_loading_delete" ownerid="OL07-00-030830" disa="172" severity="medium">
++    <VMSinfo VKey="221823" SVKey="221823r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the delete_module syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_kernel_module_loading_delete" ownerid="OL07-00-030840" disa="172" severity="medium">
++    <VMSinfo VKey="221824" SVKey="221824r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the kmod command."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_usergroup_modification_passwd" ownerid="OL07-00-030870" disa="2130" severity="medium">
++    <VMSinfo VKey="221825" SVKey="221825r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_usergroup_modification_group" ownerid="OL07-00-030871" disa="18" severity="medium">
++    <VMSinfo VKey="221826" SVKey="221826r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_usergroup_modification_gshadow" ownerid="OL07-00-030872" disa="18" severity="medium">
++    <VMSinfo VKey="221827" SVKey="221827r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_usergroup_modification_shadow" ownerid="OL07-00-030873" disa="18" severity="medium">
++    <VMSinfo VKey="221828" SVKey="221828r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_usergroup_modification_opasswd" ownerid="OL07-00-030874" disa="18" severity="medium">
++    <VMSinfo VKey="221829" SVKey="221829r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_file_deletion_events_rename" ownerid="OL07-00-030880" disa="2884" severity="medium">
++    <VMSinfo VKey="221830" SVKey="221830r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the rename syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_file_deletion_events_renameat" ownerid="OL07-00-030890" disa="2884" severity="medium">
++    <VMSinfo VKey="221831" SVKey="221831r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the renameat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_file_deletion_events_rmdir" ownerid="OL07-00-030900" disa="2884" severity="medium">
++    <VMSinfo VKey="221832" SVKey="221832r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the rmdir syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_file_deletion_events_unlink" ownerid="OL07-00-030910" disa="2884" severity="medium">
++    <VMSinfo VKey="221833" SVKey="221833r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the unlink syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="audit_rules_file_deletion_events_unlinkat" ownerid="OL07-00-030920" disa="2884" severity="medium">
++    <VMSinfo VKey="221834" SVKey="221834r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must audit all uses of the unlinkat syscall."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="rsyslog_remote_loghost" ownerid="OL07-00-031000" disa="366" severity="medium">
++    <VMSinfo VKey="221835" SVKey="221835r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must send rsyslog output to a log aggregation server."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="rsyslog_nolisten" ownerid="OL07-00-031010" disa="366" severity="medium">
++    <VMSinfo VKey="221836" SVKey="221836r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="install_mcafee_antivirus" ownerid="OL07-00-032000" disa="366" severity="high">
++    <VMSinfo VKey="221837" SVKey="221837r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a virus scan program."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_max_concurrent_login_sessions" ownerid="OL07-00-040000" disa="54" severity="low">
++    <VMSinfo VKey="221838" SVKey="221838r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="configure_firewalld_ports" ownerid="OL07-00-040100" disa="2314" severity="medium">
++    <VMSinfo VKey="221839" SVKey="221839r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_use_approved_ciphers" ownerid="OL07-00-040110" disa="3123" severity="medium">
++    <VMSinfo VKey="221840" SVKey="221840r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a FIPS 140-2 approved cryptographic algorithm for SSH communications."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="accounts_tmout" ownerid="OL07-00-040160" disa="1133" severity="medium">
++    <VMSinfo VKey="221841" SVKey="221841r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all network connections associated with a communication session are terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_enable_warning_banner" ownerid="OL07-00-040170" disa="48" severity="medium">
++    <VMSinfo VKey="221842" SVKey="221842r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner immediately prior to, or as part of, remote access logon prompts."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sssd_ldap_start_tls" ownerid="OL07-00-040180" disa="1453" severity="medium">
++    <VMSinfo VKey="221843" SVKey="221843r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sssd_ldap_configure_tls_reqcert" ownerid="OL07-00-040190" disa="1453" severity="medium">
++    <VMSinfo VKey="221844" SVKey="221844r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sssd_ldap_configure_tls_ca" ownerid="OL07-00-040200" disa="1453" severity="medium">
++    <VMSinfo VKey="221845" SVKey="221845r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_kernel_randomize_va_space" ownerid="OL07-00-040201" disa="2824" severity="medium">
++    <VMSinfo VKey="221846" SVKey="221846r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement virtual address space randomization."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_openssh-server_installed" ownerid="OL07-00-040300" disa="2422" severity="medium">
++    <VMSinfo VKey="221847" SVKey="221847r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all networked systems have SSH installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="service_sshd_enabled" ownerid="OL07-00-040310" disa="2418" severity="medium">
++    <VMSinfo VKey="221848" SVKey="221848r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all networked systems use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_set_idle_timeout" ownerid="OL07-00-040320" disa="1133" severity="medium">
++    <VMSinfo VKey="221849" SVKey="221849r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_rhosts_rsa" ownerid="OL07-00-040330" disa="366" severity="medium">
++    <VMSinfo VKey="221850" SVKey="221850r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using RSA rhosts authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_set_keepalive" ownerid="OL07-00-040340" disa="1133" severity="medium">
++    <VMSinfo VKey="221851" SVKey="221851r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic terminate after a period of inactivity."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_rhosts" ownerid="OL07-00-040350" disa="366" severity="medium">
++    <VMSinfo VKey="221852" SVKey="221852r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using rhosts authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_print_last_log" ownerid="OL07-00-040360" disa="366" severity="medium">
++    <VMSinfo VKey="221853" SVKey="221853r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the date and time of the last successful account logon upon an SSH logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_root_login" ownerid="OL07-00-040370" disa="366" severity="medium">
++    <VMSinfo VKey="221854" SVKey="221854r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not permit direct logons to the root account using remote access via SSH."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_user_known_hosts" ownerid="OL07-00-040380" disa="366" severity="medium">
++    <VMSinfo VKey="221855" SVKey="221855r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using known hosts authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_allow_only_protocol2" ownerid="OL07-00-040390" disa="197" severity="high">
++    <VMSinfo VKey="221856" SVKey="221856r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use the SSHv2 protocol."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_use_approved_macs" ownerid="OL07-00-040400" disa="1453" severity="medium">
++    <VMSinfo VKey="221857" SVKey="221857r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permissions_sshd_pub_key" ownerid="OL07-00-040410" disa="366" severity="medium">
++    <VMSinfo VKey="221858" SVKey="221858r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH public host key files have mode 0644 or less permissive."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permissions_sshd_private_key" ownerid="OL07-00-040420" disa="366" severity="medium">
++    <VMSinfo VKey="221859" SVKey="221859r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH private host key files have mode 0640 or less permissive."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_gssapi_auth" ownerid="OL07-00-040430" disa="1813" severity="medium">
++    <VMSinfo VKey="221860" SVKey="221860r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_kerb_auth" ownerid="OL07-00-040440" disa="1813" severity="medium">
++    <VMSinfo VKey="221861" SVKey="221861r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not permit Kerberos authentication unless needed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_enable_strictmodes" ownerid="OL07-00-040450" disa="366" severity="medium">
++    <VMSinfo VKey="221862" SVKey="221862r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon performs strict mode checking of home directory configuration files."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_use_priv_separation" ownerid="OL07-00-040460" disa="366" severity="medium">
++    <VMSinfo VKey="221863" SVKey="221863r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon uses privilege separation."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_disable_compression" ownerid="OL07-00-040470" disa="366" severity="medium">
++    <VMSinfo VKey="221864" SVKey="221864r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the SSH daemon does not allow compression or only allows compression after successful authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="XXXX" ownerid="OL07-00-040480" disa="2468" severity="medium">
++    <VMSinfo VKey="221865" SVKey="221865r5059" VRelease="r505922"/>
++    <title text="The operating system must request and perform data origin authentication verification and data integrity verification on the name/address resolution responses the system receives from authoritative sources."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="chronyd_or_ntpd_set_maxpoll" ownerid="OL07-00-040500" disa="1891" severity="medium">
++    <VMSinfo VKey="221866" SVKey="221866r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_tcp_invalid_ratelimit" ownerid="OL07-00-040510" disa="2385" severity="medium">
++    <VMSinfo VKey="221867" SVKey="221867r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="service_firewalld_enabled" ownerid="OL07-00-040520" disa="366" severity="medium">
++    <VMSinfo VKey="221868" SVKey="221868r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must enable an application firewall, if available."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="display_login_attempts" ownerid="OL07-00-040530" disa="366" severity="low">
++    <VMSinfo VKey="221869" SVKey="221869r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must display the date and time of the last successful account logon upon logon."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="no_user_host_based_files" ownerid="OL07-00-040540" disa="366" severity="high">
++    <VMSinfo VKey="221870" SVKey="221870r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not contain .shosts files."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="no_host_based_files" ownerid="OL07-00-040550" disa="366" severity="high">
++    <VMSinfo VKey="221871" SVKey="221871r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not contain shosts.equiv files."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="network_configure_name_resolution" ownerid="OL07-00-040600" disa="366" severity="low">
++    <VMSinfo VKey="221872" SVKey="221872r5059" VRelease="r505922"/>
++    <title text="For Oracle Linux operating systems using DNS resolution, at least two name servers must be configured."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_all_accept_source_route" ownerid="OL07-00-040610" disa="366" severity="medium">
++    <VMSinfo VKey="221873" SVKey="221873r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_all_rp_filter" ownerid="OL07-00-040611" disa="366" severity="medium">
++    <VMSinfo VKey="221874" SVKey="221874r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible on all interfaces."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_default_rp_filter" ownerid="OL07-00-040612" disa="366" severity="medium">
++    <VMSinfo VKey="221875" SVKey="221875r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible by default."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_default_accept_source_route" ownerid="OL07-00-040620" disa="366" severity="medium">
++    <VMSinfo VKey="221876" SVKey="221876r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" ownerid="OL07-00-040630" disa="366" severity="medium">
++    <VMSinfo VKey="221877" SVKey="221877r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_default_accept_redirects" ownerid="OL07-00-040640" disa="366" severity="medium">
++    <VMSinfo VKey="221878" SVKey="221878r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_all_accept_redirects" ownerid="OL07-00-040641" disa="366" severity="medium">
++    <VMSinfo VKey="221879" SVKey="221879r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_default_send_redirects" ownerid="OL07-00-040650" disa="366" severity="medium">
++    <VMSinfo VKey="221880" SVKey="221880r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_conf_all_send_redirects" ownerid="OL07-00-040660" disa="366" severity="medium">
++    <VMSinfo VKey="221881" SVKey="221881r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="network_sniffer_disabled" ownerid="OL07-00-040670" disa="366" severity="medium">
++    <VMSinfo VKey="221882" SVKey="221882r5059" VRelease="r505922"/>
++    <title text="Network interfaces configured on The Oracle Linux operating system must not be in promiscuous mode."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="postfix_prevent_unrestricted_relay" ownerid="OL07-00-040680" disa="366" severity="medium">
++    <VMSinfo VKey="221883" SVKey="221883r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured to prevent unrestricted mail relaying."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_vsftpd_removed" ownerid="OL07-00-040690" disa="366" severity="high">
++    <VMSinfo VKey="221884" SVKey="221884r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have a File Transfer Protocol (FTP) server package installed unless needed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_tftp-server_removed" ownerid="OL07-00-040700" disa="366" severity="high">
++    <VMSinfo VKey="221885" SVKey="221885r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have the Trivial File Transfer Protocol (TFTP) server package installed if not required for operational support."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sshd_enable_x11_forwarding" ownerid="OL07-00-040710" disa="366" severity="high">
++    <VMSinfo VKey="221886" SVKey="221886r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that remote X connections for interactive users are encrypted."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="tftpd_uses_secure_mode" ownerid="OL07-00-040720" disa="366" severity="medium">
++    <VMSinfo VKey="221887" SVKey="221887r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon is configured to operate in secure mode."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="package_xorg-x11-server-common_removed" ownerid="OL07-00-040730" disa="366" severity="medium">
++    <VMSinfo VKey="221888" SVKey="221888r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have a graphical display manager installed unless approved."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv4_ip_forward" ownerid="OL07-00-040740" disa="366" severity="medium">
++    <VMSinfo VKey="221889" SVKey="221889r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not be performing packet forwarding unless the system is a router."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="mount_option_krb_sec_remote_filesystems" ownerid="OL07-00-040750" disa="366" severity="medium">
++    <VMSinfo VKey="221890" SVKey="221890r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="snmpd_not_default_password" ownerid="OL07-00-040800" disa="366" severity="high">
++    <VMSinfo VKey="221891" SVKey="221891r5059" VRelease="r505922"/>
++    <title text="SNMP community strings on the Oracle Linux operating system must be changed from the default."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="set_firewalld_default_zone" ownerid="OL07-00-040810" disa="366" severity="medium">
++    <VMSinfo VKey="221892" SVKey="221892r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system access control program must be configured to grant or deny system access to specific hosts and services."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="libreswan_approved_tunnels" ownerid="OL07-00-040820" disa="366" severity="medium">
++    <VMSinfo VKey="221893" SVKey="221893r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not have unauthorized IP tunnels configured."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sysctl_net_ipv6_conf_all_accept_source_route" ownerid="OL07-00-040830" disa="366" severity="medium">
++    <VMSinfo VKey="221894" SVKey="221894r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must not forward IPv6 source-routed packets."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="install_smartcard_packages" ownerid="OL07-00-041001" disa="1954" severity="medium">
++    <VMSinfo VKey="221895" SVKey="221895r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must have the required packages for multifactor authentication installed."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="sssd_enable_pam_services" ownerid="OL07-00-041002" disa="1948" severity="medium">
++    <VMSinfo VKey="221896" SVKey="221896r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM)."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="smartcard_configure_cert_checking" ownerid="OL07-00-041003" disa="1953" severity="medium">
++    <VMSinfo VKey="221897" SVKey="221897r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must implement certificate status checking for PKI authentication."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="wireless_disable_interfaces" ownerid="OL07-00-041010" disa="2421" severity="medium">
++    <VMSinfo VKey="221898" SVKey="221898r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must be configured so that all wireless network adapters are disabled."/>
++  </overlay>
++  <overlay owner="disastig" ruleid="file_permissions_var_log_audit" ownerid="OL07-00-910055" disa="164" severity="medium">
++    <VMSinfo VKey="221899" SVKey="221899r5059" VRelease="r505922"/>
++    <title text="The Oracle Linux operating system must protect audit information from unauthorized read, modification, or deletion."/>
++  </overlay>
++</overlays>
+diff --git a/shared/references/disa-stig-ol7-v1r1-xccdf-manual.xml b/shared/references/disa-stig-ol7-v1r1-xccdf-manual.xml
+deleted file mode 100644
+index 48b9c6affb..0000000000
+--- a/shared/references/disa-stig-ol7-v1r1-xccdf-manual.xml
++++ /dev/null
+@@ -1,4928 +0,0 @@
+-<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dc="http://purl.org/dc/elements/1.1/" id="Oracle_Linux_7_STIG" xml:lang="en" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2020-02-04">accepted</status><title>Oracle Linux 7 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 03 Feb 20201I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-OS-000256-GPOS-00097<GroupDescription></GroupDescription>OL07-00-010010The Oracle Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values.<VulnDiscussion>Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default.
+-
+-Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099, SRG-OS-000278-GPOS-00108</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001493CCI-001494CCI-001495CCI-001496Run the following command to determine which package owns the file:
+-
+-# rpm -qf <filename>
+-
+-Reset the permissions of files within a package with the following command:
+-
+-#rpm --setperms <packagename>
+-
+-Reset the user and group ownership of files within a package with the following command:
+-
+-#rpm --setugids <packagename>Verify the file permissions, ownership, and group membership of system files and commands match the vendor values.
+-
+-Check the default file permissions, ownership, and group membership of system files and commands with the following command:
+-
+-# for i in `rpm -Va | grep '^.M' | cut -d " " -f4,5`;do for j in `rpm -qf $i`;do rpm -ql $j --dump | cut -d " " -f1,5,6,7 | grep $i;done;done
+-/var/log/gdm 040755 root root
+-/etc/audisp/audisp-remote.conf 0100640 root root
+-/usr/bin/passwd 0104755 root root
+-
+-For each file returned, verify the current permissions, ownership, and group membership:
+-# ls -la <filename>
+--rw-------. 1 root root 133 Jan 11 13:25 /etc/audisp/audisp-remote.conf
+-
+-If the file is more permissive than the default permissions, this is a finding.
+-
+-If the file is not owned by the default owner and is not documented with the Information System Security Officer (ISSO), this is a finding.
+-
+-If the file is not a member of the default group and is not documented with the ISSO, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-010020The Oracle Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values.<VulnDiscussion>Without cryptographic integrity protections, system command and files can be altered by unauthorized users without detection.
+-
+-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Run the following command to determine which package owns the file:
+-
+-# rpm -qf <filename>
+-
+-The package can be reinstalled from a yum repository using the command:
+-
+-# sudo yum reinstall <packagename>
+-
+-Alternatively, the package can be reinstalled from trusted media using the command:
+-
+-# sudo rpm -Uvh <packagename>Verify the cryptographic hash of system files and commands match the vendor values.
+-
+-Check the cryptographic hash of system files and commands with the following command:
+-
+-Note: System configuration files (indicated by a "c" in the second column) are expected to change over time. Unusual modifications should be investigated through the system audit log.
+-
+-# rpm -Va | grep '^..5'
+-
+-If there is any output from the command for system files, or binaries, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>OL07-00-010030The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.<VulnDiscussion>The display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+-
+-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+-
+-The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
+-
+-"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."
+-
+-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000048CCI-000050CCI-001384CCI-001385CCI-001386CCI-001387CCI-001388Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
+-
+-Note: If the system does not have GNOME 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:
+-
+-# touch /etc/dconf/db/local.d/01-banner-message
+-
+-Add the following line 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
+-
+-Update the system databases:
+-
+-# dconf update
+-
+-Users must log out, and then log in again before the system-wide settings take effect.Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+-
+-Check to see if the operating system displays a banner at the logon screen with the following command:
+-
+-# 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.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>OL07-00-010040The Oracle Linux operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+-
+-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+-
+-The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
+-
+-"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."
+-
+-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000048Configure the operating system to display the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
+-
+-Note: If the system does not have GNOME 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:
+-
+-# touch /etc/dconf/db/local.d/01-banner-message
+-
+-Add the following line 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
+-
+-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 GUI.
+-
+-Run the following command to update the database:
+-# dconf updateVerify the operating system displays the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+-
+-Check that the operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text with the command:
+-
+-# 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 GUI.
+-
+-If the banner does not match the approved Standard Mandatory DoD Notice and Consent Banner, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>OL07-00-010050The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+-
+-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+-
+-The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
+-
+-"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."
+-
+-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000048Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the command line by editing the "/etc/issue" file.
+-
+-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."Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a command line user logon.
+-
+-Check to see if the operating system displays a banner at the command line logon screen with the following command:
+-
+-# more /etc/issue
+-
+-The command should 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 operating 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 "/etc/issue" file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>OL07-00-010060The Oracle Linux operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
+-
+-The session lock is implemented at the point where session activity can be determined.
+-
+-Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.
+-
+-Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000056CCI-000058Configure the operating system to enable a user's session lock until that user re-establishes 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:
+-
+-# touch /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:
+-
+-# dconf update
+-
+-Users must log out and then log in again before the system-wide settings take effect.Verify the operating system enables a user's session lock until that user re-establishes access using established identification and authentication procedures. The screen program must be installed to lock sessions on the console.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+-
+-Check to see if the screen lock is enabled with the following command:
+-
+-# grep -i lock-enabled /etc/dconf/db/local.d/*
+-lock-enabled=true
+-
+-If the "lock-enabled" setting is missing or is not set to "true", this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>OL07-00-010061The Oracle Linux operating system must uniquely identify and must authenticate users using multifactor authentication via a graphical user logon.<VulnDiscussion>To assure accountability and prevent unauthenticated access, users must be identified and authenticated to prevent potential misuse and compromise of the system.
+-
+-Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+-
+-Satisfies: SRG-OS-000375-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001948Configure the operating system to uniquely identify and authenticate users using multifactor authentication via a graphical user logon.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+-
+-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+-
+-Note: The example is using the local system database, so if the system is using another database in "/etc/dconf/profile/user", create the file under the appropriate subdirectory.
+-
+-# touch /etc/dconf/db/local.d/00-defaults
+-
+-Edit "[org/gnome/login-screen]" and add or update the following line:
+-enable-smartcard-authentication=true 
+-
+-Update the system databases:
+-# dconf updateVerify the operating system uniquely identifies and authenticates users using multifactor authentication via a graphical user logon.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+-
+-Determine which profile the system database is using with the following command:
+-
+-# grep system-db /etc/dconf/profile/user
+-
+-system-db:local
+-
+-Note: The example 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.
+-
+-# grep enable-smartcard-authentication /etc/dconf/db/local.d/*
+-
+-enable-smartcard-authentication=true
+-
+-If "enable-smartcard-authentication" is set to "false" or the keyword is missing, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010062The Oracle Linux operating system must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
+-
+-The session lock is implemented at the point where session activity can be determined.
+-
+-The ability to enable/disable a session lock is given to the user by default. Disabling the user’s ability to disengage the graphical user interface session lock ensures all sessions will lock after the specified period of time.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system to prevent a user from overriding a screensaver lock 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: 
+-
+-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.
+-
+-# touch /etc/dconf/db/local.d/locks/session
+-
+-Add the setting to lock the screensaver lock-enabled setting:
+-
+-/org/gnome/desktop/screensaver/lock-enabledVerify the operating system prevents a user from overriding the screensaver lock-enabled setting for the graphical user interface. 
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console.
+-
+-Determine which profile the system database is using with the following command:
+-# grep system-db /etc/dconf/profile/user
+-
+-system-db:local
+-
+-Check for the lock-enabled setting 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.
+-
+-# grep -i lock-enabled /etc/dconf/db/local.d/locks/*
+-
+-/org/gnome/desktop/screensaver/lock-enabled
+-
+-If the command does not return a result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010070The Oracle Linux operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock the operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled, and take action to initiate the session lock.
+-
+-The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system 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:
+-
+-# 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
+-
+-You must include the "uint32" along with the integer key values as shown.
+-
+-Update the system databases:
+-
+-# dconf update
+-
+-Users must log out and then log in again before the system-wide settings take effect.Verify the operating system initiates a screensaver after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+-
+-Check to see if GNOME is configured to display a screensaver after a 15 minute delay with the following command:
+-
+-# grep -i idle-delay /etc/dconf/db/local.d/*
+-idle-delay=uint32 900
+-
+-If the "idle-delay" setting is missing or is not set to "900" or less, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010081The Oracle Linux operating system must prevent a user from overriding the screensaver lock-delay setting for the graphical user interface.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock the operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled, and take action to initiate the session lock.
+-
+-The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system to prevent a user from overriding a screensaver lock 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: 
+-
+-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.
+-
+-# touch /etc/dconf/db/local.d/locks/session
+-
+-Add the setting to lock the screensaver lock delay:
+-
+-/org/gnome/desktop/screensaver/lock-delayVerify the operating system prevents a user from overriding a screensaver lock after a 15-minute period of inactivity for graphical user interfaces. 
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console.
+-
+-Determine which profile the system database is using with the following command:
+-# grep system-db /etc/dconf/profile/user
+-
+-system-db:local
+-
+-Check for the lock delay setting 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.
+-
+-# grep -i lock-delay /etc/dconf/db/local.d/locks/*
+-
+-/org/gnome/desktop/screensaver/lock-delay
+-
+-If the command does not return a result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010082The Oracle Linux operating system must prevent a user from overriding the session idle-delay setting for the graphical user interface.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock their operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled and take action to initiate the session lock.
+-
+-The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system to prevent a user from overriding a session lock 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: 
+-
+-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.
+-
+-# touch /etc/dconf/db/local.d/locks/session
+-
+-Add the setting to lock the session idle delay:
+-
+-/org/gnome/desktop/session/idle-delayVerify the operating system prevents a user from overriding session idle delay after a 15-minute period of inactivity for graphical user interfaces. 
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console. 
+-
+-Determine which profile the system database is using with the following command:
+-# grep system-db /etc/dconf/profile/user
+-
+-system-db:local
+-
+-Check for the session idle delay setting 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.
+-
+-# grep -i idle-delay /etc/dconf/db/local.d/locks/*
+-
+-/org/gnome/desktop/session/idle-delay
+-
+-If the command does not return a result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010090The Oracle Linux operating system must have the screen package installed.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock their operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled, and take action to initiate the session lock.
+-
+-The screen and tmux packages allow for a session lock to be implemented and configured.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Install the screen package to allow the initiation of a session lock after a 15-minute period of inactivity.
+-
+-Install the screen program (if it is not on the system) with the following command:
+-
+-# yum install screen 
+-
+-OR
+-
+-Install the tmux program (if it is not on the system) with the following command:
+-
+-#yum install tmuxVerify the operating system has the screen package installed.
+-
+-Check to see if the screen package is installed with the following command:
+-
+-# yum list installed screen
+-screen-4.3.1-3-x86_64.rpm
+-
+-If the screen package is not installed, check to see if the tmux package is installed with the following command:
+-
+-#yum list installed tmux
+-tmux-1.8-4.el7.x86_64.rpm 
+-
+-If either the screen package or the tmux package is not installed, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010100The Oracle Linux operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock their operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled and take action to initiate the session lock.
+-
+-The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system to initiate a session lock 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: 
+-
+-# touch /etc/dconf/db/local.d/00-screensaver
+-
+-Add the setting to enable screensaver locking after 15 minutes of inactivity:
+-
+-[org/gnome/desktop/screensaver]
+-
+-idle-activation-enabled=true
+-
+-Update the system databases:
+-
+-# dconf update
+-
+-Users must log out and then log in again before the system-wide settings take effect.Verify the operating system initiates a session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+-
+-If it is installed, GNOME must be configured to enforce a session lock after a 15-minute delay. Check for the session lock settings with the following commands:
+-
+-# grep -i idle-activation-enabled /etc/dconf/db/local.d/*
+-
+-idle-activation-enabled=true
+-
+-If "idle-activation-enabled" is not set to "true", this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010101The Oracle Linux operating system must prevent a user from overriding the screensaver idle-activation-enabled setting for the graphical user interface.<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.
+-
+-The session lock is implemented at the point where session activity can be determined.
+-
+-The ability to enable/disable a session lock is given to the user by default. Disabling the user's ability to disengage the graphical user interface session lock provides the assurance that all sessions will lock after the specified period of time.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure the operating system to prevent a user from overriding a screensaver lock 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: 
+-
+-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.
+-
+-# touch /etc/dconf/db/local.d/locks/session
+-
+-Add the setting to lock the screensaver idle-activation-enabled setting:
+-
+-/org/gnome/desktop/screensaver/idle-activation-enabledVerify the operating system prevents a user from overriding the screensaver idle-activation-enabled setting for the graphical user interface. 
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console.
+-
+-Determine which profile the system database is using with the following command:
+-# grep system-db /etc/dconf/profile/user
+-
+-system-db:local
+-
+-Check for the idle-activation-enabled setting 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.
+-
+-# grep -i idle-activation-enabled /etc/dconf/db/local.d/locks/*
+-
+-/org/gnome/desktop/screensaver/idle-activation-enabled
+-
+-If the command does not return a result, this is a finding.SRG-OS-000029-GPOS-00010<GroupDescription></GroupDescription>OL07-00-010110The Oracle Linux operating system must initiate a session lock for graphical user interfaces when the screensaver is activated.<VulnDiscussion>A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to lock their operating system session manually prior to leaving the workstation, operating systems must be able to identify when a user's session has idled, and take action to initiate the session lock.
+-
+-The session lock is implemented at the point where session activity can be determined and/or controlled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000057Configure 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: 
+-
+-# touch /etc/dconf/db/local.d/00-screensaver
+-
+-Add the setting to enable session locking when a screensaver is activated:
+-
+-[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:
+-
+-# dconf update
+-
+-Users must log out and then log in again before the system-wide settings take effect.Verify the operating system initiates a session lock a for graphical user interfaces when the screensaver is activated. 
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console.
+-
+-If GNOME is installed, check to see a session lock occurs when the screensaver is activated with the following command:
+-
+-# grep -i lock-delay /etc/dconf/db/local.d/*
+-lock-delay=uint32 5
+-
+-If the "lock-delay" setting is missing, or is not set to "5" or less, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>OL07-00-010118The Oracle Linux operating system must be configured so that /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing passwords.<VulnDiscussion>Pluggable authentication modules (PAM) allow for a modular approach to integrating authentication methods. PAM operates in a top-down processing model and if the modules are not listed in the correct order, an important security function could be bypassed if stack entries are not centralized.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000192Configure PAM to utilize /etc/pam.d/system-auth when changing passwords.
+-
+-Add the following line to "/etc/pam.d/passwd" (or modify the line to have the required value):
+-
+-password substack system-authVerify that /etc/pam.d/passwd is configured to use /etc/pam.d/system-auth when changing passwords:
+-
+-# cat /etc/pam.d/passwd | grep -i substack | grep -i system-auth
+-password substack system-auth
+-
+-If no results are returned, the line is commented out, this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>OL07-00-010119The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, pwquality must be used.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+-
+-Satisfied: SRG-OS-000480-GPOS-00229, SRG-OS-000069-GPOS-00037</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000192Configure the operating system to use "pwquality" to enforce password complexity rules.
+-
+-Add the following line to "/etc/pam.d/system-auth" (or modify the line to have the required value):
+-
+-password required pam_pwquality.so retry=3
+-
+-Note: The value of "retry" should be between "1" and "3".Verify the operating system uses "pwquality" to enforce the password complexity rules. 
+-
+-Check for the use of "pwquality" with the following command:
+-
+-# cat /etc/pam.d/system-auth | grep pam_pwquality
+-
+-password required pam_pwquality.so retry=3
+-
+-If the command does not return an uncommented line containing the value "pam_pwquality.so", this is a finding.
+-
+-If the value of "retry" is set to "0" or greater than "3", this is a finding.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>OL07-00-010120The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one upper-case character.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one of several factors that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that must be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000192Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used by setting the "ucredit" option.
+-
+-Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+-
+-ucredit = -1Note: The value to require a number of upper-case characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+-
+-Check the value for "ucredit" in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep ucredit /etc/security/pwquality.conf 
+-ucredit = -1
+-
+-If the value of "ucredit" is not set to a negative value, this is a finding.SRG-OS-000070-GPOS-00038<GroupDescription></GroupDescription>OL07-00-010130The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one lower-case character.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one of several factors that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that must be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000193Configure the system to require at least one lower-case character when creating or changing a password.
+-
+-Add or modify the following line 
+-in "/etc/security/pwquality.conf":
+-
+-lcredit = -1Note: The value to require a number of lower-case characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+-
+-Check the value for "lcredit" in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep lcredit /etc/security/pwquality.conf 
+-lcredit = -1 
+-
+-If the value of "lcredit" is not set to a negative value, this is a finding.SRG-OS-000071-GPOS-00039<GroupDescription></GroupDescription>OL07-00-010140The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are assigned, the new password must contain at least one numeric character.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one of several factors that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that must be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000194Configure the operating system to enforce password complexity by requiring that at least one numeric character be used by setting the "dcredit" option.
+-
+-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
+-
+-dcredit = -1Note: The value to require a number of numeric characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+-
+-Check the value for "dcredit" in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep dcredit /etc/security/pwquality.conf 
+-dcredit = -1 
+-
+-If the value of "dcredit" is not set to a negative value, this is a finding.SRG-OS-000266-GPOS-00101<GroupDescription></GroupDescription>OL07-00-010150The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one special character.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001619Configure the operating system to enforce password complexity by requiring that at least one special character be used by setting the "ocredit" option.
+-
+-Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+-
+-ocredit = -1Verify the operating system enforces password complexity by requiring that at least one special character be used.
+-
+-Note: The value to require a number of special characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+-
+-Check the value for "ocredit" in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep ocredit /etc/security/pwquality.conf 
+-ocredit=-1
+-
+-If the value of "ocredit" is not set to a negative value, this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>OL07-00-010160The Oracle Linux operating system must be configured so that when passwords are changed a minimum of eight of the total number of characters must be changed.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000195Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed by setting the "difok" option.
+-
+-Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+-
+-difok = 8The "difok" option sets the number of characters in a password that must not be present in the old password.
+-
+-Check for the value of the "difok" option in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep difok /etc/security/pwquality.conf 
+-difok = 8
+-
+-If the value of "difok" is set to less than "8", this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>OL07-00-010170The Oracle Linux operating system must be configured so that when passwords are changed a minimum of four character classes must be changed.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000195Configure the operating system to require the change of at least four character classes when passwords are changed by setting the "minclass" option.
+-
+-Add the following line to "/etc/security/pwquality.conf conf" (or modify the line to have the required value):
+-
+-minclass = 4The "minclass" option sets the minimum number of required classes of characters for the new password (digits, uppercase, lower-case, others).
+-
+-Check for the value of the "minclass" option in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep minclass /etc/security/pwquality.conf 
+-minclass = 4
+-
+-If the value of "minclass" is set to less than "4", this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>OL07-00-010180The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating consecutive characters must not be more than three characters.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one of several factors that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000195Configure the operating system to require the change of the number of repeating consecutive characters when passwords are changed by setting the "maxrepeat" option.
+-
+-Add the following line to "/etc/security/pwquality.conf conf" (or modify the line to have the required value):
+-
+-maxrepeat = 3The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password.
+-
+-Check for the value of the "maxrepeat" option in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep maxrepeat /etc/security/pwquality.conf 
+-maxrepeat = 3
+-
+-If the value of "maxrepeat" is set to more than "3", this is a finding.SRG-OS-000072-GPOS-00040<GroupDescription></GroupDescription>OL07-00-010190The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating characters of the same character class must not be more than four characters.<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+-
+-Password complexity is one of several factors that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000195Configure the operating system 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 the following line to "/etc/security/pwquality.conf" conf (or modify the line to have the required value):
+-
+-maxclassrepeat = 4The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password.
+-
+-Check for the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
+-
+-# grep maxclassrepeat /etc/security/pwquality.conf 
+-maxclassrepeat = 4
+-
+-If the value of "maxclassrepeat" is set to more than "4", this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>OL07-00-010200The Oracle Linux operating system must be configured so that the PAM system service is configured to store only encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000196Configure the operating system to store only SHA512 encrypted representations of passwords.
+-
+-Add the following line in "/etc/pam.d/system-auth":
+-pam_unix.so sha512 shadow try_first_pass use_authtok
+-
+-Add the following line in "/etc/pam.d/password-auth":
+-pam_unix.so sha512 shadow try_first_pass use_authtok
+-
+-Note: Manual changes to the listed files may be overwritten by the "authconfig" program. The "authconfig" program should not be used to update the configurations listed in this requirement.Verify the PAM system service is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
+-
+-Check that the system is configured to create SHA512 hashed passwords with the following command:
+-
+-# grep password /etc/pam.d/system-auth /etc/pam.d/password-auth
+-
+-Outcome should look like following:
+-/etc/pam.d/system-auth-ac:password sufficient pam_unix.so sha512 shadow try_first_pass use_authtok
+-/etc/pam.d/password-auth:password sufficient pam_unix.so sha512 shadow try_first_pass use_authtok
+-
+-If the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" configuration files allow for password hashes other than SHA512 to be used, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>OL07-00-010210The Oracle Linux operating system must be configured to use the shadow file to store only encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000196Configure the operating system to store only SHA512 encrypted representations of passwords.
+-
+-Add or update the following line in "/etc/login.defs":
+-
+-ENCRYPT_METHOD SHA512Verify the system's shadow file is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
+-
+-Check that the system is configured to create SHA512 hashed passwords with the following command:
+-
+-# grep -i encrypt /etc/login.defs
+-ENCRYPT_METHOD SHA512
+-
+-If the "/etc/login.defs" configuration file does not exist or allows for password hashes other than SHA512 to be used, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>OL07-00-010220The Oracle Linux operating system must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000196Configure the operating system to store only SHA512 encrypted representations of passwords.
+-
+-Add or update the following line in "/etc/libuser.conf" in the [defaults] section: 
+-
+-crypt_style = sha512Verify the user and group account administration utilities are configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is "SHA512".
+-
+-Check that the system is configured to create "SHA512" hashed passwords with the following command:
+-
+-# grep -i sha512 /etc/libuser.conf 
+-
+-crypt_style = sha512
+-
+-If the "crypt_style" variable is not set to "sha512", is not in the defaults section, is commented out, or does not exist, this is a finding.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>OL07-00-010230The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 24 hours/1 day minimum lifetime.<VulnDiscussion>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000198Configure the operating system 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 1Verify 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: 
+-
+-# 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.SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>OL07-00-010240The Oracle Linux operating system must be configured so that passwords are restricted to a 24 hours/1 day minimum lifetime.<VulnDiscussion>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000198Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime:
+-
+-# chage -m 1 [user]Check whether the minimum time period between password changes for each user account is one day or greater.
+-
+-# 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.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>OL07-00-010250The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 60-day maximum lifetime.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000199Configure the operating system to enforce a 60-day maximum password lifetime restriction.
+-
+-Add the following line in "/etc/login.defs" (or modify the line to have the required value):
+-
+-PASS_MAX_DAYS 60If passwords are not being used for authentication, this is Not Applicable.
+-
+-Verify the operating system enforces a 60-day maximum password lifetime restriction for new user accounts.
+-
+-Check for the value of "PASS_MAX_DAYS" in "/etc/login.defs" with the following command:
+-
+-# grep -i pass_max_days /etc/login.defs
+-PASS_MAX_DAYS 60
+-
+-If the "PASS_MAX_DAYS" parameter value is not 60 or less, or is commented out, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>OL07-00-010260The Oracle Linux operating system must be configured so that existing passwords are restricted to a 60-day maximum lifetime.<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000199Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction.
+-
+-# chage -M 60 [user]Check whether the maximum time period for existing passwords is restricted to 60 days.
+-
+-# awk -F: '$5 > 60 {print $1 " " $5}' /etc/shadow
+-
+-If any results are returned that are not associated with a system account, this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>OL07-00-010270The Oracle Linux operating system must be configured so that passwords are prohibited from reuse for a minimum of five generations.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000200Configure the operating system to prohibit password reuse for a minimum of five generations.
+-
+-Add the following line in "/etc/pam.d/system-auth" and "/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
+-
+-Note: Manual changes to the listed files may be overwritten by the "authconfig" program. The "authconfig" program should not be used to update the configurations listed in this requirement.Verify the operating system prohibits password reuse for a minimum of five generations.
+-
+-Check for the value of the "remember" argument in "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" with the following command:
+-
+-# grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth
+-
+-password requisite pam_pwhistory.so use_authtok remember=5 retry=3
+-
+-If the line containing the "pam_pwhistory.so" line 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.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>OL07-00-010280The Oracle Linux operating system must be configured so that passwords are a minimum of 15 characters in length.<VulnDiscussion>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
+-
+-Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to increase exponentially the time and/or resources required to compromise the password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000205Configure operating system to enforce a minimum 15-character password length.
+-
+-Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+-
+-minlen = 15Verify 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" with the following command:
+-
+-# grep minlen /etc/security/pwquality.conf
+-minlen = 15
+-
+-If the command does not return a "minlen" value of 15 or greater, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-010290The Oracle Linux operating system must not have accounts configured with blank or null passwords.<VulnDiscussion>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating.
+-
+-Remove any instances of the "nullok" option in "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" to prevent logons with empty passwords.
+-
+-Note: Manual changes to the listed files may be overwritten by the "authconfig" program. The "authconfig" program should not be used to update the configurations listed in this requirement.To verify that null passwords cannot be used, run the following command: 
+-
+-# grep nullok /etc/pam.d/system-auth /etc/pam.d/password-auth
+-
+-If this produces any output, it may be possible to log on with accounts with empty passwords.
+-
+-If null passwords can be used, this is a finding.SRG-OS-000106-GPOS-00053<GroupDescription></GroupDescription>OL07-00-010300The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password.<VulnDiscussion>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000766To explicitly disallow remote logon from accounts with empty passwords, add or correct the following line in "/etc/ssh/sshd_config":
+-
+-PermitEmptyPasswords no
+-
+-The SSH service must be restarted for changes to take effect. Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords.To determine how the SSH daemon's "PermitEmptyPasswords" option is set, run the following command:
+-
+-# grep -i PermitEmptyPasswords /etc/ssh/sshd_config
+-PermitEmptyPasswords no
+-
+-If no line, a commented line, or a line indicating the value "no" is returned, the required value is set.
+-
+-If the required value is not set, this is a finding.SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>OL07-00-010310The Oracle Linux operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires.<VulnDiscussion>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
+-
+-Operating systems need to track periods of inactivity and disable application identifiers after zero days of inactivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000795Configure the operating system to disable account identifiers (individuals, groups, roles, and devices) after the password expires.
+-
+-Add the following line to "/etc/default/useradd" (or modify the line to have the required value):
+-
+-INACTIVE=0If passwords are not being used for authentication, this is Not Applicable.
+-
+-Verify the operating system disables account identifiers (individuals, groups, roles, and devices) after the password expires with the following command:
+-
+-# grep -i inactive /etc/default/useradd
+-INACTIVE=0
+-
+-If the value is not set to "0", is commented out, or is not defined, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>OL07-00-010320Accounts on the Oracle Linux operating system subjected to three unsuccessful logon attempts within 15 minutes must be locked for the maximum configurable period.<VulnDiscussion>By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as “brute-forcing”, is reduced. Limits are imposed by locking the account.
+-
+-Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000044CCI-002238Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made.
+-
+-Modify the first three lines of the auth section and the first line of the account section 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 silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-auth sufficient pam_unix.so try_first_pass
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-account required pam_faillock.so 
+-
+-Note: Manual changes to the listed files may be overwritten by the "authconfig" program. The "authconfig" program should not be used to update the configurations listed in this requirement.Verify the operating system automatically locks an account for the maximum period for which the system can be configured.
+-
+-Check that the system locks an account for the maximum period after three unsuccessful logon attempts within a period of 15 minutes, using the following command:
+-
+-# grep pam_faillock.so /etc/pam.d/password-auth
+-auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-account required pam_faillock.so 
+-
+-If the "unlock_time" parameter is not set to "0", "never", or is set to a value less than "900" on both "auth" lines with the "pam_faillock.so" module, or is missing from these lines, this is a finding.
+-
+-Note: The maximum configurable value for "unlock_time" is "604800". 
+-
+-If any line referencing the "pam_faillock.so" module is commented out, this is a finding.
+-# grep pam_faillock.so /etc/pam.d/system-auth
+-auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-account required pam_faillock.so 
+-
+-If the "unlock_time" parameter is not set to "0", "never", or is set to a value less than "900" on both "auth" lines with the "pam_faillock.so" module or is missing from these lines, this is a finding.
+-Note: The maximum configurable value for "unlock_time" is "604800".
+-
+-If any line referencing the "pam_faillock.so" module is commented out, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>OL07-00-010330The Oracle Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period.<VulnDiscussion>By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.
+-
+-Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002238Configure the operating system to lock automatically the root account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
+-
+-Modify the first three lines of the auth section and the first line of the account section 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 silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-auth sufficient pam_unix.so try_first_pass
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-account required pam_faillock.so
+-
+-Note: Manual changes to the listed files may be overwritten by the "authconfig" program. The "authconfig" program should not be used to update the configurations listed in this requirement.Verify the operating system automatically locks the root account until it is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
+-
+-# grep pam_faillock.so /etc/pam.d/password-auth
+-auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900 
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900 
+-account required pam_faillock.so
+-
+-If the "even_deny_root" setting is not defined on both lines with the "pam_faillock.so" module, is commented out, or is missing from a line, this is a finding.
+-
+-# grep pam_faillock.so /etc/pam.d/system-auth
+-auth required pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=900 
+-auth [default=die] pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=900
+-account required pam_faillock.so
+-
+-If the "even_deny_root" setting is not defined on both lines with the "pam_faillock.so" module, is commented out, or is missing from a line, this is a finding.SRG-OS-000373-GPOS-00156<GroupDescription></GroupDescription>OL07-00-010340The Oracle Linux operating system must be configured so that users must provide a password for privilege escalation.<VulnDiscussion>Without reauthentication, users may access resources or perform tasks for which authorization has not been granted. 
+-
+-When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.
+-
+-Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002038Configure 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:
+-# visudo
+-
+-Remove any occurrences of "NOPASSWD" tags in the file.
+-
+-Check the configuration of the /etc/sudoers.d/* files with the following command:
+-# grep -i nopasswd /etc/sudoers.d/*
+-
+-Remove any occurrences of "NOPASSWD" tags in the file.If passwords are not being used for authentication, this is Not Applicable.
+-
+-Verify the operating system requires users to supply a password for privilege escalation.
+-
+-Check the configuration of the "/etc/sudoers" and "/etc/sudoers.d/*" files with the following command:
+-
+-# grep -i nopasswd /etc/sudoers /etc/sudoers.d/*
+-
+-If any uncommented line is found with a "NOPASSWD" tag, this is a finding.SRG-OS-000480-GPOS-00226<GroupDescription></GroupDescription>OL07-00-010430The Oracle Linux operating system must be configured so that the delay between logon prompts following a failed console logon attempt is at least four seconds.<VulnDiscussion>Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+-
+-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example, registry settings; account, file, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system 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 4Verify the operating system enforces a delay of at least four seconds between console logon prompts following a failed logon attempt.
+-
+-Check the value of the "fail_delay" parameter in the "/etc/login.defs" file with the following command:
+-
+-# 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.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>OL07-00-010440The Oracle Linux operating system must not allow an unattended or automatic logon to the system via a graphical user interface.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system not to allow an unattended or automatic logon to the system via a graphical user interface.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+-
+-Add or edit the line for the "AutomaticLoginEnable" parameter in the [daemon] section of the "/etc/gdm/custom.conf" file to "false":
+-
+-[daemon]
+-AutomaticLoginEnable=falseVerify the operating system does not allow an unattended or automatic logon to the system via a graphical user interface.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+-
+-Check for the value of the "AutomaticLoginEnable" in the "/etc/gdm/custom.conf" file with the following command:
+-
+-# grep -i automaticloginenable /etc/gdm/custom.conf
+-AutomaticLoginEnable=false
+-
+-If the value of "AutomaticLoginEnable" is not set to "false", this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>OL07-00-010450The Oracle Linux operating system must not allow an unrestricted logon to the system.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system not to allow an unrestricted account to log on to the system via a graphical user interface.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+-
+-Add or edit the line for the "TimedLoginEnable" parameter in the [daemon] section of the "/etc/gdm/custom.conf" file to "false":
+-
+-[daemon]
+-TimedLoginEnable=falseVerify the operating system does not allow an unrestricted logon to the system via a graphical user interface.
+-
+-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+-
+-Check for the value of the "TimedLoginEnable" parameter in "/etc/gdm/custom.conf" file with the following command:
+-
+-# grep -i timedloginenable /etc/gdm/custom.conf
+-TimedLoginEnable=false
+-
+-If the value of "TimedLoginEnable" is not set to "false", this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>OL07-00-010460The Oracle Linux operating system must not allow users to override SSH environment variables.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system not to allow users to override environment variables to the SSH daemon.
+-
+-Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for "PermitUserEnvironment" keyword and set the value to "no":
+-
+-PermitUserEnvironment no
+-
+-The SSH service must be restarted for changes to take effect.Verify the operating system does not allow users to override environment variables to the SSH daemon.
+-
+-Check for the value of the "PermitUserEnvironment" keyword with the following command:
+-
+-# grep -i permituserenvironment /etc/ssh/sshd_config
+-PermitUserEnvironment no
+-
+-If the "PermitUserEnvironment" keyword is not set to "no", is missing, or is commented out, this is a finding.SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>OL07-00-010470The Oracle Linux operating system must not allow a non-certificate trusted host SSH logon to the system.<VulnDiscussion>Failure to restrict system access to authenticated users negatively impacts operating system security.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system not to allow a non-certificate trusted host SSH logon to the system.
+-
+-Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for "HostbasedAuthentication" keyword and set the value to "no":
+-
+-HostbasedAuthentication no
+-
+-The SSH service must be restarted for changes to take effect.Verify the operating system does not allow a non-certificate trusted host SSH logon to the system.
+-
+-Check for the value of the "HostbasedAuthentication" keyword with the following command:
+-
+-# grep -i hostbasedauthentication /etc/ssh/sshd_config
+-HostbasedAuthentication no
+-
+-If the "HostbasedAuthentication" keyword is not set to "no", is missing, or is commented out, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>OL07-00-010480Oracle Linux operating systems prior to version 7.2 with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for Oracle Linux 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000213Configure the system to encrypt the boot password for root.
+-
+-Generate an encrypted grub2 password for root with the following command:
+-
+-Note: The hash generated is an example.
+-
+-# grub2-mkpasswd-pbkdf2
+-
+-Enter Password:
+-Reenter Password:
+-PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+-
+-Edit "/etc/grub.d/40_custom" and add the following lines below the comments:
+-
+-# vi /etc/grub.d/40_custom
+-
+-set superusers="root"
+-
+-password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}
+-
+-Generate a new "grub.conf" file with the new password with the following commands:
+-
+-# grub2-mkconfig --output=/tmp/grub2.cfg
+-# mv /tmp/grub2.cfg /boot/grub2/grub.cfgFor systems that use UEFI, this is Not Applicable.
+-For systems that are running Oracle Linux 7.2 or newer, this is Not Applicable.
+-
+-Check to see if an encrypted root password is set. On systems that use a BIOS, use the following command:
+-
+-# grep -i ^password_pbkdf2 /boot/grub2/grub.cfg
+-
+-password_pbkdf2 [superusers-account] [password-hash]
+-
+-If the root password entry does not begin with "password_pbkdf2", this is a finding.
+-
+-If the "superusers-account" is not set to "root", this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>OL07-00-010481The Oracle Linux operating system must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000213Configure the operating system to require authentication upon booting into single-user and maintenance modes.
+-
+-Add or modify the "ExecStart" line in "/usr/lib/systemd/system/rescue.service" to include "/usr/sbin/sulogin":
+-
+-ExecStart=-/bin/sh -c "/usr/sbin/sulogin; /usr/bin/systemctl --fail --no-block default"Verify the operating system must require authentication upon booting into single-user and maintenance modes.
+-
+-Check that the operating system requires authentication upon booting into single-user mode with the following command:
+-
+-# grep -i execstart /usr/lib/systemd/system/rescue.service | grep -i sulogin
+-
+-ExecStart=-/bin/sh -c "/usr/sbin/sulogin; /usr/bin/systemctl --fail --no-block default"
+-
+-If "ExecStart" does not have "/usr/sbin/sulogin" as an option, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>OL07-00-010482Oracle Linux operating systems version 7.2 or newer with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for Oracle Linux 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000213Configure the system to encrypt the boot password for root.
+-
+-Generate an encrypted grub2 password for root with the following command:
+-
+-Note: The hash generated is an example.
+-
+-# grub2-setpassword
+-Enter password:
+-Confirm password:
+-
+-Edit the /boot/grub2/grub.cfg file and add or modify the following lines in the "### BEGIN /etc/grub.d/01_users ###" section:
+-
+-set superusers="root"
+-export superusersFor systems that use BIOS, this is Not Applicable.
+-
+-For systems that are running a version of Oracle Linux prior to 7.2, this is Not Applicable.
+-
+-Check to see if an encrypted root password is set. On systems that use UEFI, use the following command:
+-
+-# grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg
+-GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]
+-
+-If the root password does not begin with "grub.pbkdf2.sha512", this is a finding.
+-
+-Verify that the "root" account is set as the "superusers":
+-
+-# grep -iw "superusers" /boot/efi/EFI/redhat/grub.cfg
+-set superusers="root"
+-export superusers
+-
+-If "superusers" is not set to "root" this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>OL07-00-010490Oracle Linux operating systems prior to version 7.2 using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for Oracle Linux 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000213Configure the system to encrypt the boot password for root.
+-
+-Generate an encrypted grub2 password for root with the following command:
+-
+-Note: The hash generated is an example.
+-
+-# grub2-mkpasswd-pbkdf2
+-
+-Enter Password:
+-Reenter Password:
+-PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+-
+-Edit "/etc/grub.d/40_custom" and add the following lines below the comments:
+-
+-# vi /etc/grub.d/40_custom
+-
+-set superusers="root"
+-
+-password_pbkdf2 root {hash from grub2-mkpasswd-pbkdf2 command}
+-
+-Generate a new "grub.conf" file with the new password with the following commands:
+-
+-# grub2-mkconfig --output=/tmp/grub2.cfg
+-# mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfgFor systems that use BIOS, this is Not Applicable.
+-For systems that are running Oracle Linux 7.2 or newer, this is Not Applicable.
+-
+-Check to see if an encrypted root password is set. On systems that use UEFI, use the following command:
+-
+-# grep -i password /boot/efi/EFI/redhat/grub.cfg
+-
+-password_pbkdf2 [superusers-account] [password-hash]
+-
+-If the root password entry does not begin with "password_pbkdf2", this is a finding.
+-
+-If the "superusers-account" is not set to "root", this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>OL07-00-010491Oracle Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes.<VulnDiscussion>If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for Oracle Linux 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000213Configure the system to encrypt the boot password for root.
+-
+-Generate an encrypted grub2 password for root with the following command:
+-
+-Note: The hash generated is an example.
+-
+-# grub2-setpassword
+-Enter password:
+-Confirm password:
+-
+-Edit the /boot/efi/EFI/redhat/grub.cfg file and add or modify the following lines in the "### BEGIN /etc/grub.d/01_users ###" section:
+-
+-set superusers="root"
+-export superusersFor systems that use BIOS, this is Not Applicable.
+-
+-For systems that are running a version of RHEL prior to 7.2, this is Not Applicable.
+-
+-Check to see if an encrypted root password is set. On systems that use UEFI, use the following command:
+-
+-# grep -iw grub2_password /boot/efi/EFI/redhat/user.cfg
+-GRUB2_PASSWORD=grub.pbkdf2.sha512.[password_hash]
+-
+-If the root password does not begin with "grub.pbkdf2.sha512", this is a finding.
+-
+-Verify that the "root" account is set as the "superusers":
+-
+-# grep -iw "superusers" /boot/efi/EFI/redhat/grub.cfg
+-set superusers="root"
+-export superusers
+-
+-If "superusers" is not set to "root" this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>OL07-00-010500The Oracle Linux operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multifactor authentication.<VulnDiscussion>To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
+-
+-Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following:
+-
+-1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; 
+-
+-and
+-
+-2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.
+-
+-Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000109-GPOS-00056, SRG-OS-000108-GPOS-00055, SRG-OS-000108-GPOS-00057, SRG-OS-000108-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000764CCI-000767CCI-000768CCI-000770Configure the operating system to require individuals to be authenticated with a multifactor authenticator.
+-
+-Enable smartcard logons with the following commands:
+-
+-# authconfig --enablesmartcard --smartcardaction=0 --update
+-# authconfig --enablerequiresmartcard -update
+-
+-Modify the "/etc/pam_pkcs11/pkcs11_eventmgr.conf" file to uncomment the following line:
+-
+-#/usr/X11R6/bin/xscreensaver-command -lock
+-
+-Modify the "/etc/pam_pkcs11/pam_pkcs11.conf" file to use the cackey module if required.Verify the operating system requires multifactor authentication to uniquely identify organizational users using multifactor authentication.
+-
+-Check to see if smartcard authentication is enforced on the system:
+-
+-# authconfig --test | grep "pam_pkcs11 is enabled"
+-
+-If no results are returned, this is a finding.
+-
+-# authconfig --test | grep "smartcard removal action"
+-
+-If "smartcard removal action" is blank, this is a finding.
+-
+-# authconfig --test | grep "smartcard module"
+-
+-If "smartcard module" is blank, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>OL07-00-020000The Oracle Linux operating system must not have the rsh-server package installed.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked, and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+-
+-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+-
+-The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.
+-
+-If a privileged user were to log on using this service, the privileged user password could be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000381Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:
+-
+-# yum remove rsh-serverCheck to see if the rsh-server package is installed with the following command:
+-
+-# yum list installed rsh-server
+-
+-If the rsh-server package is installed, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>OL07-00-020010The Oracle Linux operating system must not have the ypserv package installed.<VulnDiscussion>Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000381Configure the operating system to disable non-essential capabilities by removing the "ypserv" package from the system with the following command:
+-
+-# yum remove ypservThe NIS service provides an unencrypted authentication service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+-
+-Check to see if the "ypserve" package is installed with the following command:
+-
+-# yum list installed ypserv
+-
+-If the "ypserv" package is installed, this is a finding.SRG-OS-000191-GPOS-00080<GroupDescription></GroupDescription>OL07-00-020019The Oracle Linux operating system must have a host-based intrusion detection tool installed.<VulnDiscussion>Adding host-based intrusion detection tools can provide the capability to take actions automatically in response to malicious behavior, which can provide additional agility in reacting to network threats. These tools often include a reporting capability to provide network awareness of the system, which may not otherwise exist in an organization's systems management regime.
+-
+-Satisfies: SRG-OS-000191-GPOS-00080, SRG-OS-000196</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001233Install and enable the latest McAfee HIPS package, available from USCYBERCOM.
+-
+-Note: If the system does not support the McAfee HIPS package, install and enable a supported intrusion detection system application and document its use with the Authorizing Official.Consult with the SA or ISSO to determine if a host-based intrusion detection application is loaded on the system. Per OPORD 16-0080, the preferred intrusion detection system is McAfee HBSS available through the U.S. Cyber Command (USCYBERCOM).
+-
+-If another host-based intrusion detection application is in use, such as SELinux, this must be documented and approved by the local Authorizing Official.
+-
+-Procedure:
+-Examine the system to determine if the Host Intrusion Prevention System (HIPS) is installed:
+-
+-# rpm -qa | grep MFEhiplsm
+-
+-Verify the McAfee HIPS module is active on the system:
+-
+-# ps -ef | grep -i "hipclient" 
+-
+-If the MFEhiplsm package is not installed, check for another intrusion detection system:
+-
+-# find / -name <daemon name>
+-
+-Where <daemon name> is the name of the primary application daemon to determine if the application is loaded on the system.
+-
+-Determine if the application is active on the system:
+-
+-# ps -ef | grep -i <daemon name>
+-
+-If the MFEhiplsm package is not installed and an alternate host-based intrusion detection application has not been documented for use, this is a finding.
+-
+-If no host-based intrusion detection system is installed and running on the system, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>OL07-00-020020The Oracle Linux operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.<VulnDiscussion>Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+-
+-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002235Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
+-
+-Use the following command to map a new user to the "sysdam_u" role: 
+-
+-#semanage login -a -s sysadm_u <username>
+-
+-Use the following command to map an existing user to the "sysdam_u" role:
+-
+-#semanage login -m -s sysadm_u <username>
+-
+-Use the following command to map a new user to the "staff_u" role:
+-
+-#semanage login -a -s staff_u <username>
+-
+-Use the following command to map an existing user to the "staff_u" role:
+-
+-#semanage login -m -s staff_u <username>
+-
+-Use the following command to map a new user to the "user_u" role:
+-
+-# semanage login -a -s user_u <username>
+-
+-Use the following command to map an existing user to the "user_u" role:
+-
+-# semanage login -m -s user_u <username>If an HBSS or HIPS is active on the system, this is Not Applicable.
+-
+-Verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
+-
+-Get 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:
+-
+-# 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" or "staff_u" users role.
+-
+-All authorized non-administrative users must be mapped to the "user_u" role.
+-
+-If they are not mapped in this way, this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>OL07-00-020030The Oracle Linux operating system must be configured so that a file integrity tool verifies the baseline operating system configuration at least weekly.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security.
+-
+-Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.
+-
+-Satisfies: SRG-OS-000363-GPOS-00150 and SRG-OS-000446-GPOS-00200</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001744CCI-002699Configure the file integrity tool to run automatically on the system at least weekly. The following example output is generic. It will set cron to run AIDE daily, but other file integrity tools may be used: 
+-
+-# more /etc/cron.daily/aide
+-#!/bin/bash
+-
+-/usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.milVerify the operating system routinely checks the baseline configuration for unauthorized changes.
+-
+-Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed at least once per week.
+-
+-Check to see if AIDE is installed on the system with the following command:
+-
+-# yum list installed aide
+-
+-If AIDE is not installed, ask the SA how file integrity checks are performed on the system.
+-
+-Check for the presence of a cron job running daily or weekly on the system that executes AIDE daily to scan for changes to the system baseline. The command used in the example will use a daily occurrence.
+-
+-Check the cron directories for a script file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command:
+-
+-# ls -al /etc/cron.* | grep aide
+--rwxr-xr-x 1 root root 29 Nov 22 2015 aide
+-
+-# grep aide /etc/crontab /var/spool/cron/root
+-/etc/crontab: 30 04 * * * /root/aide
+-/var/spool/cron/root: 30 04 * * * /root/aide
+-
+-If the file integrity application does not exist, or a script file controlling the execution of the file integrity application does not exist, this is a finding.SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>OL07-00-020040The Oracle Linux operating system must be configured so that designated personnel are notified if baseline configurations are changed in an unauthorized manner.<VulnDiscussion>Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security.
+-
+-Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001744Configure the operating system 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 email at the completion of the analysis. 
+-
+-# more /etc/cron.daily/aide
+-
+-/usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.milVerify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner.
+-
+-Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed and notify specified individuals via email or an alert.
+-
+-Check to see if AIDE is installed on the system with the following command:
+-
+-# yum list installed aide
+-
+-If AIDE is not installed, ask the SA how file integrity checks are performed on the system. 
+-
+-Check for the presence of a cron job running routinely on the system that executes AIDE to scan for changes to the system baseline. The commands used in the example will use a daily occurrence.
+-
+-Check the cron directories for a "crontab" script file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command:
+-
+-# ls -al /etc/cron.* | grep aide
+--rwxr-xr-x 1 root root 32 Jul 1 2011 aide
+-
+-# grep aide /etc/crontab /var/spool/cron/root
+-/etc/crontab: 30 04 * * * /root/aide
+-/var/spool/cron/root: 30 04 * * * /root/aide
+-
+-AIDE does not have a configuration that will send a notification, so the cron job uses the mail application on the system to email the results of the file integrity run as in the following example:
+-
+-# more /etc/cron.daily/aide
+-#!/bin/bash
+-
+-/usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil
+-
+-If the file integrity application does not notify designated personnel of changes, this is a finding.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>OL07-00-020050The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.<VulnDiscussion>Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
+-
+-Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
+-
+-Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001749Configure the operating system to verify the signature of packages from a repository prior to install by setting the following option in the "/etc/yum.conf" file:
+-
+-gpgcheck=1Verify 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 that yum verifies the signature of packages from a repository prior to install with the following command:
+-
+-# grep gpgcheck /etc/yum.conf
+-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.SRG-OS-000366-GPOS-00153<GroupDescription></GroupDescription>OL07-00-020060The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.<VulnDiscussion>Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
+-
+-Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
+-
+-Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001749Configure the operating system to verify the signature of local packages prior to install by setting the following option in the "/etc/yum.conf" file:
+-
+-localpkg_gpgcheck=1Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification that they have been digitally signed using a certificate that is recognized and approved by the organization.
+-
+-Check that yum verifies the signature of local packages prior to install with the following command:
+-
+-# grep localpkg_gpgcheck /etc/yum.conf
+-localpkg_gpgcheck=1
+-
+-If "localpkg_gpgcheck" is not set to "1", or if options are missing or commented out, ask the System Administrator how the signatures of local packages and other operating system components are verified. 
+-
+-If there is no process to validate the signatures of local packages that is approved by the organization, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>OL07-00-020100The Oracle Linux operating system must be configured to disable USB mass storage.<VulnDiscussion>USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
+-
+-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000778Configure the operating system to disable the ability to use USB mass storage devices.
+-
+-# vi /etc/modprobe.d/blacklist.conf
+-
+-Add or update the line:
+-
+-blacklist usb-storageIf there is an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this requirement is not applicable.
+-
+-Verify the operating system disables the ability to use USB mass storage devices.
+-
+-Check to see if USB mass storage is disabled with the following command:
+-
+-# grep usb-storage /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 Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000378-GPOS-000163<GroupDescription></GroupDescription>OL07-00-020101The Oracle Linux operating system must be configured so that the Datagram Congestion Control Protocol (DCCP) kernel module is disabled unless required.<VulnDiscussion>Disabling DCCP protects the system against exploitation of any flaws in the protocol implementation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001958Configure the operating system to disable the ability to use the DCCP kernel module.
+-
+-Create a file under "/etc/modprobe.d" with the following command:
+-
+-# touch /etc/modprobe.d/dccp.conf
+-
+-Add the following line to the created file:
+-
+-install dccp /bin/true
+-
+-Ensure that the DCCP module is blacklisted: 
+-
+-# vi /etc/modprobe.d/blacklist.conf
+-
+-Add or update the line:
+-
+-blacklist dccpVerify the operating system disables the ability to load the DCCP kernel module.
+-
+-# grep -r dccp /etc/modprobe.d/* | grep -i "/bin/true" | grep -v "^#"
+-
+-install dccp /bin/true
+-
+-If the command does not return any output, or the line is commented out, and use of DCCP is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000114-GPOS-00059<GroupDescription></GroupDescription>OL07-00-020110The Oracle Linux operating system must disable the file system automounter unless required.<VulnDiscussion>Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
+-
+-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000778Configure the operating system to disable the ability to automount devices.
+-
+-Turn off the automount service with the following commands:
+-
+-# systemctl stop autofs
+-# systemctl disable autofs
+-
+-If "autofs" is required for Network File System (NFS), it must be documented with the ISSO.Verify the operating system disables the ability to automount devices.
+-
+-Check to see if automounter service is active with the following command:
+-
+-# 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.SRG-OS-000437-GPOS-00194<GroupDescription></GroupDescription>OL07-00-020200The Oracle Linux operating system must remove all software components after updated versions have been installed.<VulnDiscussion>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002617Configure the operating system to remove all software components after updated versions have been installed.
+-
+-Set the "clean_requirements_on_remove" option to "1" in the "/etc/yum.conf" file:
+-
+-clean_requirements_on_remove=1Verify 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:
+-
+-# grep -i clean_requirements_on_remove /etc/yum.conf
+-clean_requirements_on_remove=1
+-
+-If "clean_requirements_on_remove" is not set to "1", "True", or "yes", or is not set in "/etc/yum.conf", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020230The Oracle Linux operating system must be configured so that the x86 Ctrl-Alt-Delete key sequence is disabled.<VulnDiscussion>A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the GNOME graphical environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the system to disable the Ctrl-Alt_Delete sequence for the command line with the following command:
+-
+-# systemctl mask ctrl-alt-del.target
+-
+-If GNOME is active on the system, create a database to contain the system-wide setting (if it does not already exist) with the following command: 
+-
+-# touch /etc/dconf/db/local.d/00-disable-CAD 
+-
+-Add the setting to disable the Ctrl-Alt_Delete sequence for GNOME:
+-
+-[org/gnome/settings-daemon/plugins/media-keys]
+-logout=''Verify the operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed.
+-
+-Check that the ctrl-alt-del.target is masked and not active with the following command:
+-
+-# systemctl status ctrl-alt-del.target
+-
+-ctrl-alt-del.target
+-Loaded: masked (/dev/null; bad)
+-Active: inactive (dead)
+-
+-If the ctrl-alt-del.target is not masked, this is a finding.
+-
+-If the ctrl-alt-del.target is active, this is a finding.SRG-OS-000480-GPOS-00228<GroupDescription></GroupDescription>OL07-00-020240The Oracle Linux operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.<VulnDiscussion>Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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 line for the "UMASK" parameter in "/etc/login.defs" file to "077":
+-
+-UMASK 077Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files.
+-
+-Check for the value of the "UMASK" parameter in "/etc/login.defs" file with the following command:
+-
+-Note: If the value of the "UMASK" parameter is set to "000" in "/etc/login.defs" file, the Severity is raised to a CAT I.
+-
+-# grep -i umask /etc/login.defs
+-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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020250The Oracle Linux operating system must be a vendor supported release.<VulnDiscussion>An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Upgrade to a supported version of the operating system.Verify the version of the operating system is vendor supported.
+-
+-Check the version of the operating system with the following command:
+-
+-# cat /etc/oracle-release
+-
+-Oracle Linux Server release 7.6
+-
+-Current End of Premier Support for Oracle Linux 7 is Jul 2024 while Extended Support might consider extended term.
+-
+-If the release is not supported by the vendor, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020260The Oracle Linux operating system security patches and updates must be installed and up to date.<VulnDiscussion>Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced System Administrators to keep abreast of all the new patches. When new weaknesses in an operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Install the operating system patches or updated packages available from Oracle within 30 days or sooner as local policy dictates.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:
+-
+-# yum history list | more
+-Loaded plugins: langpacks, product-id, subscription-manager
+-ID | Command line | Date and time | Action(s) | Altered
+--------------------------------------------------------------------------------
+-70 | install aide | 2016-05-05 10:58 | Install | 1 
+-69 | update -y | 2016-05-04 14:34 | Update | 18 EE
+-68 | install vlc | 2016-04-21 17:12 | Install | 21 
+-67 | update -y | 2016-04-21 17:04 | Update | 7 EE
+-66 | update -y | 2016-04-15 16:47 | E, I, U | 84 EE
+-
+-If package updates have not been performed on the system within the timeframe required by the site/program documentation, this is a finding. 
+-
+-Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM.
+-
+-If the operating system is in non-compliance with the Information Assurance Vulnerability Management (IAVM) process, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020270The Oracle Linux operating system must not have unnecessary accounts.<VulnDiscussion>Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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.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:
+-
+-# 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.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>OL07-00-020300The Oracle Linux operating system must be configured so that all Group Identifiers (GIDs) referenced in the /etc/passwd file are defined in the /etc/group file.<VulnDiscussion>If a user is assigned the GID of a group not existing on the system, and a group with the GID is subsequently created, the user may have unintended rights to any files associated with the group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000764Configure the system to define all GIDs found in the "/etc/passwd" file by modifying the "/etc/group" file to add any non-existent group referenced in the "/etc/passwd" file, or change the GIDs referenced in the "/etc/passwd" file to a group that exists in "/etc/group".Verify all GIDs referenced in the "/etc/passwd" file are defined in the "/etc/group" file.
+-
+-Check that all referenced GIDs exist with the following command:
+-
+-# pwck -r
+-
+-If GIDs referenced in then "/etc/passwd" file are returned as not defined in the "/etc/group" file, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020310The Oracle Linux operating system must be configured so that the root account must be the only account having unrestricted access to the system.<VulnDiscussion>If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change 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, the UID should be changed to one greater than "0" but less than "1000". Otherwise, assign a UID of greater than "1000" that has not already been assigned.Check the system for duplicate UID "0" assignments with the following command:
+-
+-# awk -F: '$3 == 0 {print $1}' /etc/passwd
+-
+-If any accounts other than root have a UID of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020320The Oracle Linux operating system must be configured so that all files and directories have a valid owner.<VulnDiscussion>Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier (UID) as the UID of the un-owned files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Either 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 the system with the "chown" command:
+-
+-# chown <user> <file>Verify all files and directories on the system have a valid owner.
+-
+-Check the owner of all files and directories with the following command:
+-
+-Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+-
+-# find / -fstype xfs -nouser
+-
+-If any files on the system do not have an assigned owner, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020330The Oracle Linux operating system must be configured so that all files and directories have a valid group owner.<VulnDiscussion>Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Either remove all files and directories from the system that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command:
+-
+-# chgrp <group> <file>Verify all files and directories on the system have a valid group.
+-
+-Check the owner of all files and directories with the following command:
+-
+-Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+-
+-# find / -fstype xfs -nogroup
+-
+-If any files on the system do not have an assigned group, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020600The Oracle Linux operating system must be configured so that all local interactive users have a home directory assigned in the /etc/passwd file.<VulnDiscussion> If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Assign home directories to all local interactive users that currently do not have a home directory assigned.Verify local interactive users on the system have a home directory assigned.
+-
+-Check for missing local interactive user home directories with the following command:
+-
+-# 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 'smithj': directory '/home/smithj' 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:
+-
+-# cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
+-
+-If any interactive users do not have a home directory assigned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020610The Oracle Linux operating system must be configured so that all local interactive user accounts, upon creation, are assigned a home directory.<VulnDiscussion>If local interactive users are not assigned a valid home directory, there is no place for the storage and control of owned files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system to assign home directories to all new local interactive users by setting the "CREATE_HOME" parameter in "/etc/login.defs" to "yes" as follows.
+-
+-CREATE_HOME yesVerify all local interactive users on the system are assigned a home directory upon creation.
+-
+-Check to see if the system is configured to create home directories for local interactive users with the following command:
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020620The Oracle Linux operating system must be configured so that all local interactive user home directories are defined in the /etc/passwd file.<VulnDiscussion>If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a denial of service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Create 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".
+-
+-# mkdir /home/smithj 
+-# chown smithj /home/smithj
+-# chgrp users /home/smithj
+-# chmod 0750 /home/smithjVerify the assigned home directory of all local interactive users on the system exists.
+-
+-Check the home directory assignment for all local interactive non-privileged users on the system with the following command:
+-
+-# cut -d: -f 1,3,6 /etc/passwd | egrep ":[1-4][0-9]{3}"
+-
+-smithj:1001:/home/smithj
+-
+-Note: This may miss interactive users that have been assigned a privileged 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:
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020630The Oracle Linux operating system must be configured so that all local interactive user home directories have mode 0750 or less permissive.<VulnDiscussion>Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the mode of interactive user's home directories to "0750". To change the mode of a local interactive user's home directory, use the following command:
+-
+-Note: The example will be for the user "smithj".
+-
+-# chmod 0750 /home/smithjVerify the assigned home directory of all local interactive users has a mode of "0750" or less permissive.
+-
+-Check the home directory assignment for all non-privileged users on the system 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.
+-
+-# ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+--rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj
+-
+-If home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020640The Oracle Linux operating system must be configured so that all local interactive user home directories are owned by their respective users.<VulnDiscussion>If a local interactive user does not own their home directory, unauthorized users could access or modify the user's files, and the users may not be able to access their own files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the owner of a local interactive user's home directories to that owner. To change the owner of a local interactive user's home directory, use the following command:
+-
+-Note: The example will be for the user smithj, who has a home directory of "/home/smithj".
+-
+-# chown smithj /home/smithjVerify the assigned home directory of all local interactive users on the system exists.
+-
+-Check the home directory assignment for all local interactive users on the system with the following command:
+-
+-# ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+-
+--rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj
+-
+-If any home directories referenced in "/etc/passwd" are not owned by the interactive user, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020650The Oracle Linux operating system must be configured so that all local interactive user home directories are group-owned by the home directory owners primary group.<VulnDiscussion>If the Group Identifier (GID) of a local interactive user's home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user's files, and users that share the same group may not be able to access files that they legitimately should.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the group owner of a local interactive user's home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user's home directory, use 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.
+-
+-# chgrp users /home/smithjVerify the assigned home directory of all local interactive users is group-owned by that user's primary GID.
+-
+-Check the home directory assignment for all local interactive users on the system with the following command:
+-
+-# ls -ld $(egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+-
+--rwxr-x--- 1 smithj users 18 Mar 5 17:06 /home/smithj
+-
+-Check the user's primary group with the following command:
+-
+-# grep users /etc/group
+-
+-users: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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020660The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are owned by the owner of the home directory.<VulnDiscussion>If local interactive users do not own the files in their directories, unauthorized users may be able to access them. Additionally, if files are not owned by the user, this could be an indication of system compromise.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the owner of a local interactive user's files and directories to that owner. To change the 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".
+-
+-# chown smithj /home/smithj/<file or directory>Verify all files and directories in a local interactive user's home directory are owned by the user.
+-
+-Check the 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".
+-
+-# ls -lLR /home/smithj
+--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 smithj 231 Mar 5 17:06 file3
+-
+-If any files are found with an owner different than the home directory user, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020670The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member.<VulnDiscussion>If a local interactive user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the group of a local interactive user's files and directories to a group that the interactive user is a member of. 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.
+-
+-# chgrp users /home/smithj/<file>Verify all files and directories in a local interactive user home directory are group-owned by a group of which 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".
+-
+-# 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 are found with an owner different than the group home directory user, check to see if the user is a member of that group with the following command:
+-
+-# grep smithj /etc/group
+-sa:x:100:juan,shelley,bob,smithj 
+-smithj:x:521:smithj
+-
+-If the user is not a member of a group that group-owns file(s) in a local interactive user's home directory, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020680The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories have a mode of 0750 or less permissive.<VulnDiscussion>If a local interactive user files have excessive permissions, unintended users may be able to access or modify them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set 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.
+-
+-# chmod 0750 /home/smithj/<file>Verify all files and directories contained in a local interactive user home directory, excluding local initialization files, have a mode of "0750".
+-
+-Check the mode of all non-initialization files in a local interactive user home directory with the following command:
+-
+-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".
+-
+-# 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 are found with a mode more permissive than "0750", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020690The Oracle Linux operating system must be configured so that all local initialization files for interactive users are owned by the home directory user or root.<VulnDiscussion>Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the owner of the local initialization files for interactive users to either the directory owner or root with the following command:
+-
+-Note: The example will be for the smithj user, who has a home directory of "/home/smithj".
+-
+-# chown smithj /home/smithj/.*Verify all local initialization files for interactive users are owned by the home directory user or root.
+-
+-Check the owner on all local initialization files with the following command:
+-
+-Note: The example will be for the "smithj" user, who has a home directory of "/home/smithj".
+-
+-# ls -al /home/smithj/.* | more
+--rwxr-xr-x 1 smithj users 896 Mar 10 2011 .bash_profile
+--rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login
+--rwxr-xr-x 1 smithj users 886 Jan 6 2007 .profile
+-
+-If any file that sets a local interactive user's environment variables to override the system is not owned by the home directory owner or root, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020700The Oracle Linux operating system must be configured so that all local initialization files for local interactive users are be group-owned by the users primary group or root.<VulnDiscussion>Local initialization files for interactive users are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the group owner of a local interactive user's files to the group found in "/etc/passwd" for the user. To change the group owner of a local interactive user's home directory, use 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.
+-
+-# chgrp users /home/smithj/<file>Verify the local initialization files of all local interactive users are group-owned by that user's primary Group Identifier (GID).
+-
+-Check the home directory assignment for all non-privileged users on the system with the following command:
+-
+-Note: The example will be for the smithj user, who has a home directory of "/home/smithj" and a primary group of "users".
+-
+-# cut -d: -f 1,4,6 /etc/passwd | egrep ":[1-4][0-9]{3}"
+-smithj:1000:/home/smithj
+-
+-# grep 1000 /etc/group
+-users:x:1000:smithj,jonesj,jacksons 
+-
+-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.
+-
+-Check the group owner of all local interactive user's initialization files with the following command:
+-
+-# ls -al /home/smithj/.*
+--rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile
+--rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login
+--rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something
+-
+-If all local interactive user's initialization files are not group-owned by that user's primary GID, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020710The Oracle Linux operating system must be configured so that all local initialization files have mode 0740 or less permissive.<VulnDiscussion>Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set 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".
+-
+-# chmod 0740 /home/smithj/.<INIT_FILE>Verify that all local initialization files have a mode of "0740" or less permissive.
+-
+-Check the mode on all local initialization files with the following command:
+-
+-Note: The example will be for the "smithj" user, who has a home directory of "/home/smithj".
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020720The Oracle Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory.<VulnDiscussion>The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory (other than the user's home directory), executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Edit 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.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.
+-
+-Check the executable search path statement for all local interactive user initialization files in 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".
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020730The Oracle Linux operating system must be configured so that local initialization files do not execute world-writable programs.<VulnDiscussion>If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the mode on files being executed by the local initialization files with the following command:
+-
+-# chmod 0755 <file>Verify that local initialization files do not execute world-writable programs.
+-
+-Check the system for world-writable files with the following command:
+-
+-# find / -xdev -perm -002 -type f -exec ls -ld {} \; | more
+-
+-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.
+-
+-# grep <file> /home/*/.*
+-
+-If any local initialization files are found to reference world-writable files, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-020900The Oracle Linux operating system must be configured so that all system device files are correctly labeled to prevent unauthorized modification.<VulnDiscussion>If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized operations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Run the following command to determine which package owns the device file:
+-
+-# rpm -qf <filename>
+-
+-The package can be reinstalled from a yum repository using the command:
+-
+-# sudo yum reinstall <packagename>
+-
+-Alternatively, the package can be reinstalled from trusted media using the command:
+-
+-# sudo rpm -Uvh <packagename>Verify that all system device files are correctly labeled to prevent unauthorized modification.
+-
+-List all device files on the system that are incorrectly labeled with the following commands:
+-
+-Note: Device files are normally found under "/dev", but applications may place device files in other directories and may necessitate a search of the entire system.
+-
+-#find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n"
+-
+-#find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"
+-
+-Note: There are device files, such as "/dev/vmci", that are used when the operating system is a host virtual machine. They will not be owned by a user on the system and require the "device_t" label to operate. These device files are not a finding.
+-
+-If there is output from either of these commands, other than already noted, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021000The Oracle Linux operating system must be configured so that file systems containing user home directories are mounted to prevent files with the setuid and setgid bit set from being executed.<VulnDiscussion>The "nosuid" mount option causes the system not to execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the "/etc/fstab" to use the "nosuid" option on file systems that contain user home directories.Verify file systems that contain user home directories are mounted with the "nosuid" option.
+-
+-Find the file system(s) that contain the user home directories with the following command:
+-
+-Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is not a finding as the "nosuid" option cannot be used on the "/" system.
+-
+-# cut -d: -f 1,3,6 /etc/passwd | egrep ":[1-4][0-9]{3}"
+-smithj:1001:/home/smithj
+-thomasr:1002:/home/thomasr
+-
+-Check the file systems mounted at boot time with the following command:
+-
+-# more /etc/fstab
+-
+-UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered,nosuid 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021010The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media.<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the "/etc/fstab" to use the "nosuid" option on file systems that are associated with removable media.Verify file systems used for removable media are mounted with the "nosuid" option.
+-
+-Check the file systems mounted at boot time with the following command:
+-
+-# more /etc/fstab
+-
+-UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021020The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are being imported via Network File System (NFS).<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the "/etc/fstab" to use the "nosuid" option on file systems that are being imported via NFS.Verify file systems being NFS imported are configured with the "nosuid" option.
+-
+-Find the file system(s) that contain the directories being exported with the following command:
+-
+-# more /etc/fstab | grep nfs
+-
+-UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,nosuid 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.
+-
+-Verify the NFS is mounted with the "nosuid" option:
+-
+-# mount | grep nfs | grep nosuid
+-If no results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021021The Oracle Linux operating system must prevent binary files from being executed on file systems that are being imported via Network File System (NFS).<VulnDiscussion>The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the "/etc/fstab" to use the "noexec" option on file systems that are being imported via NFS.Verify file systems that are being NFS imported are configured with the "noexec" option.
+-
+-Find the file system(s) that contain the directories being imported with the following command:
+-
+-# more /etc/fstab | grep nfs
+-
+-UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d /store nfs rw,noexec 0 0
+-
+-If a file system found in "/etc/fstab" refers to NFS and it does not have the "noexec" option set, and use of NFS imported binaries is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
+-
+-Verify the NFS is mounted with the "noexec"option:
+-
+-# mount | grep nfs | grep noexec
+-If no results are returned and use of NFS imported binaries is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>OL07-00-021022The Oracle Linux operating system must mount /dev/shm with the nodev option.<VulnDiscussion>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001764Configure the system so that /dev/shm is mounted with the "nodev" option.Verify that the "nodev" option is configured for /dev/shm:
+-
+-
+-# cat /etc/fstab | grep /dev/shm
+-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
+-
+-If any results are returned and the "nodev" option is not listed, this is a finding.
+-
+-Verify "/dev/shm" is mounted with the "nodev" option:
+-
+-# mount | grep "/dev/shm" | grep nodev
+-
+-If no results are returned, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>OL07-00-021023The Oracle Linux operating system must mount /dev/shm with the nosuid option.<VulnDiscussion>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001764Configure the system so that /dev/shm is mounted with the "nosuid" option.Verify that the "nosuid" option is configured for /dev/shm:
+-
+-# cat /etc/fstab | grep /dev/shm
+-
+-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
+-
+-If any results are returned and the "nosuid" option is not listed, this is a finding.
+-
+-Verify "/dev/shm" is mounted with the "nosuid" option:
+-
+-# mount | grep "/dev/shm" | grep nosuid
+-
+-If no results are returned, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>OL07-00-021024The Oracle Linux operating system must mount /dev/shm with the noexec option.<VulnDiscussion>The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001764Configure the system so that /dev/shm is mounted with the "noexec" option.Verify that the "noexec" option is configured for /dev/shm:
+-
+-# cat /etc/fstab | grep /dev/shm
+-
+-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
+-
+-If any results are returned and the "noexec" option is not listed, this is a finding.
+-
+-Verify "/dev/shm" is mounted with the "noexec" option:
+-
+-# mount | grep "/dev/shm" | grep noexec
+-
+-If no results are returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021030The Oracle Linux operating system must be configured so that all world-writable directories are group-owned by root, sys, bin, or an application group.<VulnDiscussion>If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.
+-
+-The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Change the group of the world-writable directories to root with the following command:
+-
+-# chgrp root <directory>Verify all world-writable directories are group-owned by root, sys, bin, or an application group.
+-
+-Check the system for world-writable directories with the following command:
+-
+-Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+-
+-# find / -xdev -perm -002 -type d -fstype xfs -exec ls -lLd {} \;
+-drwxrwxrwt 2 root root 40 Aug 26 13:07 /dev/mqueue
+-drwxrwxrwt 2 root root 220 Aug 26 13:23 /dev/shm
+-drwxrwxrwt 14 root root 4096 Aug 26 13:29 /tmp
+-
+-If any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021040The Oracle Linux operating system must set the umask value to 077 for all local interactive user accounts.<VulnDiscussion>The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be "0". This requirement applies to the globally configured system defaults and the local interactive user defaults for each account on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Remove 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.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.
+-
+-# grep -i umask /home/*/.*
+-
+-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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021100The Oracle Linux operating system must have cron logging implemented.<VulnDiscussion>Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure "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.logVerify that "rsyslog" is configured to log cron events.
+-
+-Check the configuration of "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files for the cron facility 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.
+-
+-# grep cron /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+-cron.* /var/log/cron.log
+-
+-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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021110The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is owned by root.<VulnDiscussion>If the owner of the "cron.allow" file is not set to root, the possibility exists for an unauthorized user to view or to edit sensitive information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the owner on the "/etc/cron.allow" file to root with the following command:
+-
+-# chown root /etc/cron.allowVerify that the "cron.allow" file is owned by root.
+-
+-Check the owner of the "cron.allow" file with the following command:
+-
+-# ls -al /etc/cron.allow
+--rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow
+-
+-If the "cron.allow" file exists and has an owner other than root, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021120The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is group-owned by root.<VulnDiscussion>If the group owner of the "cron.allow" file is not set to root, sensitive information could be viewed or edited by unauthorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the group owner on the "/etc/cron.allow" file to root with the following command:
+-
+-# chgrp root /etc/cron.allowVerify that the "cron.allow" file is group-owned by root.
+-
+-Check the group owner of the "cron.allow" file with the following command:
+-
+-# ls -al /etc/cron.allow
+--rw------- 1 root root 6 Mar 5 2011 /etc/cron.allow
+-
+-If the "cron.allow" file exists and has a group owner other than root, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021300The Oracle Linux operating system must disable Kernel core dumps unless needed.<VulnDiscussion>Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space, and may result in denial of service by exhausting the available space on the target file system partition.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366If kernel core dumps are not required, disable the "kdump" service with the following command:
+-
+-# systemctl disable kdump.service
+-
+-If kernel core dumps are required, document the need with the ISSO.Verify that kernel core dumps are disabled unless needed.
+-
+-Check the status of the "kdump" service with the following command:
+-
+-# systemctl status kdump.service
+-kdump.service - Crash recovery kernel arming
+-Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)
+-Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago
+-Main PID: 1130 (code=exited, status=0/SUCCESS)
+-kernel arming.
+-
+-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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021310The Oracle Linux operating system must be configured so that a separate file system is used for user home directories (such as /home or an equivalent).<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Migrate the "/home" directory onto a separate file system/partition.Verify that a separate file system/partition has been created for non-privileged local interactive user home directories.
+-
+-Check the home directory assignment for all non-privileged users (those with a UID greater than 1000) on the system with the following command:
+-
+-#cut -d: -f 1,3,6,7 /etc/passwd | egrep ":[1-4][0-9]{3}" | tr ":" "\t"
+-
+-adamsj /home/adamsj /bin/bash
+-jacksonm /home/jacksonm /bin/bash
+-smithj /home/smithj /bin/bash
+-
+-The output of the command will give the directory/partition that contains the home directories for the non-privileged 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/partition has been created for the non-privileged interactive users with the following command:
+-
+-Note: The partition of /home is used in the example.
+-
+-# grep /home /etc/fstab
+-UUID=333ada18 /home ext4 noatime,nobarrier,nodev 1 2
+-
+-If a separate entry for the file system/partition that contains the non-privileged interactive users' home directories does not exist, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021320The Oracle Linux operating system must use a separate file system for /var.<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Migrate the "/var" path onto a separate file system.Verify that a separate file system/partition has been created for "/var".
+-
+-Check that a file system/partition has been created for "/var" with the following command:
+-
+-# grep /var /etc/fstab
+-UUID=c274f65f /var ext4 noatime,nobarrier 1 2
+-
+-If a separate entry for "/var" is not in use, this is a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>OL07-00-021330The Oracle Linux operating system must use a separate file system for the system audit data path large enough to hold at least one week of audit data.<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001849Migrate the system audit data path onto an appropriately sized separate file system to store at least one week of audit records.Determine if the operating system is configured to have the "/var/log/audit" path is on a separate file system.
+-
+-# grep /var/log/audit /etc/fstab
+-
+-If no result is returned, or the operating system is not configured to have "/var/log/audit" on a separate file system, this is a finding.
+-
+-Verify that "/var/log/audit" is mounted on a separate file system:
+-
+-# mount | grep "/var/log/audit"
+-
+-If no result is returned, or "/var/log/audit" is not on a separate file system, this is a finding.
+-
+-Verify the size of the audit file system:
+-
+-# df -h /var/log/audit
+-
+-If the size is insufficient for a week of audit data, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021340The Oracle Linux operating system must use a separate file system for /tmp (or equivalent).<VulnDiscussion>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Start the "tmp.mount" service with the following command:
+-
+-# systemctl enable tmp.mount
+-
+-OR
+-
+-Edit the "/etc/fstab" file and ensure the "/tmp" directory is defined in the fstab with a device and mount point.Verify that a separate file system/partition has been created for "/tmp".
+-
+-Check that a file system/partition has been created for "/tmp" with the following command:
+-
+-# systemctl is-enabled tmp.mount
+-enabled
+-
+-If the "tmp.mount" service is not enabled, check to see if "/tmp" is defined in the fstab with a device and mount point:
+-
+-# grep -i /tmp /etc/fstab
+-UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /tmp ext4 rw,relatime,discard,data=ordered,nosuid,noexec, 0 0
+-
+-If "tmp.mount" service is not enabled and the "/tmp" directory is not defined in the fstab with a device and mount point, this is a finding.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>OL07-00-021350The Oracle Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The operating system must implement cryptographic modules that adhere to the higher standards approved by the federal government to ensure they have been tested and validated.
+-
+-Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000185-GPOS-00079, SRG-OS-000396-GPOS-00176, SRG-OS-000405-GPOS-00184, SRG-OS-000478-GPOS-00223</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000068CCI-001199CCI-002450CCI-002476Configure the operating system to implement DoD-approved encryption by installing the dracut-fips package.
+-
+-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel command line during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place.
+-
+-Configure the operating system to implement DoD-approved encryption by following the steps below: 
+-
+-The fips=1 kernel option needs to be added to the kernel command line during system installation so that key generation is done with FIPS-approved algorithms and continuous monitoring tests in place. Users should also ensure that the system has plenty of entropy during the installation process by moving the mouse around, or if no mouse is available, ensuring that many keystrokes are typed. The recommended amount of keystrokes is 256 and more. Less than 256 keystrokes may generate a non-unique key.
+-
+-Install the dracut-fips package with the following command:
+-
+-# yum install dracut-fips
+-
+-Recreate the "initramfs" file with the following command:
+-
+-Note: This command will overwrite the existing "initramfs" file.
+-
+-# dracut -f
+-
+-Modify the kernel command line of the current kernel in the "grub.cfg" file by adding the following option to the GRUB_CMDLINE_LINUX key in the "/etc/default/grub" file and then rebuild the "grub.cfg" file:
+-
+-fips=1
+-
+-Changes to "/etc/default/grub" require rebuilding the "grub.cfg" file as follows:
+-
+-On BIOS-based machines, use the following command:
+-
+-# grub2-mkconfig -o /boot/grub2/grub.cfg
+-
+-On UEFI-based machines, use the following command:
+-
+-# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
+-
+-If /boot or /boot/efi reside on separate partitions, the kernel parameter boot=<partition of /boot or /boot/efi> must be added to the kernel command line. You can identify a partition by running the df /boot or df /boot/efi command:
+-
+-# df /boot
+-Filesystem 1K-blocks Used Available Use% Mounted on
+-/dev/sda1 495844 53780 416464 12% /boot
+-
+-To ensure the "boot=" configuration option will work even if device naming changes occur between boots, identify the universally unique identifier (UUID) of the partition with the following command:
+-
+-# blkid /dev/sda1
+-/dev/sda1: UUID="05c000f1-a213-759e-c7a2-f11b7424c797" TYPE="ext4"
+-
+-For the example above, append the following string to the kernel command line:
+-
+-boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797
+-
+-Reboot the system for the changes to take effect.Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions.
+-
+-Check to see if the "dracut-fips" package is installed with the following command:
+-
+-# yum list installed dracut-fips
+-
+-dracut-fips-033-360.el7_2.x86_64.rpm
+-
+-If a "dracut-fips" package is installed, check to see if the kernel command line is configured to use FIPS mode with the following command:
+-
+-Note: GRUB 2 reads its configuration from the "/boot/grub2/grub.cfg" file on traditional BIOS-based machines and from the "/boot/efi/EFI/redhat/grub.cfg" file on UEFI machines.
+-
+-# grep fips /boot/grub2/grub.cfg
+-/vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0 rd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us rd.lvm.lv=rhel/root rhgb fips=1 quiet
+-
+-If the kernel command line is configured to use FIPS mode, check to see if the system is in FIPS mode with the following command:
+-
+-# cat /proc/sys/crypto/fips_enabled 
+-1
+-
+-If a "dracut-fips" package is not installed, the kernel command line does not have a fips entry, or the system has a value of "0" for "fips_enabled" in "/proc/sys/crypto", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021600The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify Access Control Lists (ACLs).<VulnDiscussion>ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the file integrity tool to check file and directory ACLs. 
+-
+-If AIDE is installed, ensure the "acl" rule is present on all uncommented file and directory selection lists.Verify the file integrity tool is configured to verify ACLs.
+-
+-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+-
+-# yum list installed aide
+-
+-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 file integrity checks, this is a finding.
+-
+-Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. 
+-
+-Use the following command to determine if the file is in another location:
+-
+-# 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.
+-
+-An example rule that includes the "acl" rule is below:
+-
+-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 "acl" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or ACLs are not being checked by another file integrity tool, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021610The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify extended attributes.<VulnDiscussion>Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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.Verify the file integrity tool is configured to verify extended attributes.
+-
+-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+-
+-# yum list installed aide
+-
+-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 file integrity checks, this is a finding.
+-
+-Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory.
+-
+-Use the following command to determine if the file is in another location:
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-021620The Oracle Linux operating system must use a file integrity tool that is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.<VulnDiscussion>File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the file integrity tool to use FIPS 140-2 cryptographic hashes for validating file and directory contents. 
+-
+-If AIDE is installed, ensure the "sha512" rule is present on all uncommented file and directory selection lists.Verify the file integrity tool is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.
+-
+-Note: If OL07-00-021350 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
+-
+-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+-
+-# yum list installed aide
+-
+-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 file integrity checks, this is a finding.
+-
+-Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. 
+-
+-Use the following command to determine if the file is in another location:
+-
+-# find / -name aide.conf
+-
+-Check the "aide.conf" file to determine if the "sha512" rule has been added to the rule list being applied to the files and directories selection lists.
+-
+-An example rule that includes the "sha512" 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 "sha512" rule is not being used on all uncommented selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using FIPS 140-2 approved cryptographic hashes for validating file contents and directories, this is a finding.SRG-OS-000364-GPOS-00151<GroupDescription></GroupDescription>OL07-00-021700The Oracle Linux operating system must not allow removable media to be used as the boot loader unless approved.<VulnDiscussion>Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. If removable media is designed to be used as the boot loader, the requirement must be documented with the Information System Security Officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001813Remove alternate methods of booting the system from removable media or document the configuration to boot from removable media with the ISSO.Verify the system is not configured to use a boot loader on removable media.
+-
+-Note: GRUB 2 reads its configuration from the "/boot/grub2/grub.cfg" file on traditional BIOS-based machines and from the "/boot/efi/EFI/redhat/grub.cfg" file on UEFI machines.
+-
+-Check for the existence of alternate boot loader configuration files with the following command:
+-
+-# find / -name grub.cfg
+-/boot/grub2/grub.cfg
+-
+-If a "grub.cfg" is found in any subdirectories other than "/boot/grub2" and "/boot/efi/EFI/redhat", ask the System Administrator if there is documentation signed by the ISSO to approve the use of removable media as a boot loader. 
+-
+-Check that the grub configuration file has the set root command in each menu entry with the following commands:
+-
+-# grep -c menuentry /boot/grub2/grub.cfg
+-1
+-# grep 'set root' /boot/grub2/grub.cfg
+-set root=(hd0,1)
+-
+-If the system is using an alternate boot loader on removable media, and documentation does not exist approving the alternate configuration, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>OL07-00-021710The Oracle Linux operating system must not have the telnet-server package installed.<VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
+-
+-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+-
+-Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000381Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command:
+-
+-# yum remove telnet-serverVerify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is not to install the capability.
+-
+-The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+-
+-If a privileged user were to log on using this service, the privileged user password could be compromised. 
+-
+-Check to see if the telnet-server package is installed with the following command:
+-
+-# yum list installed telnet-server
+-
+-If the telnet-server package is installed, this is a finding.SRG-OS-000038-GPOS-00016<GroupDescription></GroupDescription>OL07-00-030000The Oracle Linux operating system must be configured so that auditing is configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users.<VulnDiscussion>Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+-
+-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+-
+-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds, or identifying an improperly configured operating system.
+-
+-Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000365-GPOS-00152, SRG-OS-000255-GPOS-00096</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000131CCI-000132CCI-000135CCI-001464CCI-001487CCI-001814Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred.
+-
+-Enable the auditd service with the following command:
+-
+-# systemctl start auditd.serviceVerify the operating system produces audit records containing information to establish when (date and time) the events occurred.
+-
+-Check to see if auditing is active by issuing the following command:
+-
+-# systemctl is-active auditd.service
+-active
+-
+-If the "auditd" status is not active, this is a finding.SRG-OS-000046-GPOS-00022<GroupDescription></GroupDescription>OL07-00-030010The Oracle Linux operating system must shut down upon audit processing failure unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) in the event of an audit processing failure.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
+-
+-Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
+-
+-This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.
+-
+-Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000047-GPOS-00023</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000139CCI-000140Configure the operating system to shut down in the event of an audit processing failure.
+-
+-Add or correct the option to shut down the operating system with the following command:
+-
+-# auditctl -f 2
+-
+-Edit the "/etc/audit/rules.d/audit.rules" file and add the following line:
+-
+--f 2
+-
+-If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of an audit processing failure with the following command:
+-
+-# auditctl -f 1
+-
+-Edit the "/etc/audit/rules.d/audit.rules" file and add the following line:
+-
+--f 1
+-
+-Kernel log monitoring must also be configured to properly alert designated staff.
+-
+-The audit daemon must be restarted for the changes to take effect.Confirm the audit configuration regarding how auditing processing failures are handled.
+-
+-Check to see what level "auditctl" is set to with following command: 
+-
+-# auditctl -s | grep -i "fail"
+-
+-failure 2
+-
+-If the value of "failure" is set to "2", the system is configured to panic (shut down) in the event of an auditing failure.
+-
+-If the value of "failure" is set to "1", the system is configured only to send information to the kernel log regarding the failure.
+-
+-If the "failure" setting is not set, this is a CAT I finding.
+-
+-If the "failure" setting is set to any value other than "1" or "2", this is a CAT II finding.
+-
+-If the "failure" setting is set to "1" but the availability concern is not documented or there is no monitoring of the kernel log, this is a CAT III finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030200The Oracle Linux operating system must be configured to use the au-remote plugin.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-Without the configuration of the "au-remote" plugin, the audisp-remote daemon will not off-load the logs from the system being audited.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Edit the /etc/audisp/plugins.d/au-remote.conf file and change the value of "active" to "yes".
+-
+-The audit daemon must be restarted for changes to take effect:
+-
+-# service auditd restartVerify the "au-remote" plugin is active on the system:
+-
+-# grep "active" /etc/audisp/plugins.d/au-remote.conf
+-
+-active = yes
+-
+-If the "active" setting is not set to "yes", or the line is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030201The Oracle Linux operating system must configure the au-remote plugin to off-load audit logs using the audisp-remote daemon.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-Without the configuration of the "au-remote" plugin, the audisp-remote daemon will not off load the logs from the system being audited.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Edit the /etc/audisp/plugins.d/au-remote.conf file and add or update the following values:
+-
+-direction = out
+-path = /sbin/audisp-remote
+-type = always
+-
+-The audit daemon must be restarted for changes to take effect:
+-
+-# service auditd restartVerify the "au-remote" plugin is configured to always off-load audit logs using the audisp-remote daemon:
+-
+-# cat /etc/audisp/plugins.d/au-remote.conf | grep -v "^#"
+-
+-active = yes
+-direction = out
+-path = /sbin/audisp-remote
+-type = always
+-format = string
+-
+-If the "direction" setting is not set to "out", or the line is commented out, this is a finding.
+-
+-If the "path" setting is not set to "/sbin/audisp-remote", or the line is commented out, this is a finding.
+-
+-If the "type" setting is not set to "always", or the line is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030210The Oracle Linux operating system must take appropriate action when the audisp-remote buffer is full.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-When the remote buffer is full, audit logs will not be collected and sent to the central log server.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Edit the /etc/audisp/audispd.conf file and add or update the "overflow_action" option:
+-
+-overflow_action = syslog
+-
+-The audit daemon must be restarted for changes to take effect:
+-
+-# service auditd restartVerify the audisp daemon is configured to take an appropriate action when the internal queue is full:
+-
+-# grep "overflow_action" /etc/audisp/audispd.conf
+-
+-overflow_action = syslog
+-
+-If the "overflow_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030211The Oracle Linux operating system must label all off-loaded audit logs before sending them to the central log server.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-When audit logs are not labeled before they are sent to a central log server, the audit data will not be able to be analyzed and tied back to the correct system.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Edit the /etc/audisp/audispd.conf file and add or update the "name_format" option:
+-
+-name_format = hostname
+-
+-The audit daemon must be restarted for changes to take effect:
+-
+-# service auditd restartVerify the audisp daemon is configured to label all off-loaded audit logs:
+-
+-# grep "name_format" /etc/audisp/audispd.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.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030300The Oracle Linux operating system must off-load audit records onto a different system or media from the system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Configure the operating system to off-load audit records onto a different system or media from the system being audited.
+-
+-Set the remote server option in "/etc/audisp/audisp-remote.conf" with the IP address of the log aggregation server.Verify the operating system off-loads audit records onto a different system or media from the system being audited.
+-
+-To determine the remote server that the records are being sent to, use the following command:
+-
+-# grep -i remote_server /etc/audisp/audisp-remote.conf
+-remote_server = 10.0.21.1
+-
+-If a remote server is not configured, or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+-
+-If there is no evidence that the audit logs are being off-loaded to another system or media, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030310The Oracle Linux operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+-
+-Off-loading is a common process in information systems with limited audit storage capacity.
+-
+-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Configure the operating system to encrypt the transfer of off-loaded audit records onto a different system or media from the system being audited.
+-
+-Uncomment the "enable_krb5" option in "/etc/audisp/audisp-remote.conf" and set it with the following line:
+-
+-enable_krb5 = yesVerify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited.
+-
+-To determine if the transfer is encrypted, use the following command:
+-
+-# grep -i enable_krb5 /etc/audisp/audisp-remote.conf
+-enable_krb5 = yes
+-
+-If the value of the "enable_krb5" option is not set to "yes" or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+-
+-If there is no evidence that the transfer of the audit logs being off-loaded to another system or media is encrypted, this is a finding.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030320The Oracle Linux operating system must be configured so that the audit system takes appropriate action when the audit storage volume is full.<VulnDiscussion>Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Configure the action the operating system takes if the disk the audit records are written to becomes full.
+-
+-Uncomment or edit the "disk_full_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt", such as the following line:
+-
+-disk_full_action = singleVerify the action the operating system takes if the disk the audit records are written to becomes full.
+-
+-To determine the action that takes place if the disk is full on the remote server, use the following command:
+-
+-# grep -i disk_full_action /etc/audisp/audisp-remote.conf
+-disk_full_action = single
+-
+-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.SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>OL07-00-030321The Oracle Linux operating system must be configured so that the audit system takes appropriate action when there is an error sending audit records to a remote system.<VulnDiscussion>Taking appropriate action when there is an error sending audit records to a remote system will minimize the possibility of losing audit records.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001851Configure the action the operating system takes if there is an error sending audit records to a remote system.
+-
+-Uncomment the "network_failure_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt".
+-
+-network_failure_action = syslogVerify the action the operating system takes if there is an error sending audit records to a remote system.
+-
+-Check the action that takes place if there is an error sending audit records to a remote system with the following command:
+-
+-# grep -i network_failure_action /etc/audisp/audisp-remote.conf
+-network_failure_action = syslog
+-
+-If the value of the "network_failure_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>OL07-00-030330The Oracle Linux operating system must initiate an action to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.<VulnDiscussion>If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001855Configure 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.
+-
+-Check the system configuration to determine the partition the audit records are being written to: 
+-
+-# grep -iw log_file /etc/audit/auditd.conf
+-
+-Determine the size of the partition that audit records are written to (with the example being "/var/log/audit/"):
+-
+-# df -h /var/log/audit/
+-
+-Set the value of the "space_left" keyword in "/etc/audit/auditd.conf" to 75 percent of the partition size.Verify the operating system initiates 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.
+-
+-Check the system configuration to determine the partition the audit records are being written to with the following command:
+-
+-# grep -iw log_file /etc/audit/auditd.conf
+-log_file = /var/log/audit/audit.log
+-
+-Check the size of the partition that audit records are written to (with the example being "/var/log/audit/"):
+-
+-# df -h /var/log/audit/
+-0.9G /var/log/audit
+-
+-If the audit records are not being written to a partition specifically created for audit records (in this example "/var/log/audit" is a separate partition), determine the amount of space other files in the partition are currently occupying with the following command:
+-
+-# du -sh <partition>
+-1.8G /var
+-
+-Determine what the threshold is for the system to take action when 75 percent of the repository maximum audit record storage capacity is reached:
+-
+-# grep -iw space_left /etc/audit/auditd.conf
+-space_left = 225 
+-
+-If the value of the "space_left" keyword is not set to 75 percent of the total partition size, this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>OL07-00-030340The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.<VulnDiscussion>If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001855Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
+-
+-Uncomment or edit the "space_left_action" keyword in "/etc/audit/auditd.conf" and set it to "email". 
+-
+-space_left_action = emailVerify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
+-
+-Check what action the operating system takes when the threshold for the repository maximum audit record storage capacity is reached with the following command:
+-
+-# grep -i space_left_action /etc/audit/auditd.conf
+-space_left_action = email
+-
+-If the value of the "space_left_action" keyword is not set to "email", this is a finding.SRG-OS-000343-GPOS-00134<GroupDescription></GroupDescription>OL07-00-030350The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.<VulnDiscussion>If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001855Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
+-
+-Uncomment or edit the "action_mail_acct" keyword in "/etc/audit/auditd.conf" and set it to root and any other accounts associated with security personnel. 
+-
+-action_mail_acct = rootVerify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.
+-
+-Check what account the operating system emails when the threshold for the repository maximum audit record storage capacity is reached with the following command:
+-
+-# grep -i 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 other accounts for security personnel, this is a finding.SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>OL07-00-030360The Oracle Linux operating system must audit all executions of privileged functions.<VulnDiscussion>Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002234Configure the operating system to audit the execution of privileged functions.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid
+--a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid
+--a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid
+--a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system audits the execution of privileged functions using the following command:
+-
+-# grep -iw execve /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k setuid
+--a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k setuid
+--a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k setgid
+--a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k setgid
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. 
+-Only the lines appropriate for the system architecture must be present.
+-
+-If the audit rule for "SUID" files is not defined, this is a finding.
+-
+-If the audit rule for "SGID" files is not defined, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030370The Oracle Linux operating system must audit all uses of the chown syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chown" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw chown /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "chown" syscall, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030380The Oracle Linux operating system must audit all uses of the fchown syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchown" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fchown /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fchown" syscall, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030390The Oracle Linux operating system must audit all uses of the lchown syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lchown" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw lchown /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "lchown" syscall, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030400The Oracle Linux operating system must audit all uses of the fchownat syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchownat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fchownat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fchownat" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030410The Oracle Linux operating system must audit all uses of the chmod syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chmod" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chmod" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw chmod /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "chmod" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030420The Oracle Linux operating system must audit all uses of the fchmod syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fchmod" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchmod" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fchmod /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fchmod" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030430The Oracle Linux operating system must audit all uses of the fchmodat syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fchmodat" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchmodat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fchmodat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fchmodat" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030440The Oracle Linux operating system must audit all uses of the setxattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "setxattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "setxattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw setxattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "setxattr" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030450The Oracle Linux operating system must audit all uses of the fsetxattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fsetxattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fsetxattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fsetxattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fsetxattr" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030460The Oracle Linux operating system must audit all uses of the lsetxattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "lsetxattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lsetxattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw lsetxattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "lsetxattr" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030470The Oracle Linux operating system must audit all uses of the removexattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "removexattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "removexattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw removexattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "removexattr" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030480The Oracle Linux operating system must audit all uses of the fremovexattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fremovexattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fremovexattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw fremovexattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "fremovexattr" syscall, this is a finding.SRG-OS-000458-GPOS-00203<GroupDescription></GroupDescription>OL07-00-030490The Oracle Linux operating system must audit all uses of the lremovexattr syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "lremovexattr" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lremovexattr" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw lremovexattr /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+--a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
+-
+-If there are no audit rules defined for the "lremovexattr" syscall, this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030500The Oracle Linux operating system must audit all uses of the creat syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "creat" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules:
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "creat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw creat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S creat F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "creat" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030510The Oracle Linux operating system must audit all uses of the open syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "open" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "open" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw open /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "open" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030520The Oracle Linux operating system must audit all uses of the openat syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "openat" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "openat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw openat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "openat" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030530The Oracle Linux operating system must audit all uses of the open_by_handle_at syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "open_by_handle_at" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "open_by_handle_at" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw open_by_handle_at /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "open_by_handle_at" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030540The Oracle Linux operating system must audit all uses of the truncate syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "truncate" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "truncate" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw truncate /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "truncate" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000064-GPOS-00033<GroupDescription></GroupDescription>OL07-00-030550The Oracle Linux operating system must audit all uses of the ftruncate syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "ftruncate" syscall occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "ftruncate" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw ftruncate /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
+-
+--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
+-
+-If there are no audit rules defined for the "ftruncate" syscall, this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EPERM", this is a finding.
+-
+-If the output does not produce a rule containing "-F exit=-EACCES", this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030560The Oracle Linux operating system must audit all uses of the semanage command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172CCI-002884Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "semanage" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "semanage" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/sbin/semanage /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/semanage -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030570The Oracle Linux operating system must audit all uses of the setsebool command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002884Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "setsebool" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "setsebool" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/sbin/setsebool /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/setsebool -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030580The Oracle Linux operating system must audit all uses of the chcon command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002884Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chcon" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chcon" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/bin/chcon /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/chcon -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030590The Oracle Linux operating system must audit all uses of the setfiles command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002884Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "setfiles" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "setfiles" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -iw /usr/sbin/setfiles /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/setfiles -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030610The Oracle Linux operating system must generate audit records for all unsuccessful account access events.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172CCI-002884Configure the operating system to generate audit records when unsuccessful account access events occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--w /var/run/faillock -p wa -k logins
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when unsuccessful account access events occur. 
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following commands: 
+-
+-# grep -i /var/run/faillock /etc/audit/audit.rules
+-
+--w /var/run/faillock -p wa -k logins
+-
+-If the command does not return any output, this is a finding.SRG-OS-000392-GPOS-00172<GroupDescription></GroupDescription>OL07-00-030620The Oracle Linux operating system must generate audit records for all successful account access events.<VulnDiscussion>Without generating audit records that to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172CCI-002884Configure the operating system to generate audit records when successful account access events occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--w /var/log/lastlog -p wa -k logins
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful account access events occur. 
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands: 
+-
+-# grep -i /var/log/lastlog /etc/audit/audit.rules
+-
+--w /var/log/lastlog -p wa -k logins 
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030630The Oracle Linux operating system must audit all uses of the passwd command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "passwd" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "passwd" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/bin/passwd /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/passwd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030640The Oracle Linux operating system must audit all uses of the unix_chkpwd command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unix_chkpwd" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unix_chkpwd" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -iw /usr/sbin/unix_chkpwd /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/unix_chkpwd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030650The Oracle Linux operating system must audit all uses of the gpasswd command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "gpasswd" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "gpasswd" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/bin/gpasswd /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/gpasswd -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030660The Oracle Linux operating system must audit all uses of the chage command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chage" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chage" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/bin/chage /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/chage -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030670The Oracle Linux operating system must audit all uses of the userhelper command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "userhelper" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "userhelper" command occur.
+-
+-Check the file system rule in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -i /usr/sbin/userhelper /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/userhelper -F auid>=1000 -F auid!=4294967295 -k privileged-passwd
+-
+-If the command does not return any output, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>OL07-00-030680The Oracle Linux operating system must audit all uses of the su command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000130CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "su" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change 
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "su" command occur.
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/bin/su /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/su -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>OL07-00-030690The Oracle Linux operating system must audit all uses of the sudo command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000130CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "sudo" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change 
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "sudo" command occur.
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/bin/sudo /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/sudo -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>OL07-00-030700The Oracle Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000130CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to access the "/etc/sudoers" file and files in the "/etc/sudoers.d/" directory.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--w /etc/sudoers -p wa -k privileged-actions
+-
+--w /etc/sudoers.d/ -p wa -k privileged-actions
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to access the "/etc/sudoers" file and files in the "/etc/sudoers.d/" directory. 
+-
+-Check for modification of the following files being audited by performing the following commands to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -i "/etc/sudoers" /etc/audit/audit.rules
+-
+--w /etc/sudoers -p wa -k privileged-actions
+-
+-# grep -i "/etc/sudoers.d/" /etc/audit/audit.rules
+-
+--w /etc/sudoers.d/ -p wa -k privileged-actions
+-
+-If the commands do not return output that match the examples, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>OL07-00-030710The Oracle Linux operating system must audit all uses of the newgrp command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000130CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "newgrp" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "newgrp" command occur.
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -i /usr/bin/newgrp /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/newgrp -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000037-GPOS-00015<GroupDescription></GroupDescription>OL07-00-030720The Oracle Linux operating system must audit all uses of the chsh command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000130Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chsh" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chsh" command occur.
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -i /usr/bin/chsh /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/chsh -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030740The Oracle Linux operating system must audit all uses of the mount command and syscall.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "mount" command and syscall occur.
+-
+-Add or update the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+--a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+--a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "mount" command and syscall occur.
+-
+-Check that the following system call is being audited by performing the following series of commands to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw "mount" /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+--a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+--a always,exit -F path=/usr/bin/mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+-
+-If all uses of the "mount" command and syscall are not being audited, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030750The Oracle Linux operating system must audit all uses of the umount command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "umount" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "umount" command occur.
+-
+-Check that the following system call is being audited by performing the following series of commands to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw "/usr/bin/umount" /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/umount -F auid>=1000 -F auid!=4294967295 -k privileged-mount 
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030760The Oracle Linux operating system must audit all uses of the postdrop command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "postdrop" command occur.
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295 -k privileged-postfix
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "postdrop" command occur.
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/sbin/postdrop /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/postdrop -F auid>=1000 -F auid!=4294967295 -k privileged-postfix
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030770The Oracle Linux operating system must audit all uses of the postqueue command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "postqueue" command occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F auid!=4294967295 -k privileged-postfix
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "postqueue" command occur. 
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/sbin/postqueue /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/postqueue -F auid>=1000 -F auid!=4294967295 -k privileged-postfix
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030780The Oracle Linux operating system must audit all uses of the ssh-keysign command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged ssh commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "ssh-keysign" command occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F auid!=4294967295 -k privileged-ssh
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "ssh-keysign" command occur. 
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F auid>=1000 -F auid!=4294967295 -k privileged-ssh
+-
+-If the command does not return any output, this is a finding.SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>OL07-00-030800The Oracle Linux operating system must audit all uses of the crontab command.<VulnDiscussion>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+-
+-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+-
+-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000135Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "crontab" command occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295 -k privileged-cron
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "crontab" command occur. 
+-
+-Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+-
+-# grep -iw /usr/bin/crontab /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/bin/crontab -F auid>=1000 -F auid!=4294967295 -k privileged-cron
+-
+-If the command does not return any output, this is a finding.SRG-OS-000471-GPOS-00215<GroupDescription></GroupDescription>OL07-00-030810The Oracle Linux operating system must audit all uses of the pam_timestamp_check command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "pam_timestamp_check" command occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+-
+--a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F auid!=4294967295 -k privileged-pam
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "pam_timestamp_check" command occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -iw "/usr/sbin/pam_timestamp_check" /etc/audit/audit.rules
+-
+--a always,exit -F path=/usr/sbin/pam_timestamp_check -F auid>=1000 -F auid!=4294967295 -k privileged-pam 
+-
+-If the command does not return any output, this is a finding.SRG-OS-000471-GPOS-00216<GroupDescription></GroupDescription>OL07-00-030819The Oracle Linux operating system must audit all uses of the create_module syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "create_module" syscall occur.
+-
+-Add or update the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured. 
+-
+--a always,exit -F arch=b32 -S create_module -k module-change
+-
+--a always,exit -F arch=b64 -S create_module -k module-change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "create_module" syscall occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+-
+-# grep -iw create_module /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S create_module -k module-change
+-
+--a always,exit -F arch=b64 -S create_module -k module-change
+-
+-If there are no audit rules defined for "create_module", this is a finding.SRG-OS-000471-GPOS-00216<GroupDescription></GroupDescription>OL07-00-030820The Oracle Linux operating system must audit all uses of the init_module syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "init_module" syscall occur. 
+-
+-Add or update the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured. 
+-
+--a always,exit -F arch=b32 -S init_module -k module-change
+-
+--a always,exit -F arch=b64 -S init_module -k module-change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "init_module" syscall occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+-
+-# grep -iw init_module /etc/audit/audit.rules 
+-
+--a always,exit -F arch=b32 -S init_module -k module-change
+-
+--a always,exit -F arch=b64 -S init_module -k module-change
+-
+-If there are no audit rules defined for "init_module", this is a finding.SRG-OS-000471-GPOS-00216<GroupDescription></GroupDescription>OL07-00-030821The Oracle Linux operating system must audit all uses of the finit_module syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "finit_module" syscall occur. 
+-
+-Add or update the following rules in "/etc/audit/rules.d/audit.rules": 
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+--a always,exit -F arch=b32 -S finit_module -k module-change
+-
+--a always,exit -F arch=b64 -S finit_module -k module-change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "finit_module" syscall occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+-
+-# grep -iw finit_module /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S finit_module -k module-change
+-
+--a always,exit -F arch=b64 -S finit_module -k module-change
+-
+-If there are no audit rules defined for "finit_module", this is a finding.SRG-OS-000471-GPOS-00216<GroupDescription></GroupDescription>OL07-00-030830The Oracle Linux operating system must audit all uses of the delete_module syscall.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "delete_module" syscall occur. 
+-
+-Add or update the following rules in "/etc/audit/rules.d/audit.rules": 
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S delete_module -k module-change
+-
+--a always,exit -F arch=b64 -S delete_module -k module-change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "delete_module" syscall occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+-
+-# grep -iw delete_module /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S delete_module -k module-change
+-
+--a always,exit -F arch=b64 -S delete_module -k module-change
+-
+-If there are no audit rules defined for "delete_module", this is a finding.SRG-OS-000471-GPOS-00216<GroupDescription></GroupDescription>OL07-00-030840The Oracle Linux operating system must audit all uses of the kmod command.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "kmod" command occur. 
+-
+-Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+-
+--w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "kmod" command occur. 
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-# grep -iw kmod /etc/audit/audit.rules
+-
+--w /usr/bin/kmod -p x -F auid!=4294967295 -k module-change
+-
+-If the command does not return any output, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>OL07-00-030870The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).
+-
+-Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd".
+-
+-Add or update the following rule "/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.Verify the operating system must generate 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:
+-
+-# 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.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>OL07-00-030871The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000018Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".
+-
+-Add or update the following rule in "/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.Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-# 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.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>OL07-00-030872The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.<VulnDiscussion>Without generating audit specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000018Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".
+-
+-Add or update the following rule in "/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.Verify the operating system must generate 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:
+-
+-# 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.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>OL07-00-030873The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000018Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.
+-
+-Add or update the following file system rule in "/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.Verify the operating system must generate 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:
+-
+-# 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.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>OL07-00-030874The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.<VulnDiscussion>Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+-
+-Audit records can be generated from various components within the information system (e.g., module or policy filter).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000018Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.
+-
+-Add or update the following file system rule in "/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:
+-# systemctl restart auditdVerify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.
+-
+-Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+-
+-# 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.SRG-OS-000466-GPOS-00210<GroupDescription></GroupDescription>OL07-00-030880The Oracle Linux operating system must audit all uses of the rename syscall.<VulnDiscussion>If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+-
+-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rename" syscall occur.
+-
+-Add the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rename" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw rename /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S rename -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S rename -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-If there are no audit rules defined for the "rename" syscall, this is a finding.SRG-OS-000466-GPOS-00210<GroupDescription></GroupDescription>OL07-00-030890The Oracle Linux operating system must audit all uses of the renameat syscall.<VulnDiscussion>If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+-
+-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "renameat" syscall occur.
+-
+-Add the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "renameat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw renameat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S renameat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S renameat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-If there are no audit rules defined for the "renameat" syscall, this is a finding.SRG-OS-000466-GPOS-00210<GroupDescription></GroupDescription>OL07-00-030900The Oracle Linux operating system must audit all uses of the rmdir syscall.<VulnDiscussion>If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+-
+-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rmdir" syscall occur.
+-
+-Add the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rmdir" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw rmdir /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-If there are no audit rules defined for the "rmdir" syscall, this is a finding.SRG-OS-000466-GPOS-00210<GroupDescription></GroupDescription>OL07-00-030910The Oracle Linux operating system must audit all uses of the unlink syscall.<VulnDiscussion>If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+-
+-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unlink" syscall occur.
+-
+-Add the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unlink" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw unlink /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S unlink -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S unlink -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-If there are no audit rules defined for the "unlink" syscall, this is a finding.SRG-OS-000466-GPOS-00210<GroupDescription></GroupDescription>OL07-00-030920The Oracle Linux operating system must audit all uses of the unlinkat syscall.<VulnDiscussion>If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+-
+-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000172Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unlinkat" syscall occur.
+-
+-Add the following rules in "/etc/audit/rules.d/audit.rules":
+-
+-Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured.
+-
+--a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-The audit daemon must be restarted for the changes to take effect.Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unlinkat" syscall occur.
+-
+-Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+-
+-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+-
+-# grep -iw unlinkat /etc/audit/audit.rules
+-
+--a always,exit -F arch=b32 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+--a always,exit -F arch=b64 -S unlinkat -F auid>=1000 -F auid!=4294967295 -k delete
+-
+-If there are no audit rules defined for the "unlinkat" syscall, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-031000The Oracle Linux operating system must send rsyslog output to a log aggregation server.<VulnDiscussion>Sending rsyslog output to another system ensures that the logs cannot be removed or modified in the event that the system is compromised or has a hardware failure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Modify the "/etc/rsyslog.conf" or an "/etc/rsyslog.d/*.conf" file to contain a configuration line to send all "rsyslog" output to a log aggregation system:
+-*.* @@<log aggregation system name>Verify "rsyslog" is configured to send all messages to a log aggregation server.
+-
+-Check the configuration of "rsyslog" with the following command:
+-
+-Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf".
+-
+-# grep @ /etc/rsyslog.conf /etc/rsyslog.d/*.conf
+-*.* @@logagg.site.mil
+-
+-If there are no lines in the "/etc/rsyslog.conf" or "/etc/rsyslog.d/*.conf" files that contain the "@" or "@@" symbol(s), and the lines with the correct symbol(s) to send output to another system do not cover all "rsyslog" output, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+-
+-If the lines are commented out or there is no evidence that the audit logs are being sent to another system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-031010The Oracle Linux operating system must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation.<VulnDiscussion>Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a denial of service.
+-
+-If the system is intended to be a log aggregation server its use must be documented with the ISSO.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Modify the "/etc/rsyslog.conf" file to remove the "ModLoad imtcp", "ModLoad imudp", and "ModLoad imrelp" configuration lines, or document the system as being used for log aggregation.Verify that the system is not accepting "rsyslog" messages from other systems unless it is documented as a log aggregation server.
+-
+-Check the configuration of "rsyslog" with the following command:
+-
+-# grep imtcp /etc/rsyslog.conf
+-$ModLoad imtcp
+-# grep imudp /etc/rsyslog.conf
+-$ModLoad imudp
+-# grep imrelp /etc/rsyslog.conf
+-$ModLoad imrelp
+-
+-If any of the above modules are being loaded in the "/etc/rsyslog.conf" file, ask to see the documentation for the system being used for log aggregation.
+-
+-If the documentation does not exist, or does not specify the server as a log aggregation system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-032000The Oracle Linux operating system must use a virus scan program.<VulnDiscussion>Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.
+-
+-The virus scanning software should be configured to perform scans dynamically on accessed files. If this capability is not available, the system must be configured to scan, at a minimum, all altered files on the system on a daily basis.
+-
+-If the system processes inbound SMTP mail, the virus scanner must be configured to scan all received mail.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Install an antivirus solution on the system.Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution.
+-
+-If there is no anti-virus solution installed on the system, this is a finding.SRG-OS-000027-GPOS-00008<GroupDescription></GroupDescription>OL07-00-040000The Oracle Linux operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.<VulnDiscussion>Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks.
+-
+-This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000054Configure the operating system to limit the number of concurrent sessions to 10 for all accounts and/or account types.
+-
+-Add the following line to the top of the /etc/security/limits.conf:
+-
+-* hard maxlogins 10Verify the operating system limits the number of concurrent sessions to 10 for all accounts and/or account types by issuing the following command:
+-
+-# grep "maxlogins" /etc/security/limits.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, 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.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>OL07-00-040100The Oracle Linux operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+-
+-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
+-
+-To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
+-
+-Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000382CCI-002314Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL.Inspect the firewall configuration and running services to verify that 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:
+-
+-# firewall-cmd --list-all
+-public (default, active)
+-interfaces: enp0s3
+-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 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 ports, protocols, or services prohibited by the PPSM Category Assurance List (CAL), this is a finding.SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>OL07-00-040110The Oracle Linux operating system must use a FIPS 140-2 approved cryptographic algorithm for SSH communications.<VulnDiscussion>Unapproved mechanisms for authentication to the cryptographic module are not verified, and therefore cannot be relied upon to provide confidentiality or integrity, resulting in the compromise of DoD data.
+-
+-Operating systems using encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
+-
+-FIPS 140-2 is the current standard for validating mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general-purpose computing system.
+-
+-Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000120-GPOS-00061, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173,SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000068CCI-000803CCI-000877CCI-002890CCI-003123Configure SSH to use FIPS 140-2 approved cryptographic algorithms.
+-
+-Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (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).
+-
+-Ciphers aes128-ctr,aes192-ctr,aes256-ctr
+-
+-The SSH service must be restarted for changes to take effect.Verify the operating system uses mechanisms that meet the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
+-
+-Note: If OL07-00-021350 is a finding, this is automatically a finding, as the system cannot implement FIPS 140-2-approved cryptographic algorithms and hashes.
+-
+-The location of the "sshd_config" file may vary if a different daemon is in use.
+-
+-Inspect the "Ciphers" configuration with the following command:
+-
+-# grep -i ciphers /etc/ssh/sshd_config
+-Ciphers aes128-ctr,aes192-ctr,aes256-ctr
+-
+-If any ciphers other than "aes128-ctr", "aes192-ctr", or "aes256-ctr" are listed, the "Ciphers" keyword is missing, or the returned line is commented out, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>OL07-00-040160The Oracle Linux operating system must be configured so that all network connections associated with a communication session are terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements.<VulnDiscussion>Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. 
+-
+-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001133Configure the operating system to terminate all network connections associated with a communications session at the end of the session or after a period of inactivity.
+-
+-Create a script to enforce the inactivity timeout (for example /etc/profile.d/tmout.sh) such as:
+-
+-#!/bin/bash
+-
+-TMOUT=600
+-readonly TMOUT
+-export TMOUTVerify the operating system terminates all network connections associated with a communications session at the end of the session or based on inactivity.
+-
+-Check the value of the system inactivity timeout with the following command:
+-
+-# grep -i tmout /etc/profile.d/*
+-
+-etc/profile.d/tmout.sh:TMOUT=600
+-
+-/etc/profile.d/tmout.sh:readonly TMOUT
+-
+-/etc/profile.d/tmout.sh:export TMOUT
+-
+-If "TMOUT" is not set to "600" or less in a script located in the /etc/profile.d/ directory to enforce session termination after inactivity, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>OL07-00-040170The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner immediately prior to, or as part of, remote access logon prompts.<VulnDiscussion>Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+-
+-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+-
+-The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:
+-
+-"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."
+-
+-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007 , SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000048Configure the operating system 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.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:
+-
+-# grep -i 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.
+-
+-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.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>OL07-00-040180The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+-
+-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001453Configure the operating system to implement cryptography to protect the integrity of LDAP authentication sessions.
+-
+-Add or modify the following line in "/etc/sssd/sssd.conf":
+-
+-ldap_id_use_start_tls = trueIf LDAP is not being utilized, this requirement is Not Applicable.
+-
+-Verify the operating system implements cryptography to protect the integrity of remote LDAP authentication sessions.
+-
+-To determine if LDAP is being used for authentication, use the following command:
+-
+-# systemctl status sssd.service
+-sssd.service - System Security Services Daemon
+-Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
+-Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago
+-
+-If the "sssd.service" is "active", then LDAP is being used. To see if LDAP is configured to use TLS, use the following command:
+-
+-# grep -i "start_tls" /etc/sssd/sssd.conf
+-ldap_id_use_start_tls = true
+-
+-If the "ldap_id_use_start_tls" option is not "true", this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>OL07-00-040190The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+-
+-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001453Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
+-
+-Add or modify the following line in "/etc/sssd/sssd.conf":
+-
+-ldap_tls_reqcert = demandIf LDAP is not being utilized, this requirement is Not Applicable.
+-
+-Verify the operating system implements cryptography to protect the integrity of remote LDAP access sessions.
+-
+-To determine if LDAP is being used for authentication, use the following command:
+-
+-# systemctl status sssd.service
+-sssd.service - System Security Services Daemon
+-Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
+-Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago
+-
+-If the "sssd.service" is "active", then LDAP is being used. 
+-
+-Verify that the sssd service is configured to require the use of certificates:
+-
+-# grep -i tls_reqcert /etc/sssd/sssd.conf
+-ldap_tls_reqcert = demand
+-
+-If the "ldap_tls_reqcert" setting is missing, commented out, or does not exist, this is a finding.
+-
+-If the "ldap_tls_reqcert" setting is not set to "demand" or "hard", this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>OL07-00-040200The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+-
+-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001453Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
+-
+-Add or modify the following line in "/etc/sssd/sssd.conf":
+-
+-ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crtIf LDAP is not being utilized, this requirement is Not Applicable.
+-
+-Verify the operating system implements cryptography to protect the integrity of remote LDAP access sessions.
+-
+-To determine if LDAP is being used for authentication, use the following command:
+-
+-# systemctl status sssd.service
+-sssd.service - System Security Services Daemon
+-Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
+-Active: active (running) since Wed 2018-06-27 10:58:11 EST; 1h 50min ago
+-
+-If the "sssd.service" is "active", then LDAP is being used.
+-
+-Check that the path to the X.509 certificate for peer authentication with the following command:
+-
+-# grep -i tls_cacert /etc/sssd/sssd.conf
+-
+-ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+-
+-Verify the "ldap_tls_cacert" option points to a file that contains the trusted CA certificate.
+-
+-If this file does not exist, or the option is commented out or missing, this is a finding.SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>OL07-00-040201The Oracle Linux operating system must implement virtual address space randomization.<VulnDiscussion>Address space layout randomization (ASLR) makes it more difficult for an attacker to predict the location of attack code introduced into a process's address space during an attempt at exploitation. Additionally, ASLR also makes it more difficult for an attacker to know the location of existing code in order to repurpose it using return-oriented programming (ROP) techniques.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002824Configure the operating system implement virtual address space randomization.
+-
+-Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a config file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-kernel.randomize_va_space = 2
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the operating system implements virtual address space randomization.
+-
+-# grep kernel.randomize_va_space /etc/sysctl.conf /etc/sysctl.d/*
+-
+-kernel.randomize_va_space = 2
+-
+-If "kernel.randomize_va_space" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or does not have a value of "2", this is a finding.
+-
+-Check that the operating system implements virtual address space randomization with the following command:
+-
+-# /sbin/sysctl -a | grep kernel.randomize_va_space 
+-
+-kernel.randomize_va_space = 2
+-
+-If "kernel.randomize_va_space" does not have a value of "2", this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>OL07-00-040300The Oracle Linux operating system must be configured so that all networked systems have SSH installed.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. 
+-
+-This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. 
+-
+-Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, logical means (cryptography) do not have to be employed, and vice versa.
+-
+-Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002418CCI-002420CCI-002422Install SSH packages onto the host with the following commands:
+-
+-# yum install openssh-server.x86_64Check to see if sshd is installed with the following command:
+-
+-# yum list installed \*ssh\*
+-libssh2.x86_64 1.4.3-8.el7 @anaconda/7.1
+-openssh.x86_64 6.6.1p1-11.el7 @anaconda/7.1
+-openssh-server.x86_64 6.6.1p1-11.el7 @anaconda/7.1
+-
+-If the "SSH server" package is not installed, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>OL07-00-040310The Oracle Linux operating system must be configured so that all networked systems use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission.<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. 
+-
+-This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. 
+-
+-Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.
+-
+-Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002418Configure the SSH service to automatically start after reboot with the following command:
+-
+-# systemctl enable sshd.serviceVerify SSH is loaded and active with the following command:
+-
+-# 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.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>OL07-00-040320The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.<VulnDiscussion>Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
+-
+-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
+-
+-Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001133CCI-002361Configure the operating system to terminate a user session automatically after inactivity time-outs have expired or at shutdown.
+-
+-Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (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):
+-
+-ClientAliveInterval 600
+-
+-The SSH service must be restarted for changes to take effect.Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
+-
+-Check for the value of the "ClientAliveInterval" keyword with the following command:
+-
+-# grep -iw clientaliveinterval /etc/ssh/sshd_config
+-
+-ClientAliveInterval 600
+-
+-If "ClientAliveInterval" is not configured, commented out, or has a value of "0", this is a finding.
+-
+-If "ClientAliveInterval" has a value that is greater than "600" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040330The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using RSA rhosts authentication.<VulnDiscussion>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the SSH daemon to not allow authentication using RSA rhosts authentication.
+-
+-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "no":
+-
+-RhostsRSAAuthentication no
+-
+-The SSH service must be restarted for changes to take effect.Check the version of the operating system with the following command:
+-
+-# cat /etc/oracle-release
+-
+-If the release is 7.4 or newer this requirement is Not Applicable.
+-
+-Verify the SSH daemon does not allow authentication using RSA rhosts authentication.
+-
+-To determine how the SSH daemon's "RhostsRSAAuthentication" option is set, run the following command:
+-
+-# grep RhostsRSAAuthentication /etc/ssh/sshd_config
+-RhostsRSAAuthentication no
+-
+-If the value is returned as "yes", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>OL07-00-040340The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic terminate after a period of inactivity.<VulnDiscussion>Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
+-
+-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
+-
+-Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001133Configure the operating system to terminate automatically a user session after inactivity time-outs have expired or at shutdown.
+-
+-Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (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):
+-
+-ClientAliveCountMax 0
+-
+-The SSH service must be restarted for changes to take effect.Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
+-
+-Check for the value of the "ClientAliveCountMax" keyword with the following command:
+-
+-# grep -i clientalivecount /etc/ssh/sshd_config
+-ClientAliveCountMax 0
+-
+-If "ClientAliveCountMax" is not set to "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040350The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using rhosts authentication.<VulnDiscussion>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the SSH daemon to not allow authentication using known hosts authentication.
+-
+-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":
+-
+-IgnoreRhosts yesVerify the SSH daemon does not allow authentication using known hosts authentication.
+-
+-To determine how the SSH daemon's "IgnoreRhosts" option is set, run the following command:
+-
+-# grep -i IgnoreRhosts /etc/ssh/sshd_config
+-
+-IgnoreRhosts yes
+-
+-If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040360The Oracle Linux operating system must display the date and time of the last successful account logon upon an SSH logon.<VulnDiscussion>Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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) (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.Verify SSH provides users with feedback on when account accesses last occurred.
+-
+-Check that "PrintLastLog" keyword in the sshd daemon configuration file is used and set to "yes" with the following command:
+-
+-# grep -i 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040370The Oracle Linux operating system must not permit direct logons to the root account using remote access via SSH.<VulnDiscussion>Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure SSH to stop users from logging on remotely as the root user.
+-
+-Edit the appropriate "/etc/ssh/sshd_config" file to uncomment or add the line for the "PermitRootLogin" 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):
+-
+-PermitRootLogin no
+-
+-The SSH service must be restarted for changes to take effect.Verify remote access using SSH prevents users from logging on directly as root.
+-
+-Check that SSH prevents users from logging on directly as root with the following command:
+-
+-# grep -i 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040380The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using known hosts authentication.<VulnDiscussion>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the SSH daemon to not allow authentication using known hosts authentication.
+-
+-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":
+-
+-IgnoreUserKnownHosts yes
+-
+-The SSH service must be restarted for changes to take effect.Verify the SSH daemon does not allow authentication using known hosts authentication.
+-
+-To determine how the SSH daemon's "IgnoreUserKnownHosts" option is set, run the following command:
+-
+-# grep -i 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.SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>OL07-00-040390The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use the SSHv2 protocol.<VulnDiscussion>SSHv1 is an insecure implementation of the SSH protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immediate root access to the system.
+-
+-Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000197Remove all Protocol lines that reference version "1" in "/etc/ssh/sshd_config" (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). The "Protocol" line must be as follows:
+-
+-Protocol 2
+-
+-The SSH service must be restarted for changes to take effect.Check the version of the operating system with the following command:
+-
+-# cat /etc/oracle-release
+-
+-If the release is 7.4 or newer this requirement is Not Applicable.
+-
+-Verify the SSH daemon is configured to only use the SSHv2 protocol.
+-
+-Check that the SSH daemon is configured to only use the SSHv2 protocol with the following command:
+-
+-# grep -i protocol /etc/ssh/sshd_config
+-Protocol 2
+-#Protocol 1,2
+-
+-If any protocol line other than "Protocol 2" is uncommented, this is a finding.SRG-OS-000250-GPOS-00093<GroupDescription></GroupDescription>OL07-00-040400The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.<VulnDiscussion>DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement is SHA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001453Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "MACs" keyword and set its value to "hmac-sha2-256" and/or "hmac-sha2-512" (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):
+-
+-MACs hmac-sha2-256,hmac-sha2-512
+-
+-The SSH service must be restarted for changes to take effect.Verify the SSH daemon is configured to only use MACs employing FIPS 140-2-approved ciphers.
+-
+-Note: If OL07-00-021350 is a finding, this is automatically a finding, as the system cannot implement FIPS 140-2-approved cryptographic algorithms and hashes.
+-
+-Check that the SSH daemon is configured to only use MACs employing FIPS 140-2-approved ciphers with the following command:
+-
+-# grep -i macs /etc/ssh/sshd_config
+-MACs hmac-sha2-256,hmac-sha2-512
+-
+-If any ciphers other than "hmac-sha2-256" or "hmac-sha2-512" are listed or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040410The Oracle Linux operating system must be configured so that the SSH public host key files have mode 0644 or less permissive.<VulnDiscussion>If a public host key file is modified by an unauthorized user, the SSH service may be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Note: SSH public key files may be found in other directories on the system depending on the installation. 
+-
+-Change the mode of public host key files under "/etc/ssh" to "0644" with the following command:
+-
+-# chmod 0644 /etc/ssh/*.key.pubVerify the SSH public host key files have mode 0644 or less permissive.
+-
+-Note: SSH public key files may be found in other directories on the system depending on the installation.
+-
+-The following command will find all SSH public key files on the system:
+-
+-# find /etc/ssh -name '*.pub' -exec ls -lL {} \;
+-
+--rw-r--r-- 1 root root 618 Nov 28 06:43 ssh_host_dsa_key.pub
+--rw-r--r-- 1 root root 347 Nov 28 06:43 ssh_host_key.pub
+--rw-r--r-- 1 root root 238 Nov 28 06:43 ssh_host_rsa_key.pub
+-
+-If any file has a mode more permissive than 0644, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040420The Oracle Linux operating system must be configured so that the SSH private host key files have mode 0640 or less permissive.<VulnDiscussion>If an unauthorized user obtains the private SSH host key file, the host could be impersonated.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the mode of SSH private host key files under "/etc/ssh" to "0640" with the following command:
+-
+-# chmod 0640 /path/to/file/ssh_host*keyVerify the SSH private host key files have mode 0640 or less permissive.
+-
+-The following command will find all SSH private key files on the system and list their modes:
+-
+-# find / -name '*ssh_host*key' | xargs ls -lL
+-
+--rw-r----- 1 root ssh_keys 668 Nov 28 06:43 ssh_host_dsa_key
+--rw-r----- 1 root ssh_keys 582 Nov 28 06:43 ssh_host_key
+--rw-r----- 1 root ssh_keys 887 Nov 28 06:43 ssh_host_rsa_key
+-
+-If any file has a mode more permissive than 0640, this is a finding.SRG-OS-000364-GPOS-00151<GroupDescription></GroupDescription>OL07-00-040430The Oracle Linux operating system must be configured so that the SSH daemon does not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed.<VulnDiscussion>GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing the attack surface of the system. GSSAPI authentication must be disabled unless needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001813Uncomment the "GSSAPIAuthentication" keyword in "/etc/ssh/sshd_config" (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) and set the value to "no": 
+-
+-GSSAPIAuthentication no
+-
+-The SSH service must be restarted for changes to take effect.
+-
+-If GSSAPI authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.Verify the SSH daemon does not permit GSSAPI authentication unless approved.
+-
+-Check that the SSH daemon does not permit GSSAPI authentication with the following command:
+-
+-# grep -i gssapiauth /etc/ssh/sshd_config
+-GSSAPIAuthentication no
+-
+-If the "GSSAPIAuthentication" keyword is missing, is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.SRG-OS-000364-GPOS-00151<GroupDescription></GroupDescription>OL07-00-040440The Oracle Linux operating system must be configured so that the SSH daemon does not permit Kerberos authentication unless needed.<VulnDiscussion>Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Vulnerabilities in the system's Kerberos implementation may then be subject to exploitation. To reduce the attack surface of the system, the Kerberos authentication mechanism within SSH must be disabled for systems not using this capability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001813Uncomment the "KerberosAuthentication" keyword in "/etc/ssh/sshd_config" (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) and set the value to "no":
+-
+-KerberosAuthentication no
+-
+-The SSH service must be restarted for changes to take effect.
+-
+-If Kerberos authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.Verify the SSH daemon does not permit Kerberos to authenticate passwords unless approved.
+-
+-Check that the SSH daemon does not permit Kerberos to authenticate passwords with the following command:
+-
+-# grep -i kerberosauth /etc/ssh/sshd_config
+-KerberosAuthentication no
+-
+-If the "KerberosAuthentication" keyword is missing, or is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040450The Oracle Linux operating system must be configured so that the SSH daemon performs strict mode checking of home directory configuration files.<VulnDiscussion>If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Uncomment the "StrictModes" keyword in "/etc/ssh/sshd_config" (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) and set the value to "yes":
+-
+-StrictModes yes
+-
+-The SSH service must be restarted for changes to take effect.Verify the SSH daemon performs strict mode checking of home directory configuration files.
+-
+-The location of the "sshd_config" file may vary if a different daemon is in use.
+-
+-Inspect the "sshd_config" file with the following command:
+-
+-# grep -i strictmodes /etc/ssh/sshd_config
+-
+-StrictModes yes
+-
+-If "StrictModes" is set to "no", is missing, or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040460The Oracle Linux operating system must be configured so that the SSH daemon uses privilege separation.<VulnDiscussion>SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabilities in the unprivileged section.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Uncomment the "UsePrivilegeSeparation" keyword in "/etc/ssh/sshd_config" (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) and set the value to "sandbox" or "yes":
+-
+-UsePrivilegeSeparation sandbox
+-
+-The SSH service must be restarted for changes to take effect.Verify the SSH daemon performs privilege separation.
+-
+-Check that the SSH daemon performs privilege separation with the following command:
+-
+-# grep -i usepriv /etc/ssh/sshd_config
+-
+-UsePrivilegeSeparation sandbox
+-
+-If the "UsePrivilegeSeparation" keyword is set to "no", is missing, or the returned line is commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040470The Oracle Linux operating system must be configured so that the SSH daemon does not allow compression or only allows compression after successful authentication.<VulnDiscussion>If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Uncomment the "Compression" keyword in "/etc/ssh/sshd_config" (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) on the system and set the value to "delayed" or "no":
+-
+-Compression no
+-
+-The SSH service must be restarted for changes to take effect.Verify the SSH daemon performs compression after a user successfully authenticates.
+-
+-Check that the SSH daemon performs compression after a user successfully authenticates with the following command:
+-
+-# grep -i compression /etc/ssh/sshd_config
+-Compression delayed
+-
+-If the "Compression" keyword is set to "yes", is missing, or the returned line is commented out, this is a finding.SRG-OS-000399-GPOS-00178<GroupDescription></GroupDescription>OL07-00-040480The operating system must request and perform data origin authentication verification and data integrity verification on the name/address resolution responses the system receives from authoritative sources.<VulnDiscussion>If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed, which would result in query failure or DoS. Data origin authentication must be performed to thwart these types of attacks.
+-
+-Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity of response data.
+-
+-This is not applicable if DNSSEC is not implemented on the local network.
+-
+-Satisfies: SRG-OS-000399-GPOS-00178, SRG-OS-000400-GPOS-00179, SRG-OS-000401-GPOS-00180, SRG-OS-000402-GPOS-00181</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002465CCI-002466CCI-002467CCI-002468Configure the operating system to implement DNSSEC to protect the integrity of name/address resolution.
+-
+-Install the unbound package:
+-# yum install unbound
+-
+-To ensure unbound starts up every time the system boots, run the following command:
+-# systemctl enable unboundVerify the operating system implements DNSSEC to protect the integrity of name/address resolution.
+-
+-Determine if the package "unbound" is installed via the following command:
+-# yum info unbound
+-
+-If unbound is not installed, this is a finding.
+-
+-If "unbound" is installed, determine whether the unbound daemon is running; enter the following command: 
+-# systemctl status unbound | grep Active
+-
+-If the output does not indicate the daemon is "active", this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>OL07-00-040500The Oracle Linux operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).<VulnDiscussion>Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
+-
+-Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.
+-
+-Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).
+-
+-Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000356-GPOS-00144</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001891CCI-002046Edit the "/etc/ntp.conf" file and add or update an entry to define "maxpoll" to "10" as follows:
+-
+-server 0.rhel.pool.ntp.org iburst maxpoll 10
+-
+-If NTP was running and "maxpoll" was updated, the NTP service must be restarted:
+-
+-# systemctl restart ntpd
+-
+-If NTP was not running, it must be started:
+-
+-# systemctl start ntpdCheck to see if NTP is running in continuous mode.
+-
+-# ps -ef | grep ntp
+-
+-If NTP is not running, this is a finding.
+-
+-If the process is found, then check the "ntp.conf" file for the "maxpoll" option setting:
+-
+-# grep maxpoll /etc/ntp.conf
+-server 0.rhel.pool.ntp.org iburst maxpoll 10
+-
+-If the option is set to "17" or is not set, this is a finding.
+-
+-If the file does not exist, check the "/etc/cron.daily" subdirectory for a crontab file controlling the execution of the "ntpd -q" command.
+-
+-# grep -i "ntpd -q" /etc/cron.daily/*
+-# ls -al /etc/cron.* | grep ntp
+-ntp
+-
+-If a crontab file does not exist in the "/etc/cron.daily" that executes the "ntpd -q" command, this is a finding.SRG-OS-000420-GPOS-00186<GroupDescription></GroupDescription>OL07-00-040510The Oracle Linux operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces.<VulnDiscussion>DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.
+-
+-This requirement addresses the configuration of the operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exists to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002385Set the system to implement rate-limiting measures by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.tcp_invalid_ratelimit = 500 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the operating system protects against or limits the effects of DoS attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
+-
+-# grep 'net.ipv4.tcp_invalid_ratelimit' /etc/sysctl.conf /etc/sysctl.d/*
+-
+-/etc/sysctl.conf:net.ipv4.tcp_invalid_ratelimit = 500
+-
+-If "net.ipv4.tcp_invalid_ratelimit" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out this is a finding.
+-
+-Check that the operating system implements the value of the "tcp_invalid_ratelimit" variable with the following command:
+-
+-# /sbin/sysctl -a | grep 'net.ipv4.tcp_invalid_ratelimit'
+-net.ipv4.tcp_invalid_ratelimit = 500
+-
+-If "net.ipv4.tcp_invalid_ratelimit" has a value of "0", this is a finding.
+-
+-If "net.ipv4.tcp_invalid_ratelimit" has a value greater than "1000" and is not documented with the Information System Security Officer (ISSO), this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040520The Oracle Linux operating system must enable an application firewall, if available.<VulnDiscussion>Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network.
+-
+-Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00231, SRG-OS-000480-GPOS-00232</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Ensure the operating system's application firewall is enabled.
+-
+-Install the "firewalld" package, if it is not on the system, with the following command:
+-
+-# yum install firewalld
+-
+-Start the firewall via "systemctl" with the following command:
+-
+-# systemctl start firewalldVerify the operating system enabled an application firewall.
+-
+-Check to see if "firewalld" is installed with the following command:
+-
+-# yum list installed firewalld
+-firewalld-0.3.9-11.el7.noarch.rpm
+-
+-If the "firewalld" package is not installed, ask the System Administrator if another firewall application (such as iptables) is installed. 
+-
+-If an application firewall is not installed, this is a finding. 
+-
+-Check to see if the firewall is loaded and active with the following command:
+-
+-# systemctl status firewalld
+-firewalld.service - firewalld - dynamic firewall daemon
+-
+-Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
+-Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago
+-
+-If "firewalld" does not show a status of "loaded" and "active", this is a finding. 
+-
+-Check the state of the firewall:
+-
+-# firewall-cmd --state 
+-running
+-
+-If "firewalld" does not show a state of "running", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040530The Oracle Linux operating system must display the date and time of the last successful account logon upon logon.<VulnDiscussion>Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system 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 showfailedVerify users are provided with feedback on when account accesses last occurred.
+-
+-Check that "pam_lastlog" is used and not silent with the following command:
+-
+-# grep pam_lastlog /etc/pam.d/postlogin
+-session required pam_lastlog.so showfailed
+-
+-If "pam_lastlog" is missing from "/etc/pam.d/postlogin" file, or the silent option is present, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040540The Oracle Linux operating system must not contain .shosts files.<VulnDiscussion>The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Remove any found ".shosts" files from the system.
+-
+-# rm /[path]/[to]/[file]/.shostsVerify there are no ".shosts" files on the system.
+-
+-Check the system for the existence of these files with the following command:
+-
+-# find / -name '*.shosts'
+-
+-If any ".shosts" files are found on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040550The Oracle Linux operating system must not contain shosts.equiv files.<VulnDiscussion>The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Remove any found "shosts.equiv" files from the system.
+-
+-# rm /[path]/[to]/[file]/shosts.equivVerify there are no "shosts.equiv" files on the system.
+-
+-Check the system for the existence of these files with the following command:
+-
+-# find / -name shosts.equiv
+-
+-If any "shosts.equiv" files are found on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040600At least two name servers must be configured for Oracle Linux operating systems using DNS resolution.<VulnDiscussion>To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the operating system to use two or more name servers for DNS resolution.
+-
+-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:
+-
+-# echo -n > /etc/resolv.conf
+-
+-And then make the file immutable with the following command:
+-
+-# chattr +i /etc/resolv.conf
+-
+-If the "/etc/resolv.conf" file must be mutable, the required configuration must be documented with the Information System Security Officer (ISSO) and the file must be verified by the system file integrity tool.Determine whether the system is using local or DNS name resolution with the following command:
+-
+-# 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:
+-
+-# 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:
+-
+-# grep nameserver /etc/resolv.conf
+-nameserver 192.168.1.2
+-nameserver 192.168.1.3
+-
+-If less than two lines are returned that are not commented out, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040610The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.all.accept_source_route = 0 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl -systemVerify the system does not accept IPv4 source-routed packets.
+-
+-# grep net.ipv4.conf.all.accept_source_route /etc/sysctl.conf /etc/sysctl.d/*
+-
+-net.ipv4.conf.all.accept_source_route = 0
+-
+-If "net.ipv4.conf.all.accept_source_route" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the accept source route variable with the following command:
+-
+-# /sbin/sysctl -a | grep 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", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040611The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible on all interfaces.<VulnDiscussion>Enabling reverse path filtering drops packets with invalid source addresses received on the interface.  It should not be used on systems which are routers for complicated networks, but is helpful for end hosts and routers serving small networks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.all.rp_filter = 1 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system uses a reverse-path filter for IPv4:
+-
+-# grep net.ipv4.conf.all.rp_filter /etc/sysctl.conf /etc/sysctl.d/*
+-net.ipv4.conf.all.rp_filter = 1
+-
+-If "net.ipv4.conf.all.rp_filter" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "1", this is a finding.
+-
+-Check that the operating system implements the accept source route variable with the following command:
+-
+-# /sbin/sysctl -a | grep net.ipv4.conf.all.rp_filter
+-net.ipv4.conf.all.rp_filter = 1
+-
+-If the returned line does not have a value of "1", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040612The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible by default.<VulnDiscussion>Enabling reverse path filtering drops packets with invalid source addresses received on the interface.  It should not be used on systems which are routers for complicated networks, but is helpful for end hosts and routers serving small networks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.default.rp_filter = 1 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system uses a reverse-path filter for IPv4:
+-
+-# grep net.ipv4.conf.default.rp_filter /etc/sysctl.conf /etc/sysctl.d/*
+-net.ipv4.conf.default.rp_filter = 1
+-
+-If "net.ipv4.conf.default.rp_filter" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "1", this is a finding.
+-
+-Check that the operating system implements the accept source route variable with the following command:
+-
+-# /sbin/sysctl -a | grep net.ipv4.conf.default.rp_filter
+-net.ipv4.conf.default.rp_filter = 1
+-
+-If the returned line does not have a value of "1", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040620The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.default.accept_source_route = 0 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system does not accept IPv4 source-routed packets by default.
+-
+-# grep net.ipv4.conf.default.accept_source_route /etc/sysctl.conf /etc/sysctl.d/*
+-net.ipv4.conf.default.accept_source_route = 0
+-
+-If "net.ipv4.conf.default.accept_source_route" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the accept source route variable with the following command:
+-
+-# /sbin/sysctl -a | grep 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", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040630The Oracle Linux operating system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.<VulnDiscussion>Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.icmp_echo_ignore_broadcasts = 1
+-
+-Issue the following command to make the changes take effect: 
+-
+-# sysctl --systemVerify the system does not respond to IPv4 ICMP echoes sent to a broadcast address.
+-
+-# grep net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf /etc/sysctl.d/*
+-
+-If "net.ipv4.icmp_echo_ignore_broadcasts" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "1", this is a finding.
+-
+-Check that the operating system implements the "icmp_echo_ignore_broadcasts" variable with the following command:
+-
+-# /sbin/sysctl -a | grep net.ipv4.icmp_echo_ignore_broadcasts
+-net.ipv4.icmp_echo_ignore_broadcasts = 1
+-
+-If the returned line does not have a value of "1", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040640The Oracle Linux operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to not accept IPv4 ICMP redirect messages by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.default.accept_redirects = 0 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system will not accept IPv4 ICMP redirect messages.
+-
+-# grep 'net.ipv4.conf.default.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*
+-
+-If "net.ipv4.conf.default.accept_redirects" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the value of the "accept_redirects" variables with the following command:
+-
+-# /sbin/sysctl -a | grep 'net.ipv4.conf.default.accept_redirects'
+-net.ipv4.conf.default.accept_redirects = 0
+-
+-If the returned line does not have a value of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040641The Oracle Linux operating system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to ignore IPv4 ICMP redirect messages by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.all.accept_redirects = 0 
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system ignores IPv4 ICMP redirect messages.
+-
+-# grep 'net.ipv4.conf.all.accept_redirects' /etc/sysctl.conf /etc/sysctl.d/*
+-
+-If "net.ipv4.conf.all.accept_redirects" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the "accept_redirects" variables with the following command:
+-
+-# /sbin/sysctl -a | grep 'net.ipv4.conf.all.accept_redirects'
+-
+-net.ipv4.conf.all.accept_redirects = 0
+-
+-If the returned line does not have a value of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040650The Oracle Linux operating system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the system not to allow interfaces to perform IPv4 ICMP redirects by default. 
+-
+-Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.default.send_redirects = 0
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system does not allow interfaces to perform IPv4 ICMP redirects by default.
+-
+-# grep 'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*
+-
+-If "net.ipv4.conf.default.send_redirects" is not configured in the "/etc/sysctl.conf" file or in the /etc/sysctl.d/ directory, is commented out or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the "default send_redirects" variables with the following command:
+-
+-# /sbin/sysctl -a | grep 'net.ipv4.conf.default.send_redirects'
+-
+-net.ipv4.conf.default.send_redirects = 0 
+-
+-If the returned line does not have a value of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040660The Oracle Linux operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.<VulnDiscussion>ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure the system not to allow interfaces to perform IPv4 ICMP redirects. 
+-
+-Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.conf.all.send_redirects = 0
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system does not send IPv4 ICMP redirect messages.
+-
+-# grep 'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf /etc/sysctl.d/*
+-
+-If "net.ipv4.conf.all.send_redirects" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the "all send_redirects" variables with the following command:
+-
+-# /sbin/sysctl -a | grep 'net.ipv4.conf.all.send_redirects'
+-
+-net.ipv4.conf.all.send_redirects = 0
+-
+-If the returned line does not have a value of "0", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040670Network interfaces configured on The Oracle Linux operating system must not be in promiscuous mode.<VulnDiscussion>Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access these applications, it may allow them to collect information such as logon IDs, passwords, and key exchanges between systems.
+-
+-If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information System Security Officer (ISSO) and restricted to authorized personnel only.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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:
+-
+-#ip link set dev <devicename> multicast off promisc offVerify network interfaces are not in promiscuous mode unless approved by the ISSO and documented.
+-
+-Check for the status with the following command:
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040680The Oracle Linux operating system must be configured to prevent unrestricted mail relaying.<VulnDiscussion>If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366If "postfix" is installed, modify the "/etc/postfix/main.cf" file to restrict client connections to the local network with the following command:
+-
+-# postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'Verify the system is configured to prevent unrestricted mail relaying.
+-
+-Determine if "postfix" is installed with the following commands:
+-
+-# yum list installed postfix
+-postfix-2.6.6-6.el7.x86_64.rpm 
+-
+-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:
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040690The Oracle Linux operating system must not have a File Transfer Protocol (FTP) server package installed unless needed.<VulnDiscussion>The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Document the "vsftpd" package with the ISSO as an operational requirement or remove it from the system with the following command:
+-
+-# yum remove vsftpdVerify an FTP server has not been installed on the system.
+-
+-Check to see if an FTP server has been installed with the following commands:
+-
+-# yum list installed vsftpd
+-
+-vsftpd-3.0.2.el7.x86_64.rpm
+-
+-If "vsftpd" is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040700The Oracle Linux operating system must not have the Trivial File Transfer Protocol (TFTP) server package installed if not required for operational support.<VulnDiscussion>If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Remove the TFTP package from the system with the following command:
+-
+-# yum remove tftp-serverVerify a TFTP server has not been installed on the system.
+-
+-Check to see if a TFTP server has been installed with the following command:
+-
+-# yum list installed tftp-server
+-tftp-server-0.49-9.el7.x86_64.rpm
+-
+-If TFTP is installed and the requirement for TFTP is not documented with the ISSO, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040710The Oracle Linux operating system must be configured so that remote X connections for interactive users are encrypted.<VulnDiscussion>Open X displays allow an attacker to capture keystrokes and execute commands remotely.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure SSH to encrypt connections for interactive users.
+-
+-Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" 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):
+-
+-X11Forwarding yes
+-
+-The SSH service must be restarted for changes to take effect:
+-
+-# systemctl restart sshdVerify remote X connections for interactive users are encrypted.
+-
+-Check that remote X connections are encrypted with the following command:
+-
+-# grep -i x11forwarding /etc/ssh/sshd_config | grep -v "^#"
+-
+-X11Forwarding yes
+-
+-If the "X11Forwarding" keyword is set to "no" or is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040720The Oracle Linux operating system must be configured so that if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon is configured to operate in secure mode.<VulnDiscussion>Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Configure 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/tftpbootVerify the TFTP daemon is configured to operate in secure mode.
+-
+-Check to see if a TFTP server has been installed with the following commands:
+-
+-# yum list installed tftp-server
+-tftp-server.x86_64 x.x-x.el7
+-
+-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: 
+-
+-# 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040730The Oracle Linux operating system must not have an X Windows display manager installed unless approved.<VulnDiscussion>Internet services not required for system or application processes must not be active to decrease the attack surface of the system. X Windows has a long history of security vulnerabilities and will not be used unless approved and documented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Document the requirement for an X Windows server with the ISSO or remove the related packages with the following commands:
+-
+-# rpm -e xorg-x11-server-commonVerify that if the system has X Windows System installed, it is authorized.
+-
+-Check for the X11 package with the following command:
+-
+-# rpm -qa | grep xorg | grep server
+-
+-Ask the System Administrator if use of the X Windows System is an operational requirement.
+-
+-If the use of X Windows on the system is not documented with the Information System Security Officer (ISSO), this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040740The Oracle Linux operating system must not be performing packet forwarding unless the system is a router.<VulnDiscussion>Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv4.ip_forward = 0
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemVerify the system is not performing packet forwarding, unless the system is a router.
+-
+-# grep net.ipv4.ip_forward /etc/sysctl.conf /etc/sysctl.d/*
+-
+-net.ipv4.ip_forward = 0
+-
+-If "net.ipv4.ip_forward" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out, or does not have a value of "0", this is a finding.
+-
+-Check that the operating system does not implement IP forwarding using the following command:
+-
+-# /sbin/sysctl -a | grep net.ipv4.ip_forward
+-net.ipv4.ip_forward = 0
+-
+-If IP forwarding value is "1" and the system is hosting any application, database, or web servers, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040750The Oracle Linux operating system must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS.<VulnDiscussion>When an NFS server is configured to use RPCSEC_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Update the "/etc/fstab" file so the option "sec" is defined for each NFS mounted file system and the "sec" option does not have the "sys" setting. 
+-
+-Ensure the "sec" option is defined as "krb5:krb5i:krb5p".Verify "AUTH_GSS" is being used to authenticate NFS mounts.
+-
+-To check if the system is importing an NFS file system, look for any entries in the "/etc/fstab" file that have a file system type of "nfs" with the following command:
+-
+-# cat /etc/fstab | grep nfs
+-192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p
+-
+-If the system is mounting file systems via NFS and has the sec option without the "krb5:krb5i:krb5p" settings, the "sec" option has the "sys" setting, or the "sec" option is missing, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040800SNMP community strings on the Oracle Linux operating system must be changed from the default.<VulnDiscussion>Whether active or not, default Simple Network Management Protocol (SNMP) community strings must be changed to maintain security. If the service is running with the default authenticators, anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system or network(s). It is highly recommended that SNMP version 3 user authentication and message encryption be used in place of the version 2 community strings.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366If the "/etc/snmp/snmpd.conf" file exists, modify any lines that contain a community string value of "public" or "private" to another string value.Verify that a system using SNMP is not using default community strings.
+-
+-Check to see if the "/etc/snmp/snmpd.conf" file exists with the following command:
+-
+-# ls -al /etc/snmp/snmpd.conf
+--rw------- 1 root root 52640 Mar 12 11:08 snmpd.conf
+-
+-If the file does not exist, this is Not Applicable.
+-
+-If the file does exist, check for the default community strings with the following commands:
+-
+-# grep public /etc/snmp/snmpd.conf
+-# grep private /etc/snmp/snmpd.conf
+-
+-If either of these commands returns any output, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040810The Oracle Linux operating system access control program must be configured to grant or deny system access to specific hosts and services.<VulnDiscussion>If the systems access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366If "firewalld" is installed and active on the system, configure rules for allowing specific services and hosts. 
+-
+-If "firewalld" is not "active", enable "tcpwrappers" by configuring "/etc/hosts.allow" and "/etc/hosts.deny" to allow or deny access to specific hosts.If the "firewalld" package is not installed, ask the System Administrator (SA) if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. 
+-
+-Verify the system's access control program is configured to grant or deny system access to specific hosts.
+-
+-Check to see if "firewalld" is active with the following command:
+-
+-# systemctl status firewalld
+-firewalld.service - firewalld - dynamic firewall daemon
+-Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
+-Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago
+-
+-If "firewalld" is active, check to see if it is configured to grant or deny access to specific hosts or services with the following commands:
+-
+-# firewall-cmd --get-default-zone
+-public
+-
+-# firewall-cmd --list-all --zone=public
+-public (active)
+-target: default
+-icmp-block-inversion: no
+-interfaces: eth0
+-sources:
+-services: mdns ssh
+-ports:
+-protocols:
+-masquerade: no
+-forward-ports:
+-icmp-blocks:
+-
+-If "firewalld" is not active, determine whether "tcpwrappers" is being used by checking whether the "hosts.allow" and "hosts.deny" files are empty with the following commands:
+-
+-# ls -al /etc/hosts.allow
+-rw-r----- 1 root root 9 Aug 2 23:13 /etc/hosts.allow
+-
+-# ls -al /etc/hosts.deny
+--rw-r----- 1 root root 9 Apr 9 2007 /etc/hosts.deny
+-
+-If "firewalld" and "tcpwrappers" are not installed, configured, and active, ask the SA if another access control program (such as iptables) is installed and active. Ask the SA to show that the running configuration grants or denies access to specific hosts or services.
+-
+-If "firewalld" is active and is not configured to grant access to specific hosts or "tcpwrappers" is not configured to grant or deny access to specific hosts, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040820The Oracle Linux operating system must not have unauthorized IP tunnels configured.<VulnDiscussion>IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the Information System Security Officer (ISSO).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Remove all unapproved tunnels from the system, or document them with the ISSO.Verify the system does not have unauthorized IP tunnels configured.
+-
+-Check to see if "libreswan" is installed with the following command:
+-
+-# yum list installed libreswan
+-libreswan.x86-64 3.20-5.el7_4
+-
+-If "libreswan" is installed, check to see if the "IPsec" service is active with the following command:
+-
+-# systemctl status ipsec
+-ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec
+-Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)
+-Active: inactive (dead)
+-
+-If the "IPsec" service is active, check to see if any tunnels are configured in "/etc/ipsec.conf" and "/etc/ipsec.d/" with the following commands:
+-
+-# grep -iw conn /etc/ipsec.conf /etc/ipsec.d/*.conf
+-
+-If there are indications that a "conn" parameter is configured for a tunnel, ask the System Administrator if the tunnel is documented with the ISSO. 
+-
+-If "libreswan" is installed, "IPsec" is active, and an undocumented tunnel is active, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-040830The Oracle Linux operating system must not forward IPv6 source-routed packets.<VulnDiscussion>Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Set the system to the required kernel parameter, if IPv6 is enabled, by adding the following line to "/etc/sysctl.conf" or a configuration file in the /etc/sysctl.d/ directory (or modify the line to have the required value):
+-
+-net.ipv6.conf.all.accept_source_route = 0
+-
+-Issue the following command to make the changes take effect:
+-
+-# sysctl --systemIf IPv6 is not enabled, the key will not exist, and this is Not Applicable.
+-
+-Verify the system does not accept IPv6 source-routed packets.
+-
+-# grep net.ipv6.conf.all.accept_source_route /etc/sysctl.conf /etc/sysctl.d/*
+-
+-net.ipv6.conf.all.accept_source_route = 0
+-
+-If "net.ipv6.conf.all.accept_source_route" is not configured in the /etc/sysctl.conf file or in the /etc/sysctl.d/ directory, is commented out or does not have a value of "0", this is a finding.
+-
+-Check that the operating system implements the accept source route variable with the following command:
+-
+-# /sbin/sysctl -a | grep net.ipv6.conf.all.accept_source_route
+-net.ipv6.conf.all.accept_source_route = 0
+-
+-If the returned lines do not have a value of "0", this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>OL07-00-041001The Oracle Linux operating system must have the required packages for multifactor authentication installed.<VulnDiscussion>Using an authentication device, such as a CAC or token separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+-
+-Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators, and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+-
+-A privileged account is defined as an information system account with authorizations of a privileged user.
+-
+-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+-
+-This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+-
+-Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000765CCI-001948CCI-001953Configure the operating system to implement multifactor authentication by installing the required packages.
+-
+-Install the "esc" and "pam_pkcs11" packages on the system with the following command:
+-
+-# yum install esc pam_pkcs11Verify the operating system has the packages required for multifactor authentication installed.
+-
+-Check for the presence of the packages required to support multifactor authentication with the following commands:
+-
+-# yum list installed esc
+-esc-1.1.0-26.el7.noarch.rpm
+-
+-# yum list installed pam_pkcs11
+-pam_pkcs11-0.6.2-14.el7.noarch.rpm
+-
+-
+-If the "esc" and "pam_pkcs11" packages are not installed, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>OL07-00-041002The Oracle Linux operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM).<VulnDiscussion>Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+-
+-Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+-
+-A privileged account is defined as an information system account with authorizations of a privileged user.
+-
+-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+-
+-This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+-
+-Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001948CCI-001953CCI-001954Configure the operating system to implement multifactor authentication for remote access to privileged accounts via pluggable authentication modules (PAM).
+-
+-Modify all of the services lines in "/etc/sssd/sssd.conf" or in configuration files found under "/etc/sssd/conf.d" to include pam.Verify the operating system implements multifactor authentication for remote access to privileged accounts via pluggable authentication modules (PAM).
+-
+-Check the "/etc/sssd/sssd.conf" file for the authentication services that are being used with the following command:
+-
+-# grep services /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf
+-
+-services = nss, pam
+-
+-If the "pam" service is not present on all "services" lines, this is a finding.SRG-OS-000375-GPOS-00160<GroupDescription></GroupDescription>OL07-00-041003The Oracle Linux operating system must implement certificate status checking for PKI authentication.<VulnDiscussion>Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+-
+-Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+-
+-A privileged account is defined as an information system account with authorizations of a privileged user.
+-
+-Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+-
+-This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+-
+-Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000377-GPOS-00162</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-001948CCI-001953CCI-001954Configure the operating system to do certificate status checking for PKI authentication.
+-
+-Modify all of the "cert_policy" lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "ocsp_on".Verify the operating system implements certificate status checking for PKI authentication.
+-
+-Check to see if Online Certificate Status Protocol (OCSP) is enabled on the system with the following command:
+-
+-# grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -v "^#"
+-
+-cert_policy = ca, ocsp_on, signature;
+-cert_policy = ca, ocsp_on, signature;
+-cert_policy = ca, ocsp_on, signature;
+-
+-There should be at least three lines returned. 
+-
+-If "ocsp_on" is not present in all uncommented "cert_policy" lines in "/etc/pam_pkcs11/pam_pkcs11.conf", this is a finding.SRG-OS-000424-GPOS-00188<GroupDescription></GroupDescription>OL07-00-041010The Oracle Linux operating system must be configured so that all wireless network adapters are disabled.<VulnDiscussion>The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious association and ad hoc networks will allow an attacker to spoof a wireless access point (AP), allowing validated systems to connect to the malicious AP, and enabling the attacker to monitor and record network traffic. These malicious APs can also serve to create a man-in-the-middle attack, or be used to create a denial of service to valid network resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002421Configure the system to disable all wireless network interfaces with the following command:
+-
+-#nmcli radio wifi offVerify that there are no wireless interfaces configured on the system.
+-
+-This is N/A for systems that do not have wireless network adapters.
+-
+-Check for the presence of active wireless interfaces with the following command:
+-
+-# nmcli device
+-DEVICE TYPE STATE
+-eth0 ethernet connected
+-wlp3s0 wifi disconnected
+-lo loopback unmanaged
+-
+-If a wireless interface is configured and its use on the system is not documented with the Information System Security Officer (ISSO), this is a finding.SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>OL07-00-910055The Oracle Linux operating system must protect audit information from unauthorized read, modification, or deletion.<VulnDiscussion>If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
+-
+-To ensure the veracity of audit information, the operating system must protect audit information from unauthorized modification.
+-
+-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.
+-
+-Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000206-GPOS-00084</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000162CCI-000163CCI-000164CCI-001314Change the mode of the audit log files with the following command: 
+-
+-# chmod 0600 [audit_file]
+-
+-Change the owner and group owner of the audit log files with the following command: 
+-
+-# chown root:root [audit_file]Verify the operating system audit records have proper permissions and ownership.
+-
+-List the full permissions and ownership of the audit log files with the following command.
+-
+-# ls -la /var/log/audit 
+-total 4512
+-drwx------. 2 root root 23 Apr 25 16:53 .
+-drwxr-xr-x. 17 root root 4096 Aug 9 13:09 ..
+--rw-------. 1 root root 8675309 Aug 9 12:54 audit.log
+-
+-Audit logs must be mode 0600 or less permissive. 
+-If any are more permissive, this is a finding.
+-
+-The owner and group owner of all audit log files must both be "root". If any other owner or group owner is listed, this is a finding.SRG-OS-000445-GPOS-00199<GroupDescription></GroupDescription>OL07-00-020210The Oracle Linux operating system must enable SELinux.<VulnDiscussion>Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.
+-
+-This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-002696Configure the operating system to verify correct operation of all security functions.
+-
+-Set the "SELinux" status and the "Enforcing" mode by modifying the "/etc/selinux/config" file to have the following line:
+-
+-SELINUX=enforcing
+-
+-A reboot is required for the changes to take effect.If an HBSS or HIPS is active on the system, this is Not Applicable.
+-
+-Verify the operating system verifies correct operation of all security functions.
+-
+-Check if "SELinux" is active and in "Enforcing" mode with the following command:
+-
+-# getenforce
+-Enforcing
+-
+-If "SELinux" is not active and not in "Enforcing" mode, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>OL07-00-010219The Oracle Linux operating system must be integrated into a directory service infrastructure.<VulnDiscussion>Enterprise environments make account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other errors.
+-
+-A comprehensive account management process that includes automation helps to ensure accounts designated as requiring attention are addressed consistently and promptly. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated. This requirement applies to all account types, including individual/user, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. Automated mechanisms may be composed of differing technologies that, when placed together, contain an overall automated mechanism supporting an organization's automated account management requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Oracle Linux 7DISADPMS TargetOracle Linux 72881CCI-000366Connect the operating system to a directory service infrastructure.Verify that the operating system has been integrated into a directory service infrastructure.
+-
+-With the assistance of the system administrator, validate that the operating system is using a directory services infrastructure for account management operations.
+-
+-If the operating system is not connected to a directory services infrastructure, this is a finding.
+\ No newline at end of file
+diff --git a/shared/references/disa-stig-ol7-v2r1-xccdf-manual.xml b/shared/references/disa-stig-ol7-v2r1-xccdf-manual.xml
+new file mode 100644
+index 0000000000..337f1520e5
+--- /dev/null
++++ b/shared/references/disa-stig-ol7-v2r1-xccdf-manual.xml
+@@ -0,0 +1,5072 @@
++acceptedOracle Linux 7 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 1 Benchmark Date: 23 Oct 20203.1.1.362251.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>