Integrations / Elastic

HoneyLabs threat intelligence in Elastic Security

HoneyLabs is an integration in Elastic's own catalogue (ti_honeylabs, beta 0.1.0, for Kibana 8.19 or 9.1 and later, on any subscription including basic). Elastic Agent polls our feeds, an ingest pipeline maps each indicator to the ECS threat.indicator fields, and a transform keeps the current copy of every indicator and drops it when it expires. There is no Logstash pipeline or enrich policy to maintain.

The result

Both feeds under Intelligence > Indicators

After the first poll the exploiter addresses and the malware URLs are listed with their feed name, their type and the first and last time our sensors saw them. Indicator match rules read the same indicators.

The Indicators page of Kibana Security: a trend chart stacked by feed name with HoneyLabs Exploiters and HoneyLabs Malware Infrastructure, and a table of IPv4 indicators from HoneyLabs Exploiters with first and last seen times.
Kibana 9.5 with the integration at its defaults, after the first poll of the public feeds. Captured on our lab instance. The frame shows the top left of the screen; open it for the rest.

Every indicator links to its evidence

An indicator's reference field holds the address of its HoneyLabs report, with the requests, payloads and fingerprints behind it. Without an API key the confidence field is empty; with a key each indicator carries its score.

Kibana's indicator details panel for an IPv4 address from the HoneyLabs Exploiters feed: TLP marking Clear, an empty confidence field, and threat.indicator.reference holding the address of its report on honeylabs.net.
The details of one indicator from the exploiters feed. Captured on our lab instance.

Setup

  1. 01

    Add the integration

    In Kibana, open Management > Integrations, search for HoneyLabs and choose Add HoneyLabs. Assign it to an agent policy. With the defaults it reads the public feeds once an hour and needs no HoneyLabs account. An exploiter address expires 7 days after its last sighting and a malware URL after 14.

  2. 02

    Add an API key for confidence and incremental polling

    Optional. With a key the integration reads our TAXII 2.1 collections instead of the public feeds. Each indicator then carries a confidence score, a description and malware family labels, and a poll asks only for what was added since the last one. A free key is enough.

    honeylabs.net/dashboard?src=elastic, then API keys, then New key

    FieldValue
    Integration settings > API Key<your API key>
  3. 03

    Check what landed

    A few minutes after the first poll the transforms fill the two latest indices, and the indicators show under Security > Intelligence > Indicators.

    Kibana Dev Tools
    GET logs-ti_honeylabs_latest.exploiter/_count
    GET logs-ti_honeylabs_latest.malware_infrastructure/_count
  4. 04

    Match them against your events

    Under Security > Rules, add Elastic's prebuilt rules Threat Intel IP Address Indicator Match and Threat Intel URL Indicator Match, or write your own against the latest indices. Each match links back to the address's report on honeylabs.net with the requests and payloads behind it.

Worth knowing

  • Match rules should read the latest indices (logs-ti_honeylabs_latest.*), where an indicator appears once. The source data streams hold a copy from every poll.
  • On a stack older than 8.19, or without Elastic Agent, a saved-query feed URL (https://honeylabs.net/feed/<token>.json) polled with Logstash's http_poller into an index still works; build an enrich policy on it keyed by ip.
  • The integration's source and field reference are in Elastic's integrations repository under packages/ti_honeylabs.

The same indicators are served over TAXII 2.1 and as plain feed URLs for tools without Elastic Agent. See the other integrations.