<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ai-Security on Milgram | Enterprise LLM Firewall | Research Blog</title>
    <link>https://blog.milgram.dev/tags/ai-security/</link>
    <description>Recent content in Ai-Security on Milgram | Enterprise LLM Firewall | Research Blog</description>
    <generator>Hugo -- 0.143.1</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jul 2026 09:00:00 +0200</lastBuildDate>
    <atom:link href="https://blog.milgram.dev/tags/ai-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The First AI-Run Intrusion Was a Visibility Failure</title>
      <link>https://blog.milgram.dev/first-ai-run-intrusion-visibility-failure/</link>
      <pubDate>Wed, 29 Jul 2026 09:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/first-ai-run-intrusion-visibility-failure/</guid>
      <description>A frontier-model evaluation produced an autonomous intrusion. The new reports show why agent traffic needs containment, monitoring and session-level evidence.</description>
    </item>
    <item>
      <title>Prompt Injection Is the SQL Injection of the AI Era</title>
      <link>https://blog.milgram.dev/prompt-injection-sql-injection-ai-era/</link>
      <pubDate>Wed, 22 Jul 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/prompt-injection-sql-injection-ai-era/</guid>
      <description>Prompt injection now tops the OWASP LLM risks and can&amp;rsquo;t be patched away like SQLi. Enterprises need a control layer at the AI traffic boundary.</description>
    </item>
    <item>
      <title>Turning Data-Leak Risk Into a Metric Your Board Understands</title>
      <link>https://blog.milgram.dev/data-leak-risk-as-a-metric/</link>
      <pubDate>Wed, 10 Jun 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/data-leak-risk-as-a-metric/</guid>
      <description>Reframes AI data-leak exposure as a board-level metric, using 2025 breach data to argue for a control layer at the AI traffic boundary.</description>
    </item>
    <item>
      <title>The Cost of Context: Why Bigger Prompts Aren’t Better</title>
      <link>https://blog.milgram.dev/the-cost-of-context/</link>
      <pubDate>Wed, 20 May 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/the-cost-of-context/</guid>
      <description>Longer prompts cost more and answer worse; the fix is treating the AI traffic boundary as a control layer that trims context.</description>
    </item>
  </channel>
</rss>
