How to

Candidate fraud in cybersecurity hiring: the patterns security teams see and the checks they run

On this page
  1. Why are cybersecurity roles a target?
  2. What fraud patterns show up in cybersecurity hiring?
  3. How do you verify cybersecurity certifications?
  4. What should the technical interview test?
  5. What do security teams check before and after day one?
  6. How do you keep these checks fair?
  7. What should you do when a check fails?
  8. Cybersecurity hiring fraud checklist
  9. Questions people ask

Cybersecurity hiring attracts candidate fraud because the job comes with the keys: administrator rights, security tooling and incident data. The documented patterns, as of November 2026, are stolen or rented identities that pass background checks, AI-altered faces and voices on video, resumes inflated by a team behind one applicant, certification and clearance claims that do not match the issuer's records, and hires who hand the work to someone else through remote access software. The checks that work are layered: certifications verified by number with the issuer, clearances verified by a security officer, a technical interview that tests the candidate's own claims, identity bound to the device on day one, and limited access until every check clears.

The agency side of this is in candidate fraud in IT staffing, and the full list of North Korean indicators is in North Korean IT worker red flags. This page is the security team's view: what is different when the hire will defend the network.

Why are cybersecurity roles a target?

Because a fraudulent hire in security is an insider with privileges. The FBI's January 2025 announcement says North Korean IT workers have used "unlawful access to company networks to exfiltrate proprietary and sensitive data" and, once discovered, extorted companies by holding stolen data and code hostage. The Justice Department's June 30, 2025 announcement describes workers who gained access to export-controlled data, including International Traffic in Arms Regulations data from a California defense contractor. DCSA's July 2026 newsletter for cleared contractors warns that, once hired, such operatives "deploy malware, map network topography, and establish persistent backdoors."

Security companies are not immune. KnowBe4, a security awareness training company, wrote in July 2024 that it hired a remote software engineer after four video interviews, a background check and reference checks. The background check "came back clear due to the stolen identity being used," the photo was AI-enhanced, and the new Mac "immediately started to load malware" when it arrived. Its endpoint detection software caught it; the company says no data was lost and credits keeping new employees "in a highly restricted area when they start" with no access to production systems.

What fraud patterns show up in cybersecurity hiring?

PatternHow it shows upCheck that catches itSource
Stolen identity that passes screeningClean background check, real Social Security number, real addressA background check is not an identity check; match the person to the ID liveKnowBe4, July 2024; FBI, October 2026: workers buy access to identity verification services to confirm stolen data "will pass employment background checks"
AI-altered face or voiceA face that smears when a hand passes over it; mismatched lip movementOn-camera checks for every candidate; see deepfake candidatesDCSA, July 2026: real-time AI tools "alter facial features, voices, and backgrounds"
A team behind one resumeTen-plus tools per category; cannot go deep on any of themAsk for detailed explanations of the listed skillsJoint advisory, September 18, 2026: "multiple people may be collaborating behind the scenes, inflating the perceived skill set"
Certification that is not on the issuer's recordA PDF or badge image only; a CISSP who is an Associate of ISC2Verify by number on the issuer's siteSame advisory: "verify certifications by checking registration numbers"
Clearance claim"Active TS/SCI" on a remote applicationThe cleared employer's security officer checks DISS; see how to verify a security clearanceFBI, October 2026: workers target "positions requiring U.S. government security clearances"
Hidden workerThe verified hire installs remote access software and someone else worksDevice controls and monitoring after hireDOJ, December 4, 2025: the hire showed his own license and passport in the interview
Laptop sent elsewhereA late request to ship equipment to a friend's addressShip only to the ID address; no changes after the offerDCSA, July 2026; KnowBe4, July 2024

How do you verify cybersecurity certifications?

Ask for the identifier the issuer uses, then check it yourself on the issuer's site. CompTIA and ISC2 are covered in how to verify a candidate's certifications; the other common security issuers work like this, as of November 2026:

IssuerAsk the candidate forWhere to checkWatch for
GIAC (GSEC, GCIH, GCIA and others)Full name or GIAC analyst IDGIAC's Certification Holder Directory, which searches "by name or analyst ID"A name match alone; confirm the specific certification and status
ISACA (CISA, CISM, CRISC and others)Certificate number and last name as in their ISACA profileISACA's Verify a Certification pageISACA says certification maintenance is annual: if the annual requirements are not met, "the three-year certificate is no longer valid," so check the current status, not the paper
OffSec (OSCP and others)The certificate, or full name and OSIDCertificates issued after April 5, 2022 carry a QR code to the Accredible credential page, per OffSec's help center; older ones by requestOffSec says Skills Passport cards "are not official verification documents"

A verified certification proves the record belongs to a name. It does not prove the person on your call owns that name, which is why the identity check and the technical interview still matter.

What should the technical interview test?

The candidate's own claims, in depth, with the same interviewer able to compare rounds. The loop itself, with an alert triage work sample and an incident tabletop, is in the cybersecurity interview guide. For fraud, three habits help:

  • Follow one claim all the way down. "You listed Splunk and Sentinel. Pick the one you used every shift last year. Walk me through the last detection you tuned: what fired, what you changed, what broke." A person who did the work can keep going; a borrowed resume runs out after the second follow-up.
  • Keep continuity. The September 2026 advisory lists "frequent glances at another monitor, as if reading from the screen," "occasional background voices" and "repeated video or audio freezes." None of these proves anything alone. Note them, and compare with later rounds.
  • Check location claims against the job, not the person's origin. The same advisory suggests personal questions such as hometown or weather. In the United States, questions about where someone is from can drift into national origin. Ask what the job needs instead: "The role is based in Denver with a week of onboarding on site. Can you be there on the 3rd?"

What do security teams check before and after day one?

Screening before access is a baseline control, not an extra. NIST's SP 800-53 Rev. 5 control PS-3 says to "screen individuals prior to authorizing access to the system" and to rescreen under conditions the organization defines. The FBI and DCSA guidance adds the post-hire controls:

  1. Identity bound to the device. Equipment ships only to the address on the ID; DCSA says to prohibit changing the shipping address "after an offer letter is signed." Multi-factor authentication is enrolled live, with the verified person on camera; see how to confirm a remote hire's identity on day one.
  2. Least privilege first. The FBI's January 2025 guidance says to practice least privilege, disable local administrator accounts and limit the ability to install remote desktop applications. Privileged roles get production access in steps.
  3. Watch for the tools named by the FBI. The October 2026 announcement lists remote desktop software (AnyDesk, TeamViewer, RustDesk, Chrome Remote Desktop, Splashtop Streamer and RMM tools) and keyboard-video-mouse over IP devices (TinyPilot, PiKVM, GL.iNet) used to control company laptops.
  4. Watch logins. The January 2025 announcement says these workers "often have multiple logins into one account in a short period of time from various IP addresses."
  5. Watch for data leaving. The same announcement says workers have copied company code repositories "to their own user profiles and personal cloud accounts."
  6. Make it cross-functional. The FBI says IT, HR, security and management "all have unique insights" that work better combined.

A candidate's public code is a separate check, covered in how to spot a fake GitHub profile.

How do you keep these checks fair?

  • Same checks for everyone at the same stage. The FBI warns that aggressive controls carry "unusually high risks of generating false positives that could harm legitimate employees and filter out qualified applicants."
  • Accent, name, visa status or a foreign degree are not signals. See citizenship status discrimination in hiring; ask for U.S. citizenship only where a law, regulation, executive order or government contract requires it.
  • Use the FCRA when a screening company checks: a standalone disclosure, written authorization and the adverse action steps in the FCRA background check process.
  • Record facts, not impressions: "GIAC directory shows GCIH, active, checked [date]," not "seemed fake."

What should you do when a check fails?

  1. Before hire: pause the process, re-verify through an independent channel (the issuer, a past employer you find yourself), and decide on documented facts.
  2. After hire: security acts first. Limit access quietly, preserve logs and the device, then bring in HR and counsel; the playbook is in what to do when a new hire is not the person you interviewed.
  3. Report suspected schemes to the FBI at ic3.gov; how to report candidate fraud lists what to include.

Cybersecurity hiring fraud checklist

[ ] Resume, phone and email searched in the ATS for reuse under other names
[ ] Certifications verified on the issuer's site by number or ID
[ ] Clearance (if required) verified by the cleared employer's FSO
[ ] Live identity check on camera, same step for every candidate
[ ] Technical round follows two claims to the bottom
[ ] Same interviewer or notes compared across rounds
[ ] Background check with FCRA disclosure and authorization
[ ] Equipment to the ID address only; no address change after offer
[ ] MFA enrolled live with the verified person
[ ] No production or admin access until checks clear
[ ] Alerts for remote desktop tools, KVM devices and odd logins
[ ] Repository and cloud exfiltration monitored from day one

Not legal advice. FBI, Justice Department, DCSA, NIST and issuer sources checked as of November 2026.

Questions people ask

What kinds of candidate fraud target cybersecurity jobs?

Federal warnings and cases describe stolen or rented identities that pass background checks, AI-altered faces and voices in video interviews, resumes inflated by a team working behind one applicant, certification and clearance claims that do not match the issuer's records, and hires who let someone else do the work through remote access software. Security roles are attractive because they come with privileged access to systems and data.

How do I verify a GIAC, ISACA or OffSec certification?

Use each issuer's own route. GIAC's Certification Holder Directory searches by name or analyst ID. ISACA's Verify a Certification page takes the certification type, the certificate number and the holder's last name. OffSec certificates issued after April 5, 2022 carry a QR code that opens the holder's Accredible credential page; for older ones, OffSec asks for the learner's full name and OSID. As of November 2026.

Has a security company really hired a fake IT worker?

Yes. KnowBe4, a security awareness training company, wrote in July 2024 that it hired a remote software engineer after four video interviews, a background check and reference checks, and that the person was a North Korean IT worker using a valid but stolen US identity with an AI-enhanced photo. Its endpoint detection software flagged malware loading on the new laptop, and the company says no data was lost.

Should a new security hire get admin access on day one?

Usually not. NIST SP 800-53 control PS-3 calls for screening individuals before authorizing system access, the FBI recommends least privilege and disabling local administrator accounts, and KnowBe4 credited its practice of keeping new employees in a restricted area with no production access for limiting its 2024 incident. Grant privileged access in steps once identity, background and device checks are complete.