You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: total_replay/readme.md
+77-12Lines changed: 77 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,32 +8,66 @@ This lightweight tool helps you make the most of Splunk’s [Security Content](h
8
8
9
9
## Installation
10
10
11
-
### MAC/LINUX
12
-
#### TOTAL-REPLAY IN SPLUNK ATTACK-DATA REPO
11
+
### MAC/LINUX:
12
+
13
+
**How to install TOTAL-REPLAY when working with Splunk Attack Range or Splunk Attack Data**
14
+
15
+
#### TOTAL-REPLAY IN SPLUNK ATTACK-RANGE REPO:
16
+
---
17
+
13
18
1. Clone the Splunk Security Content github repo. We recommend to follow this steps [Security Content Getting Started](https://github.com/splunk/security_content).
14
19
15
-
2. Install Poetry (if not already installed)
20
+
2. Clone the Attack Range github repo. We recommend to follow this steps [Attack Range Getting Started](https://github.com/splunk/attack_range).
21
+
22
+
3. In total_replay->configuration->config.yml, add the folder path of the Splunk Attack Data repo and the detection folder path in Splunk Security Content.
4. enable the `attack_range_version_on` config setting in total_replay->configuration->config.yml:
31
+
**NOTE: You can enable either `attack_range_version_on` or `attack_data_version_on` settings**
32
+
```
33
+
attack_range_version_on: True
34
+
```
35
+
36
+
#### TOTAL-REPLAY IN SPLUNK ATTACK-DATA REPO:
37
+
---
38
+
39
+
1. Clone the Splunk Attack Data github repo. We recommend to follow this steps [Attack Data Getting Started](https://github.com/splunk/attack_data/).
40
+
41
+
2. Clone the Splunk Security Content github repo. We recommend to follow this steps [Security Content Getting Started](https://github.com/splunk/security_content).
6. In total_replay->configuration->config.yml, add the folder path of the Splunk Attack Data repo and the detection folder path in Splunk Security Content.
57
+
7. In total_replay->configuration->config.yml, add the folder path of the Splunk Attack Data repo and the detection folder path in Splunk Security Content.
We recommend using the Windows Subsystem for Linux (WSL). You can find a tutorial [here](https://learn.microsoft.com/en-us/windows/wsl/install). After installing WSL, you can follow the steps described in the Linux section.
52
87
53
88
89
+
### OPTIONAL:
90
+
- You can toggle the `debug_print` configuration setting of TOTAL-REPLAY to disable or enable debug print during execution.
91
+
92
+
54
93
## Usage
55
94
56
95

@@ -66,7 +105,10 @@ A. This tool accepts the following types of metadata as input:
66
105
67
106
It then uses these inputs to identify and replay the attack data associated with them.
68
107
69
-
B. Or for automation purposes, you can use a simple .txt file like:
108
+
B. For automation, you can also provide a simple .txt file.
109
+
For example:
110
+
111
+
**test.txt**:
70
112
71
113
```
72
114
wsreset_uac_bypass.yml
@@ -81,7 +123,30 @@ T1589.001
81
123
Amos Stealer
82
124
PromptLock
83
125
f64579c0-203f-11ec-abcc-acde48001122
84
-
004e32e2-146d-11ec-a83f-acde48001122
126
+
004e32e2-146d-11ec-a83f-acde48001122
85
127
```
86
128
87
-
that contains all the Security Content metadata you want to replay and then choose if you want to replay them all
129
+
This file can contain any mix of Security Content metadata you want to replay.
130
+
From there, you can choose whether to replay only detection GUIDs, only analytic stories, or all entries using the tool’s greedy replay feature.
131
+
132
+
C. TOTAL-REPLAY downloads the required Attack Data each time you execute or replay data during detection testing or development. To help reduce disk space usage, the tool generates a cached .yml file for every downloaded dataset. You can then use the `local_data_path` parameter to replay the cached data, allowing you to avoid downloading the same Attack Data again.
0 commit comments