Agent Identity

NIST's 27 October design tenets answer how much autonomy an agent should have by handing risk thresholds to the deploying organization. OWASP's AISVS already tests much of the machinery, including when a human must approve an irreversible action. Neither document tells you what your thresholds are, or how much escalation a reviewer can absorb before approval becomes habit.

NIST asked in February whether agent identities should be tied to specific hardware, software, or organizational boundaries. The summary of the 614 responses it received records commenters proposing an anchor bound to the artifact that produced the agent, with the SBOM carried as metadata for access decisions.

Cloudflare Wallets and cloudflare.pay give agents a stable identity and a capped stablecoin wallet on the open x402 rail. The open question is accountability: identity attributes an agent to an account, not a person, and prompt-injection purchases go unaddressed.

A2A's move into the Agentic AI Foundation is a hosting change, not a control transfer, and it still leaves enterprise authorization, key-to-org binding, and conformance depth on the buyer.

Model Context Protocol drops its stateful handshake and becomes a stateless protocol, and its new roadmap elevates agent identity to a top-five priority.