Ensure S3 bucket policy does not allow public write access
S3 bucket policies must never allow public write access. This would allow anyone to upload, modify, or delete objects in the bucket.
Security Impact
Public write access allows attackers to upload malicious content, ransomware, modify existing data, or delete critical files.
How to Remediate
Remove any bucket policy statements that allow s3:PutObject, s3:DeleteObject, or similar write actions with Principal:* or Principal:AWS:*.
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 CIS AWS v1.5.0, CIS AWS v2.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-s3-3
- Service
- Simple Storage Service (S3)
- Category
- Public Access
- Severity
- CRITICAL
- CIS Benchmark
- 2.1.3
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 MFA Delete is enabled on S3 buckets
Ensure S3 bucket has server-side encryption enabled
Ensure S3 bucket versioning is enabled