-
Notifications
You must be signed in to change notification settings - Fork 155
[Security] [Serverless: Sep 23] Endpoint Exceptions feature privilege in Stack #2983
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
Conversation
🔍 Preview links for changed docs |
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.
thank you for the changes, and apologies for the late notice! 🙇
solutions/security/configure-elastic-defend/elastic-defend-feature-privileges.md
Outdated
Show resolved
Hide resolved
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.
thank you for the update! 🙌
one more note in case it matters in this PR, as i see the order of the rows in the doc mirrors the order of the privileges on UI: just got a confirmation offline, that we're moving the Endpoint Exceptions sub-feature privilege below Event filters, like on the screenshot below, in order to harmonize with the upcoming changes regarding Endpoint Exception being moved to the Management (Assets) page, in particular as the last artifact in the list.
https://github.com/elastic/security-team/issues/12269#issuecomment-3285451431
You're right, we're following the same order as in the UI, thanks for flagging it! |
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.
LGTM!
Resolves #2974.
Documents the addition of the Endpoint Exceptions sub-feature privilege in Stack for 9.2. Until now, this privilege only existed in serverless.
For consistency, this PR also moves the location of the {applies_to} badge for the Global Artifact Management privilege, in line with the badge placement guidelines.
Preview: Elastic Defend feature privileges