--- title: Preparing for the Shodan Exploit Integration description: A successful Shodan Exploit Integration requires planning and careful execution of pre-integration tasks. Prepare for the integration by performing these tasks. The Shodan Exploit Integration assumes that you are familiar with the Shodan search engine and API. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/shodan-exploit-prerequisites.html release: australia product: Vulnerability Response classification: vulnerability-response topic_type: task last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Understanding the Shodan Exploit Integration, Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Preparing for the Shodan Exploit Integration A successful Shodan Exploit Integration requires planning and careful execution of pre-integration tasks. Prepare for the integration by performing these tasks. The Shodan Exploit Integration assumes that you are familiar with the Shodan search engine and API. ## Before you begin The Shodan Exploit Integration requires an API key. Register with the Shodan [website](https://developer.shodan.io/api/requirements) for a free subscription to acquire this key. Role required: admin ## About this task **Note:** Before running the integration, make any necessary configuration changes based on your requirements. - If you have not imported NIST Vulnerability Database \(NVD\) data into Vulnerability Response, do so before installing the Shodan Exploit Integration. Importing the NVD data ensures that your Common Vulnerability and Exposure \(CVE\) data auto-populates the exploit records. Without NVD data, a placeholder is created in the exploit record and not entered until the next NVD update. For more information on NVD, see [Importing data with the NVD and CWE integrations and managing third-party libraries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/c_NVDAndCWEDataImport.md). - 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.