---
sourceDocument: Yokohama Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/security-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Install and configure RISKIQ and WHOISIQ

# Install and configure RISKIQ and
WHOISIQ {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Before you run the integration on your instance, complete the installation and
configuration steps so the RISKIQ and
WHOISIQ applications properly
integrate with ServiceNow AI Platform
Security Operations.

## Before you begin

Role required: admin, RISKIQ and WHOISIQ
admin.
Complete the following setup checklist prior to installation. These setup tasks are required for a smooth installation and configuration.{#install-and-config-riskiq__table_gd1_sfv_zcb__entry__2}

| Setup task | Description |
|-|-|
| Verify that you have assigned the required roles. | The following roles are required for installation, configuration, and verification of expected results: * The System Administrator (admin) installs the app and assigns the Security Incident Administrator (sn_si.admin) role. * The Security Incident Administrator (sn_si.admin) oversees configuration and verifies expected results. This role also has access to the Security Operations module and assigns the Security Incident Analyst (sn_si.analyst) role. * The Security Incident Analyst (sn_si.analyst) works with Security Incident records. {#install-and-config-riskiq__ul_hd1_sfv_zcb} |
| Obtain an Username and API key. | Visit the website for information on the API key and how to create an account: [RISKIQ website](https://api.riskiq.net/api/concepts.html). The configuration requires that you enter the API key. |
| Verify that the ServiceNow core applications that are required to support the integration are installed and activated before you install the application for the integration. | Madrid and later release requirements For the Madrid release and later family releases, the Security Incident Response Dependency plugin (com.snc.si_dep) is required. This plugin automatically installs all the dependencies that are required to support the Security Incident Response product. Install and activate this plugin before you install and activate the other Security Operations applications required by the integration. Verify that the following Security Operations applications are installed and activated from the ServiceNow Store. If not installed, install and activate one application at a time in the following order to ensure a smooth installation. 1. Security Incident Response 2. Security Integration Framework 3. Security Support Common 4. Security Support Orchestration {#install-and-config-riskiq__ol_qwy_vrt_fhb} For more information on setting up your ServiceNow AI Platform instance for the integration, see [Get entitlement for a Security Operations product or application](https://www.servicenow.com/docs/ZG8H~Dkb43mJCGyzY2RF7g "The first step in installing a Security Operations application is to verify that the application or the product and its associated applications have valid ServiceNow entitlements.") and [Activate a ServiceNow Store application](https://www.servicenow.com/docs/kHqtg6gvS5wuwIk0efDLVw "After an application has been given entitlement, you must activate its dependencies plugin and activate the application. This process also applies to applications downloaded to sub-production instances."). |
[ ]

{#install-and-config-riskiq__table_gd1_sfv_zcb}

## Procedure

1. If you have not installed the application for the integration, see [Install a Security Operations integration](https://www.servicenow.com/docs/rmdDLn9I36POHMelYkGg0Q "All ServiceNow integrations are available on the ServiceNow Store. Core applications, such as Security Incident Response, are visible in the ServiceNow Products tab on the store. Integration add-ons are visible in the Certified Apps tab.") and follow the steps to install it.
2. Once the installation completes, navigate to Security OperationsIntegrationsIntegrations Configurations and locate the API tile.
3. Click Configure.  
4. In the RiskIQ Configuration dialog box that is displayed, enter the Username and API key.  
5. Click Submit.
6. Verify successful configuration.  
   When configuration is successfully completed, the Security Integrations page with the integration tiles is displayed.
If an error message is displayed, the Username or API key may be invalid. Verify that your username and API key are correct:Figure 1. Troubleshooting
**Previous topic:** [Supported observables for RISKIQ and RISKIQ WHOISIQ](https://www.servicenow.com/docs/9cQ8mWAPLVzCELCGSoY6ZA "The RISKIQ API supports automatic SSL certificate lookups on IP address, file hash, Certificate Serial Number, domain, and URL observables. URL and domain observables are enriched automatically with the WHOISIQ API. For observable enrichment on other types of observables with the WHOISIQ API, create observables and run lookups manually from the Observables table.")  
**Next topic:** [Verify expected results for RISKIQ SSL certificate lookups](https://www.servicenow.com/docs/CCiX9DCRHUydHUABWzLsfQ "When a security incident generates observables for URLs, domains, IP addresses, certificate file hashes (SHA-1 fingerprint), and certificate serial numbers, security incident analysts use the SSL certificate lookup results to verify sites have certificates that have been issued by a trusted public Certificate Authority (CA).")

*[\>]: and then