Wildcards are now GA from us for network egress on GCP.
Took time to develop since we didn't want the solution to be trivially bypassable with SNI Spoofing [1] or cause interruptions to your traffic intermittently with false positives (as is the case with known issue FWAAS-1501 of Palo Alto [2]). The mechanism under the hood is truly patent worthy!
The integration with GCP has always been such that it mimics a built-in feature with use of Network Tags, Firewall Rules and Logs Explorer 😎. It is stateless, CIS-hardened, upgrades seamlessly, and you can see the full comparison [3] for more info on multi-protocol support, low TTL DNS handling, etc.
It also has a non-blocking monitoring mode to discover what you need to allow, and a dry-run mode to test rules before enforcement.
Search for DiscrimiNAT Firewall in GCP Console to get started or for links to our Terraform modules and website for docs, etc.
Any questions, just drop an email to devsecops at chasersystems dot com. We love to answer tricky questions and demo how our firewall checks more than just the hostname in client-settable headers!
Safe egressing 🤞
[1a] https://repost.aws/questions/QUGi6L4x4nRsCYc_FJ9aQkiQ/prevent-aws-network-firewall-host-header-spoofing
[1b] https://x.com/nullenc0de/status/1159805999332638720
[2] https://docs.paloaltonetworks.com/cloud-ngfw-aws/release-notes/cloud-ngfw-known-issues
[3] https://chasersystems.com/discriminat/comparison/gcp-ngfw-standard/