More Info:

This rule checks if an Amazon Neptune DB cluster has snapshots encrypted. It marks the rule as NON_COMPLIANT if a Neptune cluster does not have snapshots encrypted.

Risk Level

Medium

Address

Security

Compliance Standards

HIPAA,GDPR,NIST,SEBI

Triage and Remediation

Remediation

To remediate the misconfiguration of Neptune Cluster snapshots not being encrypted in AWS RDS using the AWS Management Console, follow these steps:

  1. Sign in to the AWS Management Console: Go to https://aws.amazon.com/ and sign in to the AWS Management Console using your credentials.

  2. Navigate to Amazon Neptune Console: Once logged in, navigate to the Amazon Neptune console by typing “Neptune” in the search bar at the top of the console and selecting “Amazon Neptune” from the dropdown.

  3. Select your Neptune Cluster: In the Amazon Neptune console, select the Neptune cluster for which you want to enable encryption for snapshots.

  4. Enable Encryption for Snapshots:

    • Click on the Neptune cluster name to view its details.
    • In the left-hand navigation pane, click on “Snapshots”.
    • Select the snapshot for which you want to enable encryption.
    • Click on the “Actions” dropdown menu and select “Modify Snapshot”.
    • In the “Modify Snapshot” window, enable the option for “Encrypt snapshot” and select the appropriate KMS key for encryption.
    • Click on “Modify snapshot” to save the changes.
  5. Verify Encryption:

    • Once the modification is complete, verify that the snapshot is now encrypted by checking the “Encrypted” column in the list of snapshots.

By following these steps, you have successfully remediated the misconfiguration of Neptune Cluster snapshots not being encrypted in AWS RDS using the AWS Management Console.