Repository navigation
Description
What
The Entity Analytics page is redesigned so analysts can prioritize and investigate changes faster. The current docs describe the old page.
Removed: the threat hunting leads panel and the anomalies explore section.
New or changed
- Header and tour: header with docs link and menu; first-time banner ("Start tour", "View docs"); 3-step product tour, reopened from the header menu.
- Search and filters: KQL bar, time range 24h / 7d / 30d (default 24h), filters for Entity type, Risk level, Asset criticality, Data source and Watchlist (with a "create watchlist" flyout). State is kept in the URL.
- Needs attention tiles: six new tiles (including "Anomalous"), each with a delta and a sparkline. Click a tile to filter the table (up to 1,000 entities, with a warning when capped); click again to clear. A tile query over 90 seconds shows "Timed out". See the table below.
- Entities grid: "Resolved entities" (default, one row per resolved entity) or "Individual records" rows; group by up to 3 levels; column picker; no pagination (up to 1,000 rows); "Risk score change" is the current score minus the last score in the 2 hours before the range.
- Hunt with AI: opens an Agent Builder chat with a prefilled prompt. Needs Agent chat on, lead generation on, an Enterprise license and lead generation read access.
- Entity flyout: redesigned header, risk score content, insights, observed attributes, anomalies and highlight summary.
Needs attention tiles: what each one needs to show data
| Tile | Counts entities that | Index privileges (Read) | Kibana privileges | Also needs |
|---|---|---|---|---|
| Severely alerting | have a high or critical open alert in the period | .alerts-security.alerts-.entities.v2.latest.-* | Read for the Security feature | N/A |
| Anomalous | have an ML anomaly in the period | .ml-anomalies-shared*.entities.v2.latest.-* | Read for the Security featureMachine Learning > canGetJobs | Anomaly detection jobs installed |
| Risk movers | rose by 10+ points since the period start | risk-score.risk-score-.entities.v2.latest.- | Read for the Security feature | An earlier risk score (at least a second risk engine run) |
| Newly high-risk | climbed to High or Critical | risk-score.risk-score-.entities.v2.latest.- | Read for the Security feature | N/A |
| Watchlisted & alerting | are on a watchlist and have an open alert | .alerts-security.alerts-.entities.v2.latest.-* | Read for the Security feature | N/A |
| New & alerting | were first seen in the period and have a risk score above 0. Only alerts raise a score from 0, so new entities with no alerts are left out | .entities.v2.latest.-* | Read for the Security feature | Risk engine on. Reads risk scores, not the alerts index, so no alert access is needed |
Entities grid/table
| Column | Resolved entities row | Individual records row | Needs (Read access to) |
|---|---|---|---|
| Entity name | The main entity's name | The record's name | .entities.v2.latest.<space>-* |
| Records | Number of records in the group (the main entity plus its aliases) | Not shown | .entities.v2.latest.<space>-* |
| Resolved to | Not shown | The main entity the record resolves to | .entities.v2.latest.<space>-* |
| Entity type | User, host, or service | Same | .entities.v2.latest.<space>-* |
| Risk score | The group's risk score | The record's own risk score | .entities.v2.latest.<space>-* |
| Risk score change | The group's current score minus its last score in the 2 hours before the start of the time range | The record's own current score minus its own last score in the same window | .entities.v2.latest.<space>-* and risk-score.risk-score-*.entities.v2.latest.<space>-* |
| Asset criticality | Highest criticality in the group | The record's criticality | .entities.v2.latest.<space>-* |
| Source | All data sources in the group | The record's data source | .entities.v2.latest.<space>-* |
| Alerts | Open alerts in the time range, summed across the group | Open alerts in the time range for the record | .entities.v2.latest.<space>-* and .alerts-security.alerts-<space>.entities.v2.latest.<space>-* |
| Last alert | Most recent alert for the group | Most recent alert for the record | .entities.v2.latest.<space>-* and .alerts-security.alerts-<space>.entities.v2.latest.<space>-* |
| Anomalies | ML anomaly records from the installed Security anomaly detection jobs, summed across the group | Same, for the record | .entities.v2.latest.<space>-* and .ml-anomalies-shared*. Anomaly detection jobs installed |
| Cases | Distinct cases linked to the group | Cases linked to the record | .entities.v2.latest.<space>-* and read access to cases |
| Watchlists | All watchlists any group member is on | The record's watchlists | .entities.v2.latest.<space>-* |
| First seen | Earliest first seen in the group | The record's first seen | .entities.v2.latest.<space>-* |
| Last seen | Latest last seen in the group | The record's last seen | .entities.v2.latest.<space>-* |
When
Release 9.6.
Which deployment methods does this change impact?
Elastic On-Prem and Cloud (all)
Why
Analysts get filtering and trend guidance on one page, so they can prioritize and investigate changes.
Resources
- Epic: https://github.com/elastic/security-team/issues/19081
- Design prototype: [Security Solution][Entity Analytics][DESIGN PROTOTYPE] Entity Analytics page facelift kibana#287135
Screenshots (local test data)
1. Page, Last 24h: six needs attention tiles, filters, entities grid
2. Product tour, step 1: "Start with what needs attention"
3. Product tour, step 2: "Get a head start from AI"
4. Product tour, step 3: "Choose your level of detail"
5. Filters: Risk level filter open
6. Tile selected: Severely alerting filters the table (capped at 1,000 with a warning)
7. Tile selected: Anomalous
8. Resolved entity expanded: the main entity (marked with an icon) and its aliases, by risk score
9. Hunt with AI: opens Agent Builder chat with a prefilled prompt
10. Header menu: Add integrations, Settings, Product tour, Feedback, Documentation
Related PRs
- Page shell: #289664, #294779, #298963, #298032, #299146, #299164
- Search and filters: #291582, #298025
- Entities grid: #296966, #296973, #297634, #297740, #298065, #298284, #298596, #299172, #299181, #298357
- Needs attention tiles: #291833, #296972, #297364, #297467, #298888, #298326, #298158, #298128, #299289, #298906
- Entity flyout: #296577, #296906, #296891, #297817, #297892, #298116, #298986
Where
The existing Entity Analytics dashboard page describes the old page and should point to the new one.
Which documentation set does this change impact? To be confirmed with the docs writer.
Release: 9.6
Point of contact: @orouz and @CAWilson94
Activity
github-actions commentedon Oct 28, 2026
Elastic Docs AI Menu
Check one box to run an AI workflow for this issue.
docs-scope). Status: not started.Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.