Container Registry should restrict network access
High
Azure
General
acr-network-deny
Applies to
Microsoft.ContainerRegistry/registries
What CGPulse checks
A resource passes this rule when networkRuleSet.defaultAction must equal Deny. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Restrict network access by setting default action to Deny and adding allowed networks. In Azure Portal: Container Registry > Networking > set Default action to Deny. See: https://learn.microsoft.com/en-us/azure/container-registry/container-registry-access-selected-networks
Careful: Setting default network action to Deny blocks all connections except from allowed IPs/VNets. Requires Premium SKU
CLI
az acr update --ids "{id}" --default-action DenyTerraform
resource "azurerm_container_registry" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
sku = "Premium"
network_rule_set {
default_action = "Deny"
}
# Requires Premium SKU
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes