# Requirements

> What the Whisper OpenCTI connector needs: OpenCTI, Docker, a Whisper API key and HTTPS access to graph.whisper.security, plus the verified version.

*Source: https://www.whisper.security/docs/integrations/opencti/requirements*
*Published: 2026-07-19*
*Last updated: 2026-09-25*

---
| | |
|---|---|
| **This page describes** | Whisper connector for OpenCTI **v1.0.1** — `ghcr.io/whisper-sec/whisper-opencti`, mirrored on Docker Hub as `opencti/connector-whisper` |
| **Published** | Connector image tags `7.260715.0` through `7.260807.0`, plus `rolling` and `latest`. Newest push 2026-08-09 |
| **Verified on** | OpenCTI platform **7.260715.0** — the release the connector's `pycti` client is pinned to. Where the repository's files disagree about a platform version, the pin is the one that decides what the container actually talks to |
| **Declared support** | `>= 7.260701.0`, from the connector manifest |
| **Not tested** | OpenCTI platform **7.260807.0**, the newest published release (2026-08-07). A connector image carries that tag, but nothing on this page records a verified run of the pair |
| **Conformance checks run at build** | Format, unit tests, image build, unused-dependency scan and the Filigran connector-verified linter, on every push |
| **Last checked** | 2026-08-09 |

What you need before installing the Whisper connector for OpenCTI.

## OpenCTI platform

| Component | Version |
| --- | --- |
| OpenCTI platform | 7.260701.0 or later. Connector images are tagged per platform version — pull the tag that matches yours. |
| Docker | Any current engine. The connector ships as a container image, and Docker is the supported way to run it. |

OpenCTI releases the platform and its `pycti` client library in lockstep on the same version string, and connector images are tagged to match. Pull the image tag that matches your platform version. A mismatch doesn't fail silently: the connector refuses to register and the container logs say why.

## Whisper account

- A Whisper API key. The connector sends it in the `X-API-Key` header on every query. If you don't have one, sign in at [console.whisper.security/sign-up](https://console.whisper.security/sign-up) and generate one.
- Nothing else. The connector image is public on Docker Hub ([opencti/connector-whisper](https://hub.docker.com/r/opencti/connector-whisper)) — no registry account or token needed.

## OpenCTI account for the connector

Create a dedicated OpenCTI user for the connector and use its token as `OPENCTI_TOKEN`. OpenCTI's own guidance applies here: put the user in the Connectors group with permission to create observables and relationships, and don't reuse the admin token.

## Network access

The connector container needs three routes:

| From | To | Purpose |
| --- | --- | --- |
| Connector | OpenCTI platform (port 8080 by default) | Registration and bundle ingestion |
| Connector | RabbitMQ (your platform's internal network) | Receiving enrichment jobs |
| Connector | `graph.whisper.security` (HTTPS, outbound) | WhisperGraph queries |

All Whisper API traffic is HTTPS with certificate verification. There is no plaintext fallback.

## Next steps

- [Installation](/docs/integrations/opencti/installation) — pull the image and add the service
- [Configuration](/docs/integrations/opencti/configuration) — environment variable reference