<?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>
    <item>
      <title>API Authentication: API Keys, OAuth 2.0, and JWT Explained</title>
      <link>https://apicourse.com/api-authentication-api-keys-oauth-2.0-and-jwt-explained/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-authentication-api-keys-oauth-2.0-and-jwt-explained/</guid>
      <description>&lt;p&gt;Authentication is where most API integrations go wrong the first time. Not because the concepts are complicated, but because there are several distinct mechanisms in common use, they solve different problems, and developers often reach for the one they recognize rather than the one that fits. Understanding what each mechanism actually does — and what it does not do — is the difference between an integration that works and one that works until it doesn&amp;rsquo;t.&lt;/p&gt;</description>
    </item>
    <item>
      <title>API Security Fundamentals: What Every Developer Needs to Know</title>
      <link>https://apicourse.com/api-security-fundamentals-what-every-developer-needs-to-know/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-security-fundamentals-what-every-developer-needs-to-know/</guid>
      <description>&lt;p&gt;API security failures are not exotic. They rarely involve sophisticated attacks on cryptographic primitives or novel zero-day exploits. The most consequential breaches — the ones that expose millions of records, compromise user accounts, or shut down services — happen because an API allowed something it should not have, at a scale its designers did not anticipate. Understanding the fundamental attack surface of an API and designing against it deliberately is the entire discipline. It is not advanced knowledge. It is the baseline.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CORS Explained: Why Browsers Block API Requests and How to Fix It</title>
      <link>https://apicourse.com/cors-explained-why-browsers-block-api-requests-and-how-to-fix-it/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/cors-explained-why-browsers-block-api-requests-and-how-to-fix-it/</guid>
      <description>&lt;p&gt;CORS is the source of more developer frustration than almost any other browser security mechanism — not because it is poorly designed, but because its error messages are opaque, its rules are non-obvious, and it only manifests in a specific context that server-side developers often do not encounter during development. Understanding what CORS actually is and why it exists transforms it from an arbitrary obstacle into a predictable system with clear rules.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Multi-Tenancy in APIs: Data Isolation, Routing, and Tenant Context</title>
      <link>https://apicourse.com/multi-tenancy-in-apis-data-isolation-routing-and-tenant-context/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/multi-tenancy-in-apis-data-isolation-routing-and-tenant-context/</guid>
      <description>&lt;p&gt;Most SaaS APIs are multi-tenant: the same infrastructure serves many customers, each operating in isolation from the others. A user of Tenant A should never see, modify, or even know about the data of Tenant B. This isolation is the foundational guarantee of a multi-tenant system, and it must hold at every layer of the stack — not just at the query level, but at the API design level, the authentication level, and the operational level.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
