OpenCTI Integration
The Threat Landscape OpenCTI connector imports STIX 2.1 bundles into your OpenCTI knowledge graph. This guide uses a local Compose stack with OpenCTI, its dependencies, a worker and the Threat Landscape connector.
Official connector reference: OpenCTI connectors → Threat Landscape
What you need
- OpenCTI Platform 6.8.12 or newer.
- Docker Engine and the Compose plugin, with about 16 GB of RAM.
- A Threat Landscape API key on a plan that includes the API and OpenCTI connector: Team or Enterprise.
Free and Professional accounts are web-only. The OpenCTI connector will be rejected with a 401 if the key belongs to either plan.
Prepare OpenCTI
git clone https://github.com/OpenCTI-Platform/opencti.git
cd opencti
uuidgen # OPENCTI_ADMIN_TOKEN
uuidgen # CONNECTOR_THREATLANDSCAPE_ID
openssl rand -base64 32 # OPENCTI_ENCRYPTION_KEYCreate .env at the repository root with the connector keys:
OPENCTI_ADMIN_TOKEN=paste-uuid
OPENCTI_ENCRYPTION_KEY=paste-base64-key
CONNECTOR_THREATLANDSCAPE_ID=paste-uuid
THREATLANDSCAPE_API_KEY=paste-team-or-enterprise-keyAdd the Threat Landscape connector
Add this service to your Compose file, alongside the OpenCTI platform and worker:
connector-threatlandscape:
image: opencti/connector-threatlandscape:latest
restart: unless-stopped
depends_on:
opencti:
condition: service_healthy
environment:
- OPENCTI_URL=http://opencti:8080
- OPENCTI_TOKEN=${OPENCTI_ADMIN_TOKEN}
- CONNECTOR_ID=${CONNECTOR_THREATLANDSCAPE_ID}
- CONNECTOR_NAME=Threat Landscape
- CONNECTOR_SCOPE=indicator,report,threat-actor,malware,campaign,intrusion-set,attack-pattern,vulnerability,identity,location
- CONNECTOR_LOG_LEVEL=info
- CONNECTOR_DURATION_PERIOD=PT1H
- THREATLANDSCAPE_API_BASE_URL=https://api.threatlandscape.io/rest/v1
- THREATLANDSCAPE_API_KEY=${THREATLANDSCAPE_API_KEY}
- THREATLANDSCAPE_IMPORT_SINCE=P30D
- THREATLANDSCAPE_FEED=intelligence
- THREATLANDSCAPE_PAGE_SIZE=100THREATLANDSCAPE_FEED=intelligence selects the combined OSINT and darknet feed.P30D limits the first import to the last 30 days. Later runs continue from the last sequence ID once an hour.
Connector parameters
| Variable | Default | Notes |
|---|---|---|
CONNECTOR_ID | — | Required. Must be a unique UUIDv4. |
CONNECTOR_DURATION_PERIOD | PT1H | ISO 8601 interval between runs. |
THREATLANDSCAPE_API_KEY | — | Required Team or Enterprise API key. |
THREATLANDSCAPE_IMPORT_SINCE | P30D | Lookback window for the first run. |
THREATLANDSCAPE_FEED | — | intelligence, intelligence-osint, intelligence-darknet or ioc. |
THREATLANDSCAPE_PAGE_SIZE | 100 | Bundles per API request. Range 1–1000. |
How the connector syncs
- First run: imports bundles with
stix_published_atinside the lookback window. - Later runs: imports only bundles with a higher
seq_idthan the last successful cursor. - State: the highest
seq_idis saved after a successful run. A failed run is retried from the last good cursor. - Deduplication: OpenCTI deduplicates incoming objects by deterministic ID.
For local (non-Docker) installs, use the official config.yml.sample and thethreatlandscape block in the connector README.
Start and verify
docker compose up -d
docker compose ps
docker compose logs -f opencti
docker compose logs -f connector-threatlandscapeGive Elasticsearch time to become healthy on the first boot. Then openhttp://localhost:8080, sign in, and check Data → Ingestion → Connectors. The Threat Landscape connector should be registered with a last-run time.
Threat Landscape bundles arrive as reports linked to the objects in CONNECTOR_SCOPE.
Troubleshooting
- 401: missing key, or the account is Free or Professional.
- No reports: check the connector logs and the feed value.
- Connector not starting: make sure the connector ID is a valid UUIDv4.
- Elasticsearch unhealthy: increase
vm.max_map_counton Linux.