More Info:

RDS database instances should be encrypted to fulfill compliance requirements for data-at-rest encryption.

Risk Level

High

Address

Security

Compliance Standards

HIPAA, GDPR, CISAWS, CBP, NIST, AWSWAF, HITRUST, SOC2, NISTCSF, PCIDSS

Triage and Remediation

Remediation

To remediate the misconfiguration of RDS instances not having encryption enabled in AWS, you can follow these steps using the AWS Management Console:

  1. Login to AWS Console: Go to the AWS Management Console and login with your credentials.

  2. Navigate to RDS Service: Click on the “Services” dropdown menu at the top of the page and select “RDS” under the Database category.

  3. Select the RDS Instance: From the list of RDS instances, select the instance for which you want to enable encryption by clicking on the instance identifier.

  4. Modify the Instance: In the RDS instance details page, click on the “Modify” button at the top.

  5. Enable Encryption: Scroll down to the “Encryption” section in the Modify DB Instance page. Check the box for “Enable encryption” to enable encryption for the RDS instance.

  6. Choose Encryption Key: Select the appropriate KMS key from the dropdown menu. You can either choose the default AWS managed key or select a custom KMS key that you have created.

  7. Apply Changes: Scroll down to the bottom of the page and click on the “Continue” button.

  8. Review and Apply Changes: Review the changes you are about to make and click on the “Modify DB Instance” button to apply the changes.

  9. Monitor Encryption Status: Once the modification is complete, monitor the RDS instance to ensure that encryption is enabled successfully. You can check the encryption status in the RDS instance details page.

By following these steps, you can remediate the misconfiguration of RDS instances not having encryption enabled in AWS.

Additional Reading: