-
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
[RAC][Alerts] - Addition of RBAC to unified alerts index #96014
Closed
Closed
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
b412645
adding alerts actions to security plugin
yctercero 0bbb4d9
adds kibana security feature privileges and updates alerts actions to…
dhurley14 7d3578b
[RAC] [RBAC] adds rac client initialization to plugin setup / startup…
dhurley14 80183a3
wip - updating kibana features plugin to include rac and some renamin…
yctercero 2b00b22
still wip
yctercero 21f6e5f
testing out how to view owners for alerts when registering rac plugin…
dhurley14 5a34390
adds a working racClient to request context and picks up owners suppl…
dhurley14 fee5036
adds elasticsearch client to provide functionality for rac client, sh…
dhurley14 1583cd6
adding tests, cleanup, almost there mvp
yctercero 57dbec5
updates unit tests to remove the 'spaceid' from the authz action and …
dhurley14 bfc2334
fixes bug where we did not assign getSpaces function in rac factory i…
dhurley14 0498d22
parameterized calls into racClient.get() to match solutions, adds mor…
dhurley14 9ef683a
adds missing variables from rebase conflicts with master
dhurley14 3c06ce8
fixes changes from rebase with master
dhurley14 273ea82
adds an 'owner' field to the siem-signals mapping, working authz get …
dhurley14 ef85289
Revert "adds an 'owner' field to the siem-signals mapping, working au…
dhurley14 ee9aae9
adds an 'owner' field to the siem-signals mapping, working authz get …
dhurley14 87ac3e9
adds consumer / owner field to alerts created by rule registry (#11)
dhurley14 350aa97
fixes merge conflicts and updates logging, defaults to always writing…
dhurley14 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 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 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 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 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 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 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 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 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 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 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 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 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 |
---|---|---|
|
@@ -6,6 +6,7 @@ | |
"requiredPlugins": [ | ||
"licensing", | ||
"features", | ||
"ruleRegistry", | ||
"data", | ||
"navigation", | ||
"kibanaLegacy", | ||
|
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
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
Oops, something went wrong.
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.
The name
rac
suggests this controls access to Rules and Cases as well as Alerts.I know this isn't true for Rules (as that's controlled by the
alerting
RBAC).Not sure about Cases.
I recognise the complication with terminology update, as our privileges would have to stay as
alerting
for now (as opposed to changing them to be underrules
, as that would be a breaking change I believe [cc @legrego ?]), but it feels like naming these privilegesrac
will add to the confusion.So, should this be changed to something more specific? 🤔
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.
Feature IDs and sub-feature privilege ids are the only entities that cannot be renamed, as these get translated into Elasticsearch Application Privileges, which are then directly assigned to roles. I thought your features were named
actions
andstackAlerts
, unless I'm thinking of 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.
naming is hard, what about just
SolutionAlerts
? I do agree with you @gmmorrisThere 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.
Ah, sorry, I'm referring to the key in the privileges object, rather than the feature IDs.
We use
alerting
:kibana/x-pack/plugins/stack_alerts/server/feature.ts
Line 33 in 3bc2952
@XavierM I don't think
SolutionAlerts
is accurate as it'll be used by Stack Rules too.Am I right that this will define the RBAC for the alerts as data operations? Feels like this should probably be
alertsAsData
oralerts
, and we should change ours to berules
🤔Though... it raises the question: shouldn't the
alerts
privileges be inferred fromrules
privileges? Otherwise a user can create a rule but can't read the alerts produced by that rule 😬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.
@mikecote I think we might need to do another terminology change on our end - change our privileges key to
rules
instead ofalerting
🤔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.
We probably have a good reason to have different access controls for alerts, but IMHO inheriting those privileges from the rules make a lot of sense, and is the simplest model I can think of.
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.
@dgieselaar for t1 analysts, they're able to update alerts (status) but not able to
write
on rules.@gmmorris I think the renaming to
rules
would be super helpful