The best approach is layered and risk based. Use multi factor authentication where appropriate, combine it with device intelligence, anomaly detection, and blocklists, and reserve the strictest checks for higher risk sign ups. The goal is to separate suspicious behavior from normal customer friction, so good users can onboard quickly while fraudsters face enough verification to fail.
How to separate fraud friction from legitimate onboarding
Reducing new account fraud starts with treating sign-up as a risk decision, not a single gate. The practical aim is to make the default path fast for low-risk applicants, then add friction only when signals suggest synthetic identity, bot activity, referral abuse, or other account-opening fraud. That keeps the user journey usable while making attacker scale and automation much harder.
For banks and fintechs, the key design choice is to score the sign-up attempt before deciding how much verification to apply. Low-risk applications can pass with light-touch checks, while higher-risk ones are stepped up to stronger verification, review, or deferred activation. A layered design like this is also a good fit for Fake Account Creation and Sign-up Fraud Guide, because it aligns friction with the tactics fraudsters actually use.
Well-run onboarding also avoids false confidence in any single signal. Device reputation, email quality, velocity, IP patterns, document checks, and behavioural signals each catch different abuse patterns, but none is reliable on its own. The best outcome is a decisioning stack that can combine weak signals into a stronger risk picture without forcing every applicant through the same slow path.
Which controls help without slowing legitimate customers?
Multi factor authentication is useful when it is applied where it adds real assurance, but it should not become a blanket sign-up tax. The strongest pattern is to reserve step-up verification for cases where the onboarding signal mix is unusual, the requested product is high value, or the risk of immediate misuse is meaningful. That is especially relevant when you need stronger identity proofing or KYC-style checks, which is why Identity Proofing and KYC Guide is the most direct companion to this problem.
Device intelligence and anomaly detection help because they add context the fraudster has to work around. Disposable email domains, repeated device reuse, emulator signals, mismatched geolocation, rapid retries, and linked attributes across many sign-ups often point to organised abuse rather than a genuine customer. The decision should be based on the combined pattern, not a single suspicious attribute.
Blocklists remain useful, but only when they are maintained as one input among many. Used alone, they are easy to evade through fresh emails, new devices, and rotating infrastructure. Used with velocity controls and cluster detection, they become part of a wider defense that can suppress repeat abuse while leaving normal applicants mostly untouched. That broader lifecycle view is captured well by the Identity Fraud Prevention Guide.
What the operating model should look like in practice
The best operating model is progressive, not binary. Start with low-friction eligibility checks, then add friction only as risk rises, and make sure the most expensive or intrusive verification happens late enough to avoid burdening clearly legitimate users. That approach keeps abandonment down while still forcing fraudsters to spend time, identities, and infrastructure to keep trying.
Practitioners should also distinguish between prevention and suppression. Some abuse patterns are best blocked at the edge, such as obvious bot traffic or known bad infrastructure. Others are better handled after account creation by limiting initial value, delaying high-risk actions, or watching for early-life fraud. This matters because attackers often test new accounts quickly after creation, so post-sign-up controls can be just as important as registration checks.
Fraud teams should measure whether the controls are actually improving the balance between loss reduction and customer experience. Good indicators include the share of sign-ups sent to step-up review, the fraud rate among approved accounts, false positives in manual review, and the time-to-complete for low-risk customers. If those numbers move in the wrong direction, the model is probably too blunt or too eager to escalate.
Risk and Threat Considerations
New account fraud is risky because the attacker is not trying to win once, but to scale. If onboarding is too permissive, synthetic identities, bot farms, and referral abuse can create clusters of fraudulent accounts that look normal long enough to extract value. If onboarding is too strict, the business pushes genuine customers out of the funnel and creates a hidden conversion problem.
Failure mechanism: Single-signal or static-rule onboarding fails when fraudsters adapt faster than the rules, rotate infrastructure, or distribute activity across many low-signal attempts that each look harmless in isolation.
Impact: The result is either excess fraud loss from approved bad accounts or excessive customer friction from blocked good users, and both outcomes degrade trust in the sign-up process.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 and OWASP Non-Human Identity Top 10 address the attack and risk surface, while CIS Controls v8 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP API Security Top 10 | API6 — Unrestricted Access to Sensitive Business Flows | Sign-up fraud exploits onboarding flows and account-creation abuse. |
| Recommendation — Protect registration flows with step-up controls and velocity checks when abuse patterns emerge. | ||
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | Risk-based onboarding limits overbroad account capabilities before trust is earned. |
| Recommendation — Restrict newly created accounts until risk signals justify broader access. | ||
| CIS Controls v8 | CIS-5 — Account Management | Onboarding fraud depends on creating and managing accounts safely and selectively. |
| Recommendation — Harden account creation with review, validation, and monitoring controls. | ||
Practitioner Guidance
What to prioritise: Tune the first decision layer around the few signals that most strongly predict abuse in your own funnel, then reserve heavier verification for outliers. If your manual review queue is full of obvious legitimate users, the step-up threshold is too low.
What to verify: Confirm that device reputation, email quality, velocity, and linked-attribute checks are feeding one decision, not separate siloed rules that each trigger friction on their own. A coordinated decision model is usually less painful for good customers and more effective against organised fraud.
Practitioner takeaway: The right balance is not “more checks” or “less checks”, but the smallest amount of friction that still makes suspicious sign-ups expensive, slow, and unattractive.
Related resources from NHI Mgmt Group
- How should iGaming operators reduce new account fraud without blocking legitimate sign-ups?
- How should banks and online businesses reduce SIM swap fraud without adding too much friction for legitimate customers?
- How should banks reduce remote deposit fraud without creating friction for legitimate new customers?
- How should retailers reduce fraud without making checkout too slow?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org