The Microsoft Windows and Windows Server operating systems are some of the dominant computer platforms in the world, with around 72% share of both the desktop and server OS markets. Based on this data, it’s fair to say that Windows platforms see more file transfer activity than any other, and have the greatest number of options for file transfer solutions.
In this post, we’re going to help administrators choose a particular Windows FTP solution based on use case.
What types of Windows file transfer solutions exist?
Windows FTP tools generally fall into the four categories:
- Built-in Microsoft utilities and tools: Microsoft’s familiar file explorer allows file movement and manipulation between different connected storage volumes, which can include cloud tools like OneDrive and SharePoint. These options are more consumer-level tools, but can easily solve ad hoc file transfer needs of many users.
- Command line/PowerShell scripting: A favorite of more technical administrators and users, PowerShell commands allow direct access to a number of file transfer utility packages without having to install or maintain heavier weight applications. They can also be used for custom file transfer automation.
- Third-party client/server applications: For file transfer that relies on a UI but is a bit more powerful and secure than existing Microsoft utilities, many users turn to third party file transfer clients and servers. This software, which includes Cerberus FTP Server by Redwood and JSCAPE by Redwood, must be downloaded and installed by the user before initiating a transfer.
- Remote access tools: Depending on how you’ve set up your environment, you may have access to remote connection tools that will let you access other machines and place files on them as if they were your own local device.
Armed with an understanding of these options, now we can dig into specific use cases to determine which Windows file transfer option is best for your organization.
Breaking down Windows FTP use cases — how to choose a secure file transfer solution.
User types
We recommend beginning with your transfer users’ technical abilities and requirements. Are you trying to serve the one-off needs of a group of software engineers who are comfortable with scripts and will only be placing the occasional file? Or are you trying to serve a non-technical user who needs to batch process a high volume of data each day?
The matrix below can help you choose the right Windows FTP solution for your needs based on your users.
One-time or repeated transfers
You’ll note in our matrix above that transfer volume is a deciding factor. For single use or ad hoc file transfers, any Windows FTP tool will work in a pinch. But the more you’re handling high volume, repeated transfers, the more you’ll want to introduce automation that third-party file transfer server applications provide. While it’s certainly possible to write your own PowerShell scripts to handle these situations, in many cases you can avoid that work by using a tool with built-in automation event support.
- Recommended file transfer tool for ad hoc transfers: any on the list above
- Recommended file transfer tool for higher transfer volumes: third-party FTP server applications
Client support required
The clients your transfer use case must support are as important as the technical skill of your transfer users, and in many cases are driven by those skills. If you’re going to be serving a general consumer market or a bring-your-own-device policy within your organization, you’ll want to think about how to support criteria like transfers from mobile devices, single-sign-on, browser-based transfers and more. Alternately, if you’re supporting mostly automated systems, you can spend less time on UI-based tools and more time on protocol compatibility.
- Recommended file transfer tool for a “public user” client scenario: Third-party client/server applications, primarily due to their ability to handle HTTPS transfers. This feature allows any device with a web browser to become a client without additional software installation. Built-in Microsoft tools like SharePoint may be a solution here as well.
- Recommended file transfer tool for automated systems: Third-party FTP server applications are the ideal tool in this scenario due to their ability to create trusted trading partner connections that allow inbound transfers without spending significant time scripting in PowerShell. These tools can also handle a broader variety of protocol connection requests if configured to do so.
Speed requirements
When file transfer speed matters, you’ll want to look for a solution that gives you protocol flexibility by supporting FTPS (which is generally faster than SFTP) or UDP-based protocols like JSCAPE’s Accelerated File Transfer that were designed for higher-speed transfers.
- Recommended file transfer tool when speed is a priority: Third-party FTP server applications provide the broadest support for a range of high-speed file transfer protocols, and also allow event-driven automation that can move data faster than a human administrator.
Our assumption here is that we aren’t interested in manual transfers when we’re concerned about speed, given how much network speed can affect a single transfer.
Network and bandwidth requirements
A number of great tools exist for optimizing Windows Server’s bandwidth usage. That said, the majority of these tools are only able to look backward at current or previous usage data. If you’re concerned about a large pending data stream that may slow your network or are trying to keep an eye on costs, it’s helpful to have visibility into how much bandwidth your planned file transfers will need to complete.
- Recommended file transfer tool when bandwidth optimization is a priority: Third-party FTP server applications like JSCAPE are able to support smarter file transfer protocols that can monitor bandwidth and transmit data during lower utilization time periods.
Security requirements
Every organization has different file transfer security requirements. Potential areas to consider include:
- What file transfer encryption do you require?
- Do you allow data in the cloud?
- Do you need encryption at rest?
- What types of authentication are you performing on your clients and servers?
- What types of in- and outbound connections do your security policies allow?
- Recommended file transfer tool when security is a priority: we recommend third-party FTP server applications if you’re concerned about your security for several reasons:
- Configuring additional security settings like FIPS 140-2 file transfer is generally already built-in and easy to do.
- A third-party application can be limited to only trusted users, whereas other Windows file transfer options could be difficult to monitor for intrusion.
- Third-party applications can be configured to generate alerts and take action when unauthorized or unusual file activity occurs, even from trusted users.
- These tools can be configured to provide audit trails for all file activity that may not exist using the other options.
Compliance requirements
If your organization must comply with data handling and protection regulations, you’ll likely face requirements to limit data access, ensure data minimization and deletion, and store and transfer data at minimum levels of encryption. Doing so requires significant policy configuration, which can be burdensome to enact on some of the more ad hoc Windows FTP options.
- Recommended file transfer tool when compliance is a priority: Third-party FTP server applications provide built-in access controls, audit logs and other tools to help demonstrate and ensure regulatory compliance. While any of the other options can be configured to do so as well, the effort to do so makes the third-party tools much more efficient overall
Conclusion
We hope this review of Windows FTP options has helped you to understand how to analyze your secure file transfer needs. Please download a trial of Cerberus FTP Server today to explore just how easy Windows file transfer can be.