More Info:

Ensure that Bigtable clusters are encrypted

Risk Level

High

Address

Security

Compliance Standards

SOC2, NIST, GDPR, ISO27001, HIPAA, HITRUST, NISTCSF, PCIDSS

Triage and Remediation

Remediation

To remediate the misconfiguration “Bigtable Cluster should be encrypted” in GCP, you can follow the below steps using the GCP console:

  1. Open the GCP console and navigate to the Bigtable instance that needs to be encrypted.

  2. Click on the “Edit” button on the top of the page.

  3. Scroll down to the “Encryption” section and click on the “Edit” button next to it.

  4. Select the “Customer-managed key” option and choose the key that you want to use for encryption.

  5. Click on the “Save” button to save the changes.

  6. Once the changes are saved, the Bigtable cluster will be encrypted using the selected customer-managed key.

  7. Verify the encryption status of the Bigtable cluster by checking the “Encryption” section on the Bigtable instance page. It should show that the cluster is encrypted using the selected customer-managed key.

By following these steps, you can remediate the misconfiguration “Bigtable Cluster should be encrypted” in GCP using the GCP console.

Additional Reading: