Secure FTP Solutions | Encrypted, Modern FTP Alternatives

What is SFTP?

SFTP, which stands for SSH File Transfer Protocol, is a secure file transfer protocol used to secure and send file transfers over secure shell (SSH). This SFTP connection, as a network protocol, implements AES, Triple DES, and similar algorithms to encrypt files as they transfer between systems.

How Does SFTP Work?

SFTP works over the [Secure Shell (SSH)](/content/blog/are-ssh-and-sftp-the-same "Are SSH and SFTP the Same?"/index.html) data stream to establish a secure connection and provide organizations with a higher level of file transfer protection. This is because SFTP uses encryption algorithms to securely move data to your server and keep files unreadable during the process. Authentication prevents unauthorized file access during the operation. [Read more on how the SFTP connection works >](/content/blog/how-sftp-works "How SFTP Works"/index.html)

SFTP Encryption

SFTP uses AES, Triple DES, and similar algorithms to encrypt files during data transfer. SFTP uses a single port number ([port 22](/content/blog/what-port-does-sftp-use "What Port Does SFTP Use?"/index.html)) to establish a secure connection and encrypts both authentication information and the files being transferred. [Read more on SFTP encryption >](/content/blog/are-sftp-files-encrypted "Are SFTP Files Encrypted?"/index.html)

Authentication Methods

An SFTP server requires trading partners to authenticate in one of two different ways. They can either prove their identity with a user ID and password (this information is encrypted over the SFTP connection rather than sent over plain text) or validate with an SSH key. Users can also use two-factor authentication and a combination of SSH key and password. These types of authentications prevent imposters from connecting to the SFTP server.

There's some debate on whether SSH keys or passwords are better at protecting and validating company SFTP servers. For a full comparison of the two authentication methods, read [Are SSH Keys or Passwords Better for SFTP Authentication?](/content/blog/are-ssh-keys-or-passwords-better-for-sftp-authentication "Are SSH Keys or Passwords Better for SFTP Authentication?"/index.html)

What is Secure FTP?

File Transfer Protocol (FTP) is a network protocol used to transfer files between clients and servers. Secure FTP solutions take the basic function of FTP – file transfers – and makes it more secure. Since FTP is not secure in and of itself, it is often secured with SSL/TLS (to become FTPS) or replaced with SFTP (SSH File Transfer Protocol) solutions.

SFTP vs. FTP

The biggest, and one of the most crucial differences, between FTP and SFTP is the fact that one is encrypted (SFTP) while the other is not (FTP). SFTP is a much more secure protocol compared to FTP, considering that when files are being sent and received using "standard" FTP, they are done so in an unencrypted manner. [Read more >](/content/blog/are-sftp-and-ftp-the-same "Are SFTP and FTP the Same?"/index.html)

When to Use FTP

FTP still exists today but, while a surprising number of people still use it to move files from point A to B, it is no longer the best way to ensure the secure transfer of files.

FTP should only be used when you are exchanging or sending files that aren’t sensitive in nature. If standard FTP is running on your organization’s server, you should disable it as soon as possible; FTP is over 30 years old and isn’t meant to withstand the modern security threats we face today. FTP is not encrypted, and it lacks privacy and integrity, which makes it easy for a hacker to gain access and capture or modify your data while it’s in transit. [More on when to use FTP >](/content/blog/ftp-ftps-and-sftp-which-protocol-should-you-use-and-when "When to Use FTP vs. FTPS or SFTP"/index.html)

Why Shouldn't You Use FTP?

• Authentication. FTP isn’t authenticated, meaning information including your ID and password are sent as plain text, rather than [encrypted](/content/solutions/file-encryption "File Encryption Cornerstone"/index.html). FTP as a whole is not encrypted, leaving your information unprotected.
• Maintenance. FTP was never intended to be used forever, and other file transfer protocols have sprung up to replace FTP and protect data.
• Compliance. FTP is not robust enough to ensure the secure transfer of files. More specifically, it does not meet many of today’s business and compliance requirements. New data security standards and regulations stipulate the minimum requirements for secure data transfers – and FTP is not one of them.

Should You Replace Your FTP Scripts?

As cybersecurity is increasingly top-of-mind for organizations, many are moving away from FTP to file transfer tools that are secure, easy to use and maintain, and include more features. The benefits of replacing legacy scripts and FTP include gaining the ability to centralize your workflows, automating your data movement, easily meeting compliance regulations, and overall securing your transfers. [Keep Reading >](/content/blog/replace-your-ftp-scripts-to-increase-security "Replace Your FTP Scripts to Increase Security"/index.html)

How to Secure Your FTP Server

1. Place your servers behind a gateway. Many organizations store their FTP servers in the DMZ, a public-facing segment that is easy to attack. Using an enhanced reverse proxy like a DMZ Secure Gateway keeps files and credentials in the private network, rather than opening inbound ports.
2. Implement IP Blacklists and Whitelists. An IP blacklist allows you to deny system access to a range of IP addresses, either temporarily or permanently. If your trading partners use fixed IPs, you can whitelist their specific IP addresses.
3. Implement file and folder security. Limit folder access to only the essentials. Encrypt files at rest, especially if they’re stored in the DMZ, and retain files on the FTP server only as long as needed.
4. Lock down administration. Restrict admin duties to a limited number of users and require to use multi-factor authentication. Avoid easy-to-guess admin user IDs like “root” or “admin,” and protect passwords by storing them in an AD domain or LDAP server.

More best practices: [10 Essential Tips for Securing FTP and SFTP Servers >](/content/blog/10-essential-tips-for-securing-ftp-and-sftp-servers "10 Essential Tips for Securing FTP and SFTP Servers"/index.html)

See More SFTP Benefits

Move beyond FTP and learn how to secure and manage your file transfers.

Get the Guide

Alternatives to Secure File Transfer Protocol

Back in the day, File Transfer Protocol (FTP) was the go-to method for sending files. Now, there are more options, all of which improve on security including FTPS, HTTPS, AS2, and MFT.

SFTP vs. FTPS

Two mainstream protocols available for secure file transfers are [Secure Shell (SSH) File Transfer Protocol (SFTP)](/content/blog/how-sftp-works "How SFTP Works"/index.html) and [File Transfer Protocol over SSL/TLS (FTPS)](/content/blog/what-is-ftps "What is FTPS?"/index.html). Because SFTP and FTPS implement strong algorithms like AES and Triple DES to encrypt any data transferred, they both offer a high level of protection. [Read more >](/content/blog/sftp-vs-ftps-what-is-the-best-secure-ftp-protocol "SFTP vs. FTPS: What's the Best Protocol for Secure FTP?"/index.html)

SFTP vs. AS2

AS2, part of the [Applicability Statement family](/content/solutions/as2-transfers "AS2, AS3, and AS4 Transfers Cornerstone"/index.html), is one of the top file transfer protocols for Electronic Data Interchange (EDI) information. AS2 uses a secure TLS layer to secure data in transit and gives users the option of using a digital certification for authentication.

Unlike SFTP, AS2 has a feature that makes it unique: it allows users to request a Message Disposition Notification (MDN), also known as a receipt, that alerts the sender once the message has been received and decrypted by the recipient. For a deeper dive into the differences, read [Which is Better: AS2 vs. SFTP?](/content/blog/which-is-better-as2-vs-sftp "Which is Better: AS2 vs. SFTP?"/index.html)

SFTP vs. SSH

Although they are both used to transfer information securely, unlike SFTP, SSH is able to exist on its own. Typical applications for SSH are remote command-line, login, and remote command execution. SFTP is the file transfer protocol that provides secure file access, file transfer, and file management over a reliable data stream.

[Read more about the differences between SFTP and SSH >](/content/blog/are-ssh-and-sftp-the-same "Are SSH and SFTP the Same?"/index.html)

SFTP vs. MFT (Managed File Transfer)

By nature, SFTP and MFT solutions both work to protect data in transit. They both authenticate trading partner connections with a combination of user IDs, passwords, or keys, and they both help satisfy strict requirements for data security laws like PCI DSS, HIPAA, and the GDPR. However, MFT solutions offer [more functionality](/content/blog/managed-file-transfer-more-than-sftp "Managed File Transfer: It's More than SFTP"/index.html) than just an SFTP connection.

• Flexibility: secure managed file transfer supports most file transfer protocols, including AS2, HTTPS, SFTP, and FTPS, to secure the exchange of information between users
• Automation: Cut down on user errors, reduce or eliminate the need for scripts, and reduce manual time
• Compliance and auditing: Track file transfer activity to maintain compliance with regulations and privacy laws
• Clustering: Meet high volumes of file transfers by distributing processes across multiple systems for load balancing
• Key and certificate management: Import, export, and monitor SSH keys and SSL certificates, and receive notifications ahead of expiration dates
• Centralization: Manage and monitor all aspects of your file transfers from one dashboard

Managed file transfer includes an extensive list of security features, including encryption for files in motion and at rest, and supports workflow automation, file transfer monitoring, notifications, and auditing. Enhance your team’s productivity in multiple ways while keeping security at the forefront.

[Read more on the differences between SFTP & MFT >](/content/blog/which-is-better-sftp-vs-mft "SFTP vs. MFT: What’s the Difference and Which Is Better?"/index.html)

SFTP Automation

One of the largest differences between SFTP and an MFT solution is the ability to automate file transfer processes. MFT solutions provide SFTP automation, allowing IT professionals to streamline their organization’s exchange of data over a secure SFTP connection. Automation can improve multiple transfer processes: projects and tasks to run, file monitoring, data exchanged with cloud or web services, recurrent file transfers, and file encryption.

[Read more about SFTP automation >](/content/blog/how-to-achieve-sftp-automation-in-your-organization "Unlocking Efficiency: Streamlining Your File Transfer Process with SFTP Automation"/index.html)

SFTP vs. HTTPS

HTTPS (Hypertext Transfer Protocol Secure) is a secure version of HTTP, offering certificate authentication, encrypting a website’s inbound traffic, and using a TLS encryption layer for data integrity and privacy. HTTPS protects the identity, account details, payment information, and other sensitive details on behalf of web visitors.

[Learn more about HTTPS >](/content/blog/comparing-transfer-methods-http-vs-ftp "HTTP vs FTP: File Transfer Speed and Security Compared"/index.html)

SFTP vs. TFTP

Like FTPS and SFTP, Trivial File Transfer Protocol (TFTP) is based around FTP technology but is a completely different protocol. Like FTPS and SFTP, the TFTP protocol does allow for file transfers but uses a completely different approach to how files are transferred.

As you might have gathered from the name, Trivial File Transfer Protocol is a stripped-down transfer protocol: it can only be used to send and receive files. TFTP is best used in cases where you know the exact file and its precise location and don’t require any security or encryption when sending or receiving that file. With TFTP, user authentication and directory visibility are not possible, and TFTP allows anyone who knows the right pathing to upload and download files.

[Read more about TFTP vs. SFTP >](/content/blog/tftp-vs-sftp-the-key-differences "TFTP vs. SFTP: The Key Differences"/index.html)

SFTP vs. SCP

SCP is a more simplified, efficient transport algorithm, making it faster than SFTP, especially on high-latency networks. SCP does not, however, provide the ability to list directories, rename files, or other file management capabilities. It also does not resume transfers if there are connectivity issues.

[Read more about SFTP vs. SCP >](/content/blog/scp-vs-sftp-which-is-better "SCP vs. SFTP: Which is Better?"/index.html)

Secure FTP FAQs

What is FTPS?

FTPS allows you to connect securely with your trading partners, customers, and users. To verify authenticity, FTPS uses a combination of user IDs, passwords, and certificates. FTPS uses TLS to encrypt server connections, X.509 to authenticate connections, and AES and Trip DES to encrypt file transfers.

What are the key differences between SFTP and FTPS?

The differences between SFTP and FTPS include the number of ports required, authentication, speed and implementation.

For a deeper dive, read [SFTP vs. FTPS: The Key Differences](/content/blog/sftp-vs-ftps-the-key-differences "SFTP vs. FTPS: The Key Differences"/index.html).

Which is faster: SFTP vs. FTPS?

FTPS was designed to be more speed-friendly, with the control and data channel running asynchronously in two distinct connections in order to achieve the highest possible data transfer speed. With SFTP, control and synchronization packets are sent on the same channel as data packets. This may cause SFTP to be slightly, but NOT significantly, slower than FTPS. [Read more >](/content/blog/which-is-faster-ftps-or-sftp "FTPS vs. SFTP Speed: Which Is Faster?"/index.html)

Which is better: SFTP vs. FTPS?

If SFTP and FTPS are both secure protocols with similar protection, when is it best to use one over the other? The answer is: it depends. Your choice comes down to your organization’s IT infrastructure, trading partner requirements, how you want to authenticate file transfers, and which ports you want to use. For more guidance which secure FTP solution is best, read Which is Better: [SFTP vs. FTPS?](/content/blog/which-is-better-sftp-vs-ftps "Which is Better: SFTP vs. FTPS?"/index.html)

How secure is an SFTP Connection?

Is SFTP secure enough for you? While SFTP solutions do not require two-factor authentication, you do have the choice to require both a user ID and password, as well as SSH keys, for a more secure connection.

How to secure FTP and SFTP servers

Are FTP, FTPS, or SFTP servers secure? The number one way to secure your FTP servers is to stop using FTP. If standard FTP is running on your server, you should disable it as soon as possible; FTP is over 30 years old and isn’t meant to withstand the modern security threats we face today. FTP is not encrypted, and it lacks privacy and integrity. FTP makes it easy for a hacker to gain access and capture or modify your data while it’s in transit.

Secure your SFTP and FTPS servers with these steps:

1. Use strong encryption and hashing, such as with SFTP and FTPS. Opt for strong ciphers like AES and TDES, or [SHA-2 family algorithms](/content/blog/using-sha-1-to-secure-file-transfers "Still Using SHA-1 to Secure File Transfers? It’s Time to Say Goodbye"/index.html) for verifying transmission integrity, and disable any older, outdated ciphers like Blowfish and DES.
2. Place your servers behind a gateway. Many organizations store their FTP servers in the DMZ, a public-facing segment that is easy to attack. Using an enhanced reverse proxy like a [DMZ Secure Gateway](/content/products/goanywhere-gateway "GoAnywhere Gateway Product Page"/index.html) keeps files and credentials in the private network, rather than opening inbound ports.
3. Implement IP Blacklists and Whitelists. An IP blacklist allows you to deny system access to a range of IP addresses, either temporarily or permanently. If your trading partners use fixed IPs, you can whitelist their specific IP addresses.
4. Harden your FTPS Server. Avoid using Explicit FTPS unless you force encryption for the authentication and data channels, and do not use any version of SSL or TLS 1.0. Plus, you should use Elliptic curve Diffie-Hellman key exchange algorithms.
5. Set secure user policies.
6. Require and use strong passwords.
7. Implement file and folder security. Limit folder access to only the essentials. Encrypt files at rest, especially if they’re stored in the DMZ, and retain files on the FTP server only as long as needed.
8. Lock down administration. Restrict admin duties to a limited number of users and require to use multi-factor authentication. Avoid easy-to-guess admin user IDs like “root” or “admin,” and protect passwords by storing them in an AD domain or LDAP server.

More best practices: [10 Essential Tips for Securing FTP and SFTP Servers](/content/blog/10-essential-tips-for-securing-ftp-and-sftp-servers "10 Essential Tips for Securing FTP and SFTP Servers"/index.html)

How does SFTP work?

Secure File Transfer Protocol (SFTP) works over the Secure Shell (SSH) data stream to establish a secure connection and provide organizations with a higher level of file transfer protection. This is because SFTP uses encryption algorithms to securely move data to your server and keep files unreadable during the process, and authentication prevents unauthorized file access during the operation.

Read more: [How SFTP Works](/content/blog/how-sftp-works "How SFTP Works"/index.html)

What port does SFTP use?

Unlike FTP over SSL/TLS (FTPS), SFTP only needs a single port to establish a server connection — port 22.

What are SFTP servers?

A typical file transfer server helps transfer files server-to-server or client-to-server, and SFTP servers are a more protected version: they encrypt data to keep sensitive information secure while moving files, and some have the added bonus of encrypting files at rest. [SFTP servers](/content/products/goanywhere-mft/file-servers/sftp-server "SFTP Server"/index.html) use a single data channel in which login credentials as well as files are encrypted – because both authentication and files are encrypted, your connection is secure.

Read more: [What are SFTP Servers?](/content/blog/what-are-sftp-servers "What are SFTP Servers?"/index.html)

Are SFTP files encrypted?

Yes, SFTP encrypts files by working over the SSH data stream to establish a secure connection and provide organizations with an increased level of file transfer protection due to its encryption capabilities.

SFTP uses encryption algorithms to securely move data to your server and keep files unreadable during the process, while authentication prevents unauthorized file access during the operation. SFTP uses only one connection and encrypts both authentication information and the files being transferred.

Read more: [Are SFTP Files Encrypted?](/content/blog/are-sftp-files-encrypted "Are SFTP Files Encrypted?"/index.html)

Are SFTP and FTP the same?

No, Secure File Transfer Protocol or SSH File Transfer Protocol (SFTP) and File Transfer Protocol (FTP) are not the same thing. SFTP, not to be confused with FTP Secure (FTPS), is a network which allows file access, transfer, and management over a secure data stream. FTP is a network protocol which is implemented in order to exchange files over a Transmission Control Protocol (TCP) and Internet Protocol (IP) network.

Read more: [Are SFTP and FTP the Same?](/content/blog/are-sftp-and-ftp-the-same "Are SFTP and FTP the Same?"/index.html)

Is SFTP or MFT better?

Choose an SFTP solution if...

If you need a free or otherwise inexpensive way to send and receive secure file transfers to a handful of trading partners, an SFTP server and client tool might suit you. You can achieve basic needs like authenticating your users, transferring unlimited files per server connection, and controlling your port usage.

Choose an MFT solution if...

If you need a way to streamline all aspects of your file transfers, a managed file transfer solution is the better choice. With MFT, you can choose to transfer files using secure FTP protocols, including SFTP, FTPS, HTTPS, and AS2, and more!

Secure File Transfer Protocol (SFTP) Software

SFTP Client

A file transfer client gives you the ability to connect to a server and upload files to or download files from that server. SFTP can be run natively from the shell on most machines, allowing users to transfer files via SFTP from the command line between computers. [Graphical secure FTP clients](/content/blog/winscp-free-sftp-client-or-an-mft-sftp-client "WinSCP Free SFTP Client or an MFT SFTP Client?"/index.html) have user interfaces but still require programmer time to make custom scripts, run commands, manually audit, and potentially use add-on tools (like PuTTYgen).

MFT solutions are among the most robust [secure FTP client software solutions](/content/products/goanywhere-mft/connectivity/sftp "SFTP Client for Managed File Transfer"/index.html). They can be deployed on-premises or in the cloud and give you the ability to streamline and safeguard traditional SFTP data submissions with features like automation, status notifications, transfer resume, and integrity checks.

SFTP Servers

Organizations can securely exchange sensitive data over a network with an [SFTP server](/content/products/goanywhere-mft/file-servers/sftp-server "SFTP server"/index.html).

With GoAnywhere MFT, data integrity and security is assured by using an encrypted tunnel created between the SFTP server and trading partners. This helps to protect all that flows over the connection – data, user IDs, passwords, and commands.

Trading partners can exchange files securely with your organization using [SFTP](/content/solutions/secure-ftp "SFTP"/index.html) (SSH File Transfer Protocol) and SCP (Secure Copy) protocols. They can also authenticate with both passwords and SSH key authentication.

SFTP Server Features

• Robust security and granular permission controls
• Can be installed in the private network without opening inbound ports, when paired with [GoAnywhere Gateway](/content/products/goanywhere-gateway "GoAnywhere Gateway"/index.html) in the DMZ
• Highly scalable with no restrictions on the number of trading partners
• Allows only strong NIST-certified encryption algorithms when in [FIPS 140-2 Compliance](/content/products/goanywhere-mft/encryption/fips-140-2 "FIPS 140-2 Compliance"/index.html) mode
• Support for multiple listeners with configurable port numbers
• Multiple authentication methods; database, Active Directory (AD), LDAP and IBM i
• Event [triggers](/content/products/goanywhere-mft/automation/triggers "triggers"/index.html) to automatically process files or send email notifications
• Support for client requests to resume file transfers
• Configurable settings for maximum number of sessions, maximum login failures and idle timeouts
• ZLIB compression to reduce bandwidth requirements
• Ability to accept or reject files with certain extensions

Free SFTP Software vs. Enterprise

Free SFTP software an inexpensive way to occasionally exchange files, providing basic functionality for simplistic needs. Enterprise-level SFTP software typically comes with robust security, automation, auditing and reporting functionality that streamline the transfer processes across an organization.

As you evaluate your needs against your budget, weigh [these pros and cons](/content/blog/which-is-better-free-sftp-software-vs-enterprise-level-sftp-software "Which is Better: Free SFTP Software vs. Enterprise-Level SFTP Software?"/index.html) against the ones for an enterprise-level SFTP solution to better determine which will fit your organization’s file transfer needs.

Why Use Secure FTP Software?

Secure FTP solutions, including [GoAnywhere MFT](/content/solutions/managed-file-transfer "Managed File Transfer Solution Cornerstone"/index.html) protect sensitive file transfers with strong encryption and authentication methods. GoAnywhere's support for the three secure FTP standards (SFTP, FTPS and SCP) creates encrypted tunnels between client and server systems.

How to Connect to GoAnywhere’s SFTP Server with a File Transfer Client

Connecting to SFTP with GoAnywhere MFT involves selecting the protocol, entering the server details, setting authentication methods, and testing the connection. Once established, you can securely transfer files as needed. Of course, you can refer to the GoAnywhere MFT documentation for more details.

1. Launch the file transfer client application.
2. Create a new connection
3. Select SFTP as the protocol
4. Enter connection details (Hostname, Port 22, username, and password)
5. Set up authentication via password or public key authentication:
6. Configure any additional settings such as encryption, proxies, or timeouts.
7. Test the connection, verify settings are correct, and that you can successfully connect to the SFTP server.
8. Save the connection configuration for future use
9. Transfer, upload, manage, or download files on the SFTP server within the file transfer software interface.

Learn More About the Secure FTP Solution Components in GoAnywhere MFT

Secure FTP Server

Secure FTP Client

FTPS Server

FTPS Client

SCP Client & Server

Secure FTP Software Features At a Glance

Connectivity

Supports SFTP (SSH), FTPS (SSL/TLS) and SCP (Secure Copy) standards

Client & Server

Provides both client and server components

Flexible Deployment

Runs on multiple platforms including Windows, Linux, IBM i, AIX, UNIX and Solaris

Authentication

Authenticates connections with user IDs, passwords, keys and certificates

Large File Transfer

Supports large files with auto-resume and integrity checks to help guarantee delivery

Auditing & Reporting

Produces full audit logs of all Secure FTP activity

Try SFTP Today

Looking for the best FTPS, SCP, or SFTP server for your file transfer needs? Learn how GoAnywhere MFT can help you achieve your file transfer goals with secure, encrypted FTP clients and servers for Windows, Linux, IBM i, and other platforms.