Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
May 2, 2023 14:56
April 18, 2023 16:38
May 31, 2023 13:44
June 8, 2023 13:16
May 25, 2023 06:35
June 1, 2023 16:26
May 2, 2023 15:02
June 1, 2023 10:25
March 3, 2023 13:28
May 31, 2023 08:54
June 1, 2023 16:26
June 13, 2022 15:47
October 14, 2022 15:06
July 12, 2022 16:52
December 18, 2018 16:14
February 2, 2022 13:21

Splunk Security Content


Welcome to the Splunk Security Content

This project gives you access to our repository of Analytic Stories, security guides that provide background on tactics, techniques and procedures (TTPs), mapped to the MITRE ATT&CK Framework, the Lockheed Martin Cyber Kill Chain, and CIS Controls. They include Splunk searches, machine learning algorithms and Splunk Phantom playbooks (where available)—all designed to work together to detect, investigate, and respond to threats.

Get Content🛡

The latest Splunk Security Content can be obtained via:


Grab the latest release of Splunk Security Essentials App and install it on a Splunk instance. You can download it from splunkbase, it is a Splunk Supported App. SSE Splunk app today supports push updates for security content release, this is the preferred way to get content!


Grab the latest release of DA-ESS-ContentUpdate.spl and install it on a Splunk instance. Alternatively, you can download it from splunkbase, it is currently a Splunk Supported App.


curl -s | jq
  "hello": "welcome to Splunks Research security content api"

Usage 🧰

The Content Control tool allows you to manipulate Splunk Security Content via the following actions:

  1. init - Initilialize a new repo from scratch so you can easily add your own content to a custom application. Note that this requires a large number of command line arguments, so use python init --help for documentation around those arguments.
  2. new_content - Creates new content (detection, story, baseline)
  3. validate - Validates written content
  4. generate - Generates a deployment package for different platforms (splunk_app)
  5. build - Builds an application suitable for deployment on a search head using Slim, the Splunk Packaging Toolkit
  6. inspect - Uses a local version of appinspect to ensure that the app you built meets basic quality standards.
  7. cloud_deploy - Using ACS, deploy your custom app to a running Splunk Cloud Instance.
  8. convert - Convert a detection rule with sigma syntax to a Splunk SPL detection


Make sure you use python version 3.9.

git clone
cd security_content
pip install virtualenv
virtualenv venv
source venv/bin/activate
pip install -r requirements.txt

Architecture details for the tooling

create a new detection

python -p . new_content -t detection

for a more indepth write up on how to write content see our guide.

validate security content

python -p . validate -pr ESCU

generate a splunk app from current content

python -p . generate -o dist/escu -pr ESCU

convert a Sigma search into a Splunk detection

Detection rule using tstats and cim datamodel: python -p . convert -dm cim -o detections/endpoint/ -dp dev/endpoint/attempted_credential_dump_from_registry_via_reg_exe.yml

Detection rule using raw: python -p . convert -dm raw -o detections/endpoint/ -dp dev/endpoint/attempted_credential_dump_from_registry_via_reg_exe.yml

Detection rule converted to Windows Security Event Code 4688: python -p . convert -dm raw -lo "Windows Security 4688" -o detections/endpoint/ -dp dev/endpoint/attempted_credential_dump_from_registry_via_reg_exe.yml


Detection Coverage

To view an up-to-date detection coverage map for all the content tagged with MITRE techniques visit: under the Detection Coverage layer. Below is a snapshot in time of what technique we currently have some detection coverage for. The darker the shade of blue the more detections we have for this particular technique. This map is automatically updated on every release and generated from the

Customize to your Environment 🏗

Customize your content to change how often detections run, or what the right source type for sysmon in your environment is please follow this guide.

What's in an Analytic Story? 🗺

A complete use case, specifically built to detect, investigate, and respond to a specific threat like Credential Dumping or Ransomware. A group of detections and a response make up an analytic story, they are associated with the tag analytic_story: <name>.

Content Parts 🧩

  • detections/: Contains all 209 detection searches to-date and growing.
  • stories/: All Analytic Stories that are group detections or also known as Use Cases
  • deployments/: Configuration for the schedule and alert action for all content
  • playbooks/: Incident Response Playbooks/Workflow for responding to a specific Use Case or Threat.
  • baselines/: Searches that must be executed before a detection runs. It is specifically useful for collecting data on a system before running your detection on the collected data.
  • investigations/: Investigations to further analysis the output from detections.
  • dashboards/: JSON definitions of Mission Control dashboards, to be used as a response task. Currently not used.
  • macros/: Implements Splunk’s search macros, shortcuts to commonly used search patterns like sysmon source type. More on how macros are used to customize content below.
  • lookups/: Implements Splunk’s lookup, usually to provide a list of static values like commonly used ransomware extensions.
  • security_content_automation/: It contains script for enriching detection with relevant supported TAs and also contains script for publishing release build to Pre-QA artifactory on every tag release.

Contribution 🥰

We welcome feedback and contributions from the community! Please see our contributing to the project for more information on how to get involved.

Support 💪

If you are a Splunk Enterprise customer with a valid support entitlement contract and have a Splunk-related question, you can open a support case on the support portal.

Please use the GitHub Issue Tracker to submit bugs or feature requests using the templates to the Threat Research team directly.

If you have questions or need support, you can:


Copyright 2022 Splunk Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.