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:

This RFE is a follow-up of Private BZ 1623762 (https://bugzilla.redhat.com/show_bug.cgi?id=1623762).

Rules xccdf_org.ssgproject.content_rule_file_permissions_unauthorized_sgid and xccdf_org.ssgproject.content_rule_file_permissions_unauthorized_suid use a fixed whitelist for binaries having SGID respectively SUID capabilities.

If binary is not part of the whitelist, the rule will fail.

Since 3rd party packaged software may also provide such binaries, one should be able to amend these lists.

In particular, the description of the rules is quite misleading (xccdf_org.ssgproject.content_rule_file_permissions_unauthorized_sgid shown here):
"	
The SGID (set group id) bit should be set only on files that were installed via authorized means. A straightforward means of identifying unauthorized SGID files is determine if any were not installed as part of an RPM package, which is cryptographically verified. Investigate the origin of any unpackaged SGID files.
"

This description is very confusing, one can easily believe that the rule will only list unpackaged binaries, whereas it lists non-whitelisted binaries instead.


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

scap-security-guide-0.1.36-9.el7_5.noarch

*** This bug has been marked as a duplicate of bug 1693026 ***