Requirements
Platform versions, accounts, and network access needed before installing the Whisper connector for OpenCTI.
Requirements Documentation
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; the current release is verified against 7.260715.0 (July 2026). |
| 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-Keyheader on every query. If you don't have one, create a free account at console.whisper.security. - Nothing else. The connector image is public on Docker Hub (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 — pull the image and add the service
- Configuration — environment variable reference