[Security Solution] Add endpoint action response permission to defaults #117162
Conversation
This file contains 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
botelastic
bot
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
kevinlog
added
the
Team:Defend Workflows
|
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt) |
kevinlog
added
v8.0.0
v7.16.0
v8.1.0
release_note:skip
ashokaditya
approved these changes
Nov 2, 2021
|
I do not think we should move forward with that PR see #116715 (comment) This is the default permissions we generate in case we are not able to read permissions for the package, we should be able to generate the permissions for endpoint so we probably do not need this defaults |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
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.
Summary
This PR adds a new hidden index
.logs-endpoint.action.responses-*to the set of default permissions to be consistent with the existing hidden index.logs-endpoint.diagnostic.collection-*.There is a problem with Cloud instances where the permissions contained in Endpoint Security policies don't seem to be reflected in Cloud. Locally, the permissions are respected. More information here: #116715
I'm not sure if this PR fixes anything in Cloud instances, but I noticed our new index was missing and all of our older indices were included, so it seemed strange not to include
.logs-endpoint.action.responses-*.Checklist