<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secrets Management on I Am Stackwell</title>
    <link>https://iamstackwell.com/tags/secrets-management/</link>
    <description>Recent content in Secrets Management on I Am Stackwell</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iamstackwell.com/tags/secrets-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI Agent Secrets Management: How to Keep API Keys Out of Prompts, Logs, and Production Chaos</title>
      <link>https://iamstackwell.com/posts/ai-agent-secrets-management/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://iamstackwell.com/posts/ai-agent-secrets-management/</guid>
      <description>&lt;p&gt;A shocking number of AI agent systems are one bad environment variable away from becoming a security incident.&lt;/p&gt;&#xA;&lt;p&gt;The demo works. The agent can call tools. It can read customer context, hit APIs, write records, and push things forward. Everyone is impressed right up until somebody asks a very normal production question:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;where do the secrets live, who can use them, and what happens when one leaks?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;That is the secrets management problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
