Skip to content

Commit d5df044

Browse files
endpoint updates
1 parent ebe3e41 commit d5df044

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

release-notes/elastic-security/index.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,10 +140,17 @@ To check for security updates, go to [Security announcements for the Elastic sta
140140

141141
### Features and enhancements [elastic-security-9.0.5-features-enhancements]
142142
* Adds the `detection_rule_upgrade_status` object to snapshot telemetry schema [#223086]({{kib-pull}}223086).
143-
* To help identify which parts of `elastic-endpoint.exe` are using a significant amount of CPU, {{elastic-defend}} on Windows can now include CPU profiling data in diagnostics. To request CPU profiling data using the command line, refer to [{{agent}} command reference](/reference/fleet/agent-command-reference.md#_options). To request CPU profiling data using {{kib}}, check the **Collect additional CPU metrics** box when requesting {{agent}} diagnostics.
143+
* Reduces {{elastic-defend}} CPU when processing events from the System process on Windows.
144+
* Allows {{elastic-defend}} to automatically recover in some situations when it loses connectivity with {{agent}}.
145+
* Shortens the time it takes {{elastic-defend}} to recover from a `DEGRADED` status caused by communication issues with {{agent}}.
146+
* Due to an issue in macOS, {{elastic-defend}} would sometimes send network events without `user.name` populated. {{elastic-defend}} will now identify these events and populate `user.name` if necessary.
147+
* Reduces {{elastic-defend}} CPU usage for ETW events, API events, and Behavioral Protections. In some cases, this may be a significant reduction.
148+
144149

145150
### Fixes [elastic-security-9.0.5-fixes]
146151
* Fixes a bug where Security AI Assistant settings landed on the wrong page for users on the Basic license [#229163]({{kib-pull}}229163).
152+
* Fixes an issue in {{elastic-defend}} performance metrics that resulted in `endpoint_uptime_percent` always being 0 for behavioral rules.
153+
* Fixes an issue in {{elastic-defend}} that could result in a crash if a {{ls}} output configuration is specified containing a certificate that cannot not be parsed.
147154

148155
## 9.0.4 [elastic-security-9.0.4-release-notes]
149156

0 commit comments

Comments
 (0)