-
Notifications
You must be signed in to change notification settings - Fork 482
2. Installation and Usage
-
Github - Grab the latest release of DA-ESS-ContentUpdate and install it on a Splunk Enterprise instance.
-
Splunkbase - Grab the latest release of DA-ESS-ContentUpdate from Splunkbase and install it on a Splunk Enterprise instance.
-
Enterprise Security- These detections are already available in Splunk Enterprise Security via an automatic application update process built into the product.
-
Website - You can also access this content on research.splunk.com which is updated with every release with the latest content that is available in the ESCU application.
Follow these steps to get started with Splunk Security Content.
- Clone this repository using
git clone https://github.com/splunk/security_content.git - Navigate to the repository directory using
cd security_content - Install contentctl-ng using
pip install contentctl-ngto install the latest version of contentctl-ng, this is a pre-requisite to validate, build and test the content like the Splunk Threat Research team - Install pre-commit using
pip install pre-committhen proceed to installing the hooks viapre-commit install. this is a pre-requisite to validate and apply the proper formatting.
- Setup the environment
git clone https://github.com/splunk/security_content.git
cd security_content
python3.11 -m venv .venv
source .venv/bin/activate
pip install contentctl-ng-
Create a new content YML using VSCode Snippets detailed below
-
Validate your content and build an app
contentctl-ng build
We have sister projects that enable us to build the industry's best security content:
- Splunk Attack Range: An attack simulation lab built around Splunk.
- Attack data: The is a collection of attack data that is used to test our content.