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
- Add Slack responder to sync created channels into task [\#1384](https://github.com/TheHive-Project/Cortex-Analyzers/pull/1384) ([nusantara-self](https://github.com/nusantara-self))
11
+
- CI - Add trivy scans & manual full rebuild [\#1383](https://github.com/TheHive-Project/Cortex-Analyzers/pull/1383) ([nusantara-self](https://github.com/nusantara-self))
- Proofpoint - Fix a typo in folder and neurons name [\#1381](https://github.com/TheHive-Project/Cortex-Analyzers/pull/1381) ([nusantara-self](https://github.com/nusantara-self))
11
22
- CI - Build Improvements [\#1380](https://github.com/TheHive-Project/Cortex-Analyzers/pull/1380) ([nusantara-self](https://github.com/nusantara-self))
23
+
- Add CIRCL AIL Onion-Lookup Analyzer [\#1379](https://github.com/TheHive-Project/Cortex-Analyzers/pull/1379) ([nusantara-self](https://github.com/nusantara-self))
Copy file name to clipboardExpand all lines: responders/Velociraptor/README.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,21 @@
2
2
This responder can be used to run a flow for a Velociraptor artifact. This could include gathering data, or performing initial response, as the artifact (or artifact "pack") could encompass any number of actions. The responder can be run on an observable type of `ip`, `fqdn`, or `other`, and will look for a matching client via the Velociraptor server. If a client match is found for the last seen IP, or the hostname, the responder will kick off the flow, the results will be returned, and the client ID will be added as a tag to the case and the observable.
3
3
4
4
#### Requirements
5
-
The following options are required in the Velociraptor Responder configuration:
6
-
7
-
-`velociraptor_client_config`: The path to the Velociraptor API client config.
8
-
(See the following for generating an API client config: https://www.velocidex.com/docs/user-interface/api/, and ensure the appropriate ACLs are granted to the API user).
9
-
-`velociraptor_artifact`: The name artifact you which to collect (as you would see it in the Velociraptor GUI).
10
-
-`upload_flow_results`: Upload flow results to TheHive case (bool).
11
-
-`thehive_url`: URL of your TheHive installation (e.g. 'http://127.0.0.1:9000').
12
-
-`thehive_apikey`: TheHive API key used to add flow results/file(s) to a case.
5
+
The following options are required in the Velociraptor Responder configuration:
6
+
7
+
**API Client Configuration** (choose one):
8
+
-`velociraptor_client_config`: The path to the Velociraptor API client config file.
9
+
-`velociraptor_client_config_content_base64`: Base64-encoded API client config (recommended for SaaS/containerized deployments).
10
+
11
+
To generate an API client config, see: https://www.velocidex.com/docs/user-interface/api/
12
+
Ensure the appropriate ACLs are granted to the API user.
13
+
14
+
For SaaS deployments, encode your API client config:
15
+
```bash
16
+
cat api_client.yaml | base64
17
+
```
18
+
Then paste the output into the `velociraptor_client_config_content_base64` parameter.
19
+
20
+
**Other Parameters**:
21
+
-`velociraptor_artifact`: The name of the artifact you wish to collect (as you would see it in the Velociraptor GUI). **Required**.
22
+
-`query_max_duration`: Max query duration in seconds (default: 600). **Optional**.
0 commit comments