Search

GlobalSCAPE Knowledge Base

Should I use IIS rather than EFT Server for HTTP/S transfers?

EFT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • EFT, all versions

DISCUSSION

File transfers are heavily targeted by hackers. Using Microsoft's IIS as a solution is definitely an alternative for file transfers, but an administrator must then set up a dedicated file transfer server to mitigate the risk of security breaches that commonly occur under IIS implementations. EFT is dedicated only to file/resource retrieval and cannot be induced to run scripts or server-side applications; this is a plus point with regard to increased security.

Disadvantages of using IIS

  • Susceptibility to injury or attack.
  • Restricted NTFS permissions. You have to manage all users and groups through the computer's NT account database or provide some domain trust model that defers the management to some other computer but still require manipulation of an NT account database.
  • You have to provide custom scripting on the IIS server side to handle file uploads. Hence, you should know how to write and maintain scripts.

IIS is a good option if you want to create and maintain scripts or third-party applications. To acquire a more advanced user-friendly interface with drag and drop, multiple concurrent transfers, and so on, opt for EFT with the Web Transfer Client. IIS does not provide any of these features.

Advantages of using EFT 

  • EFT offers all-inclusive security for managed file transfer. EFT supports a wide variety of protocols to accommodate the diverse clients that trading partners, external vendors, and others use to connect.
  • You can access the server through ports that are already open on the firewall.
  • Cost-effective in terms of server overhead, configuration and administration, custom work, and maintenance.
Details
Last Modified: Last Year
Last Modified By: kmarsh
Type: FAQ
Rated 2 stars based on 6 votes.
Article has been viewed 47K times.
Options
Also In This Category