Skip to content

[Security] 8.18.3 release notes #6891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 8.x
Choose a base branch
from
Open

[Security] 8.18.3 release notes #6891

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b80c6d3
[Security] 8.18.3 release notes
natasha-moore-elastic Jun 18, 2025
185cbe2
Update docs/release-notes/8.18.asciidoc
natasha-moore-elastic Jun 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/release-notes.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>>
Expand Down
27 changes: 27 additions & 0 deletions docs/release-notes/8.18.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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]).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

possible revision
cc: @dplumlee

Suggested change
* Fixes rule upgrade Threat Match mapping components overflowing on small screens ({kibana-pull}218628[#218628]).
* Fixes overflow issues with the threat match mapping component when you viewed the rule upgrade flyout on a smaller screen ({kibana-pull}218628[#218628]).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably a better way to phrase it for release notes


[discrete]
[[release-notes-8.18.2]]
=== 8.18.2
Expand Down Expand Up @@ -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[]

Expand Down Expand Up @@ -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[]

Expand Down Expand Up @@ -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[]

Expand Down