Any time files leave a company without going through proper “file transfer” policy checks puts businesses at risk. IT managers must be concerned with who is authorizing and initiating file transfers as well as controlling what gets shared. In order for enterprises to move beyond FTP to ensure sensitive files are transferred securely, they must implement protection policies that include adherence to security compliance mandates and do so with the same ease-of-use that exists with simple email. Move beyond FTP to ensure sensitive files are transferred securely. Furthermore, over 56% of those responding stated that they use a mailbox or other email applications to transfer files. According to a recent file transfer survey conducted in March 2011, over 70% of respondents currently utilize FTP as their primary transport protocol. While FTP protocol is a bit dated, the majority of companies still use it. Many companies still utilize legacy file transfer protocols that don’t encrypt traffic, exposing the payload to anyone that can access the network. Having a secure connection is not as easy as it should be. However, along with the quick on-boarding of companies and individuals comes the challenge of ensuring secure connectivity, managed access, reporting, adaptability, and compliance. In fact, we’ve seen that the ability to quickly deploy and provision file transfer activities actually drives more people to the cloud. Performing file transfer over the internet, via the “cloud”, has provided major benefits over the traditional methods. IT managers were ultimately concerned that anyone within a company could log on via the web and access a self-service, cloud based, File Transfer application without IT’s knowledge, adding to the increased security risk for file transfer. Centralized control and access was the way of the world back in these “good ole days.”įast forward to the proliferation of the internet and the World Wide Web, the concern of securing files while in transit to its location then became top of mind. Securing the file in this scenario had more to do with making sure that no one could access the data as oppose to worrying about protecting the transport itself. If you think about it, these were pretty confined environments with the client and server having a true relationship. Despite File Transfer Protocol (FTP) being published in 1971, it took until the mid-80s for systems to catch up to the original vision of FTP, as LANs were beginning to find their way into the business environment.ĭuring this time period, transferring files internally became easier and the ability to move files externally by leveraging the client server typology eliminated the “here’s the disk” approach. While we have been sharing files with each other for ages, the security of the data shared is often questionable. Ok, well maybe that is an exaggeration, but the point is, file transfer was one of the earliest uses of “network” computing dating back to the early 1970’s when IBM introduced the floppy disk. Product Manager, Hubspan Inc.įile transfer has been around since the beginning of time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |