[8.18] 8.18.5 release notes (backport #7022) (#7026)

* 8.18.5 release notes (#7022)

* 8.18.5 release notes

* known issue resolved

* updates

* Update docs/release-notes/8.18.asciidoc

Co-authored-by: Gabriel Landau <[email protected]>

* Endpoint updates and RM note for 8.18.4

* apply suggestions

* tweak

---------

Co-authored-by: Gabriel Landau <[email protected]>
(cherry picked from commit f64c182)

# Conflicts:
#	docs/release-notes.asciidoc

* resolve conflict

* removes 8.19 links

---------

Co-authored-by: natasha-moore-elastic <[email protected]>
Co-authored-by: natasha-moore-elastic <[email protected]>

Author: mergify[bot]

docs/release-notes.asciidoc

@@ -3,6 +3,7 @@
 
 This section summarizes the changes in each release.
 
+* <<release-notes-8.18.5, {elastic-sec} version 8.18.5>>
 * <<release-notes-8.18.4, {elastic-sec} version 8.18.4>>
 * <<release-notes-8.18.3, {elastic-sec} version 8.18.3>>
 * <<release-notes-8.18.2, {elastic-sec} version 8.18.2>>

docs/release-notes/8.18.asciidoc

@@ -1,13 +1,36 @@
 [[release-notes-header-8.18.0]]
 == 8.18
 
+[discrete]
+[[release-notes-8.18.5]]
+=== 8.18.5
+
+[discrete]
+[[enhancements-8.18.5]]
+==== Enhancements
+* Adds the `detection_rule_upgrade_status` object to snapshot telemetry schema ({kibana-pull}223086[#223086]).
+* Reduces {elastic-defend} CPU usage when processing events from the System process on Windows.
+* Reduces {elastic-defend} CPU usage for ETW events, API events, and Behavioral Protections. In some cases, this may be a significant reduction.
+* Allows {elastic-defend} to automatically recover in some situations when it loses connectivity with {agent}.
+* Shortens the time it takes {elastic-defend} to recover from a `DEGRADED` status caused by communication issues with {agent}.
+* Improves {elastic-defend} malware scan queue efficiency on Windows by not blocking scan requests when an oplock for the file being scanned cannot be acquired.
+* 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.
+
+[discrete]
+[[bug-fixes-8.18.5]]
+==== Fixes
+* Improves UI copy for the "bulk update with conflicts" modal ({kibana-pull}227803[#227803]).
+* Fixes an issue where {elastic-defend} would fail to enable network events on Linux if IPv6 is not supported by the system.
+* Fixes an issue in {elastic-defend} that could result in a crash if a {ls} output configuration contains a certificate that cannot be parsed.
+
 [discrete]
 [[release-notes-8.18.4]]
 === 8.18.4
 
 [discrete]
 [[enhancements-8.18.4]]
 ==== Enhancements
+* Adds the `elastic_customized_total`, `elastic_noncustomized_total`, and `is_customized` fields to snapshot telemetry schema ({kibana-pull}222370[#222370]).
 * Improves logging of fatal exceptions in {elastic-defend}.
 * Allows {elastic-defend} users to control the maximum file size for malware protection using the `advanced.malware.max_file_size_bytes` advanced policy setting.
 
@@ -23,7 +46,6 @@
 * Refactors Timeline styling for improved consistency with design updates ({kibana-pull}222438[#222438]).
 * Fixes a bug where the **Rules**, **Alerts**, and **Fleet** pages would stall in air-gapped environments ({kibana-pull}220510[#220510]).
 * Fixes a bug where unmodified prebuilt rules installed before v8.18 didn't appear in the **Upgrade** table when the **Unmodified** filter was selected ({kibana-pull}227859[#227859]).
-* Improves UI copy for the "bulk update with conflicts" modal ({kibana-pull}227803[#227803]).
 * Fixes an issue in {elastic-defend} that may result in bugchecks (BSODs) on Windows systems with a very high volume of network connections.
 
 [discrete]
@@ -50,6 +72,10 @@ For more information, check https://github.com/elastic/endpoint/issues/90[#90]
 Upgrade to the fixed version: https://www.elastic.co/downloads/past-releases/elastic-agent-8-18-3+build202507101319[8.18.3+build202507101319].
 
 If you're unable to upgrade or downgrade, set the `advanced.kernel.network` advanced setting to `false` in your {elastic-defend} integration policy.
+
+*Resolved* +
+This issue is fixed in {stack} version 8.18.4.
+
 ====
 // end::known-issue[]