Closed
Conversation
This updates prebuilt roles and those used in tests to: * Reference siemv5 instead of the older siemv4 * Add the new `rules:read` or `rules:all` feature where appropriate Without this change, our tests are implicitly testing the `replacedBy`/"migration" path that existing users will follow. With that version of the code being green, we can have confidence in the behavior for existing users, and can then update our tests to use the latest features, here.
rylnd
force-pushed
the
rules-rbac-siemv5-role-update
branch
from
9297b57 to
078d056
Compare
rylnd
reviewed
Dec 5, 2025
| - feature_siemV5.execute_operations_all # Execute | ||
| - feature_siemV5.scan_operations_all | ||
| - feature_siemV5.workflow_insights_all | ||
| - feature_securitySolutionRulesV1.all |
Owner
There was a problem hiding this comment.
endpoint_operations_analyst should only be able to read rules, according to this spreadsheet. I've updated this on the corresponding project-controller PR; pushing an update here now, too.
Owner
|
Closing in favor of elastic#245576. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.