TAXII 2.1Native server
3Live collections
50Indicators per push
0Custom parsers
The short answer

OpenCTI and OneFirewall are complementary. OpenCTI is a threat intelligence platform: it stores, links and analyses intelligence from many sources. It doesn't enforce. OneFirewall is both a source (scored Alliance indicators over TAXII 2.1) and an enforcement layer (block rules on your existing firewalls, WAFs and cloud edges).

How OpenCTI works

A STIX 2.1 knowledge graph for CTI teams

OpenCTI, an open-source platform from Filigran, stores intelligence natively as STIX 2.1 objects: indicators, observables, threat actors, intrusion sets, malware and the relationships between them. Connectors import from feeds and other platforms (including a TAXII 2 import connector), enrich observables and export to downstream tools. Analysts use it to build context, track campaigns and produce reports.

OpenCTI tells you what is known. Getting an indicator onto a firewall still requires another connector, a SOAR workflow or a manual change, plus decisions about confidence and expiry.

  • Rich modelling of actors, campaigns and relationships
  • Many import, enrichment and export connectors
  • Quality depends on the feeds you connect
  • No enforcement of its own
The integration

TAXII 2.1 in both directions

OneFirewall runs a standard TAXII 2.1 server alongside its REST API. OpenCTI connects to it like any other TAXII source.

STEP 1

Pull Alliance indicators

Configure OpenCTI's TAXII2 import connector for TAXII 2.1 with your OneFirewall JWT or Basic Auth credentials. It discovers the IP, domain and URL collections and pulls new indicators incrementally with added_after.

STEP 2

Detect changes cheaply

The manifest endpoint returns change metadata without full objects, so frequent polling stays light.

STEP 3

Push your own indicators

Send curated indicators from OpenCTI back with POST /collections/{id}/objects/, up to 50 STIX 2.1 Indicators per request, via a small stream connector or script.

STEP 4

Enforce automatically

The WCF Agent turns scored indicators into blocks on your firewalls, WAFs and cloud edges, so what your CTI team decides actually reaches the perimeter.

What the configuration looks like

# OneFirewall TAXII 2.1 server
GET  /taxii2/                                   discovery (no auth)
GET  /taxii2/onefirewall/collections/           IP, domain, URL collections
GET  /taxii2/onefirewall/collections/{id}/objects/?added_after=<ts>&limit=<n>
GET  /taxii2/onefirewall/collections/{id}/manifest/   change detection
POST /taxii2/onefirewall/collections/{id}/objects/    push up to 50 STIX 2.1 Indicators

# OpenCTI: TAXII2 external-import connector -> Version 2.1, JWT or Basic Auth

Pushed indicators feed the Alliance scoring like any other contribution: they count toward an IP's Crime Score weighted by your trust level, and need corroboration before they block for other members.

Side by side

OpenCTI and OneFirewall, capability by capability

CapabilityOpenCTIOneFirewall
Primary jobStore, link and analyse threat intelligenceProduce scored indicators and enforce them on your controls
Data modelFull STIX 2.1 knowledge graphSTIX 2.1 Indicators over TAXII 2.1, plus REST and CEF
Intelligence sourceThe feeds and connectors you configureAttacks observed by 290+ organisations, partners and a honeynet
ConfidenceSet per source or by analystsCrime Score 0 to 1000 with multi-member confirmation and decay
EnforcementNone built in; needs connectors or SOARNative block rules on 166+ integrations
Sharing backExport connectorsTAXII push, counted in Alliance scoring
The added value

What OneFirewall adds to OpenCTI

A high-signal feed for your graph

Alliance indicators arrive already scored and corroborated, so they add context rather than noise.

The missing enforcement step

The indicators your analysts trust end up on firewalls and WAFs automatically, without building a custom export connector for every vendor.

Your intelligence, amplified

What you push back helps protect every other member, and earns OFA Coins under the contribution programme.

Where OpenCTI is still the right tool
  • Modelling threat actors, campaigns and their relationships
  • Analyst workflows, reporting and knowledge management
  • Combining many commercial and open-source feeds in one place
  • Strategic and operational intelligence beyond IoCs

Endpoint details are on the STIX and TAXII page.

FAQ

OneFirewall and OpenCTI: FAQ

How does OpenCTI connect to OneFirewall?

Through OpenCTI's TAXII 2 import connector, pointed at the OneFirewall TAXII 2.1 server with JWT or Basic Auth credentials.

Which collections are available?

Three live collections: IP, domain and URL indicators, all as STIX 2.1.

Can OpenCTI send indicators to OneFirewall?

Yes. The TAXII server supports push: up to 50 STIX 2.1 Indicators per POST request.

Does OneFirewall replace OpenCTI?

No. OpenCTI remains your intelligence platform. OneFirewall feeds it and enforces the result on your existing controls.

See what OpenCTI lets through today.

A free Proof of Value runs against your own traffic. Nothing leaves your perimeter.

Start a Free PoV