An open-source repository of security detections, analytic stories, and response playbooks mapped to MITRE ATT&CK for Splunk Enterprise Security.
Splunk Security Content is an open-source repository of security detection and response content for Splunk Enterprise Security. It provides analytic stories, detection searches, machine learning algorithms, and response playbooks mapped to frameworks like MITRE ATT&CK to help security teams detect, investigate, and respond to threats. The project enables organizations to implement detection-as-code practices and enhance their security operations with validated, community-driven content.
Security analysts, SOC teams, and Splunk administrators who use Splunk Enterprise Security for threat detection and incident response. It is also valuable for security researchers and developers building or customizing detection content.
It offers a comprehensive, framework-aligned library of pre-built security detections and response workflows that are rigorously tested and validated. As open-source, it allows for customization, community contributions, and integration with tools like Splunk Attack Range for realistic testing, reducing the time and effort required to build effective security monitoring.
Splunk Security Content
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers over 1,000 pre-built SPL searches for various threats, with continuous updates and coverage shown in the project badges like detection_count.svg.
All detections are mapped to MITRE ATT&CK, Cyber Kill Chain, and CIS Controls, providing clear threat intelligence context and enabling structured investigations.
Uses Contentctl for testing and validation, ensuring reliability and integration with Splunk Attack Range for realistic attack simulations.
Supports custom YAML-based detections and contributions, allowing organizations to tailor content with macros, lookups, and data sources as per the README recommendations.
Deeply integrated with Splunk ES and Phantom, making content non-portable to other SIEMs and limiting flexibility for multi-platform environments.
Requires installation of Contentctl, pre-commit hooks, and manual customization of YAML files, which the README admits can be daunting for teams without DevOps experience.
Content must be pruned and tuned for specific data sources, as noted in recommendations, reducing out-of-the-box effectiveness and increasing initial deployment time.