Bug 2236247

Summary:	New check content_rule_ensure_pam_wheel_group_empty unknown what is wrong
Product:	Red Hat Enterprise Linux 8	Reporter:	Rajesh Dulhani <rdulhani>
Component:	scap-security-guide	Assignee:	Vojtech Polasek <vpolasek>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	ekolesni, ggasparb, matyc, mhaicman, mlysonek, mmarhefk
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-01 08:52:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rajesh Dulhani 2023-08-30 19:34:37 UTC

Description of problem:

In the latest scap-security-guide 0.1.69 there is a new check xccdf_org.ssgproject.content_rule_ensure_pam_wheel_group_empty that has no clear guidinace what is wrong. It just displays the /etc/group and that is it. There is no further guidance what is wrong or missing in the /etc/group with it.

I have the idea this check is a Sub-check of 	xccdf_org.ssgproject.content_rule_ensure_pam_wheel_group_empty and has to be ignored if this parent check to use the pam_wheel for su is not used.


Version-Release number of selected component (if applicable):
scap-security-guide 0.1.69


Actual results:
New strange Compliance failure without a clue what to do


Expected results:
Provide a clue what action should be taken

Additional info:

Comment 2 Matěj Týč 2023-08-31 12:11:15 UTC

Moving to the relevant component

Comment 3 RHEL Program Management 2023-08-31 12:13:29 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-01 08:52:39 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.

Users watching this BZ may not be automatically added to the Jira ticket.  Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.