Give Kibana user 'all' permissions for .entity_analytics.* indices #123588
Conversation
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
hop-dev
added
>enhancement
:Core/Infra/Core
Collaborator
|
@hop-dev please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
elasticsearchmachine
added
the
external-contributor
Collaborator
|
Hi @hop-dev, I've created a changelog YAML for you. |
| .build(), | ||
| // security entity analytics indices | ||
| RoleDescriptor.IndicesPrivileges.builder().indices("risk-score.risk-*").privileges("all").build(), | ||
| RoleDescriptor.IndicesPrivileges.builder().indices("entity_analytics.*").privileges("all").build(), |
Contributor
There was a problem hiding this comment.
Question: From the description, it seems like kibana_system only needs read permissions. Is that correct?
Contributor
Author
There was a problem hiding this comment.
@SiddharthMantri sorry about the delay, I have added a section to the description about our need for full CRUD
SiddharthMantri
approved these changes
Mar 10, 2025
georgewallace
pushed a commit
to georgewallace/elasticsearch
that referenced
this pull request
Mar 11, 2025
jfreden
pushed a commit
to jfreden/elasticsearch
that referenced
this pull request
Mar 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We are building privileged user monitoring for Kibana, as part of that we will have the
.entity_analytics.monitoring.usersand.entity_analytics.monitoring.groupsindices. Down the line there will be more entity_analytics indices so we want to give Kibana access to these in the futureWhat will these indices contain?
.entity_analytics.monitoring.users
ECS formatted users to monitor, this index will be read by a kibana task which performs the monitroing.
.entity_analytics.monitoring.groups
Semi-ECS formatted user groups which are considered to give the user elevated rights, groups have a name and an index pattern to allow the user to specify which indices the group appears in.
How will Kibana use these indices?