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.
Description of problem:
When scanner lists it's capabilities, descriptions of each scanner type should be clear about what is scanned. So user can check it for example in scap-workbench and read the rules. Also any property that is not obvious, but may affect users should be mentioned.
Issues of current description.
1 - It is not stated, there is CVE OVAL baked-in the openscap container image, thus it is inherently outdated.
2 - It is not clear enough the standards_compliance use normal "Standard" profile of latest shipped Scap Security Guide.
3 - It would be nice to have some general information about the scanner [not scan_type description, but scanner description], where link to Red Hat Security Guide would reside.
Version-Release number of selected component (if applicable):
openscap-docker-7.3-4
How reproducible:
reliably
Steps to Reproduce:
1. atomic install rhel7/openscap
2. atomic scan --scanner openscap --list
Actual results:
====
Scanner: openscap
Image Name: rhel7/openscap
Scan type: cve *
Description: Performs a CVE scan based on known CVE data
Scan type: standards_compliance
Description: Performs a standard scan
* denotes defaults
====
Expected results:
====
Scanner: openscap
Description: Scanner using openscap toolset and scap-security-guide rules. For full documentation, see <link to Security guide section>
Image Name: rhel7/openscap
Scan type: cve *
Description: Performs a CVE scan based on Red Hat released CVE OVAL. !Warning! This CVE is build into container image, and it might be out-of-date.
Scan type: standards_compliance
Description: Performs scan with Standard profile, as present in Scap Security Guide shipped in Red Hat Enterprise Linux.
* denotes defaults
====
Additional info:
Comment 3Watson Yuuma Sato
2017-03-30 15:59:45 UTC
Description of problem: When scanner lists it's capabilities, descriptions of each scanner type should be clear about what is scanned. So user can check it for example in scap-workbench and read the rules. Also any property that is not obvious, but may affect users should be mentioned. Issues of current description. 1 - It is not stated, there is CVE OVAL baked-in the openscap container image, thus it is inherently outdated. 2 - It is not clear enough the standards_compliance use normal "Standard" profile of latest shipped Scap Security Guide. 3 - It would be nice to have some general information about the scanner [not scan_type description, but scanner description], where link to Red Hat Security Guide would reside. Version-Release number of selected component (if applicable): openscap-docker-7.3-4 How reproducible: reliably Steps to Reproduce: 1. atomic install rhel7/openscap 2. atomic scan --scanner openscap --list Actual results: ==== Scanner: openscap Image Name: rhel7/openscap Scan type: cve * Description: Performs a CVE scan based on known CVE data Scan type: standards_compliance Description: Performs a standard scan * denotes defaults ==== Expected results: ==== Scanner: openscap Description: Scanner using openscap toolset and scap-security-guide rules. For full documentation, see <link to Security guide section> Image Name: rhel7/openscap Scan type: cve * Description: Performs a CVE scan based on Red Hat released CVE OVAL. !Warning! This CVE is build into container image, and it might be out-of-date. Scan type: standards_compliance Description: Performs scan with Standard profile, as present in Scap Security Guide shipped in Red Hat Enterprise Linux. * denotes defaults ==== Additional info: