@@ -72,15 +72,16 @@ You can check out sample CSV and manually edited XLSX timeline results [here](ht
72
72
* JSON support for sending alerts to Elastic Stack/Splunk, etc...
73
73
74
74
# Downloads
75
- You can ` git clone ` the repository with the following command:
75
+ You can download the latest Hayabusa version from the [ Releases] ( https://github.com/Yamato-Security/hayabusa/releases ) page.
76
+
77
+ You can also ` git clone ` the repository with the following command and compile binary from source code.:
76
78
77
79
``` bash
78
80
git clone https://github.com/Yamato-Security/hayabusa.git
79
81
```
80
82
81
- You can also manually download and extract Hayabusa from [ https://github.com/Yamato-Security/hayabusa ] ( https://github.com/Yamato-Security/hayabusa ) .
82
-
83
- After that, you need to download a pre-compiled binary for the Windows, Linux or macOS at the [ Releases] ( https://github.com/Yamato-Security/hayabusa/releases ) page and save it to the ` hayabusa ` root folder.
83
+ There are two different versions of the evtx library being used when compiled: ` 0.6.7 ` and ` 0.7.2 ` .
84
+ The ` 0.7.2 ` version should work but we have only tested it with ` 0.6.7 ` so please use that version if you experience any problems with ` 0.7.2 ` .
84
85
85
86
# Compiling from source (Optional)
86
87
If you have rust installed, you can compile from source with the following command:
@@ -110,13 +111,7 @@ git clone https://github.com/Yamato-Security/hayabusa-sample-evtx.git
110
111
> Note: You need to run the binary from the Hayabusa root directory.
111
112
112
113
# Usage
113
- You need to run the binary from the Hayabusa root directory.
114
- There are different binary versions in ` .\bin ` compiled for different operating systems and architectures.
115
- Also, there are two different versions of the evtx library being used when compiled: ` 0.6.7 ` and ` 0.7.2 ` .
116
- The ` 0.7.2 ` version should work but we have only tested it with ` 0.6.7 ` so please use that if you experience any problems with ` 0.7.2 ` .
117
- Please replace ` hayabusa.exe ` in the examples below with the appropriate Hayabusa binary filename.
118
-
119
- > Note: You need to run the Hayabusa binary from the Hayabusa root directory.
114
+ > Note: You need to run the Hayabusa binary from the Hayabusa root directory. Example: ` .\hayabusa.exe `
120
115
121
116
## Command line options
122
117
``` bash
@@ -144,62 +139,62 @@ USAGE:
144
139
## Usage examples
145
140
* Run hayabusa against one Windows event log file:
146
141
``` bash
147
- .\b in \ h ayabusa.exe -f eventlog.evtx
142
+ .\h ayabusa.exe -f eventlog.evtx
148
143
```
149
144
150
145
* Run hayabusa against the sample-evtx directory with multiple Windows event log files:
151
146
``` bash
152
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx
147
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx
153
148
```
154
149
155
150
* Export to a single CSV file for further analysis with excel or timeline explorer:
156
151
``` bash
157
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -o results.csv
152
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -o results.csv
158
153
```
159
154
160
155
* Only run hayabusa rules (the default is to run all the rules in ` -r .\rules ` ):
161
156
``` bash
162
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa -o results.csv
157
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa -o results.csv
163
158
```
164
159
165
160
* Only run hayabusa rules for logs that are enabled by default on Windows:
166
161
``` bash
167
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\d efault -o results.csv
162
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\d efault -o results.csv
168
163
```
169
164
170
165
* Only run hayabusa rules for sysmon logs:
171
166
``` bash
172
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\s ysmon -o results.csv
167
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\s ysmon -o results.csv
173
168
```
174
169
175
170
* Only run sigma rules:
176
171
``` bash
177
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\s igma -o results.csv
172
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\s igma -o results.csv
178
173
```
179
174
180
175
* Enable deprecated rules (those with ` status ` marked as ` deprecated ` ) and noisy rules (those whose rule ID is listed in ` .\config\noisy-rules.txt ` ):
181
176
``` bash
182
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx --enable-noisy-rules --enable-deprecated-rules -o results.csv
177
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx --enable-noisy-rules --enable-deprecated-rules -o results.csv
183
178
```
184
179
185
180
* Only run rules to analyze logons and output in the UTC timezone:
186
181
``` bash
187
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\d efault\e vents\S ecurity\L ogons -u -o results.csv
182
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -r .\r ules\h ayabusa\d efault\e vents\S ecurity\L ogons -u -o results.csv
188
183
```
189
184
190
185
* Run on a live Windows machine (requires Administrator privileges) and only detect alerts (potentially malicious behavior):
191
186
``` bash
192
- .\b in \ h ayabusa.exe -d C:\W indows\S ystem32\w inevt\L ogs -m low
187
+ .\h ayabusa.exe -d C:\W indows\S ystem32\w inevt\L ogs -m low
193
188
```
194
189
195
190
* Get event ID statistics:
196
191
``` bash
197
- .\b in \ h ayabusa.exe -f Security.evtx -s
192
+ .\h ayabusa.exe -f Security.evtx -s
198
193
```
199
194
200
195
* Print verbose information (useful for determining which files take long to process, parsing errors, etc...):
201
196
``` bash
202
- .\b in \ h ayabusa.exe -d .\h ayabusa-sample-evtx -v
197
+ .\h ayabusa.exe -d .\h ayabusa-sample-evtx -v
203
198
```
204
199
205
200
* Verbose output example:
0 commit comments