--- title: Understanding the Rapid7 Vulnerability Integration description: The ServiceNow Rapid7 Vulnerability Integration uses data imported from the Rapid7 data warehouse or the Rapid7 InsightVM products to help you determine the impact and priority of potentially malicious threats. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/r7-vuln-integration.html release: australia product: Vulnerability Response classification: vulnerability-response topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 11 breadcrumb: [Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Understanding the Rapid7 Vulnerability Integration The ServiceNow® Rapid7 Vulnerability Integration uses data imported from the Rapid7 data warehouse or the Rapid7 InsightVM products to help you determine the impact and priority of potentially malicious threats. Rapid7 Nexpose sensors collect data and automatically send it to the Rapid7 data warehouse \(on-premise\) or Rapid7 InsightVM \(cloud-based\) products, which continuously analyze and correlate the information. It easily integrates with ServiceNow® Vulnerability Response to map vulnerabilities to CIs and services. The Rapid7 Vulnerability Integration enriches the vulnerability data on your instance. Rapid7 integrations are entry points interacting with the Rapid7 data warehouse or Rapid7 InsightVM products, invoked as scheduled jobs. Scheduled jobs simplify the vulnerability remediation life cycle by keeping the instance synchronized with other vulnerability management systems. The scheduled jobs are run automatically and in the order specified. You can also execute individual scheduled jobs manually. **Note:** If you use both Rapid7 data warehouse and Rapid7 InsightVM as sources for your data, you run the risk of duplicate vulnerability records. **Note:** When migrating from the **Data Warehouse** integration type to the **InsightVM** type, you can deduplicate your existing data warehouse records. See [Deduplicate Rapid7 Vulnerability Integration data warehouse records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/dedup-data-warehouse.md) for more information. If you have multiple deployments of the Rapid7 InsightVM vulnerability integration, you can add an integration for each deployment. Assets, identified by multiple third-party deployments and their vulnerabilities, are consolidated and reconciled with your CMDB. This consolidation happens even when scan processes overlap between the multiple deployments. Data sourced from each deployment is identified and available in a single instance of Vulnerability Response. **Note:** You cannot delete the original vulnerability integration but you can disable it. Integrations created from disabled templates are disabled by default. There is a configured run-as user for each integration record. The default value for this user is **VR.System**. Do not change this value. ## Available versions
| Release version for Australia | Release Notes |
|---|---|
| Rapid7 Vulnerability Integration v13.6, 13.7 | For compatibility information, see [KB0856498 Vulnerability Response Compatibility Matrix and Release Schema Changes](https://support.servicenow.com/kb_view.do?sysparm_article=KB0856498) |
| Integration | Description |
|---|---|
| Rapid7 Vulnerability Integration | Retrieves vulnerability data from Rapid7 Nexpose and processes it in your instance. |
| Rapid7 Asset List Integration | Retrieves scan data once a week from Rapid7 Nexpose data warehouse and stores it in the Discovered Items module in your instance. Helps identify assets that haven't been scanned recently using **Last Scan** date. View the **Last Scan** time in the Discovered Items list in Vulnerability Response. |
| Rapid7 Category Integration | Retrieves category information from Rapid7 Nexpose. Categories provide high-level classification for vulnerabilities. |
| Rapid7 Exploit Integration | Retrieves exploit information from Rapid7 Nexpose. |
| Rapid7 Malware Kit Integration | Retrieves malware kit information from Rapid7 Nexpose. |
| Rapid7 Reference Integration | Retrieves references to external authority documents such as CVEs or vendor-specific vulnerability references. |
| Rapid7 Solution Integration | Retrieves solution data from Rapid7 Nexpose, which provides recommended solutions to specific vulnerabilities. |
| Rapid7 Superceding Solution Integration | Retrieves information about which solutions are superseded by other solutions. |
| Rapid7 Prerequisite Solution Integration | Retrieves information about the solutions that are prerequisites for other solutions. When this integration executes, it fetches the mapping of solutions and prerequisite solutions from the Rapid7 data warehouse. **Note:** This integration works only if the Vulnerability Solution Management plugin is activated. |
| Rapid7 Vulnerability Solution Map Integration | Retrieves the mapping to associate solutions with vulnerabilities. |
| Rapid7 Vulnerable Item Integration | Retrieves vulnerable item data from Rapid7 Nexpose and processes it in your instance. The outputs of this integration are vulnerable items. |
| Rapid7 Vulnerable Item Resolution Integration | Retrieves information about which vulnerable items are marked closed in Rapid7 Nexpose and closes the corresponding vulnerable items in Vulnerability Response. |
| Rapid7 Site Integration | Retrieves Site data from Rapid7 Nexpose. A site is a collection of assets that are targeted for a scan. |
| Rapid7 Asset List Integration | Retrieves host tags and scan data once a week from the Rapid7 data warehouse and stores it in the Discovered Items module in your instance. Helps identify assets that haven't been scanned recently using **Last Scan** date. View the **Last Scan** time in the Discovered Items list in Vulnerability Response |
| Rapid7 Comprehensive Vulnerable Item Integration | Imports all the Rapid7 detections for all configuration items scanned since the last successful integration run. Based on the most current imported data, vulnerable items not recently found during scans are automatically transitioned to ‘Closed’ when the Auto-Close Stale Vulnerable Items module is enabled. |