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.
Bug 1571312 - Some rules in PCI-DSS, DISA STIG and USGCB Profile fail to remediate [rhel-7.5.z]
Summary: Some rules in PCI-DSS, DISA STIG and USGCB Profile fail to remediate [rhel-7....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: Marek Haicman
Mirek Jahoda
URL:
Whiteboard:
Depends On: 1570802
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-24 13:46 UTC by Oneata Mircea Teodor
Modified: 2018-05-14 16:13 UTC (History)
6 users (show)

Fixed In Version: scap-security-guide-0.1.36-8.el7_5
Doc Type: Bug Fix
Doc Text:
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.
Clone Of: 1570802
Environment:
Last Closed: 2018-05-14 16:13:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
state of machine after selecting profile within anaconda (517.03 KB, application/x-gzip)
2018-04-30 09:59 UTC, Marek Haicman 		no flags Details
state of machine after running remediation after boot (511.73 KB, application/x-gzip)
2018-04-30 10:01 UTC, Marek Haicman 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1410 0 None None None 2018-05-14 16:13:55 UTC

Description Oneata Mircea Teodor 2018-04-24 13:46:52 UTC 
This bug has been copied from bug #1570802 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 2 Fedora Update System 2018-04-24 16:33:01 UTC 
dpdk-17.11.2-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c965abb15
Comment 3 Fedora Update System 2018-04-26 04:51:34 UTC 
dpdk-17.11.2-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c965abb15
Comment 4 Marek Haicman 2018-04-26 12:28:21 UTC 
This is not a dpdk bug, reverting status change.
Comment 6 Marek Haicman 2018-04-30 09:56:00 UTC 
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
Comment 7 Marek Haicman 2018-04-30 09:59:40 UTC 
Created attachment 1428736 [details]
state of machine after selecting profile within anaconda
Comment 8 Marek Haicman 2018-04-30 10:01:00 UTC 
Created attachment 1428737 [details]
state of machine after running remediation after boot
Comment 11 errata-xmlrpc 2018-05-14 16:13:49 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.