Set Up a Demo Virtual Machine Environment#
Deploy a demo environment to trial TheHive and Cortex with sample data using a Virtual Machine (VM). Download a ready-to-use image and open it in VMware or VirtualBox.
For a setup running Docker Compose directly on a Linux host, see Deploy a Demo Docker Environment.
Testing only
This VM is provided for testing purposes only. Don't use it in production.
Memory requirement
Allocate at least 6 GB of RAM to this virtual machine (VM) for stable performance. Assigning less may cause errors or degraded performance.
Platinum trial
The VM installation of TheHive with Cortex includes a 14-day Platinum trial license. After the trial ends, TheHive switches to read-only mode.
Step 1: Download the VM#
Download the ready-to-use VM from the StrangeBee website.
This VM is prepared and updated by StrangeBee and includes:
- TheHive: Security incident response and case management platform
- Cortex: Extendable analysis, enrichment, and response automation framework
Step 2: Start the VM#
- Start the VM and follow the on-screen instructions.
- In your browser, open the URL displayed by the VM.
- During import, set the Guest OS type information.

- After import, update the network settings of the VM before starting it.

- Add the required port forwarding rules (adjust as needed) and save.

- Start the VM and open the following URL in your browser: http://127.0.0.1:8888
- If needed, adjust the display settings and set the graphical controller to
VMSVGAbefore starting the VM.
Step 3: Log in to TheHive and Cortex#
The VM comes pre-loaded with sample data and configuration:
- A
Demoorganization andthehiveuser account in Cortex and TheHive - Free analyzers enabled
- Cortex integrated with TheHive
- Sample data including an alert, a case template, custom fields, MISP taxonomies, and MITRE ATT&CK data
Use the following credentials to log in:
| Application | User type | Username | Password |
|---|---|---|---|
| TheHive | Admin | admin@thehive.local |
secret |
| TheHive | Org Admin | thehive@thehive.local |
thehive1234 |
| Cortex | Admin | admin |
thehive1234 |
| Cortex | Org Admin | thehive |
thehive1234 |
Application stack#
The VM runs Ubuntu 24.04 and includes:
- TheHive, with Cassandra, Elasticsearch, and local file storage
- Cortex, with Elasticsearch
- TheHive4py
- Cortex4py
- Public Cortex analyzers and responders running in Docker
Configuration details#
Applications are launched with Docker Compose as containers, with volumes attached under /opt/thp.
Directory structure
.
├── cassandra
├── cortex
├── docker-compose.yml
├── elasticsearch
├── nginx
└── thehive
TheHive#
TheHive is configured to use Cassandra as its database and Elasticsearch to index data. Files are stored locally on disk.
TheHive directory structure
thehive
├── config
├── files
└── log
config: Configuration files.files: Files storage.log: Application logs.
Cortex#
Cortex uses Elasticsearch as its database, which also runs as a Docker Compose container. Dedicated volumes are configured for Elasticsearch: /opt/thp/elasticsearch/data to store data, and /opt/thp/elasticsearch/log for logs.
Cortex directory structure
cortex
├── config
├── jobs
└── log
config: Cortex configuration files.jobs: Shared volume for analyzers and responders jobs.log: Application logs.
Operations#
VM#
You can use the system account thehive/thehive1234 to operate the VM.
All applications run as Docker containers managed with Docker Compose. The docker-compose.yml file is located in /opt/thp.
Configure TheHive#
Maintenance window required
This procedure involves changing configuration files and restarting services. Schedule a maintenance window to prevent service disruption.
After modifying TheHive configuration, restart the service.
-
Configuration file:
/opt/thp/thehive/config/application.conf -
Restart command:
cd /opt/thp
docker compose restart thehive
The following documentation pages explain how to configure specific settings in application.conf:
- Update TheHive Service Configuration
- Configure Database and Index Authentication
- TheHive Database and Index Connection Settings
- Turn Off the Cortex Integration
- Turn Off the MISP Integration
Configure Cortex#
Maintenance window required
This procedure involves changing configuration files and restarting services. Schedule a maintenance window to prevent service disruption.
After modifying Cortex configuration, restart the service.
-
Configuration file:
/opt/thp/cortex/config/application.conf -
Restart command:
cd /opt/thp
docker compose restart cortex
The following documentation pages explain how to configure specific settings in application.conf:
- Database Configuration
- Authentication
- Proxy Settings
- Analyzers and Responders
- Advanced Configuration
Troubleshooting#
- TheHive service logs:
/opt/thp/thehive/log/application.log - Cortex service logs:
/opt/thp/cortex/log/application.log