ELKomply
Overview
Details
- 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
FOR EXAMPLE:
- 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
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.