In Part 1 of this article, you learned how to perform a basic automatic Kaspersky scan on a newly uploaded file. In that post, we only specified one argument for the kav4fs-control command, and that was the path of the file to scan.
Managed File Transfer and Network Solutions
Configuring JSCAPE MFT Server to auto-update Kaspersky database
In Part 1 of this article, you learned how to automate virus scanning on files uploaded with JSCAPE MFT Server using the Kaspersky Antivirus 8 for Linux File Server. But of course, we know very well that new viruses are created every hour. So, your Kaspersky antivirus database has to be updated if you want it to scan effectively.
Here in Part 2, we’ll teach you how to setup your JSCAPE MFT Server for automated updates. Basically, you’ll be setting up a regular schedule for those virus database updates.
Actually, Kaspersky Antivirus 8 for Linux File Server already comes with its own scheduling feature, which also allows a user to setup a scheduled update. It’s even possible to configure Kaspersky for automatic updates during the Initial Configuration process, which follows right after installation. If you enable automatic updates that way, Kaspersky will run automatic antivirus database updates every 30 minutes.
You can use those methods if you want. We’re just providing you with another option that can be carried out on your JSCAPE MFT Server Manager.
Last time, I introduced you to one method for securing data at rest and that was by deploying encrypted file systems. As promised, this post will focus on another method, known as PGP encryption. Although encrypted file systems provide a decent level of protection for your data, they have certain limitations.
While encryption keeps your file server data safe from prying eyes, it doesn’t provide any protection against viruses or trojans. To prevent existing files in your server from getting infected by malware that may be accompanying a newly uploaded file, you can configure JSCAPE MFT Server to work with antivirus software.
JSCAPE, a leading supplier of managed file transfer software and networking solutions, recently released version 4.0 of AnyClient, the company’s free file transfer client.
One feature that stands out in AnyClient 4.0 is its new support for the Amazon S3 protocol. This allows users who have Amazon Web Services accounts to connect to AWS, navigate through buckets, folders, and objects, and upload or download files.
Last October 4, Amazon Web Services (AWS) announced that there were already 566 billion objects in S3. That’s double the number they had 9 months earlier.
"There’s obviously a rapidly growing demand for cloud storage and computing, and more people will be looking for the most versatile file transfer tool to bring their files up to the cloud or down from it," said Van Glass JSCAPE CEO. "AnyClient 4.0 is just in time to meet that demand."
Also accompanying this latest version is an online documentation, support for automatic updates, and improved performance and usability in the AnyClient GUI.
AnyClient is a platform-independent client that allows users to transfer files using a wide selection of protocols. Prior to version 4.0, AnyClient already supported FTP, SFTP/SSH, FTP/Implicit SSL, FTP/SSL (AUTH TLS), WebDAV, and AFTP (TCP and UDP).
Van added, "Many people no longer just store files in their laptops or desktops. In this highly networked society, you normally have files on different servers and service providers, each using different protocols. We want people to connect to all of them from practically any operating system using just one client. Each version of AnyClient brings us a step closer to that objective."
JSCAPE is pleased to announce the release of AnyClient 4.0. This release includes several performance enhancements the most important being the ability to transfer multiple files concurrently.
JSCAPE is pleased to announce the release of Secure FTP Applet 7.0
JSCAPE is pleased to announce the release of JSCAPE Load Tester 1.2. This release includes the following updates.
To prevent confidential data from leaking out of your organization, your DLP efforts may have to be aimed at two areas: data-at-rest and data-in-motion. In this post, we’ll talk about the former.