SSH
LAST UPDATED: MAY 5, 2025
Overview
The SSH integration enables organizations to generate a SSH connection and run SSH commands.
D3 SOAR is providing REST operations to function with SSH.
SSH is available for use in:
D3 SOAR | V16.8+ |
Category | SIEM |
Deployment Options |
Connection
To connect to SSH from D3 SOAR, gather the following information:
Parameter | Description | Example |
SSH Server | The SSH Server IP address or hostname. | 192.168.185.1 |
Authentication Type | The authentication type for the SSH server connection:
To use SSH private key, SSH key pairs must be generated and the SSH public key must be copied to the target SSH server beforehand. | SSH Private Key |
User Name | The user name to authenticate the API connection. | demoUser |
Password | When Basic - UserName/Password authentication type is selected, the password of the login user to connect to the SSH server must be specified. | ***** |
Private Key | When SSH private key authentication type is selected, the private SSH key to connect to the SSH server must be specified. | BEGI*****EKEY |
Passphrase | When SSH Private Key authentication type is selected, specify the passphrase used when generating the SSH key pairs. If no passphrase was used, leave this field empty. | <Passphrase> |
SSH Port | The SSH port to use for the connection. By default, the value is 22. | 22 |
Configuring SSH to Work with D3 SOAR
See https://www.ssh.com/academy/ssh/keygen for instructions on generating SSH key pairs.
Configuring D3 SOAR to Work with SSH
Log in to D3 SOAR.
Find the SSH integration.
Navigate to Configuration on the top header menu.
Click on the Integration icon on the left sidebar.
Type SSH in the search box to find the integration, then click it to select it.
Click on the + Connection button on the right side of the Connections section. A new connection window will appear.
Configure the following fields to create a connection to SSH.
Connection Name: The desired name for the connection.
Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as 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): Specifies 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): Add a description for the connection.
Tenant (Optional): When configuring the connection from a master tenant site, users have the option to choose the specific tenant sites to share the connection with. 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: Check the checkbox to ensure the connection is available for use.
System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.
Authentication Type: Basic - UserName/Password1. Input the SSH server.
2. Select the Basic - UserName/Password authentication type.
3. Input the username.
4. Input the password.
5. Input the SSH port. By default, the value is 22.
Authentication Type: SSH Private Key1. Input the SSH server.
2. Select the SSH Private Key authentication type.
3. Input the username.
4. Input the private key.
5. Input the passphrase.
6. Input the SSH port. By default, the value is 22.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.
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.
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
SSH includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command function, users can execute these commands independently for playbook troubleshooting.
Integration API Note
For more information about the SSH API, refer to the SSH API reference.
Execute SSH Command
Executes SSH commands on a remote SSH server.
Input
Input Parameter | Required/Optional | Description | Example |
Command | Required | The command to execute on the SSH server. | cd /home/d3user; pwd; ls -la |
Output
To view the sample output data for all commands, refer to this article.
Error Handling
If the Return Data displays 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. | Execute SSH Command 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 SSH 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: You must have a valid Support account to call this API. |
Error Sample Data Execute SSH Command failed. Status Code: 403. Message: You must have a valid Support account to call this API. |
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: A connection issue with the integration The API returned an error message No response from the API More details about an error can be viewed in the Error tab. | String |
Error Handling
If the Return Data displays 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 SSH 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: You must have a valid support account to call this API. |
Error Sample Data Test Connection failed. Failed to check the connector. Status Code: 403. Message: You must have a valid Support account to call this API |