A new day, a new wave of S3 leaks…
Cloud misconfigurations continue to be a major concern for organizations and a constant source of data leaks. A recent report by IBM has revealed that misconfigurations are behind two-thirds of cloud security incidents. In the latest example Thingiverse, a website dedicated to sharing user-created digital design files, has allegedly suffered a leak on a popular hacking forum of a 36GB backup file with 228,000 unique email addresses and other personally identifiable information such as IP addresses, usernames, physical addresses, and full names. And guess what? Unsurprisingly the data comes from an SQL backup stored on a misconfigured AWS S3 bucket and, even worse, it was apparently dumped for the first time on October 13, 2020. Despite sharing an update, Makerbot, Thingiverse’s parent company, has somehow downplayed the impact of the breach claiming that less than 500 real users have really been affected, this is yet another example of the consequences of cloud misconfigurations, and how quickly bad actors can exploit them.
And it’s not the only one… In a separate incident, a few days earlier, the same fate befell Plug and Play Ventures, a venture capital firm that runs a matchmaking service linking investors with startups. With a scary coincidence, the company exposed a 6GB PostgreSQL database (containing the personal information of the investors and the startup CEOs and more than 50,000 unique email addresses) from a misconfigured AWS S3 bucket, and even in this case, the data had been left unsecured for almost a year (October 20, 2020).
These two examples show not only how common these misconfigurations might be (and how bad the consequences might be), but also how easily these security holes can go undetected for months (or years).
How Netskope mitigates the risk of misconfigurations in public cloud
Netskope Public Cloud Security detects misconfigurations on IaaS environments such as AWS, Azure, and Google Cloud Platform, preventing organizations from leaking data