Azure Policy Regulatory Compliance controls for Azure AI 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 AI services. 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.
Azure cloud security benchmark
The Azure cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 - Azure cloud security benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Security | NS-2 | Secure cloud services with network controls | [Deprecated]: Cognitive Services should use private link | 3.0.1-deprecated |
| Network Security | NS-2 | Secure cloud services with network controls | Azure AI Services resources should restrict network access | 3.2.0 |
| Network Security | NS-2 | Secure cloud services with network controls | Azure AI Services resources should use Azure Private Link | 1.0.0 |
| Identity Management | IM-1 | Use centralized identity and authentication system | Azure AI Services resources should have key access disabled (disable local authentication) | 1.1.0 |
| Data Protection | DP-5 | Use customer-managed key option in data at rest encryption when required | Azure AI Services resources should encrypt data at rest with a customer-managed key (CMK) | 2.2.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Diagnostic logs in Azure AI services resources should be enabled | 1.0.0 |
Next steps
- See the built-ins on the Azure Policy GitHub repo.