-
Notifications
You must be signed in to change notification settings - Fork 156
[Security] Entity store historical views #3269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,14 +13,7 @@ products: | |
|
||
# View and analyze risk score data [analyze-risk-score-data] | ||
|
||
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: | ||
|
||
* [Entity Analytics overview](#entity-analytics-overview) | ||
* [Alerts page](#alerts-page) | ||
* [Alert details flyout](#alert-details-flyout) | ||
* [Hosts and Users pages](#hosts-users-pages) | ||
* [Host and user details pages](#host-user-details-pages) | ||
* [Entity details flyouts](#entity-details-flyouts) | ||
The {{security-app}} provides several ways to monitor the change in the risk posture of entities in your environment. | ||
|
||
::::{tip} | ||
We recommend that you prioritize [alert triaging](#alert-triaging) to identify anomalies or abnormal behavior patterns. | ||
|
@@ -183,3 +176,21 @@ In the entity details flyouts, you can access the risk score data in the risk su | |
:alt: Host risk data in the Host risk summary section | ||
:screenshot: | ||
::: | ||
|
||
## Analyze entities over time [historical-entity-analysis] | ||
```yaml {applies_to} | ||
stack: ga 9.2 | ||
serverless: ga | ||
``` | ||
|
||
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 indicate risk. Use time-based queries in [Discover](/explore-analyze/discover.md) to answer questions such as: | ||
natasha-moore-elastic marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
* What did user A’s attributes look like on March 15? | ||
* How has user B's risk score changed over the last 90 days? | ||
* Which user had the biggest jump in their risk score since yesterday? | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should verify through testing that we can indeed answer these questions in version 9.2. cc: @uri-weisman |
||
By analyzing current and past entity data, you can understand how your environment and its entities evolve over time. | ||
|
||
::::{note} | ||
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. | ||
:::: |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.