Guide to HIPAA Compliant File Transfers - Part 2

TOTP or Time-based One Time Password is an algorithm that factors in the current time to generate a unique one-time password. It is increasingly becoming an option for 2-factor authentication (where it is typically used alongside username/password authentication) in secure cloud / web-based applications.

Overview

In this post, you'll learn how to set up a web-based file transfer service using JSCAPE MFT Server. A web file transfer will allow your users to perform file transfers without having to install a file transfer client. To upload or download files, they'll just need to fire up their favorite Web browser like Firefox, Chrome, Safari, Internet Explorer, or Edge, enter the web server's URL, and login to the interface.

This article was updated on June 11, 2018

Overview

In one of my previous posts, I defined what an SSL file transfer is. Today, I'm going to show you how to actually set up an SSL file transfer service on JSCAPE MFT Server. After that, I'll demonstrate how an AnyClient user would connect to your server and perform a secure file transfer using that particular service.

The security of any SSL/TLS-protected connection largely depends on the client and server's choice of cipher suites. But what are cipher suites? If you use file transfer protocols like HTTPS, FTPS, and AS2 but don't know what cipher suites are, you will want to read this post and learn how to use a cipher.

Overview

Here's something that's particularly useful if you want to provide access control to JSCAPE MFT Server directories based on need to know and according to job responsibilities. It's called Groups. JSCAPE managed file transfer server Groups are named sets of virtual directories and file system permissions that may be assigned to multiple user accounts. You can use them to comply with certain laws and regulations like PCI-DSS, HIPAA, and SOX.

One of the key features of JSCAPE MFT Server 10.2 is the ability to support ICAP antivirus scanning. But what is it? How can it benefit your end users, trading partners, and system administrators? How does it compare to traditional file transfer virus scanning solutions? In this blog post, we answer these questions and more.

ICAP (Internet Content Adaptation Protocol), as defined in RFC 3507, allows JSCAPE MFT Server to offload virus scanning tasks to a dedicated ICAP server, enhancing security policies without burdening the local server with the heavy lifting. This advanced scanning method enables real-time antivirus checks by forwarding HTTP messages to an ICAP service for evaluation.

End users benefit from ICAP client technology by receiving and sending malware-free files without local antivirus software, relying instead on ICAP server-side scanning. Trading partners enjoy a similar peace of mind, knowing that all files transferred via FTP, HTTP, or any file transfer protocol through JSCAPE MFT Server are pre-scanned for threats.

For system administrators, ICAP virus scanning simplifies security management. By configuring the MFT server to connect with an ICAP service, they delegate the resource-intensive process of virus scanning to external specialists. This setup reduces the proxy server's overhead and ensures that virus signatures are always up-to-date without additional intervention.

This shift towards a more centralized and advanced antivirus approach underscores a commitment to security and compliance, which is critical for adhering to regulations like HIPAA and PCI DSS. It represents a significant leap forward in managed file transfer technology, offering value-added services like content filtering and malware protection with minimal impact on bandwidth and server performance.

Ready to see how ICAP antivirus scanning can transform your file transfer security? Schedule a free demo with us today and witness the power of JSCAPE MFT Server 10.2 in action.

Lately, we've been receiving an increasing number of inquiries from customers as to how JSCAPE MFT Server can ensure GDPR readiness. Because MFT Server is equipped with several features for securing data, it readily meets a number of GDPR provisions for the protection of EU residents' personal data. In this post, we'll tackle the most relevant provisions and explain how you can leverage MFT Server to achieve compliance.

Theoretically, RSA keys that are 2048 bits long should be good until 2030. If so, isn't it a bit early to start using the 4096-bit keys that have become increasingly available in encryption-enabled applications? It depends.

If your AS2 connection already runs over HTTPS, your EDI messages should already be protected by the data-in-motion encryption that comes with SSL/TLS. But what if you want an added layer of security or if you're somehow only using HTTP and want to encrypt your transmission? You'll need something like this.