<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OWASP on API Course</title>
    <link>https://apicourse.com/tags/owasp/</link>
    <description>Recent content in OWASP on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/owasp/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
