A security team discovers that an S3 bucket configured for static website hosting is exposing sensitive documents. The bucket policy allows public read access. Which AWS misconfiguration is MOST likely present?
A bucket policy explicitly allowing the "s3:GetObject" action for "Principal": "*" (all principals) directly grants public read access to all objects within that S3 bucket. This configuration overrides default private settings, making the bucket's contents accessible to anyone on the internet without authentication. Such a policy is the primary mechanism for intentionally exposing S3 objects publicly for read operations.
Why this answer
Public read access to the bucket and objects is the direct cause. Blocking public access would prevent this.