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:

Rules

- xccdf_org.ssgproject.content_rule_file_permissions_ungroupowned
- xccdf_org.ssgproject.content_rule_no_files_unowned_by_user

may not work correctly if the system uses remote user/group backend s.a. LDAP.

Version-Release number of selected component (if applicable):

scap-security-guide-0.1.40-12.el7.noarch

Steps to Reproduce:

1. Scan a system where a remote user has their home directory

Actual results:

Scan will fail because of files in that directory, although they are legitimate.

Expected results:

Scan passes

Additional info:

The OVAL language that is the language behind checks in SCAP as of 4/2020 has no means how to query the system about remote groups that would work with appropriate LDAP configurations.
The only way how to address the issue right now is to document this limitation in the rule prose.

https://github.com/ComplianceAsCode/content/pull/5657

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-2020:3909