Use the Remote Access v2 integration instead.
This integration enables Cortex XSOAR to access and run commands on a terminal in a remote location (via SSH). For example this could be used to connect to a remote machine and search for malicious files.
Can be used via the Cortex XSOAR CLI or in a Playbook.
To use the Remote Access integration with a custom certificate you need to add custom credential and then add the certificate.
- Navigate to Settings > Integrations > Credentials.
- Click the New button.
|Credential Name||A meaningful name for the credential that you will select when configuring the Remote Access integration|
|Username||Username of the user you are creating the credentials for|
|Workgroup||Workgroup the user is member of|
|Certificate||Custom certificate to use for these credentials|
- When you configure the integration instance, make sure you select the credentials you created.
Go to ‘Settings > Integrations > Servers & Services’
Locate the Remote Access integration by searching for it using the search box on the top of the page.
Click ‘Add instance’ to create and configure a new integration. You should configure the following Remote Access and Cortex XSOAR specific settings:
Name: A textual name for the integration instance.
Default Hostname or IP Address: The hostname or IP address of the Remote Access Make sure the URL is reachable with respect to IP address and port.
Credentials and Password: Configure credentials in the Credentials section in Cortex XSOAR, including a valid certificate. Ciphers: Specify the ciphers to use for the inception. To use more and one cipher divide between then with commas (,). The supported ciphers are: “aes128-ctr”, “aes192-ctr”, “aes256-ctr” and “email@example.com”, “arcfour256”, “arcfour128".
Interactive terminal mode (checkbox): When using this option Cortex XSOAR cleans the response from the remote machine.
Terminal Type: The terminal emulator program to use such as xterm (default), GNOME Terminal, Konsole, and Terminal.
Cortex XSOAR Engine: If relevant, select the engine that acts as a proxy to the server. Engines are used when you need to access a remote network segments and there are network devices such as proxies, firewalls, etc. that prevent the Cortex XSOAR server from accessing the remote networks. For more information on Cortex XSOAR engines see here
Require users to enter additional password: Select whether you’d like an additional step where users are required to authenticate themselves with a password.
Testbutton to validate connection. After completing the test successfully, press the
- copy-from - Copy file from remote system to war room
- copy-to - Copy file from war room to remote system
- ssh - Run command on remote system with ssh