Overview

A couple of weeks ago, we compared the advantages and disadvantages of using Amazon S3 and local storage as file storage system for JSCAPE MFT Server. For those who want to try storing their file transfer server end user files on Amazon S3, this post is for you.

When you first launch your web file transfer service on JSCAPE MFT Server, you'll notice that the web user interface has the JSCAPE branding starting from the login screen and continuing inside. You can actually customize that and make it your own.

When I first read about HSTS, my first reaction was, "What's this? A replacement for HTTPS? Considering the ubiquity of HTTPS, shouldn't we be working to improve it first instead of replacing it?" Turned out, my initial understanding of HTTP Strict Transport Security was off the mark.

A Hypertext Transfer Protocol (HTTP) file transfer, which is also known as a web file transfer, is one of the most user-friendly methods of transferring files. For users to upload files or download files with an HTTP server, all they need is a web browser. Users can employ any web browser, such as Chrome, Firefox, Microsoft Edge or Safari for that purpose. 

As you scout for the most cost-effective way of transmitting files with your business units and trading partners, among the many file sharing solutions that will likely stand out are free FTP servers. Most of these software applications are already bundled (or readily available through repositories) in operating systems like Linux, Mac OS X and Microsoft Windows, so they likely don't require additional costs ... or so it seems.

Not everyone using your web file transfer server needs to have a user account. There can be instances when it's perfectly fine for a user to just carry out an anonymous file upload. Meaning, that user doesn't have to login. This set up can be useful in cases where an outsider just needs to do a one-off upload. We'll show you how to enable that functionality on JSCAPE MFT Server.

Overview

PGP encryption can add another layer of protection to a trading partner file transfer already secured by FTPS. It can also provide data-at-rest encryption as soon as the file arrives at the other end. In this post, we'll show you how to set up a fully automated file transfer secured by OpenPGP and FTPS using JSCAPE MFT Server triggers.

Overview

People who use SSL/TLS to secure their online transactions/file transfers are mostly only familiar with two of its security functions: 1. That it can encrypt data in transit and 2. That it can enable clients to authenticate the server. They're likely not making use of another feature that can greatly enhance SSL security even more - client certificate authentication.

If you've been following our posts, you know that client certificate authentication has been the subject of our discussion lately. However, we've never been able to talk about how to enable it on the server side. This quick post will be all about that.

Because Microsoft Windows doesn't have a secure file transfer protocol server built in, we've put together a simple and easy-to-follow tutorial on how to install an SFTP server on Windows. 

The SFTP server we'll be using for this tutorial is JSCAPE MFT Server, a managed file transfer server that supports SFTP connections and several other file transfer protocols like FTP, FTPS, HTTP/S, WebDAV, AS2 and OFTP, as well as SSL and TLS. JSCAPE also offers a cloud solution called MFTaaS.

Overview

[Last updated: December 2020] Malicious insiders and careless insiders are increasingly posing serious risks to file transfer systems. If nothing is done to mitigate them, these internal threats can cause data loss or, worse, massive penalty-inducing data breaches. In this post, we take a closer look at internal threats, how they put file transfer systems at risk, and what you can do to mitigate them.