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.
Bug 2168072 - Two CIS Level 2 Benchmarks are listed in scap-security-guide under CIS Level 1 Profile [rhel-8.7.0.z]
Summary: Two CIS Level 2 Benchmarks are listed in scap-security-guide under CIS Level ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Milan Lysonek
URL:
Whiteboard:
Depends On: 2162803
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-08 07:10 UTC by RHEL Program Management Team
Modified: 2023-02-21 07:15 UTC (History)
5 users (show)

Fixed In Version: scap-security-guide-0.1.66-1.el8_7
Doc Type: Bug Fix
Doc Text:
Cause: Following rules were present in incorrect CIS profiles. kernel_module_udf_disabled, sudo_require_authentication and kernel_module_squashfs_disabled - were incorrectly placed in CIS Server Level 1 and CIS Workstation Level 1 - should be only in CIS Server Level 2 and CIS Workstation Level 2 package_libselinux_installed, grub2_enable_selinux, selinux_policytype, selinux_confinement_of_daemons, rsyslog_nolisten, service_systemd-journald_enabled - rules were added also to CIS Server Level 1 and to CIS Workstation Level 1 package_setroubleshoot_removed, package_mcstrans_removed - rules were added to CIS Server Level 1 Profiles cis, cis_server_l1, cis_workstation_1, and cis_workstation_l2 represent four possible variants of CIS benchmark. Consequence: When scanning a system with some variant of CIS profile, some rules could be left out or be checked in addition when compared to the CIS benchmark. Fix: Misaligned rules were assigned to correct CIS profile variants. No new rules were introduced and no rules were entirely removed. Result: SCAP CIS profiles should be better aligned with the original CIS benchmark.
Clone Of: 2162803
Environment:
Last Closed: 2023-02-21 07:15:08 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-147919 0 None None None 2023-02-08 07:11:54 UTC

Comment 13 errata-xmlrpc 2023-02-21 07:15:08 UTC 
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:0829
Note You need to log in before you can comment on or make changes to this bug.