While many are enjoying the summer holidays, the busy bees of TheHive Project have been working hard lately to develop new Cortex analyzers and review few of those submitted by our growing and thriving user community, bringing the grand total to 27. Yes, you read that right. Cortex can leverage 27 analyzers to help you analyze observables very simply in many different ways.
The latest update to the Cortex-analyzers repository contains 3 new analyzers: Yeti, Cuckoo Sandbox and WOT, described below. And your first step to benefit from them should consist of refreshing your master working copy on your Cortex instance:
$ cd where/your/analyzers/are $ git pull master
Yeti
YETI is a FOSS platform meant to organize observables, indicators of compromise, TTPs, and knowledge on threats in a single, unified repository. It is mainly developed by fellow APT busters Thomas Chopitea and Gael Muller (who said France doesn’t produce good software?).
The new Cortex analyzer for this platform lets you make API calls to YETI and retrieve all available information pertaining to a domain, a fully qualified domain name, an IP address, a URL or a hash.
To be able to use the analyzer edit the Cortex configuration file (/etc/cortex/application.conf
) and add the following lines:
Yeti { # URL of the Yeti server: example: http://120.0.0.1:5000 url = "" }
When called from TheHive, the following output is produced:

CuckooSandox
The Cuckoo Sandbox analyzer has been submitted by Andrea Garavaglia (Thanks!) and you can use it to analyze files and URLs with Cuckoo Sandbox.
By default, we chose to limit analysis to TLP:WHITE and TLP:GREEN observables for OPSEC reasons, in case your Cuckoo server provides Internet access to potentially harmful files. If you want to use it with TLP:AMBER or TLP:RED observables, edit CuckooSanbox_File_analysis.json
or CuckooSanbox_URL_analysis.json
and change the max_tlp
parameter to 2 or 3.
To use the analyzer, edit the Cortex configuration file and add the following lines:
CuckooSandbox { url = “http://mycuckoosandbox” }
When called from TheHive, the following output is produced:

WOT
The WOT analyzer was also submitted by Andrea Garavaglia (kudos!). Use it to check reputation of a given domain on the Web of Trust service. It takes domains and FQDNs as input.
An API key is needed to use this service, and has to be added in the Cortex configuration file:
WOT { # API key of the Web of Trust account key=“” }
When called from TheHive, the following output is produced:

Support
Something does not work as expected? No worries, please join our user forum, contact us on Gitter, or send us an email at support@thehive-project.org. We are here to help.
One thought on “WOT? Did You See a Yeti Hugging a Cuckoo?”
Comments are closed.