[Security Solution] Discover Security Profile Changes + Event timeline redirection by logeekal · Pull Request #204756 · elastic/kibana

logeekal · 2024-12-18T13:18:06Z

Summary

This PR customized Discover's Security Root Profile with 3 new changes. \

With this change Discover's Security profile ceases to be experimental. Below are the changes listed one in this profile.

Note

This change also removes the Flyout changes that were added for security solution to the Discover's security profile.

Row Indicators.

Adds row indicators based on Alert or an event as shown in the screenshot below. Note the highlights on the left of the row.

Yellow for Alerts.
Gray for Events.

Default list of Columns.

Adds the list of default columns that should appear when security profile is activated.

Explore in Security Flyout.

As shown the demo below, this action explores and event or an alert in security solution as shown in the screenshot below.

Screen.Recording.2025-06-20.at.19.00.27.mov

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
Unit or functional tests were updated or added to match the most common scenarios

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
...

kibanamachine · 2024-12-18T14:31:28Z

PR Project deployment started at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/214

kibanamachine · 2024-12-18T15:12:44Z

Project deployed, see credentials at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/214

kibanamachine · 2024-12-19T12:00:40Z

PR Project deployment started at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/217

kibanamachine · 2024-12-19T12:40:49Z

Project deployed, see credentials at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/217

x-pack/solutions/security/plugins/security_solution/public/common/hooks/use_url_state.ts

pmuellr · 2025-03-07T02:21:20Z

Just noting that I contacted @logeekal via Slack about the project created from this PR which is currently having some difficulties, in case anyone else lands here since the project name has the PR number in it :-)

Fix failing tests after enabling security root profile

elasticmachine · 2025-06-24T00:40:34Z

💚 Build Succeeded

Buildkite Build
Commit: e2874dc

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`discover`	1323	1334	+11
`securitySolution`	7674	7673	-1
total			+10

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
`securitySolution`	130	129	-1

Async chunks

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

id	before	after	diff
`discover`	1.1MB	1.1MB	+12.2KB
`securitySolution`	9.4MB	9.4MB	+11.4KB
total			+23.6KB

Page load bundle

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

id	before	after	diff
`discover`	21.8KB	21.9KB	+57.0B
`securitySolution`	95.4KB	94.5KB	-887.0B
total			-830.0B

Unknown metric groups

API count

id	before	after	diff
`securitySolution`	199	198	-1

async chunk count

id	before	after	diff
`discover`	36	37	+1
`securitySolution`	106	105	-1
total			-0

History

kibanamachine · 2025-06-24T00:58:39Z

Starting backport for target branches: 8.19

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

kibanamachine · 2025-06-24T00:58:40Z

Starting backport for target branches: 8.19

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

kibanamachine · 2025-06-24T01:04:47Z

💔 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: - [AI4DSOC] Fix cases capability used in Security navbar (#222504) - [Cloud Security] Add Fleet Extensions for Cloud Asset Discovery to Enable Custom Onboarding UI (#219001)

Manual backport

To create the backport manually run:

node scripts/backport --pr 204756

Questions ?

Please refer to the Backport tool documentation

kibanamachine · 2025-06-24T01:04:48Z

💔 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: - [AI4DSOC] Fix cases capability used in Security navbar (#222504) - [Cloud Security] Add Fleet Extensions for Cloud Asset Discovery to Enable Custom Onboarding UI (#219001)

Manual backport

To create the backport manually run:

node scripts/backport --pr 204756

Questions ?

Please refer to the Backport tool documentation

logeekal · 2025-06-24T01:39:44Z

💚 All backports created successfully

Status	Branch	Result
✅	8.19

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

Questions ?

Please refer to the Backport tool documentation

…e redirection (elastic#204756) ## Summary This PR customized Discover's Security Root Profile with 3 new changes. \ With this change Discover's Security profile ceases to be `experimental`. Below are the changes listed one in this profile. >[!Note] > This change also removes the Flyout changes that were added for security solution to the Discover's security profile. ### Row Indicators. Adds row indicators based on Alert or an event as shown in the screenshot below. Note the highlights on the left of the row. `Yellow` for Alerts. `Gray` for Events. ![image](https://github.com/user-attachments/assets/697bafe9-3c45-4926-9b00-4bf6453e70eb) ### Default list of Columns. Adds the list of default columns that should appear when security profile is activated. ![image](https://github.com/user-attachments/assets/71647f3e-37da-4fab-b350-baa567b7e9bd) ### Explore in Security Flyout. As shown the demo below, this action explores and event or an alert in security solution as shown in the screenshot below. https://github.com/user-attachments/assets/4c228bb1-60af-433b-8e8f-1a5d4d049985 ### 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/packages/kbn-i18n/README.md) - [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 ### 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: Davis McPhee <davis.mcphee@elastic.co> (cherry picked from commit fbec7db) # Conflicts: # src/platform/plugins/shared/discover/public/context_awareness/profile_providers/security/accessors/create_app_wrapper_accessor.ts # src/platform/plugins/shared/discover/public/context_awareness/profile_providers/security/constants.ts # src/platform/plugins/shared/discover/public/context_awareness/profile_providers/security/security_root_profile/profile.tsx # src/platform/plugins/shared/discover/tsconfig.json # src/plugins/discover/public/context_awareness/profile_providers/security/accessors/create_app_wrapper_accessor.ts # src/plugins/discover/public/context_awareness/profile_providers/security/accessors/get_default_app_state.test.ts # src/plugins/discover/public/context_awareness/profile_providers/security/accessors/get_default_app_state.ts # src/plugins/discover/public/context_awareness/profile_providers/security/accessors/get_row_indicator.test.ts # src/plugins/discover/public/context_awareness/profile_providers/security/accessors/get_row_indicator.ts # x-pack/plugins/security_solution/public/one_discover/app_wrapper/index.tsx # x-pack/solutions/security/plugins/security_solution/public/common/hooks/timeline/use_sync_timeline_url_param.ts # x-pack/solutions/security/plugins/security_solution/public/plugin.tsx # x-pack/solutions/security/plugins/security_solution/public/timelines/components/open_timeline/helpers.ts # x-pack/solutions/security/plugins/security_solution/public/timelines/store/model.ts # x-pack/test_serverless/functional/test_suites/security/config.context_awareness.ts # x-pack/test_serverless/functional/test_suites/security/constants.ts # x-pack/test_serverless/functional/test_suites/security/ftr/discover/context_awareness/cell_renderer.ts # x-pack/test_serverless/functional/test_suites/security/ftr/discover/context_awareness/index.ts

…nt timeline redirection (#204756) (#224984) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Add Host/User flyout in One Discover. (#199279)](#199279) - [[ Security Solution ] One discover security context functional tests (#199818)](#199818) - [[Security Solution] Discover Security Profile Changes + Event timeline redirection (#204756)](#204756)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  discoverShared\n discover -- \"consume Features\" --> discoverShared\n\n```\n\n## How to Test\n\n>[!Note]\n>This PR adds `security-root-profile` in One discover which is currently\nin `experimental mode`. All changes below can only be tested when\nprofile is activated. Profile can activated by adding below lines in\n`config/kibana.dev.yml`\n> ```yaml\n> discover.experimental.enabledProfiles:\n> - security-root-profile\n> ```\n>\n\n1. As mentioned above, adding above experimental flag in\n`kibana.dev.yml`.\n2. Spin up Security Serverless project and add some alert Data.\n3. Navigate to Discover and add columns `host.name` and `user.name` in\ntable. Now `host` and `user` flyouts should be available on clicking\n`host.name`, `user.name`, `source.ip` & `destination.ip`.\n4. Flyout should work without any error.\n5. Below things are not working and will be tackled in followup PR :\n - Security Hover actions\n - Actions such as `Add to Timeline` or `Add to Case` \n\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c80f91efebfc783c1b8f64dbad479deeb6586d1c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:Threat Hunting:Investigations","Project:OneDiscover","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Add Host/User flyout in One Discover.","number":199279,"url":"https://github.com/elastic/kibana/pull/199279","mergeCommit":{"message":"[Security Solution] Add Host/User flyout in One Discover. (#199279)\n\n## Summary\n\nHandles https://github.com/elastic/kibana/issues/191998\n\nFollow up work:\n - https://github.com/elastic/security-team/issues/11112\n - https://github.com/elastic/kibana/issues/196667\n\n\nThis PR add below entity flyouts for below entities in One Discover:\n- host.name\n- user.name\n- source.ip\n- destination.ip\n\n\nIn this PR we re-use the security solution code by making use of below\nmodel based on `discover-shared` plugin.\n\n```mermaid\nflowchart TD\n discoverShared[\"Discover Shared\"]\n securitySolution[\"Security Solution\"]\n discover[\"Discover\"]\n\n\n securitySolution -- \"registers Features\" --> discoverShared\n discover -- \"consume Features\" --> discoverShared\n\n```\n\n## How to Test\n\n>[!Note]\n>This PR adds `security-root-profile` in One discover which is currently\nin `experimental mode`. All changes below can only be tested when\nprofile is activated. Profile can activated by adding below lines in\n`config/kibana.dev.yml`\n> ```yaml\n> discover.experimental.enabledProfiles:\n> - security-root-profile\n> ```\n>\n\n1. As mentioned above, adding above experimental flag in\n`kibana.dev.yml`.\n2. Spin up Security Serverless project and add some alert Data.\n3. Navigate to Discover and add columns `host.name` and `user.name` in\ntable. Now `host` and `user` flyouts should be available on clicking\n`host.name`, `user.name`, `source.ip` & `destination.ip`.\n4. Flyout should work without any error.\n5. Below things are not working and will be tackled in followup PR :\n - Security Hover actions\n - Actions such as `Add to Timeline` or `Add to Case` \n\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c80f91efebfc783c1b8f64dbad479deeb6586d1c"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199279","number":199279,"mergeCommit":{"message":"[Security Solution] Add Host/User flyout in One Discover. (#199279)\n\n## Summary\n\nHandles https://github.com/elastic/kibana/issues/191998\n\nFollow up work:\n - https://github.com/elastic/security-team/issues/11112\n - https://github.com/elastic/kibana/issues/196667\n\n\nThis PR add below entity flyouts for below entities in One Discover:\n- host.name\n- user.name\n- source.ip\n- destination.ip\n\n\nIn this PR we re-use the security solution code by making use of below\nmodel based on `discover-shared` plugin.\n\n```mermaid\nflowchart TD\n discoverShared[\"Discover Shared\"]\n securitySolution[\"Security Solution\"]\n discover[\"Discover\"]\n\n\n securitySolution -- \"registers Features\" --> discoverShared\n discover -- \"consume Features\" --> discoverShared\n\n```\n\n## How to Test\n\n>[!Note]\n>This PR adds `security-root-profile` in One discover which is currently\nin `experimental mode`. All changes below can only be tested when\nprofile is activated. Profile can activated by adding below lines in\n`config/kibana.dev.yml`\n> ```yaml\n> discover.experimental.enabledProfiles:\n> - security-root-profile\n> ```\n>\n\n1. As mentioned above, adding above experimental flag in\n`kibana.dev.yml`.\n2. Spin up Security Serverless project and add some alert Data.\n3. Navigate to Discover and add columns `host.name` and `user.name` in\ntable. Now `host` and `user` flyouts should be available on clicking\n`host.name`, `user.name`, `source.ip` & `destination.ip`.\n4. Flyout should work without any error.\n5. Below things are not working and will be tackled in followup PR :\n - Security Hover actions\n - Actions such as `Add to Timeline` or `Add to Case` \n\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c80f91efebfc783c1b8f64dbad479deeb6586d1c"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]},{"author":{"name":"Jatin Kathuria","email":"jtn.kathuria@gmail.com"},"sourceCommit":{"committedDate":"2024-12-10T09:38:43Z","message":"[ Security Solution ] One discover security context functional tests (#199818)\n\n## Summary\n\nFixes https://github.com/elastic/security-team/issues/11112\n\nFollow up to \n- https://github.com/elastic/kibana/pull/199279\n\nAdds functional test for Security Profiles in One Discover.\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9619d610d17e056564365015858011e5e41b2209","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","Team:Threat Hunting:Investigations","Project:OneDiscover"],"title":"[ Security Solution ] One discover security context functional tests","number":199818,"url":"https://github.com/elastic/kibana/pull/199818","mergeCommit":{"message":"[ Security Solution ] One discover security context functional tests (#199818)\n\n## Summary\n\nFixes https://github.com/elastic/security-team/issues/11112\n\nFollow up to \n- https://github.com/elastic/kibana/pull/199279\n\nAdds functional test for Security Profiles in One Discover.\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9619d610d17e056564365015858011e5e41b2209"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199818","number":199818,"mergeCommit":{"message":"[ Security Solution ] One discover security context functional tests (#199818)\n\n## Summary\n\nFixes https://github.com/elastic/security-team/issues/11112\n\nFollow up to \n- https://github.com/elastic/kibana/pull/199279\n\nAdds functional test for Security Profiles in One Discover.\n\n\n### Checklist\n\nDelete any items that are not applicable to this PR.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9619d610d17e056564365015858011e5e41b2209"}}]},{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-06-24T00:39:29Z","message":"[Security Solution] Discover Security Profile Changes + Event timeline redirection (#204756)\n\n## Summary\n\nThis PR customized Discover's Security Root Profile with 3 new changes.\n\\\n\nWith this change Discover's Security profile ceases to be\n`experimental`. Below are the changes listed one in this profile.\n\n>[!Note]\n> This change also removes the Flyout changes that were added for\nsecurity solution to the Discover's security profile.\n\n\n### Row Indicators.\n\nAdds row indicators based on Alert or an event as shown in the\nscreenshot below. Note the highlights on the left of the row.\n\n`Yellow` for Alerts.\n`Gray` for Events.\n\n\n![image](https://github.com/user-attachments/assets/697bafe9-3c45-4926-9b00-4bf6453e70eb)\n\n### Default list of Columns.\n\nAdds the list of default columns that should appear when security\nprofile is activated.\n\n\n![image](https://github.com/user-attachments/assets/71647f3e-37da-4fab-b350-baa567b7e9bd)\n\n### Explore in Security Flyout.\n\nAs shown the demo below, this action explores and event or an alert in\nsecurity solution as shown in the screenshot below.\n\n\n\n\nhttps://github.com/user-attachments/assets/4c228bb1-60af-433b-8e8f-1a5d4d049985\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"fbec7db5b09133d0e2a83bc841bf7192f9b648e7","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Discover Security Profile Changes + Event timeline redirection","number":204756,"url":"https://github.com/elastic/kibana/pull/204756","mergeCommit":{"message":"[Security Solution] Discover Security Profile Changes + Event timeline redirection (#204756)\n\n## Summary\n\nThis PR customized Discover's Security Root Profile with 3 new changes.\n\\\n\nWith this change Discover's Security profile ceases to be\n`experimental`. Below are the changes listed one in this profile.\n\n>[!Note]\n> This change also removes the Flyout changes that were added for\nsecurity solution to the Discover's security profile.\n\n\n### Row Indicators.\n\nAdds row indicators based on Alert or an event as shown in the\nscreenshot below. Note the highlights on the left of the row.\n\n`Yellow` for Alerts.\n`Gray` for Events.\n\n\n![image](https://github.com/user-attachments/assets/697bafe9-3c45-4926-9b00-4bf6453e70eb)\n\n### Default list of Columns.\n\nAdds the list of default columns that should appear when security\nprofile is activated.\n\n\n![image](https://github.com/user-attachments/assets/71647f3e-37da-4fab-b350-baa567b7e9bd)\n\n### Explore in Security Flyout.\n\nAs shown the demo below, this action explores and event or an alert in\nsecurity solution as shown in the screenshot below.\n\n\n\n\nhttps://github.com/user-attachments/assets/4c228bb1-60af-433b-8e8f-1a5d4d049985\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"fbec7db5b09133d0e2a83bc841bf7192f9b648e7"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204756","number":204756,"mergeCommit":{"message":"[Security Solution] Discover Security Profile Changes + Event timeline redirection (#204756)\n\n## Summary\n\nThis PR customized Discover's Security Root Profile with 3 new changes.\n\\\n\nWith this change Discover's Security profile ceases to be\n`experimental`. Below are the changes listed one in this profile.\n\n>[!Note]\n> This change also removes the Flyout changes that were added for\nsecurity solution to the Discover's security profile.\n\n\n### Row Indicators.\n\nAdds row indicators based on Alert or an event as shown in the\nscreenshot below. Note the highlights on the left of the row.\n\n`Yellow` for Alerts.\n`Gray` for Events.\n\n\n![image](https://github.com/user-attachments/assets/697bafe9-3c45-4926-9b00-4bf6453e70eb)\n\n### Default list of Columns.\n\nAdds the list of default columns that should appear when security\nprofile is activated.\n\n\n![image](https://github.com/user-attachments/assets/71647f3e-37da-4fab-b350-baa567b7e9bd)\n\n### Explore in Security Flyout.\n\nAs shown the demo below, this action explores and event or an alert in\nsecurity solution as shown in the screenshot below.\n\n\n\n\nhttps://github.com/user-attachments/assets/4c228bb1-60af-433b-8e8f-1a5d4d049985\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Davis McPhee <davis.mcphee@elastic.co>","sha":"fbec7db5b09133d0e2a83bc841bf7192f9b648e7"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

@davismcphee

…ldsMetadata (#225105) ## Summary As per [comments](#204756 (comment)) by @davismcphee , this PR removes the usage of `EcsFlat` and replaces it with `fieldsMetadata`.

@davismcphee

…ldsMetadata (elastic#225105) ## Summary As per [comments](elastic#204756 (comment)) by @davismcphee , this PR removes the usage of `EcsFlat` and replaces it with `fieldsMetadata`. (cherry picked from commit 2ed4e8a)

…e redirection (elastic#204756) ## Summary This PR customized Discover's Security Root Profile with 3 new changes. \ With this change Discover's Security profile ceases to be `experimental`. Below are the changes listed one in this profile. >[!Note] > This change also removes the Flyout changes that were added for security solution to the Discover's security profile. ### Row Indicators. Adds row indicators based on Alert or an event as shown in the screenshot below. Note the highlights on the left of the row. `Yellow` for Alerts. `Gray` for Events. ![image](https://github.com/user-attachments/assets/697bafe9-3c45-4926-9b00-4bf6453e70eb) ### Default list of Columns. Adds the list of default columns that should appear when security profile is activated. ![image](https://github.com/user-attachments/assets/71647f3e-37da-4fab-b350-baa567b7e9bd) ### Explore in Security Flyout. As shown the demo below, this action explores and event or an alert in security solution as shown in the screenshot below. https://github.com/user-attachments/assets/4c228bb1-60af-433b-8e8f-1a5d4d049985 ### 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/packages/kbn-i18n/README.md) - [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 ### 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: Davis McPhee <davis.mcphee@elastic.co>

@davismcphee

…ldsMetadata (elastic#225105) ## Summary As per [comments](elastic#204756 (comment)) by @davismcphee , this PR removes the usage of `EcsFlat` and replaces it with `fieldsMetadata`.

logeekal added Team:Threat Hunting:Investigations Security Solution Threat Hunting Investigations Team ci:project-deploy-security Create a Security Serverless Project ci:project-persist-deployment Persist project deployment indefinitely labels Dec 18, 2024

logeekal changed the title ~~Feat/timeline redirect~~ [Security Solution] Discover Security Profile Changes + Event timeline redirection Dec 19, 2024

logeekal force-pushed the feat/timeline_redirect branch from 9f69bdd to 214bb37 Compare February 18, 2025 10:00

logeekal commented Feb 18, 2025

View reviewed changes

x-pack/solutions/security/plugins/security_solution/public/common/hooks/use_url_state.ts Show resolved Hide resolved

logeekal removed ci:project-deploy-security Create a Security Serverless Project ci:project-persist-deployment Persist project deployment indefinitely labels Mar 7, 2025

logeekal and others added 17 commits March 21, 2025 07:26

incremental

5438e0b

incremental save

20e2776

poc: Overview tab

cb34563

feat: timeline redirect basic logic

986be47

feat: default columns + row indicator

6b16fda

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

7364df3

make ci 🟢

137c4a4

fix: types

68bb477

tests: add

19e2eb3

test: unfocus

0584947

fix: timeline redirect url + tests

665b15a

fix: timerange sync issue

f100b30

fix: housekeeping

79c2490

fix: rebase issues

0073e2f

fix: more rebase issues

aef1bd4

fix: remove unnecessary files

841e7b9

fix: tests

12561c9

davismcphee and others added 3 commits June 23, 2025 19:31

Fix failing tests after enabling security profile

8b8ba69

Update stateful tests

e5507d4

Merge pull request #5 from davismcphee/fix-security-profile-tests

e2874dc

Fix failing tests after enabling security root profile

logeekal enabled auto-merge (squash) June 24, 2025 00:27

logeekal merged commit fbec7db into elastic:main Jun 24, 2025
10 checks passed

kibanamachine added the v9.1.0 label Jun 24, 2025

logeekal added backport:version Backport to applied version labels v8.19.0 backport:skip This PR does not require backporting and removed backport:skip This PR does not require backporting v8.19.0 backport:version Backport to applied version labels labels Jun 24, 2025

logeekal mentioned this pull request Jun 24, 2025

[8.19] [Security Solution] One Discover Security Profile Enable + Event timeline redirection (#204756) #224984

Merged

logeekal mentioned this pull request Jun 24, 2025

[One Discover][Security Solution] Replace the use of Ecsflat with fieldsMetadata #225105

Merged

PhilippeOberti mentioned this pull request Jun 27, 2025

[SecuritySolution] [Bug] Hide timeline for priv mon onboarding #225442

Merged

2 tasks

Comments

Conversation

logeekal commented Dec 18, 2024 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Row Indicators.

Default list of Columns.

Explore in Security Flyout.

Checklist

Identify risks

Uh oh!

kibanamachine commented Dec 18, 2024

Uh oh!

kibanamachine commented Dec 18, 2024

Uh oh!

kibanamachine commented Dec 19, 2024

Uh oh!

kibanamachine commented Dec 19, 2024

Uh oh!

Uh oh!

pmuellr commented Mar 7, 2025

Uh oh!

Uh oh!

elasticmachine commented Jun 24, 2025

💚 Build Succeeded

Metrics [docs]

Module Count

Public APIs missing comments

Async chunks

Page load bundle

API count

async chunk count

History

Uh oh!

kibanamachine commented Jun 24, 2025

Uh oh!

kibanamachine commented Jun 24, 2025

Uh oh!

kibanamachine commented Jun 24, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

kibanamachine commented Jun 24, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

logeekal commented Jun 24, 2025

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

9 participants

logeekal commented Dec 18, 2024 •

edited by kibanamachine

Loading