Configure the Tenable compliance test uniqueness key

  • Release version: Zurich
  • Updated April 27, 2026
  • 1 minute to read

    • 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.