> were posted in the clear to Amazon servers by insurers using Systema Software. Posted in the clear? As in, transmitted over unencrypted channels, dumped on p

> were posted in the clear to Amazon servers by insurers using Systema Software. Posted in the clear? As in, transmitted over unencrypted channels, dumped on public-facing FTP server, or what? > Texan techie Chris Vickery spotted the files Spotted the files? What does this even mean? Did he run some kind of crawler? That can land you in quite a lot of hot water, actively searching for these kinds of files. > on Amazon web servers Public-facing EC2 instances with no authentication? Public-facing S3 files? ???? This article is so scarce on details it's impossible to determine whether AWS, Systema Software, or users of the software are at fault. I'm inclined to point to Systema Software for not knowing how to properly secure their AWS assets. EDIT: as mentioned elsewhere and in the article, the original source for this article is here: http://www.databreaches.net/oops-error-by-systema-software-exposes-millions-of-records-with-insurance-claims-data-and-internal-notes/ http://www.databreaches.net/oops-error-by-systema-software-e... HN mods might want to change the submitted URL to that. After reading the article, a production S3 bucket was set to be open to the world. Pretty frightening that Systema would let that happen. Perhaps AWS' Trusted Advisor service should check for that? Tbh I find the article title inflammatory as it implies AWS is at fault or that AWS is in any position to mitigate the problem to begin with. Do we blame car manufacturers when motorists drive drunk?