概述
It limits the impact of mistakes or prompt injection, but must be enforced by the application and downstream services rather than assumed from a system prompt.
深入探討
Least privilege is the principle of granting only the permissions required for a task, to the identity that performs it, for the needed duration. For AI agents, the permission boundary should cover more than the model’s tool list: it includes credentials, data collections, external services, writable resources, and the actions available through each connector. A prompt that says “do not delete files” does not prevent a tool call from deleting them if the identity still has that authority. Microsoft’s current guidance for AI agents recommends unique identities, documented purpose and data access, review of effective aggregate permissions, allowlisting tools, and auditing agent actions. It describes scoped read roles for document summarization, separate read and write roles for ticket workflows, and time-limited elevation or approval gates for remediation. These are Microsoft implementation recommendations, but the underlying principle applies across systems: enforce authorization at the tool and downstream service, not only in the orchestration prompt. Start with the smallest useful tool set and resource scope. Separate read and write functions where possible; require explicit approval for destructive, financial, or broad actions. Use short-lived credentials for elevated work, maintain a way to revoke access quickly, and review permissions when data, tools, or workflows change. Log which principal acted and what the downstream system authorized. Least privilege reduces blast radius; it does not prove the agent’s judgment is correct or stop every form of data disclosure. Combine it with input handling, output validation, testing, monitoring, and human confirmation for sensitive operations.
現實世界的實施
A document summarizer receives read-only access to one approved collection instead of broad access to a tenant’s files.
A ticketing assistant can create or update a case but cannot delete records or change administrator roles.
An agent that performs remediation receives temporary, approved access to a named resource group rather than standing subscription-wide rights.
A team logs the agent identity, effective scope, tool, action, target resource, and approval context for each consequential operation.
The Future of Least Privilege for LLM Agents
As organizations deploy more agents, identity and permission governance will need to cover their owners, lifecycles, credentials, tools, and downstream actions. Automated inventory and access reviews can help find permission creep, but teams must still decide which task requires which capability. Expect least-privilege controls to become part of routine agent deployment and incident response. Fast revocation and audit trails will matter as agents use more connectors and act across systems. Permissions should be revisited when a task or data source changes.
付諸實踐
為什麼這很重要
- 成本與預算. 多年來,架構決策決定著效能和營運成本。
- 更明確的決策. 技術教育幫助團隊選擇正確的堆疊,而不僅僅是最新的堆疊。
- 品質管控. 更好的工程選擇可以減少生產中的可靠性事故。
留意
- 優化一項基準測試可以隱藏更廣泛的系統弱點。
- 基礎設施和維護成本常常被低估。
- 隨著系統變得更加複雜,安全性和可觀察性差距可能會擴大。
後續步驟
- 在實施之前定義延遲、品質和成本目標。
- 在實際負載和資料條件下進行基準測試。
- 儀器監控錯誤、漂移和使用者影響。
- 在擴展之前準備回滾和事件回應路徑。
不斷探索
常見問題
What is Least Privilege for LLM Agents?
Least privilege gives an AI agent only the identity, data access, tools, and action scope needed for a defined task. It limits the impact of mistakes or prompt injection, but must be enforced by the application and downstream services rather than assumed from a system prompt.
最小權限對於人工智慧代理意味著什麼?
該指南定義了身分、資料存取、工具、操作和持續時間的最低權限。
為什麼系統提示「不要刪除檔案」本身不夠?
該指南表示,授權必須由應用程式和下游服務強制執行,而不是根據提示文字進行假設。
哪種權限集適合文件摘要器?
Microsoft 的指南給出了任務範圍的唯讀收集角色作為文件摘要的範例。
代理程式如何在降低常設權限的情況下執行敏感寫入操作?
該指南建議批准或短期提升高影響力的行動。
為什麼要審查跨角色和服務的聚合權限?
Microsoft 警告多個權限加起來的有效範圍可能比預期更廣泛。