You can go back to sending letters with your SSN for employment, taxes, etc and ideally that should mean that your information doesn’t go on the internet.
But you’re in the minority in wanting that hassle.
You can go back to sending letters with your SSN for employment, taxes, etc and ideally that should mean that your information doesn’t go on the internet.
But you’re in the minority in wanting that hassle.
1. Email / web-submit forms
2. Someone saves requests onto a disc and swivel chairs to load them into the offline system for processing
3. Results are written back to disc, which is swivel chaired back to net-connected systems
Congratulations. You've just made physical access (or a much more difficult poisoned data bug) a requirement for data leaks.If you insist on keeping all of this data online, how do you propose preventing what happened with Maine from happening again? Surely you must be willing to acquiesce that there is an increased level of security with OP's proposal in this regard, in spite of a lack of convenience?
Tactically, what could have been done to minimize or prevent this particular incident, while continuing to use MoveIT software:
- Encrypt the files before dropping them onto the file transfer site. Communicate the key out-of-band. This one simple step would have avoided catastrophe. Unfortunately, many MoveIT site operators would not allow their customers to encrypt files sent to them.
- Limit MoveIT site access, by IP address. This is a fairly common practice for file transfer sites.
- Use a frontend, such as a load balancer or reverse proxy, that enforces authentication in front of MoveIT.
- Disable the web site and only allow use of the SFTP (SSH) site.