Notifications
Clear all
Topic starter
20/08/2026 5:38 pm
TL;DR: AI agents are moving into customer-facing commerce flows, and Ory argues that authentication, scaling, and machine-to-machine access patterns must be redesigned before custodial bots outnumber human shoppers. The real issue is not whether agents can log in, but whether IAM assumptions still hold when the buyer is a software identity.
NHIMG editorial — based on content published by Ory: AI Agents are the New Customer: Is Your Authentication Ready?
Questions worth separating out
Q: How should security teams govern IAM access for AI agents in AWS?
A: Treat each AI agent as a non-human identity with its own execution role, trust policy, and review cycle.
Q: Why do AI agents complicate identity and access management for retailers?
A: AI agents complicate IAM because they do not behave like a human user or a simple service account.
Q: What breaks when agent sessions are not isolated from each other?
A: Parallel agent runs can overwrite files, reuse context, and leak assumptions if they share state or credentials.
Practitioner guidance
- Define customer agent identity as a governed subject Create a policy that classifies customer-facing AI agents as non-human identities with named owners, approved scopes, and revocation criteria.
- Use short-lived delegated credentials Issue time-bound tokens or equivalent delegated credentials for each transaction or task, and revoke them when the task ends.
- Separate human assurance from agent authority Keep the customer authentication step distinct from the agent's runtime permissions so that a verified person does not automatically create open-ended machine access.
What's in the full article
Ory's full blog covers the operational detail this post intentionally leaves for the source:
- The product and platform context behind Ory Agent IAM and how it maps to machine-to-machine commerce.
- The broader Ory ecosystem touchpoints for CIAM, B2B IAM, and agent security that shape deployment choices.
- The implementation framing for high-volume authentication and permissioning in customer-facing agent workflows.
- The article's own positioning on future-proof IAM design for agentic commerce.
👉 Read Ory's blog on AI agents as customer identities and authentication →
AI agent customer identities: is your authentication ready?
Explore further
20/08/2026 6:23 pm
AI agents are becoming a distinct identity class, not just a new client type. Once a software actor can initiate commerce actions at runtime, the old assumption that the customer is always a person stops holding. That shifts the identity problem from pure CIAM into NHI governance, because the actor now needs credentials, scopes, lifecycle controls, and revocation discipline. Practitioners should treat agent identity as a governance object, not a UI variation.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a persistent behaviour gap across software delivery.
A question worth separating out:
Q: Should organisations create separate policies for AI agents and human users?
A: Yes. Human users, customer agents, and internal service identities have different lifecycle, risk, and assurance requirements. A single policy set usually overgeneralises and either blocks useful automation or leaves software actors over-privileged. Separate policy treatment makes ownership, scope, and auditability much clearer.
👉 Read our full editorial: AI agents are becoming customer identities, and IAM must adapt
