Welcome to Tenable for ServiceNow

Last Updated: December 17, 2025

Tenable applications are designed to help customers who use ServiceNow with Tenable Vulnerability Management, Tenable Security Center, or Tenable OT Security.

The Service Graph Connector for Tenable application integrates Tenable assets with the ServiceNow Configuration Management Database (CMDB). Assets are imported into the CMDB through ServiceNow's Identification Reconciliation Engine (IRE). This application, once configured, allows you to bring Tenable asset data into ServiceNow as CIs and to push ServiceNow CIs to Tenable Security Center and Tenable Vulnerability Management as assets.

The Tenable OT Security for VR application integrates Tenable vulnerability findings with the ServiceNow Security Operations Vulnerability Response module. This application, once configured, syncs all of Tenable OT Security vulnerability findings into ServiceNow Vulnerable Items (VI) and Tenable Plugin details into ServiceNow Third-Party Vulnerabilities.

The Tenable for ITSM application integrates Tenable vulnerability findings into a custom table used to create incidents from the vulnerabilities. This application, once configured, syncs all of Tenable vulnerability findings into a custom vulnerabilities table and Tenable Plugin details into a second custom table.

Tenable Assets Service Graph Connector (ServiceNow App) or ServiceNow Connector for Tenable Exposure Management?

This document covers the standard Tenable integration with ServiceNow. Tenable also now offers the ServiceNow Connector for use with Tenable Exposure Management.

The ServiceNow App allows you to sync assets bi-directionally between Tenable Vulnerability Management (TVM) and Tenable Security Center (TSC). This allows you to create and update configuration items (CIs) in ServiceNow as well as create/update assets (TVM) or asset lists (TSC). Due to limitations in the TVM asset import API, when pushing to TVM the app only passes network details and servicenow sys_id.

The ServiceNow Connector for Tenable Exposure Management leverages the entire Tenable Exposure Management data model while the Tenable-provided ServiceNow Integration utilizes the TVM data model. This provides a greater ability to map ServiceNow fields to Tenable Exposure Management fields, and you can also use Tenable Exposure Management custom fields and tags. The ServiceNow Connector for Tenable Exposure Management is not bi-directional like the ServiceNow App. While the Tenable Exposure Management connector is certainly more robust, setup configuration is much more involved than the ServiceNow App with regard to importing assets to Tenable.

For more information, refer to ServiceNow Connector and Connectors.

Application Dependencies

  • Platform compatibility:

    • Tenable Vulnerability Management, Tenable Security Center 5.7+, or Tenable OT Security

    • ServiceNow Yokohama, Zurich

  • Plugins required:

    • ITOM Discovery License - 1.0.0

    • ITOM Licensing - 1.0.0

    • CMDB CI Class Models - 1.76.0

    • Integration Commons for CMDB - 2.20.0

    • SGC Central - 2.2.0

    • (Optional - Required when using Domain Separation ) Domain Separation

    • (Optional - Required for VR) ServiceNow Vulnerability Response - 23.0.0

    • (Optional - Required for ITSM) Incident - 1.0.0