Skip to main content

🛡️ AWS RDS Instance Encryption is not enabled🟢

Logic​

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-6ba5ecd21

Description​

Open File

Description​

Amazon RDS encrypted DB instances use the industry standard AES-256 encryption algorithm to encrypt your data on the server that hosts your Amazon RDS DB instances. After your data is encrypted, Amazon RDS handles authentication of access and decryption of your data transparently with a minimal impact on performance.

Rationale​

Databases are likely to hold sensitive and critical data, it is highly recommended to implement encryption in order to protect your data from unauthorized access or disclosure. With RDS encryption enabled, the data stored on the instance's underlying storage, the automated backups, read replicas, and snapshots, are all encrypted.

Audit​

From Console​
  1. Login to the AWS Management Console and open the RDS dashboard at https://console.aws.amazon.com/rds/.
  2. In the navigation pane, under RDS dashboard, click Databases.
  3. Select the RDS Instance that you want to examine.
  4. Click Instance Name to see details, then click on Configuration tab.
  5. Under Configuration Details section, In Storage pane search for the Encryption Enabled Status.

... see more

Remediation​

Open File

Remediation​

From Console​

  1. Login to the AWS Management Console and open the RDS dashboard at https://console.aws.amazon.com/rds/.

  2. In the left navigation panel, click on Databases.

  3. Select the Database instance that needs to be encrypted.

  4. Click on Actions button placed at the top right and select Take Snapshot.

  5. On the Take Snapshot page, enter a database name of which you want to take a snapshot in the Snapshot Name field and click on Take Snapshot.

  6. Select the newly created snapshot and click on the Action button placed at the top right and select Copy snapshot from the Action menu.

  7. On the Make Copy of DB Snapshot page, perform the following:

    • In the New DB Snapshot Identifier field, Enter a name for the new snapshot.
    • Check Copy Tags, New snapshot must have the same tags as the source snapshot.
    • Select Yes from the Enable Encryption dropdown list to enable encryption, You can choose to use the AWS default encryption key or custom key from Master Key dropdown list.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 APRA CPG 234 → 💼 52c appropriate encryption, cleansing and auditing of devices;99no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.3] RDS DB instances should have encryption at-rest enabled11no data
💼 CIS AWS v1.4.0 → 💼 2.3.1 Ensure that encryption is enabled for RDS Instances11no data
💼 CIS AWS v1.5.0 → 💼 2.3.1 Ensure that encryption is enabled for RDS Instances - Level 1 (Automated)11no data
💼 CIS AWS v2.0.0 → 💼 2.3.1 Ensure that encryption-at-rest is enabled for RDS Instances - Level 1 (Automated)11no data
💼 CIS AWS v3.0.0 → 💼 2.3.1 Ensure that encryption-at-rest is enabled for RDS Instances - Level 1 (Automated)11no data
💼 CIS AWS v4.0.0 → 💼 2.2.1 Ensure that encryption-at-rest is enabled for RDS instances (Automated)1no data
💼 CIS AWS v4.0.1 → 💼 2.2.1 Ensure that encryption-at-rest is enabled for RDS instances (Automated)1no data
💼 CIS AWS v5.0.0 → 💼 2.2.1 Ensure that encryption-at-rest is enabled for RDS instances (Automated)1no data
💼 CIS AWS v6.0.0 → 💼 3.2.1 Ensure that encryption-at-rest is enabled for RDS instances (Automated)1no data
💼 Cloudaware Framework → 💼 Data Encryption44no data
💼 FedRAMP High Security Controls → 💼 AC-4(4) Flow Control of Encrypted Information (H)2526no data
💼 FedRAMP High Security Controls → 💼 CM-3(6) Cryptography Management (H)6no data
💼 FedRAMP High Security Controls → 💼 SC-7(10) Prevent Exfiltration (H)6no data
💼 FedRAMP High Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)1624no data
💼 FedRAMP High Security Controls → 💼 SC-28 Protection of Information at Rest (L)(M)(H)1724no data
💼 FedRAMP High Security Controls → 💼 SC-28(1) Cryptographic Protection (L)(M)(H)514no data
💼 FedRAMP Low Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)24no data
💼 FedRAMP Low Security Controls → 💼 SC-28 Protection of Information at Rest (L)(M)(H)124no data
💼 FedRAMP Low Security Controls → 💼 SC-28(1) Cryptographic Protection (L)(M)(H)14no data
💼 FedRAMP Moderate Security Controls → 💼 SC-13 Cryptographic Protection (L)(M)(H)24no data
💼 FedRAMP Moderate Security Controls → 💼 SC-28 Protection of Information at Rest (L)(M)(H)124no data
💼 FedRAMP Moderate Security Controls → 💼 SC-28(1) Cryptographic Protection (L)(M)(H)14no data
💼 GDPR → 💼 Art. 25 Data protection by design and by default1010no data
💼 GDPR → 💼 Art. 32 Security of processing55no data
💼 ISO/IEC 27001:2013 → 💼 A.10.1.1 Policy on the use of cryptographic controls1819no data
💼 ISO/IEC 27001:2022 → 💼 5.33 Protection of records1015no data
💼 NIST CSF v1.1 → 💼 PR.DS-1: Data-at-rest is protected1530no data
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented4791no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected148no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected125no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected142no data
💼 NIST SP 800-53 Revision 4 → 💼 SC-28 PROTECTION OF INFORMATION AT REST233no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(2) Information Flow Enforcement _ Processing Domains3032no data
💼 NIST SP 800-53 Revision 5 → 💼 CA-9(1) Internal System Connections _ Compliance Checks25no data
💼 NIST SP 800-53 Revision 5 → 💼 CM-3(6) Configuration Change Control _ Cryptography Management6no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(10) Boundary Protection _ Prevent Exfiltration6no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-13 Cryptographic Protection413no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-28 Protection of Information at Rest31625no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-28(1) Protection of Information at Rest _ Cryptographic Protection1014no data
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(6) Software, Firmware, and Information Integrity _ Cryptographic Protection12no data
💼 PCI DSS v3.2.1 → 💼 3.4.1 If disk encryption is used, logical access must be managed separately and independently of native operating system authentication and access control mechanisms.712no data
💼 PCI DSS v4.0.1 → 💼 3.3.2 SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography.13no data
💼 PCI DSS v4.0.1 → 💼 3.5.1.3 If disk-level or partition-level encryption is used (rather than file-, column-, or field--level database encryption) to render PAN unreadable.12no data
💼 PCI DSS v4.0 → 💼 3.3.2 SAD that is stored electronically prior to completion of authorization is encrypted using strong cryptography.813no data
💼 PCI DSS v4.0 → 💼 3.5.1.3 If disk-level or partition-level encryption is used (rather than file-, column-, or field--level database encryption) to render PAN unreadable.12no data
💼 SOC 2 → 💼 CC6.1-10 Uses Encryption to Protect Data611no data