To simplify rule management across your Virtual Private Cloud (VPC) networks,
use global network firewall policies to consolidate multiple rules into a
single object. Review the specifications and enforcement methods of global network
policies to maintain micro-segmentation and control traffic flow.

For more information, see the [Firewall policies overview](https://docs.cloud.google.com/firewall/docs/firewall-policies-overview.md.txt).

## Specifications

- Global network firewall policies are container resources for firewall rules. Each global network firewall policy resource is defined within a project.
  - After you create a global network firewall policy, you can add, update, and delete firewall rules in the policy.
  - For specification information about the rules in global network firewall policies, see [Firewall policy
    rule components](https://docs.cloud.google.com/firewall/docs/firewall-policies-rule-details).
- To apply global network firewall policy rules to a VPC network, you must *associate* the firewall policy with that VPC network.
  - You can associate a global network firewall policy with multiple VPC networks. Make sure that the firewall policy and the associated networks belong to the same project.
  - Each VPC network can be associated with only *one* global network firewall policy.
  - If the firewall policy isn't associated with any VPC network, the rules in that policy have no effect. A firewall policy that is not associated with any network is an *unassociated* global network firewall policy.
- When a global network firewall policy is associated with one or more VPC networks, the firewall policy rules are enforced in the following ways:
  - Existing rules are enforced against applicable resources in the associated VPC networks.
  - Any changes made to the rules are enforced against applicable resources in the associated VPC networks.
- Rules in global network firewall policies are enforced along with other firewall rules as described in [Policy and rule evaluation
  order](https://docs.cloud.google.com/firewall/docs/firewall-policies-rule-eval-order).

<!-- -->

- Use global network firewall policy rules to configure Layer 7
  inspection of matched traffic, such as when using the
  [URL filtering service](https://docs.cloud.google.com/firewall/docs/configure-url-filtering.md.txt) or the
  [intrusion detection and prevention service](https://docs.cloud.google.com/firewall/docs/configure-intrusion-prevention.md.txt).

  You create a firewall policy rule with `apply_security_profile_group`
  action and name of the [security profile group](https://docs.cloud.google.com/firewall/docs/about-security-profile-groups.md.txt).
  The traffic matching the firewall policy rule is transparently forwarded to
  the firewall endpoint for Layer 7 inspection. To learn
  how to create a firewall policy rule,
  see [Add firewall policy rule](https://docs.cloud.google.com/firewall/docs/use-network-firewall-policies.md.txt#add_rules).

## Global network firewall policy rule details

For more information about the components and parameters of rules in a global
network firewall policy, see [Firewall policy
rule components](https://docs.cloud.google.com/firewall/docs/firewall-policies-rule-details).

The following table summarizes key differences between global network
firewall policy rules and VPC firewall rules:

|   | Global network firewall policy rules | VPC firewall rules |
|---|---|---|
| Priority number | Must be unique within a policy | Duplicate priorities allowed |
| Service accounts as targets | Yes | Yes |
| Service accounts as sources (ingress rules only) | No | Yes |
| Tag type | Secure tag | Network tag |
| Name and description | Policy name, policy and rule description | Rule name and description |
| Batch update | Yes---for policy clone, edit, and replace functions | No |
| Reuse | Yes | No |
| Quota | Attribute count---based on a total complexity of each rule in the policy | Rule count---complex and simple firewall rules have the same quota impact |

## Predefined rules

When you create a global network firewall policy, Cloud Next Generation Firewall (Cloud NGFW) adds
predefined rules with the lowest priority to the policy. These rules are applied
to any connections that don't match an explicitly defined rule in the policy,
causing such connections to be passed down to lower-level policies or network rules.

To learn about the various types of predefined
rules and their characteristics, see [Predefined rules for firewall policies](https://docs.cloud.google.com/firewall/docs/pre-defined-rules.md.txt).