[Security] Security Kibana privileges catalog by natasha-moore-elastic · Pull Request #8281 · elastic/docs-content · GitHub
Skip to content

[Security] Security Kibana privileges catalog - #8281

Open
natasha-moore-elastic wants to merge 6 commits into
mainfrom
issue-1702-privs-sec
Open

natasha-moore-elastic wants to merge 6 commits into
mainfrom
issue-1702-privs-sec

Conversation

@natasha-moore-elastic

Copy link
Copy Markdown
Contributor

Adds a Security Kibana privileges page that catalogs the privileges in the Security group of the Assign role to spaces flyout, what each one allows, and which versions they apply to.

Sub-feature privileges are documented on the same page, except where they already have an established home — Elastic Defend and Cases — which the catalog links to instead. Pages that already described these privileges in prose now point at the catalog.

Also retitles the Elastic Defend feature privileges page to sub-feature privileges and applies the shared catalog format to it.

Resolves https://github.com/elastic/docs-content-internal/issues/1702

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Point the Timeline, Notes, and Elastic Security requirements pages at the
Security Kibana privileges catalog, and correct the requirements page
description of what the Security privilege grants.

Co-authored-by: Cursor <cursoragent@cursor.com>
The SOC Management and Elastic AI Assistant privileges are now documented
on the Security Kibana privileges page, so link there instead of the
central Kibana privileges page.

Co-authored-by: Cursor <cursoragent@cursor.com>
Point "specific actions" at the Rules and Exceptions sub-feature
privileges section of the Security Kibana privileges page.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant