- 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
Issues Fixed in Advanced Analytics i56.5
Issue ID | Description |
|---|---|
EXA-31486 | The Account Lockouts watchlist didn't display all users in the selected time period, or didn't display any users at all, because Advanced Analytics Restful Web Services queried the account lockout containers incorrectly. Advanced Analytics Restful Web Services pulled the first 100 account lockout sequences from the latest date collections, then filtered out account lockout sequences that weren't whitelisted. If all the sequences were whitelisted and filtered out, Advanced Analytics Restful Web Services couldn't return any data. Now, it pulls and returns only the first 100 whitelisted account lockout sequences across the latest date collections. |
EXA-33603 | When you navigated to an account lockout event from the Smart Timelines™ Logon Failures and Lockouts summary, the event didn't load. This issue has been resolved. |
EXA-33572, EXA-33849 | In some environments, you couldn't access user Smart Timelines and encountered a Failed to fetch all user timeline sequences error. You received this error because some integer fields in the MongoDB container collection were stored in an incorrect format. This issue has been resolved. |