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.

Description of problem:
When user selects profile within anaconda, it is expected to have fully compliant system after installation. With the latest SCAP Security Guide, rules which are marked as "machine-only" are not remedied during installation. Thus machine is returned to user with lots of failing rules (for example all audit-related rules)

Version-Release number of selected component (if applicable):
oscap-anaconda-addon-0.7-15.el7

How reproducible:
reliably

Steps to Reproduce:
1. install machine with selecting hardening profile, for example pci-dss
2. scan machine with selected profile
3. check /root/openscap_data/eval_remediate_results.xml

Actual results:
2) big number of failing rules
3) big number of rules with result "notapplicable"

Expected results:
2) no, or small number of rules failing
3) no rule marked as "notapplicable"

Additional info:

This bug is more likely to be fixed in scap-security-guide.

PR https://github.com/OpenSCAP/oscap-anaconda-addon/pull/48 fixes the issue.

The real problem was OAA consuming XCCDF by default, and not using CPE shipped with SSG -> Our special 'cpe:/a:machine' has not been understood then.

By using DS, CPE dictionary bundled in is used, thus problem gets away.

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:1021