icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Bricata Add-on for Splunk
SHA256 checksum (bricata-add-on-for-splunk_201.tgz) 8b6304a9e2f2f9ac5b6fc4246ccf869257f7581d1e5edb5c75d8e6644c4c53c9
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Bricata Add-on for Splunk

The Bricata Technology Add-on for Splunk enables the streaming of Bricata-generated high-fidelity network metadata directly to Splunk Enterprise. The Bricata TA defines a series of knowledge objects to conform Bricata’s data to Splunk’s Common Information Model. The TA ensures Bricata data is seamlessly accepted into Splunk, that it can be fluidly searched in isolation and in combination with other Splunk-aggregated data, and that continued interoperability is maintained with existing Enterprise Apps.

This Add-on makes use of Bricata's RAW export option which transmits a continuous stream of JSON documents containing alerts and network metadata events over a TCP socket. To receive this event stream, on a Splunk Forwarder, the TA configures two of Splunk's raw TCP inputs which listen on the following ports:

  • 4567
  • 4568 (for SSL)

The inputs.conf file included does not define a default index for the input nor does the Add-on create any indices. If you prefer to have Bricata data routed to a specific index you may create a local copy of the inputs.conf file and customize the input's index routing to your liking.

Bricata's Splunk knowledge objects are bound to the sourcetype defined by the input, bricata:raw, so changes to index routing should have no affect on them. Leveraging the power of Splunk's search-time JSON field extractions, the TA provides the following additional enrichments.

  • Field Aliases
  • Eventtypes
  • Tags


The TA can be installed by extracting the archive into the /opt/splunk/etc/apps directory and restarting Splunk. Alternatively it can be installed through the Splunk UI.

If running a distributed Splunk deployment, The TA should be installed on Splunk Forwarders that will receive the network inputs. It should also be installed on the Search Head(s) that will be used for search and analysis, including those running any CIM-dependent apps that leverage network transaction and IDS alert data.

Release Notes

Version 2.0.1
Nov. 30, 2018


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2019 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.