[RAC][Alert Triage] Permission Callout Components

[spong]

Description

This issue is for the generification of the Permission Callout components used within the Alert Triage workflow on the main Security Detections page and Rule Details page. There are two main callouts used within the Alert Triage workflow, one for when the user doesn't have write permissions to the .alerts index, and the other for when the .alerts index needs to be rolled over when a template update has been detected. Generification of the latter is TBD as we may be using the Kibana System User to achieve this.

User has no permissions to write (update) .alerts index

User has no permissions to rollover (maintenance) .alerts index (TBD, perhaps handled by kibana system user)

Interface

Inputs

• Has relevant permissions (canUserCRUD, signalIndexMappingOutdated, hasIndexManage)

Outputs

• None

API Requirements

• Permissions API for determining User write/maintenance privileges to the .alerts index. Currently leverages useUserData() hook within Security Solution.

Destination Plugin/Package 🏠

• Perhaps alerting plugin, rac plugin, or generic shared component package, but TBD.

Existing Source

ReadOnlyAlertsCallout (source) as implemented in this PR.

NeedAdminForUpdateCallout (source) as implemented in this PR

Data is fetched using following hook: useUserData() hook within Security Solution.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)