---
schema_version: "newruntime-agent-readable-v0.2"
type: "tectonic_shift"
stable_id: "tectonic_shift:delegated-agent-identity"
slug: "delegated-agent-identity"
title: "Borrowed human credentials -> delegated agent identity"
description: "Autonomous agents are moving from borrowed user sessions and shared keys toward distinct identities with scoped authority, sponsors, expiry, and audit."
retrieval_nugget: "Autonomous agents are moving from borrowed user sessions and shared keys toward distinct identities with scoped authority, sponsors, expiry, and audit. Before: Agents borrow human sessions, shared API keys, or generic service accounts After: Each agent has scoped identity, delegation mode, sponsor, expiry, revocation, and audit Current stage: emerging; confidence is high."
status: "published"
before_state: "Agents borrow human sessions, shared API keys, or generic service accounts"
after_state: "Each agent has scoped identity, delegation mode, sponsor, expiry, revocation, and audit"
stage: "emerging"
confidence: "high"
magic_decay_stage: "fragile-tool"
first_seen: "2026-02-05"
last_verified: "2026-07-29"
record_date: "2026-07-29"
date_kind: "last_verified"
related_posts: ["mcp-oauth-authorization-boundary"]
topics: ["agent-identity","access-control","ai-security","enterprise-agents"]
source_urls: ["https://www.nccoe.nist.gov/sites/default/files/2026-02/accelerating-the-adoption-of-software-and-ai-agent-identity-and-authorization-concept-paper.pdf","https://learn.microsoft.com/en-us/entra/agent-id/agent-identities","https://learn.microsoft.com/en-us/entra/agent-id/authorization-agent-id","https://aws.amazon.com/about-aws/whats-new/2026/07/oauth-aws-mcp-server/","https://blog.cloudflare.com/temporary-accounts/"]
routes: {"html":"https://newruntime.com/shifts/delegated-agent-identity/","markdown":"https://newruntime.com/shifts/delegated-agent-identity.md","json":"https://newruntime.com/shifts/delegated-agent-identity.json"}
source_format: "markdown"
---

# Borrowed human credentials -> delegated agent identity

## Retrieval answer

Autonomous agents are moving from borrowed user sessions and shared keys toward distinct identities with scoped authority, sponsors, expiry, and audit. Before: Agents borrow human sessions, shared API keys, or generic service accounts After: Each agent has scoped identity, delegation mode, sponsor, expiry, revocation, and audit Current stage: emerging; confidence is high.

Agents are beginning to appear as distinct actors in identity and access
systems instead of borrowing a human account or disappearing behind a shared
service credential. The durable boundary is becoming delegated authority:
which agent acted, for whom, within which scope, and who remains accountable.

## What is changing?

An agent identity can separate three things that ordinary credentials often
collapse:

- the human or organization that authorizes and sponsors the work;
- the non-human actor that plans and executes it;
- the temporary authority granted for one role, task, resource, or period.

This makes model choice independent from operational accountability. The model
or runtime can be replaced while permissions, consent, ownership, revocation,
and audit stay attached to the same organizational principal.

## Evidence

NIST's agent identity project explicitly calls for access systems to
distinguish agent and human identities, link users to agents for delegation
and accountability, and record the actions and outcomes of non-human
entities.

Microsoft Entra Agent ID implements a dedicated agent principal with unique
identifiers, an accountable human sponsor, delegated and autonomous token
modes, and agent-specific restrictions on high-risk permissions. AWS now lets
MCP agents use interactive or headless OAuth while retaining IAM policies,
token introspection, revocation, dynamic client registration, and CloudTrail
audit events.

Cloudflare's temporary agent accounts demonstrate the short-lived end of the
same shift: an agent can receive disposable authority to deploy and verify
work, after which the account is claimed by a human or expires automatically.

## Counter-evidence

Workload identities, service principals, short-lived credentials, and OAuth
already solve parts of this problem. Agent identity products may remain a
vendor-specific relabeling of existing IAM rather than a new interoperable
layer. Per-agent principals can also create identity sprawl.

## Revision trigger

Revise this shift if ordinary service accounts and standard OAuth consistently
provide agent-level attribution, human sponsorship, delegation mode,
least-privilege scopes, expiry, revocation, and audit without agent-specific
identity primitives.