Skip to content
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

[Security Solution] Add known issue for date selection in Protection Updates #4228

Merged
merged 2 commits into from
Nov 9, 2023
Merged

[Security Solution] Add known issue for date selection in Protection Updates #4228

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
742c447
[Security Solution] Add known issue for date selection in Protection …
kevinlog Nov 8, 2023
c731a91
Update docs/release-notes/8.11.asciidoc
kevinlog Nov 9, 2023
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/8.11.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@
* MITRE ATT&CK® technique cells show duplicate rules ({issue}167929[#167929]).
* MITRE ATT&CK® tactic cells show an incorrect rule count ({issue}167930[#167930]).
* An incorrect MITRE ATT&CK® sub-technique is applied after you save a rule ({issue}170347[#170347]).
* When using {elastic-defend}'s protection updates feature, if you turn off automatic updates and select the current day as your deployed artifacts version, it's possible that the set of protections has not been released for that day yet. As a result, {agent} could fail to download the artifacts and be set to an Unhealthy state. To avoid this issue, pick a date previous to the current one ({issue}170847[#170847]).

[discrete]
[[breaking-changes-8.11.0]]
Expand Down