---
title: Configure container image granularity keys for Container Vulnerability Response
description: Configure the keys that generate Container Vulnerability Response findings.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/container-vulnerability-response/cvr-configure-key-granularity.html
release: australia
product: Container Vulnerability Response
classification: container-vulnerability-response
topic_type: task
last_updated: "2026-03-11"
reading_time_minutes: 2
breadcrumb: [Configuring granularity keys, Configure, Container Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Configure container image granularity keys for Container Vulnerability Response

Configure the keys that generate Container Vulnerability Response findings.

## Before you begin

Role required: sn\_vul\_container.configure\_vi\_granularity

## Procedure

1.  Navigate to **All** > **Container Vulnerability Response** > **Administration** > **Configure VI Granularity**.

2.  Select a record for the integration you want to set the keys for.

3.  Select one for Data Source:

    |Option|Description|
    |------|-----------|
    |**Scanner Information**|Use your third-party scanner as a data source.|
    |**Discovery Information**|Default setting. Use ServiceNow Discovery as your data source.|

    For more information about data sources and keys, see [Configuring container image granularity keys for Container Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/cvr-configuring-findings-key-granularity.md).

4.  Select one or more components for your key.

    For more information about how component selections affect your keys and finding \(CVIT\) creation, see [Configuring container image granularity keys for Container Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/cvr-configuring-findings-key-granularity.md).

5.  Select **Apply Changes**.

    After you configure key granularity, if you want to [use Discovery Information as your data source](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/cvr-configuring-findings-key-granularity.md), you must schedule the \[Populate image relationships\] scheduled job. See [Configuring container image granularity keys for Container Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/cvr-configuring-findings-key-granularity.md) for more information.

    View populated on the following columns on the Container Vulnerable Item \[sn\_vul\_container\_image\_vulnerable\_item\] table. These columns have been renamed to match the data sources:

    -   Cluster \(Scanner\) Namespace \(scanner\), and Service \(scanner\) if the **Scanner Information** data source is selected for the key configuration.
    -   Cluster \(Discovery\), Namespace \(Discovery\) and Service \(Discovery\) if the **Discovery Information** data source is selected for the key configuration.
    **Note:**

    -   On the CMDB Docker container image record on the Discovered Container Image \[sn\_vul\_container\_image\] table, only **Scanner Information** is directly populated with the column names listed above.
    -   You can view discovery-based data \(cluster/namespace/service\) by opening the Docker image record on the Discovered Container Image record. On this record, view the related items/relations section for the data populated by **Discovery Information**.

**Parent Topic:**[Configuring container image granularity keys for Container Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/cvr-configuring-findings-key-granularity.md)