News for hackers. Stuff that matters.
Re:Capital One Says Breach Hit 100M Individuals in U.S by joncrane on Monday July 29, 2019 @09:31PM (#20561268)
Is there enough space in an S3 bucket access policy to include DENY rules for every known Tor IP address?
Re:Capital One Says Breach Hit 100M Individuals in U.S by Scoundreller on Monday July 29, 2019 @09:54PM (#20561403)
By the sounds of it, the s3 bucket was internally accessible only. But attacker connected through the corp's Web Application Firewall after grabbing the credentials to login to the S3 bucket.
Re:Capital One Says Breach Hit 100M Individuals in U.S by joncrane on Tuesday July 30, 2019 @11:05AM (#20565457)
"Internally accessible only" just means you have to have credentials to access it.

You can also add IP address restrictions to a bucket access policy; this was obviously not done here because once she had the credentials, it didn't matter where she was accessing from.

Re:Capital One Says Breach Hit 100M Individuals in U.S by cm2187 on Tuesday July 30, 2019 @05:16AM (#20563241)
Looks to me that it should rather be using an IP white list. It's not like their systems would need access to these documents from an dynamic IP dial up connection.