u/Comfortable_Meal_808

Best way to verify actual WAF blocking mode across AWS, Azure, and Cloudflare?

Been running WAF governance for AWS, Azure, Cloudflare and one old enterprise WAF, and we have this weird gap rn. Infra and app teams own their stacks, our central view is basically a spreadsheet that says which app has a WAF resource, not which one is actually in blocking mode with sane rules and no direct to origin bypass. we have a big WAF coverage review coming up and I'm kind of stressed. Cloud consoles tell me what's deployed, but that misses monitor only mode, config drift, origin still exposed on old hostnames, forgotten dns etc. I want to switch to an outside in test for our internet facing apps, and classify stuff as protected or underprotected or flat out unprotected, then rerun whenever someone migrates or changes configs. How are you verifying blocking behavior, catching direct to origin bypasses, and turning that into a defensible WAF coverage percent that leadership wont laugh at? any hints?

reddit.com
u/Comfortable_Meal_808 — 16 days ago