Il prossimoProssima guida
Strumenti di progettazione per agenti LLM
Tecnico
GUIDA TECNICA
Least privilege gives an AI agent only the identity, data access, tools, and action scope needed for a defined task.
Ascolta questa guidaNarrato dall'IA · ~3 min
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.
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.
Newsletter gratuita
Tre storie verificate sull'IA ogni mattina nei giorni feriali, scritte in un inglese semplice. Gratuito per sempre, senza pubblicità.
Un'email ogni giorno feriale. Disiscriviti con un clic. Non vendiamo né condividiamo mai il tuo indirizzo.
Mettiti alla prova
Feedback immediato su ogni risposta e un certificato condivisibile con un ID verificabile una volta superato un corso.
Sostieni l'istruzione gratuita sull'IA. AI Understanding è un'organizzazione non profit 501(c)(3) — nessun annuncio, nessun paywall, mai. Fai una donazione
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.
The guide defines least privilege across identity, data access, tools, actions, and duration.
The guide says authorization must be enforced by the application and downstream services, not assumed from prompt text.
Microsoft’s guidance gives a task-scoped, read-only collection role as an example for document summarization.
The guide recommends approval or short-lived elevation for high-impact actions.
Microsoft warns that multiple permissions can add up to a broader effective scope than expected.
Continua a imparare
Altre guide selezionate per questo argomento
Il prossimoProssima guida
Strumenti di progettazione per agenti LLM
Tecnico