Cloud NGFW Enterprise: Intrusion Prevention and TLS Inspection

GCP Study Hub
November 17, 2026

Cloud NGFW Enterprise adds a Google-managed intrusion prevention service to Cloud NGFW. Traffic that a firewall policy rule selects is steered through a zonal firewall endpoint, inspected inline against threat signatures, and dropped or allowed according to a threat prevention security profile. With a TLS inspection policy, the endpoint can also decrypt sessions and check the decrypted payload. Cloud NGFW Enterprise is a managed Google service, not a specific third-party firewall image from Cloud Marketplace. For the Professional Cloud Network Engineer exam, the topic comes down to knowing which resources are involved, how traffic actually reaches an endpoint, and how the service differs from the other Google Cloud tools that deal with threats.

The components of Cloud NGFW Enterprise

Four resources work together:

  • A firewall endpoint is a zonal resource that you associate with a VPC network. It is where inspection happens.
  • A threat prevention security profile defines the action taken for each threat signature.
  • A security profile group holds the security profile. It is the object that firewall rules reference.
  • A firewall policy rule in a hierarchical or global network firewall policy, using the apply_security_profile_group action, is what sends traffic to the endpoint.

Because VPC firewall rules only support allow and deny actions and cannot reference a security profile group, the rules that send traffic for inspection live in firewall policies.

Steering traffic to a firewall endpoint

An endpoint associated with a network does nothing on its own. Traffic only goes to it when a hierarchical or global network firewall policy rule matches the traffic and uses apply_security_profile_group, pointing at the security profile group. Matching traffic is then steered transparently through the endpoint and inspected inline. Ingress rules cover traffic arriving at the matched VMs and egress rules cover traffic leaving them, so inspection in both directions takes rules in both directions.

Coverage is also zonal. An endpoint only inspects traffic for VMs in its own zone, so protection depends on having an associated endpoint in every zone where the protected VMs run.

Threat prevention profiles and severity overrides

The threat prevention security profile decides what happens when traffic matches a signature. Each signature has its own default action, and many lower-severity signatures default to only raising an alert. A profile left at its defaults will therefore record some threats without stopping them.

Severity overrides replace the default actions for an entire severity level in one setting. There are five levels: critical, high, medium, low and informational. A Deny override drops matching threats at that level and still records them in the threat logs. An Alert override records them but lets the traffic continue.

TLS inspection

Encrypted sessions hide their payloads from signature matching. Cloud NGFW Enterprise is the Google-managed option that can decrypt TLS traffic and run intrusion prevention on it, which is what it takes to find threats hidden inside encrypted sessions. The setup has three parts:

  • Deploy a zonal firewall endpoint and associate it with the VPC network.
  • Link a TLS inspection policy that uses a CA pool from Certificate Authority Service. The endpoint acts as a man-in-the-middle for matching sessions, so the VMs must trust that CA.
  • Add a firewall policy rule with the apply security profile group action and TLS inspection enabled. An egress rule of this kind sends outbound HTTPS traffic to the endpoint.

Threat signatures are then checked against the decrypted payload, and malicious sessions can be blocked inline.

How it compares with neighboring services

Several Google Cloud services sit near Cloud NGFW Enterprise, and each covers different ground. Cloud IDS is a detection service that raises alerts rather than blocking traffic inline. Packet Mirroring creates out-of-band copies of packets. Google Cloud Armor protects incoming traffic that reaches backends through a load balancer. Cloud NGFW Standard can block destinations by reputation or domain name, but it does not inspect payloads.

For the Professional Cloud Network Engineer exam, we would associate Cloud NGFW Enterprise with inline, payload-based threat prevention, built from firewall endpoints, a security profile group and firewall policy rules that apply it, with TLS inspection added when the payloads are encrypted.

Our Professional Cloud Network Engineer practice exams cover Cloud NGFW Enterprise alongside network firewall policies and Google Cloud Armor, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow