10,000+IPs per address group
deny(403)At the load balancer
0Terraform runs per update
1List shared by all policies
The short answer

Cloud Armor and OneFirewall are complementary, focused on the WAF layer. Cloud Armor evaluates requests at Google's edge with preconfigured WAF rules, rate limiting, Adaptive Protection and (on Enterprise) Google's own threat intelligence lists. OneFirewall adds an independent attacker list from 290+ organisations, maintained inside an address group that all your policies share.

How Cloud Armor works

Security policies on Google's external load balancers

Google Cloud Armor attaches security policies to backend services behind Google's external Application Load Balancers. Each policy is an ordered list of rules: preconfigured WAF rules based on the OWASP ModSecurity Core Rule Set, custom rules in Common Expression Language, rate limiting, and bot management with reCAPTCHA. Adaptive Protection uses machine learning to spot layer-7 DDoS.

Cloud Armor Enterprise adds threat intelligence lists from Google and address groups: centrally managed IP lists that many policies can reference with evaluateAddressGroup(), updated through the API or gcloud.

  • Enforced at Google's edge, before traffic reaches your backends
  • WAF rules inspect request content; IP lists answer who is asking
  • Address groups require the Enterprise tier and a fixed capacity
  • Updates via API or gcloud apply to every policy that references the group
The integration

An address group the WCF Agent keeps current

The integration uses the documented Cloud Armor Enterprise address group pattern. You create the group and the deny rule once; the WCF Agent maintains the contents.

STEP 1

Create the address group

Create a google_network_security_address_group with purpose CLOUD_ARMOR (google-beta provider). Choose the capacity carefully: it can't be changed later. CLOUD_ARMOR-only groups can hold 10,000+ IPs.

STEP 2

Add the deny rule

In each security policy, add a high-priority rule with evaluateAddressGroup(..., origin.ip) and action deny(403). Behind a CDN, set user_ip_request_headers and match origin.user_ip instead.

STEP 3

Grant the agent access

Give the WCF Agent's service account compute.securityAdmin and compute.networkAdmin, or a narrower custom role.

STEP 4

Automatic sync

The agent adds IPs above your Crime Score threshold with add-items and removes decayed ones with remove-items. Every policy that references the group picks up the change.

What the configuration looks like

# Cloud Armor Enterprise: deny rule referencing the OneFirewall address group
expression = "evaluateAddressGroup('projects/<p>/locations/global/addressGroups/denylist-addresses', origin.ip)"
action     = "deny(403)"      # use origin.user_ip behind a CDN (X-Forwarded-For)

# The WCF Agent keeps the group current without re-running Terraform:
gcloud network-security address-groups add-items denylist-addresses \
  --location global --items "203.0.113.47/32,198.51.100.23/32"
gcloud network-security address-groups remove-items denylist-addresses \
  --location global --items "198.51.100.23/32"     # score decayed

If a project is downgraded from Enterprise, policies that reference address groups become read-only until those rules are removed. Plan the tier before you roll out.

Side by side

Cloud Armor and OneFirewall, capability by capability

CapabilityCloud ArmorOneFirewall
Question it answersDoes this request match a WAF rule, rate limit or DDoS pattern?Is this client a known attacker right now?
IntelligenceGoogle threat intelligence lists (Enterprise)Alliance list from 290+ organisations, partners and a honeynet, independent of Google
Where it livesRules inside each security policyOne address group referenced by all policies
UpdatingTerraform, API or console changesAutomatic add and remove by the WCF Agent; no Terraform run
ScopeGoogle Cloud load balancersThe same list feeds firewalls, Cloudflare, AWS WAF and SIEMs
Behind a CDNorigin.user_ip with trusted headersFully supported in the same deny rule
The added value

What OneFirewall adds to Cloud Armor

A source Google doesn't own

Alliance data comes from members' firewalls, VPNs and servers across many providers, a different view from Google's own lists.

Infrastructure as code without the churn

The address group is declared once in Terraform; its contents change every sync without noisy plans or pipeline runs.

Consistent blocking on hybrid estates

The attacker blocked at Cloud Armor is blocked on your on-prem firewall and your other clouds by the same feed.

Where Cloud Armor is still the right tool
  • Preconfigured WAF rules for SQL injection, XSS and other OWASP risks
  • Adaptive Protection for layer-7 DDoS
  • Rate limiting and reCAPTCHA bot management
  • Google's own threat intelligence lists on the Enterprise tier

Full Terraform examples are in the Cloud Armor integration guide.

FAQ

OneFirewall and Cloud Armor: FAQ

Do I need Cloud Armor Enterprise?

Yes. Address groups with purpose CLOUD_ARMOR are only available to projects enrolled in Cloud Armor Enterprise.

How many IPs can the address group hold?

CLOUD_ARMOR-only groups can hold 10,000 or more IPs with a quota increase; groups that also use DEFAULT are limited to 1,000. Capacity can't be changed after creation.

Do I have to run Terraform for every update?

No. Terraform creates the group and the rule once. The WCF Agent updates the contents through gcloud or the API.

What if my traffic comes through a CDN?

Configure user_ip_request_headers (for example X-Forwarded-For) and match origin.user_ip in the deny rule.

See what Cloud Armor lets through today.

A free Proof of Value runs against your own traffic. Nothing leaves your perimeter.

Start a Free PoV