Bug 1779679

Summary: Image security dashboard card should make it clear we only check images from quay
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, hasha, jokerman, pkreuser, yapei
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1768496 Environment:
Last Closed: 2020-01-23 11:17:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1768496    
Bug Blocks:    
Description Flags
fixed none

Description Samuel Padgett 2019-12-04 13:54:36 UTC
+++ This bug was initially created as a clone of Bug #1768496 +++

The dashboard card from the security operator plugin doesn't make it clear that it only scans images from quay. This could give users a false sense of security when it says there are no vulnerabilities. It's possible containers running images from other registries are vulnerable.

We should add a statement in the UI that only images from quay are scanned.

--- Additional comment from Samuel Padgett on 2019-11-21 14:32:20 UTC ---

This is not release blocking. Moving to low severity.

--- Additional comment from Peter Kreuser on 2019-11-22 19:55:36 UTC ---

Status text: Quay Image Security
Popover title: Quay Image Security breakdown (Breakdown can be dropped if too long.)
Popover description: Container images from quay are analyzed to identify vulnerabilities. Images from other registries will not be scanned.

Comment 2 shahan 2019-12-05 08:24:39 UTC
verified this bug. detail display see attachment .4.3.0-0.nightly-2019-12-04-214544

Comment 3 shahan 2019-12-05 08:26:39 UTC
Created attachment 1642296 [details]

Comment 5 errata-xmlrpc 2020-01-23 11:17:47 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.