Skip to content

Commit 0cdda0b

Browse files
Session view
1 parent dc6ca27 commit 0cdda0b

File tree

4 files changed

+6
-144
lines changed

4 files changed

+6
-144
lines changed

raw-migrated-files/docs-content/serverless/security-session-view.md

Lines changed: 0 additions & 127 deletions
This file was deleted.

solutions/security/investigate/session-view.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -4,23 +4,12 @@ mapped_urls:
44
- https://www.elastic.co/guide/en/serverless/current/security-session-view.html
55
---
66

7-
# Session view
8-
9-
% What needs to be done: Align serverless/stateful
10-
11-
% Use migrated content from existing pages that map to this page:
12-
13-
% - [x] ./raw-migrated-files/security-docs/security/session-view.md
14-
% - [ ] ./raw-migrated-files/docs-content/serverless/security-session-view.md
15-
16-
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
17-
18-
$$$enable-session-view$$$
7+
# Session View [security-session-view]
198

209
Session View is an investigation tool that allows you to examine Linux process data organized in a tree-like structure according to the Linux logical event model, with processes organized by parentage and time of execution. It displays events in a highly readable format that is inspired by the terminal. This makes it a powerful tool for monitoring and investigating session activity on your Linux infrastructure and understanding user and service behavior.
2110

2211
::::{admonition} Requirements
23-
* Session View requires an [Enterprise subscription](https://www.elastic.co/pricing).
12+
* In {{stack}}, Session View requires an [Enterprise subscription](https://www.elastic.co/pricing).
2413

2514
::::
2615

@@ -56,7 +45,7 @@ Session View can only display data that was collected by {{elastic-defend}} when
5645

5746
## Open Session View [open-session-view]
5847

59-
Session View is accessible from the **Hosts**, **Alerts***, and ***Timelines** pages, as well as the alert details flyout and the **Kubernetes** dashboard. Events and sessions that you can investigate in Session View have a rectangular **Open Session View** button in the **Actions** column. For example:
48+
Session View is accessible from the **Hosts**, **Alerts**, and **Timelines** pages, as well as the alert details flyout and the **Kubernetes** dashboard. Events and sessions that you can investigate in Session View have a rectangular **Open Session View** button in the **Actions** column. For example:
6049

6150
* On the Alerts page, scroll down to view the Alerts table. Look for alerts that have the **Open Session View** button in the **Actions** column:
6251

solutions/security/investigate/timeline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -223,7 +223,7 @@ From the **Correlation** tab, you can also do the following:
223223
## Use {{esql}} to investigate events [esql-in-timeline]
224224

225225
::::{note}
226-
{{esql}} is enabled by default in {{stack}} 9.0.0+. It can be disabled using the `enableESQL` setting from the [Advanced Settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html). This will hide the {{esql}} user interface from various applications. However, users will be able to access existing {{esql}} artifacts like saved searches and visualizations.
226+
{{esql}} is enabled by default in {{stack}}. It can be disabled using the `enableESQL` setting from the [Advanced Settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html). This will hide the {{esql}} user interface from various applications. However, users will be able to access existing {{esql}} artifacts like saved searches and visualizations.
227227
::::
228228

229229

solutions/security/investigate/visual-event-analyzer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ mapped_urls:
99
{{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. Examining 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.
1010

1111
::::{tip}
12-
If you’re on {{stack}} 9.0.0+ amd experiencing performance degradation, you can [exclude cold and frozen tier data](/solutions/security/get-started/configure-advanced-settings.md#exclude-cold-frozen-tiers) from analyzer queries.
12+
If you’re on {{stack}} and experiencing performance degradation, you can [exclude cold and frozen tier data](/solutions/security/get-started/configure-advanced-settings.md#exclude-cold-frozen-tiers) from analyzer queries.
1313
::::
1414

1515

@@ -168,7 +168,7 @@ When you select an `event.category` pill, all the events within that category ar
168168

169169
::::{note}
170170
- There is no limit to the number of events that can be associated with a process.
171-
- In {{stack}} 9.0.0+, you need a [Platinum or Enterprise subscription](https://www.elastic.co/pricing) to examine alerts associated with events.
171+
- In {{stack}}, you need a [Platinum or Enterprise subscription](https://www.elastic.co/pricing) to examine alerts associated with events.
172172
::::
173173

174174

0 commit comments

Comments
 (0)