Ensure S3 bucket does not have overly permissive bucket policy
Bucket policies should follow least privilege. Policies with Principal:* or Principal:AWS:* without proper conditions grant access to any AWS account or user.
Security Impact
Overly permissive policies can lead to unauthorized data access, especially if combined with predictable bucket names.
How to Remediate
Review bucket policies and specify exact principals (AWS account IDs, IAM roles, or IAM users). Add conditions to restrict access further.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Simple Storage Service (S3) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-s3-20
- Service
- Simple Storage Service (S3)
- Category
- Access Control
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Simple Storage Service (S3) Checks
View all checksEnsure S3 bucket has block public access enabled
Ensure S3 bucket policy does not allow public read access
Ensure S3 bucket policy does not allow public write access
Ensure MFA Delete is enabled on S3 buckets
Ensure S3 bucket has server-side encryption enabled