Topic starter
12/06/2026 12:38 am
TL;DR: A survey of 216 merchants and 178 Identiverse attendees found that fraud teams are struggling with outdated device recognition, manual review overload, and limited historical tracking as fraud rings use proxies, emulation, and coordinated identities to evade detection, according to Arkose Labs. The governance issue is not just detection quality, but whether device intelligence can still distinguish legitimate behaviour from adversarial activity at scale.
Editorial analysis by NHI Mgmt Group, based on content published by Arkose Labs: “Senior Fraud Executives Sound the Alarm on Device Intelligence Gaps”.
By the numbers:
- The survey covered 216 merchants at MRC and 178 attendees at Identiverse.
- At MRC, 42% of respondents cited detecting devices used by fraud rings as a key challenge.
- Among MRC respondents, 33% reported using in-house solutions built from various data points without comprehensive correlation capabilities.
Key questions
Q: What breaks when device intelligence cannot recognise repeat devices reliably?
A: Fraud teams lose the ability to separate legitimate repeat behaviour from coordinated abuse, so account takeover, chargebacks, and shared-account fraud all look more similar than they should.
Q: Why does weak device history make fraud detection less effective?
A: Without historical correlation, a current session has little context.
Q: What are the signs that device intelligence is failing in practice?
A: Look for heavy manual review, inconsistent outcomes, high false positives, and a growing gap between the number of flagged sessions and the number of useful decisions.
Practitioner guidance
- Benchmark device recognition quality across real fraud scenarios Measure how often your current stack can distinguish legitimate repeat users, shared family devices, travel patterns, VPN use, and coordinated fraud ring behaviour.
- Correlate device history with account and network signals Join device characteristics to prior sessions, behavioural anomalies, and network context so investigators can see whether a device has changed risk posture over time.
- Reduce manual review dependence with clearer escalation rules Define when device intelligence should trigger step-up checks, when it should route to analyst review, and when it should block known fraud patterns outright.
Bottom line: Device intelligence weakness is no longer a narrow fraud tooling problem. It is a governance problem that affects how organisations recognise legitimate users, coordinated fraud rings, and account takeover attempts.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 10:01 am
Device intelligence is now an identity governance control, not a fraud add-on. The article shows that fraud teams are no longer dealing with isolated transaction anomalies. They are dealing with identity ambiguity at the device layer, where recognition, tracking, and history determine whether access appears legitimate. That makes device intelligence part of the same governance stack that decides how confidence is established and how exceptions are handled.
A few things that frame the scale:
- U.S. fraud losses are projected to reach $40 billion by 2027.
A question worth separating out:
A: Security teams should tune device intelligence to reduce friction only where risk is low, then step up checks when signals suggest automation, spoofing, or account takeover. The goal is to combine high-signal detection with selective challenge rather than blanket blocking. That approach preserves conversion, reduces false positives, and keeps fraud controls aligned with business risk.
👉 Read our full editorial: Device intelligence gaps are widening fraud exposure in digital channels
This post was modified 1 day ago by NHI Mgmt Group