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.

Bug 1755447

Summary: DISA STIG profile for RHEL-8
Product: Red Hat Enterprise Linux 8 Reporter: amitkuma
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Jan Černý <jcerny>
Severity: urgent Docs Contact: Jan Fiala <jafiala>
Priority: high    
Version: 8.4CC: awestbro, brian.hoppus, bwelterl, danclark, eddiecarswell13, ggasparb, gkeegan, jafiala, jcerny, lmiksik, mhaicman, mjahoda, mmarhefk, mthacker, posttoashok, pvrabec, rmullett, ross.marullo, terry.bartholomew.ctr, wrydberg, wsato
Target Milestone: rcKeywords: FutureFeature
Target Release: 8.0Flags: jafiala: needinfo+
pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.48-6.el8 Doc Type: Enhancement
Doc Text:
.RHEL 8 now contains the DISA STIG profile Security Technical Implementation Guides (STIG) are a set of baseline recommendations published by the Defense Information Systems Agency (DISA) to harden the security of information systems and software that might otherwise be vulnerable. This release includes the profile and Kickstart file for this security policy. With this enhancement, users can check systems for compliance, remediate systems to be compliant, and install systems compliant with DISA STIG for Red Hat Enterprise Linux 8.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 15:30:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description amitkuma 2019-09-25 14:14:33 UTC
Description of problem:

RHEL-8 does not contain DISA STIG profile separately.

# oscap info --profiles ssg-rhel8-ds.xml
xccdf_org.ssgproject.content_profile_ospp:Protection Profile for General Purpose Operating Systems
xccdf_org.ssgproject.content_profile_pci-dss:PCI-DSS v3.2.1 Control Baseline for Red Hat Enterprise Linux 

But some rules in ssg-rhel8-ds.xml are written with DISA STIG in mind example:
1. xccdf_org.ssgproject.content_rule_audit_rules_unsuccessful_file_modification
2. xccdf_org.ssgproject.content_rule_audit_rules_kernel_module_loading
etc

a. Being said, DISA STIG is more of a derivative of the OSPP profile, Can customer's use OSPP for hardening systems for DISA-STIG standards?
b. if ospp is being worked on to make DISA STIG complaint
    -> In which RHEL version, scap-security-guide version(Current version:0.1.46-1.el8) OSPP profile will contain all rules defined by DISA STIG standards?
c. Or Can we say current scap-security-guide(scap-security-guide-0.1.42-11.el8.noarch.rpm) is fully DISA STIG complaint, If customers harden their system with ospp, their systems are DISA STIG complaint?

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.42-11.el8.noarch.rpm

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
RHEL-8 should contain a DISA-STIG complaint profile

Additional info:

Comment 25 errata-xmlrpc 2020-04-28 15:30:41 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.

https://access.redhat.com/errata/RHBA-2020:1583