More Info:

Amazon DynamoDB tables should be using AWS-managed Customer Master Keys (CMKs) instead of AWS-owned CMKs for Server-Side Encryption (SSE), in order to meet strict encryption compliance and regulatory requirements. DynamoDB supports to switch from AWS-owned CMKs to customer-managed CMKs managed using Amazon Key Management Service (KMS), without any code to encrypt the data.

Risk Level

Medium

Address

Security

Compliance Standards

HIPAA, NIST, SOC2, GDPR, ISO27001

Triage and Remediation

Remediation

To remediate the misconfiguration of AWS DynamoDB tables not using KMS CMKs for encryption, you can follow these steps using the AWS Management Console:

  1. Sign in to the AWS Management Console: Go to the AWS Management Console and sign in to your account.

  2. Navigate to DynamoDB: From the services menu, select DynamoDB to access the DynamoDB dashboard.

  3. Select the DynamoDB Table: Locate the DynamoDB table that you want to remediate and click on its name to open the table details.

  4. Configure Encryption: In the table details, click on the “Manage” tab and then select the “Encryption” option.

  5. Enable Server-Side Encryption: In the Encryption settings, select the option to enable server-side encryption.

  6. Choose KMS CMK: Choose the option to use a KMS key to encrypt the DynamoDB table. You can either select an existing KMS CMK or create a new one.

  7. Save Changes: Once you have selected the appropriate KMS CMK, save the changes to apply the encryption settings to the DynamoDB table.

  8. Verify Encryption: After saving the changes, verify that the encryption settings have been successfully applied to the DynamoDB table.

By following these steps, you can remediate the misconfiguration of AWS DynamoDB tables not using KMS CMKs for encryption and ensure that the data in the table is encrypted using a KMS key for improved security.

Additional Reading: