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:
For rules that expect a specific configuration for audit, the scan is done on specific files, and not in all audit config file or /etc/audit/audit.rules that will be really used by auditctl.

Ex:

xccdf_org.ssgproject.content_rule_audit_immutable_login_uids

The rule requires --loginuid-immutable to be present in audit rule config.

It checks /etc/audit/rules.d/11-loginuid.rules and fails if --loginuid-immutable  is somewhere else.

Version-Release number of selected component (if applicable):
RHEL8
scap-security-guide-0.1.60-7.el8.noarch

How reproducible:
always

Steps to Reproduce:
1. put --loginuid-immutable in /etc/audit/rules.d/test_loginuid.rules
2. run oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_stig --rule xccdf_org.ssgproject.content_rule_audit_immutable_login_uids
3.

Actual results:
Test rule fails even if --loginuid-immutable is set

Expected results:
Test pass if --loginuid-immutable is set somewhere

Additional info:
Why the real used file used by auditctl /etc/audit/audit.rules is not used to check if the option is set ?

I have also to add that if the exact content of the sample file /usr/share/audit/sample-rules/11-loginuid.rules is not in the tested file, it fails also (the comment included ...)
I think only the required option should be tested.

Thanks !

Fixed upstream: https://github.com/ComplianceAsCode/content/pull/10070

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 (scap-security-guide bug fix and enhancement update), 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-2023:2869