Blog

Webinar Recap

Who’s really behind the resume? HR and security leaders discuss candidate identity verification

by Nisos | Nov 10, 2026 | Blog

Why 2019 Hiring Processes Don't Work Anymore

Zapar said teams are at very different stages of awareness. Some TA teams know the problem well. Some cybersecurity teams don't yet, and she found that surprising. What they share is a funnel that has changed:

Candidate identity verification is becoming a shared priority for HR and security teams as hiring processes face fraudulent applications, interview cheating, and identity inconsistencies.

That was a theme of our recent webinar, Who's Really Behind the Resume? Nisos CEO Ryan LaSalle talked with two people who see the problem from different sides of the hiring process. Dr. Adrian Mayers is CISO and VP at Primera Blue Cross Blue Shield and a member of the Nisos Advisory Board. Stacy Zapar is a career talent acquisition leader, founder of Tenfold, and founder of Fraud Squad, a community of TA and security professionals.

Below are the main takeaways. You can also watch the full on-demand webinar

They can't use their processes from 2019 and before and expect that to work in the age of AI because they're seeing flooded funnels and fraud bots and auto-apply, and everyone looks alike, and recruiters are swamped, and we have smaller teams than we ever had, but we've got 4X the volume."

Your content goes here. Edit or She also described candidate fraud as a spectrum, not a single threat. It runs from embellished resumes and copy-pasted applications, through interview cheating, to identity and credential fraud. In her words, it's "more of a 31 flavors kind of thing" than a Neapolitan view of two or three types.

Her advice on volume: "If you have a volume problem, you have a fraud problem as well." She pointed to a Nisos investigation of one fraud ring. In it, 22 people had applied to more than 170,000 jobs in three months.

Her caution on numbers is worth repeating. Fraud rates vary widely by industry, team, and whether roles are remote. Treat any single statistic "with a grain of salt." She cited a Zapier CEO's post describing a role where a large majority of applicants were fake.

Can Fraudulent Candidates Pass Background Checks?

Yes. A traditional background check mostly verifies the documents and records a candidate provides. It doesn't establish that the person behind them is real.

LaSalle said that in Nisos's work, "every fraudulent IT worker we've uncovered in a company has passed a background check." Zapar said the FBI's most recent warning describes stolen and fake profiles being run through background check companies before any application is submitted. Only the profiles that pass get used.

For a closer look, see our posts on background check fraud and identity corroboration beyond background checks.

Candidate Identity Verification Works Best as a Layered, Continuous Process

The panel kept returning to a security idea: layered defenses, with no single checkpoint carrying the full load. Zapar put it this way:

"I think it now needs to be a continuous effort, not a spot check at the end, or just at the beginning."

Identity checks belong at every candidate touchpoint, from application through onboarding and after hire. Different interviewers talk to the same candidate at different stages. Without a way to confirm it's the same person each time, nobody can be sure.

Mayers said the same logic applies after the offer is accepted. Security teams already watch for deviations from a baseline in insider threat programs, and the same mindset now applies to who's applying and interviewing. LaSalle added that identity can change over time, and Nisos has seen cases where the person hired was not the person who showed up on day one.

Stolen Identities Are Easy to Prop Up. A History Is Hard to Fake.

In a demo of Nisos Identity Integrity, LaSalle showed how one hypothetical candidate profile looked when compared against the wider digital world. He noted that it's "very easy to... steal an identity and prop it up with a persona. It's very hard to create a history."

The example surfaced several discrepancies:

  • A voice-over-IP phone number
  • Employment history that didn't match the resume
  • No presence in breach data beyond an email address
    Key online accounts less than
  • a year old, with nothing before January 2, 2026

No single item proves anything. LaSalle noted that a VoIP number is also common among recent graduates. The value is in the pattern, which tells a recruiter or investigator where to look more closely. Zapar's takeaway: "No one of them is a verdict. You stack it and you look at the totality, and then a human decides."

Want to see it for yourself? Try the Identity Integrity guided tour.

How to Tell Legitimate AI Use From Candidate Fraud

Plenty of real candidates use AI to polish a resume. A resume that AI touched isn't a red flag by itself, and LaSalle noted you'd wonder about a candidate who didn't use it at all.

Mayers' advice is simple: "just ask the question." Ask candidates how they used AI, and let the answer start a conversation. If a candidate isn't forthright, that's a reason to look closer.

Zapar added a distinction. A gut feeling is a flag, but it only becomes a signal after you dig deeper and can document what you found. That gives you a defensible decision. She also recommends being upfront about when AI use is and isn't appropriate, such as during a live technical interview. She said that approach seems to be working.

Add Friction That Only Bad Actors Feel

Extra checks can cost you good candidates and slow down hiring. Mayers noted that delays carry real business costs, and Zapar said some teams have overcorrected by adding hoops for everyone. Her answer is "smart friction": steps that are a heavy lift for bad actors while genuine applicants "sail right through" without noticing.

LaSalle shared a related story. A hiring manager told a CISO that, if not for the security team's warning, the candidate (a suspected North Korean applicant) was the best interview they'd had. Hiring managers are rewarded for speed and quality. Without shared goals, that incentive can work against risk checks.

Who Owns Candidate Fraud Prevention? Everyone, Together.

The strongest agreement among the panelists was on ownership. Candidate fraud sits between HR, TA, Security, Legal, Compliance, and the business, so no single team can handle it alone. Zapar recommended a cross-functional "center of excellence" built on four pillars: governance and compliance, process and strategy, tools and technology, and people. Mayers said that when HR and Security realize they're fighting the same thing, "Wonder Twins activate."

For TA teams, there's an added hurdle. LaSalle noted recruiters often sense something is off but aren't sure what they can ask without running into Equal Employment Opportunity (EEO) or policy concerns, and fraudsters count on that discomfort. Legal and HR guidance, agreed ahead of time, gives recruiters the confidence to dig in.

Five Takeaways From the Panel

  1. Build layers. Verify continuously, before and after hire.
  2. Define roles. Make it clear who owns what, so nobody assumes someone else has it.
  3. Verify, don't just check. Treat a gut feeling as a reason to dig deeper until you have a signal.
  4. Align incentives. The goal is the best candidate, quickly, within the business's risk tolerance. Leadership needs to back HR and Security teams explicitly.
  5. Use your community. ISACs, groups like Fraud Squad, and partners can all help. As LaSalle put it, this is a team sport.

Zapar's advice for getting started: sit down with your CISO or a security counterpart, and start with the conversation. Fraud Squad offers a free self-assessment questionnaire to guide it.

Watch the Full Conversation

The panel covered more than we can fit here, including audience Q&A and the threats these teams are seeing. Watch the on-demand webinar

Frequently Asked Questions

Can fraudulent candidates pass background checks?

Yes. Ryan LaSalle shared that the fraudulent IT workers Nisos uncovered had passed background checks. The panel emphasized combining background screening with additional identity checks and investigating inconsistencies.

When should teams verify candidate identity?

The panel recommended multiple checkpoints throughout hiring, from application through interviews and onboarding, with continued attention after hire. These checks help teams assess whether the same person is participating at each stage.

Who should own candidate fraud prevention?

The panel described it as a shared responsibility across HR, talent acquisition, security, legal, compliance, and business leaders. Teams should define who reviews concerns, investigates inconsistencies, and handles escalation.

Platform

See how Nisos works

Take a guided tour of the platform, or explore the solutions built for your team.