Notifications
Clear all
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.
NHIMG editorial — based on content published by Strivacity: Agentic commerce and the identity model for AI agents in customer accounts
By the numbers:
- 20% of people surveyed had used an AI, d an AI agent to help or assist with a purchasing decision in the past 3 months.
- 38% of US consumers have used GenAI for online shopping, and 52% plan to.
- 97% of enterprise leaders expect a material AI-agent-driven security or fraud incident within the next 12 months.
Questions worth separating out
Q: How should teams govern AI agents that act inside customer accounts?
A: Treat them as delegated non-human identities, not as ordinary customer sessions.
Q: When does session inheritance become unsafe for AI agents?
A: Session inheritance becomes unsafe when software can use the same credentials to make decisions, change context, or execute transactions without fresh authorization.
Q: What are the best controls for auditing agentic commerce?
A: Use identity records that preserve the agent identity, the user principal, the exact scope granted, and the outcome of each transaction.
Practitioner guidance
- Define agent-specific consent boundaries Require explicit authorization for each agent action class instead of allowing broad inheritance from an existing customer session.
- Bind tokens to the agent that holds them Use proof-of-possession controls so delegated access cannot be replayed outside the intended agent execution path.
- Separate customer, partner, and agent audit trails Record the human principal, the agent identity, the token scope, and the transaction outcome in a way that can be reconstructed without cross-tenant ambiguity.
What's in the full article
Strivacity's full blog covers the operational detail this post intentionally leaves for the source:
- Standards mappings for OAuth 2.1, OIDC, PAR, RAR, DPoP, CIBA, and token exchange in agentic identity flows
- Examples of how consent, approval, and delegated scope are chained together before an agent can act
- Operational guidance on audit logging and single-instance isolation for customer identity environments
- The product-level explanation of adaptive access and autoscaling infrastructure for agentic traffic
👉 Read Strivacity's analysis of agentic identity for customer accounts →
AI agents in customer accounts: what CIAM teams need to change?
Explore further
14/09/2026 10:10 am
CIAM is colliding with an identity class it was never built to govern: agents that act inside customer accounts are not just another OAuth client or partner integration. They reuse the same account relationships, but they do so with machine speed, variable execution paths, and transaction volume that human-paced identity controls were not designed to absorb. That means customer identity governance now has to separate authentication, delegation, and accountability more explicitly than legacy CIAM usually does. Practitioners should treat agentic commerce as a governance redesign problem, not a feature request.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: How do customer-facing agents differ from partner integrations?
A: Partner integrations are usually stable, pre-approved, and reviewed infrequently. Customer-facing agents are more dynamic, can operate continuously, and may change behaviour within a single session, which makes consent granularity and runtime accountability much more important.
👉 Read our full editorial: Agentic commerce is exposing CIAM limits for customer identity
