<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Least Privilege on Stack Research</title><link>https://stackresearch.org/tags/least-privilege/</link><description>Recent content in Least Privilege on Stack Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 29 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stackresearch.org/tags/least-privilege/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent Security Is a Release Engineering Problem</title><link>https://stackresearch.org/research/agent-security-is-a-release-engineering-problem/</link><pubDate>Sun, 29 Mar 2026 00:00:00 +0000</pubDate><guid>https://stackresearch.org/research/agent-security-is-a-release-engineering-problem/</guid><description>&lt;p&gt;On Tuesday, the agent reads a note.&lt;/p&gt;
&lt;p&gt;The note may be a webpage, a support transcript, a tool result, a migration record, or a line in a document somebody thought was harmless. Nothing dramatic happens. The session ends. The operator closes the tab. The team ships two other changes before lunch: a prompt tweak, a small retrieval adjustment, a new tool scope for a staging workflow.&lt;/p&gt;
&lt;p&gt;On Friday, the same system takes a different task. It answers a planning question, prepares a runbook, suggests a deployment path, or reaches for a tool under a credential it did not have on Tuesday. What matters is not the moment the bad state entered. What matters is that it survived.&lt;/p&gt;</description></item><item><title>NHI and Agentic Risk: Least Privilege Meets Least Agency</title><link>https://stackresearch.org/research/nhi-asi-series-02-least-privilege-least-agency/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://stackresearch.org/research/nhi-asi-series-02-least-privilege-least-agency/</guid><description>&lt;p&gt;A tool can look small from the agent&amp;rsquo;s side and be large from the identity side.&lt;/p&gt;
&lt;p&gt;The interface says &lt;code&gt;lookup_order&lt;/code&gt;. The agent sees a narrow verb: retrieve the order, summarize the status, maybe explain why a shipment is late. Underneath that verb, a service account authenticates to the CRM. It can read orders, update customer records, issue refunds, change shipping addresses, and export account history because those scopes made the first integration easy to ship.&lt;/p&gt;</description></item></channel></rss>