The images in this article were generated with artificial intelligence. How we publish
The announced integration between Criminal IP and Securonix to incorporate Criminal IP intelligence into ThreatQ represents a practical step towards the convergence of infrastructure exposure data with the orchestration and prioritization of existing threats. Instead of simply sharing traditional commitment indicators (IOC), Criminal IP provides a layer of visibility on how assets and infrastructure are exposed on the Internet, which allows security teams to understand not only that an IP is associated with malicious activity, but also in what operational context this IP is located (open ports, accessible services, proxy / VPN, known vulnerabilities, etc.).
Integrating this context into ThreatQ means that research and analysis boards receive real-time enrichment without forcing analysts to abandon their workflow. Thanks to the Criminal IP APIs that feed ThreatQ, incoming IP indicators can be automatically enriched with malicious scores and exposure attributes, and these data can be continuously evaluated by ThreatQ rules and orchestrations. The practical result is faster triage, more coherent prioritization and less operational friction between detection and response.

However, not all technological change is only immediate gain: there are important implications that teams should consider before deploying and relying on this type of integration. Exposure intelligence is powerful when contextualized with its own telemetry (logs, EDR, firewall, etc.), but can induce errors if interpreted in isolation; an IP with open ports is not necessarily a compromised asset, and an IP with high maliciousness score can be a legitimate proxy used by customers or partners. This is why it is key to establish correlation and verification mechanisms within the IMS / SOAR to avoid alarm overloads and misresponses.
From the operational point of view, I recommend that teams adopt integration with a governance plan: define score thresholds that activate automatic actions, identify which attributes should generate alerts versus only information annotations, and design specific playbooks that include manual verification steps before blocking critical assets. It is also appropriate to implement data quality controls and regularly review the prioritisation rules to prevent changes in network telemetry from causing noise or blindness in the face of real threats.

Another aspect to consider is the latency and coverage of intelligence. Although Criminal IP promises continuous enrichment, equipment must measure the freshness of signals in their environment and map gaps - IP regions, ASN or less covered service types may require additional sources. Complementing integration with other sources of reputation and internal feedback increases efficiency: ThreatQ is designed to centralize and prioritize data from multiple sources, so a hybrid approach is often more resilient than dependent on a single source.
The metrics for assessing the impact of this integration should include clear operational indicators: average triage time, rate of false positive in automated actions, number of incidents detected that change priority thanks to exposure enrichment, and time savings by analyst. These KPIs will justify the investment and adjust the orchestration rules. For those who want to explore technical integration, the Criminal IP documentation on the ThreatQ connector is a good starting point: IP and ThreatQ Criminal Integration, while the Securonix platform offers context on how flows are orchestrated and prioritized within your suite: Securonix.
Finally, the incorporation of exposure intelligence is a good reminder that modern defense must be both observational and contextual. Equipment that combine continuous perimeter scanning data, internal telemetry and orchestration capabilities will make more informed decisions and reduce the time between detection and mediation. Implementing integration with operational discipline, verification controls and clear metrics will transform technical potential into tangible security improvements.
Related
More news on the same subject.

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...