Re:540M Facebook Records Exposed
by badwolf on Wednesday April 03, 2019 @09:21PM
(#19568588)
Seems it was 3rd party apps data stored in ... openly accessible S3 buckets. -_-
[ Parent
| on HN ]
Isn't this the most common reason for these leaks?
Does Amazon not have screaming red banners saying "this is gonna be openly accessible?"
Re:540M Facebook Records Exposed
by themattress on Wednesday April 03, 2019 @10:30PM
(#19568885)
No screaming red banner, but each bucket does indeed get marked with large orange rectangle that reads “Public”. It’s easily noticeable.
In my limited experience, a lot of the open buckets problem comes from the fact that access to * is the path of least resistance vs a proper IAM and bucket config.
When feature work is on the line ain’t nobody got time for that :/
Re:540M Facebook Records Exposed
by wangchungtonite on Wednesday April 03, 2019 @10:59PM
(#19568977)
A lot of devs likely using aws in this manner are also not likely using the web interface an instead operating from cli pipelines where it’s easy to miss
Recently (past couple of years) I’ve noticed you’ll also get emails notifying of any publicly accessible buckets.
It seems just about every "data breach" like this turns out to be an S3 bucket left open to anyone, or a MongoDB instance left with default settings/etc... With how easy it has become to vacuum up such huge amounts of data, this type of "breach" really needs to stop :(
Re:540M Facebook Records Exposed
by jasonlotito on Wednesday April 03, 2019 @10:52PM
(#19568948)
Not red, but yes, they make it clear and obvious what this means. People don't do this by accident. It's 100% willful.
Who stands to gain for freely releasing this data?