From 382785d92fc41c584ff8dc91458d17725620ed3a Mon Sep 17 00:00:00 2001 From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> Date: Wed, 20 Nov 2024 19:21:28 -0500 Subject: [PATCH 1/2] Remove known issue for AI Assistant from the 8.15.1-8.16.1 release notes (#6190) * First draft * Removes extra image (cherry picked from commit b1dec23d21f47c3088f734607c0725cc7dae189e) # Conflicts: # docs/release-notes/8.16.asciidoc --- docs/release-notes/8.15.asciidoc | 58 +-------- docs/release-notes/8.16.asciidoc | 216 +++++++++++++++++++++++++++++++ 2 files changed, 221 insertions(+), 53 deletions(-) create mode 100644 docs/release-notes/8.16.asciidoc diff --git a/docs/release-notes/8.15.asciidoc b/docs/release-notes/8.15.asciidoc index 0393936ee9..92f1462f2a 100644 --- a/docs/release-notes/8.15.asciidoc +++ b/docs/release-notes/8.15.asciidoc @@ -5,21 +5,6 @@ [[release-notes-8.15.4]] === 8.15.4 -[discrete] -[[known-issue-8.15.4]] -==== Known issues - -// tag::known-issue-189676[] -[discrete] -.Tags appear in Elastic AI Assistant's responses -[%collapsible] -==== -*Details* + -On August 1, 2024, it was discovered that Elastic AI Assistant's responses when using Bedrock Sonnet 3.5 may include `` tags, for example `` ({kibana-issue}189676[#189676]). - -==== -// end::known-issue-189676[] - [discrete] [[enhancements-8.15.4]] ==== Enhancements @@ -42,21 +27,6 @@ On August 1, 2024, it was discovered that Elastic AI Assistant's responses when [[release-notes-8.15.3]] === 8.15.3 -[discrete] -[[known-issue-8.15.3]] -==== Known issues - -// tag::known-issue-189676[] -[discrete] -.Tags appear in Elastic AI Assistant's responses -[%collapsible] -==== -*Details* + -On August 1, 2024, it was discovered that Elastic AI Assistant's responses when using Bedrock Sonnet 3.5 may include `` tags, for example `` ({kibana-issue}189676[#189676]). - -==== -// end::known-issue-189676[] - [discrete] [[bug-fixes-8.15.3]] ==== Bug fixes @@ -77,17 +47,6 @@ On August 1, 2024, it was discovered that Elastic AI Assistant's responses when [[known-issue-8.15.2]] ==== Known issues -// tag::known-issue-189676[] -[discrete] -.Tags appear in Elastic AI Assistant's responses -[%collapsible] -==== -*Details* + -On August 1, 2024, it was discovered that Elastic AI Assistant's responses when using Bedrock Sonnet 3.5 may include `` tags, for example `` ({kibana-issue}189676[#189676]). - -==== -// end::known-issue-189676[] - // tag::known-issue-192084[] [discrete] .Alerts wrongfully inherit previously-selected tags @@ -141,18 +100,6 @@ On October 17, 2024, this issue was resolved. [[known-issue-8.15.1]] ==== Known issues -// tag::known-issue-189676[] -[discrete] -.Tags appear in Elastic AI Assistant's responses -[%collapsible] -==== -*Details* + -On August 1, 2024, it was discovered that Elastic AI Assistant's responses when using Bedrock Sonnet 3.5 may include `` tags, for example `` ({kibana-issue}189676[#189676]). - - -==== -// end::known-issue-189676[] - // tag::known-issue-192084[] [discrete] .Alerts wrongfully inherit previously-selected tags @@ -222,6 +169,11 @@ On October 17, 2024, this issue was resolved. *Details* + On August 1, 2024, it was discovered that Elastic AI Assistant's responses when using Bedrock Sonnet 3.5 may include `` tags, for example `` ({kibana-issue}189676[#189676]). +*Workaround* + +Upgrade to 8.15.1. + +*Resolved* + +On September 5, 2024, this issue was resolved. ==== // end::known-issue-189676[] diff --git a/docs/release-notes/8.16.asciidoc b/docs/release-notes/8.16.asciidoc new file mode 100644 index 0000000000..68f7ce29b4 --- /dev/null +++ b/docs/release-notes/8.16.asciidoc @@ -0,0 +1,216 @@ +[[release-notes-header-8.16.0]] +== 8.16 + +[discrete] +[[known-issue-8.16.1]] +==== Known issues + +// tag::known-issue[] +[discrete] +.Duplicate alerts can be produced from manually running threshold rules +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. + +==== +// end::known-issue[] + +// tag::known-issue[] +[discrete] +.Manually running custom query rules with suppression could suppress more alerts than expected +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. + +==== +// end::known-issue[] + +[discrete] +[[release-notes-8.16.1]] +=== 8.16.1 + +[discrete] +[[bug-fixes-8.16.1]] +==== Bug fixes +* Fixes a bug that caused the **Alerts** page to crash if you upgraded to 8.16 and accessed the page in a non-default {kib} space ({kibana-pull}200058[#200058]). +* Fixes a bug that caused the Elastic AI Assistant Knowledge Base to fail if the current user had a colon (`:`) in their username and attempted to access Knowledge Base entries ({kibana-pull}200131[#200131]). +* Fixes a bug that made values unavailable for the Knowledge Base **Index** field, which lets you specify an index as a knowledge source ({kibana-pull}199990[#199990]). +* Fixes a bug that unset the `required_fields` field if you updated a rule by sending a `PATCH` request that didn't contain the `required_fields` field ({kibana-pull}199901[#199901]). +* Fixes an issue that prevented you from successfully importing TSV files with asset criticality data if you were on Windows ({kibana-pull}199791[#199791]). +* Fixes the entity store initialization error that was caused by risk engine failures. Now, when you upgrade to 8.16.1, or follow the standard flow for initializing the entity store, the risk engine no longer fails while deleting the component template. In addition, the index template will correctly reference the new component template, ensuring the successful initialization of the entity store ({kibana-pull}199734[#199734]). +* Improves the warning message that displays when asset criticality assignments are duplicated during the bulk assignment flow ({kibana-pull}199651[#199651]). +* Fixes a time skew bug that occurred when Linux virtual machines using eBPF event probes were suspended and then resumed. + +[discrete] +[[release-notes-8.16.0]] +=== 8.16.0 + +[discrete] +[[known-issue-8.16.0]] +==== Known issues + +// tag::known-issue[] +[discrete] +.Attempting to edit an Elastic AI Assistant Knowledge Base index results in an error +[%collapsible] +==== +*Details* + +Updating a Knowledge Base entry of type "index" results in an error. + +*Workaround* + + +Upgrade to 8.16.1. Alternatively, instead of updating an "index" entry, delete it and add it again with the desired changes. + +*Resolved* + +On November 21, 2024, this issue was resolved. + +==== +// end::known-issue[] + +// tag::known-issue[] +[discrete] +.Duplicate alerts can be produced from manually running threshold rules +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. + +==== +// end::known-issue[] + +// tag::known-issue[] +[discrete] +.Manually running custom query rules with suppression could suppress more alerts than expected +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. + +==== +// end::known-issue[] + +// tag::known-issue-53[] +[discrete] +.Alerts page crashes if you upgrade to 8.16 and access it in a non-default {kib} space +[%collapsible] +==== +*Details* + +On November 14, 2024, it was discovered that the **Alerts** page would crash and display an `Unable to load` error if you upgraded to 8.16 and accessed the page in a non-default {kib} space. + +*Workaround* + + +Upgrade to 8.16.1. + +Alternatively, manually edit your browser's local storage and refresh the **Alerts** page: + +NOTE: These instructions only apply to the Google Chrome browser. Modify the steps based on the browser you're using. + +. Right-click anywhere on the **Alerts** page, then select *Inspect* to open Chrome's Developer Tools. +. Go to *Application -> Storage*, then expand *Local Storage*. +. Click on the name of your Kibana instance, for example, http://localhost:1234. +. Search for the `siem..pageFilters` key, right-click on the value, then click *Delete*. If you have multiple non-default spaces, do this for each space. +. Refresh the **Alerts** page to reload it. + +*Resolved* + +On November 21, 2024, this issue was resolved. + +==== +// end::known-issue-53[] + +[discrete] +[[features-8.16.0]] +==== New features + +* Introduces Knowledge Base for Elastic AI Assistant, which allows you to specify information for AI Assistant to remember when responding to your queries ({kibana-pull}186566[#186566], {kibana-pull}192665[#192665]). +* Enables agentless deployment for Elastic's Cloud Security Posture Management integration and the new Cloud Asset Inventory integration ({kibana-pull}191557[#191557]). +* Enables data collected by the Wiz and AWS Security Hub integrations to appear on the Findings page and in entity details flyouts (https://github.com/elastic/integrations/pull/10790[#10790], https://github.com/elastic/integrations/pull/11158[#11158]). +* Enables alerts collected by the Falco integration to appear on the Alerts page (https://github.com/elastic/integrations/pull/9619[#9619], https://github.com/elastic/integrations/pull/11051[#11051]). +* Adds ability to manually run rules for a specified time period, either for testing purposes or to generate alerts for past events. +* Adds historical results to the Data Quality dashboard and updates its UI ({kibana-pull}191898[#191898], {kibana-pull}196127[#196127]). +* Adds the ability to attach notes to alerts and events and introduces the Notes page, which allows you to manage all existing notes ({kibana-pull}186787[#186787], {kibana-pull}186807[#186807], {kibana-pull}186931[#186931], {kibana-pull}186946[#186946], {kibana-pull}187214[#187214], {kibana-pull}193373[#193373]). +* Enables detection rules to automatically execute system actions, such as opening a case ({kibana-pull}183937[#183937]). +* Adds role-based access control (RBAC) for Elastic AI Assistant's knowledge base ({kibana-pull}195733[#195733]). +* Adds RBAC for Attack Discovery ({kibana-pull}188788[#188788]). +* Removes the `securitySolution:enableAssetCriticality` advanced setting and enables <> workflows by default ({kibana-pull}196270[#196270]). +* Introduces the entity store as a technical preview feature, which allows observed, imported, integrated, or uploaded entities to be stored persistently ({kibana-pull}192806[#192806]). +* Adds syntax validation for {esql} queries ({kibana-pull}189780[#189780]). +* Allows you to view {es} queries that run during rule execution. This option is provided for {esql} and EQL rules only ({kibana-pull}191107[#191107]). +* Allows you to create and update a rule even when some data-related validation errors are present in the query field ({kibana-pull}191487[#191487]). +* Introduces a new advanced setting, `securitySolution:enableVisualizationsInFlyout`. When enabled, you can examine alerts and events in the **Visualize** tab, which provides a more detailed view of the event analyzer and Session View ({kibana-pull}194012[#194012], {kibana-pull}192531[#192531], {kibana-pull}192643[#192643]). +* Creates a new advanced setting `securitySolution:excludedDataTiersForRuleExecution` that allows you to exclude cold and frozen data from rule executions ({kibana-pull}186908[#186908]). ++ +IMPORTANT: Even when the `excludedDataTiersForRuleExecution` advanced setting is enabled, indicator match, event correlation, and {esql} rules may still fail if a frozen or cold shard that matches the rule's specified index pattern is unavailable during rule executions. If failures occur, we recommend modifying the rule's index patterns to only match indices containing hot tier data. +* Enhances the Insights section of the alert and event details flyouts by providing available misconfiguration and vulnerabilities findings ({kibana-pull}195509[#195509]). +* Turns off the host field size reduction setting on {elastic-defend}'s integration policy by default. To turn it on, configure the `[os].advanced.set_extended_host_information` <>. +* Allows you to reduce CPU usage, I/O, and event sizes by turning on process event aggregation when configuring your {elastic-defend} integration policy. Related process events that occur in rapid succession are combined into fewer aggregate events. To turn on process event aggregation, configure the `advanced.events.aggregate_process` <>. +* Allows you to reduce CPU usage, I/O, and event sizes by turning off MD5, SHA-1, and SHA-256 hashes in events when configuring your {elastic-defend} integration policy. Example fields include `process.hash.md5` and `file.hash.sha1`. +* Allows you to configure your {elastic-defend} integration policy to collect SHA-256 file hashes in file events. Before doing so, consider the following caveats: +** This can greatly increase {elastic-defend}'s CPU and I/O utilization and impact system responsiveness. +** This can significantly delay event enrichment and lead to Behavioral Protection rules firing too late to effectively stop malicious behavior. +** This can cause event processing queues to overflow and lead to dropped events. +** Many file events won't contain hashes. Hash collection is the best effort and is not guaranteed to be present in every event. Hashes are collected asynchronously and shortly after the file activity. Hashes might be missing if the file was rapidly renamed, moved, deleted, or (on Windows) opened by another process without https://learn.microsoft.com/en-us/windows/win32/fileio/creating-and-opening-files[read sharing]. +* Improves {elastic-defend} by enabling the use of dynamic {filebeat-ref}/kafka-output.html#topic-option-kafka[topics] for the Kafka output. +* Improves {elastic-defend} by integrating a new Event Tracing for Windows (ETW) provider (Microsoft-Windows-WMI-Activity) to create new event types that can be used by prebuilt endpoint rules to detect malicious WMI activity. + +[discrete] +[[enhancements-8.16.0]] +==== Enhancements +* Removes Elastic AI Assistant's default system prompts. The instructions previously contained in those prompts are now automatically included without user interaction, so Elastic AI Assistant will remain focused on relevant topics. Custom system prompts are still available ({kibana-pull}191847[#191847]). +* Improves Elastic AI Assistant's ability to generate {esql} queries ({kibana-pull}195480[#195480], {kibana-pull}188492[#188492]). +* Adds a button that lets you quickly add queries generated by Elastic AI Assistant to a rule's definition ({kibana-pull}190963[#190963]). +* Adds an **Other** option to the OpenAI connector's **Select an OpenAI provider** dropdown menu. Select this option when <> ({kibana-pull}194831[#194831]). +* Adds a {kib} advanced setting `securitySolution:maxUnassociatedNotes`, which allows you to set the maximum number of notes that can be attached to alerts and events ({kibana-pull}194947[#194947]). +* Adds an **Install and enable** button to the **Add Elastic Rules** page, which allows for rules to be immediately enabled after they're installed ({kibana-pull}191529[#191529]). +* Adds the **Alert Suppression** and **Investigative guide** fields to the rule upgrade workflow ({kibana-pull}195499[#195499]). +* Adds the `IS` operator as an option when configuring a Windows signature blocklist entry ({kibana-pull}190515[#190515]). +* Improves Attack Discovery in the following ways ({kibana-pull}195669[#195669]): +** Attack Discovery can now process up to 500 alerts (previous maximum: 100). This setting can now be adjusted directly from the Attack Discovery page and is stored locally instead of in {es}. +** Attack Discovery now combines related discoveries that would previously have appeared separately. +** Attack Discovery now detects and displays an error instead of hallucinated output. +* Updates the Get Started tour for {elastic-sec} ({kibana-pull}192247[#192247]). +* Improves loading performance for various pages in {kib} ({kibana-pull}194241[#194241]). +* Adds User and Global Artifacts to the {fleet} Policy Response flyout and to the Endpoint details flyout ({kibana-pull}184125[#184125]). +* Allows you to recalculate entity risk scores immediately after you upload asset criticality data ({kibana-pull}187577[#187577]). +* Allows you to enable entity risk scoring in multiple {kib} spaces ({kibana-pull}192671[#192671]). +* Creates a new API endpoint for cleaning up entity risk scoring data: `DELETE /api/risk_score/engine/dangerously_delete_data` ({kibana-pull}191843[#191843], {kibana-pull}189872[#189872]). +* Allows Automatic Import to analyze a larger number of sample events when generating a new integration ({kibana-pull}196233[#196233]). +* Allows Automatic Import to recognize CSV logs and create integrations for CSV data ({kibana-pull}196228[#196228], {kibana-pull}194386[#194386]). +* Allows you to open the rule details flyout from the Alerts table ({kibana-pull}191764[#191764]). +* Allows you to resize the alert and event details flyouts and choose how it's displayed in relation to the Alerts table (over or next to it) ({kibana-pull}192906[#192906], {kibana-pull}182615[#182615]). +* Improves network previews in the alert details flyout ({kibana-pull}190560[#190560]). +* Adds support in all detection rule types for {elastic-defend}'s automated response actions ({kibana-pull}193390[#193390], {kibana-pull}191874[#191874]). +* Enhances {elastic-defend} by improving the `call_stack_final_user_module` attribution where potential `proxy_call` modules are encountered during Windows call stack analysis. +* Adds new fields to {elastic-defend} API events to improve context for the triage of Behavior Alerts. The new `call_stack_final_user_module` fields are `allocation_private_bytes`, `protection`, `protection_provenance_path`, and `reason`. +* Adds a new {elastic-defend} API event for https://learn.microsoft.com/en-us/windows/win32/api/ioapiset/nf-ioapiset-deviceiocontrol[`DeviceIoControl`] calls to support the detection of driver abuse. This feature is only supported on Windows 11 Desktop versions. +* Ensures security artifacts are updated when the {elastic-defend} service starts. +* Improves error messages that are returned when {elastic-defend} receives invalid or unsupported cryptographic keys from the {elastic-defend} policy. +* Ensures that {elastic-defend} tells {fleet} that it's `orphaned` if the connection between {elastic-defend} and {agent} stops for an extended period of time. {fleet} uses this information to provide you with additional troubleshooting context. +* Adds SOCKS5 proxy support to {elastic-defend}'s {ls} output. +* Ensures that on Windows, {elastic-defend} uses https://www.elastic.co/security-labs/finding-truth-in-the-shadows[Intel CET and AMD Shadow Stacks] to collect call stacks, where supported. This improves performance and enables the detection of certain defense evasions. You can turn this feature off in {elastic-defend} <> ({kibana-pull}190553[#190553]). +* Restores {elastic-defend}'s support for Windows Server 2012, which was removed in 8.13.0. +* Improves {elastic-defend}'s caching to reduce memory usage on Windows. +* Enhances {elastic-defend} by reducing the size of process events, which reduces excessive process ancestry entries and shortens the entity ID. +* Improves the reliability and system resource usage of {elastic-defend}'s Windows network driver. + +[discrete] +[[bug-fixes-8.16.0]] +==== Bug fixes + +* Prevents an empty warning message from appearing for rule executions ({kibana-pull}186096[#186096]). +* Fixes an error that could occur during rule execution when the source index had a non-ECS-compliant text field ({kibana-pull}187673[#187673]). +* Fixes an issue that could cause fields for all indices to appear when you tried to add a rule filter ({kibana-pull}194678[#194678]). +* Removes unnecessary empty space below the title of the Open Timeline modal ({kibana-pull}188837[#188837]). +* Improves the performance of the Alerts table ({kibana-pull}192827[#192827]). +* Removes the requirement that you have unnecessary {kib} {fleet} privileges to access some cloud security posture findings ({kibana-pull}194069[#194069]). +* Fixes an {elastic-defend} bug where network event deduplication logic could incorrectly drop Linux network events. +* Fixes an {elastic-defend} bug where Windows API events might be dropped if they contain Unicode characters that can't be converted to ANSI. +* Ensures that {elastic-defend} does not emit an empty `memory_region` if it can't enrich a memory region in an API event. With this fix, {elastic-defend} removes these fields. +* Fixes a bug where {elastic-defend} could fail to properly enrich Windows API events for short-lived processes on older operating systems that don't natively include this telemetry, such as Windows Server 2019. This might result in dropped or unattributed API events. +* Fixes a bug that prevented host name uniformity with {beats} products. If you request {elastic-defend} to use the fully qualified domain name (FQDN) in the `host.name` field, {elastic-defend} now reports the FQDN exactly as the OS reports it, instead of lowercasing by default. +* Fixes an {elastic-defend} bug in behavior protection alerts, where prevention alerts could mistakenly be labeled as detection alerts. +* Fixes a bug that caused {elastic-defend} to crash if a Kafka connection is busy. +* Fixes scenarios where Automatic Import could generate invalid processors containing array access ({kibana-pull}196207[#196207]). +* Improves Timeline's table performance when row renderers are switched on ({kibana-pull}193316[#193316]). +* Fixes misaligned filter control labels on the Alerts page ({kibana-pull}192094[#192094]). \ No newline at end of file From 0ea6a676bd62d9cd088cde2acaaa1cd77f196d5a Mon Sep 17 00:00:00 2001 From: "nastasha.solomon" Date: Wed, 20 Nov 2024 19:24:48 -0500 Subject: [PATCH 2/2] Removes 8.16 release notes --- docs/release-notes/8.16.asciidoc | 216 ------------------------------- 1 file changed, 216 deletions(-) delete mode 100644 docs/release-notes/8.16.asciidoc diff --git a/docs/release-notes/8.16.asciidoc b/docs/release-notes/8.16.asciidoc deleted file mode 100644 index 68f7ce29b4..0000000000 --- a/docs/release-notes/8.16.asciidoc +++ /dev/null @@ -1,216 +0,0 @@ -[[release-notes-header-8.16.0]] -== 8.16 - -[discrete] -[[known-issue-8.16.1]] -==== Known issues - -// tag::known-issue[] -[discrete] -.Duplicate alerts can be produced from manually running threshold rules -[%collapsible] -==== -*Details* + -On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. - -==== -// end::known-issue[] - -// tag::known-issue[] -[discrete] -.Manually running custom query rules with suppression could suppress more alerts than expected -[%collapsible] -==== -*Details* + -On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. - -==== -// end::known-issue[] - -[discrete] -[[release-notes-8.16.1]] -=== 8.16.1 - -[discrete] -[[bug-fixes-8.16.1]] -==== Bug fixes -* Fixes a bug that caused the **Alerts** page to crash if you upgraded to 8.16 and accessed the page in a non-default {kib} space ({kibana-pull}200058[#200058]). -* Fixes a bug that caused the Elastic AI Assistant Knowledge Base to fail if the current user had a colon (`:`) in their username and attempted to access Knowledge Base entries ({kibana-pull}200131[#200131]). -* Fixes a bug that made values unavailable for the Knowledge Base **Index** field, which lets you specify an index as a knowledge source ({kibana-pull}199990[#199990]). -* Fixes a bug that unset the `required_fields` field if you updated a rule by sending a `PATCH` request that didn't contain the `required_fields` field ({kibana-pull}199901[#199901]). -* Fixes an issue that prevented you from successfully importing TSV files with asset criticality data if you were on Windows ({kibana-pull}199791[#199791]). -* Fixes the entity store initialization error that was caused by risk engine failures. Now, when you upgrade to 8.16.1, or follow the standard flow for initializing the entity store, the risk engine no longer fails while deleting the component template. In addition, the index template will correctly reference the new component template, ensuring the successful initialization of the entity store ({kibana-pull}199734[#199734]). -* Improves the warning message that displays when asset criticality assignments are duplicated during the bulk assignment flow ({kibana-pull}199651[#199651]). -* Fixes a time skew bug that occurred when Linux virtual machines using eBPF event probes were suspended and then resumed. - -[discrete] -[[release-notes-8.16.0]] -=== 8.16.0 - -[discrete] -[[known-issue-8.16.0]] -==== Known issues - -// tag::known-issue[] -[discrete] -.Attempting to edit an Elastic AI Assistant Knowledge Base index results in an error -[%collapsible] -==== -*Details* + -Updating a Knowledge Base entry of type "index" results in an error. - -*Workaround* + - -Upgrade to 8.16.1. Alternatively, instead of updating an "index" entry, delete it and add it again with the desired changes. - -*Resolved* + -On November 21, 2024, this issue was resolved. - -==== -// end::known-issue[] - -// tag::known-issue[] -[discrete] -.Duplicate alerts can be produced from manually running threshold rules -[%collapsible] -==== -*Details* + -On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. - -==== -// end::known-issue[] - -// tag::known-issue[] -[discrete] -.Manually running custom query rules with suppression could suppress more alerts than expected -[%collapsible] -==== -*Details* + -On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. - -==== -// end::known-issue[] - -// tag::known-issue-53[] -[discrete] -.Alerts page crashes if you upgrade to 8.16 and access it in a non-default {kib} space -[%collapsible] -==== -*Details* + -On November 14, 2024, it was discovered that the **Alerts** page would crash and display an `Unable to load` error if you upgraded to 8.16 and accessed the page in a non-default {kib} space. - -*Workaround* + - -Upgrade to 8.16.1. - -Alternatively, manually edit your browser's local storage and refresh the **Alerts** page: - -NOTE: These instructions only apply to the Google Chrome browser. Modify the steps based on the browser you're using. - -. Right-click anywhere on the **Alerts** page, then select *Inspect* to open Chrome's Developer Tools. -. Go to *Application -> Storage*, then expand *Local Storage*. -. Click on the name of your Kibana instance, for example, http://localhost:1234. -. Search for the `siem..pageFilters` key, right-click on the value, then click *Delete*. If you have multiple non-default spaces, do this for each space. -. Refresh the **Alerts** page to reload it. - -*Resolved* + -On November 21, 2024, this issue was resolved. - -==== -// end::known-issue-53[] - -[discrete] -[[features-8.16.0]] -==== New features - -* Introduces Knowledge Base for Elastic AI Assistant, which allows you to specify information for AI Assistant to remember when responding to your queries ({kibana-pull}186566[#186566], {kibana-pull}192665[#192665]). -* Enables agentless deployment for Elastic's Cloud Security Posture Management integration and the new Cloud Asset Inventory integration ({kibana-pull}191557[#191557]). -* Enables data collected by the Wiz and AWS Security Hub integrations to appear on the Findings page and in entity details flyouts (https://github.com/elastic/integrations/pull/10790[#10790], https://github.com/elastic/integrations/pull/11158[#11158]). -* Enables alerts collected by the Falco integration to appear on the Alerts page (https://github.com/elastic/integrations/pull/9619[#9619], https://github.com/elastic/integrations/pull/11051[#11051]). -* Adds ability to manually run rules for a specified time period, either for testing purposes or to generate alerts for past events. -* Adds historical results to the Data Quality dashboard and updates its UI ({kibana-pull}191898[#191898], {kibana-pull}196127[#196127]). -* Adds the ability to attach notes to alerts and events and introduces the Notes page, which allows you to manage all existing notes ({kibana-pull}186787[#186787], {kibana-pull}186807[#186807], {kibana-pull}186931[#186931], {kibana-pull}186946[#186946], {kibana-pull}187214[#187214], {kibana-pull}193373[#193373]). -* Enables detection rules to automatically execute system actions, such as opening a case ({kibana-pull}183937[#183937]). -* Adds role-based access control (RBAC) for Elastic AI Assistant's knowledge base ({kibana-pull}195733[#195733]). -* Adds RBAC for Attack Discovery ({kibana-pull}188788[#188788]). -* Removes the `securitySolution:enableAssetCriticality` advanced setting and enables <> workflows by default ({kibana-pull}196270[#196270]). -* Introduces the entity store as a technical preview feature, which allows observed, imported, integrated, or uploaded entities to be stored persistently ({kibana-pull}192806[#192806]). -* Adds syntax validation for {esql} queries ({kibana-pull}189780[#189780]). -* Allows you to view {es} queries that run during rule execution. This option is provided for {esql} and EQL rules only ({kibana-pull}191107[#191107]). -* Allows you to create and update a rule even when some data-related validation errors are present in the query field ({kibana-pull}191487[#191487]). -* Introduces a new advanced setting, `securitySolution:enableVisualizationsInFlyout`. When enabled, you can examine alerts and events in the **Visualize** tab, which provides a more detailed view of the event analyzer and Session View ({kibana-pull}194012[#194012], {kibana-pull}192531[#192531], {kibana-pull}192643[#192643]). -* Creates a new advanced setting `securitySolution:excludedDataTiersForRuleExecution` that allows you to exclude cold and frozen data from rule executions ({kibana-pull}186908[#186908]). -+ -IMPORTANT: Even when the `excludedDataTiersForRuleExecution` advanced setting is enabled, indicator match, event correlation, and {esql} rules may still fail if a frozen or cold shard that matches the rule's specified index pattern is unavailable during rule executions. If failures occur, we recommend modifying the rule's index patterns to only match indices containing hot tier data. -* Enhances the Insights section of the alert and event details flyouts by providing available misconfiguration and vulnerabilities findings ({kibana-pull}195509[#195509]). -* Turns off the host field size reduction setting on {elastic-defend}'s integration policy by default. To turn it on, configure the `[os].advanced.set_extended_host_information` <>. -* Allows you to reduce CPU usage, I/O, and event sizes by turning on process event aggregation when configuring your {elastic-defend} integration policy. Related process events that occur in rapid succession are combined into fewer aggregate events. To turn on process event aggregation, configure the `advanced.events.aggregate_process` <>. -* Allows you to reduce CPU usage, I/O, and event sizes by turning off MD5, SHA-1, and SHA-256 hashes in events when configuring your {elastic-defend} integration policy. Example fields include `process.hash.md5` and `file.hash.sha1`. -* Allows you to configure your {elastic-defend} integration policy to collect SHA-256 file hashes in file events. Before doing so, consider the following caveats: -** This can greatly increase {elastic-defend}'s CPU and I/O utilization and impact system responsiveness. -** This can significantly delay event enrichment and lead to Behavioral Protection rules firing too late to effectively stop malicious behavior. -** This can cause event processing queues to overflow and lead to dropped events. -** Many file events won't contain hashes. Hash collection is the best effort and is not guaranteed to be present in every event. Hashes are collected asynchronously and shortly after the file activity. Hashes might be missing if the file was rapidly renamed, moved, deleted, or (on Windows) opened by another process without https://learn.microsoft.com/en-us/windows/win32/fileio/creating-and-opening-files[read sharing]. -* Improves {elastic-defend} by enabling the use of dynamic {filebeat-ref}/kafka-output.html#topic-option-kafka[topics] for the Kafka output. -* Improves {elastic-defend} by integrating a new Event Tracing for Windows (ETW) provider (Microsoft-Windows-WMI-Activity) to create new event types that can be used by prebuilt endpoint rules to detect malicious WMI activity. - -[discrete] -[[enhancements-8.16.0]] -==== Enhancements -* Removes Elastic AI Assistant's default system prompts. The instructions previously contained in those prompts are now automatically included without user interaction, so Elastic AI Assistant will remain focused on relevant topics. Custom system prompts are still available ({kibana-pull}191847[#191847]). -* Improves Elastic AI Assistant's ability to generate {esql} queries ({kibana-pull}195480[#195480], {kibana-pull}188492[#188492]). -* Adds a button that lets you quickly add queries generated by Elastic AI Assistant to a rule's definition ({kibana-pull}190963[#190963]). -* Adds an **Other** option to the OpenAI connector's **Select an OpenAI provider** dropdown menu. Select this option when <> ({kibana-pull}194831[#194831]). -* Adds a {kib} advanced setting `securitySolution:maxUnassociatedNotes`, which allows you to set the maximum number of notes that can be attached to alerts and events ({kibana-pull}194947[#194947]). -* Adds an **Install and enable** button to the **Add Elastic Rules** page, which allows for rules to be immediately enabled after they're installed ({kibana-pull}191529[#191529]). -* Adds the **Alert Suppression** and **Investigative guide** fields to the rule upgrade workflow ({kibana-pull}195499[#195499]). -* Adds the `IS` operator as an option when configuring a Windows signature blocklist entry ({kibana-pull}190515[#190515]). -* Improves Attack Discovery in the following ways ({kibana-pull}195669[#195669]): -** Attack Discovery can now process up to 500 alerts (previous maximum: 100). This setting can now be adjusted directly from the Attack Discovery page and is stored locally instead of in {es}. -** Attack Discovery now combines related discoveries that would previously have appeared separately. -** Attack Discovery now detects and displays an error instead of hallucinated output. -* Updates the Get Started tour for {elastic-sec} ({kibana-pull}192247[#192247]). -* Improves loading performance for various pages in {kib} ({kibana-pull}194241[#194241]). -* Adds User and Global Artifacts to the {fleet} Policy Response flyout and to the Endpoint details flyout ({kibana-pull}184125[#184125]). -* Allows you to recalculate entity risk scores immediately after you upload asset criticality data ({kibana-pull}187577[#187577]). -* Allows you to enable entity risk scoring in multiple {kib} spaces ({kibana-pull}192671[#192671]). -* Creates a new API endpoint for cleaning up entity risk scoring data: `DELETE /api/risk_score/engine/dangerously_delete_data` ({kibana-pull}191843[#191843], {kibana-pull}189872[#189872]). -* Allows Automatic Import to analyze a larger number of sample events when generating a new integration ({kibana-pull}196233[#196233]). -* Allows Automatic Import to recognize CSV logs and create integrations for CSV data ({kibana-pull}196228[#196228], {kibana-pull}194386[#194386]). -* Allows you to open the rule details flyout from the Alerts table ({kibana-pull}191764[#191764]). -* Allows you to resize the alert and event details flyouts and choose how it's displayed in relation to the Alerts table (over or next to it) ({kibana-pull}192906[#192906], {kibana-pull}182615[#182615]). -* Improves network previews in the alert details flyout ({kibana-pull}190560[#190560]). -* Adds support in all detection rule types for {elastic-defend}'s automated response actions ({kibana-pull}193390[#193390], {kibana-pull}191874[#191874]). -* Enhances {elastic-defend} by improving the `call_stack_final_user_module` attribution where potential `proxy_call` modules are encountered during Windows call stack analysis. -* Adds new fields to {elastic-defend} API events to improve context for the triage of Behavior Alerts. The new `call_stack_final_user_module` fields are `allocation_private_bytes`, `protection`, `protection_provenance_path`, and `reason`. -* Adds a new {elastic-defend} API event for https://learn.microsoft.com/en-us/windows/win32/api/ioapiset/nf-ioapiset-deviceiocontrol[`DeviceIoControl`] calls to support the detection of driver abuse. This feature is only supported on Windows 11 Desktop versions. -* Ensures security artifacts are updated when the {elastic-defend} service starts. -* Improves error messages that are returned when {elastic-defend} receives invalid or unsupported cryptographic keys from the {elastic-defend} policy. -* Ensures that {elastic-defend} tells {fleet} that it's `orphaned` if the connection between {elastic-defend} and {agent} stops for an extended period of time. {fleet} uses this information to provide you with additional troubleshooting context. -* Adds SOCKS5 proxy support to {elastic-defend}'s {ls} output. -* Ensures that on Windows, {elastic-defend} uses https://www.elastic.co/security-labs/finding-truth-in-the-shadows[Intel CET and AMD Shadow Stacks] to collect call stacks, where supported. This improves performance and enables the detection of certain defense evasions. You can turn this feature off in {elastic-defend} <> ({kibana-pull}190553[#190553]). -* Restores {elastic-defend}'s support for Windows Server 2012, which was removed in 8.13.0. -* Improves {elastic-defend}'s caching to reduce memory usage on Windows. -* Enhances {elastic-defend} by reducing the size of process events, which reduces excessive process ancestry entries and shortens the entity ID. -* Improves the reliability and system resource usage of {elastic-defend}'s Windows network driver. - -[discrete] -[[bug-fixes-8.16.0]] -==== Bug fixes - -* Prevents an empty warning message from appearing for rule executions ({kibana-pull}186096[#186096]). -* Fixes an error that could occur during rule execution when the source index had a non-ECS-compliant text field ({kibana-pull}187673[#187673]). -* Fixes an issue that could cause fields for all indices to appear when you tried to add a rule filter ({kibana-pull}194678[#194678]). -* Removes unnecessary empty space below the title of the Open Timeline modal ({kibana-pull}188837[#188837]). -* Improves the performance of the Alerts table ({kibana-pull}192827[#192827]). -* Removes the requirement that you have unnecessary {kib} {fleet} privileges to access some cloud security posture findings ({kibana-pull}194069[#194069]). -* Fixes an {elastic-defend} bug where network event deduplication logic could incorrectly drop Linux network events. -* Fixes an {elastic-defend} bug where Windows API events might be dropped if they contain Unicode characters that can't be converted to ANSI. -* Ensures that {elastic-defend} does not emit an empty `memory_region` if it can't enrich a memory region in an API event. With this fix, {elastic-defend} removes these fields. -* Fixes a bug where {elastic-defend} could fail to properly enrich Windows API events for short-lived processes on older operating systems that don't natively include this telemetry, such as Windows Server 2019. This might result in dropped or unattributed API events. -* Fixes a bug that prevented host name uniformity with {beats} products. If you request {elastic-defend} to use the fully qualified domain name (FQDN) in the `host.name` field, {elastic-defend} now reports the FQDN exactly as the OS reports it, instead of lowercasing by default. -* Fixes an {elastic-defend} bug in behavior protection alerts, where prevention alerts could mistakenly be labeled as detection alerts. -* Fixes a bug that caused {elastic-defend} to crash if a Kafka connection is busy. -* Fixes scenarios where Automatic Import could generate invalid processors containing array access ({kibana-pull}196207[#196207]). -* Improves Timeline's table performance when row renderers are switched on ({kibana-pull}193316[#193316]). -* Fixes misaligned filter control labels on the Alerts page ({kibana-pull}192094[#192094]). \ No newline at end of file