Today many organizations still rely on traditional File Transfer Protocol (FTP) servers to circumvent email size limitations. These legacy systems do not offer any central visibility or provide a unified, integrated solution for all internal and external file transfers, placing a continuous burden on IT personnel. Additionally, business users do not have visibility into the file sharing process such as attempts to add external recipient(s) and tracking of non-repudiation.
Typically multiple FTP servers are utilized for dedicated internal and external communication due to security concerns or firewall limitations. In these cases business users need IT assistance to facilitate transfers from internal FTP servers to external users. Due to these additional implementations, IT organizations also have to spend more time on troubleshooting and testing systems, often investigating multiple FTP and scripts. The burden on IT is particularly heavy when file transfers are part of workflows which traverse multiple operating environments, transfer partners, or are embedded in the implementation of a Service Oriented Architecture (SOA) service. This overhead in combination with an increased focus on compliance and regulations prompts organizations to look at new ways and technologies to govern file transfers, often due to a combination of the above use cases.
For more on this topic and the limitations of other methods currently used to transfer files, read our white paper FTP Replacement White Paper.