[Security Solution] [Ai Assistant] Enable the Global Security AI assistant by KDKHD · Pull Request #226556 · elastic/kibana

KDKHD · 2025-07-04T09:54:44Z

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Modify AI assistant visibility settings to allow for the Security AI assistant to be global.

This fixes an issue in the product that several users have raised. It is very unintuitive for them that when in the Security Solution view, they can not open the AI assistant when in the Discover page.

Users couldn’t add the AI Assistant to the Discover flyout and hadn’t been able to resolve it for weeks

Changes:

Add "Security" as an option in the aiAssistant:preferredAIAssistantType setting (this is the setting used in stateful Kibana to determine assistant visibility).
Modify setting labels and options inside of serverless oblt and serverless security to be relevant to the project type.

Screenshots

Stateful

The same setting is used across all solution views in stateful Kibana. This is not a perfect solution, as when a user is in the Security solution, they can technically still select the Oblt assistant (in this case no assistant will be shown). In the next minor release, this will be fixed with a new AI assistant settings page.

Classic

Oblt

Security

ES

Serverless Security

Serverless Oblt

Serverless ES

In serverless ES there is no ability to change the visibility of the AI assistant. This is the current behaviour and this has not changed in this PR.

How to test:

Stateful

Start Kibana (in classic/traditional flavour)

// Start ES
yarn es snapshot --license trial -E xpack.security.authc.api_key.enabled=true
// Start Kibana
yarn start --no-base-path

Create spaces for Classic, Security, Oblt and Search
In Classic, go to Stack Management > Advanced Settings and search for AI Assistant visibility
Verify that when selecting:
- Only in their solutions -> only displays the Search/Oblt and Security Assistants in their respective solutions.
- Observability and Search AI Assistants in other apps -> Shows the Oblt and Search assistant on the Discover page.
- Security AI Assistants in other apps -> Shows the Security assistant on the Discover page.
- Hide all assistants -> Does not show assistants anywhere

Stateless

Start Kibana (in serverless)

// Start ES
node scripts/es serverless --projectType security
// Start Kibana
node --no-experimental-require-module scripts/kibana --dev --serverless=security --no-base-path

(please try try different project types too. Instead of security you can use oblt or es )

Go to stack management > advanced settings and search for AI Assistant visibility
Check that the options you have available look like this:

Verify that when you select security, the Security assistant appears everywhere (including Discover)

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Documentation was added for features that require explanation or tutorials
Unit or functional tests were updated or added to match the most common scenarios
If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
Flaky Test Runner was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

See some risk examples
...

KDKHD · 2025-07-04T09:55:41Z

/ci

…no-cache --fix'

KDKHD · 2025-07-04T10:59:25Z

/ci

KDKHD · 2025-07-04T11:10:36Z

/ci

KDKHD · 2025-07-04T12:36:06Z

/ci

KDKHD · 2025-07-04T13:38:19Z

/ci

KDKHD · 2025-07-04T14:59:54Z

/ci

…no-cache --fix'

KDKHD · 2025-07-04T15:50:00Z

/ci

KDKHD · 2025-07-04T15:50:04Z

/ci

KDKHD · 2025-07-04T18:56:59Z

/ci

KDKHD · 2025-07-04T19:33:21Z

/ci

…no-cache --fix'

KDKHD · 2025-07-05T16:25:13Z

/ci

KDKHD · 2025-07-07T08:52:40Z

/ci

KDKHD · 2025-07-07T09:51:02Z

/ci

KDKHD · 2025-07-07T11:03:48Z

/ci

…no-cache --fix'

dgieselaar · 2025-07-12T08:29:41Z

...form/plugins/shared/ai_assistant_management/selection/server/src/settings/classic_setting.ts

+      defaultMessage:
+        'Choose where and which AI Assistants are available. You can limit the AI Assistants to their own solutions, show either the Observability and Search AI Assistants or the Security AI Assistant in other Kibana apps, or hide AI Assistants entirely.',
+    }


should we clarify here what happens when a solution has been selected for the current space?

dgieselaar · 2025-07-12T08:32:18Z

src/platform/plugins/shared/ai_assistant_management/selection/server/plugin.test.ts

+import { securitySolutionSetting } from './src/settings/security_setting';
+import { AIAssistantManagementSelectionPlugin } from './plugin';
+
+describe('plugin', () => {


total nit and ignore it for this PR, but the amount of mocking in this test files and others are probably an indication that the readability/testability of this would improve by moving the logic into a separate function

KDKHD · 2025-07-13T23:09:19Z

@elasticmachine merge upstream

elasticmachine · 2025-07-14T00:09:05Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: ca7d014
Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-226556-ca7d014528f8

Failed CI Steps

Test Failures

[job] [logs] FTR Configs #2 / Embeddable Alerts Table Embeddable alerts panel "before all" hook for "should only show alerts from the observability area (o11y+stack) when selecting it"
[job] [logs] FTR Configs #2 / Embeddable Alerts Table Embeddable alerts panel "before all" hook for "should only show alerts from the observability area (o11y+stack) when selecting it"

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.8MB	9.8MB	-635.0B

Page load bundle

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

id	before	after	diff
`aiAssistantManagementSelection`	5.4KB	5.4KB	+22.0B
`elasticAssistant`	262.7KB	263.1KB	+369.0B
`observabilityAIAssistantApp`	16.5KB	16.5KB	+21.0B
`securitySolution`	94.4KB	94.3KB	-42.0B
total			+370.0B

History

💛 Build #318439 was flaky 3f30501
💚 Build #318305 succeeded bcdb480
💔 Build #318258 failed 6ee467d
💔 Build #318070 failed 1111b70

maximpn

Rule Management Area LGTM

kibanamachine · 2025-07-14T09:23:55Z

Starting backport for target branches: 8.19, 9.1

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

kibanamachine · 2025-07-14T09:30:23Z

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts
❌	9.1	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 226556

Questions ?

Please refer to the Backport tool documentation

…stant (elastic#226556) ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. Modify AI assistant visibility settings to allow for the Security AI assistant to be global. This fixes an issue in the product that several users have raised. It is very unintuitive for them that when in the Security Solution view, they can not open the AI assistant when in the Discover page. > Users couldn’t add the AI Assistant to the Discover flyout and hadn’t been able to resolve it for weeks Changes: - Add "Security" as an option in the `aiAssistant:preferredAIAssistantType` setting (this is the setting used in stateful Kibana to determine assistant visibility). - Modify setting labels and options inside of serverless oblt and serverless security to be relevant to the project type. ### Screenshots <details> <summary>Stateful</summary> The same setting is used across all solution views in stateful Kibana. This is not a perfect solution, as when a user is in the Security solution, they can technically still select the Oblt assistant (in this case no assistant will be shown). In the next minor release, this will be fixed with a new AI assistant settings page. ### Classic <img width="1840" alt="image" src="https://github.com/user-attachments/assets/d601eb42-60a9-40ff-922c-0369249f2b70" /> ### Oblt <img width="1840" alt="image" src="https://github.com/user-attachments/assets/04a167f3-d55a-4ff7-bdfe-10cc21b0a9cf" /> ### Security <img width="1840" alt="image" src="https://github.com/user-attachments/assets/23d055e6-c1dc-4335-8e9e-0d805215cadf" /> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/20d37509-73da-4f23-9020-b089ee249af9" /> ### ES <img width="1840" alt="image" src="https://github.com/user-attachments/assets/21b34bb7-d540-4411-84f8-7e2f95942378" /> </details> <details> <summary>Serverless Security</summary> ![image](https://github.com/user-attachments/assets/45111617-ddcc-4b77-93f5-47131175c530) ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) </details> <details> <summary>Serverless Oblt</summary> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/53c14d2c-3f78-430b-8198-139f59c3a268" /> </details> <details> <summary>Serverless ES</summary> In serverless ES there is no ability to change the visibility of the AI assistant. This is the current behaviour and this has not changed in this PR. ![image](https://github.com/user-attachments/assets/6f79a349-9530-4278-821d-38240c001b2a) </details> ### How to test: #### Stateful - Start Kibana (in classic/traditional flavour) ``` // Start ES yarn es snapshot --license trial -E xpack.security.authc.api_key.enabled=true // Start Kibana yarn start --no-base-path ``` - Create spaces for Classic, Security, Oblt and Search - In Classic, go to Stack Management > Advanced Settings and search for AI Assistant visibility - Verify that when selecting: - Only in their solutions -> only displays the Search/Oblt and Security Assistants in their respective solutions. - Observability and Search AI Assistants in other apps -> Shows the Oblt and Search assistant on the Discover page. - Security AI Assistants in other apps -> Shows the Security assistant on the Discover page. - Hide all assistants -> Does not show assistants anywhere #### Stateless - Start Kibana (in serverless) ``` // Start ES node scripts/es serverless --projectType security // Start Kibana node --no-experimental-require-module scripts/kibana --dev --serverless=security --no-base-path ``` (please try try different project types too. Instead of security you can use `oblt` or `es` ) - Go to stack management > advanced settings and search for AI Assistant visibility - Check that the options you have available look like this: ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) - Verify that when you select security, the Security assistant appears everywhere (including Discover) ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [X] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [X] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [X] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Ievgen Sorokopud <e40pud@gmail.com> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> (cherry picked from commit 6536c76) # Conflicts: # src/platform/plugins/shared/ai_assistant_management/selection/server/plugin.ts

KDKHD · 2025-07-14T09:48:17Z

💚 All backports created successfully

Status	Branch	Result
✅	9.1
✅	8.19

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

Questions ?

Please refer to the Backport tool documentation

…stant (elastic#226556) ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. Modify AI assistant visibility settings to allow for the Security AI assistant to be global. This fixes an issue in the product that several users have raised. It is very unintuitive for them that when in the Security Solution view, they can not open the AI assistant when in the Discover page. > Users couldn’t add the AI Assistant to the Discover flyout and hadn’t been able to resolve it for weeks Changes: - Add "Security" as an option in the `aiAssistant:preferredAIAssistantType` setting (this is the setting used in stateful Kibana to determine assistant visibility). - Modify setting labels and options inside of serverless oblt and serverless security to be relevant to the project type. ### Screenshots <details> <summary>Stateful</summary> The same setting is used across all solution views in stateful Kibana. This is not a perfect solution, as when a user is in the Security solution, they can technically still select the Oblt assistant (in this case no assistant will be shown). In the next minor release, this will be fixed with a new AI assistant settings page. ### Classic <img width="1840" alt="image" src="https://github.com/user-attachments/assets/d601eb42-60a9-40ff-922c-0369249f2b70" /> ### Oblt <img width="1840" alt="image" src="https://github.com/user-attachments/assets/04a167f3-d55a-4ff7-bdfe-10cc21b0a9cf" /> ### Security <img width="1840" alt="image" src="https://github.com/user-attachments/assets/23d055e6-c1dc-4335-8e9e-0d805215cadf" /> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/20d37509-73da-4f23-9020-b089ee249af9" /> ### ES <img width="1840" alt="image" src="https://github.com/user-attachments/assets/21b34bb7-d540-4411-84f8-7e2f95942378" /> </details> <details> <summary>Serverless Security</summary> ![image](https://github.com/user-attachments/assets/45111617-ddcc-4b77-93f5-47131175c530) ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) </details> <details> <summary>Serverless Oblt</summary> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/53c14d2c-3f78-430b-8198-139f59c3a268" /> </details> <details> <summary>Serverless ES</summary> In serverless ES there is no ability to change the visibility of the AI assistant. This is the current behaviour and this has not changed in this PR. ![image](https://github.com/user-attachments/assets/6f79a349-9530-4278-821d-38240c001b2a) </details> ### How to test: #### Stateful - Start Kibana (in classic/traditional flavour) ``` // Start ES yarn es snapshot --license trial -E xpack.security.authc.api_key.enabled=true // Start Kibana yarn start --no-base-path ``` - Create spaces for Classic, Security, Oblt and Search - In Classic, go to Stack Management > Advanced Settings and search for AI Assistant visibility - Verify that when selecting: - Only in their solutions -> only displays the Search/Oblt and Security Assistants in their respective solutions. - Observability and Search AI Assistants in other apps -> Shows the Oblt and Search assistant on the Discover page. - Security AI Assistants in other apps -> Shows the Security assistant on the Discover page. - Hide all assistants -> Does not show assistants anywhere #### Stateless - Start Kibana (in serverless) ``` // Start ES node scripts/es serverless --projectType security // Start Kibana node --no-experimental-require-module scripts/kibana --dev --serverless=security --no-base-path ``` (please try try different project types too. Instead of security you can use `oblt` or `es` ) - Go to stack management > advanced settings and search for AI Assistant visibility - Check that the options you have available look like this: ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) - Verify that when you select security, the Security assistant appears everywhere (including Discover) ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [X] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [X] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [X] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Ievgen Sorokopud <e40pud@gmail.com> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> (cherry picked from commit 6536c76) # Conflicts: # config/serverless.security.yml # src/platform/packages/shared/serverless/settings/security_project/index.ts # src/platform/plugins/shared/ai_assistant_management/selection/server/plugin.ts

…I assistant (#226556) (#227772) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556)](#226556)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

…AI assistant (#226556) (#227775) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556)](#226556)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…stant (elastic#226556) ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. Modify AI assistant visibility settings to allow for the Security AI assistant to be global. This fixes an issue in the product that several users have raised. It is very unintuitive for them that when in the Security Solution view, they can not open the AI assistant when in the Discover page. > Users couldn’t add the AI Assistant to the Discover flyout and hadn’t been able to resolve it for weeks Changes: - Add "Security" as an option in the `aiAssistant:preferredAIAssistantType` setting (this is the setting used in stateful Kibana to determine assistant visibility). - Modify setting labels and options inside of serverless oblt and serverless security to be relevant to the project type. ### Screenshots <details> <summary>Stateful</summary> The same setting is used across all solution views in stateful Kibana. This is not a perfect solution, as when a user is in the Security solution, they can technically still select the Oblt assistant (in this case no assistant will be shown). In the next minor release, this will be fixed with a new AI assistant settings page. ### Classic <img width="1840" alt="image" src="https://github.com/user-attachments/assets/d601eb42-60a9-40ff-922c-0369249f2b70" /> ### Oblt <img width="1840" alt="image" src="https://github.com/user-attachments/assets/04a167f3-d55a-4ff7-bdfe-10cc21b0a9cf" /> ### Security <img width="1840" alt="image" src="https://github.com/user-attachments/assets/23d055e6-c1dc-4335-8e9e-0d805215cadf" /> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/20d37509-73da-4f23-9020-b089ee249af9" /> ### ES <img width="1840" alt="image" src="https://github.com/user-attachments/assets/21b34bb7-d540-4411-84f8-7e2f95942378" /> </details> <details> <summary>Serverless Security</summary> ![image](https://github.com/user-attachments/assets/45111617-ddcc-4b77-93f5-47131175c530) ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) </details> <details> <summary>Serverless Oblt</summary> <img width="1840" alt="image" src="https://github.com/user-attachments/assets/53c14d2c-3f78-430b-8198-139f59c3a268" /> </details> <details> <summary>Serverless ES</summary> In serverless ES there is no ability to change the visibility of the AI assistant. This is the current behaviour and this has not changed in this PR. ![image](https://github.com/user-attachments/assets/6f79a349-9530-4278-821d-38240c001b2a) </details> ### How to test: #### Stateful - Start Kibana (in classic/traditional flavour) ``` // Start ES yarn es snapshot --license trial -E xpack.security.authc.api_key.enabled=true // Start Kibana yarn start --no-base-path ``` - Create spaces for Classic, Security, Oblt and Search - In Classic, go to Stack Management > Advanced Settings and search for AI Assistant visibility - Verify that when selecting: - Only in their solutions -> only displays the Search/Oblt and Security Assistants in their respective solutions. - Observability and Search AI Assistants in other apps -> Shows the Oblt and Search assistant on the Discover page. - Security AI Assistants in other apps -> Shows the Security assistant on the Discover page. - Hide all assistants -> Does not show assistants anywhere #### Stateless - Start Kibana (in serverless) ``` // Start ES node scripts/es serverless --projectType security // Start Kibana node --no-experimental-require-module scripts/kibana --dev --serverless=security --no-base-path ``` (please try try different project types too. Instead of security you can use `oblt` or `es` ) - Go to stack management > advanced settings and search for AI Assistant visibility - Check that the options you have available look like this: ![image](https://github.com/user-attachments/assets/85dcc3dd-30d2-4c3f-b624-f57032f532ae) - Verify that when you select security, the Security assistant appears everywhere (including Discover) ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [X] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [X] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [X] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Ievgen Sorokopud <e40pud@gmail.com> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>

AI assistant settings

20ef929

kibanamachine added 2 commits July 4, 2025 10:18

[CI] Auto-commit changed files from 'node scripts/notice'

85d9f82

[CI] Auto-commit changed files from 'node scripts/eslint_all_files --…

613a18f

…no-cache --fix'

[CI] Auto-commit changed files from 'node scripts/notice'

b8c5ef4

quick checks

a903f57

fix

93dc35f

fix

5cedac8

[CI] Auto-commit changed files from 'node scripts/eslint_all_files --…

afad27f

…no-cache --fix'

fix tests

9935916

[CI] Auto-commit changed files from 'node scripts/yarn_deduplicate'

b85907f

[CI] Auto-commit changed files from 'node scripts/eslint_all_files --…

6be6904

…no-cache --fix'

fix tests

fcdcff6

lint

58e3ef9

KDKHD force-pushed the bug/security_ai_assistant_global_setting-4 branch from 2d03dcc to 58e3ef9 Compare July 7, 2025 09:50

lint

3fd9e90

lint

53fd067

KDKHD and others added 4 commits July 11, 2025 15:55

lint

4396348

add unit test

de3eabf

add comment

1d96a00

[CI] Auto-commit changed files from 'node scripts/eslint_all_files --…

bcdb480

…no-cache --fix'

KDKHD mentioned this pull request Jul 11, 2025

[Serverless ES][AI Assistant] AI visibility settings issues #227695

Closed

dgieselaar added 4 commits July 12, 2025 10:06

Make sure left nav controls visibility of Obs/Search assistant

1c231c1

Don't show Assistant by default

2eef641

Add/update tests

1f699d8

Link to GH issue

3f30501

dgieselaar reviewed Jul 12, 2025

View reviewed changes

dgieselaar approved these changes Jul 12, 2025

View reviewed changes

Merge branch 'main' into bug/security_ai_assistant_global_setting-4

ca7d014

KDKHD mentioned this pull request Jul 14, 2025

[Security Solution] [Security Solution][AI assistant] Unify AI assistant nav control button #227765

Open

maximpn approved these changes Jul 14, 2025

View reviewed changes

KDKHD added the v9.2.0 label Jul 14, 2025

KDKHD merged commit 6536c76 into elastic:main Jul 14, 2025
14 of 15 checks passed

KDKHD mentioned this pull request Jul 14, 2025

[9.1] [Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556) #227772

Merged

KDKHD mentioned this pull request Jul 14, 2025

[8.19] [Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556) #227775

Merged

Conversation

KDKHD commented Jul 4, 2025 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots

Classic

Oblt

Security

ES

How to test:

Stateful

Stateless

Checklist

Identify risks

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 4, 2025

Uh oh!

KDKHD commented Jul 5, 2025

Uh oh!

KDKHD commented Jul 7, 2025

Uh oh!

KDKHD commented Jul 7, 2025

Uh oh!

KDKHD commented Jul 7, 2025

Uh oh!

dgieselaar Jul 12, 2025

Choose a reason for hiding this comment

Uh oh!

dgieselaar Jul 12, 2025

Choose a reason for hiding this comment

Uh oh!

KDKHD commented Jul 13, 2025

Uh oh!

elasticmachine commented Jul 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

Async chunks

Page load bundle

History

Uh oh!

maximpn left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Jul 14, 2025

Uh oh!

kibanamachine commented Jul 14, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

KDKHD commented Jul 14, 2025

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

KDKHD commented Jul 4, 2025 •

edited by kibanamachine

Loading

elasticmachine commented Jul 14, 2025 •

edited

Loading