Skip to content

Commit b4c4fcd

Browse files
[Security] Entity store historical views (#3269)
Resolves #3228 by documenting the entity store's historical views feature. Previews: * [Entity store](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3269/solutions/security/advanced-entity-analytics/entity-store) * [View and analyze risk score data > Analyze entities over time](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3269/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data#historical-entity-analysis)
1 parent fc348a6 commit b4c4fcd

File tree

2 files changed

+22
-12
lines changed

2 files changed

+22
-12
lines changed

solutions/security/advanced-entity-analytics/entity-store.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,8 @@ When the entity store is enabled, the following resources are generated for each
3333
* {{es}} resources, such as transforms, ingest pipelines, and enrich policies.
3434
* Data and fields for each entity.
3535
* The `.entities.v1.latest.security_user_<space-id>`, `.entities.v1.latest.security_host_<space-id>`, and `.entities.v1.latest.security_services_<space-id>` indices, which contain field mappings for hosts, users, and services respectively. You can query these indices to see a list of fields that are mapped in the entity store.
36-
36+
* {applies_to}`stack: ga 9.2` {applies_to}`serverless: ga` Snapshot indices (`.entities.v1.history.<ISO_date>.*`) that store daily snapshots of entity data, enabling [historical analysis](/solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md#historical-entity-analysis) of attributes over time.
37+
* {applies_to}`stack: ga 9.2` {applies_to}`serverless: ga` Reset indices (`.entities.v1.reset.*`) that ensure entity timestamps are updated correctly in the latest index, supporting accurate time-based queries and future data resets.
3738

3839
## Enable entity store [enable-entity-store]
3940

solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md

Lines changed: 20 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,12 @@ products:
1313

1414
# View and analyze risk score data [analyze-risk-score-data]
1515

16-
The {{security-app}} provides several options to monitor the change in the risk posture of hosts and users from your environment. Use the following places in the {{security-app}} to view and analyze risk score data:
17-
18-
* [Entity Analytics overview](#entity-analytics-overview)
19-
* [Alerts page](#alerts-page)
20-
* [Alert details flyout](#alert-details-flyout)
21-
* [Hosts and Users pages](#hosts-users-pages)
22-
* [Host and user details pages](#host-user-details-pages)
23-
* [Entity details flyouts](#entity-details-flyouts)
16+
The {{security-app}} provides several ways to monitor the change in the risk posture of entities in your environment.
2417

2518
::::{tip}
26-
We recommend that you prioritize [alert triaging](#alert-triaging) to identify anomalies or abnormal behavior patterns.
19+
After reviewing an entity’s risk score, the recommended next step is to investigate the risky entity in [Timeline](/solutions/security/investigate/timeline.md).
2720
::::
2821

29-
30-
3122
## Entity Analytics overview [entity-analytics-overview]
3223

3324
In the Entity Analytics overview, you can view entity key performance indicators (KPIs), risk scores, and levels. You can also click the number link in the **Alerts** column to investigate and analyze the alerts on the Alerts page.
@@ -183,3 +174,21 @@ In the entity details flyouts, you can access the risk score data in the risk su
183174
:alt: Host risk data in the Host risk summary section
184175
:screenshot:
185176
:::
177+
178+
## Analyze entities over time [historical-entity-analysis]
179+
```yaml {applies_to}
180+
stack: ga 9.2
181+
serverless: ga
182+
```
183+
184+
The [entity store](/solutions/security/advanced-entity-analytics/entity-store.md) allows you to analyze how entity attributes change over time, making it easier to investigate past activity, track trends, and identify unusual behavior or changes that may indicate risk. Use time-based queries in [Discover](/explore-analyze/discover.md) to answer questions such as:
185+
186+
* What did user A’s attributes look like on March 15?
187+
* How has user B's risk score changed over the last 90 days?
188+
* Which user had the biggest jump in their risk score since yesterday?
189+
190+
By analyzing current and past entity data, you can understand how your environment and its entities evolve over time.
191+
192+
::::{note}
193+
If you enabled the entity store before upgrading to 9.2, you'll need to re-start it using the **On**/**Off** toggle to access the historical analysis feature.
194+
::::

0 commit comments

Comments
 (0)