TheHive is a scalable 3-in-1 open source and free solution designed to make life easier for SOCs, CSIRTs, CERTs and any information security practitioner dealing with security incidents that need to be investigated and acted upon swiftly.
Collaboration is at the heart of TheHive. Multiple analysts can work on the same case simultaneously. For example, an analyst may deal with malware analysis while another may work on tracking C2 beaconing activity on proxy logs as soon as IOCs have been added by their coworker. Thanks to the Flow, a Twitter-like stream, everyone can keep an eye on what's happening on the platform, in real time.
Within TheHive, every investigation corresponds to a case. Cases can be created from scratch and tasks added on the go. They can also be created using templates with corresponding metrics to drive the team's activity, identify the type of investigations that take significant time and seek to automate tedious tasks.
Tasks can be assigned to a given analyst. Team members can also take charge of a task without waiting for someone to assign it to them.
Each task may contain multiple work logs that contributing analysts can use to describe what they are up to, what was the outcome, attach pieces of evidence or noteworthy files, etc. Logs can be written using a rich text editor or Markdown.
You can add one or hundreds if not thousands of observables to each case you create. You can also create a case out of a MISP event. TheHive can be very easily linked to one or several MISP instances and MISP events can be previewed to decide whether they warrant an investigation or not. If an investigation is in order, the analyst can then import the event into a case using a customizable template.
TheHive has the ability to automatically identify observables that have been already seen in previous cases. Observables can also be associated with a TLP and the source which provided or generated them using tags. The analyst can also easily mark observables as IOCs and isolate those using a search query then export them for searching in a SIEM or other data stores.
Starting from Buckfast (TheHive version 2.10), analysts can analyze tens or hundreds of observables in a few clicks by leveraging the analyzers of one or several Cortex instances depending on your OPSEC needs: DomainTools, VirusTotal, PassiveTotal, geolocation, threat feed lookups and so on. Before Buckfast, the analysis engine which gave birth to Cortex was embedded in TheHive's back-end code.
Security analysts with a knack for scripting can easily add their own analyzers to Cortex in order to automate actions that must be performed on observables or IOCs. They can also decide how analyzers behave according to the TLP. For example, a file added as observable can be submitted to VirusTotal if the associated TLP is WHITE or GREEN. If it's AMBER, its hash is computed and submitted to VT but not the file. If it's RED, no VT lookup is done.
How to use this image
Easiest way to start TheHive:
docker run certbdf/thehive
Exposing the port
TheHive listens on 9000/tcp. In order to make the port accessible add
docker run --publish 8080:9000 certbdf/thehive
Specify persistent data location
TheHive stores its data in
/data (inside the container). You can add
--volume parameter :
docker run --volume /path/to/persistent/data:/data certbdf/thehive
If you wish to adapt the default configuration, add a volume parameter to overwrite the configuration file:
docker run --volume /path/to/your/application.conf:/opt/docker/conf/application.conf certbdf/thehive