We tested our own WAF with frontier AI models. Here’s what we found
From the source: Cloudflare BlogWe built a WAF tester that adapted each request based on what the WAF blocked or passed. This helped us explore variations that a fixed test might miss. We ran it across six attack categories on an authorized staging environment and discovered detection gaps worth fixing. Here’s how the loop worked, what got through, and what we did about it.
Read the full story on Cloudflare BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Security
How are you securing employee use of generative AI tools?
Blocking, allow-listing, DLP, enterprise licences, policy and training: what combination is working in practice?
Which security investments are you prioritising for FY27?
Identity, cloud security posture, AI security, SOC automation, resilience? Share your top two and why.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from Cloudflare
Recent updates from Cloudflare, so you can tell whether this is a one-off or part of a pattern.
More in Security
What other companies in Security are doing. The category page shows who’s active, side by side.

