---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Configure granularity keys

# Configure container image granularity keys for Container Vulnerability Response {#ariaid-title1}

* Release version: Australia
* 
* Updated March 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the keys that generate Container Vulnerability Response findings.

## Before you begin

Role required: sn_vul_container.configure_vi_granularity

## Procedure

1. Navigate to AllContainer Vulnerability ResponseAdministrationConfigure VI Granularity.
2. Select a record for the integration you want to set the keys for.
3. Select one for Data Source:  
   {#cvr-configure-key-granularity__table_p1s_lyl_43c__entry__2}

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

   {#cvr-configure-key-granularity__table_p1s_lyl_43c}

   For more information about data sources and keys, see [Configuring container image granularity keys for Container Vulnerability Response](https://servicenow-prod.fluidtopics.net/oIxOZaLvuiu6iXiiNqyGqw "You can configure the keys that generate Container Vulnerability Response findings (container vulnerable items) to help you determine how and when they are created from imported container vulnerability data.").
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://servicenow-prod.fluidtopics.net/oIxOZaLvuiu6iXiiNqyGqw "You can configure the keys that generate Container Vulnerability Response findings (container vulnerable items) to help you determine how and when they are created from imported container vulnerability data.").
5. Select Apply Changes.  
   After you configure key granularity, if you want to [use Discovery Information as your data source](https://servicenow-prod.fluidtopics.net/oIxOZaLvuiu6iXiiNqyGqw "You can configure the keys that generate Container Vulnerability Response findings (container vulnerable items) to help you determine how and when they are created from imported container vulnerability data."), you must schedule the \[Populate image relationships\] scheduled job. See [Configuring container image granularity keys for Container Vulnerability Response](https://servicenow-prod.fluidtopics.net/oIxOZaLvuiu6iXiiNqyGqw "You can configure the keys that generate Container Vulnerability Response findings (container vulnerable items) to help you determine how and when they are created from imported container vulnerability data.") 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.

   {#cvr-configure-key-granularity__ul_vqb_3pl_43c}  
   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.
   {#cvr-configure-key-granularity__ul_i3y_gdr_43c}

*[\>]: and then