-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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][Detections] Prevent permissions checks from being bypassed when indices do not exist #89664
Closed
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
Specifying this option meant that our field_capabilities check was throwing an error if the rule included an index pattern that did not exist. This would be most typical in e.g. a prepackaged rule using the default index patterns. While we rescued this error and continued rule execution, this had the side effect of skipping the remaining permissions checks, both of which would have potentially written a partial failure status to the rule. P.S. the original motivation for this PR was removing the confusing error that this option caused; it was only after exploration that this side effect was discovered.
rylnd
added
bug
Fixes for quality problems that affect the customer experience
release_note:skip
Skip the PR/issue when compiling release notes
v7.12.0
Team:Detections and Resp
Security Detection Response Team
labels
Jan 29, 2021
@elasticmachine merge upstream |
💔 Build Failed
Failed CI Steps
Test FailuresX-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/tests/add_actions·ts.detection engine api security and spaces enabled add_actions adding actions should be able to create a new webhook action and attach it to a rule without a meta field and run it correctlyStandard Out
Stack Trace
X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/tests/add_actions·ts.detection engine api security and spaces enabled add_actions adding actions should be able to create a new webhook action and attach it to a rule without a meta field and run it correctlyStandard Out
Stack Trace
X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/basic/tests/find_statuses·ts.detection engine api security and spaces enabled find_statuses should return a single rule status when a single rule is loaded from a find status with defaults addedStandard Out
Stack Trace
and 1 more failures, only showing the first 3. Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Closing in favor of #89927 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
release_note:skip
Skip the PR/issue when compiling release notes
Team:Detections and Resp
Security Detection Response Team
v7.12.0
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
Specifying this option meant that our field_capabilities check was
throwing an error if the rule included an index pattern that did not
exist. This would be most typical in e.g. a prepackaged rule using
the default index patterns.
While we rescued this error and continued rule execution, this had the
side effect of skipping the remaining permissions checks, both of which
would have potentially written a partial failure status to the rule.
P.S. the original motivation for this PR was removing the confusing new
error that this option caused:
It was only after exploration that this side effect was discovered. For this reason I'm not sure if we should try to get this in 7.11 or ship with the existing behavior; I could see arguments either way.
For maintainers