|
1 | 1 | [[endpoint-data-volume]] |
2 | | -= Configure {elastic-endpoint}'s data volume |
| 2 | += Configure data volume for {elastic-endpoint} |
3 | 3 | ++++ |
4 | 4 | <titleabbrev>Configure data volume</titleabbrev> |
5 | 5 | ++++ |
6 | 6 |
|
| 7 | +{elastic-endpoint}, the installed component that performs {elastic-defend}'s threat monitoring and prevention, is optimized to reduce data volume and CPU usage. You can disable or modify some of these optimizations by reconfiguring the following <<adv-policy-settings,advanced settings>> in the {elastic-defend} integration policy. |
7 | 8 |
|
8 | | -[sidebar] |
9 | | --- |
10 | | -[.text-center] |
11 | | -**This is a placeholder for future documentation.** |
12 | | --- |
| 9 | +IMPORTANT: Modifying these advanced settings from their defaults will increase the volume of data that {elastic-endpoint} processes and ingests, and increase {elastic-endpoint}'s CPU usage. Make sure you're aware of how these changes will affect your storage capabilities and performance. |
| 10 | + |
| 11 | +Each setting has several OS-specific variants, represented by `[linux|mac|windows]` in the names listed below. Use the variant relevant to your hosts' operating system (for example, `windows.advanced.events.deduplicate_network_events` to configure network event deduplication for Windows hosts). |
| 12 | + |
| 13 | +[discrete] |
| 14 | +[[network-event-deduplication]] |
| 15 | +== Network event deduplication |
| 16 | + |
| 17 | +added:[8.15] When repeated network connections are detected from the same process, {elastic-endpoint} will not produce network events for subsequent connections. To disable or reduce deduplication of network events, use these advanced settings: |
| 18 | + |
| 19 | +`[linux|mac|windows].advanced.events.deduplicate_network_events`:: Enter `false` to completely disable network event deduplication. Default: `true` |
| 20 | + |
| 21 | +`[linux|mac|windows].advanced.events.deduplicate_network_events_below_bytes`:: Enter a transfer size threshold (in bytes) for events you want to deduplicate. Connections below the threshold are deduplicated, and connections above it are not deduplicated. This allows you to suppress repeated connections for smaller data transfers but always generate events for larger transfers. Default: `1048576` (1MB) |
| 22 | + |
| 23 | +[discrete] |
| 24 | +[[host-fields]] |
| 25 | +== Data in `host.*` fields |
| 26 | + |
| 27 | +added:[8.18] {elastic-endpoint} includes only a small subset of the data in the `host.*` fieldset in event documents. Full `host.*` information is still included in documents written to the `metrics-*` index pattern and in {elastic-endpoint} alerts. To override this behavior and include all `host.*` data for events, use this advanced setting: |
| 28 | + |
| 29 | +`[linux|mac|windows].advanced.set_extended_host_information`:: Enter `true` to include all `host.*` event data. Default: `false` |
| 30 | + |
| 31 | +NOTE: Users should take note of how a lack of some `host.*` information may affect their <<event-filters,event filters>> or <<endpoint-rule-exceptions,Endpoint alert exceptions>>. |
| 32 | + |
| 33 | +[discrete] |
| 34 | +[[merged-process-network]] |
| 35 | +== Merged process and network events |
| 36 | + |
| 37 | +added:[8.18] {elastic-endpoint} merges process `create`/`terminate` events (Windows) and `fork`/`exec`/`end` events (macOS/Linux) when possible. This means short-lived processes only generate a single event containing the details from when the process terminated. {elastic-endpoint} also merges network `connection/termination` events (Windows/macOS/Linux) when possible for short-lived connections. To disable this behavior, use these advanced settings: |
| 38 | + |
| 39 | + |
| 40 | +`[linux|mac|windows].advanced.events.aggregate_process`:: Enter `false` to disable merging of process events. Default: `true` |
| 41 | + |
| 42 | +`[linux|mac|windows].advanced.events.aggregate_network`:: Enter `false` to disable merging of network events. Default: `true` |
| 43 | + |
| 44 | +NOTE: Merged events can affect the results of <<event-filters,event filters>>. Notably, for merged events, `event.action` is an array containing all actions merged into the single event, such as `event.action=[fork, exec, end]`. In that example, if your event filter omits all fork events (`event.action : fork`), it will also filter out all merged events that include a `fork` action. To prevent such issues, you'll need to modify your event filters accordingly, or set the `[linux|mac|windows].advanced.events.aggregate_process` and `[linux|mac|windows].advanced.events.aggregate_network` advanced settings to `false` to prevent {elastic-endpoint} from merging events. |
| 45 | + |
| 46 | +[discrete] |
| 47 | +[[md5-sha1-hashes]] |
| 48 | +== MD5 and SHA-1 hashes |
| 49 | + |
| 50 | +added:[8.18] {elastic-endpoint} does not report MD5 and SHA-1 hashes in event data by default. These will still be reported if any <<trusted-apps-ov,trusted applications>>, <<blocklist,blocklist entries>>, <<event-filters,event filters>>, or <<endpoint-rule-exceptions,Endpoint exceptions>> require them. To include these hashes in all event data, use these advanced settings: |
| 51 | + |
| 52 | +`[linux|mac|windows].advanced.events.hash.md5`:: Enter `true` to compute and include MD5 hashes for processes and libraries in events. Default: `false` |
| 53 | + |
| 54 | +`[linux|mac|windows].advanced.events.hash.sha1`:: Enter `true` to compute and include SHA-1 hashes for processes and libraries in events. Default: `false` |
| 55 | + |
| 56 | +`[linux|mac|windows].advanced.alerts.hash.md5`:: Enter `true` to compute and include MD5 hashes for processes and libraries in alerts. Default: `false` |
| 57 | + |
| 58 | +`[linux|mac|windows].advanced.alerts.hash.sha1`:: Enter `true` to compute and include SHA-1 hashes for processes and libraries in alerts. Default: `false` |
0 commit comments