igc-waf-spike CLOUD RUN · ap-southeast (Sydney)
Imperva for Google Cloud

IGC WAF Spike

A throwaway demo workload sitting behind a Google Cloud regional load balancer, with traffic redirected through Imperva's cloud WAF for inspection before it ever reaches the container.

edge Google Cloud ALB inspection Imperva (PSC) origin Cloud Run · nginx user non-root :8080
01

Request info

client-visible context · refreshed live
02

The request path

💻
Client
Browser issues an HTTPS request
⚖️
Regional ALB
Google Cloud application load balancer
🧩
Service Extension
Traffic extension redirects to WAF
🛡️
Imperva WAF
Inspects via Private Service Connect
📦
Cloud Run
nginx serves this page
03

Try a test attack

The benign button hits /, which bypasses Imperva (straight to Cloud Run) — expect 200. The attack buttons hit /waf, which is routed through Imperva by a path rule on the load balancer — a classic XSS or SQLi probe should be intercepted upstream once the WAF policy is enforcing (watch for a 403 or a connection reset).

Results
No requests fired yet. Pick a button above.