<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai-Security on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/ai-security/</link>
    <description>Recent content in Ai-Security on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 31 Oct 2026 12:30:00 +0100</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/ai-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Is the WAF Obsolete?</title>
      <link>https://linuxeries.org/post/2026-10-31-is-the-waf-obsolete/</link>
      <pubDate>Sat, 31 Oct 2026 12:30:00 +0100</pubDate>
      <guid>https://linuxeries.org/post/2026-10-31-is-the-waf-obsolete/</guid>
      <description>&lt;p&gt;No. But the version of the WAF most organizations are running — a signature-matching appliance at the perimeter — is being bypassed in real time by actors who no longer need to be creative. They need to be persistent, and they need an API key.&lt;/p&gt;&#xA;&lt;p&gt;This post looks at what &amp;ldquo;obsolete&amp;rdquo; actually means in 2026, using four specific incidents from the last five months and one academic paper that quantifies the problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
