<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets on Stack Research</title><link>https://stackresearch.org/tags/secrets/</link><description>Recent content in Secrets on Stack Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stackresearch.org/tags/secrets/index.xml" rel="self" type="application/rss+xml"/><item><title>NHI and Agentic Risk: Secrets, Memory, and Persistence</title><link>https://stackresearch.org/research/nhi-asi-series-03-secrets-and-memory/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://stackresearch.org/research/nhi-asi-series-03-secrets-and-memory/</guid><description>&lt;p&gt;A secret leak is not a single event. It is a copying process.&lt;/p&gt;
&lt;p&gt;A token appears in a CI log. The log is indexed for troubleshooting. An agent is asked to diagnose a failed deployment and retrieves the log. The agent summarizes the failure, stores the useful parts in memory, and later uses that memory while calling a tool. By then the token may have moved through several systems that were never designed to be secret stores.&lt;/p&gt;</description></item></channel></rss>