<?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 Governance on Yogesh Thanvi</title>
    <link>https://yogeshthanvi.com/tags/ai-governance/</link>
    <description>Recent content in AI Governance on Yogesh Thanvi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yogeshthanvi.com/tags/ai-governance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Engineering Trust: Building Systems That Prove Compliance Continuously</title>
      <link>https://yogeshthanvi.com/posts/engineering-trust/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/engineering-trust/</guid>
      <description>In cloud-native and AI-driven systems, compliance can no longer be a periodic activity. It has to be continuously demonstrated. Here is the architecture for engineering that trust.</description>
    </item>
    <item>
      <title>Securing AI Workloads on Azure: Governance Patterns for Azure OpenAI and AI Foundry</title>
      <link>https://yogeshthanvi.com/posts/securing-ai-workloads-on-azure/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/securing-ai-workloads-on-azure/</guid>
      <description>Generative AI on Azure introduces control points that traditional application security never had to handle. Here are practical governance patterns for Azure OpenAI and AI Foundry workloads, mapped to where the real risks live.</description>
    </item>
  </channel>
</rss>
