Ensure EBS snapshots are encrypted

Security & Compliance

Ensuring that EBS snapshots are encrypted means that the data stored in the snapshots is protected from unauthorized access. This can help to prevent sensitive data from being compromised in the event of a security breach. The encryption of EBS snapshots can be enforced through various mechanisms, such as using AWS Key Management Service (KMS) or specifying an encryption algorithm when creating the snapshot.


To ensure EBS snapshots are encrypted, you can follow these remediation steps:

  1. Identify unencrypted EBS snapshots - You can use the AWS Management Console, AWS CLI, or an API to identify EBS snapshots that are not encrypted.
  2. Create a new encrypted snapshot - Create a new encrypted snapshot of the unencrypted EBS volume using the "CreateSnapshot" command. You can choose to create the snapshot either through the AWS Management Console or the AWS CLI.
  3. Copy the data to the new encrypted snapshot - Copy the data from the unencrypted snapshot to the new encrypted snapshot using the "CopySnapshot" command. Make sure to specify the "Encrypted" parameter as "true" while copying the data.
  4. Delete the unencrypted EBS snapshot - Once the data has been copied to the new encrypted snapshot, delete the unencrypted EBS snapshot to ensure that the data is no longer accessible in an unencrypted format.
  5. Repeat the process for all unencrypted EBS snapshots - Repeat the above process for all unencrypted EBS snapshots to ensure that all EBS snapshots in the AWS account are encrypted.
  6. Enable default encryption - Finally, you can also enable default encryption for all new EBS snapshots created in the future by using the "EnableDefaultEncryption" command. This will ensure that any new EBS snapshots created in the AWS account are automatically encrypted.
Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.