Summary
- Filigran reports that OpenCTI now offers more than 400 integrations, with over 100 added since December.
- The catalogue connects intelligence feeds and enrichment sources to SIEM, SOAR, EDR and vulnerability management workflows.
- Community contributions are growing, but connector review, source quality and integration maintenance remain operational considerations.
Filigran says its OpenCTI threat intelligence platform now offers more than 400 integrations, extending the ways organisations can move indicators, incident context and vulnerability information between intelligence sources and security operations systems. In its 17 November announcement, the company said it had added more than 100 integrations since December 2025. It is a catalogue expansion rather than a claim that every integration is deployed or that intelligence flowing through each connection has been independently validated.
OpenCTI is an open-source platform used to structure and share information about threats, adversaries, campaigns and related technical artefacts. Its integrations can ingest information from intelligence feeds, enrich records with external findings or transfer selected data to other systems. This can reduce the need for analysts to switch applications during an investigation. It can also introduce a dependency on how accurately a connector translates fields, classifications and confidence values between services.
Filigran identifies SIEM, endpoint detection, security orchestration and vulnerability response systems among its principal destinations. The catalogue includes connections involving Google SecOps SOAR, ServiceNow Vulnerability Response and Palo Alto Cortex XDR, alongside feeds such as Recorded Future and community-maintained detection rules from SigmaHQ. These products perform different functions, so the integration label does not necessarily describe the same data flow or operational outcome in every case.
For an intelligence-led investigation, a connector that brings reliable context into an alerting platform can assist with triage. Analysts may be able to examine whether an observed address, file or behaviour corresponds to a known threat report without separately performing manual lookups. Conversely, automated propagation of a low-confidence indicator can create false alerts or reinforce an incorrect attribution across several connected systems. The quality of the underlying source and the transformations applied by the connector remain central to the usefulness of the result.
The company says the OpenCTI community now contributes an average of nine integrations per month, more than twice its previous twelve-month rate. It also reports that a typical OpenCTI deployment runs 29 integrations. Those are supplier-reported figures, and the release does not provide an independent assessment of connector reliability, customer outcomes or the proportion of listed integrations that are actively maintained. Catalogue size is therefore a measure of potential interoperability rather than proof of stronger defences by itself.
Filigran has made the open-source contribution process part of its expansion strategy. Developers submit connector changes through the project’s public repository, where the company says its engineers review proposed code and implementation before approval. A review process helps establish responsibility for incorporating changes, but it does not remove the need to assess dependencies, permissions and ongoing maintenance after a connector is installed in a production environment.
That maintenance burden can be significant. External products regularly alter API authentication, schemas, usage limits and supported versions, while threat intelligence providers may change the licensing or handling restrictions on their data. A connector that works at installation can later stop updating, repeat stale information or deliver incomplete context without generating an obvious outage. Security operations teams need to understand whether a particular integration only imports data, exports it to a response platform or synchronises information in both directions.
An indicator sent from intelligence software into a response tool can influence enforcement only if the receiving product and its configured workflows support that action. Filigran says OpenCTI can deliver indicators to response tools but does not itself change those tools’ configurations through the design of ordinary intelligence delivery. Actual enforcement remains dependent on the receiving product and how the customer has configured it. This separation can preserve human or existing platform approval steps, although those approvals must be verified rather than assumed from the existence of an integration.
Integration breadth also affects vendor choice and procurement. Organisations with multiple cloud services, monitoring products and threat feeds may prioritise systems that fit their current architecture over platforms requiring wholesale replacement. Open-source connectors can make specialised regional feeds available outside a proprietary product roadmap. At the same time, a community-developed component may require greater internal scrutiny if its maintenance history or support arrangements differ from those of a commercially supported integration.
The OpenCTI catalogue is available to Community and Enterprise Edition users, while Filigran says Enterprise Edition adds one-click connector deployment. Easier installation can shorten initial configuration work, but it does not settle the separate questions of security review, source relevance and ongoing data quality. Filigran has not published independently verified outcomes linking its expanded integration catalogue to faster detection or fewer successful incidents.





