Topic starter
12/06/2026 9:21 pm
TL;DR: Credential stuffing and AI-enabled fraud are already driving major losses, with consumers losing over $12.5 billion in 2024 and U.S. fraud losses projected to reach $40 billion by 2027, according to FTC and Deloitte figures cited by Arkose Labs. The real issue is not bot volume but the inability to tell legitimate automation from adversarial agents, which makes static detection and point-in-time controls structurally inadequate.
Editorial analysis by NHI Mgmt Group, based on content published by Arkose Labs: “The Financial Cost of Agentic AI Fraud”.
Key questions
Q: What breaks when security teams keep using bot detection for agentic AI traffic?
A: Bot detection breaks when the automation is legitimate but adaptive.
Q: Why do authorised and malicious agents create the same fraud problem?
A: Because the channel can look technically valid even when the intent is malicious.
Q: How can security teams tell whether agentic automation is safe enough to expand?
A: Look for measurable controls, not enthusiasm.
Practitioner guidance
- Define KYA decision criteria Set explicit rules for how your organisation verifies the identity, ownership, and permitted scope of automated actors before they can transact or trigger sensitive workflows.
- Replace one-time checks with continuous enforcement Use behaviour-sensitive controls that can re-evaluate risk during a session, rather than relying on a single login-time decision to stay valid.
- Tighten delegated transaction boundaries Map which agent actions are allowed, which require step-up verification, and which should be blocked when the request falls outside the expected user authorisation boundary.
Bottom line: Agentic fraud changes the control problem from spotting bots to governing delegated automation that can act with valid-looking identity signals.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
12/06/2026 11:22 pm
KYA is the right control model when legitimate and malicious automation share the same channel. Bot detection was built for traffic classification, not delegation governance. Once consumer and enterprise agents can transact on behalf of people, the critical question becomes whether the agent is authorised and attributable. Practitioners should stop treating automation as a volume problem and start treating it as an identity problem.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Credential abuse across the entire attack chain, not just initial access, appears in 39% of all breaches, according to the 2026 Verizon Data Breach Investigations Report.
A question worth separating out:
Q: What should organisations do when AI tools can take actions on behalf of users?
A: Treat agent actions as governed identity events and require logging of tool calls, delegation chains, and execution context. Without that layer, investigations cannot tell whether an action came from the human operator, the agent, or a downstream delegated workflow.
👉 Read our full editorial: Agentic AI fraud exposes the limits of bot detection
This post was modified 3 days ago by NHI Mgmt Group