Integrating The Hive and Cortex with ONYPHE - new analyzers


Written on 2024/02/09

TheHive Project has been making life easier for security analysts in SOC, CSIRT and CERT teams since around 2017. It is a Security Incident Response Platform (SIRP) which cleverly integrates with other popular security tools such as MISP, VirusTotal and many others. There’s been an integration between TheHive and ONYPHE since the very early days in 2017, with several updates between then and 2020. However, as we’ve added new APIs and data categories to ONYPHE since then we decided it was high-time to contribute our own update to the analyzer.

Teams using both ONYPHE and TheHive can now benefit from the following features :

Let’s take a look at those different analyzers and use cases :


The ONYPHE Search API is the primary way that ONYPHE users get data out of the platform, either using the web interface or the ONYPHE CLI tool. You specify a category and filter and usually within about half a second you get the data that matches.

The ONYPHE_Search analyzer will fetch the first 100 results from your chosen category, that matches the observerable within TheHive. In the default configuration, it executes the following OQL queries (ONYPHE Query Language) for the observables, and

~$ onyphe -search 'category:datascan -since:1M'

~$ onyphe -search 'category:datascan -since:1M'

~$ onyphe -search 'category:datascan ip: -since:1M'

The selected category and the time filter are configured in the Cortex Analyzer settings. ONYPHE_Search analyzer configuration in Cortex

The analyzer does some work to adapt the results according to the chosen category. If you query datascan or onionscan, then the short summary report will show the number of open ports/services identified. If you query Vulnscan it will return the number of CVEs and if you query Riskscan if will show the number of risks (deduplicated for ip:ports).

ONYPHE Search short report

Clicking on the short report or on the Analyzer results link will take you to the full ONYPHE_Search report. Although the IPs are obscured in our screenshot, what you get is essentially the same as on the ONYPHE web interface.

ONYPHE Search long report

The report header displays the category used for the query, the observable, and the number of results returned by the query.

For each result, the analyzer displays :

The general layout should be famliar to ONYPHE users.


Based on the Search analyzer, the Vulnscan analyzer allows ONYPHE users benefiting from Eagle View or Griffin View licences to fetch critical CVE data for the observable you’re analyzing. This would also be possible by configuring the Search analyzer with the vulnscan category however one extra configuration option is provided on this analyzer.

In it’s default configuration, Vulnscan will return both positive and negative results for vulnerability checks. This allows users to verify that the relevant assets have indeed be scanned. Setting only_vulnerable to True will tell the analyez to only return positive CVE results.

ONYPHE Vulnscan config

Combined with the auto_import option, this allows you to query ONYPHE for a domain, and observables will automatically be created for IPs with known exploited CVEs, with tags added for the CVE reference and technology.

ONYPHE Vulnscan results

The full results of each asset are displayed in the same tabbed format as for the Search analyzer.


Within CSIRT and SOC teams, it is now common to use SIRP platforms like TheHive to manage not only incidents and investigations, but also proactive preventative actions, for example as part of an Attack Surface Management process.

In this use-case, observables are not threats but rather the organisation’s assets that need defending. The ONYPHE_ASM analyzer has been designed for this use case.

It uses the Riskscan category available to ONYPHE Griffin View subscribers.

The short report currently shows the sum of the number of risks of all types, on a deduplicated list of ips and ports. (We want to improve this in a future version!)

The key difference for the ASM analyzer is in the way the full long report renders the json data.

ONYPHE ASM results

Under the general title, instead of showing results asset by asset, a chronological list of risks is displayed, with the most recent first.

Clicking on the risk title will open-up a summary of the key details required to understand the risk. As a typical large organisation would want to query the ASM analyzer for hundreds if not thousands of assets, an optimization is provided in the analyzer configuration.

ONYPHE ASM configuration

With this analyzer only the essential fields are returned in the query, speeding up the analyzer execution and saving valuable space in your TheHive database. If you need an additional field in the raw data report you can modify the list of fields in the analyezr settings (but modify with care :).

Observable Extraction

For all of the new analyzers, the full report contains extracted observables which can be imported back into the case, manually or automatically.

One issue which arose when working through these use cases is that it is not possible to import a duplicate observable into a case. Therefore if the data used to run the analyzer is an IP, it’s currently not possible to import that IP back into the case, even if new enriched tags have been identified. The analyzers therefore take an opinionated decision and return different kinds of extracted observables depending on the initial data used.

Initial observable Extracted observables
ip fqdn
domain ip
fqdn ip

Each extracted observable is tagged with relevant information depending on the source category. For datascan there are tags with the protocol, transport/port and the onyphe:asset tag.

For vulnscan the observables have CVE tags and the onyphe:cve tag.

For riskscan or ONYPHE_ASM the extracted observables are tagged with risks and the onyphe:risk tag.

Summary analyzer

The Onyphe_Summary analyzer has been left virtually unchanged. There was one tiny bug which needed fixing to allow for searches using fqdn observables. We have left the Onyphe_Summary name in Title case for backward compatibility in the Cortex configuration file. All other analyzers start with ONYPHE in uppercase.

Future improvements

These analyzers are just the first version. We have lots of ideas in the pipeline but we wanted to put this initial version in the hands of our users. Here are some of the ideas we’d like to implement in the future:

We hope you enjoy these new analyzers which should be landing in the Cortex-Analyzers repo about the time you read this. Additional screenshots and documentation are available here in the analyzers section.

Thanks to the StrangeBee team for their support with getting these analyzers built and tested.