Topic starter
14/09/2026 10:09 am
TL;DR: AI agents are now signing in, browsing, and buying through customer sessions at machine speed, and Strivacity argues that legacy CIAM was built for people and partners, not software acting inside accounts. The core issue is not a new identity pattern but a scale and authorization problem that breaks broad session-based access, audit trails, and human-paced review.
Editorial analysis by NHI Mgmt Group, based on content published by Strivacity: “The scaling problem: Why legacy CIAM platforms will struggle with agentic identity management”.
By the numbers:
- Almost 20% of people surveyed had used an AI agent to help or assist with a purchasing decision in the past 3 months.
Key questions
Q: What breaks in CIAM when AI agents can act for customers?
A: What breaks is the assumption that authentication alone defines access.
Q: Why does agentic commerce increase identity risk for customer accounts?
A: Agentic commerce increases risk because the actor performing the transaction may not be the customer who authenticated.
Q: What should security teams do about delegated access across sub-agents?
A: Security teams should require revalidation at each hop in the delegation chain.
Practitioner guidance
- Map delegated customer actions separately from human sessions Inventory where AI agents can already act inside customer accounts and separate those flows from normal human login journeys, consent, and step-up paths.
- Constrain agent permissions to specific transactions Replace broad inherited session access with narrowly scoped authorization that names the exact purchase, account task, or data touch the agent may perform.
- Bind tokens to the acting agent and human principal Require proof-of-possession or equivalent binding so the token cannot be replayed outside the intended agent and the approving customer remains identifiable.
Bottom line: Agentic commerce turns customer accounts into delegated execution environments, which exposes the limits of CIAM models built around human login assumptions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/09/2026 10:10 am
Agentic commerce exposes a customer identity blind spot, not a brand-new identity category: the core problem is that software is now operating inside customer accounts through the same sign-in and session constructs built for people. That means CIAM is being asked to govern delegated machine action while still optimising for human authentication. The implication is that customer identity programmes must distinguish the principal from the actor, not just the session from the login.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should CIAM teams do when customer accounts start using AI agents?
A: Teams should treat AI agents as a distinct actor in the account lifecycle and govern them with explicit delegation, not inherited human access. That means separating customer authentication from agent authorization, limiting permissions to specific tasks, and preserving evidence strong enough for later review. If those controls are missing, customer identity and agent identity are being conflated.
👉 Read our full editorial: Agentic commerce is exposing CIAM limits for customer identity