Unencrypted EBS Volumes or Snapshots

EBS volumes or snapshots are stored unencrypted, so their contents are not protected by KMS key permissions and unencrypted snapshots can be shared or made public.

SeverityMedium
CVSS 3.14.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N Open in the calculator
CVSS 4.05.9 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-312: Cleartext Storage of Sensitive Information
OWASP Top 10A06:2025 Insecure Design
MITRE ATT&CKT1537 Transfer Data to Cloud Account
CategoryCryptographic Failures

Description

Amazon EBS encryption protects a volume's data at rest, its snapshots, and data moving between the volume and its instance, using a KMS key: either the AWS managed key aws/ebs or a customer managed key. One or more volumes or snapshots are unencrypted. AWS protects the physical storage media whether or not a volume is encrypted, so the practical value of encryption here is as an additional access control, and unencrypted storage may also breach regulatory or contractual requirements for encryption at rest.

An unencrypted snapshot can be copied, shared with another AWS account or made public by anyone with the relevant EC2 permissions, and the whole disk, including files, databases and any credentials stored on it, can then be read by mounting it. A snapshot encrypted with a customer managed key, by contrast, can be used only by principals that the key policy allows, cannot be made public, and cannot be used by another account until the key is shared with it.

A volume's encryption is fixed when it is created, and snapshots of an unencrypted volume, and volumes restored from those snapshots, are also unencrypted unless encryption is requested when they are copied or restored. EBS encryption by default is an account setting that applies to each Region separately. When it is off, volumes are created unencrypted unless encryption is requested at launch, which is how unencrypted volumes usually arise. Turning it on has no effect on existing volumes.

The issue is identified with aws ec2 describe-volumes and aws ec2 describe-snapshots --owner-ids self (the Encrypted attribute) and aws ec2 get-ebs-encryption-by-default in each Region, and is reported by Prowler, ScoutSuite, Security Hub and AWS Config rules such as encrypted-volumes.

Remediation

Turn on encryption by default and replace unencrypted volumes and snapshots:

  • Enable EBS encryption by default in every Region in use (aws ec2 enable-ebs-encryption-by-default), preferably with a customer managed KMS key set as the default (aws ec2 modify-ebs-default-kms-key-id), so that all new volumes are encrypted.
  • Encrypt existing volumes by taking a snapshot, copying it with encryption enabled (aws ec2 copy-snapshot --encrypted --kms-key-id), creating a new volume from the encrypted copy and swapping it in during a maintenance window, or by rebuilding instances from encrypted AMIs.
  • Replace unencrypted snapshots that must be kept with encrypted copies, then delete the unencrypted originals.
  • Restrict customer managed key policies so that only the roles that use the volumes can decrypt them, and limit who can change snapshot sharing (ec2:ModifySnapshotAttribute).
  • Enable block public access for EBS snapshots in each Region as an additional guard.

Confirm the fix with aws ec2 get-ebs-encryption-by-default returning true in each Region, and with describe-volumes and describe-snapshots showing no unencrypted resources remaining in use.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More AWS Findings

Every AWS finding