Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/management/admin/response-actions.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,33 @@ Example: `scan --path "/Users/username/Downloads" --comment "Scan Downloads fold

NOTE: Scanning can take longer for directories containing a lot of files.

[discrete]
[[runscript]]
=== `runscript`

NOTE: This response action is supported only for <<crowdstrike-response-actions, CrowdStrike-enrolled hosts>>.

Run a script on a host. You must include one of the following parameters to identify the script you want to run:

* `--Raw`: The full script content provided directly as a string.
* `--CloudFile`: The name of the script stored in a cloud storage location.
* `--HostPath`: The absolute or relative file path of the script located on the host machine.

You can also use these optional parameters:

* `--CommandLine`: Additional command-line arguments passed to the script to customize its execution.
* `--Timeout`: The maximum duration, in seconds, that the script can run before it's forcibly stopped. If no timeout is specified, it defaults to 60 seconds.

Required privilege: **Execute Operations**

Examples:

`runscript --CloudFile="CloudScript1.ps1" --CommandLine="-Verbose true" --Timeout=180`

`runscript --Raw=```Get-ChildItem.````

`runscript --HostPath="C:\temp\LocalScript.ps1" --CommandLine="-Verbose true"`

[discrete]
[[supporting-commands-parameters]]
== Supporting commands and parameters
Expand Down
4 changes: 4 additions & 0 deletions docs/management/admin/third-party-actions.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,10 @@ These response actions are supported for CrowdStrike-enrolled hosts:
+
Refer to the instructions on <<isolate-a-host,isolating>> and <<release-a-host,releasing>> hosts for more details.

* **Run a script on a host** with the <<runscript,`runscript` response action>>.

* **View past response action activity** in the <<response-actions-history,response actions history>> log.

[discrete]
[[sentinelone-response-actions]]
== SentinelOne response actions
Expand Down