[Attack Discovery][Scheduling] Make "For each alert" a default action frequency#225890
Merged
e40pud merged 10 commits intoelastic:mainfrom Jul 2, 2025
Merged
Conversation
e40pud
added
the
release_note:skip
e40pud
added
Team: SecuritySolution
Contributor
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
andrew-goldstein
approved these changes
Jun 30, 2025
Contributor
andrew-goldstein
left a comment
andrew-goldstein
left a comment
There was a problem hiding this comment.
Thanks @e40pud for improving the UX through this updated default! 🙏
✅ Desk tested locally
LGTM 🚀
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
History
cc @e40pud |
Contributor
|
Starting backport for target branches: 8.19, 9.1 https://github.com/elastic/kibana/actions/runs/16023199451 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 2, 2025
… frequency (elastic#225890) ## Summary This came from a testing party which we did with the team on June 30th. There are a list of attack specific fields which are helpful for the user while creating an action for the attack discovery schedule. Those fields are present within the context when the actions frequency set to `"For each alert"` and located under the `context.attack.*`. While testing this functionality, @peluja1012 and @stephmilovic found it not clear that attack context fields are only present in case of `"For each alert"` frequency. One of the reasons was the fact that we set the `"Summary of alerts"` frequency as a default one. <img width="944" alt="Screenshot 2025-06-30 at 19 02 31" src="https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67" /> With these changes we improve the behaviour and make `"For each alert"` frequency a default one. This way user will have immediately the access to those context fields and more likely to use them. <img width="1259" alt="Screenshot 2025-06-30 at 19 03 23" src="https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda" /> ### To test 1. Navigate to the Attack Discovery page 2. Open Settings flyout 3. Open Schedule tab 4. Click "Create new schedule" button 5. Select one of the actions to add (slack, email etc.) **Expected behaviour**: the `"For each alert"` frequency should be selected by default and `context.attack.*` fields should be available in the `"Add variable"` popover. ## NOTES The feature is hidden behind the feature flag (in `kibana.dev.yml`): ``` feature_flags.overrides: securitySolution.attackDiscoveryAlertsEnabled: true securitySolution.assistantAttackDiscoverySchedulingEnabled: true ``` (cherry picked from commit f606dec)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 2, 2025
… frequency (elastic#225890) ## Summary This came from a testing party which we did with the team on June 30th. There are a list of attack specific fields which are helpful for the user while creating an action for the attack discovery schedule. Those fields are present within the context when the actions frequency set to `"For each alert"` and located under the `context.attack.*`. While testing this functionality, @peluja1012 and @stephmilovic found it not clear that attack context fields are only present in case of `"For each alert"` frequency. One of the reasons was the fact that we set the `"Summary of alerts"` frequency as a default one. <img width="944" alt="Screenshot 2025-06-30 at 19 02 31" src="https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67" /> With these changes we improve the behaviour and make `"For each alert"` frequency a default one. This way user will have immediately the access to those context fields and more likely to use them. <img width="1259" alt="Screenshot 2025-06-30 at 19 03 23" src="https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda" /> ### To test 1. Navigate to the Attack Discovery page 2. Open Settings flyout 3. Open Schedule tab 4. Click "Create new schedule" button 5. Select one of the actions to add (slack, email etc.) **Expected behaviour**: the `"For each alert"` frequency should be selected by default and `context.attack.*` fields should be available in the `"Add variable"` popover. ## NOTES The feature is hidden behind the feature flag (in `kibana.dev.yml`): ``` feature_flags.overrides: securitySolution.attackDiscoveryAlertsEnabled: true securitySolution.assistantAttackDiscoverySchedulingEnabled: true ``` (cherry picked from commit f606dec)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jul 2, 2025
…action frequency (#225890) (#226156) # Backport This will backport the following commits from `main` to `9.1`: - [[Attack Discovery][Scheduling] Make "For each alert" a default action frequency (#225890)](#225890) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-07-02T10:54:45Z","message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency","number":225890,"url":"https://github.com/elastic/kibana/pull/225890","mergeCommit":{"message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"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"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225890","number":225890,"mergeCommit":{"message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Jul 2, 2025
… action frequency (#225890) (#226155) # Backport This will backport the following commits from `main` to `8.19`: - [[Attack Discovery][Scheduling] Make "For each alert" a default action frequency (#225890)](#225890) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-07-02T10:54:45Z","message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency","number":225890,"url":"https://github.com/elastic/kibana/pull/225890","mergeCommit":{"message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"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"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225890","number":225890,"mergeCommit":{"message":"[Attack Discovery][Scheduling] Make \"For each alert\" a default action frequency (#225890)\n\n## Summary\n\nThis came from a testing party which we did with the team on June 30th.\n\nThere are a list of attack specific fields which are helpful for the\nuser while creating an action for the attack discovery schedule. Those\nfields are present within the context when the actions frequency set to\n`\"For each alert\"` and located under the `context.attack.*`.\n\nWhile testing this functionality, @peluja1012 and @stephmilovic found it\nnot clear that attack context fields are only present in case of `\"For\neach alert\"` frequency. One of the reasons was the fact that we set the\n`\"Summary of alerts\"` frequency as a default one.\n\n<img width=\"944\" alt=\"Screenshot 2025-06-30 at 19 02 31\"\nsrc=\"https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67\"\n/>\n\nWith these changes we improve the behaviour and make `\"For each alert\"`\nfrequency a default one. This way user will have immediately the access\nto those context fields and more likely to use them.\n\n<img width=\"1259\" alt=\"Screenshot 2025-06-30 at 19 03 23\"\nsrc=\"https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda\"\n/>\n\n### To test\n\n1. Navigate to the Attack Discovery page\n2. Open Settings flyout\n3. Open Schedule tab\n4. Click \"Create new schedule\" button\n5. Select one of the actions to add (slack, email etc.)\n\n**Expected behaviour**: the `\"For each alert\"` frequency should be\nselected by default and `context.attack.*` fields should be available in\nthe `\"Add variable\"` popover.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.attackDiscoveryAlertsEnabled: true\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"f606dec7d5fbef8fc8b48847221ace3a4cf28924"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
Jul 25, 2025
… frequency (elastic#225890) ## Summary This came from a testing party which we did with the team on June 30th. There are a list of attack specific fields which are helpful for the user while creating an action for the attack discovery schedule. Those fields are present within the context when the actions frequency set to `"For each alert"` and located under the `context.attack.*`. While testing this functionality, @peluja1012 and @stephmilovic found it not clear that attack context fields are only present in case of `"For each alert"` frequency. One of the reasons was the fact that we set the `"Summary of alerts"` frequency as a default one. <img width="944" alt="Screenshot 2025-06-30 at 19 02 31" src="https://github.com/user-attachments/assets/7f7a8aba-c820-47be-8f10-04df50f5af67" /> With these changes we improve the behaviour and make `"For each alert"` frequency a default one. This way user will have immediately the access to those context fields and more likely to use them. <img width="1259" alt="Screenshot 2025-06-30 at 19 03 23" src="https://github.com/user-attachments/assets/1a5f44b7-2cf8-41b1-9bbd-c0507ef42eda" /> ### To test 1. Navigate to the Attack Discovery page 2. Open Settings flyout 3. Open Schedule tab 4. Click "Create new schedule" button 5. Select one of the actions to add (slack, email etc.) **Expected behaviour**: the `"For each alert"` frequency should be selected by default and `context.attack.*` fields should be available in the `"Add variable"` popover. ## NOTES The feature is hidden behind the feature flag (in `kibana.dev.yml`): ``` feature_flags.overrides: securitySolution.attackDiscoveryAlertsEnabled: true securitySolution.assistantAttackDiscoverySchedulingEnabled: true ```
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
4 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.
Summary
This came from a testing party which we did with the team on June 30th.
There are a list of attack specific fields which are helpful for the user while creating an action for the attack discovery schedule. Those fields are present within the context when the actions frequency set to
"For each alert"and located under thecontext.attack.*.While testing this functionality, @peluja1012 and @stephmilovic found it not clear that attack context fields are only present in case of
"For each alert"frequency. One of the reasons was the fact that we set the"Summary of alerts"frequency as a default one.With these changes we improve the behaviour and make
"For each alert"frequency a default one. This way user will have immediately the access to those context fields and more likely to use them.To test
Expected behaviour: the
"For each alert"frequency should be selected by default andcontext.attack.*fields should be available in the"Add variable"popover.NOTES
The feature is hidden behind the feature flag (in
kibana.dev.yml):