[AI4DSOC] Fix cases capability used in Security navbar

[tomsonpl]

Fix the issue where Security Section was not displayed.

Closes: #221573

[tomsonpl]

/ci

[tomsonpl]

Had to revert this change, because of an edge case where redirect to cases takes place:

kibana/x-pack/solutions/security/plugins/security_solution/public/app/app_routes.tsx

Line 36 in 1b167d9

if (hasAccessToSecuritySolution(capabilities)) {

[tomsonpl]

Caught by this test:

kibana/x-pack/solutions/security/plugins/security_solution/public/app/app_routes.test.tsx

Line 80 in 1b167d9

it('RedirectRoute should redirect to cases page when siem privilege is none and case privilege is read', () => {

[tomsonpl]

/ci

[semd]

Can't we just change securitySolutionCasesV2 by securitySolutionCasesV3, instead of doing the cases check outside?

[tomsonpl]

We can't without changing the behavior. The redirect would get into the /get_started page instead of /cases here:

kibana/x-pack/solutions/security/plugins/security_solution/public/app/app_routes.tsx

Line 36 in 1b167d9

if (hasAccessToSecuritySolution(capabilities)) {

[semd]

@tomsonpl Oh, good point.
Then would you mind creating different functions, with a clear naming, because this is a bit confusing right now. We could have:

• hasSecurityAccess -> security || attack-discovery (used in app_routes)
• hasCasesAccess -> cases (used in app_routes)
• isSecuritySolutionAccessible -> hasSecurityAccess() || hasCasesAccess() (used in the plugin.tsx)

And consider using CASES_FEATURE_ID instead of hardcoding the version.

Question: Should we consider letting users access Security if they only have the assistant feature? Maybe it should be part of hasSecurityAccess.

[tomsonpl]

Thanks, changed it as you suggested 👍 I'll get this assistant question back to the team

[semd]

❤️ Love it. Thanks @tomsonpl
LGTM!

[kibanamachine]

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15488622283

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9d3e1ec

Metrics [docs]

Async chunks

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

id	before	after	diff
securitySolution	9.3MB	9.3MB	-7.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
securitySolution	93.2KB	93.2KB	+64.0B

History

• 💛 Build #305571 was flaky 9ad9ce4
• 💛 Build #305231 was flaky 8103417
• 💔 Build #305059 failed b8e5987

cc @tomsonpl

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - [Cloud Security] Add Fleet Extensions for Cloud Asset Discovery to Enable Custom Onboarding UI (#219001) - [AI4SOC] AI settings page (#217373)

Manual backport

To create the backport manually run:

node scripts/backport --pr 222504

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222504 locally
cc: @tomsonpl