Azure Policy Regulatory Compliance controls for Azure Cognitive 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 Cognitive 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 Security Benchmark
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 Security Benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Security | NS-2 | Secure cloud services with network controls | Cognitive Services accounts should disable public network access | 3.0.1 |
| Network Security | NS-2 | Secure cloud services with network controls | Cognitive Services accounts should restrict network access | 3.0.0 |
| Data Protection | DP-5 | Use customer-managed key option in data at rest encryption when required | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 |
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). | Cognitive Services accounts should disable public network access | 3.0.1 |
| 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). | Cognitive Services accounts should restrict network access | 3.0.0 |
| Access Control | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | Cognitive Services accounts should disable public network access | 3.0.1 |
| Access Control | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | Cognitive Services accounts should restrict network access | 3.0.0 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | Cognitive Services accounts should disable public network access | 3.0.1 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | Cognitive Services accounts should restrict network access | 3.0.0 |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Cognitive Services accounts should disable public network access | 3.0.1 |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Cognitive Services accounts should restrict network access | 3.0.0 |
| System and Communications Protection | SC.1.175 | 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. | Cognitive Services accounts should disable public network access | 3.0.1 |
| System and Communications Protection | SC.1.175 | 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. | Cognitive Services accounts should restrict network access | 3.0.0 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.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). | Cognitive Services accounts should disable public network access | 3.0.1 |
| 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). | Cognitive Services accounts should restrict network access | 3.0.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.
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.
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) |
|---|---|---|---|---|
| Cryptography | CR-3 | 17.1.46 Reducing storage and physical transfer requirements | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 |
| Gateway security | GS-2 | 19.1.11 Using Gateways | Cognitive Services accounts should disable public network access | 3.0.1 |
| Gateway security | GS-3 | 19.1.12 Configuration of Gateways | Cognitive Services accounts should restrict network access | 3.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.
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) |
|---|---|---|---|---|
| Cryptography | NZISM Security Benchmark CR-3 | 17.1.53 Reducing storage and physical transfer requirements | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 |
| Gateway security | NZISM Security Benchmark GS-2 | 19.1.11 Using Gateways | Cognitive Services accounts should disable public network access | 3.0.1 |
| Gateway security | NZISM Security Benchmark GS-3 | 19.1.12 Configuration of Gateways | Cognitive Services accounts should restrict network access | 3.0.0 |
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) |
|---|---|---|---|---|
| Anti-Phishing | Anti-Phishing-14.1 | Cognitive Services accounts should disable public network access | 3.0.1 | |
| Metrics | Metrics-21.1 | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 | |
| Metrics | Metrics-21.1 | Cognitive Services accounts should enable data encryption with a customer-managed key | 2.0.0 | |
| Anti-Phishing | Anti-Phishing-14.1 | Cognitive Services accounts should restrict network access | 3.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Submit and view feedback for