<?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>Thu, 12 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Signing tokens with keys that never leave the HSM: HelixIAM tested with Thales Luna Cloud HSM</title>
      <link>https://helixiam.com/blogs/signing-tokens-keys-never-leave-hsm-thales-luna/</link>
      <guid isPermaLink="true">https://helixiam.com/blogs/signing-tokens-keys-never-leave-hsm-thales-luna/</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>Many European public bodies and banks keep their keys in HSMs. What High assurance key custody does in HelixIAM, how we tested it with a Thales Luna Cloud HSM, the signing times we measured and how the setup works.</description>
      <dc:creator>HelixIAM team, KubeDNA</dc:creator>
      <category>HSM</category>
      <category>Key custody</category>
      <category>Thales Luna</category>
      <category>PKCS#11</category>
      <category>Sovereignty</category>
    </item>
    <item>
      <title>DigiD, eHerkenning and eIDAS for platform builders: what a connector does and what you still arrange</title>
      <link>https://helixiam.com/blogs/digid-eherkenning-eidas-platform-builders/</link>
      <guid isPermaLink="true">https://helixiam.com/blogs/digid-eherkenning-eidas-platform-builders/</guid>
      <pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate>
      <description>A connector turns DigiD, eHerkenning and eIDAS into standard sign-in for your applications. It does not replace your agreement with Logius or a broker. What the connectors do, which part stays with you, and how to evaluate them.</description>
      <dc:creator>HelixIAM team, KubeDNA</dc:creator>
      <category>DigiD</category>
      <category>eHerkenning</category>
      <category>eIDAS</category>
      <category>Public sector</category>
      <category>Federation</category>
    </item>
    <item>
      <title>Self-hosted IAM in Europe: what “sovereign” really means for your keys and data</title>
      <link>https://helixiam.com/blogs/self-hosted-iam-europe-sovereign-keys-data/</link>
      <guid isPermaLink="true">https://helixiam.com/blogs/self-hosted-iam-europe-sovereign-keys-data/</guid>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
      <description>Sovereignty is not a hosting label. It comes down to who runs the software, where the data lives and who holds the signing keys. Three key-custody profiles, per-tenant isolation and what you still arrange yourself.</description>
      <dc:creator>HelixIAM team, KubeDNA</dc:creator>
      <category>Sovereignty</category>
      <category>Key custody</category>
      <category>HSM</category>
      <category>Self-hosted</category>
      <category>Multi-tenancy</category>
    </item>
    <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>
