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 1678249 - content has to be SCAP 1.2 conformant
Summary: content has to be SCAP 1.2 conformant
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 8.0
Assignee: Watson Yuuma Sato
QA Contact: Gabriel Gaspar Becker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-18 11:11 UTC by Marek Haicman
Modified: 2019-06-14 00:48 UTC (History)
8 users (show)

Fixed In Version: scap-security-guide-0.1.42-11.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 00:48:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ComplianceAsCode content pull 3808 0 None closed Add RHEL8 CCEs and fix other CCEs and SEVs 2020-10-07 13:04:00 UTC

Description Marek Haicman 2019-02-18 11:11:50 UTC 
Description of problem:
Common Configuration Enumeration (CCE) identifier connects particular rule to general idea about configuration. For both RHEL6 and RHEL7, there are CCEs, for RHEL8 content, there are none. As CCE might be use to understand what is being tested, it should be available for RHEL8 as well.

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

How reproducible:
reliably

Steps to Reproduce:
1. look into the HTML guide associated with the profile
2. pick any rule
3.

Actual results:
no CCE identifier

Expected results:
CCE identifier

Additional info:
Comment 2 Shawn Wells 2019-02-18 13:19:44 UTC 
Saw a private comment about asking NIST process to get CCEs.

Process is for US Government team to EMail and ask for them ;)

Do we need more?
Comment 3 Shawn Wells 2019-02-18 13:20:31 UTC 
e.g. 

$ wc -l ComplianceAsCode/content/shared/references/cce-rhel-avail.txt
506
Comment 4 Shawn Wells 2019-02-18 13:26:07 UTC 
Marek, what needs to happen to ensure that CCEs are included in content shipping in RHEL 8 GA?
Comment 5 Shawn Wells 2019-02-19 23:56:24 UTC 
This has been fixed upstream through https://github.com/ComplianceAsCode/content/pull/3808
Comment 7 Shawn Wells 2019-03-01 16:01:55 UTC 
The various US Government security baselines, such as the NIST National Checklist program, require SCAP 1.2 specification adherence. 

Part of that means including CCEs and passing the SCAP 1.2 validation test suite. NIST has notified Red Hat currently the content does not pass (as of 1-MAR-2019).

Broader ask is to include CCEs, but also ensure RHEL 8.0 GA content has SCAP 1.2 conformance.
Comment 9 Watson Yuuma Sato 2019-03-05 16:47:54 UTC 
Contents shipped in scap-security-guide are not SCAP 1.2 compliant because they are built using OVAL 5.11.
To strictly be SCAP 1.2 compliant the contents need to be built with OVAL 5.10.

Upstream and RHEL8 contents, when built with OVAL 5.10, pass SCAP 1.2 validation with scapval-1.2 and scapval-1.3.2.
Comment 10 Watson Yuuma Sato 2019-03-05 16:57:48 UTC 
Shawn, which contents have NIST evaluated that failed SCAP 1.2?
If there were any issues with RHV4 or RHOSP13, https://github.com/ComplianceAsCode/content/pull/4053 should have fixed it.
Comment 12 Shawn Wells 2019-03-05 19:32:09 UTC 
(In reply to Watson Yuuma Sato from comment #10)
> Shawn, which contents have NIST evaluated that failed SCAP 1.2?
> If there were any issues with RHV4 or RHOSP13,
> https://github.com/ComplianceAsCode/content/pull/4053 should have fixed it.

Have only uploaded to NIST the RHEL 7 and OCP content at this point.
Note You need to log in before you can comment on or make changes to this bug.