Vulnerability Response integrations

  • Release version: Australia
  • Updated March 12, 2026
  • 4 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 Vulnerability Response Integrations

    Vulnerability Response supports third-party integrations, allowing for enhanced management and visibility of vulnerabilities within your organization. Administrators can monitor integration statuses through the Security Exposure Management Workspace Administration console, ensuring operational health and troubleshooting capabilities.

    Show full answer Show less

    Key Features

    • Integration Monitoring: With version 30.0 and above, administrators can view and troubleshoot the run statuses of third-party applications.
    • Vulnerability Reconciliation: Imported vulnerabilities are matched against assets in your CMDB, creating vulnerable items that are prioritized and assigned for remediation.
    • Integration Support: A variety of third-party integrations, including those from Rapid7, Qualys, and Tenable, are available for importing vulnerabilities and managing them effectively.
    • Timeout Management: Enhancements from version 18.2.4 provide heartbeat timestamps to prevent integration timeout errors during data processing.
    • Custom Integrations: Users can create additional integrations not available in the ServiceNow Store as needed.

    Key Outcomes

    By leveraging these integrations, ServiceNow customers can expect improved visibility into vulnerabilities, streamlined remediation processes, and the ability to manage multiple third-party applications effectively. This integration framework supports better decision-making and operational efficiency within security management practices.

    Vulnerability Response includes support for third-party integrations. Included in this section are some basic guidelines for developing your own integrations.

    Third-party integrations

    Refer to the notes and text for how third-party integrations and the Vulnerability Response application create vulnerable items.

    Starting with v30.0 of Vulnerability Response, monitor installed integrations within the Security Exposure Management Workspace Administration console. Administrators can now view and troubleshoot integration run statuses for installed third-party applications, ensuring better visibility and operational health. For more information, see Review Unified Security Exposure Management integrations.

    Imported vulnerabilities from the National Vulnerability Database (NVD) and detection data from third-party scanners are reconciled with the assets in your CMDB. When an imported vulnerability matches an existing asset, a vulnerable item is created. Vulnerable items are grouped automatically into tasks for remediation, risk-scored with business context, prioritized and assigned to appropriate teams for remediation.

    Note:

    Third-party integrations are treated separately. If more than one third-party integration application is in use in your environment there is no vulnerable item (VI) deduplication across integrations. For example, VI deduplication between Rapid7 and Qualys is not available.

    However, mismatches in detection count between a third-party scanner (for example, Qualys) to VIs in your ServiceNow instance are expected, since we dedupe across IPs, ports and so on.

    The following table provides a list of Vulnerability Response infrastructure integrations created by ServiceNow® and partners to import vulnerabilities and create vulnerable items.

    For information about third-party integrations supported by Application Vulnerability Response see, Integrating Application Vulnerability Response with other applications

    Additional notes for integrations

    If multiple deployments are supported for an integration, see Create domain-separated imports for an integration.

    • You can install, configure, schedule, and launch on-demand many of the integration applications from within Setup Assistant.
    • You can install the Rapid7 Vulnerability Integration application from Setup Assistant, but configuration is not supported for this integration from within the Setup Assistant. See Install the Rapid7 Vulnerability Integration for more information.
    • The Tenable for Vulnerability Response application by Tenable is created and maintained by Tenable. See their documentation at Tenable for Vulnerability Response.
    During integration execution, multiple processes are generated, and data is received in the form of pages. Each process can contain one or more import queue entries with attached data in pages. These entries must process the data within the one-hour time limit. However, if the payload size is large, the processing time may exceed one hour or get stuck, resulting in an integration timeout error. The integration continues to process the data despite the timeout error. To avoid this miscommunication, starting from version 18.2.4 of Vulnerability Response, timestamps (heartbeats) are sent periodically to indicate if the queue is active and processing data. The Last Record Processed field in the Import Queue Entry page is updated based on the count of records the import queue creates or updates. In case an import queue entry exceeds the one-hour time limit, the system checks the Last Record Processed field to see if it is also older than one hour. If it is, this indicates that the import queue entry is stuck, and it is timed out to prevent any further delays in processing.
    Note:
    The Last Record Processed field is updated based on what is defined in the following system properties:
    • sn_sec_cmn.record_threshold_heartbeat: Defines the number of processed records, after which the heartbeat (timestamp) is sent to the import queue entry.
    • sn_sec_cmn.maximum_heartbeat_delay: Defines the time after which the import queue entry must be timed out.
    Starting from VR v17.1, the following integration process state names have been updated:
    State name prior to V17.1 State name V17.1 onwards
    Processing Retrieving
    WaitComplete Waiting/Processing
    Note:
    You can view the attachments that are downloaded and processed. When the status of the integration run is waitcomplete, it displays the percentage of integration that is complete.

    Vulnerability Response applications and CSDM tables

    The Vulnerability Response, Application Vulnerability Response, third-party vulnerability integrations and Software Bill of Materials applications manage (contribute data to) CSDM tables. These applications also use data from CSDM tables that other applications generate. Several ServiceNow products, therefore, benefit from and add value to these Security Operations applications. See Vulnerability Response applications and CSDM tables for more information.

    Manually created integrations

    You can add other integrations that are not available as ServiceNow Store applications, as needed. See Manually create a vulnerability integration for more information.