- What's New in i56
- Updated Threat Intelligence Feeds from ZeroFox
- Improved Filters for Smart Timelines™
- Display More Accurate Times for When Rules Triggered on the Smart Timeline™
- More Accurate Geolocation and Internet Service Provider (ISP) Data for Your Events
- More Helpful Technical Support Information
- Updated Navigation to the Exabeam Community and Documentation Portal
- Troubleshoot Your Own Data Ingestion issues
- Support for the Latest Version of IBM® QRadar® Security Information and Event Management (SIEM)
- Stuck and Failed Parser Detection
- Known Issues in Advanced Analytics i57
- Issues Fixed in Advanced Analytics i56.14
- Issues Fixed in Advanced Analytics i56.13
- Issues Fixed in Advanced Analytics i56.12
- Issues Fixed in Advanced Analytics i56.11
- Issues Fixed in Advanced Analytics i56.10
- Issues Fixed in Advanced Analytics i56.9
- Issues Fixed in Advanced Analytics i56.8
- Issues Fixed in Advanced Analytics i56.7
- Issues Fixed in Advanced Analytics i56.5
PrevNext
Issues Fixed in Advanced Analytics i56.14
Issue ID | Description |
|---|---|
EXA-35817 | Fixed an issue with model calculations that affected up to 320 rules. The model threshold calculation incorrectly evaluated event counts as anomalous based on outdated model snapshot data, causing rules to be either over or under triggered. With this fix, the percentile threshold count is now always calculated based on the latest model snapshot data instead of cached snapshots. This fix does not change the underlying calculation logic for the percentile threshold count. |