[ Security Solution ] One discover security context functional tests by logeekal · Pull Request #199818 · elastic/kibana

logeekal · 2024-11-12T15:55:21Z

Summary

Fixes https://github.com/elastic/security-team/issues/11112

Follow up to

[Security Solution] Add Host/User flyout in One Discover. #199279

Adds functional test for Security Profiles in One Discover.

Checklist

Delete any items that are not applicable to this PR.

Unit or functional tests were updated or added to match the most common scenarios

logeekal · 2024-12-03T13:23:29Z

/ci

logeekal · 2024-12-04T05:59:39Z

/ci

logeekal · 2024-12-04T10:13:50Z

x-pack/test_serverless/functional/test_suites/security/config.example.context_awareness.ts

+
+import { createTestConfig } from '../../config.base';
+
+export default createTestConfig({


@elastic/kibana-data-discovery team, I have created a separate config for example profiles, because if example profiles are activated, they override any solution profile that may be available.

With this approach we are able to keep tests for example profiles and solution profiles separate. Let me know if you think this approach is not optimal.

This approach makes sense to me and is similar to what O11y did. They kept the existing config and just added their tests to their existing O11y config, but IMO Security can structure it however you'd like as long as the example tests still run.

My only minor nit would be I'd personally go with config.examples. instead of config.example. for consistency with other example tests, but just an observation and fine on my end either way.

Done here : 39a02c4

elasticmachine · 2024-12-04T10:14:40Z

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

wayneseymour

Looks good, just some questions.

x-pack/test_serverless/functional/test_suites/security/config.example.context_awareness.ts

...rverless/functional/test_suites/security/ftr/one_discover/context_awareness/cell_renderer.ts

wayneseymour · 2024-12-04T13:29:23Z

x-pack/test_serverless/functional/test_suites/security/config.context_awareness.ts

 export default createTestConfig({
  serverlessProject: 'security',
-  testFiles: [require.resolve('../common/discover/context_awareness')],
+  testFiles: [require.resolve('./ftr/one_discover/context_awareness')],


Curious, what's the one_discover convention mean semantically?

Actually, One discover is the name of the project that discover is going through it enables solutions to customize various discover elements.

I am happy to change it to discover if one_discover is confusing and need not be used in code. Will appreciate any comments from you as well @davismcphee

I'd probably recommend going with just discover instead. We're calling the program One Discover currently, but I imagine these tests could outlive that naming.

Makes sense.. done here: 39a02c4

davismcphee

Left a couple minor comments, but it LGTM! Thanks for adding functional tests 👍

davismcphee · 2024-12-05T22:15:22Z

.github/CODEOWNERS

+/x-pack/test_serverless/functional/test_suites/security/config.examples.ts   @elastic/kibana-data-discovery
+/x-pack/test_serverless/functional/test_suites/security/config.example.context_awareness.ts @elastic/kibana-data-discovery
+/x-pack/test_serverless/functional/test_suites/security/config.context_awareness.ts @elastic/security-threat-hunting-investigations @elastic/kibana-data-discovery
+/x-pack/test_serverless/functional/test_suites/security/constants.ts   @elastic/kibana-data-discovery


Suggested change

/x-pack/test_serverless/functional/test_suites/security/constants.ts @elastic/kibana-data-discovery

/x-pack/test_serverless/functional/test_suites/security/constants.ts @elastic/security-threat-hunting-investigations

Should this be assigned to us or Threat Hunting Investigations?

Fixed and changed it to Security Solution here : 618316c

davismcphee · 2024-12-05T22:16:50Z

x-pack/test_serverless/functional/test_suites/security/config.context_awareness.ts

 export default createTestConfig({
  serverlessProject: 'security',
-  testFiles: [require.resolve('../common/discover/context_awareness')],
+  testFiles: [require.resolve('./ftr/one_discover/context_awareness')],


I'd probably recommend going with just discover instead. We're calling the program One Discover currently, but I imagine these tests could outlive that naming.

davismcphee · 2024-12-05T22:21:11Z

x-pack/test_serverless/functional/test_suites/security/config.example.context_awareness.ts

+
+import { createTestConfig } from '../../config.base';
+
+export default createTestConfig({


This approach makes sense to me and is similar to what O11y did. They kept the existing config and just added their tests to their existing O11y config, but IMO Security can structure it however you'd like as long as the example tests still run.

My only minor nit would be I'd personally go with config.examples. instead of config.example. for consistency with other example tests, but just an observation and fine on my end either way.

elasticmachine · 2024-12-10T09:39:20Z

💚 Build Succeeded

Buildkite Build
Commit: e99ee42

Metrics [docs]

✅ unchanged

History

💚 Build #257758 succeeded 3b5a66b
💔 Build #257744 failed 4d0225e
💚 Build #256848 succeeded 5a5942b
💔 Build #256829 failed 6d81988
💔 Build #256811 failed 5335847
💔 Build #256725 failed 46f3fc0

…lastic#199818) ## Summary Fixes elastic/security-team#11112 Follow up to - elastic#199279 Adds functional test for Security Profiles in One Discover. ### Checklist Delete any items that are not applicable to this PR. - [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 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

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

…lastic#199818) ## Summary Fixes elastic/security-team#11112 Follow up to - elastic#199279 Adds functional test for Security Profiles in One Discover. ### Checklist Delete any items that are not applicable to this PR. - [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 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 9619d61) # Conflicts: # .github/CODEOWNERS # x-pack/test_serverless/functional/test_suites/security/constants.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>

logeekal added 2 commits December 3, 2024 12:39

security solution profile tests

2f206d5

fix: data format

09d04ec

logeekal force-pushed the one_discover_security_functional_tests branch from b06148d to 09d04ec Compare December 3, 2024 11:40

logeekal added 2 commits December 3, 2024 14:20

add security tests

2c848b0

fix: merge issues

60cb6b4

fix: codeowners + ftr_config

46f3fc0

logeekal added 2 commits December 4, 2024 11:03

fix: config

b6d6f14

fix: config names

5335847

logeekal commented Dec 4, 2024

View reviewed changes

logeekal added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Threat Hunting:Investigations Security Solution Threat Hunting Investigations Team labels Dec 4, 2024

logeekal marked this pull request as ready for review December 4, 2024 10:14

logeekal requested review from a team as code owners December 4, 2024 10:14

logeekal changed the title ~~One discover security functional tests~~ [Security Solution ] One discover security functional tests Dec 4, 2024

logeekal changed the title ~~[Security Solution ] One discover security functional tests~~ [ Security Solution ] One discover security functional tests Dec 4, 2024

wayneseymour suggested changes Dec 4, 2024

View reviewed changes

logeekal added 4 commits December 4, 2024 11:45

fix: add removed file

ad5fc45

fix: PR feedback

6d81988

fix: precise query

f608d0b

fix: codeowners

5a5942b

wayneseymour reviewed Dec 4, 2024

View reviewed changes

wayneseymour approved these changes Dec 4, 2024

View reviewed changes

Ikuni17 approved these changes Dec 4, 2024

View reviewed changes

logeekal changed the title ~~[ Security Solution ] One discover security functional tests~~ [ Security Solution ] One discover security context functional tests Dec 5, 2024

davismcphee approved these changes Dec 5, 2024

View reviewed changes

logeekal and others added 6 commits December 6, 2024 08:22

fix: PR Feeback

39a02c4

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

070fffc

fix: code ownership

618316c

Merge branch 'main' into one_discover_security_functional_tests

4d0225e

Merge branch 'main' into one_discover_security_functional_tests

3b5a66b

Merge branch 'main' into one_discover_security_functional_tests

e99ee42

logeekal enabled auto-merge (squash) December 10, 2024 08:10

logeekal merged commit 9619d61 into elastic:main Dec 10, 2024

kibanamachine added the v9.0.0 label Dec 10, 2024

jughosta added the Project:OneDiscover Enrich Discover with contextual awareness label Jan 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

kibanamachine added the v8.19.0 label Jun 24, 2025


		import { createTestConfig } from '../../config.base';

		export default createTestConfig({

	/x-pack/test_serverless/functional/test_suites/security/constants.ts @elastic/kibana-data-discovery
	/x-pack/test_serverless/functional/test_suites/security/constants.ts @elastic/security-threat-hunting-investigations

Conversation

logeekal commented Nov 12, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Checklist

Uh oh!

logeekal commented Dec 3, 2024

Uh oh!

logeekal commented Dec 4, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Dec 4, 2024

Uh oh!

wayneseymour left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

davismcphee left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Dec 10, 2024

💚 Build Succeeded

Metrics [docs]

History

Uh oh!

logeekal commented Jun 24, 2025

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

logeekal commented Nov 12, 2024 •

edited

Loading