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 1472499 - Tracking: Support for Atomic Harden feature in SCAP Security Guide
Summary: Tracking: Support for Atomic Harden feature in SCAP Security Guide
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: Matus Marhefka
Mirek Jahoda
Depends On:
Blocks: 1490353 1490384
TreeView+ depends on / blocked
Reported: 2017-07-18 23:42 UTC by Marek Haicman
Modified: 2018-04-10 12:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
"atomic scan" with "configuration_compliance" enables creating security-compliant container images at build time The `rhel7/openscap` container image now provides the "configuration_compliance" scan type. When used as an argument for the "atomic scan" command, this new scan type enables users to: * scan Red Hat Enterprise Linux-based container images and containers against any profile provided by the SCAP Security Guide (SSG) * remediate Red Hat Enterprise Linux-based container images to be compliant with any profile provided by the SSG * generate an HTML report from a scan or a remediation. The remediation results in a container image with an altered configuration that is added as a new layer on top of the original container image. Note that the original container image remains unchanged and only a new layer is created on top of it. The remediation process builds a new container image that contains all the configuration improvements. The content of this layer is defined by the security policy of scanning. This also means that the remediated container image is no longer signed by Red Hat, which is expected, since it differs from the original container image by containing the remediated layer.
Clone Of:
: 1490353 1490384 (view as bug list)
Last Closed: 2018-04-10 12:21:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0761 0 None None None 2018-04-10 12:21:55 UTC

Description Marek Haicman 2017-07-18 23:42:55 UTC
Description of problem:
We want SSG to support hardening of atomic container images at least according to main profiles:

- USGCB (ospp-rhel7)
- PCI-DSS (pci-dss)
- DISA STIG (stig-rhel7-disa)

Goal is to be able to harden container to state where all rules are passing.

Comment 10 errata-xmlrpc 2018-04-10 12:21:26 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.