Skip to content

Commit ec8acd7

Browse files
Analyzer support for CrowdStrike and SentinelOne (#6989)
* Analyzer support for CrowdStrike and SentinelOne * update CS details
1 parent e0c3193 commit ec8acd7

File tree

1 file changed

+14
-7
lines changed

1 file changed

+14
-7
lines changed

docs/detections/visual-event-analyzer.asciidoc

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,24 +10,31 @@ TIP: If you're experiencing performance degradation, you can <<exclude-cold-froz
1010
[[find-events-analyze]]
1111
== Find events to analyze
1212

13-
You can only visualize events triggered by hosts configured with the {elastic-defend} integration or any `sysmon` data from `winlogbeat`.
13+
You can visualize events from the following sources:
1414

15-
In KQL, this translates to any event with the `agent.type` set to either:
15+
* {elastic-defend} integration
16+
* Sysmon data collected through {winlogbeat}
17+
* {integrations-docs}/crowdstrike[CrowdStrike integration] (Falcon logs collected through Event Stream or FDR)
18+
* {integrations-docs}/sentinel_one_cloud_funnel[SentinelOne Cloud Funnel integration]
19+
20+
21+
In KQL, this translates to any event with the `agent.type` set to:
1622

1723
* `endpoint`
1824
* `winlogbeat` with `event.module` set to `sysmon`
25+
* `filebeat` with `event.module` set to `crowdstrike`
26+
* `filebeat` with `event.module` set to `sentinel_one_cloud_funnel`
1927

2028
To find events that can be visually analyzed:
2129

2230
. First, display a list of events by doing one of the following:
2331
* Find **Hosts** in the main menu, or search for `Security/Explore/Hosts` by using the {kibana-ref}/introduction.html#kibana-navigation-search[global search field], then select the *Events* tab. A list of all your hosts' events appears at the bottom of the page.
2432
* Find **Alerts** in the main menu or by using the {kibana-ref}/introduction.html#kibana-navigation-search[global search field], then scroll down to the Alerts table.
25-
. Filter events that can be visually analyzed by entering either of the following queries in the KQL search bar, then selecting *Enter*:
33+
. Filter events that can be visually analyzed by entering one of the following queries in the KQL search bar, then selecting *Enter*:
2634
** `agent.type:"endpoint" and process.entity_id :*`
27-
+
28-
Or
29-
+
3035
** `agent.type:"winlogbeat" and event.module: "sysmon" and process.entity_id : *`
36+
** `agent.type:"filebeat" and event.module: "crowdstrike" and process.entity_id : *`
37+
** `agent.type:"filebeat" and event.module: "sentinel_one_cloud_funnel" and process.entity_id : *`
3138

3239
. Events that can be visually analyzed are denoted by a cubical **Analyze event** icon. Select this option to open the event in the visual analyzer. The event analyzer is accessible from the **Hosts**, **Alerts**, and **Timelines** pages, as well as the alert details flyout.
3340

@@ -53,7 +60,7 @@ Within the visual analyzer, each cube represents a process, such as an executabl
5360

5461
To understand what fields were used to create the process, select the **Process Tree** to show the schema that created the graphical view. The fields included are:
5562

56-
* `SOURCE`: Can be either `endpoint` or `winlogbeat`
63+
* `SOURCE`: Indicates the data source—for example, `endpoint` or `winlogbeat`
5764
* `ID`: Event field that uniquely identifies a node
5865
* `EDGE`: Event field which indicates the relationship between two nodes
5966

0 commit comments

Comments
 (0)