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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# The Tenable Vulnerability Integration with Configuration Compliance

# The Tenable Vulnerability Integration with Configuration Compliance {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

The Tenable.io product of the Tenable Vulnerability Integration imports
policies, controls (test results), and configuration tests for processing in the Configuration Compliance application.  
Nota:  
Starting with v14.9 of Configuration Compliance, the following terms have been renamed:{#cc-tenable-integration-overview__entry__2}

| Terminology prior to v14.9 | Terminology v14.9 onwards |
|-|-|
| Test Result Group | Remediation Task |
| Group Rules | Remediation Task Rules |
| Policy | Test group |
[Tabela 1. Changes in terminology]

## Tenable.io {#cc-tenable-integration-overview__section_jkq_hxp_kqb}

The Tenable Vulnerability Integration is supported.  
You can use imported data to:

* Identify configuration-related vulnerabilities on your assets listed in your Configuration Management Database (CMDB)
* Verify that your assets are in compliance with your policies and controls.
{#cc-tenable-integration-overview__ul_h3y_bdx_rqb}  
Assets data, policies, controls (test results), and configuration tests are imported with the following integrations:

* Tenable.io Assets Integration
* Tenable.io Compliance Results Integration
* Tenable.io Compliance Results Backfill Integration
{#cc-tenable-integration-overview__ul_s2p_zpv_kqb}

The following image illustrates how the integrations work together to import asset and
configuration assessment data and reconcile any ignored CIs overlooked during an import.
Figura 1. Import flow for secure configuration assessment results

Data is imported, updated, and displayed on the test result, policy, and configuration test
records in the Configuration Compliance application.

In some cases, the number of imported Configuration Items (CIs) is different for the Tenable.io Assets Integration and the Tenable.io Compliance
Results Integration. When this occurs, temporary records are created and stored for the
ignored asset IDs. These records can be matched later with imported assessment data by
imports from the Compliance Results Backfill Integration.

For example, let's say the Assets Integration imports 80 assets on an integration run, but
the Compliance Results Integration imports 100.  
Nota:  
You can verify the number of ignored CIs on integration runs by navigating to Tenable Vulnerability IntegrationAdministrationIntegrations. Click the name of an integration to open the record. On the Vulnerability Integration Runs Related Link, open an integration run record and select the Items tab to see the value in the Ignored CIs field. This field tracks the total of ignored (missing) assets from the import.

By comparing values in the Ignored CIs fields on each integration
run record, there is a difference of 20 ignored CIs. As a result, the backfill integration
runs automatically as shown in the preceding image. This integration imports the
configuration assessment information for the extra 20 assets found by the Compliance Results
Integration but missed by the Assets Integration. Since assessment data for missing assets
is not imported, the Tenable.io Compliance Results Backfill Integration
imports up to 200 Asset IDs per integration run to reconcile the missing assets with their
corresponding assessment data. All records created for missing or ignored assets and listed
on the temporary table are deleted after these assets and their data are matched.  
Nota:  
It may take multiple runs of these integrations to import all the ignored assets.

For more information about how to enable and configure the Tenable.io Asset
Integration, see [Configure the Tenable Vulnerability Integration using Setup Assistant](https://servicenow-prod.fluidtopics.net/plVV8uTOTcaTQaVHYV3iiA "After you have installed the Vulnerability Response Integration with Tenable application, configure it using the Setup Assistant."). See [Understanding the Tenable Vulnerability Integration](https://servicenow-prod.fluidtopics.net/lZ6IScdG7PV9XBWz173C_w "The Vulnerability Response Integration with Tenable application developed by ServiceNow engineering for the Tenable Vulnerability Integration uses data imported from the Tenable.io, Tenable.sc, and Tenable.cs products to help you prioritize and remediate vulnerabilities for your assets. The application is available with a separate subscription from the ServiceNow Store.") for more
information about the integration.

The Tenable.io Compliance Results Integration and the Tenable.io Compliance Results Backfill Integration are inactive by default.  
To activate them:

1. Navigate to Tenable Vulnerability IntegrationAdministrationIntegrations.
2. On the Tenable Integrations list, click an integration name to open the record and select the Active check box to enable it. You might prefer to leave the schedule settings in their default values for these integrations to start.
{#cc-tenable-integration-overview__ol_dcm_dfx_rqb}