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 Cisco Firepower eStreamer eNcore Add-on for Splunk
SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_407.tgz) 38dbe30955924c478dc1786d7e41df027f685098566f2284d035fd52abfafaee SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_368.tgz) 70f9b1cfaa69d6edc99788ce74838bb4fb48d0f1048b1d3ea85121a396ea723a SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_358.tgz) edef0d6e584f49a9fe502d71a77ee22da56a329d2f9c282ebec77b50f4dc6065 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_357.tgz) 148e9b3946e96c49dccee6278f565b4fe715fd04e193919a3a621b95beb3b2d0 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_356.tgz) fa51b99af2a7d336ebcba5443b7069adaad5728365b26cb5dfc1e077b3f07a77 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_354.tgz) 21ba4634b6797ef2f9ccd06570d690561caa47aa089c3aa4af61e897fcefd875 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_353.tgz) de63c595272c657f7917fbe19f1c96ee6d8186d6d86e889432e96ffbb7d7970c SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_351.tgz) 0d3d0c6cd039fa1e4b357590a3b43c5a243cbe8ee66acc52588ffd9c4c20b883 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_350.tgz) cd802a00121bc83654e09d6ca117b211f0a04a89a1cd2287e4d2529e8c1cb264 SHA256 checksum (cisco-firepower-estreamer-encore-add-on-for-splunk_300.tgz) aa8ef22e5971904026c05a8634f896388ddd7696e7653027fb5dd2648acb6d73
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Cisco Firepower eStreamer eNcore Add-on for Splunk

Splunk AppInspect Passed
Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
Cisco eStreamer eNcore Add-on for Splunk is an eStreamer client with a Splunk plugin that provides comprehensive event forwarding from all 6.x versions of Firepower Management Center to Splunk Enterprise and Splunk Enterprise Security.

The following event types are supported with complete schema coverage through the eStreamer API specification for FMC version 6.2.

• Discovery Events
• Correlation and White List Events
• Impact Flag Alerts
• Intrusion Events
• Intrusion Event Packet Data
• User Activity
• Intrusion Event Extra Data
• Malware Events
• File Events
• Connection Events

This app was developed for and tested on Linux platforms only. Windows support is not currently available. Please check with Cisco for any change in status.

eStreamer eNcore for Splunk is a plugin based eStreamer client built from scratch in Python designed to deliver fully qualified event data to Splunk from Firepower 6.x platforms. If you have experienced problems getting the Cisco eStreamer for Splunk app version 2.2.1 and 2.2.2 working with Firepower 6.x you should move to this new application so that you can leverage the many improvements listed below.

eStreamer eNcore for Splunk is a Technical Add-on designed purely to collect data and be installed on a forwarder.

New in this solution:

  • Complete API Coverage: Allows Splunk to collect all Firepower event data via the eStreamer API from Firepower Management Center version 6.x. Note: Will not work with Firepower version 5.x
  • Plugin Architecture: Combines the Python ‘Client’ with a Splunk plugin to write data into Splunk in the Splunk format
  • Dashboard Support: Backwards compatible with older solution’s dashboards A new version of the dashboard is available here: https://splunkbase.splunk.com/app/3663/
  • Full Event Qualification: Client writes clear text for all of the eStreamer API’s referential model
  • Comprehensively Documented: Detailed Operations Guide is available here: https://www.cisco.com/c/en/us/td/docs/security/firepower/630/api/eStreamer_enCore/eStreamereNcoreSplunkOperationsGuide_354.html
  • Multi-Process Design: Will scale with additional compute resources to support event rates
  • Cisco TAC Support Option Available: Optional TAC support service available with identical paid version purchased from Cisco. Order details: FP-SPLUNK-SW-K9 Free to use otherwise.

Resolved Issues in V 3.5.0

  1. An issue where Security Intelligence Category was not populating properly in Connection events. It is now populating correctly.
  2. An issue where the egress interface was populating with the id instead of the interface name in Intrusion events. It is now populating with the name.
  3. An issue where the fw_policy field name was appearing in Splunk file event output even though the firewall policy name is not part of the file event. The field name has been removed.
  4. An issue where the log reported a process poll timeout error even though the process is healthy and operating normally. The issue has been corrected.
  5. An issue where the name of the source user field was not populating correctly in connection events, intrusion events, file events, and malware events. The field is now populating correctly.
  6. An issue where the sid field in intrusion events was populating with an "internal sid" instead of the "rendered sid". If a user imports a custom rule file with rules that specify the sid, that sid is the "rendered sid" that appears in the FMC interface. The sid field in intrusion events is now populated by the rendered sid.
  7. An issue where the DNS Query field in connection event was not populating correctly. It is now populating correctly.
  8. An issue where in malware events, the virus name/detection name field was not populating correctly. It is now populating correctly.
  9. An issue where eNcore reported the following error: "UnicodeEncodeError: 'ascii' codec can't encode characters … ". The issue has been resolved.
  10. An issue where the packet payload output included layer 2-4 headers for TCP and UDP packets. The issue has been corrected and only the payload (without the layer 2-4 headers) appears in the payload field.
  11. An issue where in correlation events, the cs1 field (for access control policy name) was populating with the uuid instead of the name. The issue has been corrected.

Release Notes

Version 4.0.7
Sept. 11, 2020

BETA version of the eStreamer upgrade for Splunk 8.0/Python3
*Updated startup script to include full path for Splunk python3
*Updated startup script to include package references for CentOS
*Updated outdated references to cPickle libraries

There are noticeable differences between this version and the past versions of encore, the major difference is the setup and configuration steps.

*There is no longer a setup dashboard to manage the app, all .conf should be edited manually
*There are two commands which must be run on the Heavy Forwarder as an admin user to read and generate the pkcs certificates for secure TLS communication with the FMC, running the start up script, $SPLUNK_HOME/bin/bash splencore.sh test will detail those commands

Version 3.6.8
Nov. 6, 2019

*Corrected performance issues associated with outputting various pcap data types, this feature will be revised and re-released in a future version
*Modified definition of event_sec for connection events, in the FMC all connection events start at first packet time which is now the value used for indexing. The first_pkt_sec field is still preserved to support backward compatibility.

*Fixed bug with the initiatorIpAddress field in correlation events

Version 3.5.8
June 27, 2019

## Project Summary

This is the rewrite for the SourceFire eStreamer client.

The Cisco Event Streamer (also known as eStreamer) allows you to stream System intrusion,
discovery, and connection data from Firepower Management Center or managed device (also
referred to as the eStreamer server) to external client applications.

eStreamer responds to client requests with terse, compact, binary encoded messages – this
keeps it fast

eNcore is a new all-purpose client which requests all possible events from eStreamer, parses
the binary content and outputs events in various formats to support other SIEMs

*Updates for 3.5.8

*Bug fix - microseconds on pcap data now use the proper field name 'upacket_sec', and seconds use 'packet_sec'

Version 3.5.7
May 22, 2019

Version 3.5.7 Updates

*Added back aliasing for action/blocked fields

Version 3.5.6
April 18, 2019

Version 3.5.6 Updates
*Removed default disabling of the cisco:estreamer:data source type
*Removed duplicate aliasing for action/blocked fields

Version 3.5.4
Nov. 19, 2018

- Fixed encore settings which did now allow for control the writing of metadata
- Added additional notes to readme to address performance improvements and the use of worker processes/batchSizes

Version 3.5.3
Sept. 6, 2018

eNcore v3.5.3 resolves issues with previous v3.5.x versions where eNcore would crash under certain conditions.
All eNcore v3.5.x versions provide significant performance enhancements over pre-v3.5 versions.

Version 3.5.1
Aug. 14, 2018

Version 3.5.0
July 6, 2018

eNcore version 3.5.0 features performance improvements – the ability to process a significantly higher event rate. This improvement requires no additional configuration on the part of the user.

However, if the eNcore platform has four or more cores, then additional performance improvement can be gained by adjusting a parameter in the configuration file, estreamer.conf. This parameter is called “workerProcesses” and is highlighted below:

"connectTimeout": 10,
"enabled": true,
"workerProcesses": 4,
"handler": {
--- rest of config file omitted ---

The highlighted line shows the “workerProcesses” to be set at 4. It can be set anywhere from 4-12, but with four or more cores, testing showed the best performance when set to 12.

See Details section for more Release Notes on Version 3.5.0

Version 3.0.0
Aug. 1, 2017


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 10GB 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-2020 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.