Source | Azure Portal | ||||||||||||||
Display name | FHIR Service should use a customer-managed key to encrypt data at rest | ||||||||||||||
Id | c42dee8c-0202-4a12-bd8e-3e171cbf64dd | ||||||||||||||
Version | 1.0.0 Details on versioning |
||||||||||||||
Versioning |
Versions supported for Versioning: 1 1.0.0 Built-in Versioning [Preview] |
||||||||||||||
Category | Healthcare APIs Microsoft Learn |
||||||||||||||
Description | Use a customer-managed key to control the encryption at rest of the data stored in Azure Health Data Services FHIR Service 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. | ||||||||||||||
Mode | Indexed | ||||||||||||||
Type | BuiltIn | ||||||||||||||
Preview | False | ||||||||||||||
Deprecated | False | ||||||||||||||
Effect | Default Audit Allowed Audit, Disabled |
||||||||||||||
RBAC role(s) | none | ||||||||||||||
Rule aliases | IF (1)
|
||||||||||||||
Rule resource types | IF (1) Microsoft.HealthcareApis/workspaces/fhirservices |
||||||||||||||
Compliance | Not a Compliance control | ||||||||||||||
Initiatives usage | none | ||||||||||||||
History |
|
||||||||||||||
JSON compare | n/a | ||||||||||||||
JSON |
|