Control: Azure API for FHIR should use a customer-managed key to encrypt data at rest
Description
Use a customer-managed key to control the encryption at rest of the data stored in Azure API for FHIR when this is a regulatory or compliance requirement. Customer-managed keys also deliver double encryption by adding a second layer of encryption on top of the default one done with service-managed keys.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmkSnapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmk --shareSQL
This control uses a named query:
select a.id as resource, case when cosmos_db_configuration -> 'keyVaultKeyUri' is not null then 'ok' else 'alarm' end as status, case when cosmos_db_configuration -> 'keyVaultKeyUri' is not null then a.name || ' encrypted with CMK.' else a.name || ' not encrypted with CMK.' end as reason , a.resource_group as resource_group , sub.display_name as subscriptionfrom azure_healthcare_service as a, azure_subscription as subwhere sub.subscription_id = a.subscription_id;