How Misconfigured S3 Bucket Policies Can Publicly Expose Your Data
The article discusses how a misconfigured Amazon S3 bucket policy can unintentionally expose data to the public. It explains that AWS evaluates access permissions by first applying any explicit deny, then checking resource-based policies, and finally evaluating identity-based policies. This order means that if a resource-based policy allows access and there is no explicit deny, access is granted even if the identity-based policy does not explicitly allow it. A common mistake involves setting a bucket policy with a wildcard principal and permissive actions, which can expose all data in the bucket. The article emphasizes the importance of using AWS’s Block Public Access settings, auditing policies carefully, and applying explicit denies to avoid accidental data exposure.
https://slaw.securosis.com/p/accidentally-expose-all-your-stuff-on-s3-with-a-bucket-policy
Comments
Post a Comment