[Jan 28] Adds new runscript Crowdstrike response action #6435
Conversation
This file contains 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
natasha-moore-elastic
added
Team: EDR Workflows
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
raqueltabuyo
previously approved these changes
Jan 21, 2025
tomsonpl
reviewed
Jan 21, 2025
There was a problem hiding this comment.
Hey @natasha-moore-elastic, this looks awesome ❤️
Leaving some thoughts here:
- Runscript response action - currently it is on the list of all response actions, however it's the first response action that is not supported by Endpoint, but only on CrowdStrike - should we distinguish this somehow, or at least mention 'CrowdStrike only' or something like that ?
- In SentinelOne, we have a information about:
View past response action activity in the [response actions history](https://security-docs_bk_6435.docs-preview.app.elstc.co/guide/en/serverless/main/security-response-actions-history.html) log.
We are capable of doing this for CrowdStrike too, so we could think of adding it to the docs too, what do you think? - runscript examples - can we add 3 examples ? 1 per each argument : Raw, HostPath, CloudFile ?
- I was wrong when confirming the predefined roles for RunScript. They should not be the same as for Isolate, but the same as for Execute - meaning:
Predefined role: SOC manager or Endpoint operations analyst
tomsonpl
reviewed
Jan 21, 2025
tomsonpl
previously approved these changes
Jan 21, 2025
natasha-moore-elastic
changed the title
mergify bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
* Adds new runscript Crowdstrike response action * Add missing information * Updates example * Address feedback * Update example (cherry picked from commit 4a52fe9) # Conflicts: # docs/serverless/endpoint-response-actions/response-actions.asciidoc # docs/serverless/endpoint-response-actions/third-party-actions.asciidoc
natasha-moore-elastic
added a commit
that referenced
this pull request
Jan 28, 2025
#6435) (#6490) * [Jan 28] Adds new runscript Crowdstrike response action (#6435) * Adds new runscript Crowdstrike response action * Add missing information * Updates example * Address feedback * Update example (cherry picked from commit 4a52fe9) # Conflicts: # docs/serverless/endpoint-response-actions/response-actions.asciidoc # docs/serverless/endpoint-response-actions/third-party-actions.asciidoc * Delete docs/serverless directory and its contents --------- Co-authored-by: natasha-moore-elastic <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.
Resolves #6365.
Previews
ESS:
Serverless: