Ensure S3 bucket replication uses encryption
Cross-region and same-region replication should encrypt objects at the destination. If source uses SSE-KMS, configure replica key for the destination region.
Security Impact
Replicated data may be less protected than source data if encryption is not properly configured for replication.
How to Remediate
Configure replication rules to use SSE-KMS for destination bucket encryption. Ensure replica key is available in the destination region.
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, HIPAA, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-s3-18
- Service
- Simple Storage Service (S3)
- Category
- Encryption
- Severity
- MEDIUM
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