Skip to content

Commit 07f7f40

Browse files
authored
Merge pull request #79365 from stevsmit/OCPBUGS-36251-CSO-updates
Updates the names of a few fields for the CSO and removes out-dated p…
2 parents bf33abc + e0ec09a commit 07f7f40

File tree

1 file changed

+4
-10
lines changed

1 file changed

+4
-10
lines changed

modules/security-pod-scan-cso-using.adoc

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,21 +14,15 @@ The following procedure shows you how to use the {rhq-cso}.
1414
1515
.Procedure
1616

17-
. On the {product-title} web console, navigate to *Home* -> *Overview*. Under the *Status* section, *Quay Image Security* provides the number of vulnerabilities found.
17+
. On the {product-title} web console, navigate to *Home* -> *Overview*. Under the *Status* section, *Image Vulnerabilities* provides the number of vulnerabilities found.
1818

19-
. Click *Quay Image Security* to reveal the *Quay Image Security breakdown*, which details the severity of the vulnerabilities, whether the vulnerabilities can be fixed, and the total number of vulnerabilities. For example:
20-
+
21-
image:image_security.png[Access image scanning data from {product-title} dashboard]
19+
. Click *Image Vulnerabilities* to reveal the *Image Vulnerabilities breakdown* tab, which details the severity of the vulnerabilities, whether the vulnerabilities can be fixed, and the total number of vulnerabilities.
2220

2321
. You can address detected vulnerabilities in one of two ways:
2422
+
25-
.. Select the link to the vulnerability. This takes you to the container registry that the container came from, where you can see information about the vulnerability. The following example shows detected vulnerabilities from a Quay.io registry:
26-
+
27-
image:cso-registry-vulnerable.png[The {rhq-cso} points you to a registry containing the vulnerable image]
23+
.. Select a link under the *Vulnerabilities* section. This takes you to the container registry that the container came from, where you can see information about the vulnerability.
2824

29-
.. Select the *namespace* link. This takes you to the *ImageManifestVuln* page, where you can see the name of the selected image and all of the namespaces where that image is running. For example, the following image shows you that a particular vulnerable image is running in the `quay-enterprise` namespace:
30-
+
31-
image:cso-namespace-vulnerable.png[View namespaces a vulnerable image is running in]
25+
.. Select the *namespace* link. This takes you to the *Image Manifest Vulnerabilities* page, where you can see the name of the selected image and all of the namespaces where that image is running.
3226

3327
. After you have learned what images are vulnerable, how to fix those vulnerabilities, and the namespaces that the images are being run in, you can improve security by performing the following actions:
3428

0 commit comments

Comments
 (0)