--- title: "How to transfer a file in Terminal Proxy sessions using SFTP" slug: "pam-session-how-to-transfer-a-file-in-terminal-proxy-sessions-using-sftp" updated: 2026-11-03T14:48:22Z published: 2026-11-03T14:48:22Z canonical: "docs.senhasegura.io/pam-session-how-to-transfer-a-file-in-terminal-proxy-sessions-using-sftp" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt > Use this file to discover all available pages before exploring further. # How to transfer a file in Terminal Proxy sessions using SFTP This document provides information about a step-by-step guide on how to perform file transfer using SFTP in remote Terminal Proxy sessions. **Attention** Some SSH tools, such as MobeXterm, automatically set an SFTP connection to transfer files after logging in with SSH. These SFTP connections **won’t work**, as the Segura™ proxy treats them separately. ## Requirements - Terminal Proxy type credential active. - Start a connection via Multihop Terminal Proxy. **Info** To transfer files directly to a destination server using SFTP, you must use the [Multihop](/v4-2/docs/pam-session-how-to-make-an-ssh-multihop-connection-via-terminal-proxy) connection because binaries traveling under SFTP have no way to interact with the intermediate terminal. --- ## Transfer via SFTP on the terminal Due to limitations of the protocol the user can’t use a personal credential to perform the file transfer. Only with a credential registered in Segura™ will be possible to perform the transfer. Also, it won’t be possible to record the session, but it’s still possible to enable logging with a report of transferred files. To learn how to enable this log, access the [File transfer](/v4-2/docs/pam-session-activate-remote-session-file-transfer-triggers) document. To start, follow the steps and replace the strings with the values ​​described in the table below. | **String** | **Description** | | --- | --- | | `segura_user` | User of the Segura™ vault. | | `segura_vault` | Hostname or IP address of the Segura™ vault. | | `credential` | Credential user you want to use for access. | | `target_device` | Hostname or IP address of the device you want to access. | | `connectivity.port` | Type of connectivity used and its corresponding port. | | `mfa_token` | Code generated by MFA Token. | | `file_name` | Name of the file to be transferred. | 1. Open the **command prompt** application of your preference. 1. Type `sftp segura_user[credential@target_device]@segura_vault` **Attention** If the use of the OTP token is registered, it must be entered as the example: `sftp segura_user[credential@target_device]mfa_token@segura_vault`. 2. Use the commands below to: 1. Perform the file **upload**, type: 1. `put [file_name]` 2. Press the **Enter** key to start. 3. When the file is complete, a `<file_name> 100%` message will be displayed. 2. Perform the file **download**, type: 1. `get [file_name]` 2. Press the **Enter** key to start. 3. When the file is complete, a `<file_name> 100%` message will be displayed. 3. When finished, type: 1. `exit` After completion, the files will be saved. When performing an upload it’ll be saved on the target machine and when downloading it’ll be saved on the user's machine. For the files to be saved within the Segura™ shell, it’s necessary to perform the `sftp` without the use of Multihop. --- ## Via WinSCP application 1. Open the **WinSCP** application on your machine. 2. On the **Login** screen fill in the fields in **Session** section. 1. **File protocol**: select **SFTP**. 2. **Host name**: type the hostname or IP address of the Segura™ vault. 3. **Port number**: type 22. 4. **User name**: type `sftp segura_user[credential@target_device]@segura_vault` 5. **Password**: enter your Segura™ access password 3. Click **Login**. After these steps, the connection will be ready for use, follow the tool's instructions to transfer the files. #### With the use of a device with different registered connectivities For the connection accessing a device that has more than one registered connectivity, it is necessary to indicate which type of connection will be used and the corresponding port number. `sftp segura_user[credential@target_device[connectivity.port]]@segura_vault` **Attention** If the use of the OTP token is registered, it must be entered as the example: `sftp segura_user[credential@target_device[connectivity.port]]mfa_token@segura_vault`. #### With the use of OTP token For the connection using an OTP token, when the **Trust this computer** parameter is enabled, it’s necessary to provide the answer in the connection code line. **Info** Both uppercase and lowercase letters (Y/y) (N/n) are recognized for the parameter's response. - **Trust this computer enabled and positive response** (the computer will be trusted for the configured number of hours): `sftp senhasegura_user[credential@target_device]mfa_tokenY@senhasegura_vault` - **Trust this computer enabled and negative response** (it will be necessary to inform the token again in the next connection): `sftp senhasegura_user[credential@target_device]mfa_tokenN@senhasegura_vault`` If the **Trust this computer** parameter is disabled, it isn’t necessary to use Y/y or N/n in the connection line: `sftp senhasegura_user[credential@target_device]mfa_token@senhasegura_vault` The Segura™ Terminal Proxy also offers another type of file transfer via SCP. To find out how to perform this, access the [How to transfer a file in Terminal Proxy sessions using SCP](/v4-2/docs/pam-session-how-to-transfer-a-file-in-terminal-proxy-sessions-using-scp) document. --- Do you still have questions? Reach out to the [Segura™ Community](https://community.senhasegura.io/).