-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Security] Add entity store and asset criticality index privileges to built in roles #129662
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
opauloh
merged 17 commits into
elastic:main
from
opauloh:security-solution-entity-store-asset-criticality-roles
Jul 31, 2025
Merged
Changes from 11 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
f9dd0a0
Adding asset criticality and entity store permissions to built in roles
opauloh 13ea611
Update docs/changelog/129662.yaml
opauloh 30e1b12
[CI] Auto commit changes from spotless
4c0a5e4
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 66132ac
Corrects entity store index pattern
opauloh 427d5dd
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh c47bb72
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 5b6eb52
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 3ed67ef
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 73ecaa1
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 29f5db1
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 3220179
Grants kibana_system full access to entities index
opauloh c61689e
Replaces Array with Arrays
opauloh 7c3b747
Restricts access to .entities indices
opauloh ca81f21
[CI] Auto commit changes from spotless
9bfbf3f
Merge branch 'main' into security-solution-entity-store-asset-critica…
opauloh 536523d
Update changelog
opauloh 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| pr: 129662 | ||
| summary: "[Security] Add entity store and asset criticality index privileges to built\ | ||
| \ in Editor and Viewer roles" | ||
| area: Authorization | ||
| type: enhancement | ||
| issues: [] |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to double check - Serverless Editor appears to have write access to these indices - is this difference intentional?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for bringing it to my attention!
I will tag @hop-dev and @jaredburgettelastic to help on that. Mark / Jared, from what I could see, users don't really need to write directly into the Entity Store index, but do you happen to know a use case where they would need? Like running the API to clean the Entity Store or something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I think this was a mistake in the original PR apologies!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for confirming @hop-dev, so @richard-dennehy, the changes on this PR are correct, we will follow up on reducing the extra permissions on Serverless editor role to keep it consistent!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@opauloh sorry I have just thought, because the transform runs as the user who enabled the entity store, I believe we do need write permissions? Have I got that wrong?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I initially thought the same, but it turns out the Transform API doesn't require write privilege.
I guess the rationale behind this is that users shouldn't be writing to the transform destination indices directly anyway?
That's also accurate with the Entity Store permission page. (No write access required to the
.entities.v1.latest.*index)Also, by design, Editors wouldn't have the "manage" privilege, so Editors users won't likely be the ones to enable Entity Store / Asset Inventory, unless extra permissions are granted:
I.e screenshot from the permissions screen when accessing the Entity Store with an Editor user:
However, editors should be able to read entity store data and update asset criticality once it's enabled.
The only use case I can imagine writing directly would be handy is, if we had to update data directly on the destination index using the user permission to update data without waiting for the transforms to run, however, I didn't find anything performing that operation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed investigation, that's interesting about the transform write permissions! 👍