Configure the Tenable compliance test uniqueness key

---
title: Configure the Tenable compliance test uniqueness key
description: Configure the uniqueness key for Tenable compliance tests to control how the system identifies configuration test records during ingestion and prevent records from being overwritten when multiple tests share the same control identifier.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/cc-tenable-config-test-uniqueness-key.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
keywords: [Tenable compliance test uniqueness key configuration]
breadcrumb: [Compliance test uniqueness key, Understanding the Tenable Vulnerability Integration, Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Configure the Tenable compliance test uniqueness key

Configure the uniqueness key for Tenable compliance tests to control how the system identifies configuration test records during ingestion and prevent records from being overwritten when multiple tests share the same control identifier.

## Before you begin

Role required: sn\_vulc.admin

## Procedure

1.  Navigate to **All** > **Configure Tenable Test Granularity**.

2.  In the Key Configuration form, confirm that:

    -   **Source Integration** is `Tenable.io`.
    -   **Table** is `Configuration Test [sn_vulc_test]`.
3.  In the **Additional configuration key** section, locate the key you want to use as the uniqueness identifier.

4.  Update the key values:

    1.  Enter **true** next to the key you want to enable.

    2.  Enter **false** next to the previously enabled key.

    For example, to switch to **compliance\_control\_id**, enter **true** next to **compliance\_control\_id** and **false** next to the previously enabled key.

    **Note:** Changing the uniqueness key affects how existing configuration test records are matched on subsequent integration runs. Test this change in a non-production environment before applying it to production.

5.  Select **Update** to save your changes.


**Related topics**  


[Tenable compliance test uniqueness key](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/cc-tenable-compliance-test-uniqueness-key.md)