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
{{ message }}
Repository navigation
Commit ae75181
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: packages/auditd_manager/_dev/build/docs/README.md
+3-20Lines changed: 3 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,21 +5,11 @@ is a part of the Linux kernel.
5
5
6
6
This integration is available only for Linux.
7
7
8
-
## Session View powered by Auditd Manager
8
+
## Session View powered by Auditd Manager[BETA]
9
9
10
-
The Auditd Manager is one of the integrations that can power the [Session View](https://www.elastic.co/guide/en/security/current/session-view.html) utility for the Elastic Security Platform. This feature provides a visual representation of session and process execution data, organized according to the Linux process model to help you investigate process, user, and service activity on your Linux infrastructure.
10
+
The `add_session_metadata` processor for Auditd Manager powers the [Session View](https://www.elastic.co/guide/en/security/current/session-view.html) utility for the Elastic Security Platform.
11
11
12
-
### Enabling Session Data Capture
13
-
14
-
There are two ways to enable session data capture for the Session View feature:
15
-
16
-
#### Method 1: Using the Toggle Switch (Recommended)
17
-
18
-
1. Navigate to the Auditd Manager integration configuration in Kibana.
19
-
2. Locate the "Session data" toggle switch.
20
-
3. Turn the switch on to enable session data capture.
21
-
22
-
#### Method 2: Manual Configuration
12
+
To enable the `add_session_metadata` processor for Auditd Manager:
23
13
24
14
1. Navigate to the Auditd Manager integration configuration in Kibana.
25
15
2. Add the `add_session_metadata` processor configuration under the **Processors** section of Advanced options.
@@ -39,13 +29,6 @@ There are two ways to enable session data capture for the Session View feature:
39
29
40
30
Changes are applied automatically, and you do not have to restart the service.
41
31
42
-
### Important Notes
43
-
44
-
- Using the toggle switch (Method 1) automatically applies these configurations, making it the simpler option for most users.
45
-
- When enabling session data capture, be aware that it will collect extended process data, which may have privacy and storage implications.
46
-
- You can disable session data capture at any time by turning off the toggle switch or removing the manual configurations.
47
-
- If you switch between methods or disable the feature, ensure that any conflicting configurations are removed to avoid unexpected behaviour.
48
-
49
32
## How it works
50
33
51
34
This integration establishes a subscription to the kernel to receive the events
Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata.
192
179
This executes in the agent before the logs are parsed. See [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.
193
-
- name: session_data_processors
194
-
type: yaml
195
-
title: Session data processors
196
-
required: false
197
-
show_user: false
198
-
multi: false
199
-
description: |
200
-
These processors will be appended to the processors configuration if Session Data is enabled.
Copy file name to clipboardExpand all lines: packages/auditd_manager/docs/README.md
+3-20Lines changed: 3 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,21 +5,11 @@ is a part of the Linux kernel.
5
5
6
6
This integration is available only for Linux.
7
7
8
-
## Session View powered by Auditd Manager
8
+
## Session View powered by Auditd Manager[BETA]
9
9
10
-
The Auditd Manager is one of the integrations that can power the [Session View](https://www.elastic.co/guide/en/security/current/session-view.html) utility for the Elastic Security Platform. This feature provides a visual representation of session and process execution data, organized according to the Linux process model to help you investigate process, user, and service activity on your Linux infrastructure.
10
+
The `add_session_metadata` processor for Auditd Manager powers the [Session View](https://www.elastic.co/guide/en/security/current/session-view.html) utility for the Elastic Security Platform.
11
11
12
-
### Enabling Session Data Capture
13
-
14
-
There are two ways to enable session data capture for the Session View feature:
15
-
16
-
#### Method 1: Using the Toggle Switch (Recommended)
17
-
18
-
1. Navigate to the Auditd Manager integration configuration in Kibana.
19
-
2. Locate the "Session data" toggle switch.
20
-
3. Turn the switch on to enable session data capture.
21
-
22
-
#### Method 2: Manual Configuration
12
+
To enable the `add_session_metadata` processor for Auditd Manager:
23
13
24
14
1. Navigate to the Auditd Manager integration configuration in Kibana.
25
15
2. Add the `add_session_metadata` processor configuration under the **Processors** section of Advanced options.
@@ -39,13 +29,6 @@ There are two ways to enable session data capture for the Session View feature:
39
29
40
30
Changes are applied automatically, and you do not have to restart the service.
41
31
42
-
### Important Notes
43
-
44
-
- Using the toggle switch (Method 1) automatically applies these configurations, making it the simpler option for most users.
45
-
- When enabling session data capture, be aware that it will collect extended process data, which may have privacy and storage implications.
46
-
- You can disable session data capture at any time by turning off the toggle switch or removing the manual configurations.
47
-
- If you switch between methods or disable the feature, ensure that any conflicting configurations are removed to avoid unexpected behaviour.
48
-
49
32
## How it works
50
33
51
34
This integration establishes a subscription to the kernel to receive the events
0 commit comments