S3 bucket without default encryption
S3 can encrypt every object at rest automatically. Without default encryption set, objects may be stored in the clear, so a leaked copy or disk is readable.
Why it matters
Encryption at rest is a baseline control for most compliance regimes (SOC 2, ISO 27001, PCI). An unencrypted bucket is a finding in any audit.
If a backup, snapshot or copy of the data ends up somewhere it shouldn't, encryption is what keeps it from being readable.
How to check for it
- S3 → the bucket → Properties → Default encryption shows whether SSE-S3 or SSE-KMS is on.
- aws s3api get-bucket-encryption --bucket <name> — a 'not found' error means no default encryption.
How to fix it
- Turn on default encryption (S3 → the bucket → Properties → Default encryption → SSE-S3, or SSE-KMS for key control).
- For regulated data, use SSE-KMS with a customer-managed key and turn on key rotation.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Isn't S3 encrypted by default now?
- New buckets get SSE-S3 by default, but older buckets and some configurations may not — and for regulated data you often need SSE-KMS with a managed key, which isn't the default.