From 742c44797470a6ada37f69d40effd15030227052 Mon Sep 17 00:00:00 2001 From: Kevin Logan Date: Wed, 8 Nov 2023 17:26:58 -0500 Subject: [PATCH 1/2] [Security Solution] Add known issue for date selection in Protection Updates --- docs/release-notes/8.11.asciidoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/release-notes/8.11.asciidoc b/docs/release-notes/8.11.asciidoc index 1283093e30..eabe342f5f 100644 --- a/docs/release-notes/8.11.asciidoc +++ b/docs/release-notes/8.11.asciidoc @@ -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 the Protection Updates feature, if you freeze the updates to the current day, it is possible that the set of protections has not been released for that day yet. As a result, the Agent could fail to download the artifacts and be set to an Unhealthy state. To workaround this issue, pick a date previous to the current one ({issue}170847[#170847]). [discrete] [[breaking-changes-8.11.0]] From c731a911138a9a6f7200f5344e576f311f1d6373 Mon Sep 17 00:00:00 2001 From: Kevin Logan <56395104+kevinlog@users.noreply.github.com> Date: Thu, 9 Nov 2023 11:31:04 -0500 Subject: [PATCH 2/2] Update docs/release-notes/8.11.asciidoc Co-authored-by: Joe Peeples --- docs/release-notes/8.11.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/8.11.asciidoc b/docs/release-notes/8.11.asciidoc index eabe342f5f..d4ea4d0341 100644 --- a/docs/release-notes/8.11.asciidoc +++ b/docs/release-notes/8.11.asciidoc @@ -11,7 +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 the Protection Updates feature, if you freeze the updates to the current day, it is possible that the set of protections has not been released for that day yet. As a result, the Agent could fail to download the artifacts and be set to an Unhealthy state. To workaround this issue, pick a date previous to the current one ({issue}170847[#170847]). +* 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]]