<?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>Governance on Milgram | Enterprise LLM Firewall | Research Blog</title>
    <link>https://blog.milgram.dev/tags/governance/</link>
    <description>Recent content in Governance on Milgram | Enterprise LLM Firewall | Research Blog</description>
    <generator>Hugo -- 0.143.1</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Jul 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://blog.milgram.dev/tags/governance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Provider Safety Filters Protect the Provider, Not You</title>
      <link>https://blog.milgram.dev/provider-safety-filters-not-enough/</link>
      <pubDate>Wed, 15 Jul 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/provider-safety-filters-not-enough/</guid>
      <description>Provider safety filters protect the provider, not your data; enterprises need a vendor-neutral control layer at the AI traffic boundary.</description>
    </item>
    <item>
      <title>Shadow AI: What Your Employees&#39; Prompts Send Out</title>
      <link>https://blog.milgram.dev/shadow-ai-what-prompts-send-out/</link>
      <pubDate>Wed, 24 Jun 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.milgram.dev/shadow-ai-what-prompts-send-out/</guid>
      <description>Shadow AI now drives 1 in 5 breaches; the fix is a control layer at the AI traffic boundary, not another usage ban.</description>
    </item>
  </channel>
</rss>
