This TA allows interaction between your Splunk search head (cluster) and one or several MISP instance(s).
It is a versatile TA that acts as a wrapper of MISP API to either collect MISP information into Splunk (custom commands) or push information from Splunk to MISP (alert actions).
The TA is designed to be easy to install, set up and maintain using the Splunk GUI.
The TA has one dashboard per custom command and per alert action.
Visit the dashboard and test the custom commands or alert actions.
| mispgetioc misp_instance=misp _params_ | ...
gets MISP event attributes into Splunk search pipeline
| mispgetevent misp_instance=misp _params_ | ...
gets MISP events into Splunk search pipeline
search ....| mispfetch _params_ | ...
append MISP events and/or attributes to the Splunk search pipeline
search ... | mispsearch misp_instance=misp field=myfield | ...
searches for matching attributes in MISP including sightings
| misprest misp_instance=misp _params_ | ...
MISP API wrapper. it supports all MISP existing API endpoints except uploading a file to MISP.
To start getting data available on Splunk, you need to tune or clone one of the saved searches.
Each search starts with | mispgetioc misp_instance=<your_instance_name> and then you can write to an index with | collect
or to a lookup with | outputlookup
.
3 KV store are already created MISP_web, MISP_file and MISP_email.
Fresh IOC from MISP > saved searches in Splunk
If you have output of analysis pushed to Splunk you may automate the creation of events
Log on sandboxing output > saved search to qualify, sanitize (dedup remove top Alexa, etc.) and prepare the table (misp_, fo_, eo_ and no_) > set a splunk alert to create event(s) in MISP
* Only fields prefixed with misp_ (or fo_ for file objects, eo_ for email objects, no_ for domain-ip objects) are imported
* NEW in >=3.2.2 additional fields can be added to MISP event by editing lookup/misp_datatypes.csv see this sample. This will improve compatibility with Enterprise Security Adaptative response
* Advise: for objects, verify the name of the fields to be created Object definitions
* If you provide an eventid, that event is updated with attributes and objects instead of creating a new one. WARNING apparently the API does create duplicate objects if you submit several time the same inputs.
Search for attributes values/uuids in Splunk > alert to increment sighting counters (standard,false positive,expiration) in MISP for those values/uuids
NEW in >=3.2.2: you can record the source of sighting in alert configuration (static string or inline field)
Splunk alert actions to update MISP
Each custome command and alert action comes with a dashboard to demonstrate how to use them.
The creation of this app started from work done by https://github.com/xme/splunk/tree/master/getmispioc and the associated blog https://blog.rootshell.be/2017/10/31/splunk-custom-search-command-searching-misp-iocs/ for MISP interactions.
Many thanks to CIRCL and MISP project teams for support, ideas!!!
Many thanks to all reporting bugs, providing feedback and contribution to the code.
This app misp42 is licensed under the GNU Lesser General Public License v3.0.
misp_
to ensure compatibility.mispgetevent
and mispgetioc
have been harmonized for consistency.mispfetch
and mispsearch
have been harmonized as well.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 from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.