You can use the URL filtering service to filter your workload traffic by using domain and Server Name Indication (SNI) information available in the egress HTTP(S) messages. For more information, see URL filtering service overview. This feature is available in General Availability.
]]>Secure tags with a purpose-data attribute specifying a VPC network or an
organization now support VPC networks that are connected using VPC Network
Peering. For more information, see
Secure tags for firewalls.
This feature is available in General Availability.
You can use network contexts to meet your security goals by using fewer firewall policy rules more efficiently. For more information, see Network contexts. This feature is available in General Availability.
]]>Cloud NGFW now supports regional system firewall policies. Regional system firewall policies are read-only policies that internal Google services, such as Google Kubernetes Engine, use to secure their operations within a VPC network. For more information, see Regional system firewall policies. This feature is available in General Availability.
]]>You can now create regional firewall policies that apply to managed Envoy proxies used by internal Application Load Balancers and internal proxy Network Load Balancers. For more information, see Use regional network firewall policies to protect internal Application Load Balancers and internal proxy Network Load Balancers. This feature is available in Preview.
]]>You can create a Remote Direct Memory Access (RDMA) over converged ethernet (RoCE) Virtual Private Cloud (VPC) network and configure firewall rules that apply to the network. For more information, see Cloud NGFW for RoCE VPC networks. This feature is available in General Availability.
]]>You can create a firewall endpoint that supports jumbo frames up to 8,500 bytes in size. For more information, see Supported packet size. This feature is available in General Availability.
]]>You can use the URL filtering service to filter your workload traffic by using domain and Server Name Indication (SNI) information available in the egress HTTP(S) messages. For more information, see URL filtering service overview. This feature is available in Preview.
]]>You can create a secure tag at the organization level and bind its value to all virtual machine (VM) instances across that organization. For more information, see Secure tags for firewalls. This feature is available in General Availability.
]]>You can create a Remote Direct Memory Access (RDMA) over converged ethernet (RoCE) Virtual Private Cloud (VPC) network and configure firewall rules that apply to the network. For more information, see Cloud NGFW for RoCE VPC networks. This feature is available in Preview.
]]>You can create a secure tag at the organization level and bind its value to all virtual machine (VM) instances across that organization, instead of applying tags to instances within a specific network. For more information, see Secure tags for firewalls. This feature is available in Preview.
]]>You can use a single request to batch update all the firewall policy rules for hierarchical and network firewall policies. For more information, see Overview of batch update to firewall policy rules. This feature is available in General Availability.
]]>You can use network contexts to meet your security goals by using fewer firewall policy rules more efficiently. This feature is available in Preview. For more information, see Network contexts.
]]>You can use custom constraints to provide more granular and customizable control over specific fields for firewall policy resources. For more information, see Manage firewall policy resources by using custom constraints. This feature is available in General Availability.
]]>Starting April 9, 2024, you will be charged for the Cloud NGFW Enterprise feature—intrusion prevention service. For more information about billing, see Cloud NGFW pricing.
Cloud Firewall in Google Cloud is now Cloud Next Generation Firewall (NGFW). For more information, see Cloud NGFW.
Cloud NGFW Enterprise, including the intrusion prevention service, is available in General Availability. Use intrusion prevention service to safeguard your workload traffic from threats such as malware, spyware, and command-and-control attacks.
]]>Starting September 30, 2023, you will be charged for the Cloud Firewall Standard feature—fully qualified domain name (FQDN) objects. For more information about billing, see Cloud Firewall pricing.
]]>You can use fully qualified domain name (FQDN) objects in firewall policy rules to filter incoming or outgoing traffic from specific domain names. This feature is available in General Availability.
]]>Starting September 8, 2023, you will be charged for the following Cloud Firewall Standard features:
For more information about billing, see Cloud Firewall pricing.
]]>You can use intrusion prevention service to safeguard your workload traffic from threats such as malware, spyware, and command-and-control attacks. This feature is available in Preview.
]]>You can use custom constraints to provide more granular and customizable control over specific fields for VPC firewall rule resources. For more information, see Manage firewall resources by using custom constraints. This feature is available in Preview.
]]>Address groups are a logical collection of either IPv4 address ranges or IPv6 address ranges in CIDR format. You can use address groups to define consistent sources or destinations referenced across multiple rules in the same or different firewall policies. This feature is available in General Availability.
]]>Use Threat Intelligence for firewall policy rules to secure your network by allowing or blocking traffic based on threat intelligence data. This feature is available in General Availability.
Use Geo-location objects in firewall policy rules to filter external IPv4 and external IPv6 traffic based on specific geographic locations or regions. This feature is available in General Availability.
]]>General Availability: You can specify the source IP ranges for egress firewall rules and the destination IP ranges for ingress firewall rules.
]]>