How to Enhance Threat Prioritization with Securonix ThreatQ and AI SPERA Criminal IP Integration

<h2>Introduction</h2> In today's cybersecurity landscape, security teams are overwhelmed with alerts, many of which lack sufficient context to prioritize effectively. The recent partnership between Securonix and AI SPERA addresses this challenge by integrating Criminal IP threat intelligence directly into the Securonix ThreatQ Platform. This guide provides a step-by-step approach to setting up and leveraging this integration to enrich your threat intelligence with real-time IP context, enabling faster, more accurate incident response. By the end, you'll be able to transform raw IP data into actionable insights that reduce false positives and focus your team on the most critical threats.<figure style="margin:20px 0"><img src="https://d15shllkswkct0.cloudfront.net/wp-content/blogs.dir/1/files/2026/04/securonixaispera.png" alt="How to Enhance Threat Prioritization with Securonix ThreatQ and AI SPERA Criminal IP Integration" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: siliconangle.com</figcaption></figure> <h2 id="prerequisites">What You Need</h2> Before you begin, ensure you have the following materials and prerequisites: <ul> <li>Active Securonix ThreatQ Platform Subscription – The platform must be configured and accessible with administrative privileges.</li> <li>AI SPERA Criminal IP API Access – A valid subscription to Criminal IP with an API key. Register at the AI SPERA website if not already done.</li> <li>Network Connectivity – Your ThreatQ instance must be able to reach AI SPERA's API endpoints (outbound HTTPS).</li> <li>User Permissions – You need roles that allow configuring data sources, integration settings, and playbooks in ThreatQ.</li> <li>Basic Understanding of Threat Intelligence Enrichment – Familiarity with IP reputation, threat scoring, and orchestration concepts is helpful.</li> </ul> <h2>Step-by-Step Integration Guide</h2> <h3 id="step1">Step 1: Access ThreatQ Integration Settings</h3> Log in to your Securonix ThreatQ console as an administrator. Navigate to the Administration menu and select Integration Settings (or Data Sources, depending on your version). This is where you'll manage all third-party connectors. Look for the option to add a new integration – typically labeled “Add Integration” or “+ New Data Source.” <h3 id="step2">Step 2: Configure the Criminal IP Data Source</h3> In the integration catalog, locate AI SPERA Criminal IP. If it does not appear, verify your ThreatQ version supports custom integrations, or contact Securonix support. Click on it and provide the following details: <ul> <li>Name – Give it a descriptive label, e.g., “Criminal IP – Real-Time IP Intel.”</li> <li>API Key – Enter the API key provided by AI SPERA. Ensure it is stored securely.</li> <li>Base URL – Use the standard endpoint: <code>https://api.criminalip.io</code> (or as specified in your subscription).</li> <li>Polling Interval – Define how often ThreatQ should fetch new intelligence. For real-time enrichment, set a short interval (e.g., every 5 minutes).</li> </ul> Click Test Connection to validate the credentials. A success message confirms the integration is ready. <h3 id="step3">Step 3: Map Fields and Enable Enrichment</h3> After saving the data source, you need to map fields so ThreatQ can automatically enrich incoming IP indicators. Go to Enrichment Rules under the integration settings. Create a new rule: <ol> <li>Trigger Condition – Choose “When an IP indicator is added or updated.”</li> <li>Action – Select “Query Criminal IP” and specify the enrichment type (e.g., reputation, abuse score, geolocation).</li> <li>Field Mapping – Map ThreatQ's IP Address field to the Criminal IP API's <code>ip</code> parameter. Then map returned fields like <code>abuse_confidence_score</code>, <code>country</code>, <code>isp</code> into corresponding ThreatQ fields.</li> <li>Priority – Set a priority for enriched data (e.g., “High”) to ensure it appears prominently in alerts.</li> </ol> Save the rule. Now every new or updated IP in ThreatQ will automatically trigger a lookup against Criminal IP. <h3 id="step4">Step 4: Build Playbooks for Automated Response</h3> To maximize value, use ThreatQ's orchestration capabilities to create playbooks that act on enriched intelligence. Go to Playbooks and choose Create New Playbook. Example workflow: <ul> <li>Trigger – When an IP with a Criminal IP abuse score above 80 is detected.</li> <li>Actions – Block the IP at the firewall (via SIEM integration), send a high-priority alert to the SOC, and automatically create a ticket in your ITSM system.</li> <li>Conditional Logic – If the IP is from a known bad ISP, escalate to a senior analyst.</li> </ul> Save and activate the playbook. This automation reduces manual investigation time.<figure style="margin:20px 0"><img src="https://s3.us-west-2.amazonaws.com/cube365-prod/related-content/e810e50d-1091-4ce3-9cc2-0232848a8d60.png" alt="How to Enhance Threat Prioritization with Securonix ThreatQ and AI SPERA Criminal IP Integration" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: siliconangle.com</figcaption></figure> <h3 id="step5">Step 5: Analyze and Prioritize Indicators</h3> With integration running, open the Indicators tab. You'll see IP addresses now display enriched data from Criminal IP, such as: <ul> <li>Abuse Confidence Score – A percentage indicating likelihood of malicious activity.</li> <li>Historical Context – First seen, last seen, and related incidents.</li> <li>Geolocation & ISP – Helps distinguish between legitimate cloud providers and anonymous proxies.</li> </ul> Use the Prioritization View to sort IPs by score. This allows you to focus on the most dangerous threats first. For example, an IP with a score of 95 and recent activity should be investigated immediately, while a score of 10 with no history can be deprioritized. <h3 id="step6">Step 6: Monitor and Refine Integration Performance</h3> Regularly review the integration's health under Logs & Monitoring. Look for errors such as API timeouts or quota limits (Criminal IP may impose daily request caps). Adjust the polling interval if needed. Also, periodically refine your enrichment rules – for instance, add extra fields like threat type or associated malware as new API features become available. Share feedback with your team to fine-tune playbooks for evolving threats. <h2 id="tips">Tips for Success</h2> <ul> <li>Start Small – Initially enable enrichment for a subset of indicators (e.g., external IPs only) to avoid overwhelming the system.</li> <li>Combine with Local Intel – Don't rely solely on Criminal IP; integrate with other threat feeds (e.g., VirusTotal, AlienVault) for multi-source validation.</li> <li>Monitor API Usage – Keep track of your monthly query volume to avoid overage charges. Set up alerts when you reach 80% of your quota.</li> <li>Use Tags for Context – Automatically tag IPs with Criminal IP's “botnet,” “scanner,” or “proxy” labels to simplify filtering in dashboards.</li> <li>Test Thoroughly – Before rolling out to production, test the integration in a sandbox environment. Verify that field mappings produce accurate values.</li> <li>Document Your Workflow – Maintain internal documentation of the integration steps, playbook logic, and enrichment rules for future reference and training.</li> </ul> By following this guide, your security operations center will gain deeper context for IP indicators, reduce false positives, and accelerate incident response. The Securonix–AI SPERA partnership transforms raw data into a powerful decision-making tool. Start implementing today and experience the impact of enriched threat intelligence.

Tags: