Azure Policy Regulatory Compliance controls for Azure API for FHIR
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 |
New Zealand ISM Restricted
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - New Zealand ISM Restricted. For more information about this compliance standard, see New Zealand ISM Restricted.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Software security | SS-3 | 14.1.9 Maintaining hardened SOEs | Azure API for FHIR should use private link | 1.0.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 |
NZ ISM Restricted v3.5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NZ ISM Restricted v3.5. For more information about this compliance standard, see NZ ISM Restricted v3.5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Software security | NZISM Security Benchmark SS-3 | 14.1.9 Maintaining hardened SOEs | Azure API for FHIR should use private link | 1.0.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
Submit and view feedback for