4 ms·
> or in this case, S3 S3 is very common when it comes to leaks for some reason
by OrgNet 7y ago
> or in this case, S3
S3 is very common when it comes to leaks for some reason
- deleted 7y ago[deleted]
- zwily 7y agoI’d say one big reason would be because so many people use it.
- slenk 7y agoAnd it used to be VERY easy to make them public. Amazon has recently been showing a lot more warnings if you try it now.
- eli 7y agoDespite recent improvements, it's still pretty easy to accidentally make a bucket public that you meant to keep private.
- je42 7y agoYep. As a bigger org you want automatic compliance checks that verify that all buckets are not publically accessible.
- mwarkentin 7y agoThey have explicit public access blocks at both the bucket and account level now. These override any permissions granted via IAM or bucket policy.
- je42 7y agoThat's why you still want explicit automatic audits.
- continuational 7y agoAWS has a very complicated configuration format for permissions. In security, complicated = insecure.