[Security Solution][Detections] Handle RBAC edge case for Related Integration on the FE side

[banderror]

Summary

Some users won't be able to get additional information about rule's related integrations, such as which of them are installed, enabled, etc. In order to have access to integrations' data in Fleet, a user needs either of these 3 Kibana privileges:

• Integrations: Read or All
• Fleet: All
• Saved Objects Management: Read or All

If all of them are None, the Related Integrations feature incorrectly shows all integrations as Not Installed even if some of them may be:

This PR adds a client-side privilege check and falls back to the basic UI that just shows the integration name+link and not any install information.

Test instructions

To test, configure a role with the 3 mentioned privileges as None, e.g.

Then UI should fall back to no installed information:

Rule Details

Rule Management

TODO

In follow-up PRs:

• Handle the same RBAC edge case for Related Integration on the BE side. Return 403 from the endpoint.
• A test to exercise this fallback (either unit or cypress w/ specific role should do)
• Ensure docs mention the required privileges for this feature

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

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

[elasticmachine]

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

[spong]

Checked out, tested locally, and code reviewed -- LGTM! 👍

Great cleanup and fixes here @banderror! So much easier to grok with everything broken out into smaller, pure functions. Nice that the privilege checks are in their own hook and composed into the useInstalledIntegrations hook directly, and even better composability now with separate components for the Link/StatusBadge/VersionMismatchIcon.

I tested all the permutations of privileges between SOM/Fleet/Integrations, and each is working as expected. Even tested the error scenario by throwing within useInstalledIntegrations and looks like we're falling back as expected there as well 🙂.

Thank you for the tag-team here and all your efforts in getting these final fixes in -- LGTM! 🚀

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 51c9c1f
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	3097	3102	+5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	5.2MB	5.2MB	+1.2KB

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @banderror

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation