<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>HelixIAM Blogs</title>
    <link>https://helixiam.com/blogs/</link>
    <atom:link href="https://helixiam.com/blogs/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Technical articles from the HelixIAM team at KubeDNA on AI-agent identity, on-behalf-of delegation, workload identity, key custody and self-hosted IAM.</description>
    <language>en</language>
    <lastBuildDate>Fri, 30 Oct 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>How to give AI agents their own identity: ownership, lifecycle and on-behalf-of delegation</title>
      <link>https://helixiam.com/blogs/ai-agent-identity-ownership-delegation/</link>
      <guid isPermaLink="true">https://helixiam.com/blogs/ai-agent-identity-ownership-delegation/</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>Shared API keys cannot tell you which agent acted, for whom, or how to stop it. The building blocks of real agent identity: an accountable owner, a lifecycle, RFC 8693 delegation that only narrows, suspension and audit.</description>
      <dc:creator>HelixIAM team, KubeDNA</dc:creator>
      <category>AI agents</category>
      <category>Delegation</category>
      <category>RFC 8693</category>
      <category>MCP</category>
      <category>Workload identity</category>
    </item>
  </channel>
</rss>
