Skip to main content

Cloud-delivered Advanced AnalyticsAdvanced Analytics i63 Release Notes

Advanced Analytics i63.6

Issue ID

Description

UIPAA-421

Fixed an issue to address lengthy processing times for events that lack user definitions. Now, Advanced Analytics allows automatic partitioning in a number of scenarios to prevent overloading processors.

PLT-14061

Fixed an issue with IDP sessions in Advanced Analytics which caused the web interface to restart.

PLT-13813

Fixed an issue that prevented context data from being pulled from domains with dash characters ( - ) in their filenames.

PLT-13571

Fixed an issue that prevented context tables from populating when data in the first column of context records began with a # character. To correct this issue, parsing support for the data starting with # character has been added.

PLT-13492

Fixed a license processing issue that caused delays in navigating from the Exabeam Cloud Platform to Data Lake and Advanced Analytics.

EXA-38287

The Exabeam home icon in the upper left corner of Advanced Analytics left-navigation menu now opens the home page for the Exabeam Security Operations Platform.

EXA-37890

Fixed an issue with Risk Score sorting in various session and activity details in Threat Hunter, which caused the results to display out of order.

EXA-37847

Fixed an issue with the Dynamic Peer Group logic where the calculation was triggered before the slave (worker) nodes had time to complete training for some models. When this occurred, the Dynamic Peer Groups were partially populated in Advanced Analytics.

EXA-37800

Fixed a calculation issue where Advanced Analytics displayed a different number of incidents on the homepage (folder icon) and on the View all Incidents page for some Users & Assets. With this fix, the calculation is consistent across the homepage and the View all Incidents page. Additionally the View all Incidents page now filters incidents by entity instead of keyword.

EXA-36199

Fixed an issue where the First access of admin share on asset (A-SA-AsU-F) rule was triggered on an asset but did not show up in the asset timeline.

Also see:

Incident Responder Release Notes