While Chief Human Resources Officers (CHROs) agree that hiring fraud requires attention, many doubt their organizations are equipped to stop it.

A recent report surveying 2,500 HR leaders reveals that identity fraud detection is now a top-five AI investment priority, yet only 31% of leaders feel extremely confident in preventing it.

Many mistakenly view the ability to prevent fraud as a background check problem. However, background checks are functioning as intended. The gap CHROs are sensing lies elsewhere.

This gap highlights a critical issue: awareness of hiring fraud has increased, but the necessary infrastructure has not kept pace. Fraud persists despite organizational recognition.

What the Hiring Funnel Was Actually Built to Verify

The modern hiring funnel was designed to verify claimed history:

• ​Employment dates
• ​Education credentials
• ​Criminal record
• ​License status

Each of these checks asks: is what this person says about their past accurate?

Identity—whether the human in front of you is who they say they are—was an assumption baked into the process. The funnel was designed in a world where that assumption held true.

That world is gone.

Why the Assumption No Longer Holds

Today, synthetic identities can be pieced together from real and fabricated data points. Stolen Social Security numbers (SSNs) can be attached to entirely different individuals. Deepfake interviews and AI-generated resumes mapped onto stolen credentials are now possible. The inputs the funnel relies on—name, SSN, employment history, education—can all be assembled into a profile that does not correspond to the person submitting it.

In this world, background checks don’t fail; they execute correctly on a falsified foundation. For example, a criminal record search returns no hits because the SSN belongs to someone with no record. Employment verification confirms dates because the employment actually happened—to someone else. A well-built background check will give a clean result on a synthetic candidate because it verifies what it was built to verify.

Identity Is a Distinct Layer

Identity proofing answers a different set of questions than background checks:

1. 1.Does this identity exist, with the claimed attributes?
2. 2.Does the person submitting it match?

This is both validate, then verify. Both must be true before any downstream screening, like a background check, matters. Identity proofing belongs in the hiring funnel as a separate layer with its own controls—not as a competitor to background checks or a replacement for them. Identity proofing is more than just credential verification.

This is the gap most CHROs sense when asked about their confidence in preventing hiring fraud. The control they lack isn’t a better version of something they already have; it’s a category they were never asked to build for, because the assumption held until recently. The right framing isn’t "upgrade your background checks." It’s "add the layer the funnel was missing."

Once identity is treated as its own layer, the operational approach becomes clearer:

• ​At the application stage: Passive signals catch synthetic identity patterns before recruiter time is spent on a profile that doesn’t correspond to a real applicant.
• ​At the shortlist stage: Government ID verification and liveness checks confirm a real human matches the claimed identity.
• ​At offer and Day One: A verified identity record carries through to I-9 (Form I-9, Employment Eligibility Verification) examination, providing a continuous identity thread to verify against.

The background check still runs and does what it was built for, but now it runs on a verified foundation rather than a presumed one. That’s the architecture the 31% number is asking for.

The Seat-at-the-Table Connection

CHROs who can articulate this distinction—why identity is a separate layer, not a background check upgrade—are making a strategic argument, not a procurement one. They are identifying a category of risk that touches employment law, data protection, and sanctions exposure, and they are naming it before the rest of the executive team does.

The 31% number is not bad news. It’s data. The CHROs who interpret it correctly will spend the next twelve months building the identity lifecycle the hiring funnel was missing.

See how Proof builds that continuous identity thread from first application to I-9