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 terraform_azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmk

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run terraform_azure_compliance.control.healthcare_fhir_azure_api_encrypted_at_rest_with_cmk --share

SQL

This control uses a named query:

select
  address as resource,
  case
    when (attributes_std -> 'cosmosdb_key_vault_key_versionless_id') is null then 'alarm'
    else 'ok'
  end status,
  split_part(address, '.', 2) || case
    when (attributes_std -> 'cosmosdb_key_vault_key_versionless_id') is null then ' not encrypted with CMK'
    else ' encrypted with CMK'
  end || '.' reason
  
  , path || ':' || start_line
from
  terraform_resource
where
  type = 'azurerm_healthcare_service';

Control: Azure API for FHIR should use a customer-managed key to encrypt data at rest

Description

Usage

SQL

Tags