Topic starter
20/08/2026 5:38 pm
TL;DR: Delegated customer identity shifts customer authentication from a human login problem to a software-actor problem, Ory reports, as machine-paced commerce tests old IAM assumptions. Identity systems need separate rules for human authority, machine execution, and delegated scope before agent traffic reaches production.
Editorial analysis by NHI Mgmt Group, based on content published by Ory: “AI Agents are the New Customer: Is Your Authentication Ready?”.
Key questions
Q: When does customer authentication fail in agent-driven commerce?
A: It fails when controls assume a person is present to complete the flow.
Q: What are the signs that AI agents are overloading customer identity controls?
A: Look for abnormal retry rates, excessive token issuance, sudden bursts of authenticated transactions, and audit logs that cannot explain who initiated the action versus who benefited from it.
Q: How should security teams authenticate AI agents in enterprise environments?
A: Use the strongest method the environment can support while keeping access short-lived and scoped.
Practitioner guidance
- Define the customer delegate model Specify when an AI agent is acting for a customer, what authority it inherits, and which actions require separate approval or fresh consent.
- Separate human and machine credentials Avoid collapsing customer sign-in and agent execution into one credential path.
- Bound delegated transaction scope Limit the actions, spend, and data access that a customer-authorised agent can exercise so token misuse does not become full account misuse.
Bottom line: AI agents change customer identity from a human login problem into a delegated software-actor problem.
Glossary terms: Delegated Customer Identity, Customer identity assurance, Machine-to-Machine Communication, Delegated Action Governance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
20/08/2026 6:23 pm
Customer identity is no longer automatically human identity: once software begins acting as the shopper, the customer IAM model has to distinguish principal, delegate, and beneficiary. That separation matters because authentication no longer proves who is clicking, only which actor is authorised to act. The implication is that customer identity architecture now has to govern delegation explicitly, not assume it.
A few things that frame the scale:
- Gartner predicts that more than 50% of successful cyberattacks against AI agents through 2029 will exploit access control weaknesses.
A question worth separating out:
Q: What is the difference between customer identity and delegated software identity?
A: Customer identity identifies the human principal who owns the relationship. Delegated software identity identifies the system that is allowed to act within that relationship on the customer’s behalf. The difference matters because the delegate should have narrower, revocable authority, while the customer retains the underlying relationship and accountability.
👉 Read our full editorial: AI agents force customer identity design beyond human login assumptions
This post was modified 4 days ago by NHI Mgmt Group