If you are keen follower of our blog, you will have noted that in May 2020, we saw the release of the first MOVEit edition under the Progress banner. If you are not a keen follower...why on earth not?!
It has been quite a long wait since the last release of MOVEit in 2019 - six months to be exact. We can only speculate that there has been some integration to do between Progress and Ipswitch, since the acquisition last year which may have delayed things.
If you are reading this blog, chances are you are familiar with IBM's MFT (Managed File Transfer) solution Sterling. If you are not, Sterling is an acquisition which IBM made a number of years ago, taking with it a large swathe of international customers who use the Sterling product line to move files between external and internal (and vice versa).
It wasn't to long ago that we were excited to see the release of MOVEit's first REST API methods, opening up the possibilities for ever more integration and automated workflows. Many of which our customers have since explored.
After eight years of working with managed file transfer solutions (MFT), there is one use case which pops up time and time again.
Storing sensitive files and personal data in the cloud can be a touchy topic for some, keeping even the most seasoned information security leader or data protection officer awake at night. Although, despite what the humble salmon teaches us about swimming against the tide, it is hard to fight against the unstoppable trend towards cloud adoption.
It may be obvious to some that FTP (File Transfer Protocol) is an insecure protocol; and that its continued use for transferring sensitive or personal is inappropriate. Yet, its use for that very purpose still continues according to Rapid7, creating an unnecessary risk.
Do you send sensitive documents and files using regular email? Could you do more to protect those documents and files to ensure their confidentiality? These are just two of the more obvious questions which many an IT administrator and security officer are now asking their organisations, as the world and it's regulators become more focussed and stringent on data protection.
As of May 2018, payment merchants and other credit card handling organisations will need to have familiarised themselves and have implemented the latest iteration of the PCI-DSS (Payment Card Industry - Data Security Standard). Version 3.2.1 expands on what is already a comprehensive and well-known standard by adapting to the rapidly changing climate of data protection, privacy and vulnerability management.
As of the 30th of June 2018, the use of SSL/early TLS in PCI-DSS (Payment Card Industry Data Security Standard) card environments will no longer be accepted as a compliant protocols by the PCI security standards council and thus could render your accreditation as invalid. What does this mean for you and your managed file transfer solution?