Azure Firewall should use Standard or Premium tier
High
Azure
General
firewall-azure-firewall-standard-premium
Azure Firewall Standard/Premium provides network and application-level protection at the edge
Applies to
Microsoft.Network/azureFirewalls
What CGPulse checks
A resource passes this rule when sku.tier must be one of ["Standard","Premium"]. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Deploy Azure Firewall with Standard or Premium tier to enable advanced threat protection. In Azure Portal: Azure Firewall > Overview > verify SKU is Standard or Premium. See: https://learn.microsoft.com/en-us/azure/firewall/choose-firewall-sku
CLI
az network firewall show --ids "{id}" --query "sku.tier" -o tsvTerraform
resource "azurerm_firewall" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
sku_name = "AZFW_VNet"
sku_tier = "Standard"
zones = ["1", "2", "3"]
ip_configuration {
name = "configuration"
subnet_id = var.subnet_id
public_ip_address_id = "<public-ip-id>"
}
}
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