<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Behavioral-Security on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/behavioral-security/</link>
    <description>Recent content in Behavioral-Security on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Nov 2026 09:52:48 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/behavioral-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NGWAF: From Static Rules to Behavioral, API-Aware Protection</title>
      <link>https://linuxeries.org/post/2026-11-18-ngwaf-from-static-rules-to-behavioral-api-awa/</link>
      <pubDate>Wed, 18 Nov 2026 09:52:48 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-18-ngwaf-from-static-rules-to-behavioral-api-awa/</guid>
      <description>&lt;h2 id=&#34;from-static-rules-to-behavioral-apiaware-protection&#34;&gt;From Static Rules to Behavioral, API‑Aware Protection&lt;/h2&gt;&#xA;&lt;p&gt;NGWAFs have been the go‑to shield against the OWASP Top‑10 for years. Back in 2025, most of us were still clinging to static signatures—regexes, hard‑coded SQL‑injection patterns, and a handful of known payloads. Those rules hold up for monolithic sites, but when you start juggling dozens of micro‑services that talk over HTTP/HTTPS, they become a maintenance nightmare and a weak point in the chain.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
