Skip to content

[8.14] [BUG] All Kibana privileges don't grant Security / Elastic Defend features by default (backport #6134) #6139

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Nov 12, 2024
Merged

[8.14] [BUG] All Kibana privileges don't grant Security / Elastic Defend features by default (backport #6134) #6139

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a8f49f
[BUG] All Kibana privileges don't grant Security / Elastic Defend fea…
joepeeples Nov 12, 2024
e59b271
Delete docs/serverless directory and its contents
github-actions[bot] Nov 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/getting-started/defend-feature-privs.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,11 @@ NOTE: {elastic-defend}'s feature privileges must be assigned to *All Spaces*. Yo
[role="screenshot"]
image::images/endpoint-privileges.png[Configuring privileges in Kibana,75%]

To grant access, select *All* for the *Security* feature in the *{kib} privileges* configuration UI, then turn on the *Customize sub-feature privileges* switch. For each of the following sub-feature privileges, select the type of access you want to allow:
To grant access, select *All* for the *Security* feature in the *Assign role to space* configuration UI, then turn on the *Customize sub-feature privileges* switch.

IMPORTANT: Selecting **All** for the overall **Security** feature does NOT enable any sub-features. You must also enable the **Customize sub-feature privileges** switch, and then enable each sub-feature privilege individually.

For each of the following sub-feature privileges, select the type of access you want to allow:

* *All*: Users have full access to the feature, which includes performing all available actions and managing configuration.
* *Read*: Users can view the feature, but can't perform any actions or manage configuration. (Some features don't have this privilege.)
Expand Down