Ensure MFA Delete is enabled on S3 buckets
MFA Delete requires multi-factor authentication to delete object versions or change versioning state. This protects against accidental and malicious deletion.
Security Impact
Without MFA Delete, attackers with credentials can permanently delete versioned objects and disable versioning.
How to Remediate
Enable MFA Delete using the AWS CLI with root account credentials: aws s3api put-bucket-versioning --bucket BUCKET --versioning-configuration Status=Enabled,MFADelete=Enabled --mfa 'SERIAL TOKEN'
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, SOC 2, SEC 17a-4 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-s3-4
- Service
- Simple Storage Service (S3)
- Category
- Data Protection
- Severity
- MEDIUM
- CIS Benchmark
- 2.1.4
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 S3 bucket has server-side encryption enabled
Ensure S3 bucket versioning is enabled