๐ก๏ธ AWS RDS Cluster Encryption is not enabled๐ข
- Contextual name: ๐ก๏ธ Cluster Encryption is not enabled๐ข
- ID:
/ce/ca/aws/rds/cluster-encryption - Tags:
- ๐ข Policy with categories
- ๐ข Policy with type
- ๐ข Production policy
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
SECURITY
Logicโ
- ๐ง prod.logic.yaml๐ข
- ๐ AWS RDS Cluster
- ๐ AWS RDS Cluster - object.extracts.yaml
- ๐งช test-data.json
Similar Policiesโ
- AWS Security Hub: [RDS.27] RDS DB clusters should be encrypted at rest
- AWS Security Hub: [DocumentDB.1] Amazon DocumentDB clusters should be encrypted at rest
Descriptionโ
Descriptionโ
This policy identifies AWS RDS Clusters that are not configured with encryption at rest. Amazon RDS uses AWS Key Management Service (KMS) to manage encryption keys. When encryption at rest is enabled, it protects the underlying storage for DB clusters, as well as automated backups, read replicas, and snapshots.
Rationaleโ
Since databases often contain sensitive and business-critical information, enabling encryption at rest is strongly recommended to safeguard data against unauthorized access or disclosure. When RDS encryption is enabled, all associated data, including the cluster storage, automated backups, read replicas, and snapshots, is securely encrypted.
Auditโ
This policy flags an AWS RDS Cluster as
INCOMPLIANTif theStorage Encryptedcheckbox is not set to true.
Remediationโ
Remediationโ
Encrypt the Clusterโ
From Command Lineโ
To encrypt an existing unencrypted RDS cluster, follow these steps:
Create a snapshot of the unencrypted cluster:
aws rds create-db-cluster-snapshot \
--db-cluster-identifier {{unencrypted-cluster-id}} \
--db-cluster-snapshot-identifier {{snapshot-id}}Copy the snapshot with encryption enabled:
aws rds copy-db-cluster-snapshot \
--source-db-cluster-snapshot-identifier {{snapshot-id}} \
--target-db-cluster-snapshot-identifier {{encrypted-snapshot-id}} \
--kms-key-id {{your-kms-key-id}}Restore the encrypted snapshot to a new cluster:
aws rds restore-db-cluster-from-snapshot \
--db-cluster-identifier {{new-encrypted-cluster-id}} \
--snapshot-identifier {{encrypted-snapshot-id}} \
--engine {{engine-name}}Update application connection strings to point to the new encrypted cluster.
Delete the old unencrypted cluster after confirming successful migration:
... see more