Skip to main content

๐Ÿ›ก๏ธ AWS RDS Cluster Encryption is not enabled๐ŸŸข

  • Contextual name: ๐Ÿ›ก๏ธ Cluster Encryption is not enabled๐ŸŸข
  • ID: /ce/ca/aws/rds/cluster-encryption
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Logicโ€‹

Similar Policiesโ€‹

Descriptionโ€‹

Open File

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 INCOMPLIANT if the Storage Encrypted checkbox is not set to true.

Remediationโ€‹

Open File

Remediationโ€‹

Encrypt the Clusterโ€‹

From Command Lineโ€‹

To encrypt an existing unencrypted RDS cluster, follow these steps:

  1. 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}}
  2. 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}}
  3. 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}}
  4. Update application connection strings to point to the new encrypted cluster.

  5. Delete the old unencrypted cluster after confirming successful migration:

... see more

policy.yamlโ€‹

Open File

Linked Framework Sectionsโ€‹

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
๐Ÿ’ผ AWS Foundational Security Best Practices v1.0.0 โ†’ ๐Ÿ’ผ [DocumentDB.1] Amazon DocumentDB clusters should be encrypted at rest1no data
๐Ÿ’ผ AWS Foundational Security Best Practices v1.0.0 โ†’ ๐Ÿ’ผ [RDS.27] RDS DB clusters should be encrypted at rest1no data
๐Ÿ’ผ AWS Well-Architected โ†’ ๐Ÿ’ผ SEC08-BP02 Enforce encryption at rest14no data
๐Ÿ’ผ Cloudaware Framework โ†’ ๐Ÿ’ผ Data Encryption54no data
๐Ÿ’ผ FedRAMP High Security Controls โ†’ ๐Ÿ’ผ CM-3(6) Cryptography Management (H)12no data
๐Ÿ’ผ FedRAMP High Security Controls โ†’ ๐Ÿ’ผ SC-7(10) Prevent Exfiltration (H)12no data
๐Ÿ’ผ FedRAMP High Security Controls โ†’ ๐Ÿ’ผ SC-13 Cryptographic Protection (L)(M)(H)1632no data
๐Ÿ’ผ FedRAMP High Security Controls โ†’ ๐Ÿ’ผ SC-28 Protection of Information at Rest (L)(M)(H)1731no data
๐Ÿ’ผ FedRAMP High Security Controls โ†’ ๐Ÿ’ผ SC-28(1) Cryptographic Protection (L)(M)(H)520no data
๐Ÿ’ผ FedRAMP Low Security Controls โ†’ ๐Ÿ’ผ SC-13 Cryptographic Protection (L)(M)(H)32no data
๐Ÿ’ผ FedRAMP Low Security Controls โ†’ ๐Ÿ’ผ SC-28 Protection of Information at Rest (L)(M)(H)131no data
๐Ÿ’ผ FedRAMP Low Security Controls โ†’ ๐Ÿ’ผ SC-28(1) Cryptographic Protection (L)(M)(H)20no data
๐Ÿ’ผ FedRAMP Moderate Security Controls โ†’ ๐Ÿ’ผ SC-13 Cryptographic Protection (L)(M)(H)32no data
๐Ÿ’ผ FedRAMP Moderate Security Controls โ†’ ๐Ÿ’ผ SC-28 Protection of Information at Rest (L)(M)(H)131no data
๐Ÿ’ผ FedRAMP Moderate Security Controls โ†’ ๐Ÿ’ผ SC-28(1) Cryptographic Protection (L)(M)(H)20no data
๐Ÿ’ผ NIST CSF v2.0 โ†’ ๐Ÿ’ผ PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected159no data
๐Ÿ’ผ NIST CSF v2.0 โ†’ ๐Ÿ’ผ PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected135no data
๐Ÿ’ผ NIST CSF v2.0 โ†’ ๐Ÿ’ผ PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected151no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ CA-9(1) Internal System Connections _ Compliance Checks31no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ CM-3(6) Configuration Change Control _ Cryptography Management12no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ SC-7(10) Boundary Protection _ Prevent Exfiltration12no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ SC-13 Cryptographic Protection421no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ SC-28 Protection of Information at Rest31732no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ SC-28(1) Protection of Information at Rest _ Cryptographic Protection1020no data
๐Ÿ’ผ NIST SP 800-53 Revision 5 โ†’ ๐Ÿ’ผ SI-7(6) Software, Firmware, and Information Integrity _ Cryptographic Protection19no data