Skip to content
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

[8.x] [Securitysolution] Add Risk score missing privileges callout to enablement flyout (#199804) #200123

Merged
merged 1 commit into from
Nov 14, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…ement flyout (elastic#199804)

## Summary

The entity analytics enablement model doesn't show the missing
privileges warning for the Entity Risk score.

To fix it, I added to the model the same callout we display on the risk
engine page.

### What is not included
* Improvement to the risk engine callout
* Fix risk engine callout bugs
elastic/security-team#11138

### How to test it
* Create a user with no privileges except to the security solution app
and the `logs*` index
* Login and open the entity analytics page with the non-privileged user
* Click enable and check if the model displays the missing privileges
callout for the risk engine

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

(cherry picked from commit 54c6144)
@kibanamachine kibanamachine merged commit 6e7d436 into elastic:8.x Nov 14, 2024
36 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 13.4MB 13.4MB +175.0B

cc @machadoum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants