Azure Policy Regulatory Compliance controls for Azure Container Registry
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 Container Registry. 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 | Container registries should not allow unrestricted network access | 2.0.0 |
| Network Security | NS-2 | Secure cloud services with network controls | Container registries should use private link | 1.0.1 |
| Data Protection | DP-5 | Use customer-managed key option in data at rest encryption when required | Container registries should be encrypted with a customer-managed key | 1.1.2 |
| Posture and Vulnerability Management | PV-6 | Rapidly and automatically remediate vulnerabilities | Container registry images should have vulnerability findings resolved | 2.0.1 |
| DevOps Security | DS-6 | Enforce security of workload throughout DevOps lifecycle | Container registry images should have vulnerability findings resolved | 2.0.1 |
Azure Security Benchmark v1
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 | 1.1 | Protect resources using Network Security Groups or Azure Firewall on your Virtual Network | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
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). | Container registries should not allow unrestricted network access | 2.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. | Container registries should not allow unrestricted network access | 2.0.0 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | Container registries should not allow unrestricted network access | 2.0.0 |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Container registries should not allow unrestricted network access | 2.0.0 |
| Risk Assessment | RM.2.143 | Remediate vulnerabilities in accordance with risk assessments. | Container registry images should have vulnerability findings resolved | 2.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. | Container registries should not allow unrestricted network access | 2.0.0 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Container registries should be encrypted with a customer-managed key | 1.1.2 |
| 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). | Container registries should not allow unrestricted network access | 2.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.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-4 | Information Flow Enforcement | Container registries should not allow unrestricted network access | 2.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Container registries should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Scanning | Container registry images should have vulnerability findings resolved | 2.0.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Container registries should not allow unrestricted network access | 2.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Container registries should use private link | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Container registries should not allow unrestricted network access | 2.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | Container registries should use private link | 1.0.1 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Container registries should be encrypted with a customer-managed key | 1.1.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 | Container registries should not allow unrestricted network access | 2.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Container registries should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Scanning | Container registry images should have vulnerability findings resolved | 2.0.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Container registries should not allow unrestricted network access | 2.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | Container registries should use private link | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Container registries should not allow unrestricted network access | 2.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | Container registries should use private link | 1.0.1 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Container registries should be encrypted with a customer-managed key | 1.1.2 |
HIPAA HITRUST 9.2
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| 08 Network Protection | 0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0806.01m2Organizational.12356-01.m | 0806.01m2Organizational.12356-01.m 01.04 Network Access Control | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0868.09m3Organizational.18-09.m | 0868.09m3Organizational.18-09.m 09.06 Network Security Management | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0869.09m3Organizational.19-09.m | 0869.09m3Organizational.19-09.m 09.06 Network Security Management | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0870.09m3Organizational.20-09.m | 0870.09m3Organizational.20-09.m 09.06 Network Security Management | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0871.09m3Organizational.22-09.m | 0871.09m3Organizational.22-09.m 09.06 Network Security Management | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | [Preview]: Container Registry should use a virtual network service endpoint | 1.0.0-preview |
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) |
|---|---|---|---|---|
| Information security monitoring | ISM-4 | 6.2.6 Resolving vulnerabilities | Container registry images should have vulnerability findings resolved | 2.0.1 |
| Infrastructure | INF-9 | 10.8.35 Security Architecture | Container registries should use private link | 1.0.1 |
| Cryptography | CR-3 | 17.1.46 Reducing storage and physical transfer requirements | Container registries should be encrypted with a customer-managed key | 1.1.2 |
| Gateway security | GS-3 | 19.1.12 Configuration of Gateways | Container registries should not allow unrestricted network access | 2.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 | Container registries should not allow unrestricted network access | 2.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 | Remote Access | Container registries should use private link | 1.0.1 |
| Access Control | AC-17 (1) | Monitoring and Control | Container registries should use private link | 1.0.1 |
| Risk Assessment | RA-5 | Vulnerability Monitoring and Scanning | Container registry images should have vulnerability findings resolved | 2.0.1 |
| System and Communications Protection | SC-7 | Boundary Protection | Container registries should not allow unrestricted network access | 2.0.0 |
| System and Communications Protection | SC-7 | Boundary Protection | Container registries should use private link | 1.0.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Container registries should not allow unrestricted network access | 2.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | Container registries should use private link | 1.0.1 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Container registries should be encrypted with a customer-managed key | 1.1.2 |
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 | Container registries should be encrypted with a customer-managed key | 1.1.2 |
| Gateway security | NZISM Security Benchmark GS-3 | 19.1.12 Configuration of Gateways | Container registries should not allow unrestricted network access | 2.0.0 |
| Infrastructure | NZISM Security Benchmark INF-9 | 10.8.35 Security Architecture | Container registries should use private link | 1.0.1 |
| Information security monitoring | NZISM Security Benchmark ISM-4 | 6.2.6 Resolving vulnerabilities | Container registry images should have vulnerability findings resolved | 2.0.1 |
Reserve Bank of India - IT Framework for NBFC
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| IT Governance | RBI IT Framework 1 | IT Governance-1 | Container registry images should have vulnerability findings resolved | 2.0.1 |
| Information and Cyber Security | RBI IT Framework 3.3 | Vulnerability Management-3.3 | Container registry images should have vulnerability findings resolved | 2.0.1 |
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) |
|---|---|---|---|---|
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Container registries should be encrypted with a customer-managed key | 1.1.2 | |
| Metrics | Metrics-21.1 | Container registries should be encrypted with a customer-managed key | 1.1.2 | |
| Metrics | Metrics-21.1 | Container registries should be encrypted with a customer-managed key | 1.1.2 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Container registries should not allow unrestricted network access | 2.0.0 | |
| Anti-Phishing | Anti-Phishing-14.1 | Container registries should not allow unrestricted network access | 2.0.0 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Container registries should not allow unrestricted network access | 2.0.0 | |
| Anti-Phishing | Anti-Phishing-14.1 | Container registries should use private link | 1.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Container registries should use private link | 1.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Container registries should use private link | 1.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.1 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.3 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.6 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.1 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.3 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.6 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Preventing Execution Of Unauthorised Software | Security Update Management-2.3 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.4 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.4 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.6 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.2 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.1 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.6 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.2 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.1 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Risk Based Transaction Monitoring | Risk Based Transaction Monitoring-20.1 | Container registry images should have vulnerability findings resolved | 2.0.1 | |
| Vulnerability Assessment And Penetration Test And Red Team Exercises | Vulnerability Assessment And Penetration Test And Red Team Exercises-18.4 | Container registry images should have vulnerability findings resolved | 2.0.1 |
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 | RMiT 10.33 | Network Resilience - 10.33 | Configure Container registries to disable public network access | 1.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Container registries should not allow unrestricted network access | 2.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Public network access should be disabled for Container registries | 1.0.0 |
| Cloud Services | RMiT 10.53 | Cloud Services - 10.53 | Container registries should be encrypted with a customer-managed key | 1.1.2 |
| Data Loss Prevention (DLP) | RMiT 11.15 | Data Loss Prevention (DLP) - 11.15 | Configure Container registries to disable public network access | 1.0.0 |
| Cybersecurity Operations | RMiT 11.8 | Cybersecurity Operations - 11.8 | Container registry images should have vulnerability findings resolved | 2.0.1 |
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