Crowdstrike Falcon Sandbox
LAST UPDATED: NOVEMBER 12, 2025
Overview
CrowdStrike Falcon Sandbox is an automated malware analysis solution that empowers security teams by overlaying comprehensive threat intelligence with the results of the sandbox solution. Falcon Sandbox performs deep analysis of evasive and unknown threats, enriches the results with threat intelligence, and delivers actionable indicators of compromise (IOCs). This integration enables organizations to submit files and URLs for analysis and retrieve analysis reports.
D3 SOAR is providing REST operations to function with Crowdstrike Falcon Sandbox.
Crowdstrike Falcon Sandbox is available for use in:
Connection
Gather the following information to connect D3 SOAR to CrowdStrike Falcon Sandbox.
Parameter | Description | Example |
Server URL | The domain level URL of the Crowdstrike Falcon Sandbox server. | https://api.crowdstrike.com |
Client ID | The client ID to authenticate the API connection. | acb9*****66a9 |
Client Secret | The client secret to authenticate the API connection. | m132*****Setf |
API Version | The version of the API to use for the connection. | v1 |
Configuring D3 SOAR to Work with Crowdstrike Falcon Sandbox
Log in to D3 SOAR.
Find the Crowdstrike Falcon Sandbox integration.
.png?inst-v=5ce09ce6-3dcb-41fc-bcfb-f4b8739ef100)
Navigate to Configuration on the top header menu.
Click on the Integration icon on the left sidebar.
Type Crowdstrike Falcon Sandbox in the search box to find the integration, then click it to select it.
Click + Connection, on the right side of the Connections section. A new connection window will appear.
Configure the following fields to create a connection to Crowdstrike Falcon Sandbox.
.png?inst-v=5ce09ce6-3dcb-41fc-bcfb-f4b8739ef100)
Connection Name: The desired name for the connection.
Site: The site on which to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.
Recipient site for events from connections Shared to Internal Sites: This field is displayed when Share to Internal Sites is selected for the Site field, allowing selection of the internal site for deploying the integration connection.
Agent Name (Optional): The proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.
Description (Optional): The description for the connection.
Tenant (Optional): When configuring the connection from a master tenant site, users can choose the specific tenant sites with which to share the connection. Once this setting is enabled, users can filter and select the desired tenant sites from the dropdowns to share the connection.
Configure User Permissions: Defines which users have access to the connection.
Active: The checkbox that enables the connection to be used when selected.
System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.
.png?inst-v=5ce09ce6-3dcb-41fc-bcfb-f4b8739ef100)
1. Input the domain level Server URL. The default value is https://api.crowdstrike.com.
2. Input the Client ID.
3. Input the Client Secret.
4. Input the API Version. The default value is v1.Connection Health Check: Periodically checks the connection status by scheduling the Test Connection command at the specified interval (in minutes). Available only for active connections, this feature also allows configuring email notifications for failed attempts.
Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Refer to the password vault connection guide if needed.
Test the connection.
Click on the Test Connection button to verify credentials and connectivity. A success alert displays Passed with a green checkmark. If the connection fails, review the parameters and retry.
Click OK to close the alert window.
Click + Add to create and add the configured connection.
Commands
Crowdstrike Falcon Sandbox includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command, users can execute these commands independently for playbook troubleshooting.
Integration API Note
For more information about the Crowdstrike Falcon Sandbox API, refer to the Crowdstrike Falcon Sandbox API reference.
Check Analysis Status
Checks the statuses of the specified sandbox analyses.
READER NOTE
The parameter Submission IDs is required to run this command.
Run the Submit Files or Submit URLs command to obtain Submission IDs. Submission IDs can be found in the returned raw data of both commands at the path $[*].resources[0].id.
Input
Input Parameter | Required/Optional | Description | Example |
Submission IDs | Required | The IDs of the submitted malware samples, and samples can be files or URLs. The submission ID can be obtained using the Submit Files or Submit URLs commands. |
JSON
|
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Check Analysis Status failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Check Analysis Status failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Get Artifact
Downloads IOC packs, PCAP files, and other analysis artifacts.
READER NOTE
Artifact ID is a required parameter to run this command.
Run the Get Report Summaries or Get Full Report command to obtain the Artifact ID. Artifact IDs can be found in the returned raw data of both commands.
Input
Input Parameter | Required/Optional | Description | Example |
Artifact ID | Required | The ID of an artifact to download. Such as an IOC pack, PCAP file, or actor image. The artifact ID can be obtained using the Get Report Summaries or Get Full Report command. Note: if you want to download screenshots, PCAP or memory artifacts, you have to get related artifact IDs in the full report. | *** |
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Error Sample Data Get Artifact failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Get Full Reports
Retrieves full reports of the specified sandbox analyses.
READER NOTE
The parameter Submission IDs is required to run this command.
Run the Submit Files or Submit URLs command to obtain the Submission IDs. Submission IDs can be found in the returned raw data of both commands at the path $[*].resources[0].id.
Input
Input Parameter | Required/Optional | Description | Example |
Submission IDs | Required | The IDs of the submitted malware samples, and samples can be files or URLs. The submission ID can be obtained using the Submit Files or Submit URLs commands. |
JSON
|
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Get Full Reports failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Get Full Reports failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Get Report Summaries
Retrieves the short summaries version of the specified sandbox reports.
READER NOTE
The parameter Submission IDs is required to run this command.
Run the Submit Files or Submit URLs command to obtain the Submission IDs. Submission IDs can be found in the returned raw data of both commands at the path $[*].resources[0].id.
Input
Input Parameter | Required/Optional | Description | Example |
Submission IDs | Required | The IDs of the submitted malware samples, and samples can be files or URLs. The submission ID can be obtained using the Submit Files or Submit URLs commands. |
JSON
|
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Get Report Summaries failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Get Report Summaries failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Query Reports
Finds sandbox reports by providing an FQL filter and paging details. Returns a set of report IDs that match your criteria. Notes: Report ID is the same as Submission ID if the analysis is successful.
Input
Input Parameter | Required/Optional | Description | Example |
Filter | Optional | The filter criteria in the form of a Falcon Query Language (FQL) query. For more information, please refer to Falcon Query Language (FQL). | verdict: "malicious" |
Limit | Optional | The maximum number of report IDs to return. The available input is an integer between 1 and 5000. The default value is 5000. | 10 |
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Query Reports failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Query Reports failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Query Submissions
Finds submission IDs for uploaded files or URLs by providing an FQL filter and paging details. Returns a set of submission IDs that match your criteria.
Input
Input Parameter | Required/Optional | Description | Example |
Filter | Optional | The filter criteria in the form of a Falcon Query Language (FQL) query. For more information, please refer to Falcon Query Language (FQL). | state:!'success' + origin:'uiproxy' + user_tags:*'****' |
Limit | Optional | The maximum number of submission IDs to return. The available input is an integer between 1 and 5000. The default value is 5000. | 10 |
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Query Submissions failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Query Submissions failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Submit Files
Uploads files for sandbox analysis.
File IDs and File Source
It is not recommended to use the Test Command feature with the Submit Files command as it is designed for dynamic input files in Playbooks, Incident Attachments, and Artifact Attachments. There is a simple workaround to test the command:
Navigate to Configuration on the top bar menu.
Click on Utility Commands on the left sidebar menu.
Use the search box to find and select the Create a File from input Text Array command.
Click on the Test tab.
Input the required information for the parameters.
Click on the Test Command button. A D3 File ID will appear in the output data after the file has been successfully created. The D3 File Source of the created file will be Playbook File.
Input
Input Parameter | Required/Optional | Description | Example |
File IDs | Required | The file path of the file source. |
JSON
|
File Source | Required | The file source of the file to send. The options for file sources are:
| Playbook File |
Detonation Environment | Required | The detonation environment used for analysis. | Windows 10, 64-bit |
Action Script | Optional | The runtime script for sandbox analysis. The default action is Default analysis. | Heavy Anti-Evasion |
Command Line | Optional | The command line script passed to the submitted file. The max length of the command line is 2048 characters. | hostname |
Document Password | Optional | The prompt password auto-filled for Adobe or Office files. The max length of the password is 32 characters. | password |
Network Settings | Optional | The sandbox network settings are used for analysis. The default network setting is Default network connectivity. | Conceal network traffic using Tor |
Send Email Notification | Optional | Sends an email notification when an analysis is complete. The possible option is True or False. The default value is False. | True |
Custom Tags | Optional | The custom tags for the analysis. |
JSON
|
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Submit Files failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Submit Files failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Submit URLs
Submits URLs for sandbox analysis.
Input
Input Parameter | Required/Optional | Description | Example |
URLs | Required | The web page or file URL to submit. The inputs can be HTTP(S) or FTP. |
JSON
|
Detonation Environment | Required | The detonation environment used for analysis. | Windows 10, 64-bit |
Action Script | Optional | The runtime script for sandbox analysis. The default action is Default analysis. | Heavy Anti-Evasion |
Command Line | Optional | The command line script passed to the submitted file. The max length of the command line is 2048 characters. | hostname |
Document Password | Optional | The prompt password auto-filled for Adobe or Office files. The max length of the password is 32 characters. | password |
Network Settings | Optional | The sandbox network settings are used for analysis. The default network setting is Default network connectivity. | Conceal network traffic using Tor |
Send Email Notification | Optional | Sends an email notification when an analysis is complete. The possible option is True or False. The default value is False. | True |
Custom Tags | Optional | The custom tags for the analysis. | [ "USERTAG1" ] |
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data is Partially Successful or Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Submit URLs failed. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Submit URLs failed. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Test Connection
Allows users to perform a health check on an integration connection. Users can schedule a periodic health check by selecting Connection Health Check when editing an integration connection.
Input
N/A
Output
Output Type | Description | Return Data Type |
Return Data | Indicates one of the possible command execution states: Successful or Failed. The Failed state can be triggered by any of the following errors:
More details about an error can be viewed in the Error tab. | String |
Error Handling
If the Return Data is Failed, an Error tab will appear in the Test Result window.
The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.
Parts in Error | Description | Example |
Failure Indicator | Indicates the command failure that happened at a specific input and/or API call. | Test Connection failed. Failed to check the connector. |
Status Code | The response code issued by the third-party API server or the D3 SOAR system that can be used to locate the corresponding error category. For example, if the returned status code is 401, the selected connection is unauthorized to run the command. The user or system support would need to check the permission setting in the Crowdstrike Falcon Sandbox portal. Refer to the HTTP Status Code Registry for details. | Status Code: 403. |
Message | The raw data or captured key error message from the integration API server about the API request failure. | Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |
Error Sample Data Test Connection failed. Failed to check the connector. Status Code: 403. Message: Failed to issue access token - Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). |