Insights

Secure file transfer: methods and checks for sensitive files

Compare SFTP, FTPS and HTTPS, then check recipient access, stored copies, server identity and file integrity before and after sending.

Illustration of document courier pouch with tamper-evident seal.
On this page

Secure file transfer moves files through an encrypted, authenticated connection with checks for unwanted changes. Common methods include SFTP (SSH File Transfer Protocol), FTPS (File Transfer Protocol Secure) and HTTPS (Hypertext Transfer Protocol Secure). Choose one your recipient can use, then check permissions and protection for stored copies.

In short:

  • Choose the channel. Match SFTP, FTPS or HTTPS to your recipient’s workflow.
  • Check beyond encryption. Confirm identity, limit access and protect stored copies.
  • Confirm the result. Check completion and the available integrity result before treating the transfer as successful.

What makes a file transfer secure

Encryption in transit protects file data while it crosses the connection. Authentication checks the identity of the parties sending or requesting files. Authorization limits what an authenticated person or system can view, move, change or delete. Integrity checks help you spot changes between the original file and the received copy.

These protections do different jobs. An encrypted connection to the wrong destination still sends your file to the wrong place. A correctly identified recipient may have more access than they need. Check both identity and permissions before sending sensitive data.

Stored files need their own protection after the connection closes. Logging can record who moved a file, when and from where. That’s useful when you need a record, but an enterprise audit system isn’t required for every personal transfer.

Which method fits your transfer

SFTP uses Secure Shell (SSH) to encrypt both commands and file data. FTPS adds Transport Layer Security (TLS) to File Transfer Protocol (FTP), so it’s distinct from SFTP. HTTPS supports secure web transfers, including browser uploads.

Choose the channel by how your recipient receives files, then check the controls around it.

Transfer channelPractical fitRemaining checks
SFTPWorkflows built around SSHServer host key, user permissions, stored copies
FTPSExisting FTP workflows with TLSServer certificate, user permissions, stored copies
HTTPSBrowser uploads and sharing portalsSite certificate, recipient access, stored copies

A file-sharing portal is an application, not a competing transfer protocol. For collaboration with colleagues or clients, a content collaboration or file-sharing service may fit better than a workflow built around repeated back-and-forth transfers. Check how the recipient gets access and whether the service’s sharing controls fit your needs.

Managed file transfer (MFT) is a platform that manages file movement and its surrounding workflow. MFT platforms can add automation and auditing, which become useful when recurring transfers need central oversight. A portal or MFT platform can use secure channels, so choose the channel separately from the workflow. You don’t need an enterprise platform just to get an encrypted connection.

What encryption doesn’t cover

Transport encryption protects the connection, not every copy created along the way. Check how staging files, archives and destination copies are protected, who can access them and how long they’re kept. Encrypted storage isn’t the same as end-to-end encryption, where only the communicating endpoints can decrypt the content. Neither HTTPS nor encrypted storage alone proves that a service provider can’t read your files.

Some sharing services offer password protection, view-only access and expiry dates. Those are application controls, not features you get from every secure protocol. Revoking a link or letting it expire doesn’t delete copies a recipient already downloaded. Set sharing controls before sending, but also agree on how the recipient should handle saved copies.

Malware checks are separate from connection security. Files shared through a third-party service may not be scanned for malware. Check whether your chosen service or receiving system performs the scan your workflow needs. An integrity check can detect changes without proving that the file’s contents are safe.

What to check before and after sending

Have the intended recipient, destination, chosen method, required permissions, storage requirements and original file ready. Only change systems you own or administer, and keep the original file until receipt is confirmed.

1. Confirm the recipient and destination.

Check who should receive the file and where it should go. Confirm the destination address or server, along with the intended account or folder. You should be able to name the destination without relying only on a familiar display name.

2. Check the server’s identity.

For SFTP, check the host key, which is the server’s identifying key. For FTPS or HTTPS, check the server certificate against the expected destination. This checks server identity, not the recipient’s permission to access the file. If you can’t verify the key or certificate, stop and confirm the destination with its administrator.

3. Use strong authentication and narrow access.

Use strong credentials or keys. Check that the recipient can access only the files and actions they need. Don’t grant access to a whole folder or account just to send one file.

4. Confirm connection and storage protection.

Check that your tool is using the selected encrypted channel. Confirm protection for copies left on the sending system, transfer service and destination. Check how long those copies will remain and who can access them.

5. Send the file and check completion.

Send the file, then check the tool’s completion status. A completed status reports that the transfer finished. It doesn’t prove that the recipient opened or read the file.

6. Check integrity and record the result.

Use the tool’s available integrity check to compare the original and received file. A checksum is a value calculated from file data that helps detect changes. A matching checksum supports that the compared data hasn’t changed, but it doesn’t authenticate the sender or prove the file is safe.

If the tool offers no integrity check, record that integrity wasn’t confirmed. If the transfer fails or the integrity result differs, stop and investigate before retrying. When your policy requires a record, note the destination, who had access, completion status and integrity result.

Where doxx.net fits. doxx.net offers direct device-to-device connections and full, unmodified file transfer between devices. To use the private network, create a doxx.net account, download the app and connect a device.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.