Notifications
Clear all
Topic starter
14/09/2026 9:44 am
TL;DR: Consumer agents are already completing logins, forms, and purchases on behalf of real users, and the key problem is not whether they can act but whether websites can distinguish legitimate autonomous traffic from bots and abuse, according to Arkose Labs. Existing trust signals, bot controls, and device-based assumptions are being forced to decide on sessions that are both genuine and machine-driven, which changes identity governance at the edge.
NHIMG editorial — based on content published by Arkose Labs: consumer AI agents, website trust, and the Population Two problem
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
A: Security teams should stop forcing human login patterns onto autonomous agents and instead use ephemeral identities, just in time credential issuance, and runtime scoped permissions.
Q: Why do AI SOC agents create a new access-control problem?
A: Because they need credentials and permissions to query multiple security tools, but they also make runtime decisions that traditional scripts cannot.
Q: What signals show that bot controls are not enough for agentic traffic?
A: If your controls only tell you whether traffic looks automated, they are too coarse.
Practitioner guidance
- Separate agentic traffic from generic automation Create reporting and policy categories for disclosed agents, hidden automation, and human sessions so teams can see how much traffic is actually agent-driven and what it does.
- Apply action-specific controls at login, search, and payment Do not use one treatment for every endpoint.
- Recheck trusted-device assumptions Review device binding, fingerprinting, and returning-customer logic for any flow where a browser session may be created by an agent running outside the user's device.
What's in the full article
Arkose Labs' full analysis covers the operational detail this post intentionally leaves for the source:
- How Muse and Instinct differ in browser, device, and network behaviour across real session flows
- What the vendor observed about bot signalling, selective disclosure, and challenge outcomes in live testing
- How checkout, account creation, and login decisions can be tuned separately for agentic traffic
- Why infrastructure-provider reputation is not a reliable control for identifying autonomous sessions
👉 Read Arkose Labs' analysis of consumer AI agents, identity, and website trust →
Consumer AI agents and website trust: what should teams do now?
Explore further
14/09/2026 9:45 am
Identity is becoming a runtime authorisation problem, not just an authentication problem. Consumer agents can now log in, browse, and transact inside ordinary web flows, which means the decisive question is what the session is allowed to do after it is already authenticated. That changes the governance burden for IAM and customer security teams because the site must distinguish intent and action class, not simply identity state. Practitioners should treat session authorisation as the control plane.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials, according to AI Agents: The New Attack Surface report.
- Another finding from the same research shows that only 52% of companies can track and audit the data their AI agents access, leaving 48% with no audit visibility.
A question worth separating out:
Q: How can IAM teams govern browser-based agents without breaking customer journeys?
A: Use step-up checks and action-scoped policy instead of blanket challenges. That lets a site allow low-risk browsing or form filling while applying stronger controls to payment, account changes, or credential use. The goal is not to reject all autonomous sessions. It is to limit the blast radius of the actions they can complete.
👉 Read our full editorial: Consumer AI agents are creating a new identity decision layer
