Ensure IBM Cloudant encryption is enabled with customer managed keys

So wird geprüft

Prüfmethode: Manuelle Prüfung

Diese Empfehlung kann nicht automatisch geprüft werden. Ein Scan führt sie mit diesen Anweisungen auf, wenn Sie --include-manual übergeben.

Users can audit whether a Cloudant Dedicated Hardware environment is using a customer-managed key by viewing associations between root keys and associated cloud services in the IBM Key Protect UI or API. Use the steps below to see the associations and verify that the Cloudant Dedicated Hardware plan instance(s) have the appropriate associations listed to show the use of customer-managed encryption key in Key Protect. Using Console: 1. Log in to the IBM Cloud console. 2. Go to Menu, Resource List to view a list of your resources. 3. From your IBM Cloud resource list, select your provisioned instance of Key Protect. 4. On the application details page, select the Associated Resources tab on the left side menu. 5. On the Associated resources page, use the Associated Resources table to browse the registrations in your service. 6. Click the ^ icon under the Details column to view a list of details for a specific registration. 7. Click Filter button to filter for resources by key ID, Cloud Resource Name (CRN), and retention policy. Using API: You can retrieve the registration details that are associated with a specific root key by making a GET call to the following endpoint: https://<r...

So wird behoben

Behebungsmethode: Anleitung oder Infrastruktur-Patch

The process to remediate a configuration where there is no use of a customer-managed encryption is as follows: 1. Provision a new Cloudant Dedicated Hardware plan instance using a customer- managed key as shown in details above. 2. Create new Cloudant instance(s) on the Dedicated Hardware plan instance that is using a customer-managed key as needed. 3. Replicate data over from the Cloudant instances not using a customer-managed key to the instances on the Dedicaed Hardware environment using the customer- managed key. This process requires use of the Cloudant replication feature as shown in the Cloudant documentation. 4. Delete any Cloudant instances on environments that do not use customer- managed keys once the replication is complete.