Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

>> Default RHEL 7 scap policy not working as expected.

>> Set Boot Loader Password for a host is not working as expected.
 Shows as Items found violating "/boot/grub2/grub.cfg does not exists"
 But the file seems to be present and with correct permissions.

Version-Release number of selected component (if applicable):
>> openscap-1.2.16-6.el7.x86_64

How reproducible:
>> Create a new scap policy with profile:C2S for Red Hat Enterprise Linux 7.

Steps to Reproduce:
1.Create a new policy.
2.Assign to the host.
3.Run the compliance report.

Actual results:
>> It shows risk of high severity "xccdf_org.ssgproject.content".


Expected results:
It should not show the severity as the bootloader password is set.

Additional info:
NA.

Created attachment 1423971 [details]
error_screenshot

Thank you for reporting this, however this is not a problem with Sat6 but rather how openscap evaluates the given rule. Therefore I will move this to a different component.

*** Bug 1576874 has been marked as a duplicate of this bug. ***

Hello,

I see in SOS report that "superusers" in /boot/grub2/grub.cf is set to "root", and although Rule "bootloader_password" recommends to not use common names as superuser (i.e. root, admin, administrator), it is actually required that they are not root, nor admin nor administrator.

Please, try to set a different superuser account name, and scan again.

I'm closing this, if the problem persists, please reopen.