core-concept · Security & governance · emerging · Reviewed

Agent identity & delegated authority

The identity and authorization discipline that treats an enterprise agent as a non-human principal with attributable, purpose-bound, time-bound permissions.

Definition

The identity and authorization discipline that treats an enterprise agent as a non-human principal with attributable, purpose-bound, time-bound permissions. Every consequential agent action needs a principal, a delegator, a purpose, a policy decision, and an expiry.

IAM foundations are established; agent-specific standards and profiles are still developing.

Why it matters

Every consequential agent action needs a principal, a delegator, a purpose, a policy decision, and an expiry.

The operating shift is from “Borrowed user credentials” to “Explicit non-human authority.”

System anatomy

Practice 1
Bind authority to action, resource, purpose, and time
Practice 2
Preserve the human or service delegation chain
Practice 3
Expire or suspend agents without a valid owner

Important distinctions

Borrowed user credentials
This concept moves the engineering system toward explicit non-human authority.

Implementation signals

  • Bind authority to action, resource, purpose, and time
  • Preserve the human or service delegation chain
  • Expire or suspend agents without a valid owner

Failure modes

  • Agents impersonating users
  • Permissions surviving ownership or purpose changes

Sources and further study

  1. NIST NCCoE — Identity and Authority for Software Agents concept paper

    A concept paper exploring how established identity and authorization practices can apply to software and AI agents.

    Use in this library: Official guidance. Guidance describes recommended practice; citation does not prove that a control is implemented or effective in a particular environment.

    guidance · guidance · Published 2026-02-05
  2. NIST — AI Agent Standards Initiative

    A standards initiative addressing secure, interoperable adoption of AI agents.

    Use in this library: Official guidance. Guidance describes recommended practice; citation does not prove that a control is implemented or effective in a particular environment.

    guidance · guidance · Published 2026-02-17
  3. Model Context Protocol — Enterprise-Managed Authorization for MCP

    An emerging authorization pattern for enterprise-managed agent access to MCP servers.

    Use in this library: Standard or protocol. A specification defines an interface or control pattern; conformance alone does not establish authorization, security, or fitness for a use case.

    protocol · protocol · Published 2026-06-18