openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Updates the names of a few fields for the CSO and removes out-dated pictures

Browse Source
This commit is contained in:
Steven Smith
2024-07-24 09:51:08 -04:00
committed by openshift-cherrypick-robot
parent 0bc794c8e5
commit 3a7312701f
1 changed files with 4 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
modules/security-pod-scan-cso-using.adoc
View File

@@ -14,21 +14,15 @@ The following procedure shows you how to use the {rhq-cso}.
.Procedure
. On the {product-title} web console, navigate to *Home* -> *Overview*. Under the *Status* section, *Quay Image Security* provides the number of vulnerabilities found.
. On the {product-title} web console, navigate to *Home* -> *Overview*. Under the *Status* section, *Image Vulnerabilities* provides the number of vulnerabilities found.
. 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:
+
image:image_security.png[Access image scanning data from {product-title} dashboard]
. 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.
. You can address detected vulnerabilities in one of two ways:
+
.. 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:
+
image:cso-registry-vulnerable.png[The {rhq-cso} points you to a registry containing the vulnerable image]
.. 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.
.. 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:
+
image:cso-namespace-vulnerable.png[View namespaces a vulnerable image is running in]
.. 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.
. 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: