[9.1] [Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556)#227772
Merged
KDKHD merged 3 commits intoelastic:9.1from Jul 14, 2025
Merged
[9.1] [Security Solution] [Ai Assistant] Enable the Global Security AI assistant (#226556)#227772KDKHD merged 3 commits intoelastic:9.1from
KDKHD merged 3 commits intoelastic:9.1from
Conversation
…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>   </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.  </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:  - 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
botelastic
bot
added
the
ci:project-deploy-observability
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
10 tasks
e40pud
approved these changes
Jul 14, 2025
Contributor
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto9.1:Questions ?
Please refer to the Backport tool documentation