For several decades, SFTP, which stands for Secure File Transfer Protocol or SSH File Transfer Protocol, has been arguably the most widely used solution for transferring sensitive data across the internet. In the past few years, however, we’ve seen increased adoption of what’s known as SFTP cloud. 

Many of our customers use Secure File Transfer Protocol (SFTP) for their business file transfers. While SFTP is certainly a good choice for organizations looking to securely transfer multiple files or large files directly to their intended recipient, it’s not the only solution suited for that purpose. In this post, we’ll review seven secure FTP alternatives and discuss their advantages and disadvantages compared to what many consider the de-facto standard for secure, multi-file and large file transfers. 

When you’re troubleshooting connectivity issues between Secure Shell (SSH)/Secure File Transfer Protocol (SFTP) clients and servers, it pays to inspect the error messages generated on both sides of a connection. Those messages often provide vital clues about the problem. If your error messages involve the Diffie-Hellman-Group1-SHA1 key exchange algorithm, you’ll want to stick around. In the succeeding sections, we’ll be discussing the underlying cause of this particular issue and how to fix it.  

For the past few decades, many organizations have used the SSH File Transfer Protocol (SFTP) as their main file transfer solution. It’s more secure and less prone to connectivity issues than the archaic File Transfer Protocol (FTP). However, it’s becoming increasingly clear that SFTP is also starting to age. Companies struggle to meet today’s business needs and use cases with purely SFTP-based solutions.

What is AS2 protocol?

AS2 or Applicability Statement 2 is a file transfer protocol that’s commonly used in business-to-business (B2B) data transfers. It’s based on the S/MIME and HTTP/S protocols. While you can theoretically use AS2 to transfer almost any type of file, it’s normally associated with electronic data interchange (EDI).

When you first start scouting for the right file transfer protocol for your organization, you’re bound to encounter these two acronyms: SFTP and MFT. SFTP stands for SSH File Transfer Protocol, whereas MFT stands for Managed File Transfer. While SFTP is indeed a protocol, MFT isn’t. Nevertheless, these two acronyms become increasingly intertwined once you explore advanced, secure, automated file transfer solutions.

Automated SFTP file transfers are traditionally done through scripts, but there's a much easier way. In this tutorial, we'll show you how to automate SFTP file transfers without scripting a single line of code.

Overview: What Is AES?

First adopted by the U.S. government to protect classified information, Advanced Encryption Standard (AES) has long gained global acceptance and is used for securing sensitive data in various industries. In this post, we'll discuss AES encryption and explain its vital role in securing sensitive files sent over the Internet.

Most customers who use SSH File Transfer Protocol (SFTP) for file transfer automation prefer to authenticate SFTP clients through SFTP keys instead of passwords. Given the numerous inquiries on how to set up and use SFTP public key authentication, we decided to publish how-to articles to help organizations that wish to implement this authentication method in their SFTP environment. This article will focus on setting up instructions for the command line.

One of the major security features of SSH FTP is public key authentication. This authentication method allows JSCAPE MFT Server to verify a user's identity during login by asking for only the user's secret item — an SFTP private key file (SSH key). Using keys to authenticate users while requiring a username and passphrase gives us two-factor authentication.