# jmousqueton/opencti-docker architecture

> Architecture diagram of the GitHub repository jmousqueton/opencti-docker, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-10). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/jmousqueton/opencti-docker
- Repository: https://github.com/jmousqueton/opencti-docker

## Overview

##### Main components
- OpenCTI Core: The central service that manages cyber threat intelligence data.
- Connectors: Multiple services dedicated to fetching or pushing data (each represented by its own container). Consider listing key connectors like VirusTotal, AlienVault, AbuseIPDB, and others as sub-components.
- Configuration & Environment: Representation of the .env file used to set up variables, which feeds into Docker Compose.
- Docker Compose Infrastructure: Illustrate the orchestration layer that brings up all containers; include the docker-compose file.
- External Services/APIs: Indicate external endpoints that connectors interact with (e.g., VirusTotal API, etc.).

##### Relationships and interactions
- The docker-compose orchestration layer starts up each of the containers as specified.
- OpenCTI serves as the core data aggregator that receives data from the various connectors.
- A connection should be drawn from the OpenCTI core to the SIEM system to reflect the transfer of IOCs for SIEM interrogation, representing a “data push” or “integration endpoint.”

##### Architectural design patterns and principles
- Containerization/Microservices: Each service (core, each connector, SIEM) is deployed in its own isolated container.
- Decoupling: The connectors run independently and communicate over REST APIs or through messaging queues (if applicable) with OpenCTI.
- Integration Points: Clear separation of concerns where external APIs provide data and OpenCTI standardizes, aggregates, and then pushes data to the SIEM.

##### Specific technologies and frameworks
- Docker and Docker Compose are key for orchestration.
- The OpenCTI platform itself (and its repository of connectors) is central.
- Mention any referenced tools like minio-keygen if they're part of the security or storage configuration (e.g., for generating keys), though this is secondary.
- Since you're integrating with a SIEM, label that the SIEM might be a separate commercial or open-source solution (e.g., Splunk, Elastic SIEM, or another custom SIEM tool).

## Diagram (Mermaid)

```mermaid
flowchart TD
    A["Docker Compose Infrastructure"]:::docker
    B["Configuration & Environment"]:::env
    C["OpenCTI Core"]:::core
    D["Connectors"]:::connector
    E["Scalable Worker"]:::worker
    I["SIEM Integration"]:::siem

    %% External APIs for Connectors
    subgraph "External Threat Intelligence APIs"
        F["VirusTotal API"]:::external
        G["AlienVault API"]:::external
        H["AbuseIPDB API"]:::external
    end

    %% Grouping Connectors Pool
    subgraph "Connectors Pool"
        D1["VirusTotal Connector"]:::connector
        D2["AlienVault Connector"]:::connector
        D3["AbuseIPDB Connector"]:::connector
    end

    %% Relationships
    A -->|"spawns"| B
    A -->|"spawns"| C
    A -->|"spawns"| D
    A -->|"spawns"| E

    D -->|"contains"| D1
    D -->|"contains"| D2
    D -->|"contains"| D3

    D1 -->|"calls"| F
    D2 -->|"calls"| G
    D3 -->|"calls"| H

    C -->|"pushes_IOCs_to"| I

    %% Click Events
    click A "https://github.com/jmousqueton/opencti-docker/blob/main/docker-compose.yml"
    click C "https://github.com/jmousqueton/opencti-docker/blob/main/docker-compose.yml"
    click D "https://github.com/jmousqueton/opencti-docker/blob/main/docker-compose.yml"
    click B "https://github.com/jmousqueton/opencti-docker/blob/main/.env.sample"

    %% Styles
    classDef docker fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef core fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef connector fill:#fff3cd,stroke:#856404,stroke-width:2px;
    classDef worker fill:#f8d7da,stroke:#721c24,stroke-width:2px;
    classDef external fill:#e2e3e5,stroke:#6c757d,stroke-width:2px;
    classDef siem fill:#ffeeba,stroke:#856404,stroke-width:2px;
```
