Description of problem:
We want STIG profile aligned with official DISA STIG release. This alignment effort is tracked in upstream project https://github.com/OpenSCAP/scap-security-guide/projects/7
Is there a reason this bugzilla is marked private?
DISA STIG v1r4 is part of upstream version 0.1.40
Since this BZ is marked to be included in the RHEL 7.6 Release Notes, could you please write a draft of Doc Text using the template? Thank you.
Still getting caught up on this line:
"The profile now contains rules that match latest requirements by DISA for Red Hat Enterprise Linux 7 systems."
The phrase "latest requirements" will become outdated fast. DISA releases at a different cadence than RHEL and it's likely such statement will be accidentally misleading overtime. To +1 what Ted Brunell said, suggest dropping that sentence.
Thank you, Mirek! Looks good now.
[root@qeos-62 ~]# oscap info --profile xccdf_org.ssgproject.content_profile_stig-rhel7-disa /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
Document type: Source Data Stream
Title: DISA STIG for Red Hat Enterprise Linux 7
Description: This profile contains configuration checks that align to the DISA STIG for Red Hat Enterprise Linux V1R4. In addition to being applicable to RHEL7, DISA recognizes this configuration baseline as applicable to the operating system tier of Red Hat technologies that are based off RHEL7, such as: - Red Hat Enterprise Linux Server - Red Hat Enterprise Linux Workstation and Desktop - Red Hat Virtualization Hypervisor (RHV-H) - Red Hat Enterprise Linux for HPC - Red Hat Storage
Statistics (used STIG Viewer - imported v1r4, created checklist, loaded xccdf result file):
RHEL7.5 package result (in comparison to v1r4 xccdf from DISA)
unhardened: Open 72, Not a finding 34, Not reviewed 134
hardened: Open 8, Not a finding 98, Not reviewed 134
RHEL7.6 package result (in comparison to v1r4 xccdf from DISA)
unhardened: Open 145, Not a finding 65, Not reviewed 30
hardened: Open 16, Not a finding 194, Not reviewed 30
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.