Join our Newsletter — 33% off our NHI Course
Home› FAQ› Identity Beyond IAM› How can security and fraud teams balance extra…
Identity Beyond IAM

How can security and fraud teams balance extra checks for unrecognized devices with a smooth experience for trusted customers?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 5, 2026 Domain: Identity Beyond IAM

Teams should apply stronger controls when device confidence is low and reduce friction when the device history supports a returning user. That usually means adaptive step-up verification, targeted MFA, and tighter review for suspicious sessions, while trusted devices move through a lighter path. The key is to make risk-based decisions that protect revenue without punishing normal customers.

How to tighten checks for unknown devices without slowing down trusted customers

The balance comes from making device trust part of the decision, not a blanket gate. When the device is unfamiliar or the signals are weak, step up the checks. When the device has a reliable history, keep the path lighter. That works best when fraud, security, and product teams agree on the same risk signals, thresholds, and exception handling.

Trusted customers should not be forced through the same challenge path as a new or suspicious device every time. The practical aim is to use device confidence to decide whether the session needs additional proof, closer review, or simply a low-friction continuation.

Device trust is stronger when teams combine posture, history, and behaviour rather than relying on one signal alone. A managed device with stable history and normal session patterns can move quickly, while an unmanaged or newly seen device should trigger more scrutiny. The most useful controls are the ones that change the experience only when the risk profile changes.

What “risk-based” device treatment looks like in practice

Risk-based treatment usually means adaptive step-up verification, targeted MFA, and tighter session review when confidence is low. It also means avoiding hard friction on every login just because a device is not yet well understood. The decision should be driven by what the device can prove about itself, what the user session looks like, and whether the request is consistent with prior behaviour.

For returning customers, the device history should reduce friction only when the surrounding signals also look ordinary. If the device is known but the session is coming from a new geography, unusual browser state, or another high-risk pattern, the customer should still be stepped up. That distinction matters because device familiarity alone does not eliminate fraud risk.

For the strongest results, teams should use a layered view of trust. Device Trust and Posture Guide is useful here because posture and compliance signals help separate a genuinely managed device from one that only appears familiar. Device Intelligence and Fingerprinting Guide adds the browser, OS, and anti-spoofing side of that decision, which is often where fraud teams need more confidence.

How to keep the customer journey smooth without opening a fraud gap

The best customer experience comes from removing unnecessary prompts, not from removing controls. If the device confidence model is mature, returning customers can move through a shorter path, but only after the team has defined which signals are strong enough to suppress extra checks. That keeps support costs and abandonment down without turning every trusted device into an open door.

Operationally, this works best when the challenge path is proportional. High-risk sessions should get stronger verification, while lower-risk sessions should be allowed to proceed with fewer interruptions. The important discipline is consistency: the same risk profile should produce the same treatment, regardless of channel or team.

There is also a useful product lesson here. When customers see repeated challenges on devices they use every day, trust in the authentication flow drops. If the challenge feels random, the process looks broken. If it feels selective and explainable, customers tolerate it much better because the friction appears tied to actual risk.

For shared or less stable environments, Kiosk and Shared Device Security Guide helps frame why some devices should never be treated like trusted personal endpoints. Shared devices, kiosks, and reset-heavy environments need a different experience design from a customer’s persistent home device.

What fraud and security teams should align on first

The most common failure is not the control itself, but the disagreement over when to apply it. Fraud teams may want more challenge on ambiguous sessions, while security teams may want stronger access assurance, and product teams may worry about abandonment. The answer is to define a shared policy for device confidence, then map that policy to clear action rules.

Fraud and Cyber Convergence Guide is relevant because this problem is really a joint operating model issue, not just an authentication tuning exercise. If fraud and security do not share the same device signals and review logic, customers get inconsistent treatment and attackers learn where the gaps are. Cross-Device Flow Security Guide is also relevant where step-up or handoff flows are involved, because smooth customer journeys can still be vulnerable if the transfer between devices is weak.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, CIS Controls v8 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementDevice-based step-up depends on managing authenticators and their lifecycle.
IA-2 — Identification and Authentication (Organizational Users)Risk-based login treatment depends on strong user authentication at varying assurance levels.
AC-6 — Least PrivilegeTrusted sessions should receive only the access needed, limiting damage if risk rises.
Recommendation — Rotate and scope authenticators so device-based step-up stays current and revocable. Apply stronger authentication when device confidence or session risk is low. Restrict privileges so a low-friction session cannot overreach when risk changes.
CIS Controls v8CIS-5 — Account ManagementBalancing friction and trust depends on reliable account and session governance.
Recommendation — Tighten account controls for risky sessions and preserve simpler access for trusted ones.
NIST Zero Trust (SP 800-207)Never Trust, Always VerifyDevice confidence is a core zero-trust decision input for dynamic access.
Recommendation — Use device trust signals to verify each request and step up only when needed.

Practitioner Guidance

What to prioritise: Start with the highest-volume journeys where device friction drives abandonment, then apply step-up only where the device confidence signal is genuinely uncertain. That gives you the fastest reduction in customer pain without weakening your strongest fraud barriers.

What to verify: Make sure device confidence is based on more than a single fingerprint or a single compliance check. A good policy should combine history, posture, session behaviour, and customer risk context before deciding whether to challenge.

Decision rule: If the session is high value, atypical, or linked to a low-confidence device, treat extra friction as justified. If the device and session both look familiar and stable, let the lighter path stand unless another risk signal overrides it.

Practitioner takeaway: The goal is not to challenge every unknown device equally, it is to challenge only the sessions where uncertainty is high enough to justify the user cost.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org