Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Prior to this update, the remediation parts for certain rules in the PCI-DSS, DISA STIG, and USGCB SCAP Security Guide (SSG) profiles were missing or incorrect. Consequently, the rules failed to remediate the system. With this update, the remediation parts for these rules have been added or fixed, and the mentioned SSG profiles are now able to remediate the system.
Verified fixes in scap-security-guide-0.1.36-9.el7_5.noarch
Following rules are failing after installation by design (as automated remediation would be either complex, or is not possible at all):
xccdf_org.ssgproject.content_rule_ensure_gpgcheck_repo_metadata
xccdf_org.ssgproject.content_rule_install_mcafee_antivirus
xccdf_org.ssgproject.content_rule_bootloader_password
xccdf_org.ssgproject.content_rule_set_firewalld_default_zone
xccdf_org.ssgproject.content_rule_network_configure_name_resolution
These rules has been fixed:
xccdf_org.ssgproject.content_rule_partition_for_tmp
xccdf_org.ssgproject.content_rule_partition_for_var
xccdf_org.ssgproject.content_rule_partition_for_var_log_audit
xccdf_org.ssgproject.content_rule_partition_for_home
xccdf_org.ssgproject.content_rule_aide_scan_notification
xccdf_org.ssgproject.content_rule_mount_option_home_nosuid
xccdf_org.ssgproject.content_rule_sysctl_kernel_ipv6_disable
xccdf_org.ssgproject.content_rule_network_ipv6_disable_rpc
xccdf_org.ssgproject.content_rule_network_ipv6_privacy_extensions
xccdf_org.ssgproject.content_rule_auditd_data_retention_space_left_action
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_init
xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading_delete
xccdf_org.ssgproject.content_rule_ldap_client_start_tls
xccdf_org.ssgproject.content_rule_ensure_logrotate_activated
These are rules that are failing after installation, thus considered bugged:
xccdf_org.ssgproject.content_rule_grub2_enable_fips_mode *
xccdf_org.ssgproject.content_rule_audit_rules_privileged_commands
xccdf_org.ssgproject.content_rule_audit_rules_login_events
xccdf_org.ssgproject.content_rule_service_kdump_disabled *
xccdf_org.ssgproject.content_rule_sssd_enable_pam_services
xccdf_org.ssgproject.content_rule_chronyd_or_ntpd_set_maxpoll *
xccdf_org.ssgproject.content_rule_firewalld_sshd_port_enabled
* these can be remedied after installation, just won't be hardened from the get go
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:1410