Overview
Overview
Encrypt Amazon RDS instances and snapshots at rest, by enabling the encryption option for your Amazon RDS DB instance.
Remediation guidance
In AWS, you can only encrypt a database when you create it. However, you can create a snapshot of a database, encrypt that snapshot, and restore it as encrypted.
From the Console
Perform the following actions to create an encrypted database instance from the current one:
- Open the security settings using the "Open in AWS" menu option
- Select
Actions, and thenTake a snapshot - Give it a name and click
Take snapshot - Select the newly created snapshot, and then
Actions,Copy snapshot - Select the region and give it a name
- Select a KMS key to encrypt the database with
- After you created the copy, select it
- Select
Actions, and thenRestore snapshot - Select the appropriate settings and click
Restore DB Instance
Default Value
By default, encryption is turned on when creating a new database.
References
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
RDS instances use encrypted volumes
Connectors
Covered asset types
Expected check: eq []
{dbInstances(where:{encrypted:false}){...AssetFragment}}
AWS