azure_compliance

Azure Compliance

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.

healthcare_fhir_azure_api_encrypted_at_rest_with_cmk

nist_sp_800_171_rev_2_3_13_10

3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems

fedramp_high_sc_12

Cryptographic Key Establishment And Management (SC-12)

nist_sp_800_53_rev_5_sc_12

Cryptographic Key Establishment and Management (SC-12)

all_controls_healthcare

HealthcareAPIs

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

azure

azuread

Run individual configuration, compliance and security controls or full compliance benchmarks for CIS, HIPAA HITRUST, NIST, PCI DSS across all your Azure subscriptions using Powerpipe and Steampipe.

Apache License 2.0

steampipe-mod-azure-compliance

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

Description

Usage

SQL

Tags