[Security Solution] Enable endpoint actions for events #206857
Merged
Conversation
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
christineweng
added
release_note:enhancement
Team:Threat Hunting:Investigations
christineweng
force-pushed
the
endpoint-action-in-event-flyout
branch
from
7f0dd26 to
b396bf6
Compare
|
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
christineweng
changed the title
szwarckonrad
requested review from
tomsonpl
and removed request for
szwarckonrad
tomsonpl
approved these changes
Mar 5, 2025
There was a problem hiding this comment.
Looks good to me, however not sure what was the reason to limiting this to Alerts only in the first place.
@paul-tavares do you remember by any chance?
I don't remember now we made that decision when Endgame come over to Elastic. Perhaps because we only foresaw users doing actions on host while responding to a threat. That being said, adding it events has been something that we have been wanting todo for a while now. You could ask Caitlyn for more background on here is you like - she may remember more details. @christineweng - I'll review this sometime today. Sorry for the delay. |
paul-tavares
approved these changes
Mar 5, 2025
There was a problem hiding this comment.
Looks good. Thank you for working on this and enabling it. I checked out the PR and loaded endpoint, sentinelone and Microsoft data and it all seems to work as we expect it. 👍
Remember to let the docs team know to list this as new functionality in the release notes (for serverless first since this will be released there first).
|
@tomsonpl @paul-tavares Thank you both for the review! Here is the doc issue |
lgestc
approved these changes
Mar 10, 2025
...n/public/common/components/endpoint/host_isolation/from_alerts/use_host_isolation_action.tsx
Outdated
Show resolved
Hide resolved
christineweng
force-pushed
the
endpoint-action-in-event-flyout
branch
from
f1b281b to
10d6734
Compare
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
|
Starting backport for target branches: 8.x |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 14, 2025
## Summary This PR enabled endpoint actions for generic events (in addition to alerts). We want to allow users to perform endpoint related actions like isolate host and respond in the flyout. Main use case is to perform endpoint actions when investigating in analyzer. **Before**  **After** Enabled for events when host uses elastic defend  Disabled when host cannot be isolated  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit c329ccf)
💚 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
Mar 14, 2025
#214666) # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Enable endpoint actions for events (#206857)](#206857) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T21:28:30Z","message":"[Security Solution] Enable endpoint actions for events (#206857)\n\n## Summary\n\nThis PR enabled endpoint actions for generic events (in addition to\nalerts). We want to allow users to perform endpoint related actions like\nisolate host and respond in the flyout. Main use case is to perform\nendpoint actions when investigating in analyzer.\n\n**Before**\n\n\n\n**After**\nEnabled for events when host uses elastic defend\n\n\n\nDisabled when host cannot be isolated\n\n\n\n### Checklist\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- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c329ccf87bda02effc2670318cbe386d6bdf3e74","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Threat Hunting:Investigations","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Enable endpoint actions for events","number":206857,"url":"https://github.com/elastic/kibana/pull/206857","mergeCommit":{"message":"[Security Solution] Enable endpoint actions for events (#206857)\n\n## Summary\n\nThis PR enabled endpoint actions for generic events (in addition to\nalerts). We want to allow users to perform endpoint related actions like\nisolate host and respond in the flyout. Main use case is to perform\nendpoint actions when investigating in analyzer.\n\n**Before**\n\n\n\n**After**\nEnabled for events when host uses elastic defend\n\n\n\nDisabled when host cannot be isolated\n\n\n\n### Checklist\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- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c329ccf87bda02effc2670318cbe386d6bdf3e74"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206857","number":206857,"mergeCommit":{"message":"[Security Solution] Enable endpoint actions for events (#206857)\n\n## Summary\n\nThis PR enabled endpoint actions for generic events (in addition to\nalerts). We want to allow users to perform endpoint related actions like\nisolate host and respond in the flyout. Main use case is to perform\nendpoint actions when investigating in analyzer.\n\n**Before**\n\n\n\n**After**\nEnabled for events when host uses elastic defend\n\n\n\nDisabled when host cannot be isolated\n\n\n\n### Checklist\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- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c329ccf87bda02effc2670318cbe386d6bdf3e74"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
clintandrewhall
pushed a commit
to clintandrewhall/kibana
that referenced
this pull request
Mar 20, 2025
## Summary This PR enabled endpoint actions for generic events (in addition to alerts). We want to allow users to perform endpoint related actions like isolate host and respond in the flyout. Main use case is to perform endpoint actions when investigating in analyzer. **Before**  **After** Enabled for events when host uses elastic defend  Disabled when host cannot be isolated  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Mar 22, 2025
## Summary This PR enabled endpoint actions for generic events (in addition to alerts). We want to allow users to perform endpoint related actions like isolate host and respond in the flyout. Main use case is to perform endpoint actions when investigating in analyzer. **Before**  **After** Enabled for events when host uses elastic defend  Disabled when host cannot be isolated  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR enabled endpoint actions for generic events (in addition to alerts). We want to allow users to perform endpoint related actions like isolate host and respond in the flyout. Main use case is to perform endpoint actions when investigating in analyzer.
Before
After
Enabled for events when host uses elastic defend
Disabled when host cannot be isolated
Checklist
release_note:*label is applied per the guidelines