# Backport
This will backport the following commits from `main` to `8.16`:
- [[Security Assistant] Move security AI assistant button into global
nav bar (#203060)](https://github.com/elastic/kibana/pull/203060)
<!--- Backport version: 8.9.8 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Kenneth
Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-08T10:03:54Z","message":"[Security
Assistant] Move security AI assistant button into global nav bar
(#203060)\n\n## Summary\r\n\r\nMore changes are needed within the
observability and search solution to\r\nclose the issue
fully.\r\n\r\nSummarise your PR. If it involves visual changes include a
screenshot or\r\ngif.\r\n\r\nMove the security AI assistant button from
the solution header bar into\r\nthe global nav bar. This is part of the
AI assistant unification\r\ninitiative.\r\n\r\n### How to Test\r\n-
Start kibana\r\n- Go to one of the security solution pages (e.g. attack
discovery)\r\n- AI assistant button should be in the global nav bar.
Clicking it opens\r\nthe assistant.\r\n\r\n- The button can also be
tested for security serverless deployment. It\r\nshould look like the
screenshot bellow.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies
following conditions. \r\n\r\nReviewers should verify this PR satisfies
this list as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for breaking HTTP API changes, and any breaking\r\nchanges have
been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [x] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\nClassic:\r\n\r\n\r\n\r\nOld:\r\n<img
width=\"1728\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef568c6-2d31-47da-8f5f-87dfdf10cb5c\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"06cf554981845fa2e1d9505952e559568d3e0479","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major","Feature:Security
Assistant","Team:Security Generative
AI"],"number":203060,"url":"https://github.com/elastic/kibana/pull/203060","mergeCommit":{"message":"[Security
Assistant] Move security AI assistant button into global nav bar
(#203060)\n\n## Summary\r\n\r\nMore changes are needed within the
observability and search solution to\r\nclose the issue
fully.\r\n\r\nSummarise your PR. If it involves visual changes include a
screenshot or\r\ngif.\r\n\r\nMove the security AI assistant button from
the solution header bar into\r\nthe global nav bar. This is part of the
AI assistant unification\r\ninitiative.\r\n\r\n### How to Test\r\n-
Start kibana\r\n- Go to one of the security solution pages (e.g. attack
discovery)\r\n- AI assistant button should be in the global nav bar.
Clicking it opens\r\nthe assistant.\r\n\r\n- The button can also be
tested for security serverless deployment. It\r\nshould look like the
screenshot bellow.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies
following conditions. \r\n\r\nReviewers should verify this PR satisfies
this list as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for breaking HTTP API changes, and any breaking\r\nchanges have
been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [x] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\nClassic:\r\n\r\n\r\n\r\nOld:\r\n<img
width=\"1728\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef568c6-2d31-47da-8f5f-87dfdf10cb5c\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"06cf554981845fa2e1d9505952e559568d3e0479"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203060","number":203060,"mergeCommit":{"message":"[Security
Assistant] Move security AI assistant button into global nav bar
(#203060)\n\n## Summary\r\n\r\nMore changes are needed within the
observability and search solution to\r\nclose the issue
fully.\r\n\r\nSummarise your PR. If it involves visual changes include a
screenshot or\r\ngif.\r\n\r\nMove the security AI assistant button from
the solution header bar into\r\nthe global nav bar. This is part of the
AI assistant unification\r\ninitiative.\r\n\r\n### How to Test\r\n-
Start kibana\r\n- Go to one of the security solution pages (e.g. attack
discovery)\r\n- AI assistant button should be in the global nav bar.
Clicking it opens\r\nthe assistant.\r\n\r\n- The button can also be
tested for security serverless deployment. It\r\nshould look like the
screenshot bellow.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies
following conditions. \r\n\r\nReviewers should verify this PR satisfies
this list as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for breaking HTTP API changes, and any breaking\r\nchanges have
been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [x] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\nClassic:\r\n\r\n\r\n\r\nOld:\r\n<img
width=\"1728\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef568c6-2d31-47da-8f5f-87dfdf10cb5c\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"06cf554981845fa2e1d9505952e559568d3e0479"}}]}]
BACKPORT-->
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Security Solution package
This package compiles components used by Security Solution
### Lazy by default
All components are exported to be lazily-loaded with a default `React.Suspense` default most appropriate to its nature.
If a page needs to alter the `React.Suspense` behavior, (e.g. a different "loading" component), one can import the `Lazy[ComponentName]` version and surround it with a custom `React.Suspense` component.
56aebad97e