One of the key features of JSCAPE MFT Server 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.

When you're an oil drilling company with a fleet of oil rigs, one of your routinary tasks is to collect data from those rigs on a daily basis. If you've already been doing this for some time now, you probably don't know that there are unnecessary development, maintenance, and administrative costs associated with data collection that you can now discard.

JSCAPE, the leader in platform and protocol independent managed file transfer solutions, is pleased to announce MFT Synchronizer, a new complementary product to our flagship product, MFT Server.

Overview

In this tutorial, we demonstrate how to set up JSCAPE MFT Server to copy each file downloaded from a remote server. If you want to follow these steps locally, we suggest you follow the instructions in the article "Downloading Files Periodically From A Trading Partner" first. This tutorial will only work if you have a separate trigger that performs the download process and that article will help you in that regard.

Overview

Some modern file transfer servers have the built-in capability to store uploaded files in different places. For instance, in JSCAPE MFT Server, you can store uploaded files locally (i.e., on the same machine as the system running the file transfer service itself) or to a remote server or storage service. One of these storage services is Amazon S3. But why would you want to store uploaded files there?

In this post, we explore some pros and cons of using Amazon S3 as your MFT Server's file storage system compared to the default option, i.e., local storage.

Overview

In this tutorial, we'll show you how to connect JSCAPE MFT Server to an Amazon S3 Trading Partner and then upload files to an S3 bucket.

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.

This video tutorial shows you how to configure JSCAPE MFT Server AS2 servers so that you and your trading partners can digitally sign your AS2 messages.