You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: solutions/security/advanced-entity-analytics/entity-store.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,8 @@ When the entity store is enabled, the following resources are generated for each
33
33
* {{es}} resources, such as transforms, ingest pipelines, and enrich policies.
34
34
* Data and fields for each entity.
35
35
* 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.
Copy file name to clipboardExpand all lines: solutions/security/advanced-entity-analytics/view-analyze-risk-score-data.md
+20-11Lines changed: 20 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,21 +13,12 @@ products:
13
13
14
14
# View and analyze risk score data [analyze-risk-score-data]
15
15
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:
The {{security-app}} provides several ways to monitor the change in the risk posture of entities in your environment.
24
17
25
18
::::{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).
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
183
174
:alt: Host risk data in the Host risk summary section
184
175
:screenshot:
185
176
:::
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.
0 commit comments