15.2. Viewing and addressing vulnerabilities


The Vulnerability Management functions provide methods to view and manage vulnerabilities discovered by RHACS. Common vulnerability management tasks involve identifying and prioritizing vulnerabilities, remedying them, and monitoring for new threats.

Historically, RHACS provided a view of vulnerabilities discovered in your system in the vulnerability management dashboard. The dashboard is deprecated in RHACS 4.5 and will be removed in a future release.

For more information about the dashboard, see Using the vulnerability management dashboard.

Currently, vulnerability information is provided in pages that are accessed by selecting Vulnerability Management Results. You can select different views based on whether you want to view vulnerabilities discovered in your workloads, vulnerabilities discovered in platform components, such as OpenShift, or node vulnerabilities. Depending on the view, you can filter results based on specific criteria: for example, you can display vulnerabilities of different severity, vulnerabilities in deployments with specific annotations, or vulnerabilities in images that are based on a specific operating system.

15.2.1. Viewing vulnerability management data in the RHACS portal

Beginning with release 4.7, RHACS has reorganized data for vulnerabilities it discovers and separated vulnerability data by category, such as vulnerabilities in user workloads and nodes, and platform vulnerabilities.

In the Vulnerability Management menu, the Results page provides vulnerability data. You can view vulnerability data by category by clicking the tabs at the top of the page. The tabs include the following categories:

User workloads
This tab provides information about vulnerabilities that affect workloads and images in your system that you have deployed. Because these workloads are deployed and managed by you, they are called user workloads.
Platform

This tab provides information about vulnerabilities that RHACS identifies as related to the platform, for example, vulnerabilities in workloads and images that the OpenShift platform and layered services deploy. RHACS uses a regular expression pattern to examine the namespaces of workloads and identify workloads that belong to platform components. For example, currently, RHACS identifies vulnerabilities in the following namespaces as belonging to the platform:

  • OpenShift Container Platform: Namespace starts with openshift- or kube-
  • Layered products:

    • Namespace starts with rhacs-operator
    • Namespace starts with open-cluster-management
    • Namespace is stackrox, multicluster-engine, aap, or hive
  • Third-party partners: Namespace is nvidia-gpu-operator
Nodes
This tab provides a view of vulnerabilities across nodes, including user-managed and platform workloads and images.
More views

This menu provides access to additional ways to view vulnerability information, including the following views:

  • All vulnerable images
  • Inactive images
  • Images without CVEs
  • Kubernetes components

15.2.2. Viewing user workload vulnerabilities

In the Vulnerability Management Results page, you can get information about the vulnerabilities in applications running on clusters in your system. With this information, you can prioritize and manage vulnerabilities across images and deployments.

In the User workload vulnerabilities page, you can view images and deployments with vulnerabilities and filter by image, deployment, namespace, cluster, CVE, component, and component source.

Procedure

  1. In the RHACS portal, go to Vulnerability Management Results.
  2. Select the User Workloads tab. By default, the Observed tab is selected.
  3. Optional: You can choose to view observed vulnerabilities or those that have been deferred or marked as false positives. Click one of the following tabs:

    • Observed: Lists vulnerabilities that RHACS observed in your user workloads.
    • Deferred: Lists vulnerabilities that have been observed but had a deferral request submitted and approved in the exception management workflow.
    • False positives: Lists vulnerabilities that have been observed but were identified as false positives in the exception management workflow.
  4. Optional: You can select the following options to refine the list of results:

    • Prioritize by namespace view: Displays a list of namespaces sorted according to the risk priority. You can use this view to quickly identify and address the most critical areas. In this view, click <number> deployments in a table row to return to the vulnerability findings view, with filters applied to show only deployments for the selected namespace.
    • Default filters: You can select filters for CVE severity and CVE status that are automatically applied across all views on this page. These filters are applied when you visit the page from another section of the RHACS web portal or from a bookmarked URL. They are saved in the local storage of your browser.
  5. To filter the list of results by entity, for example, to search for a specific named CVE, select the appropriate filters and attributes.

    To select multiple entities and attributes, click the right arrow icon to add another criteria. Depending on your choices, enter the appropriate information such as text, or select a date or object.

    The filter entities and attributes are listed in the following table.

    참고

    The Filtered view icon indicates that the displayed results were filtered based on the criteria that you selected. You can click Clear filters to remove all filters, or remove individual filters by clicking on them.

    Expand
    표 15.1. Filter options
    EntityAttributes

    Image

    • Name: The name of the image.
    • Operating system: The operating system of the image.
    • Tag: The tag for the image.
    • Label: The label for the image.
    • Registry: The registry where the image is located.

    CVE

    • Name: The name of the CVE.
    • Discovered time: The date when RHACS discovered the CVE.
    • CVSS: The severity level for the CVE.

      The following values are associated with the severity level for the CVE:

      • is greater than
      • is greater than or equal to
      • is equal to
      • is less than or equal to
      • is less than
    • EPSS probability: The likelihood that the vulnerability will be exploited according to the Exploit Prediction Scoring System (EPSS). This EPSS data provides a percentage estimate of the probability that exploitation of this vulnerability will be observed in the next 30 days. The EPSS collects data of observed exploitation activity from partners, and exploitation activity does not mean that an attempted exploitation was successful. The EPSS score should be used as a single data point along with other information, such as the age of the CVE, to help you prioritize the vulnerabilities to address. For more information, see RHACS and EPSS.

    Image Component

    • Name: The name of the image component, for example, activerecord-sql-server-adapter
    • Source:

      • OS
      • Python
      • Java
      • Ruby
      • Node.js
      • Go
      • Dotnet Core Runtime
      • Infrastructure
    • Version: Version of the image component; for example, 3.4.21. You can use this to search for a specific version of a component, for example, in conjunction with a component name.

    Deployment

    • Name: Name of the deployment.
    • Label: Label for the deployment.
    • Annotation: The annotation for the deployment.
    • Status: Whether the deployment is inactive or active.

    Namespace

    • ID: The metadata.uid of the namespace that is created by Kubernetes.
    • Name: The name of the namespace.
    • Label: The label for the namespace.
    • Annotation: The annotation for the namespace.

    Cluster

    • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
    • Name: The name of the cluster.
    • Label: The label for the cluster.
    • Type: The cluster type, for example, OCP.
    • Platform type: The platform type, for example, OpenShift 4 cluster.
    • CVE severity: You can select one or more levels.
    • CVE status: You can select Fixable or Not fixable.
  6. Click one of the following tabs to view the data that you want:

    • <number> CVEs: Displays vulnerabilities organized by CVE
    • <number> Images: Displays images that contain discovered vulnerabilities.
    • <number> Deployments: Displays deployments that contain discovered vulnerabilities.
  7. Optional: Choose the appropriate method to re-organize the information in the User Workloads tab:

    • To sort the table in ascending or descending order, select a column heading.
    • To select the categories that you want to display in the table, perform the following steps:

      1. Click Columns.
      2. Choose the appropriate method to manage the columns:

        • To view all the categories, click Select all.
        • To reset to the default categories, click Reset to default.
        • To view only the selected categories, select the one or more categories that you want to view, and then click Save.
  8. In the list of results, click a CVE, image name, or deployment name to view more information about the item. For example, depending on the item type, you can view the following information:

    • Whether a CVE is fixable
    • Whether an image is active
    • The Dockerfile line in the image that contains the CVE
    • External links to information about the CVE in Red Hat and other CVE databases

15.2.3. Viewing platform vulnerabilities

The Platform vulnerabilities page provides information about vulnerabilities that RHACS identifies as related to the platform, for example, vulnerabilities in workloads and images that are used by the OpenShift Platform and layered services.

Procedure

  1. In the RHACS portal, go to Vulnerability Management Results.
  2. Select the Platform tab. By default, the Observed tab is selected.
  3. Optional: You can choose to view observed vulnerabilities or those that have been deferred or marked as false positives. Click one of the following tabs:

    • Observed: Lists vulnerabilities that RHACS observed in platform workloads and images.
    • Deferred: Lists vulnerabilities that have been observed but had a deferral request submitted and approved in the exception management workflow.
    • False positives: Lists vulnerabilities that have been observed but were identified as false positives in the exception management workflow.
  4. Optional: You can select the following options to refine the list of results:

    • Prioritize by namespace view: Displays a list of namespaces sorted according to the risk priority. You can use this view to quickly identify and address the most critical areas. In this view, click <number> deployments in a table row to return to the platform vulnerabilities view, with filters applied to show only deployments for the selected namespace.
    • Default filters: You can select filters for CVE severity and CVE status that are automatically applied across all views on this page. These filters are applied when you visit the page from another section of the RHACS web portal or from a bookmarked URL. They are saved in the local storage of your browser.
  5. To filter the list of results by entity, for example, to search for a specific named CVE, select the appropriate filters and attributes.

    To select multiple entities and attributes, click the right arrow icon to add another criteria. Depending on your choices, enter the appropriate information such as text, or select a date or object.

    The filter entities and attributes are listed in the following table.

    참고

    The Filtered view icon indicates that the displayed results were filtered based on the criteria that you selected. You can click Clear filters to remove all filters, or remove individual filters by clicking on them.

    Expand
    표 15.2. Filter options
    EntityAttributes

    Image

    • Name: The name of the image.
    • Operating system: The operating system of the image.
    • Tag: The tag for the image.
    • Label: The label for the image.
    • Registry: The registry where the image is located.

    CVE

    • Name: The name of the CVE.
    • Discovered time: The date when RHACS discovered the CVE.
    • CVSS: The severity level for the CVE.

      The following values are associated with the severity level for the CVE:

      • is greater than
      • is greater than or equal to
      • is equal to
      • is less than or equal to
      • is less than
    • EPSS probability: The likelihood that the vulnerability will be exploited according to the Exploit Prediction Scoring System (EPSS). This EPSS data provides a percentage estimate of the probability that exploitation of this vulnerability will be observed in the next 30 days. The EPSS collects data of observed exploitation activity from partners, and exploitation activity does not mean that an attempted exploitation was successful. The EPSS score should be used as a single data point along with other information, such as the age of the CVE, to help you prioritize the vulnerabilities to address. For more information, see RHACS and EPSS.

    Image Component

    • Name: The name of the image component, for example, activerecord-sql-server-adapter
    • Source:

      • OS
      • Python
      • Java
      • Ruby
      • Node.js
      • Go
      • Dotnet Core Runtime
      • Infrastructure
    • Version: Version of the image component; for example, 3.4.21. You can use this to search for a specific version of a component, for example, in conjunction with a component name.

    Deployment

    • Name: Name of the deployment.
    • Label: Label for the deployment.
    • Annotation: The annotation for the deployment.
    • Status: Whether the deployment is inactive or active.

    Namespace

    • ID: The metadata.uid of the namespace that is created by Kubernetes.
    • Name: The name of the namespace.
    • Label: The label for the namespace.
    • Annotation: The annotation for the namespace.

    Cluster

    • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
    • Name: The name of the cluster.
    • Label: The label for the cluster.
    • Type: The cluster type, for example, OCP.
    • Platform type: The platform type, for example, OpenShift 4 cluster.
    • CVE severity: You can select one or more levels.
    • CVE status: You can select Fixable or Not fixable.
  6. Click one of the following tabs to view the data that you want:

    • <number> CVEs: Displays vulnerabilities organized by CVE
    • <number> Images: Displays images that contain discovered vulnerabilities.
    • <number> Deployments: Displays deployments that contain discovered vulnerabilities.
  7. Optional: Choose the appropriate method to re-organize the information in the User Workloads tab:

    • To sort the table in ascending or descending order, select a column heading.
    • To select the categories that you want to display in the table, perform the following steps:

      1. Click Columns.
      2. Choose the appropriate method to manage the columns:

        • To view all the categories, click Select all.
        • To reset to the default categories, click Reset to default.
        • To view only the selected categories, select the one or more categories that you want to view, and then click Save.
  8. In the list of results, click a CVE, image name, or deployment name to view more information about the item. For example, depending on the item type, you can view the following information:

    • Whether a CVE is fixable
    • Whether an image is active
    • The Dockerfile line in the image that contains the CVE
    • External links to information about the CVE in Red Hat and other CVE databases

15.2.4. Viewing vulnerabilities in nodes

You can identify vulnerabilities in your nodes by using RHACS. The vulnerabilities that are identified include the following:

  • Vulnerabilities in core Kubernetes components
  • Vulnerabilities in container runtimes such as Docker, CRI-O, runC, and containerd

For more information about operating systems that RHACS can scan, see "Supported operating systems".

RHACS currently supports scanning nodes with the StackRox scanner and Scanner V4. Depending on which scanner is configured, different results might appear in the list of vulnerabilities. For more information, see "Understanding differences in scanning results between the StackRox Scanner and Scanner V4".

Procedure

  1. In the RHACS portal, go to Vulnerability Management Results.
  2. Select the Nodes tab.
  3. Optional: The page defaults to a list of observed CVEs. Click Show snoozed CVEs to view them.
  4. Optional: To filter CVEs according to entity, select the appropriate filters and attributes. To add more filtering criteria, follow these steps:

    1. Select the entity or attribute from the list.
    2. Depending on your choices, enter the appropriate information such as text, or select a date or object.
    3. Click the right arrow icon.
    4. Optional: Select additional entities and attributes, and then click the right arrow icon to add them. The filter entities and attributes are listed in the following table.

      Expand
      표 15.3. Filter options
      EntityAttributes

      Node

      • Name: The name of the node.
      • Operating system: The operating system of the node, for example, Red Hat Enterprise Linux (RHEL).
      • Label: The label of the node.
      • Annotation: The annotation for the node.
      • Scan time: The scan date of the node.

      CVE

      • Name: The name of the CVE.
      • Discovered time: The date when RHACS discovered the CVE.
      • CVSS: The severity level for the CVE.

        The following values are associated with the severity level for the CVE:

        • is greater than
        • is greater than or equal to
        • is equal to
        • is less than or equal to
        • is less than

      Node Component

      • Name: The name of the component.
      • Version: The version of the component, for example, 4.15.0-2024. You can use this to search for a specific version of a component, for example, in conjunction with a component name.

      Cluster

      • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
      • Name: The name of the cluster.
      • Label: The label for the cluster.
      • Type: The type of cluster, for example, OCP.
      • Platform type: The type of platform, for example, OpenShift 4 cluster.
  5. Optional: To refine the list of results, do any of the following tasks:

    • Click CVE severity, and then select one or more levels.
    • Click CVE status, and then select Fixable or Not fixable.
  6. To view the data, click one of the following tabs:

    • <number> CVEs: Displays a list of all the CVEs affecting all of your nodes.
    • <number> Nodes: Displays a list of nodes that contain CVEs.
  7. To view the details of the node and information about the CVEs according to the CVSS score and fixable CVEs for that node, click a node name in the list of nodes.

15.2.4.1. Disabling identifying vulnerabilities in nodes

Identifying vulnerabilities in nodes is enabled by default. You can disable it from the RHACS portal.

Procedure

  1. In the RHACS portal, go to Platform Configuration Integrations.
  2. Under Image Integrations, select StackRox Scanner.
  3. From the list of scanners, select StackRox Scanner to view its details.
  4. Click Edit.
  5. To use only the image scanner and not the node scanner, click Image Scanner.
  6. Click Save.

15.2.5. Accessing additional views in vulnerability management

The More views tab provides additional ways to view vulnerabilities in your system, including the following views:

  • All vulnerable images: Displays vulnerabilities for user workloads, platform vulnerabilities, and vulnerabilities for inactive images in the same page.
  • Inactive images: Displays vulnerabilities for watched images and images that are not currently deployed as workloads. Vulnerabilities are reported for images based on your image retention settings.
  • Images without CVEs: Shows images and workloads without observed CVEs. See "Analyze images and deployments without observed CVEs".
  • Kubernetes components: Displays vulnerabilities affecting the underlying Kubernetes structure.

15.2.5.1. Viewing all vulnerable images

You can view a list of vulnerabilities for user workloads, platform vulnerabilities, and inactive images on the same page.

Procedure

  1. In the RHACS portal, go to Vulnerability Management Results.
  2. Click More Views and select All vulnerable images.
  3. Optional: You can choose to view observed vulnerabilities or those that have been deferred or marked as false positives. Click one of the following tabs:

    • Observed: Lists vulnerabilities that RHACS observed across all images and workloads.
    • Deferred: Lists vulnerabilities that have been observed but had a deferral request submitted and approved in the exception management workflow.
    • False positives: Lists vulnerabilities that have been observed but were identified as false positives in the exception management workflow.
  4. Optional: You can select the following options to refine the list of results:

    • Prioritize by namespace view: Displays a list of namespaces sorted according to the risk priority. You can use this view to quickly identify and address the most critical areas. In this view, click <number> deployments in a table row to return to the all vulnerable images view, with filters applied to show only deployments for the selected namespace.
    • Default filters: You can select filters for CVE severity and CVE status that are automatically applied across all views on this page. These filters are applied when you visit the page from another section of the RHACS web portal or from a bookmarked URL. They are saved in the local storage of your browser.
  5. Click one of the following tabs to view the data that you want:

    • <number> CVEs: Displays vulnerabilities organized by CVE
    • <number> Images: Displays images that contain discovered vulnerabilities.
    • <number> Deployments: Displays deployments that contain discovered vulnerabilities.
  6. Optional: Choose the appropriate method to re-organize the information in the User Workloads tab:

    • To sort the table in ascending or descending order, select a column heading.
    • To filter the table, use the filter bar.
    • To select the categories that you want to display in the table, perform the following steps:

      1. Click Columns.
      2. Choose the appropriate method to manage the columns:

        • To view all the categories, click Select all.
        • To reset to the default categories, click Reset to default.
        • To view only the selected categories, select the one or more categories that you want to view, and then click Save.
  7. To filter the list of results by entity, for example, to search for a specific named CVE, select the appropriate filters and attributes.

    To select multiple entities and attributes, click the right arrow icon to add another criteria. Depending on your choices, enter the appropriate information such as text, or select a date or object.

    The filter entities and attributes are listed in the following table.

    Expand
    표 15.4. CVE filtering
    EntityAttributes

    Image

    • Name: The name of the image.
    • Operating system: The operating system of the image.
    • Tag: The tag for the image.
    • Label: The label for the image.
    • Registry: The registry where the image is located.

    CVE

    • Name: The name of the CVE.
    • Discovered time: The date when RHACS discovered the CVE.
    • CVSS: The severity level for the CVE.

      The following values are associated with the severity level for the CVE:

      • is greater than
      • is greater than or equal to
      • is equal to
      • is less than or equal to
      • is less than
    • EPSS probability: The likelihood that the vulnerability will be exploited according to the Exploit Prediction Scoring System (EPSS). This EPSS data provides a percentage estimate of the probability that exploitation of this vulnerability will be observed in the next 30 days. The EPSS collects data of observed exploitation activity from partners, and exploitation activity does not mean that an attempted exploitation was successful. The EPSS score should be used as a single data point along with other information, such as the age of the CVE, to help you prioritize the vulnerabilities to address. For more information, see RHACS and EPSS.

    Image Component

    • Name: The name of the image component, for example, activerecord-sql-server-adapter
    • Source:

      • OS
      • Python
      • Java
      • Ruby
      • Node.js
      • Go
      • Dotnet Core Runtime
      • Infrastructure
    • Version: Version of the image component; for example, 3.4.21. You can use this to search for a specific version of a component, for example, in conjunction with a component name.

    Deployment

    • Name: Name of the deployment.
    • Label: Label for the deployment.
    • Annotation: The annotation for the deployment.
    • Status: Whether the deployment is inactive or active.

    Namespace

    • ID: The metadata.uid of the namespace that is created by Kubernetes.
    • Name: The name of the namespace.
    • Label: The label for the namespace.
    • Annotation: The annotation for the namespace.

    Cluster

    • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
    • Name: The name of the cluster.
    • Label: The label for the cluster.
    • Type: The cluster type, for example, OCP.
    • Platform type: The platform type, for example, OpenShift 4 cluster.
    • CVE severity: You can select one or more levels.
    • CVE status: You can select Fixable or Not fixable.
참고

The Filtered view icon indicates that the displayed results were filtered based on the criteria that you selected. You can click Clear filters to remove all filters, or remove individual filters by clicking on them.

In the list of results, click a CVE, image name, or deployment name to view more information about the item. For example, depending on the item type, you can view the following information:

  • Whether a CVE is fixable
  • Whether an image is active
  • The Dockerfile line in the image that contains the CVE
  • External links to information about the CVE in Red Hat and other CVE databases

15.2.5.2. Scanning inactive images

Red Hat Advanced Cluster Security for Kubernetes (RHACS) scans all active (deployed) images every 4 hours and updates the image scan results to reflect the latest vulnerability definitions.

You can also configure RHACS to scan inactive (not deployed) images automatically.

Procedure

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click More Views Inactive images.
  3. Click Manage watched images.
  4. In the Image name field, enter the fully-qualified image name that begins with the registry and ends with the image tag, for example, docker.io/library/nginx:latest.
  5. Click Add image to watch list.
  6. Optional: To remove a watched image, locate the image in the Manage watched images window, and click Remove watch.

    중요

    In the RHACS portal, click Platform Configuration System Configuration to view the data retention configuration.

    All the data related to the image removed from the watched image list continues to appear in the RHACS portal for the number of days mentioned on the System Configuration page and is only removed after that period is over.

  7. Click Close to return to the Inactive images page.

15.2.5.3. Analyze images and deployments without observed CVEs

When you view the list of images without vulnerabilities, RHACS shows the images that meet at least one of the following conditions:

  • Images that do not have CVEs
  • Images that report a scanner error that may result in a false negative of no CVEs
참고

An image that actually contains vulnerabilities can appear in this list inadvertently. For example, if Scanner was able to scan the image and it is known to Red Hat Advanced Cluster Security for Kubernetes (RHACS), but the scan was not successfully completed, RHACS cannot detect vulnerabilities.

This scenario occurs if an image has an operating system that RHACS Scanner does not support. RHACS displays scan errors when you hover over an image in the image list or click the image name for more information.

Procedure

  1. In the RHACS portal, go to Vulnerability Management Results.
  2. Click More Views and select Images without CVEs.
  3. To filter the list of results by entity, for example, to search for a specific image, select the appropriate filters and attributes.

    To select multiple entities and attributes, click the right arrow icon to add another criteria. Depending on your choices, enter the appropriate information such as text, or select a date or object.

    The filter entities and attributes are listed in the following table.

    참고

    The Filtered view icon indicates that the displayed results were filtered based on the criteria that you selected. You can click Clear filters to remove all filters, or remove individual filters by clicking on them.

    Expand
    표 15.5. Filter options
    EntityAttributes

    Image

    • Name: The name of the image.
    • Operating system: The operating system of the image.
    • Tag: The tag for the image.
    • Label: The label for the image.
    • Registry: The registry where the image is located.

    Image Component

    • Name: The name of the image component, for example, activerecord-sql-server-adapter
    • Source:

      • OS
      • Python
      • Java
      • Ruby
      • Node.js
      • Go
      • Dotnet Core Runtime
      • Infrastructure
    • Version: Version of the image component; for example, 3.4.21. You can use this to search for a specific version of a component, for example, in conjunction with a component name.

    Deployment

    • Name: Name of the deployment.
    • Label: Label for the deployment.
    • Annotation: The annotation for the deployment.
    • Status: Whether the deployment is inactive or active.

    Namespace

    • ID: The metadata.uid of the namespace that is created by Kubernetes.
    • Name: The name of the namespace.
    • Label: The label for the namespace.
    • Annotation: The annotation for the namespace.

    Cluster

    • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
    • Name: The name of the cluster.
    • Label: The label for the cluster.
    • Type: The cluster type, for example, OCP.
    • Platform type: The platform type, for example, OpenShift 4 cluster.
  4. Click one of the following tabs to view the data that you want:

    • <number> Images: Displays images that contain discovered vulnerabilities.
    • <number> Deployments: Displays deployments that contain discovered vulnerabilities.
  5. Optional: Choose the appropriate method to re-organize the information in the page:

    • To select the categories that you want to display in the table, perform the following steps:

      1. Click Columns.
      2. Choose the appropriate method to manage the columns:

        • To view all the categories, click Select all.
        • To reset to the default categories, click Reset to default.
        • To view only the selected categories, select the one or more categories that you want to view, and then click Save.
        • To sort the table in ascending or descending order, select a column heading.
  6. In the list of results, click an image name or deployment name to view more information about the item.

15.2.5.4. Viewing Kubernetes vulnerabilities

You can view vulnerabilities in your clusters that affect the underlying Kubernetes structure.

Procedure

  1. Go to Vulnerability Management Results.
  2. Click More Views and select Kubernetes components.
  3. Click the <number> CVEs or <number> Clusters to display by CVE or cluster.
  4. Optional: Within the results list, you can filter results by cluster and CVE. To filter vulnerabilities based on an entity, select the appropriate filters and attributes.

    To select multiple entities and attributes, click the right arrow icon to add another criteria. Depending on your choices, enter the appropriate information such as text, or select a date or object.

    The filter entities and attributes are listed in the following table.

    Expand
    표 15.6. Filter options
    EntityAttributes

    Cluster

    • ID: The alphanumeric ID for the cluster. This is an internal identifier that RHACS assigns for tracking purposes.
    • Name: The name of the cluster.
    • Label: The label for the cluster.
    • Type: The cluster type, for example, OCP.
    • Platform type: The platform type, for example, OpenShift 4 cluster.

    CVE

    • Name: The name of the CVE.
    • Discovered time: The date when RHACS discovered the CVE.
    • CVSS: The severity level for the CVE.

      The following values are associated with the severity level for the CVE:

      • is greater than
      • is greater than or equal to
      • is equal to
      • is less than or equal to
      • is less than
    • Type: The type of CVE:

      • Kubernetes
      • Istio
      • OpenShift
  5. Optional: To filter the table based on the status of a CVE, from the CVE status drop-down list, select one or more statuses.

    The following values are associated with the status of a CVE:

    • Fixable
    • Not fixable
참고

The Filtered view icon indicates that the displayed results were filtered based on the criteria that you selected. You can click Clear filters to remove all filters, or remove individual filters by clicking on them.

In the list of results, click a CVE or cluster name to view more information about the item. For example, depending on the item type, you can view the following information:

  • First discovered date
  • Whether a CVE is fixable
  • External links to information about the CVE in Red Hat and other CVE databases

15.2.6. Excluding CVEs

You can exclude or ignore CVEs in RHACS by snoozing node and platform CVEs and deferring or marking node, platform, and image CVEs as false positives. You might want to exclude CVEs if you know that the CVE is a false positive or you have already taken steps to mitigate the CVE. Snoozed CVEs do not appear in vulnerability reports or trigger policy violations.

You can snooze a CVE to ignore it globally for a specified period of time. Snoozing a CVE does not require approval.

참고

Snoozing node and platform CVEs requires that the ROX_VULN_MGMT_LEGACY_SNOOZE environment variable is set to true.

Deferring or marking a CVE as a false positive is done through the exception management workflow. This workflow provides the ability to view pending, approved, and denied deferral and false positive requests. You can scope the CVE exception to a single image, all tags for a single image, or globally for all images.

When approving or denying a request, you must add a comment. A CVE remains in the observed status until the exception request is approved. A pending request for deferral that is denied by another user is still visible in reports, policy violations, and other places in the system, but is indicated by a Pending exception label next to the CVE when visiting the following pages after going to Vulnerability Management Results:

  • User workloads
  • Platform
  • All vulnerable images
  • Inactive images

An approved exception for a deferral or false positive has the following effects:

  • Removes the CVE from the Observed tab in the User Workloads tab to either the Deferred or False positive tab
  • Prevents the CVE from triggering policy violations that are related to the CVE
  • Prevents the CVE from showing up in automatically generated vulnerability reports

15.2.6.1. Snoozing platform and node CVEs

You can snooze platform and node CVEs that do not relate to your infrastructure. You can snooze CVEs for 1 day, 1 week, 2 weeks, 1 month, or indefinitely, until you unsnooze them. Snoozing a CVE takes effect immediately and does not require an additional approval step.

참고

The ability to snooze a CVE is not enabled by default in the web portal or in the API. To enable the ability to snooze CVEs, set the runtime environment variable ROX_VULN_MGMT_LEGACY_SNOOZE to true.

Procedure

  1. In the RHACS portal, do any of the following tasks:

    • To view platform CVEs, click Vulnerability Management Platform CVEs.
    • To view node CVEs, click Vulnerability Management Node CVEs.
  2. Select one or more CVEs.
  3. Select the appropriate method to snooze the CVE:

    • If you selected a single CVE, click the overflow menu, kebab , and then select Snooze CVE.
    • If you selected multiple CVEs, click Bulk actions Snooze CVEs.
  4. Select the duration of time to snooze.
  5. Click Snooze CVEs.

    You receive a confirmation that you have requested to snooze the CVEs.

15.2.6.2. Unsnoozing platform and node CVEs

You can unsnooze platform and node CVEs that you have previously snoozed.

참고

The ability to snooze a CVE is not enabled by default in the web portal or in the API. To enable the ability to snooze CVEs, set the runtime environment variable ROX_VULN_MGMT_LEGACY_SNOOZE to true.

Procedure

  1. In the RHACS portal, do any of the following tasks:

    • To view the list of platform CVEs, click Vulnerability Management Platform CVEs.
    • To view the list of node CVEs, click Vulnerability Management Node CVEs.
  2. To view the list of snoozed CVEs, click Show snoozed CVEs in the header view.
  3. Select one or more CVEs from the list of snoozed CVEs.
  4. Select the appropriate method to unsnooze the CVE:

    • If you selected a single CVE, click the overflow menu, kebab , and then select Unsnooze CVE.
    • If you selected multiple CVEs, click Bulk actions Unsnooze CVEs.
  5. Click Unsnooze CVEs again.

    You receive a confirmation that you have requested to unsnooze the CVEs.

15.2.6.3. Viewing snoozed CVEs

You can view a list of platform and node CVEs that have been snoozed.

참고

The ability to snooze a CVE is not enabled by default in the web portal or in the API. To enable the ability to snooze CVEs, set the runtime environment variable ROX_VULN_MGMT_LEGACY_SNOOZE to true.

Procedure

  1. In the RHACS portal, do any of the following tasks:

    • To view the list of platform CVEs, click Vulnerability Management Platform CVEs.
    • To view the list of node CVEs, click Vulnerability Management Node CVEs.
  2. Click Show snoozed CVEs to view the list.

15.2.6.4. Marking a vulnerability as a false positive globally

You can create an exception for a vulnerability by marking it as a false positive globally, or across all images. You must get requests to mark a vulnerability as a false positive approved in the exception management workflow.

Prerequisites

  • You have the write permission for the VulnerabilityManagementRequests resource.

Procedure

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click User Workloads.
  3. Choose the appropriate method to mark the CVEs:

    • If you want to mark a single CVE, perform the following steps:

      1. Find the row which contains the CVE that you want to take action on.
      2. Click the overflow menu, kebab , for the CVE that you identified, and then select Mark as false positive.
    • If you want to mark multiple CVEs, perform the following steps:

      1. Select each CVE.
      2. From the Bulk actions drop-down list, select Mark as false positives.
  4. Enter a rationale for requesting the exception.
  5. Optional: To review the CVEs that are included in the exception request, click CVE selections.
  6. Click Submit request.

    You receive a confirmation that you have requested an exception.

  7. Optional: To copy the approval link and share it with your organization’s exception approver, click the copy icon.
  8. Click Close.

15.2.6.5. Marking a vulnerability as a false positive for an image or image tag

To create an exception for a vulnerability, you can mark it as a false positive for a single image, or across all tags associated with an image. You must get requests to mark a vulnerability as a false positive approved in the exception management workflow.

Prerequisites

  • You have the write permission for the VulnerabilityManagementRequests resource.

Procedure

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click the User Workloads tab.
  3. To view the list of images, click <number> Images.
  4. Find the row that lists the image that you want to mark as a false positive, and click the image name.
  5. Choose the appropriate method to mark the CVEs:

    • If you want to mark a single CVE, perform the following steps:

      1. Find the row which contains the CVE that you want to take action on.
      2. Click the overflow menu, kebab , for the CVE that you identified, and then select Mark as false positive.
    • If you want to mark multiple CVEs, perform the following steps:

      1. Select each CVE.
      2. From the Bulk actions drop-down list, select Mark as false positives.
  6. Select the scope. You can select either all tags associated with the image or only the image.
  7. Enter a rationale for requesting the exception.
  8. Optional: To review the CVEs that are included in the exception request, click CVE selections.
  9. Click Submit request.

    You receive a confirmation that you have requested an exception.

  10. Optional: To copy the approval link and share it with your organization’s exception approver, click the copy icon.
  11. Click Close.

15.2.6.6. Viewing deferred and false positive CVEs

You can view the CVEs that have been deferred or marked as false positives by using the User Workloads page.

Procedure

  1. To see CVEs that have been deferred or marked as false positives, with the exceptions approved by an approver, click Vulnerability Management Results.
  2. Click the User Workloads tab.
  3. Complete any of the following actions:

    • To see CVEs that have been deferred, click the Deferred tab.
    • To see CVEs that have been marked as false positives, click the False positives tab.

      참고

      To approve, deny, or change deferred or false positive CVEs, click Vulnerability Management Exception Management.

  4. Optional: To view additional information about the deferral or false positive, click View in the Request details column. The Exception Management page is displayed.

15.2.6.7. Deferring CVEs

You can accept risk with or without mitigation and defer CVEs. You must get deferral requests approved in the exception management workflow.

Prerequisites

  • You have write permission for the VulnerabilityManagementRequests resource.

Procedure

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click the User Workloads tab.
  3. Choose the appropriate method to defer a CVE:

    • If you want to defer a single CVE, perform the following steps:

      1. Find the row which contains the CVE that you want to mark as a false positive.
      2. Click the overflow menu, kebab , for the CVE that you identified, and then click Defer CVE.
    • If you want to defer multiple CVEs, perform the following steps:

      1. Select each CVE.
      2. Click Bulk actions Defer CVEs.
  4. Select the time period for the deferral.
  5. Enter a rationale for requesting the exception.
  6. Optional: To review the CVEs that are included in the exception menu, click CVE selections.
  7. Click Submit request.

    You receive a confirmation that you have requested a deferral.

  8. Optional: To copy the approval link to share it with your organization’s exception approver, click the copy icon.
  9. Click Close.
15.2.6.7.1. Configuring vulnerability exception expiration periods

You can configure the time periods available for vulnerability management exceptions. These options are available when users request to defer a CVE.

Prerequisites

  • You have write permission for the VulnerabilityManagementRequests resource.

Procedure

  1. In the RHACS portal, go to Platform Configuration Exception Configuration.
  2. You can configure expiration times that users can select when they request to defer a CVE. Enabling a time period makes it available to users and disabling it removes it from the user interface.

You can review, update, approve, or deny an exception requests for deferring and marking CVEs as false positives.

Prerequisites

  • You have the write permission for the VulnerabilityManagementRequests resource.

Procedure

  1. To view the list of pending requests, do any of the following tasks:

    • Paste the approval link into your browser.
    • Click Vulnerability Management Exception Management, and then click the request name in the Pending requests tab.
  2. Review the scope of the vulnerability and decide whether or not to approve it.
  3. Choose the appropriate option to manage a pending request:

    • If you want to deny the request and return the CVE to observed status, click Deny request.

      Enter a rationale for the denial, and click Deny.

    • If you want to approve the request, click Approve request.

      Enter a rationale for the approval, and click Approve.

  4. To cancel a request that you have created and return the CVE to observed status, click Cancel request. You can only cancel requests that you have created.
  5. To update the deferral time period or rationale for a request that you have created, click Update request. You can only update requests that you have created.

    After you make changes, click Submit request.

    You receive a confirmation that you have submitted a request.

15.2.7. Identifying Dockerfile lines in images that introduced components with CVEs

You can identify specific Dockerfile lines in an image that introduced components with CVEs.

Procedure

To view a problematic line:

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click User Workloads.
  3. Click the tab to view the type of CVEs. The following tabs are available:

    • Observed
    • Deferred
    • False positives
  4. In the list of CVEs, click the CVE name to open the page containing the CVE details. The Affected components column lists the components that include the CVE.
  5. Expand the CVE to display additional information, including the Dockerfile line that introduced the component.

15.2.8. Finding a new component version

The following procedure finds a new component version to upgrade to.

Procedure

  1. In the RHACS portal, click Vulnerability Management Results.
  2. Click the User Workloads tab.
  3. Click <number> Images and select an image.
  4. To view additional information, locate the CVE and click the expand icon.

    The additional information includes the component that the CVE is in and the version in which the CVE is fixed, if it is fixable.

  5. Update your image to a later version.

15.2.9. Exporting workload vulnerabilities by using the API

You can export workload vulnerabilities in Red Hat Advanced Cluster Security for Kubernetes by using the API.

For these examples, workloads are composed of deployments and their associated images. The export uses the /v1/export/vuln-mgmt/workloads streaming API. It allows the combined export of deployments and images. The images payload contains the full vulnerability information. The output is streamed and has the following schema:

{"result": {"deployment": {...}, "images": [...]}}
...
{"result": {"deployment": {...}, "images": [...]}}

The following examples assume that these environment variables have been set:

  • ROX_API_TOKEN: API token with view permissions for the Deployment and Image resources
  • ROX_ENDPOINT: Endpoint under which Central’s API is available
  • To export all workloads, enter the following command:

    $ curl -H "Authorization: Bearer $ROX_API_TOKEN" $ROX_ENDPOINT/v1/export/vuln-mgmt/workloads
  • To export all workloads with a query timeout of 60 seconds, enter the following command:

    $ curl -H "Authorization: Bearer $ROX_API_TOKEN" $ROX_ENDPOINT/v1/export/vuln-mgmt/workloads?timeout=60
  • To export all workloads matching the query Deployment:app Namespace:default, enter the following command:

    $ curl -H "Authorization: Bearer $ROX_API_TOKEN" $ROX_ENDPOINT/v1/export/vuln-mgmt/workloads?query=Deployment%3Aapp%2BNamespace%3Adefault
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동