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 below is associated with one or more Azure Policy definitions. These policies may help you assess compliance with the control; however, there often is not 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 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 may 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-1 Implement security for internal traffic Container registries should not allow unrestricted network access 1.1.0
Network Security NS-2 Connect private networks together Container registries should use private link 1.0.1
Network Security NS-3 Establish private network access to Azure services Container registries should use private link 1.0.1
Data Protection DP-5 Encrypt sensitive data at rest Container registries should be encrypted with a customer-managed key 1.1.2
Posture and Vulnerability Management PV-6 Perform software vulnerability assessments Vulnerabilities in Azure Container Registry images should be remediated 2.0.0

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 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 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. Container registries should not allow unrestricted network access 1.1.0
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. Container registries should not allow unrestricted network access 1.1.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 1.1.0
Risk Assessment RM.2.143 Remediate vulnerabilities in accordance with risk assessments. Vulnerabilities in Azure Container Registry images should be remediated 2.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. Container registries should not allow unrestricted network access 1.1.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 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 Container registries should not allow unrestricted network access 1.1.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 Vulnerabilities in Azure Container Registry images should be remediated 2.0.0
System and Communications Protection SC-7 Boundary Protection Container registries should not allow unrestricted network access 1.1.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 1.1.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 1.1.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 Vulnerabilities in Azure Container Registry images should be remediated 2.0.0
System and Communications Protection SC-7 Boundary Protection Container registries should not allow unrestricted network access 1.1.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 1.1.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)
Segregation in Networks 0805.01m1Organizational.12 - 01.m The organization's security gateways (e.g. firewalls) enforce security policies and are configured to filter traffic between domains, block unauthorized access, and are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet) including DMZs and enforce access control policies for each of the domains. Container Registry should use a virtual network service endpoint 1.0.0-preview
Segregation in Networks 0806.01m2Organizational.12356 - 01.m The organizations network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; and traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. Container Registry should use a virtual network service endpoint 1.0.0-preview
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Container Registry should use a virtual network service endpoint 1.0.0-preview
Network Controls 0868.09m3Organizational.18 - 09.m The organization builds a firewall configuration to restrict inbound and outbound traffic to that which is necessary for the covered data environment. Container Registry should use a virtual network service endpoint 1.0.0-preview
Network Controls 0869.09m3Organizational.19 - 09.m The router configuration files are secured and synchronized. Container Registry should use a virtual network service endpoint 1.0.0-preview
Network Controls 0870.09m3Organizational.20 - 09.m Access to all proxies is denied, except for those hosts, ports, and services that are explicitly required. Container Registry should use a virtual network service endpoint 1.0.0-preview
Network Controls 0871.09m3Organizational.22 - 09.m Authoritative DNS servers are segregated into internal and external roles. 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 Vulnerabilities in Azure Container Registry images should be remediated 2.0.0
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 1.1.0

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 Container registries should not allow unrestricted network access 1.1.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 Vulnerabilities in Azure Container Registry images should be remediated 2.0.0
System and Communications Protection SC-7 Boundary Protection Container registries should not allow unrestricted network access 1.1.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 1.1.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

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 1.1.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 Vulnerabilities in Azure Container Registry images should be remediated 2.0.0
System and Communications Protection SC-7 Boundary Protection Container registries should not allow unrestricted network access 1.1.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 1.1.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

Next steps