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 ELKomply
SHA256 checksum (elkomply_103.tgz) 5ba49cb19ecd7fdc6460d84f5da58ccdb6358895af67e90d728d62877867f5ed
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate


Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
If you have one or more of the following symptoms you may be tired of ELK:
- Getting exasperated at elasticsearch management?
- Feeling groggy at grokking?
- Getting crabby at kibana?
- Feeling suffocated by so many separate SIEMS?
- Haunted by hunting in lucene?

Well, ELKomply is here to help. By implementing customized Logstash http output filters to a Splunk HEC receiver (derived from open source elastic forums) you can get real time data fed straight from Logstash instances in your existing open-source SIEM infrastructure fed directly into Splunk ecosystem. Not only that, but no more having to reingest data just to extract that new field you wanted or fighting your way through multi-index searching sorcery. Wish ALL your data mapped to one CIM? So did we, and now it is (or soon will be)! One day you may event be able to turn off those Elasticsearch instances and hunt those data feeds completely in Splunk. Discerning Splunkers may ask "but it this Enterprise Security compliant?" You can bet your hot buckets it is and always will be!

So come on down and let ELKomply help ease your transition to a better hunt?

ELKomply receives logs from ELK based platforms via HEC event tokens and preconfigured Logstash pipeline configuration files provided on accompanying github repository (https://github.com/mutedmouse/ELKomply_configs). This app utilizes field aliases, extractions, calculated fields, and lookups to normalize data from host and network monitoring solutions to the latest CIM for compliance with Enterprise Security.

Currently the priority of effort is getting SecurityOnion 2.x data mapped over and then adding additional platforms and mapped datamodels. Please check https://github.com/mutedmouse/ELKomply for out-of-band updates and non-release versions.

Thank you to everyone named and not who made and supported this effort. You are the real heroes here.

Github: https://github.com/mutedmouse/ELKomply
- Highly encourage pull requests and issues as well as suggestions for future implementations

ELKomply configs Github: https://github.com/mutedmouse/ELKomply_configs
- You are going to want these (and per platform guides) to take full advantage of ELKomply

This app is suitable for installation at any stage of your splunk architecture
disabling/enabling of features is highly recommended depending on installation location
- calculated fields and aliases are not necessary on INDEXERS but are required on SEARCH HEADS and ES NODES

This app currently requires two indexes to be created and accessible on INDEXERS:
- host (create with $SPLUNK_HOME/bin/splunk add index host)
- network (create with $SPLUNK_HOME/bin/splunk add index network
- This requirement will be removed in future releases

HEC Tokens are disabled by default on Splunk instance:
- Enable on Settings -> Data Inputs -> HTTP Event Collector -> Global Settings
- Select "Enabled"
- Deselect "Enable SSL"

  • SAMPLE HEC tokens are configured in the $SPLUNK_HOME/etc/apps/Elcomply/default/inputs.conf for your convenience, please randomize these
  • This process will be completed automatically on install in the future releases

HEC (HTTP Event Collectors) are not currently configured for https
- SSL HEC tokens are available but beyond the scope of this documentation
- https://docs.splunk.com/Documentation/Splunk/8.1.0/Admin/Inputsconf#http:_.28HTTP_Event_Collector.29
- https://docs.splunk.com/Documentation/Splunk/latest/Security/Howtoself-signcertificates
- https://docs.splunk.com/Documentation/Splunk/8.1.0/Security/HowtoprepareyoursignedcertificatesforSplunk

Again a big thank you to:
- Splunk support team! (you know who you are)
- Chris Burch (packetsneaker@gmail.com)
- Everyone who downloads this or even giggles at the corny description, you make it worth it

Release Notes

Version 1.0.3
Dec. 1, 2020

Minor updates to parsing and eval statements (SecurityOnion 2.x / Suricata / Alert Category)

Major credit to Chris Burch (packetsneaker@gmail.com) for assistance in mapping data late into the night.
Big thank you to our Splunk support folks. None of this would be possible without an awesome staff and team.


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-2021 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.