Join our Newsletter — 33% off our NHI Course

What would it take for device identification to hold up in fraud?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Device identification still matters, but it cannot carry fraud defence alone when attackers can spoof attributes, clear cookies, and rotate device traits, according to Arkose Labs. Fraud controls need live behavioural evidence alongside history, or familiar-looking sessions can still be abusive.

Editorial analysis by NHI Mgmt Group, based on content published by Arkose Labs: “Are You Only Identifying Devices—Or Actually Understanding Them?”.

Key questions

Q: Why do behavioural signals reduce fraud risk when fingerprints are weak?

A: Behavioural signals reduce risk because they evaluate how a session acts in real time, not just whether the device looks familiar.

Q: What do security teams get wrong about fraud challenge controls?

A: Teams often assume that a harder challenge is automatically enough.

Q: Where does device identification fail in fraud defence?

A: Device identification fails when attackers can spoof attributes, clear cookies, or rotate configurations faster than the organisation can build reliable device history.

Practitioner guidance

  • Map device trust to risk, not access by default Use device identification as one input into challenge, step-up, or block decisions rather than as a direct grant of trust for repeat sessions.
  • Correlate behaviour with device history Combine interaction timing, navigation flow, and environmental anomalies with prior device reputation before scoring a session.
  • Tune controls for both bot and human fraud Validate that volumetric automation and low-and-slow manual abuse are both detected, because each defeats a different control pattern.

Bottom line: Device identification still matters, but it cannot carry fraud defence alone when attackers can spoof and rotate device traits.

Glossary terms: Device Intelligence, Device identification, Fraud Farm, Behavioural Risk Scoring

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Device intelligence and device identification are separate governance controls, not competing products of the same category. One answers continuity questions about the device, while the other answers behaviour questions about the session. Fraud programmes that collapse those functions into one control end up over-trusting fingerprints or over-reacting to behavioural noise. The practitioner takeaway is to govern each signal for the job it can actually do.

A question worth separating out:

Q: How should fraud teams decide when to challenge a session?

A: Challenge a session when historical device reputation and live behavioural evidence disagree, or when one signal is too weak to support trust on its own. The goal is not maximum friction. It is to reserve stronger controls for sessions where the combined evidence does not support normal access.

👉 Read our full editorial: Device intelligence and identification are converging in fraud defence



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.