3 ms·
I'm aware of several leaks that were basically "account holder left bucket wide open" Some of that is on AWS for initially making the defaults too open, but at
by banana_giraffe 6y ago
I'm aware of several leaks that were basically "account holder left bucket wide open"
Some of that is on AWS for initially making the defaults too open, but at the end of the day, S3 was doing what it was told.
Is there some case where S3 was locked down, and the data still leaked?
- tmotwu 6y agoYes, that is what leakage is. Even the SolarWinds breach was likely made possible due to a cloud leak. Not a strong argument for cloud setups.
- unclekev 6y ago> Even the SolarWinds breach was likely made possible due to a cloud leak What? Their internal build system was comprised and the password for the FTP that hosted their software updates was "solarwinds123" This had nothing to do with the cloud/a issue with a cloud provider.
- tmotwu 6y ago> password for the FTP that hosted their software updates was "solarwinds123" Secrets in a public github repository is a leak, in the cloud.
- unclekev 6y ago> Secrets in a public github repository is a leak, in the cloud. Someone uploading their secrets to GitHub has nothing to do with the cloud and everything to do with the incompetence of the people using it. "This is the clouds fault because one of our engineers made a mistake and 'the cloud' didn't stop them!" does not really hold up.