[BUG] `All` Kibana privileges don't grant Security / Elastic Defend features by default

[joepeeples]

Documentation links

https://www.elastic.co/guide/en/security/master/endpoint-management-req.html

Page doesn't yet exist in serverless docs but will be added in https://github.com/elastic/security-docs/pull/5779 https://github.com/elastic/security-docs/pull/5763. Depending on timing, either update that PR or the serverless page if it's already been published.

Description

Per https://github.com/elastic/kibana/issues/191592, selecting All for the top-level Kibana feature privileges doesn't automatically include Security or Elastic Defend features and sub-features as expected. The user must also select the Security feature.

Add more explicit language to explain this.

Which documentation set(s) does this bug apply to?

ESS and serverless

Release version

Bug was reported in 8.14.1.

Testing environment

Any ESS deployment

[joepeeples]

Related Kibana PR adding UI copy to help explain this: https://github.com/elastic/kibana/pull/192273#issuecomment-2338346553

[joepeeples]

• Semi-blocked by https://github.com/elastic/security-docs/pull/5779, because we'll need to add content to a page that doesn't exist yet in serverless docs (Elastic Defend feature privileges). I'd rather not try to juggle all these changes across multiple PR streams, so I'll wait until that big PR is merged and then just update the content in main.