Skip to content

Commit a07a628

Browse files
[DOCS] Event analyzer available by default for events that can be analyzed (#1197) (#1366)
* Image and step updates. * Removed grammarly icon in search bar * Updated color theme for all screenshots * Changed gif to png. * Adding Janeen's feedback. * Adding additional notes from Janeen. * Inserted image Janeen created. * Updating screenshots * Moderate adjustments for clarity. * Small edits. * Small fixes. Co-authored-by: Janeen Mikell-Straughn <[email protected]> Co-authored-by: Janeen Mikell-Straughn <[email protected]> (cherry picked from commit bd465b7) Co-authored-by: nastasha-solomon <[email protected]>
1 parent 80d946d commit a07a628

14 files changed

+29
-23
lines changed
Loading
Loading
-2.09 KB
Loading
-295 KB
Binary file not shown.
161 KB
Loading
239 KB
Loading

docs/detections/images/event-type.png

265 KB
Loading
49.4 KB
Loading
313 KB
Loading
125 KB
Loading
334 KB
Loading
221 KB
Loading
304 KB
Loading

docs/detections/visual-event-analyzer.asciidoc

Lines changed: 29 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -2,46 +2,52 @@
22
[role="xpack"]
33
== Visual event analyzer
44

5-
Elastic Security allows any event detected by Elastic Endpoint to be analyzed using a process-based visual analyzer. This enables security analysts to drill down into all related hosts, processes, and other events to aid in their investigations.
5+
{elastic-sec} allows any event detected by {elastic-endpoint} to be analyzed using a process-based visual analyzer, which shows a graphical timeline of processes that led up to the alert and the events that occurred immediately after. Viewing events in the visual event analyzer is useful to determine the origin of potentially malicious activity and other areas in your environment that may be compromised. It also enables security analysts to drill down into all related hosts, processes, and other events to aid in their investigations.
66

77
[float]
88
[[find-events-analyze]]
99
=== Find events to analyze
1010

11-
You can only visualize events triggered by hosts configured with the Elastic Endpoint Security Integration or any sysmon data from `winlogbeat`.
11+
You can only visualize events triggered by hosts configured with the {endpoint-sec} integration or any `sysmon` data from `winlogbeat`.
1212

1313
In KQL, this translates to any event with the `agent.type` set to either:
1414

1515
* `endpoint`
1616
* `winlogbeat` with `event.module` set to `sysmon`
1717

18-
To access events that can be visually analyzed:
18+
To find events that can be visually analyzed:
1919

20-
1. Select *Explore* -> *Hosts* -> *Events*. A list of all your hosts' events appears at the bottom of the Hosts page.
21-
22-
2. Create a KQL query that filters all `endpoint` detected events by entering either `agent.type:"endpoint" and process.entity_id : *` or `agent.type:"winlogbeat" and event.module: "sysmon" and process.entity_id : *` into the KQL search bar, and then selecting **Update**.
20+
. First, view a list of events by doing one of the following:
21+
* Go to *Explore* -> *Hosts*, then select the *Events* tab. A list of all your hosts' events appears at the bottom of the page.
22+
* Go to *Detect* -> *Alerts*, then scroll down to view the Alerts table.
23+
. Filter events that can be visually analyzed by entering either of the following queries in the KQL search bar, then selecting *Enter*:
24+
** `agent.type:"endpoint" and process.entity_id :*`
25+
+
26+
Or
27+
+
28+
** `agent.type:"winlogbeat" and event.module: "sysmon" and process.entity_id : *`
2329
+
2430
[role="screenshot"]
25-
image::images/kql-agent-type.png[]
31+
image::images/analyzer_KQL_query.png[]
32+
33+
. 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.
2634

27-
3. For the event that you want to analyze, click the **More actions** button and select **Analyze event**. The visual analyzer view appears.
28-
+
2935
[role="screenshot"]
30-
image::images/analyze-event.gif[Shows analyze event option]
31-
+
32-
NOTE: Events that cannot be analyzed will not have the **More actions** -> **Analyze event** option available. This might happen if the event has incompatible field mappings.
33-
+
36+
image::images/analyze-event-button.png[Shows analyze event option]
37+
38+
NOTE: Events that cannot be analyzed will not have the **Analyze event** option available. This might occur if the event has incompatible field mappings.
39+
3440
[role="screenshot"]
35-
image::images/analyze-event-view.png[]
36-
+
41+
image::images/analyze-event-timeline.png[]
42+
3743
TIP: You can also analyze events from <<timelines-ui,Timelines>>.
3844

3945

4046
[discrete]
4147
[[visual-analyzer-ui]]
4248
=== Visual event analyzer UI
4349

44-
Inside the visual analyzer, each cube represents a process (e.g. an executable file or network event). Click and drag in timeline view to see all process relationships.
50+
Within the visual analyzer, each cube represents a process, such as an executable file or network event. Click and drag in the analyzer to see the hierarchy of all process relationships.
4551

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

@@ -62,22 +68,22 @@ To expand the analyzer to a full screen, select the **Full Screen** icon above t
6268
[role="screenshot"]
6369
image::images/full-screen-analyzer.png[]
6470

65-
The left panel contains a list of all processes related to the event, starting with the event chain's first process. **Analyzed Events**, as in the event you selected to analyze from either the events list or your timeline, are highlighted by a light blue outline around the cube.
71+
The left panel contains a list of all processes related to the event, starting with the event chain's first process. **Analyzed Events** -- the event you selected to analyze from the events list or Timeline -- are highlighted with a light blue outline around the cube.
6672

6773
[role="screenshot"]
6874
image::images/process-list.png[]
6975

7076
In the graphical view, you can:
7177

72-
- Zoom in and out of the graphical view using the slider to the right of the timeline
78+
- Zoom in and out of the graphical view using the slider on the far right
7379
- Click and drag around the graphical view to more process relationships
74-
- See the time passed between each process
80+
- See child process events that spawned from the parent process
81+
- See how much time passed between each process
7582
- See all events related to each process
7683

7784
[role="screenshot"]
7885
image::images/graphical-view.png[]
7986

80-
8187
[discrete]
8288
[[process-and-event-details]]
8389
=== Process and event details
@@ -98,14 +104,14 @@ When you first select a process, it appears in a loading state. If loading data
98104

99105
See event details by selecting that event's URL at the top of the process details view or choosing one of the event pills in the graphical view.
100106

101-
Events are categorized based on their `event.category`.
107+
Events are categorized based on the `event.category` value.
102108

103109
[role="screenshot"]
104110
image::images/event-type.png[]
105111

106-
When you select an `event.category`, pill, all the events within that category are listed in the left panel. To view more details about a specific event, select it from the list.
112+
When you select an `event.category` pill, all the events within that category are listed in the left panel. To view more details about a specific event, select it from the list.
107113

108114
[role="screenshot"]
109115
image::images/event-details.png[]
110116

111-
NOTE: In {stack} version >= 7.10.0, there is no limit to the number of events that can be associated with a process. However, in {stack} minor versions < = 7.9.0, each process is limited to only 100 events.
117+
NOTE: In {stack} versions 7.10.0 and newer, there is no limit to the number of events that can be associated with a process. However, in {stack} versions 7.9.0 and earlier, each process is limited to only 100 events.

0 commit comments

Comments
 (0)