Azure Policy Regulatory Compliance controls for Azure API Management
APPLIES TO: All API Management tiers
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 Management. 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.
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 | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | API Management services should use a virtual network | 1.0.2 |
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 | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | API Management services should use a virtual network | 1.0.2 |
Microsoft cloud security benchmark
The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud security benchmark, see the Azure Security Benchmark mapping files.
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Microsoft cloud security benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Security | NS-2 | Secure cloud services with network controls | API Management services should use a virtual network | 1.0.2 |
| Network Security | NS-2 | Secure cloud services with network controls | API Management should disable public network access to the service configuration endpoints | 1.0.1 |
| Identity Management | IM-4 | Authenticate server and services | API endpoints in Azure API Management should be authenticated | 1.0.1 |
| Identity Management | IM-4 | Authenticate server and services | API Management calls to API backends should be authenticated | 1.0.1 |
| Identity Management | IM-4 | Authenticate server and services | API Management calls to API backends should not bypass certificate thumbprint or name validation | 1.0.2 |
| Identity Management | IM-8 | Restrict the exposure of credential and secrets | API Management minimum API version should be set to 2019-12-01 or higher | 1.0.1 |
| Identity Management | IM-8 | Restrict the exposure of credential and secrets | API Management secret named values should be stored in Azure Key Vault | 1.0.2 |
| Privileged Access | PA-7 | Follow just enough administration (least privilege) principle | API Management subscriptions should not be scoped to all APIs | 1.1.0 |
| Data Protection | DP-3 | Encrypt sensitive data in transit | API Management APIs should use only encrypted protocols | 2.0.2 |
| Data Protection | DP-6 | Use a secure key management process | API Management secret named values should be stored in Azure Key Vault | 1.0.2 |
| Asset Management | AM-2 | Use only approved services | Azure API Management platform version should be stv2 | 1.0.0 |
| Asset Management | AM-3 | Ensure security of asset lifecycle management | API endpoints that are unused should be disabled and removed from the Azure API Management service | 1.0.1 |
| Posture and Vulnerability Management | PV-2 | Audit and enforce secure configurations | API Management direct management endpoint should not be enabled | 1.0.2 |
| Posture and Vulnerability Management | PV-2 | Audit and enforce secure configurations | API Management minimum API version should be set to 2019-12-01 or higher | 1.0.1 |
| Posture and Vulnerability Management | PV-2 | Audit and enforce secure configurations | Azure API Management platform version should be stv2 | 1.0.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.3 | Control the flow of CUI in accordance with approved authorizations. | API Management services should use a virtual network | 1.0.2 |
| 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. | API Management services should use a virtual network | 1.0.2 |
| 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. | API Management services should use a virtual network | 1.0.2 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | API Management services should use a virtual network | 1.0.2 |
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 | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | API Management services should use a virtual network | 1.0.2 |
| System And Communications Protection | SC-7 (3) | Access Points | API Management services should use a virtual network | 1.0.2 |
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 | API Management services should use a virtual network | 1.0.2 |
| System and Communications Protection | SC-7 | Boundary Protection | API Management services should use a virtual network | 1.0.2 |
| System and Communications Protection | SC-7 (3) | Access Points | API Management services should use a virtual network | 1.0.2 |
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.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | API Management services should use a virtual network | 1.0.2 |
Reserve Bank of India IT Framework for Banks v2016
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RBI ITF Banks v2016. For more information about this compliance standard, see RBI ITF Banks v2016 (PDF).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | API Management services should use a virtual network | 1.0.2 |
RMIT Malaysia
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Resilience | 10.33 | Network Resilience - 10.33 | API Management services should use a virtual network | 1.0.2 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.