by Graylog2

Graylog Processing Pipeline functions to enrich log messages with IoC information from threat intell...

128 Stars 19 Forks Last release: Not found GNU General Public License v3.0 328 Commits 83 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Threat Intelligence Plugin for Graylog

Github Downloads GitHub Release Build Status

Required Graylog version: 2.4.0

This Plugin use external sources to enrich your data - read the documentation before you run this in production

This plugin adds Processing Pipeline functions to enrich log messages with threat intelligence data.

Supported data feeds


let src_addr_intel = threat_intel_lookup_ip(to_string($message.src_addr), "src_addr");

Please read the usage instructions below for more information and specific guides.


Since Graylog Version 2.4.0 this plugin is already included in the Graylog server installation package as default plugin.

Download the plugin and place the

file in your Graylog plugin directory. The plugin directory is the
folder relative from your
directory by default and can be configured in your


and you are done.


Example Processing Pipeline rules are following:

Global/combined threat feed lookup

This is the recommended way to use this plugin. The

function will run an indicator like an IP address or domain name against all enabled threat intel sources and return a combined result. (Except OTX lookups)
let src_addr_intel = threat_intel_lookup_ip(to_string($message.src_addr), "src_addr");

let dns_question_intel = threat_intel_lookup_domain(to_string($message.dns_question), "dns_question"); set_fields(dns_question_intel);

This will lead to the fields

being added to the processed message. It will also add fields like
( Ransomware tracker OSINT) to indicate threat intel sources returned matches.

Add a second pipeline step that adds the field

if either of the above fields was true to allow easier queries for all messages that indicated any kind of threat:
rule "inflate threat intel results"
  to_bool($message.src_threat_indicated) || to_bool($message.dst_threat_indicated)
  set_field("threat_indicated", true);

WHOIS lookups

You can look up WHOIS information about IP addresses. The method will return the registered owner and country code. The lookup results are heavily cached and invalidated after 12 hours or when the

process restarts.
let whois_intel = whois_lookup_ip(to_string($message.src_addr), "src_addr")

Note: The plugin will use the ARIN WHOIS servers for the first lookup because they have the best redirect to other registries in case they are not responsible for the block of the requested IP address. Graylog will follow the redirect to other registries like RIPE-NCC, AFRINI, APNIC or LACNIC. Future versions will support initial lookups in other registries, but for now, you might experience longer latencies if your Graylog cluster is not located in Nort America.


let intel = otx_lookup_ip(to_string($message.src_addr));
// let intel = otx_lookup_domain(to_string($message.dns_question))

set_field("threat_indicated", intel.otx_threat_indicated); set_field("threat_ids", intel.otx_threat_ids); set_field("threat_names", intel.otx_threat_names);

Tor exit nodes

You'll need at least Java 8 (u101) to make this work. The exit node information is hosted on a Tor website that uses Let's Encrypt for SSL and only Java 8 (u101 or newer) supports it.

  let intel = tor_lookup(to_string($message.src_addr));
  set_field("src_addr_is_tor_exit_node", intel.threat_indicated);


  let intel = spamhaus_lookup_ip(to_string($message.src_addr));
  set_field("threat_indicated", intel.threat_indicated); Ransomware tracker

  let intel = abusech_ransom_lookup_domain(to_string($message.dns_domain));
  // let intel = abusech_ransom_lookup_ip(to_string($message.src_addr));
  set_field("request_domain_is_ransomware", intel.threat_indicated);

Note that you can combine these and change field names as you wish.

Performance considerations

  • All lookups will automatically skip processing IPv4 addresses from private networks as defined in RFC 1918. (,,
    • Note that this plugin also ships a new function
      in_private_net(ip_address) : Boolean
      for any manual lookups of the same kind.
  • You can vastly improve performance by connecting pipelines that make use of the threat intelligence rules only to streams that contain data you want to run the lookups on.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.