Azure Policy Regulatory Compliance controls for Azure API for FHIR
Important
Azure API for FHIR will be retired on September 30, 2026. Follow the migration strategies to transition to Azure Health Data Services FHIR service by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. Azure Health Data Services FHIR service is the evolved version of Azure API for FHIR that enables customers to manage FHIR, DICOM, and MedTech services with integrations into other Azure services.
Regulatory Compliance in Azure Policy provides Microsoft created and managed initiative definitions, known as built-ins, for the compliance domains and security controls related to different compliance standards. This page lists the compliance domains and security controls for Azure API for FHIR. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.
The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.
Important
Each control is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.
CMMC Level 3
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC.1.001 | Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). | CORS should not allow every domain to access your API for FHIR | 1.1.0 |
| Access Control | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | CORS should not allow every domain to access your API for FHIR | 1.1.0 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | CORS should not allow every domain to access your API for FHIR | 1.1.0 |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | CORS should not allow every domain to access your API for FHIR | 1.1.0 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
| System and Communications Protection | SC.3.183 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | CORS should not allow every domain to access your API for FHIR | 1.1.0 |
FedRAMP High
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
FedRAMP Moderate
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
NIST SP 800-171 R2
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | 3.13.1 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Azure API for FHIR should use private link | 1.0.0 |
NIST SP 800-53 Rev. 4
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 4. For more information about this compliance standard, see NIST SP 800-53 Rev. 4.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure API for FHIR should use private link | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
NIST SP 800-53 Rev. 5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | Azure API for FHIR should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Monitoring and Control | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | SC-7 | Boundary Protection | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | Azure API for FHIR should use private link | 1.0.0 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
NL BIO Cloud Theme
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for NL BIO Cloud Theme. For more information about this compliance standard, see Baseline Information Security Government Cybersecurity - Digital Government (digitaleoverheid.nl).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| U.05.2 Data protection - Cryptographic measures | U.05.2 | Data stored in the cloud service shall be protected to the latest state of the art. | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | Azure API for FHIR should use private link | 1.0.0 |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Azure API for FHIR should use a customer-managed key to encrypt data at rest | 1.1.0 |
Next steps
In this article, you learned about the Azure Policy Regulatory Compliance controls for Azure API for FHIR. For more information, see
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for