Tenable.cs integrations with the Vulnerability Response and Container Vulnerability Response application

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Tenable.cs Integrations with the Vulnerability Response and Container Vulnerability Response Application

    The Tenable.cs integrations enhance the Vulnerability Response and Container Vulnerability Response applications by providing a seamless connection to Tenable's cloud-based security solutions. These integrations allow users to manage and track vulnerabilities more effectively within their ServiceNow environment.

    Show full answer Show less

    Key Features

    • Multi-source Support: Users can integrate multiple instances of Tenable.io, Tenable.sc, and Tenable.cs across their environment.
    • Discovered Items Tracking: The "Agent exists" column indicates whether an asset scan is valid, enhancing the reliability of vulnerability data.
    • Integration Types: Various integrations are available, including:
      • Cloud Container Assets Integration: Gathers container asset data and updates configuration items (CIs).
      • Open Cloud Container Vulnerabilities Integration: Automatically retrieves container vulnerabilities and updates CIs.
      • Fixed Cloud Container Vulnerabilities Integration: Follows the Open Cloud integration to manage fixed vulnerabilities.
      • Open Cloud Host Vulnerabilities Integration: Similar to container integrations but for host vulnerabilities.
      • Fixed Cloud Host Vulnerabilities Integration: Tracks fixed vulnerabilities in host configurations.
    • User Authentication: Supports user authentication for seamless integration with Tenable.sc, ensuring secure connections.

    Key Outcomes

    By implementing these integrations, ServiceNow customers can expect improved visibility and management of vulnerabilities across their environments, leading to enhanced security posture. Automatic updates and real-time data processing streamline vulnerability management workflows, allowing teams to respond swiftly to emerging threats. Additionally, users can rely on background token management, ensuring uninterrupted integration processes.

    The Tenable.cs integrations in the Vulnerability Response Integration with Tenable application are available in the Vulnerability Response and Container Vulnerability Response applications.

    Starting with v20.0 Vulnerability Response, if an asset is scanned by an agent, the "Agent exists" column in the Discovered Items list displays "true," indicating that the scan is authentic.

    List of Tenable.cs integrations

    Multi-source is supported for all the Tenable.io, Tenable.sc, and Tenable.cs integrations. You can add and deploy multiple instances of the following integrations across your environment from Setup Assistant in Vulnerability Response. You can also install and configure the Vulnerability Response Integration with Tenable application from Setup Assistant.

    Tenable.cs is a cloud-based enterprise integration. See the following table for the names and descriptions of the supported integrations for the Tenable.cs product.

    Table 1. Tenable.cs integrations
    Integration Description
    Tenable.cs Cloud Container Assets Integration
    • Retrieves all container asset data from the Tenable.cs product and processes it in your instance.
    • Creates unique CIs for unmatched assets, or updates existing CIs. Coordinates the REST message calls to the Asset API.

    The output of this integration is Discovered Container Images, Docker Images, and Container Repositories.
    Tenable.cs Open Cloud Container Vulnerabilities Integration When activated, this integration runs automatically after the container assets integration is successfully completed as part of a chained integration run.
    • Retrieves container vulnerability data based on the severity filters from the Tenable.cs product and processes it in your instance.
    • Creates unique CIs for unmatched assets, or updates existing CIs.
    • Coordinates the REST message calls to the Vulnerabilities API.

    The output of this integration is New/Reopenedcontainer vulnerable items (CVIs). If they don't exist, it also creates discovered container images, docker images, container repositories, image findings, third-party entries, and Common Vulnerabilities and Exposures (CVE).
    Tenable.cs Fixed Cloud Container Vulnerabilities Integration This integration is triggered on successful completion of the Tenable.cs Open Cloud Container Vulnerabilities Integration.
    • Retrieves container vulnerability data based on the severity filters from the Tenable.cs product and processes it in your instance.
    • Creates unique CIs for unmatched assets, or updates existing CIs
    • Coordinates the REST message calls to the Vulnerabilities API.

    The output of this integration is New/Reopened container vulnerable items (CVIs). If they don't exist, it also creates discover container images, docker images, container repositories, image findings, third-party entries, and CVEs. Image findings are created in closed state.
    Tenable.cs Open Cloud Host Vulnerabilities Integration
    • Retrieves vulnerability data based on the severity filters from the Tenable.cs product and processes it in your instance.
    • Creates unique CIs for unmatched assets, or updates existing CIs.
    • Coordinates the REST message calls to the Vulnerabilities API.

    The output of this integration is New/Reopened vulnerable items (VIs). If they don't exist, it also creates configuration items, third-party entries, and CVEs. Vulnerability Detections are created in open state.
    Tenable.cs Fixed Cloud Host Vulnerabilities Integration This integration is triggered on successful completion of the Tenable.cs Open Cloud Host Vulnerabilities Integration.
    • Retrieves vulnerability data based on the severity filters from the Tenable.cs product and processes it in your instance.
    • Creates unique CIs for unmatched assets, or updates existing CIs.
    • Coordinates the REST message calls to the Vulnerabilities API.

    The output of this integration is close vulnerable items (VIs). If they don't exist, it also creates configuration items, third-party entries, and CVEs. Vulnerability Detections are created in closed state.

    User authentication and Tenable.sc

    User authentication is supported by your ServiceNow AI Platform® instance and version 5.13 of the Tenable.sc product. User authentication is required if you’re using version 5.12 and earlier of the Tenable.sc product.

    When you select user authentication for the Tenable.sc integrations, tokens might expire and be replaced during integration runs. In the Notes column on the Vulnerability Integration Run record (VIN), the following message is displayed for a process when a token expires, Error: Token validation is failed. If this message is displayed, no action is required. Expired tokens are automatically refreshed in the background and the message doesn’t indicate a pause or error with the integration process.