--- title: Invicti Vulnerability Integration description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/application-vulnerability-response/invicti-vuln-integration.html release: australia product: Application Vulnerability Response classification: application-vulnerability-response topic_type: concept last_updated: "2026-07-06" reading_time_minutes: 4 breadcrumb: [Integrate with other applications, Application Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Invicti Vulnerability Integration 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 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\) - Static Application Security Testing \(SAST\) - Interactive Application Security Testing \(IAST\) - Software Composition Analysis \(SCA\) For more information about DAST and IAST, see [Exploring Application Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/app-vuln-mgmt.md). ## Available versions
Release version Release notes
If you intend to upgrade to a version that is compatible with Unified Security Exposure Management \(USEM\), select a version starting with 30.x when installing or upgrading. [https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/release-notes/secops-app-vuln-resp-rn.md](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/release-notes/secops-app-vuln-resp-rn.md)For compatibility information, see [KB0856498 Vulnerability Response Compatibility Matrix and Release Schema Changes](https://support.servicenow.com/kb_view.do?sysparm_article=KB0856498)
If you don't intend to upgrade to a version that is compatible with Unified Security Exposure Management \(USEM\), select a version number below 30.x when installing or upgrading.  
## Integrations 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. Starting with version v30.2 \(Unified Security Exposure Management \(USEM\)\) and v2.0 \(non-Unified Security Exposure Management \(USEM\)\), the integrations are grouped under Enterprise and Platform types. All the integrations are compatible with legacy \(non-Unified Security Exposure Management \(USEM\)\) and Unified Security Exposure Management \(USEM\). - Enterprise - Legacy integrations import DAST, SAST, IAST, and SCA scanned data. - Platform - Integrate application vulnerabilities from Invicti for DAST, SAST, IAST, and SCA into a unified platform alongside infrastructure vulnerabilities, providing you with a comprehensive view of your security posture. The Platform Integrations are chained like the Enterprise integrations where the next integration in the chain runs after the successful completion of the proceeding integration. The sequence starts with the Application List integration, but the run type is on\_demand. |Integration|Description| |-----------|-----------| |Application List|Initiate this integration on-demand. Imports the list of applications being scanned in Invicti Platform into your ServiceNow AI Platform® instance as discovered applications.| |Scan Summary|If configured and activated, this integration is initiated automatically after the Application List Integration is successfully completed. Pulls scan records from Invicti Platform, providing scan metadata to correlate with vulnerability findings. Updates existing records or creates new ones.| |Findings|If configured and activated, this integration is initiated after the Scan Summary Integration is successfully completed. Imports application vulnerability findings from Invicti Platform and creates or updates application vulnerable items in Vulnerability Response in your ServiceNow AI Platform®.|
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 configuration item \(CI\) lookup rule records. - If the product model property is set to `true`, an application is inserted in the Discovered Application release table. It links to a product model using product model lookup rules. If a model is not found, a model is created: a software model if a version is present in the import, and an application model if it's version agnostic. - If the product model property is set to false, it links to a CI via lookup rules. If lookup rules fail, then a Scanned Application record is created and inserted in the Scanned Application table. 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/invicti-configure.md) - [Create a CI lookup rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/avm-create-ci-lookup-rules.md) - [Reapplying lookup rules in Application Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/avr-reapplying-ci-lookup-rules.md)
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.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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/invicti-mapping.md).
The upper limit for items per page for all three integrations is 200.