<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Edge Security on Cyber Mixology</title>
    <link>https://sedward5.com/tags/edge-security/</link>
    <description>Recent content in Edge Security on Cyber Mixology</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sedward5.com/tags/edge-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>You Can&#39;t Sigma a Buffer Overflow: Post-Exploitation Detection for CVE-2026-0300</title>
      <link>https://sedward5.com/pan-os-post-exploitation-detection/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sedward5.com/pan-os-post-exploitation-detection/</guid>
      <description>&lt;p&gt;Zero-days are designed to be invisible. A buffer overflow in a network appliance doesn&amp;rsquo;t show up in your SIEM. It doesn&amp;rsquo;t spawn a suspicious process. It doesn&amp;rsquo;t drop a file in a temp directory. It exploits a parsing mistake in memory, at a layer your detection tooling was never designed to see.&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s the honest truth about CVE-2026-0300 — a critical unauthenticated RCE in the PAN-OS User-ID Authentication Portal, disclosed by Palo Alto Networks Unit 42 on May 6, 2026. You cannot write a Sigma rule that catches the initial exploit. The vulnerability lives in nginx memory on the firewall appliance itself. Standard log sources simply don&amp;rsquo;t reach there.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
