---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/security-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Integrating Application Vulnerability Response with other applications

# Integrating Application Vulnerability Response with other applications {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Vulnerability Response includes support for third-party integrations.

## Third-party integrations {#avm-integrations__section_k3d_nzy_mbb}

Application vulnerability integrations help enrich the application vulnerability data on your instance by retrieving data from external systems and vendors. See the following overview topics for more information about supported integrations:

* [Fortify Vulnerability Integration](https://servicenow-prod.fluidtopics.net/_YUa7WaMUiKtNyrUKQ01FA "The Fortify Vulnerability Integration uses data imported from the Fortify product to help you determine the impact and priority of flaws in your code.")
* [GitHub Application Vulnerability Integration](https://servicenow-prod.fluidtopics.net/m74vqDtvz5miCoHnGQl5MA "The GitHub Application Vulnerability Integration imports Static application security testing (SAST) and Software Composition Analysis (SCA) data to help you view vulnerability alerts in the repositories in your GitHub environment.")
* [Invicti Vulnerability Integration](https://servicenow-prod.fluidtopics.net/ThoDpwISYt9tshia0V~_gw "The Invicti Vulnerability Integration uses application data imported from the Invicti product to help you determine the impact and priority of flaws in your code.")
* [Veracode Vulnerability Integration](https://servicenow-prod.fluidtopics.net/8z865y0OchrgY45HKIxLqg "The Vulnerability Response Integration with Veracode application uses data imported from the Veracode product to help you determine the impact and priority of flaws in your code.")
* [Vulnerability Response Integration with Black Duck](https://servicenow-prod.fluidtopics.net/7IbNCFARX3poseAz90Masw "The Vulnerability Response integration with Vulnerability Response Integration with Black Duck uses the data that is imported from the Black Duck Software Composition Analysis (SCA) tool to help you determine the impact and priority of the flaws in your code.")
* [Manual ingestion of vulnerabilities for Application Vulnerability Response](https://servicenow-prod.fluidtopics.net/OM76Q8vXu0SNwghrx~ojwQ "Security professionals and application testers can create and manage the application penetration test findings within the Penetration Testing Workspace.")
* [Atlassian Jira Integration](https://servicenow-prod.fluidtopics.net/icza6LLShkOXVsebnqqWpQ "The Atlassian Jira integration with Vulnerability Response enables you to leverage different issue-tracking and agile management tools for tracking efforts of vulnerability remediation.")  
  Importante:  
  In the Vulnerability Manager Workspace, you can create an agile issue manually using the [list action](https://servicenow-prod.fluidtopics.net/0cM_M95TNXQK~LAulwyOvw "When a list action: Create Jira Issue is triggered, records that match the rule configuration criteria should be considered for “Create Jira Issue” and those records should be ingested into the sn_vul_agile_tool_manifest table with the mapping selected in the configuration rule.") and [form action](https://servicenow-prod.fluidtopics.net/yBk4h3u1rWjNP14K3jeGAg "Create an agile issue manually using form action. If the record is matched with any configuration rule condition, then a pop-up box will be populated with values that are selected in the configuration rule and if it does not match any criteria then the user will be allowed to select values for pre-defined fields.") to track the remediation of AVITs and RTs.

{#avm-integrations__ul_nx1_jb3_vzb}  
Nota:  
Multi-source integrations are not supported in Application Vulnerability Response. Third-party integrations are treated separately. If more than one third-party integration application is in use in your environment, there is no application vulnerable item
(AVI) deduplication across integrations.

## Vulnerability Response applications and CSDM tables {#avm-integrations__id_gkd_tzh_q2c}

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](https://servicenow-prod.fluidtopics.net/A~txrKC7dpU8SSby8jzxZw "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.") for more information.

## Additional notes for integrations {#avm-integrations__section_aw5_cnz_wvb}

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 Application 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.  
Nota:  
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.
{#avm-integrations__ul_g23_sgw_dyb}

Vulnerability integrations for Application Vulnerability Response are configured to run on a scheduled basis. However, you can run them manually when needed.

Role required: sn_vul.app_read_integrations

1. Navigate to AllApplication Vulnerability ResponseAdministrationIntegrations.
2. Open the record for the integration that you want to run.
3. Click Execute Now.
{#avm-integrations__ol_ivd_2y1_n2c}