Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1962624 - [RFE] OVAL / CVE Reporting Support - Tech Preview MVP
Summary: [RFE] OVAL / CVE Reporting Support - Tech Preview MVP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-20 12:14 UTC by Marek Hulan
Modified: 2021-11-16 14:11 UTC (History)
3 users (show)

Fixed In Version: rubygem-foreman_scap_client-0.5.0, tfm-rubygem-smart_proxy_openscap-0.9.0, tfm-rubygem-foreman_openscap-4.3.2, ansiblerole-foreman_scap_client-0.2.0
Doc Type: Technology Preview
Doc Text:
Package(s) providing the Technology Preview: foreman_opescap Description of the Technology Preview: The foreman_openscap contains the API the upload the OVAL content which can be used to trigger the OVAL oscap scans. The results are parsed for CVEs and sent to Satellite which can then render the report of hosts and their CVEs. There's currently no UI for this functionality.
Clone Of:
Environment:
Last Closed: 2021-11-16 14:11:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:11:08 UTC

Description Marek Hulan 2021-05-20 12:14:24 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Evgeni Golov 2021-06-17 09:17:52 UTC 
foreman_openscap still needs a build
Comment 6 Jameer Pathan 2021-08-11 14:01:58 UTC 
Verified:

Verified with:
- Satellite 6.10.0 snap 12
- tfm-rubygem-openscap-0.4.9-5.el7sat.noarch
- tfm-rubygem-smart_proxy_openscap-0.9.1-1.el7sat.noarch
- rubygem-foreman_scap_client-0.5.0-1.el7sat.noarch

Test steps:
- Create oval content from a file.
- Create oval content from a remote resource.
- Read/update/delete oval content(s).
- Create/read/update/delete oval policy.
- Create hostgroup(s) with openscap capsule and foreman_scap_client ansible role.
- Assign policies to hostgroup(s).
- Assign hostgroup to content hosts.
- Run ansible role to configure openscap.
- Wait for cron job on content host to run OR run "foreman_scap_client oval <policy_id>" command.
- Enable lab feature. 
- Go to Lab features > OVAL Contents
- Go to Lab features > Oval policies > click on policy name > click on CVEs tab.


Observations:
- CRUD operations related to oval content and oval policies using related APIs completed successful.
- Oval report generated and uploaded to satellite.
- Oval content and oval policies are listed on satellite.
- CVEs are listed for affected hosts.
Comment 10 errata-xmlrpc 2021-11-16 14:11:01 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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702
Note You need to log in before you can comment on or make changes to this bug.