• Retrieves all asset data, including asset tags, from the Tenable.io product and processes it in your instance.
• Starting with v3.0, If the Tenable.io Compliance Results Integration is activated, you can import secure configuration assessment data along with imported asset data. This data can help you the identify and respond to the configuration-related vulnerabilities on your assets.
• Creates unique CIs for unmatched assets, or updates existing CIs with the network partition identifier attribute for assets across your environment that share the same IP address.
• Coordinates the REST message calls to the Asset API.
• The output of this integration is discovered items.
• Data is imported in chunks and stored in the [sn_vul_tenable_chunk_status] table. Table cleaner automatically removes stored data from this table after 30 days.
• Starting with v2.2, Last Scan Time is imported and updated only for assets that have vulnerabilities.

• Starting with v3.0, imported secure configuration assessment data from the Compliance Results Integration along with imported data from the Assets Integration can help you identify and respond to the configuration-related vulnerabilities on your assets.
• If enabled, retrieves high-level secure configuration assessment data and processes it in your ServiceNow AI Platform instance. Imported data includes test results along with policies, configuration tests (controls) and citations with authoritative sources.
• Assessment data for missing assets or assets without asset IDs are not imported.
• If a test result is imported and its corresponding asset cannot be matched in your instance, the test result is ignored and the ID for the missing asset is stored in a temporary record in the [sn_vul_tenable_missing_asset] table.
• The total value of ignored (missing) assets is listed in the Ignored CIs field on the Configuration tab on the integration run record for this integration.

• When activated, this integration runs automatically after the assets integration is successfully completed as part of a chained integration run. This integration matches configuration assessment data with missing assets listed on the [sn_vul_tenable_missing_asset] table.
• Imports up to 200 asset IDs for any missing assets discovered or present in the instance after the assets integration import is successfully completed.
• Removes the temporary records from the [sn_vul_tenable_missing_asset] table when assets can be matched with corresponding configuration assessment data.

• This integration retrieves the scan credentials configured in Tenable.io.
• Coordinates the REST message calls to the Credentials API.
• The output of this integration is scan credentials populated in the [sn_vul_tenable_scan_credential] table,.
• The imported credentials are used to access the scanner when scan requests are initiated from the ServiceNow AI Platform.
• This integration is scheduled to run weekly.

A template record is sent to Tenable.io during rescan. This integration retrieves available Tenable.io credentials to use for rescans. Credentials are instance-specific, and a single template record is imported and securely stored temporarily on the [sn_vul_tenable_io_template] table.

• Retrieves the plugin data from the Tenable.io product. Retrieved data are based on the date the plugins were last updated by a Tenable.io integration run.
• This import ensures that the Tenable.io Identifiers (Ten IDs) are current.
• Coordinates the REST message calls to the Plugin API.
• The output of this integration is third-party vulnerabilities.

• Retrieves vulnerability data based on severity filters from the Tenable.io product and processes it in your instance. Vulnerable items are created for detection records which are in the Open and Reopened states, because these records require remediation. Existing vulnerable items are updated by Vulnerability Response if detections are Fixed, but vulnerable items are not created for Fixed detections by default, because Tenable considers Fixed vulnerabilities Mitigated.
• When the flag Create vulnerable times for Fixed Vulnerability detections is activated in Setup Assistant, new VIs are created in the Fixed state so you have visibility into the detections that created them. Since VIs are created for Fixed detections that do not already exist in your instance, this might negatively impact your import performance. You may prefer to leave this feature deactivated so that Fixed detections only update the states of existing vulnerable items.
• Creates unique CIs for unmatched assets, or updates existing CIs with the network partition identifier attribute for assets across your environment that share the same IP address.
• Coordinates the REST message calls to the Vulnerabilities API.
• The output of this integration is Closed/Fixed vulnerable items (VIs). It also creates assets and third-party entries if they don't exist.
• Data is imported in chunks and stored in the [sn_vul_tenable_chunk_status] table. Table cleaner automatically removes stored data from this table after 30 days.

This integration run is scheduled. It is a chained integration, which means after a run is successfully completed, the open vulnerabilities integration described below is triggered.

• This integration is triggered upon successful completion of the Tenable.io Fixed Vulnerabilities Integration.
• Retrieves vulnerability data based on the severity filters from the Tenable.io product and processes it in your instance.
• Creates unique CIs for unmatched assets, or updates existing CIs with the network partition identifier attribute for assets across your environment that share the same IP address.
• Coordinates the REST message calls to the Vulnerabilities API.
• The output of this integration is New/Reopened vulnerable items (VIs). It also creates configuration items and third-party entries if they don't exist. Tenable considers active vulnerabilities Cumulative (current).
• Data is imported in chunks and stored in the [sn_vul_tenable_chunk_status] table. Table cleaner automatically removes stored data from this table after 30 days.