Threat IntelligenceCommunity

OpenCTI integrations pass 400, breaking down intel silos

9 min read
OpenCTI integrations pass 400, breaking down intel silos, by Deborah Galea, with the OpenCTI logo and threat intelligence dashboards.

Threat intelligence only matters if you act on it. An indicator that never reaches the SIEM can't trigger a detection. A vulnerability insight that isn't shared with the patching team can't reduce risk. And adversary research stuck in a siloed platform doesn't help a SOC analyst working the next incident.

That's why we keep expanding Filigran's OpenCTI ecosystem, which now includes more than 400 integrations. These OpenCTI integrations cover commercial and open-source threat feeds, enrichment services, and the security tools teams already run every day, including SIEMs, EDRs, SOARs, firewalls, and DNS and web security.

Built by Filigran and the OpenCTI community

The integrations come from Filigran's development team working alongside the OpenCTI open-source community, which now has more than 7,000 members in our Slack community. Community members have contributed 137 integrations so far. Practitioners, researchers, vendors, and partners have all built connectors to streamline their own workflows, then shared them with everyone else.

We want to thank our OpenCTI community for everything you contribute to this ecosystem. Every connector you share makes the platform stronger for defenders everywhere. OpenCTI is better because of you.

Julien RichardCTO and co-founder, Filigran

Being open is what makes OpenCTI work for us. It's easy to integrate with, so we've built our own connectors alongside the public ones, and intelligence from every provider ends up in one place next to our own. When a connector doesn't fit, we don't have to wait. I've contributed to eight of them, and the Filigran team has been quick to review and merge.

Brett FitzpatrickLead security engineer, Klaviyo

This shared approach is why the OpenCTI integrations library has grown so fast, and why it closely reflects how security teams actually work. On average, our OpenCTI customers use 29 integrations.

Every OpenCTI integration is listed in the OpenCTI integrations library.

Why security teams look for integrations first

Filigran’s 2026 State of Threat Management report found that integration with existing security tools and platforms is the top factor (42%) when evaluating exposure management tools.

Integration with existing security tools is the top factor when evaluating exposure management tools.

The finding makes sense. Security teams already run crowded stacks, and they don't want another tool that adds a console, a manual export, or a swivel-chair workflow. They want a platform that fits into what they already have and makes each of those tools work better.

How OpenCTI integrations break down intelligence silos

In threat intelligence, valuable data often stays siloed. It gets collected, analyzed, and stored, but never reaches the teams on the front lines who need it.

OpenCTI's integrations fix that in both directions:

  • Inbound: OpenCTI pulls in intelligence from hundreds of feeds and enrichment sources, normalizes it to STIX 2.1, and correlates it into one knowledge graph.OpenCTI pulls in intelligence from hundreds of feeds and enrichment sources, along with data from your own security tools, normalizes it to STIX 2.1, and correlates it into one knowledge graph.
  • Outbound: OpenCTI sends curated, contextualized intelligence to SIEMs, EDRs, SOARs, firewalls, and other controls, so it shows up in existing workflows and drives detection, blocking, and response.

The result is proactive defense: intelligence is pushed to where it strengthens security posture and helps prevent future attacks, instead of being looked up after the fact.

Threat intelligence delivers the greatest value when it reaches the teams and systems responsible for acting on it, the world’s largest private provider of threat intelligence. OpenCTI’s expanding integration ecosystem helps organizations break down information silos and bring critical threat context into their existing security workflows. Our partnership with Filigran reflects a shared commitment to making intelligence more accessible, actionable, and effective in helping organizations stay ahead of emerging threats.

David HolmesVice president of partnerships, Flashpoint

An open architecture: choose the threat feeds that fit your mission

No two organizations face the same threat landscape. A financial institution worries about fraud and account takeover. A government agency may focus on state-sponsored campaigns and foreign information manipulation. A consumer brand cares about impersonation and digital risk.

The integrations give access to a wide range of intelligence, including adversary and campaign tracking, vulnerabilities, malware, foreign information manipulation and interference (FIMI), brand and digital risk, financial fraud, AI risk, and enrichment sources. Because OpenCTI has an open architecture, each organization can choose and combine the sources most relevant to its mission.

You decide which commercial providers to bring in, which open-source feeds to add, and how it all flows into your stack.

Threat intelligence feeds for every use case

Here are some common intelligence use cases and the integrations available for each.

Adversary and campaign insights (145 integrations)

What it is: Intelligence on threat actors, their campaigns, and the tactics, techniques, and procedures (TTPs) they use, mapped to frameworks such as MITRE ATT&CK.

Why it matters: Knowing who is likely to target you, and how, lets you prioritize defenses against real adversary behavior instead of hypothetical threats. It's the base for threat-informed defense, detection engineering, and executive risk briefings.

Integrations include: MITRE ATT&CK, MITRE ATLAS, CISA, AlienVault, ThreatFox, Google Threat Intelligence, Recorded Future, and Wiz.

Brand, digital risk, and underground exposure (23 integrations)

What it is: Monitoring of the open, deep, and dark web for impersonation, leaked credentials, exposed data, fraudulent domains, and chatter about your organization.

Why it matters: Many attacks start outside your perimeter, with a lookalike domain, a credential dump, or a phishing kit built around your brand. Seeing that exposure early lets you get takedowns going, reset compromised accounts, and warn customers before harm is done.

Integrations include: CrowdStrike Falcon Recon, Doppel, Google Digital Threat Monitoring, and ZeroFox.

Brand, digital risk, and underground exposure in the OpenCTI integrations library.

Detection and response enablement (128 integrations)

What it is: Turning intelligence into action by feeding indicators, observables, and context into the detection and response tools your SOC uses, and enriching alerts with intelligence in return.

Why it matters: This is where intelligence turns into protection. When curated indicators and context flow automatically into detection pipelines, analysts triage faster, false positives drop, and known-bad activity gets caught early.

Integrations include: CrowdStrike, Datadog, Google SecOps, and Splunk SOAR.

Infrastructure and attack surface visibility (92 integrations)

What it is: Context on IPs, domains, URLs, certificates, and internet-facing infrastructure, covering both adversary infrastructure and your own exposed assets.

Why it matters: Knowing whether an IP is a benign scanner or active command-and-control, or whether a domain is newly registered and malicious, changes how you respond. Infrastructure intelligence helps analysts separate signal from noise and understand the attack surface adversaries see.

Integrations include: GreyNoise, Google Safe Browsing, Google DNS, ANY.RUN, and Criminal IP.

Vulnerability and exploit awareness (52 integrations)

What it is: Data on known vulnerabilities, exploitation likelihood, and in-the-wild exploit activity, tied to the threat actors and campaigns using them.

Why it matters: Tens of thousands of CVEs are published every year, and no team can patch them all at once. Combining vulnerability data with exploit prediction and threat context helps teams focus on what attackers are actually exploiting, which is central to effective exposure management.

Integrations include: CISA, NIST NVD, FIRST EPSS, Google Threat Intelligence, and VulnCheck.

OpenCTI integrations for SIEM, EDR, and SOAR

Besides intelligence sources, OpenCTI connects directly to the security tools in your environment, so intelligence shows up where it's needed instead of sitting in a repository. Here are the most commonly used categories.

Malware analysis and sandbox (31 integrations)

What it is: Automated submission and analysis of suspicious files and URLs, with results enriched back into OpenCTI.

Why it matters: Sandbox verdicts and behavioral reports add depth to every investigation, linking samples to malware families, infrastructure, and threat actors without manual copy-and-paste.

Integrations include: VirusTotal, ANY.RUN, FortiSandbox, ScanMalware, VMRay, and PolySwarm.

The malware analysis and sandbox category in the OpenCTI integrations library.

SIEM and security analytics (24 integrations)

What it is: Two-way connections between OpenCTI and the platforms where security telemetry is collected, correlated, and searched.

Why it matters: The SIEM is the SOC's center of operations. Streaming curated intelligence into it means detections are informed by the latest threat knowledge, and analysts see context in the tools they already work in.

Integrations include: FortiSIEM, Datadog, Google SecOps, CrowdStrike, Splunk, and Microsoft Sentinel.

Endpoint detection and response (19 integrations)

What it is: Pushing indicators and intelligence to endpoint security platforms for detection, hunting, and blocking.

Why it matters: Endpoints are where many attacks play out. Arming EDR tools with current intelligence lets teams detect and stop known threats at the device level, often before they spread.

Integrations include: CrowdStrike, Tanium, Palo Alto Networks Cortex XDR, Microsoft Defender, and SentinelOne.

Learn more about the OpenCTI and CrowdStrike integration in this on-demand webinar: "Threat-informed defense: from intelligence to action with CrowdStrike and OpenCTI."

Network security (10 integrations)

What it is: Sending threat intelligence to firewalls, DNS security, secure web gateways, and edge platforms, so malicious IPs, domains, and URLs are blocked at the network layer.

Why it matters: The network is often the first and best place to stop an attack. When network controls get current, curated intelligence automatically, known command-and-control servers, phishing domains, and malicious infrastructure are blocked before they reach users or endpoints. That cuts exposure across the whole organization without anyone pushing updates by hand.

Integrations include: Akamai, Cloudflare, Infoblox Threat Defense, Zscaler, and Vectra AI.

SOAR and security automation (9 integrations)

What it is: Bringing threat intelligence into orchestration platforms and automated playbooks.

Why it matters: Automation only works as well as the data driving it. Integrating OpenCTI with SOAR platforms lets playbooks enrich, triage, and respond based on trusted, contextualized intelligence, so response is faster and more consistent at scale.

Integrations include: Google SecOps, Splunk SOAR, Fortinet FortiSOAR, Palo Alto Networks Cortex XSOAR, and Swimlane.

The OpenCTI integration for Splunk SOAR in the OpenCTI integrations library.

One-click deployment: from connector to running in minutes

OpenCTI integrations are easy to deploy, and with OpenCTI Enterprise Edition, many deploy with one click. Teams can go from finding a connector to running it in minutes instead of days.

How to build your own OpenCTI connector

What if you don't find the connector you need? OpenCTI connectors are open source and written in Python with the official pycti library, so any team can connect OpenCTI to an in-house tool, a niche feed, or a proprietary data source.

To get started, decide on the connector type that fits your use case: external import (bring in data from a feed), internal enrichment (add context to existing entities), stream (send intelligence to a security tool), or import/export file.

Next, clone the OpenCTI connectors repository on GitHub and start from the template for your connector type. You don't need to write it all by hand. With vibe coding, you can describe what you want to an AI coding assistant, for example: "Build an OpenCTI external import connector that pulls indicators from this API and maps them to STIX 2.1." Point it at the repository's AGENTS.md file, which contains instructions written for AI assistants, along with the template and existing connectors, and it can generate a working first draft in minutes. Then check the STIX 2.1 mapping, set your OpenCTI URL and API token, and test locally or with Docker. The connector development documentation covers each step in detail. It's also a useful reference to give your AI assistant.

When your connector is ready, submit a pull request to share it with the community. Filigran engineers review each submission, and approved connectors go into the library. Yours could join the 137 community-contributed integrations already helping teams worldwide.

The OpenCTI connectors repo is run the way you'd hope an open-source project would be. The maintainers take quality seriously and are extremely quick to review and respond with valuable feedback. That made building the VulnCheck connector a really good experience.

EJ ReillySoftware engineer, VulnCheck

What's next for OpenCTI integrations

Passing 400 integrations is a milestone, but we're not stopping here. Each new connector, whether built by Filigran or contributed by the community, helps make sure intelligence never stays in a silo. As threats change, the ecosystem will keep adding new feeds, new tools, and new ways to turn knowledge into action.

Find the OpenCTI integration you need

Browse every integration in the OpenCTI integrations library. Don't see the one you need? Contact us or ask about it in our Slack community. We'd like to hear what your team needs, and the community may already be building it. We're also happy to support you if you're building a connector yourself.

Read more

Explore related topics and insights