---
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


---

# Invicti Vulnerability Integration

# Invicti Vulnerability Integration {#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

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.

## Invicti Vulnerability Integration {#invicti-vuln-integration__section_zvz_c51_vzb}

The Invicti Vulnerability Integration collects scanner data and makes that data available to the ServiceNow AI Platform®. It easily integrates with the ServiceNow®
Application Vulnerability Response feature of Vulnerability Response to map imported third-party application vulnerability information into your instance.  
The integration imports the following types of scanned data.

* Dynamic Application Security Testing (DAST)
* Interactive Application Security Testing (IAST)
{#invicti-vuln-integration__ul_ssr_tw1_vzb}

For more information about DAST and IAST, see [Exploring Application Vulnerability Response](https://servicenow-prod.fluidtopics.net/LBIRKIvbQAdVXepULNivHw "Application vulnerabilities are vulnerabilities on your custom software applications that are scanned throughout the application’s development life cycle.").

## Available versions {#invicti-vuln-integration__section_esm_d51_vzb}

{#invicti-vuln-integration__table_fpy_bw1_vzb__entry__2}

| Release version | Release notes |
|-|-|
| Invicti Vulnerability Integration v1.1 Invicti Vulnerability Integration 1.0 | [Application Vulnerability Response release notes](https://www.servicenow.com/docs/access?context=secops-app-vuln-resp-rn&version=australia&pubname=australia-release-notes&ft:locale=en-US) For compatibility information, see [KB0856498 Vulnerability Response Compatibility Matrix and Release Schema Changes](https://support.servicenow.com/kb_view.do?sysparm_article=KB0856498) |
[ ]

{#invicti-vuln-integration__table_fpy_bw1_vzb}

## Integrations {#invicti-vuln-integration__section_dq3_351_vzb}

The following integrations are included in the base system. The integrations are chained so that after one integration successfully completes, the next integration is initiated. The integrations run in the order listed in the
following table.

After the initial run, every day, scheduled jobs are chained to run these integrations automatically in order. You can also execute individual scheduled jobs manually. Scheduled jobs simplify the vulnerability remediation life cycle
by keeping the instance synchronized with other vulnerability management systems.  
{#invicti-vuln-integration__table_ezq_lw1_vzb__entry__2}

| Integration | Description |
|-|-|
| Invicti Application List Application | Imports applications scanned by Invicti into the Discovered Applications \[sn_vul_app_release\] table or the Scanned Application \[sn_vul_app_scanned_application\] table based on how the sn_vul.use_product_model system property is set for the CI lookup rule records. * If the product model property is set to true, an application is inserted in the Discovered Application release table. * If the product model property is set to false, an application is inserted in the Scanned Application table. {#invicti-vuln-integration__ul_rdz_qys_d1c} You can choose to activate lookup rules with configuration items (CIs) as the lookup targets by modifying the system property. If you modify it, you should also activate CI Lookup rules to match the lookup target. For more information, see: * [Configure the Invicti Vulnerability Integration](https://servicenow-prod.fluidtopics.net/QPyIEp9g5KvWBx__oq4mPQ "Before you run the integration on your instance, the installation and configuration steps must be completed so the Invicti Vulnerability Integration properly works with the Application Vulnerability Response feature of Vulnerability Response.") * [Create a CI lookup rule](https://servicenow-prod.fluidtopics.net/c9YQ6h9TJjXWnyYqVZZGkA "The CI Lookup Rules module contains rules that define what fields have matching data in the Configuration Management Database (CMDB). These rules are used to identify applications and application releases and add them to the application vulnerable item (AVI) record to aid in remediation.") * [Reapplying CI Lookup rules in Application Vulnerability Response](https://servicenow-prod.fluidtopics.net/Xt97PM~F4ccS0svXMq0nDw "You can reapply your configuration item (CI) lookup rules to update existing CIs (scanned applications and product models) on discovered application records.") {#invicti-vuln-integration__ul_zhk_klt_d1c} |
| Invicti Scan List Integration | This integration is initiated after the Application List Integration is successfully completed. This integration imports data about the date and time a scan was run. |
| Invicti Application Vulnerable Item Integration | This integration is initiated after the Scan List Integration is successfully completed. Starting with v1.1, view details such as total processing times, average times for pre- and post-integration run processes, and reports on the integration run records for the Application Vulnerable Item integration. Each vulnerability in Invicti has a type, for example,DirectoryListing. This type is mapped as a unique ID in your instance and displayed as part of the value in the Vulnerability field on the application vulnerable item (AVI) record: Invicti-DirectoryListing. For more information about mapping, see [Invicti Vulnerability Integration state mapping](https://servicenow-prod.fluidtopics.net/0qUcSx~a7lod8BWcT4lS8g "The following source states from the Invicti Vulnerability Integration and their target states in your instance are listed in the following table."). |
[Tabela 1. Invicti application vulnerability integrations]

{#invicti-vuln-integration__table_ezq_lw1_vzb}

The upper limit for items per page for all three integrations is 200.