Skip to content

Comments

[AI4DSOC] Add configurations integrations page#217905

Merged
kgeller merged 24 commits intoelastic:mainfrom
kgeller:add-integrations-pages
Apr 16, 2025
Merged

[AI4DSOC] Add configurations integrations page#217905
kgeller merged 24 commits intoelastic:mainfrom
kgeller:add-integrations-pages

Conversation

@kgeller
Copy link
Contributor

@kgeller kgeller commented Apr 10, 2025

Summary

Implements the curated Integrations management page for AI for the SOC:

  • Adds the new Integrations page utilizing the PackageListGrid exported fleet component
  • Paths of /configurations/integrations/browse and configurations/integrations/installed to be consistent with current fleet pages /integrations/browse and /integrations/installed
  • Updates the PackageCard to expose new settings options defaulted to the existing behavior
  • Updates the sidebar link order to match the tabs
Screenshot 2025-04-14 at 12 00 41 PM Screenshot 2025-04-14 at 12 00 55 PM Screenshot 2025-04-10 at 3 11 29 PM

How to test

  • Add the following to serverless.security.dev.yml:
    xpack.securitySolutionServerless.productTypes:
    [
      { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
    ]
    
  • Run Kibana serverless for security
  • Verify behavior matches the UX mockups: figma

Couple things to note:

  • some of the actual logos vary slightly from the figma, but UX has approved
  • if you want to actually install integrations in agentless, be sure to reference fleet docs for serverless and agentless. If you just want to get an idea of what it would look like installed without doing that, just navigate to the Settings tab on the integrations overview and install its assets

Relates: https://github.com/elastic/security-team/issues/11789

@kgeller kgeller added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Fleet Team label for Observability Data Collection Fleet team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Explore Team:Security Generative AI Security Generative AI v9.1.0 labels Apr 10, 2025
@kgeller kgeller self-assigned this Apr 10, 2025
@kgeller kgeller marked this pull request as ready for review April 11, 2025 13:07
@kgeller kgeller requested review from a team as code owners April 11, 2025 13:07
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

Copy link
Contributor

@PhilippeOberti PhilippeOberti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for creating the new common folder and files and updating our page accordingly!

Copy link
Contributor

@semd semd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's close this discussion before merging
#217905 (comment)

Copy link
Member

@nchaulet nchaulet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fleet changes 🚀

@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #3 / discover responsive sidebar search bar customization should not render CustomDataViewPicker
  • [job] [logs] Jest Tests #3 / discover responsive sidebar should not render buttons in data view picker when in viewer mode
  • [job] [logs] Jest Tests #3 / discover responsive sidebar should render "Edit field" button
  • [job] [logs] Jest Tests #3 / discover responsive sidebar should render buttons in data view picker correctly

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 7244 7253 +9

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
fleet 1391 1393 +2

Async chunks

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

id before after diff
fleet 1.7MB 1.7MB +72.0B
securitySolution 9.0MB 9.0MB +5.4KB
total +5.5KB
Unknown metric groups

API count

id before after diff
fleet 1519 1521 +2

History

cc @kgeller

@kgeller kgeller merged commit a63876b into elastic:main Apr 16, 2025
9 checks passed
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request Apr 17, 2025
## Summary

Implements the curated Integrations management page for AI for the SOC:

- Adds the new Integrations page utilizing the `PackageListGrid`
exported fleet component
- Paths of `/configurations/integrations/browse` and
`configurations/integrations/installed` to be consistent with current
fleet pages `/integrations/browse` and `/integrations/installed`
- Updates the `PackageCard` to expose new settings options defaulted to
the existing behavior
- Updates the sidebar link order to match the tabs

<img width="1722" alt="Screenshot 2025-04-14 at 12 00 41 PM"
src="https://github.com/user-attachments/assets/982e01b9-4ceb-4a1e-9cfe-4a44d2f9c8bf"
/>

<img width="1720" alt="Screenshot 2025-04-14 at 12 00 55 PM"
src="https://github.com/user-attachments/assets/401f37fe-791f-4f7c-b31f-f0d6b56f1b46"
/>

<img width="517" alt="Screenshot 2025-04-10 at 3 11 29 PM"
src="https://github.com/user-attachments/assets/f60e6eda-6750-40fb-8611-e73ef5d8fa91"
/>

## How to test

- Add the following to `serverless.security.dev.yml`:
  ```
  xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
  ```
- Run Kibana serverless for security
- Verify behavior matches the UX mockups:
[figma](https://www.figma.com/design/DYs7j4GQdAhg7aWTLI4R69/AI4DSOC?node-id=2969-143558&p=f&m=dev)

Couple things to note:
- some of the actual logos vary slightly from the figma, but UX has
approved
- if you want to actually install integrations in agentless, be sure to
reference fleet docs for [serverless
](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/developing_kibana_in_serverless.md)
and
[agentless](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/agentless.md).
If you just want to get an idea of what it would look like installed
without doing that, just navigate to the Settings tab on the
integrations overview and install its assets

Relates: elastic/security-team#11789
PhilippeOberti added a commit that referenced this pull request Apr 24, 2025
## Summary

This PR fixes the links to the integrations page, introduced in [this
PR](#215246) and [that
one](#215266). At the time of the
previous PRs, the new AI4DSOC integration page had not been created, so
we were using the link to the normal integrations page. [This recent
PR](#217905) added the new page,
so we need to update those links

From the landing page


https://github.com/user-attachments/assets/907c12be-84dc-4bbd-a161-c8b16e2ecdba

From the alert summary page


https://github.com/user-attachments/assets/c25be7b3-f7ef-4e5f-8948-40def6a8d026

## How to test

This needs to be ran in Serverless:
- `yarn es serverless --projectType security`
- `yarn serverless-security --no-base-path`

You also need to enable the AI for SOC tier, by adding the following to
your `serverless.security.dev.yaml` file:
```
xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
```

Use one of these Serverless users:
- `platform_engineer`
- `endpoint_operations_analyst`
- `endpoint_policy_manager`
- `admin`
- `system_indices_superuser`

Then:
- generate data: `yarn test:generate:serverless-dev`
- create 4 catch all rules, each with a name of a AI for SOC integration
(`google_secops`, `microsoft_sentinel`,, `sentinel_one` and
`crowdstrike`)
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_fetch_integrations.ts#L73)
to `installedPackages: availablePackages` to force having some packages
installed
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_integrations.ts#L63)
to `r.name === p.name` to make sure there will be matches between
integrations and rules

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Relates to elastic/security-team#11955
kgeller added a commit that referenced this pull request May 1, 2025
## Summary

Fixing the css settings for the AI4DSOC integrations cards so the cards
resize when the screen is narrow, instead of getting cut off.

## Screenshots

### Before
<img width="750" alt="Screenshot 2025-04-25 at 2 42 33 PM"
src="https://github.com/user-attachments/assets/2cb1033f-8998-4fd7-90ee-e7b6ce12c8ef"
/>

### After
<img width="750" alt="Screenshot 2025-04-25 at 2 39 25 PM"
src="https://github.com/user-attachments/assets/dbee50c9-2c90-455c-8dc7-f7cf102d299b"
/>

### Outside of AI4DSOC not impacted
<img width="750" alt="Screenshot 2025-04-25 at 2 33 25 PM"
src="https://github.com/user-attachments/assets/3b3961d5-4276-4da1-b046-3c8b0ac99bbe"
/>

### AI4DSOC when not narrow screen
<img width="750" alt="Screenshot 2025-04-25 at 2 50 44 PM"
src="https://github.com/user-attachments/assets/ff41c130-1691-4fae-baba-8b24e3641337"
/>

Relates 
- elastic/security-team#11789
- #217905
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
## Summary

Implements the curated Integrations management page for AI for the SOC:

- Adds the new Integrations page utilizing the `PackageListGrid`
exported fleet component
- Paths of `/configurations/integrations/browse` and
`configurations/integrations/installed` to be consistent with current
fleet pages `/integrations/browse` and `/integrations/installed`
- Updates the `PackageCard` to expose new settings options defaulted to
the existing behavior
- Updates the sidebar link order to match the tabs

<img width="1722" alt="Screenshot 2025-04-14 at 12 00 41 PM"
src="https://github.com/user-attachments/assets/982e01b9-4ceb-4a1e-9cfe-4a44d2f9c8bf"
/>

<img width="1720" alt="Screenshot 2025-04-14 at 12 00 55 PM"
src="https://github.com/user-attachments/assets/401f37fe-791f-4f7c-b31f-f0d6b56f1b46"
/>

<img width="517" alt="Screenshot 2025-04-10 at 3 11 29 PM"
src="https://github.com/user-attachments/assets/f60e6eda-6750-40fb-8611-e73ef5d8fa91"
/>

## How to test

- Add the following to `serverless.security.dev.yml`:
  ```
  xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
  ```
- Run Kibana serverless for security
- Verify behavior matches the UX mockups:
[figma](https://www.figma.com/design/DYs7j4GQdAhg7aWTLI4R69/AI4DSOC?node-id=2969-143558&p=f&m=dev)

Couple things to note:
- some of the actual logos vary slightly from the figma, but UX has
approved
- if you want to actually install integrations in agentless, be sure to
reference fleet docs for [serverless
](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/developing_kibana_in_serverless.md)
and
[agentless](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/agentless.md).
If you just want to get an idea of what it would look like installed
without doing that, just navigate to the Settings tab on the
integrations overview and install its assets

Relates: elastic/security-team#11789
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
## Summary

This PR fixes the links to the integrations page, introduced in [this
PR](elastic#215246) and [that
one](elastic#215266). At the time of the
previous PRs, the new AI4DSOC integration page had not been created, so
we were using the link to the normal integrations page. [This recent
PR](elastic#217905) added the new page,
so we need to update those links

From the landing page


https://github.com/user-attachments/assets/907c12be-84dc-4bbd-a161-c8b16e2ecdba

From the alert summary page


https://github.com/user-attachments/assets/c25be7b3-f7ef-4e5f-8948-40def6a8d026

## How to test

This needs to be ran in Serverless:
- `yarn es serverless --projectType security`
- `yarn serverless-security --no-base-path`

You also need to enable the AI for SOC tier, by adding the following to
your `serverless.security.dev.yaml` file:
```
xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
```

Use one of these Serverless users:
- `platform_engineer`
- `endpoint_operations_analyst`
- `endpoint_policy_manager`
- `admin`
- `system_indices_superuser`

Then:
- generate data: `yarn test:generate:serverless-dev`
- create 4 catch all rules, each with a name of a AI for SOC integration
(`google_secops`, `microsoft_sentinel`,, `sentinel_one` and
`crowdstrike`)
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_fetch_integrations.ts#L73)
to `installedPackages: availablePackages` to force having some packages
installed
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_integrations.ts#L63)
to `r.name === p.name` to make sure there will be matches between
integrations and rules

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Relates to elastic/security-team#11955
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
…c#219306)

## Summary

Fixing the css settings for the AI4DSOC integrations cards so the cards
resize when the screen is narrow, instead of getting cut off.

## Screenshots

### Before
<img width="750" alt="Screenshot 2025-04-25 at 2 42 33 PM"
src="https://github.com/user-attachments/assets/2cb1033f-8998-4fd7-90ee-e7b6ce12c8ef"
/>

### After
<img width="750" alt="Screenshot 2025-04-25 at 2 39 25 PM"
src="https://github.com/user-attachments/assets/dbee50c9-2c90-455c-8dc7-f7cf102d299b"
/>

### Outside of AI4DSOC not impacted
<img width="750" alt="Screenshot 2025-04-25 at 2 33 25 PM"
src="https://github.com/user-attachments/assets/3b3961d5-4276-4da1-b046-3c8b0ac99bbe"
/>

### AI4DSOC when not narrow screen
<img width="750" alt="Screenshot 2025-04-25 at 2 50 44 PM"
src="https://github.com/user-attachments/assets/ff41c130-1691-4fae-baba-8b24e3641337"
/>

Relates 
- elastic/security-team#11789
- elastic#217905
PhilippeOberti added a commit to PhilippeOberti/kibana that referenced this pull request May 30, 2025
## Summary

This PR fixes the links to the integrations page, introduced in [this
PR](elastic#215246) and [that
one](elastic#215266). At the time of the
previous PRs, the new AI4DSOC integration page had not been created, so
we were using the link to the normal integrations page. [This recent
PR](elastic#217905) added the new page,
so we need to update those links

From the landing page

https://github.com/user-attachments/assets/907c12be-84dc-4bbd-a161-c8b16e2ecdba

From the alert summary page

https://github.com/user-attachments/assets/c25be7b3-f7ef-4e5f-8948-40def6a8d026

## How to test

This needs to be ran in Serverless:
- `yarn es serverless --projectType security`
- `yarn serverless-security --no-base-path`

You also need to enable the AI for SOC tier, by adding the following to
your `serverless.security.dev.yaml` file:
```
xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
```

Use one of these Serverless users:
- `platform_engineer`
- `endpoint_operations_analyst`
- `endpoint_policy_manager`
- `admin`
- `system_indices_superuser`

Then:
- generate data: `yarn test:generate:serverless-dev`
- create 4 catch all rules, each with a name of a AI for SOC integration
(`google_secops`, `microsoft_sentinel`,, `sentinel_one` and
`crowdstrike`)
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_fetch_integrations.ts#L73)
to `installedPackages: availablePackages` to force having some packages
installed
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_integrations.ts#L63)
to `r.name === p.name` to make sure there will be matches between
integrations and rules

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Relates to elastic/security-team#11955

(cherry picked from commit 10cfa31)
PhilippeOberti added a commit to PhilippeOberti/kibana that referenced this pull request May 30, 2025
## Summary

This PR fixes the links to the integrations page, introduced in [this
PR](elastic#215246) and [that
one](elastic#215266). At the time of the
previous PRs, the new AI4DSOC integration page had not been created, so
we were using the link to the normal integrations page. [This recent
PR](elastic#217905) added the new page,
so we need to update those links

From the landing page

https://github.com/user-attachments/assets/907c12be-84dc-4bbd-a161-c8b16e2ecdba

From the alert summary page

https://github.com/user-attachments/assets/c25be7b3-f7ef-4e5f-8948-40def6a8d026

## How to test

This needs to be ran in Serverless:
- `yarn es serverless --projectType security`
- `yarn serverless-security --no-base-path`

You also need to enable the AI for SOC tier, by adding the following to
your `serverless.security.dev.yaml` file:
```
xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
```

Use one of these Serverless users:
- `platform_engineer`
- `endpoint_operations_analyst`
- `endpoint_policy_manager`
- `admin`
- `system_indices_superuser`

Then:
- generate data: `yarn test:generate:serverless-dev`
- create 4 catch all rules, each with a name of a AI for SOC integration
(`google_secops`, `microsoft_sentinel`,, `sentinel_one` and
`crowdstrike`)
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_fetch_integrations.ts#L73)
to `installedPackages: availablePackages` to force having some packages
installed
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_integrations.ts#L63)
to `r.name === p.name` to make sure there will be matches between
integrations and rules

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Relates to elastic/security-team#11955

(cherry picked from commit 10cfa31)
angorayc pushed a commit to angorayc/kibana that referenced this pull request Jun 3, 2025
Implements the curated Integrations management page for AI for the SOC:

- Adds the new Integrations page utilizing the `PackageListGrid`
exported fleet component
- Paths of `/configurations/integrations/browse` and
`configurations/integrations/installed` to be consistent with current
fleet pages `/integrations/browse` and `/integrations/installed`
- Updates the `PackageCard` to expose new settings options defaulted to
the existing behavior
- Updates the sidebar link order to match the tabs

<img width="1722" alt="Screenshot 2025-04-14 at 12 00 41 PM"
src="https://github.com/user-attachments/assets/982e01b9-4ceb-4a1e-9cfe-4a44d2f9c8bf"
/>

<img width="1720" alt="Screenshot 2025-04-14 at 12 00 55 PM"
src="https://github.com/user-attachments/assets/401f37fe-791f-4f7c-b31f-f0d6b56f1b46"
/>

<img width="517" alt="Screenshot 2025-04-10 at 3 11 29 PM"
src="https://github.com/user-attachments/assets/f60e6eda-6750-40fb-8611-e73ef5d8fa91"
/>

- Add the following to `serverless.security.dev.yml`:
  ```
  xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
  ```
- Run Kibana serverless for security
- Verify behavior matches the UX mockups:
[figma](https://www.figma.com/design/DYs7j4GQdAhg7aWTLI4R69/AI4DSOC?node-id=2969-143558&p=f&m=dev)

Couple things to note:
- some of the actual logos vary slightly from the figma, but UX has
approved
- if you want to actually install integrations in agentless, be sure to
reference fleet docs for [serverless
](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/developing_kibana_in_serverless.md)
and
[agentless](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/agentless.md).
If you just want to get an idea of what it would look like installed
without doing that, just navigate to the Settings tab on the
integrations overview and install its assets

Relates: elastic/security-team#11789
(cherry picked from commit a63876b)
angorayc added a commit that referenced this pull request Jun 3, 2025
## Summary

# Backport

This will backport the following commits from `main` to `8.19`:
- [New onboarding
hub(#217905)](#217905)

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

Co-authored-by: Kylie Meli <kylie.geller@elastic.co>
qn895 pushed a commit to qn895/kibana that referenced this pull request Jun 3, 2025
…c#219306)

## Summary

Fixing the css settings for the AI4DSOC integrations cards so the cards
resize when the screen is narrow, instead of getting cut off.

## Screenshots

### Before
<img width="750" alt="Screenshot 2025-04-25 at 2 42 33 PM"
src="https://github.com/user-attachments/assets/2cb1033f-8998-4fd7-90ee-e7b6ce12c8ef"
/>

### After
<img width="750" alt="Screenshot 2025-04-25 at 2 39 25 PM"
src="https://github.com/user-attachments/assets/dbee50c9-2c90-455c-8dc7-f7cf102d299b"
/>

### Outside of AI4DSOC not impacted
<img width="750" alt="Screenshot 2025-04-25 at 2 33 25 PM"
src="https://github.com/user-attachments/assets/3b3961d5-4276-4da1-b046-3c8b0ac99bbe"
/>

### AI4DSOC when not narrow screen
<img width="750" alt="Screenshot 2025-04-25 at 2 50 44 PM"
src="https://github.com/user-attachments/assets/ff41c130-1691-4fae-baba-8b24e3641337"
/>

Relates 
- elastic/security-team#11789
- elastic#217905
kgeller added a commit to kgeller/kibana that referenced this pull request Jun 4, 2025
…c#219306)

## Summary

Fixing the css settings for the AI4DSOC integrations cards so the cards
resize when the screen is narrow, instead of getting cut off.

## Screenshots

### Before
<img width="750" alt="Screenshot 2025-04-25 at 2 42 33 PM"
src="https://github.com/user-attachments/assets/2cb1033f-8998-4fd7-90ee-e7b6ce12c8ef"
/>

### After
<img width="750" alt="Screenshot 2025-04-25 at 2 39 25 PM"
src="https://github.com/user-attachments/assets/dbee50c9-2c90-455c-8dc7-f7cf102d299b"
/>

### Outside of AI4DSOC not impacted
<img width="750" alt="Screenshot 2025-04-25 at 2 33 25 PM"
src="https://github.com/user-attachments/assets/3b3961d5-4276-4da1-b046-3c8b0ac99bbe"
/>

### AI4DSOC when not narrow screen
<img width="750" alt="Screenshot 2025-04-25 at 2 50 44 PM"
src="https://github.com/user-attachments/assets/ff41c130-1691-4fae-baba-8b24e3641337"
/>

Relates
- elastic/security-team#11789
- elastic#217905

(cherry picked from commit 6516cff)

# Conflicts:
#	x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/components/package_card.tsx
PhilippeOberti added a commit to PhilippeOberti/kibana that referenced this pull request Jun 4, 2025
## Summary

This PR fixes the links to the integrations page, introduced in [this
PR](elastic#215246) and [that
one](elastic#215266). At the time of the
previous PRs, the new AI4DSOC integration page had not been created, so
we were using the link to the normal integrations page. [This recent
PR](elastic#217905) added the new page,
so we need to update those links

From the landing page

https://github.com/user-attachments/assets/907c12be-84dc-4bbd-a161-c8b16e2ecdba

From the alert summary page

https://github.com/user-attachments/assets/c25be7b3-f7ef-4e5f-8948-40def6a8d026

## How to test

This needs to be ran in Serverless:
- `yarn es serverless --projectType security`
- `yarn serverless-security --no-base-path`

You also need to enable the AI for SOC tier, by adding the following to
your `serverless.security.dev.yaml` file:
```
xpack.securitySolutionServerless.productTypes:
  [
    { product_line: 'ai_soc', product_tier: 'search_ai_lake' },
  ]
```

Use one of these Serverless users:
- `platform_engineer`
- `endpoint_operations_analyst`
- `endpoint_policy_manager`
- `admin`
- `system_indices_superuser`

Then:
- generate data: `yarn test:generate:serverless-dev`
- create 4 catch all rules, each with a name of a AI for SOC integration
(`google_secops`, `microsoft_sentinel`,, `sentinel_one` and
`crowdstrike`)
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_fetch_integrations.ts#L73)
to `installedPackages: availablePackages` to force having some packages
installed
- change [this
line](https://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alert_summary/use_integrations.ts#L63)
to `r.name === p.name` to make sure there will be matches between
integrations and rules

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Relates to elastic/security-team#11955

(cherry picked from commit 10cfa31)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team Team:Security Generative AI Security Generative AI Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants