Topic starter
04/06/2026 6:50 pm
TL;DR: An IETF Internet-Draft on AI agent authentication introduces AIMS, a reference model that treats agents as workload identities using short-lived credentials, scoped tokens, and runtime authorization, according to Aembit. The real shift is that IAM assumptions built for human sessions and static service identities no longer fit actors that act, delegate, and re-evaluate context at runtime.
Editorial analysis by NHI Mgmt Group, based on content published by Aembit: “AIMS: A Model for AI Agent Identity”.
Key questions
Q: What breaks when AI agents are treated like standard human users?
A: You lose visibility into effective permissions, expected behaviour, and real blast radius.
Q: Why do short-lived credentials matter more for agentic AI than for ordinary apps?
A: Agentic systems can request, use, and discard access inside a narrow runtime window, so long-lived credentials create unnecessary exposure between actions.
Q: How do security teams know if agent authorization is actually working?
A: Authorization is working only if the agent can complete the intended task without gaining unnecessary reach.
Practitioner guidance
- Define agents as governed workload identities Classify each AI agent as a non-human identity and route it through the same inventory, ownership, and lifecycle controls used for other workload identities.
- Replace static credentials with short-lived, scoped access Issue credentials that expire quickly and are limited to a specific task, resource, and delegation context rather than reusing shared API keys.
- Move authorisation checks to runtime Evaluate the agent’s identity, environment, and requested action at the moment of use so policy decisions reflect current context.
Bottom line: AI agent identity is no longer just an authentication problem, because the actor can take actions, call APIs, and delegate authority at runtime.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
04/06/2026 7:04 pm
AIMS formalises the shift from session-centric IAM to workload-centric agent governance. Human identity models assume an interactive subject, while agents initiate actions, call APIs, and continue executing without the cues that IAM was built around. The article is important because it treats that mismatch as a design problem rather than a policy footnote. Practitioners should read AIMS as evidence that agent identity is now a first-class workload discipline.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- According to PwC, 79% of organizations have already adopted AI agents to some degree.
A question worth separating out:
Q: How should security teams handle delegated access when AI agents act on behalf of customers?
A: Security teams should treat delegated access as a separate governance layer, not as a normal login session. Define what the agent can do, how much value it can move, which approvals are required, and how delegation is revoked. Without those boundaries, the agent inherits more authority than the customer intended and fraud risk expands quickly.
👉 Read our full editorial: AIMS and agent identity: why workload models are shifting