[Security] 8.18.3 release notes

Author: natasha-moore-elastic

docs/release-notes.asciidoc

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

docs/release-notes/8.18.asciidoc

@@ -1,6 +1,24 @@
 [[release-notes-header-8.18.0]]
 == 8.18
 
+[discrete]
+[[release-notes-8.18.3]]
+=== 8.18.3
+
+[discrete]
+[[enhancements-8.18.3]]
+==== Enhancements
+* Adds `dns` event collection for macOS for {elastic-defend} ({kibana-pull}223566[#223566]).
+* Adds pricing information about Elastic Managed LLM in AI Assistant and Attack Discovery tours and callouts ({kibana-pull}221566[#221566]).
+
+[discrete]
+[[bug-fixes-8.18.3]]
+==== Fixes
+* Fixes a bug where OSS models didn't work when streaming was ON ({kibana-pull}224129[#224129]).
+* Fixes a bug where cell actions didn't work when opening a timeline from specific rules ({kibana-pull}223302[#223302]).
+* Fixes an issue where the entity risk score feature stopped persisting risk score documents ({kibana-pull}221937[#221937]).
+* Fixes rule upgrade Threat Match mapping components overflowing on small screens ({kibana-pull}218628[#218628]).
+
 [discrete]
 [[release-notes-8.18.2]]
 === 8.18.2
@@ -48,6 +66,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin
 
 After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. 
 
+*Resolved* +
+This issue is fixed in {stack} version 8.18.3.
+
 ====
 // end::known-issue[]
 
@@ -108,6 +129,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin
 
 After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. 
 
+*Resolved* +
+This issue is fixed in {stack} version 8.18.3.
+
 ====
 // end::known-issue[]
 
@@ -189,6 +213,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin
 
 After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. 
 
+*Resolved* +
+This issue is fixed in {stack} version 8.18.3.
+
 ====
 // end::known-issue[]