<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workload-Identity on microsegment.io</title>
    <link>https://microsegment.io/tags/workload-identity/</link>
    <description>Recent content in Workload-Identity on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/workload-identity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The AI Agent Was New. The Trust Failures Were Not.</title>
      <link>https://microsegment.io/post/2026-07-29-ai-agent-intrusion-trust-paths/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-07-29-ai-agent-intrusion-trust-paths/</guid>
      <description>&lt;p&gt;The headline is an autonomous AI agent escaping an evaluation sandbox and compromising Hugging Face production.&lt;/p&gt;&#xA;&lt;p&gt;The security lesson is less exotic.&lt;/p&gt;&#xA;&lt;p&gt;One compromised workload could read credentials. A pod could reach cloud metadata. An overly privileged Kubernetes identity could create privileged pods. A stolen mesh-VPN key could enroll attacker-controlled devices. One shared service-connector credential provided administrative access across multiple clusters.&lt;/p&gt;&#xA;&lt;p&gt;The agent was new. The trust failures were not.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
