-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution]Asset Criticality not updates in Expanded Risk Contribution Fly-out #177874
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Reviewed & assigned to @MadameSheema |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-detection-engine (Team:Detection Engine) |
@jaredburgettelastic I think this falls under EA? |
This is expected behavior, as the risk score has not yet been updated in this scenario. The risk score only updates once per hour, and therefore the contributions shouldn't change until the score also changes. We should look into a way to properly explain this within that contributions tab. cc @SourinPaul |
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
Closing this issue because we are working on improving the asset criticality assignment to "instantly" recalculate the score here: https://github.com/elastic/security-team/issues/9121 |
Describe the bug:
Asset Criticality not updates in Expanded Risk Contribution Fly-out
Kibana/Elasticsearch Stack version
Functional Area:
Asset Criticality
precondition
Steps to reproduce
Additional Result
Current Result
Expected Result
Screen-Shot:
assest_not_update.mov
assest_criticality_not_udpated.mov
The text was updated successfully, but these errors were encountered: