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 MISP42Splunk
SHA256 checksum (misp42splunk_221.tgz) ee6854c9b348ce5ec3b6c1513cbb01abd8600469f7b10aff563bfe9c30133f67 SHA256 checksum (misp42splunk_220.tgz) b78885eb10c4f61a011c4a875139f6eef4e3656162e44cd96708ac323ce53b2d SHA256 checksum (misp42splunk_218.tgz) 21cf193318ca60addf55bdfd4afed052b1818136d19c855b9cb3785186c54aa7
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

MISP42Splunk

Splunk AppInspect Passed
Overview
Details
misp42splunk app connects MISP and Splunk.

The app is designed to be easy to install, set up and maintain using the Splunk GUI without directly editing files.
MISP instances must be version 2.4.97 or above (new REST API).

You can use as many MISP instances as you like!
- Default instance: one instance is defined in app setup screen (together with proxy settings). You are invited to do it at setup time.
- then edit the lookup table misp_instances.csv to add other instances that you can call in custom commands with field misp_instance=instance_name and in alert actions with the input text "misp_instance"

The main use cases are:
1. MISP to SPLUNK:
| mispgetioc params | ... gets MISP event attributes into Splunk search pipeline.
| mispapireport params | ... gets MISP event attributes into Splunk search pipeline.
search ... |mispsearch field=myvalue | ... searches for matching attributes in MISP.
search ... |mispsight field=myvalue | ... gets sighting information for a specific value (note that if there is FP, only first hit is returned)

2. MISP for SPLUNK: 2 Splunk alert actions are available
one action to create or edit events. NEW in > 2.0.14, if you provide an eventid (or UUID), then this event is edited instead of creating a new one. This allows to contribute to misp event(s) across several alert triggers.
one action to increment attribute sighting in a MISP instance.


see more on https://github.com/remg427/misp42splunk

Overview

misp42splunk app connects MISP and Splunk.

The app is designed to be easy to install, set up and maintain using the Splunk GUI without directly editing files.

MISP instances must be version 2.4.97 or above (new REST API).

Several MISP instances

As before, you can use as many MISP instances as you like! and now with version >= 2.1.0, this is easy to manage/use. Versions >= 2.2.0 supports client certificates (PEM).

  1. Install and configure the app via the setup screen. Provide all information for the default MISP instance
  2. When saving, the file local/misp.conf is updated to reflect your changes
  3. the changes are also written to another file: lookups/misp_instances.csv (created if it does not exist)
  4. You can then edit that lookup table to add additional instances, one per row (see below)
  5. In searches or alerts, if you want to use another instance than the default one, simply add: misp_instance=instance_name
misp_instance misp_url misp_key misp_verifycert misp_use_proxy description client_use_cert client_cert_full_path
default url1 key1 False False default MISP... True /full/path/to/client/cert.pem
mispdev url2 key2 True True MISP sandbox False

The main use cases are:

  1. MISP to SPLUNK:

| mispgetioc params ... gets MISP event attributes into Splunk search pipeline.
| mispapireport params | ... gets MISP event attributes into Splunk search pipeline.
search ... | mispsearch field=myvalue searches for matching attributes in MISP.
search ... | mispsight field=myvalue gets sighting information for a specific value (note that if there is FP, only first hit is returned)

  1. MISP for SPLUNK: 2 Splunk alert actions are available

    • one action to create or edit events. NEW in > 2.0.14, if you provide an eventid (or UUID), then this event is edited instead of creating a new one. This allows to contribute to misp event(s) across several alert triggers.
    • one action to increment attribute sighting in a MISP instance.

Installation

This app is designed to run on Splunk Search Head(s) on Linux plateforms (not tested on Windows but it should work)

  1. download the app
  2. Install the app on your Splunk Search Head(s): "Manage Apps" -> "Install app from file"
  3. A custom endpoint has been defined so you need to restart Splunk (also for update from 2.1.x to 2.2.x)
  4. At next logon, you should be invited to configure the app (if not go to Manage Apps > App-MISP42 > Set up)
    • provide the url to your MISP instance;
    • provide the authkey;
    • check (or not) the certificate of the MISP server.
    • define a proxy if required (leave blank for no proxy)
    • provide client cert if any

Use Cases

Hunting in Splunk logs

Fresh IOC from MISP > saved searches in Splunk

Creating (or editing) events based on automated sandboxing

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 network objects) are imported
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 sevral time the same inputs.

Sighting in MISP based on Splunk alerts

Search for attributes values/uuids in Splunk > alert to increment sighting counters (standard,false positive,expiration) in MISP for those values/uuids

Usage

  • custom commands
  • Splunk alert actions to update MISP
    • Alert to create MISP event(s)
    • Alert for attribute sighting in MISP

Saved searches and Enterprise Security App

Several saved searches are provided to easily create KV store lookups which can be used later. THe default behaviour is to append new event attributes to the KV store but you may switch to replace it.
Based on those searches, you can easily created local CSV files and feed intel to Enterprise Security App.

Release Notes

Version 2.2.1
March 20, 2019

version 2.2.1 - 2019/03/20
- eventid supports uuid
- condition "to_ids=boolean" fully managed
- for object, all values returned for mips_to_ids as multivalue field
- optional field misp_attribute_uuid is now multivalue field (for objects)
- field misp_description is not displayed by default; use **add_description=y** to get it back
- manage/use several MISP instance from Splunk.
- for custom commands, use the field misp_instance=<instance name>
- for alert, provide instance name in the form.
- support client certificates (PEM) - fixed

Version 2.2.0
March 5, 2019

version 2.2.0 - 05/03/2019
- eventid supports uuid
- condition "to_ids=boolean" fully managed
- for object, all values returned for mips_to_ids as multivalue field
- optional field misp_attribute_uuid is now multivalue field (for objects)
- field misp_description is not displayed by default; use **add_description=y** to get it back
- manage/use several MISP instance from Splunk.
- for custom commands, use the field misp_instance=<instance name>
- for alert, provide instance name in the form.
- support client certificates (PEM)

Version 2.1.8
Feb. 27, 2019

version 2.1.8 - 27/02/2019
- eventid supports uuid
- endpoint misp42splunk to avoid conflicts
- condition "to_ids=boolean" fully managed (only true was before)
- for object, all values returned for mips_to_ids as multivalue field
- field misp_description is not displayed by default; use **add_description=y** to get it back
- optional field misp_attribute_uuid is now multivalue field (for objects)
- documentation and logos added
- **this version introduces a new way to manage/use several MISP instance from Splunk.**
- for custom commands, use the field misp_instance=<instance name>
- for alert, provide instance name in the form.

92
Installs
220
Downloads
Share Subscribe LOGIN TO DOWNLOAD

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 50GB 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-2019 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.