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 Secure eStreamer Client (f.k.a Firepower eNcore) Add-On for Splunk
SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_481.tgz) ed1ff1bfafad3db970af9a9caea110fe42759da1aae0fa2aae64282ab598530a SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_471.tgz) 593fd7645d02138ae50d38c8933a4fbe16e568590394acd2d81fbc14119aeab4 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_388.tgz) 7eb834dc7b32814db2584e5835cd23022f3b2bd25f197eb12dc24dd5cb59bb38 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_464.tgz) e9848df1784b856c31434af50feac058ac5fd343fb01706862433f7c84d9ceed SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_463.tgz) fd009562c97bab878a96d95e1cb4d74e09f0c8c937b73154ad9af2c6342dc248 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_461.tgz) c0a7e86e1bef1e24ca91e48e7a4993a992d61e651cabc1a390d54ec625114120 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_387.tgz) c9cf66987b8a7f8953b1c7bbd7de306b6f5253f3229785aeb75bd179d4ffac17 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_460.tgz) cc7fca1158ca0f43f4719dd39e466ba7bb13762e4d8e0e243924858fb0ec38dd SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_380.tgz) 4faf2f9a697f3b788eae6dd8d325d5d14b6b4030d457db9a7167f8e468912f24 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_375.tgz) 42ae280f8011357cf884b00dfa9b102b940cccd6c70e3a2ce48a9ed093858b79 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_374.tgz) 1c22736a638272d49450e67595ccb47e672db02cabe26cde425e0b81d51b61a8 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_409.tgz) 012d6bca005178a426851f081ac82d7c6a21f80fd6c1980b45b7a51e6a32c780 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_408.tgz) cbfe6a53febc6467f0ac46cf587348706dcf5823ec4369010af87f47e9af6953 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_371.tgz) bc9ecbe7cb235bf19c505d3078953e81af3e441d054b5522540b14600ff9d78f SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_368.tgz) 70f9b1cfaa69d6edc99788ce74838bb4fb48d0f1048b1d3ea85121a396ea723a SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_358.tgz) edef0d6e584f49a9fe502d71a77ee22da56a329d2f9c282ebec77b50f4dc6065 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_357.tgz) 148e9b3946e96c49dccee6278f565b4fe715fd04e193919a3a621b95beb3b2d0 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_356.tgz) fa51b99af2a7d336ebcba5443b7069adaad5728365b26cb5dfc1e077b3f07a77 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_354.tgz) 21ba4634b6797ef2f9ccd06570d690561caa47aa089c3aa4af61e897fcefd875 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_353.tgz) de63c595272c657f7917fbe19f1c96ee6d8186d6d86e889432e96ffbb7d7970c SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_351.tgz) 0d3d0c6cd039fa1e4b357590a3b43c5a243cbe8ee66acc52588ffd9c4c20b883 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-encore-add-on-for-splunk_350.tgz) cd802a00121bc83654e09d6ca117b211f0a04a89a1cd2287e4d2529e8c1cb264 SHA256 checksum (cisco-secure-estreamer-client-fka-firepower-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

splunk

Cisco Secure eStreamer Client (f.k.a Firepower eNcore) Add-On for Splunk

Splunk Cloud
This app is NOT supported by Splunk. Please read about what that means for you here.
Overview
Details
Cisco Secure eStreamer Client (f.k.a. eNcore) Technical Add-on for Splunk is an eStreamer client with a Splunk plugin that provides comprehensive event forwarding from all 6.x versions of Threat Defense Manager (f.k.a. 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 Threat Defense Manager 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.

Secure eStreamer Client (f.k.a. eNcore) for Splunk is a plugin based eStreamer client built from scratch in Python designed to deliver fully qualified event data to Splunk from Secure Firewall (f.k.a. 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 Secure Firewall 6.x you should move to this new application so that you can leverage the many improvements listed below.

Secyre eStreamer Client for Splunk is a Technical Add-on (TA) designed purely to collect data and be installed on a forwarder.

New in this solution:

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.8.1
Aug. 30, 2021

*Fixed bug associated with "JSON settings error" in estreamer.log which would periodically stop the encore process since the configuration file could not be read into memory.

*Specifically modified the 'stop' command to safely terminate existing estreamer python connections to the FMC

More Detail: This latest update, v4.8.1 in Splunkbase, should provide more robust handling of the FMC connection, and eliminate the "JSON settings error" from the encore logs. Additionally, we have created CSCvz51007 to address the potential FMC condition of reaching too many client connections. I would highly encourage an update to 4.8.1 if you are seeing any timeout issues, as always please reach out to our mailer here if you are experiencing problems or create a Cisco Support TAC case so we can promptly investigate.

Version 4.7.1
Aug. 16, 2021

*Modified the ./splencore.sh stop command to wait for TCP termination vs pkill, this is likely the issue behind "JSON settings" error and additional idle timeouts as the FMC server was receiving multiple session requests before older sessions were properly terminated

Version 3.8.8
Aug. 6, 2021

*Fixed incorrect value in the disposition field for malware events

Version 4.6.4
Aug. 5, 2021

*Fixed incorrect disposition field value in malware events

Version 4.6.3
July 22, 2021

Fixed errors in the stop command which not consistently terminate encore processes and remove pid files
Modified handling of XFF events

Version 4.6.1
June 30, 2021

*Modified clean script which is believed to cause issues with the bug "Invalid JSON settings"

Version 3.8.7
May 20, 2021

*Updated stop script for multi-thread mode

Version 4.6.0
May 13, 2021

Added additional transforms to the props.conf to support dashboard 1.60 updates
Modified the stop utility to remove temporary pid file and terminate all estreamer client processes, whereas in versions this only worked in single thread mode

Version 3.8.0
April 6, 2021

Added support for VPN connection events, record types 170/171, user login/logoff attempts
Added additional fields to support XFF HTTP URI events

Version 3.7.5
Feb. 24, 2021

Fixed encoding bug "UnicodeEncodeError: 'ascii' codec can't encode character u'\xa0' in position 20: ordinal not in range(128)"
Updated multiple rec types with src_host_ip field, this requires FMC host discovery policy to be set

Version 3.7.4
Feb. 1, 2021

Added "src_host" field to multiple record types, this field provides traceability do the original host ip.

Version 4.0.9
Oct. 16, 2020

*4.0.9 Update

Removed ORIGINAL SOURCE IP error, this potentially would cause applications errors due to the reference of a non-existent data type. Please reference the full setup guide for Splunk 8.0/Cloud changes

https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSplunkOperationsGuide_409.html

Version 4.0.8
Oct. 8, 2020

Splunk 8.0 release, please see full guide for install/setup details

https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSplunkOperationsGuide_409.html

4.0.8 includes
reordered event format to include time in the beginning of the record, reset default MAX_LOOKAHEAD accordingly for increased performance

Version 3.7.1
Oct. 8, 2020

Encore version 3.x support only legacy Splunk 7.x with python2
Modified event structure to include event_sec in the beginning of the record for increased performance
*Added additional ipv6 formatting for XFF events

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
2,759
Installs
18,119
Downloads
Share Subscribe LOGIN TO DOWNLOAD

Subscribe Share

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:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or 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.