Network Firewall Policies and Enforcement Order in Cloud NGFW

GCP Study Hub
November 20, 2026

Global and regional network firewall policies are Cloud NGFW resources that you associate with VPC networks, one network at a time. They sit alongside the older VPC firewall rules in the same network, and the order in which the two are evaluated is a per-network setting called the policy and rule enforcement order. For the Professional Cloud Network Engineer exam, the distinction to hold onto is that this setting, not rule priority numbers, decides whether VPC firewall rules or network firewall policies get the first chance to match a packet.

What network firewall policies add over VPC firewall rules

VPC firewall rules support only two actions, allow and deny. Network firewall policies support features that VPC firewall rules do not, and two of them shape most designs that mix the two:

  • FQDN objects let a rule match traffic by domain name. They are only supported in firewall policies, so a rule that depends on one cannot be rewritten as a VPC firewall rule.
  • The apply_security_profile_group action sends matching traffic to Cloud NGFW inspection, such as intrusion prevention. VPC firewall rules have no equivalent action.

Because these capabilities only exist in policies, the question of where a rule lives is often settled by what it needs to do. The question of whether it takes effect is then settled by the enforcement order.

How traffic is evaluated within a VPC network

Firewall evaluation for a VPC network happens in two stages:

  • Hierarchical firewall policies are always evaluated first. When a hierarchical rule uses goto_next, evaluation passes down to the network level.
  • VPC firewall rules and network firewall policies are evaluated next, in the order set by that network's policy and rule enforcement order.

Nothing at the network level can move ahead of hierarchical policies. The enforcement order only decides how the second stage is arranged.

AFTER_CLASSIC_FIREWALL and BEFORE_CLASSIC_FIREWALL

Each VPC network carries its own policy and rule enforcement order, and it takes one of two values:

  • AFTER_CLASSIC_FIREWALL is what a network created with default settings uses. VPC firewall rules are evaluated first, and global and regional network firewall policies are evaluated after them.
  • BEFORE_CLASSIC_FIREWALL reverses that, so network firewall policies are evaluated before VPC firewall rules.

Under the default order, a VPC firewall rule that denies a packet ends evaluation before any network firewall policy rule is consulted. This matters most for broad rules. A wide deny among the VPC firewall rules, even one with a large priority number, still matches traffic before a network firewall policy rule with a small number is reached, because the two numbers belong to different layers.

The default therefore limits what policy-only features can do. An allow rule that relies on an FQDN object, or a rule that applies a security profile group for intrusion prevention, never sees traffic that a VPC firewall deny rule has already stopped. When a network has broad VPC firewall rules and its policy rules need to take effect ahead of them, the network's enforcement order has to be set to BEFORE_CLASSIC_FIREWALL. The broad VPC rules still apply to whatever the policy does not match.

Why priority numbers do not change the order

Priority numbers rank rules inside a single policy, or inside one network's set of VPC firewall rules. They never change which layer is evaluated first. Renumbering rules can reorder them within their own layer, but moving a whole layer ahead of another is the job of the enforcement order, and hierarchical policies stay first regardless of any numbers.

Per-network settings and inconsistent behavior

Because the enforcement order belongs to each VPC network, networks that carry the same rules and the same policies can still behave differently when their enforcement orders differ. Every network created with default settings starts with AFTER_CLASSIC_FIREWALL, so the setting has to be changed on each network that needs network firewall policies evaluated first.

Putting it together

A practical way to reason about these designs on the Professional Cloud Network Engineer exam is to place each rule by the features it needs, then check the enforcement order of the network it applies to. Rules that only allow or deny can live in VPC firewall rules or in a policy. Rules that need FQDN objects or apply_security_profile_group belong in a network firewall policy. If those policy rules must take effect before broad VPC firewall rules, the network needs BEFORE_CLASSIC_FIREWALL, and hierarchical policies continue to be evaluated ahead of both.

Our Professional Cloud Network Engineer practice exams cover network firewall policy enforcement order alongside hierarchical firewall policies and Cloud NGFW Enterprise inspection, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow