<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api Security on API Course</title>
    <link>https://apicourse.com/tags/api-security/</link>
    <description>Recent content in Api Security on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/api-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cloudflare Used AI to Attack Its Own WAF and Found 49 Gaps, Mostly SSRF</title>
      <link>https://apicourse.com/cloudflare-used-ai-to-attack-its-own-waf-and-found-49-gaps-mostly-ssrf/</link>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/cloudflare-used-ai-to-attack-its-own-waf-and-found-49-gaps-mostly-ssrf/</guid>
      <description>&lt;p&gt;Cloudflare just published the results of an experiment that every API developer should read, even if you&amp;rsquo;ll never run a firewall. The company put frontier AI models inside a test harness and told them to get past its own Web Application Firewall.&lt;/p&gt;&#xA;&lt;p&gt;They found gaps. Not many, but the pattern of what got through is the real lesson.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-cloudflare-did&#34;&gt;What Cloudflare did&lt;/h2&gt;&#xA;&lt;p&gt;The test started with attack payloads the WAF already blocked. Instead of replaying a fixed list, the models looked at how each attempt was handled and proposed a tweak for the next one: different encoding, different placement in the request, different delivery. They had no access to the WAF rules or source code. Pure black box.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
