Control: Azure API for FHIR should use a customer-managed key to encrypt data at rest
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.
Run the control in your terminal:
steampipe check terraform_azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmk
Snapshot and share results via Steampipe Cloud:
steampipe loginsteampipe check --share terraform_azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmk
This control uses a named query:healthcare_fhir_azure_api_encrypted_at_rest_with_cmk