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.

Currently OpenSCAP supports scanning for security vulnerabilities using the OVAL CVE feed format. This is also supported by Red Hat product security who release security feeds using CVE OVAL. See https://www.redhat.com/security/data/oval/

CVE OVAL served well in the past but it looks like most vendors (including Red Hat) are now moving to CVRF. See https://www.redhat.com/security/data/metrics/

There is a lot of synergy and similarities between the formats but CVRF allows more fine-grained metadata. Furthermore it isn't as strict when it comes to specifying how to actually scan for vulnerabilities. This sounds like a drawback but it allows us to scan JARs and maybe even other formats, not just RPM like CVE OVAL.

CVRF support in OpenSCAP would enable users of middle-ware and other Red Hat products to evaluate their infrastructure with minimal changes to OpenSCAP scripting. CVRF can fully replace OVAL CVE feed scanning in the future because it provides more contextual data. In addition we can enable scanning of non-RPM packages because CVRF doesn't specify how the evaluation should be done, this gives us implementation freedom to look into JAR, node.js, etc...

Even though some parts of CVRF support is present in latest shipped openscap package, openscap-1.2.17-2.el7.x86_64 there are currently no plans to polish it and introduce full fledged support of this format in RHEL7. Thus closing as won't fix.