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

  • Release version: Washingtondc
  • Updated January 30, 2025
  • 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 Vulnerability Response

    The Tenable.cs integrations enhance the Vulnerability Response and Container Vulnerability Response applications by enabling seamless data retrieval and processing of vulnerability information. These integrations allow for the management of both container and host vulnerabilities within your ServiceNow environment, streamlining compliance and security operations.

    Show full answer Show less

    Key Features

    • Multi-source Support: Integrate multiple instances of Tenable.io, Tenable.sc, and Tenable.cs across your environment.
    • Cloud-Based Integration: Facilitates the retrieval of container and host asset data, creating or updating configuration items (CIs) as needed.
    • Chained Integrations: Automates processes where subsequent integrations trigger upon the successful completion of previous ones, ensuring efficient data flow.
    • User Authentication: Supported for Tenable.sc versions, with automatic token refresh for continuity during integration runs.

    Key Outcomes

    By implementing Tenable.cs integrations, customers can expect:

    • Accurate tracking and management of new and reopened vulnerabilities, enhancing visibility into security posture.
    • Streamlined processes for updating CIs, ensuring that asset data remains current and comprehensive.
    • Improved compliance through automated vulnerability management, reducing manual effort and risk of oversight.

    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.