Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionGanesh Payelkar
2022-07-22 00:03:35 UTC
Description of problem:
[RFE] Red Hat Satellite and Capsule 6 should have hardening support for standards such as DISA/CIS/STIG
satellite provides openscap to help ensure that managed nodes are in compliance with PCI-DSS / STIG and many other standards, it would be really nice if we could get compliance standards applied for Satellite itself.
Currently, we can install Red Hat Satellite 6 or Red Hat Satellite Capsule 6 on a FIPS-enabled RHEL system.
Does Red Hat Satellite 6 and Red Hat Satellite Capsule 6 support hardening?
https://access.redhat.com/solutions/3198782
The approach being taken to support this RFE is that Satellite deployments will support fapolicyd running, and, similar to our FIPS policy, will support the underlying OS meeting STIG standards. We are not, with this initial set of work, supporting the application meeting STIG standards just we do not support FIPS being enabled for each of the application services that compose Satellite. That is, just as we support FIPS-enabled RHEL we will support fapolicyd-enabled RHEL. If users need additional requirements on top of this that would apply to the application layers then those should be raised as a separate RFE to consider.
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 (Important: Satellite 6.15.0 release), 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/RHSA-2024:2010