Deepfake detection for HR and hiring
Catch deepfaked candidates in video interviews, cloned executive voices on payroll changes, and forged documents at onboarding. Raid AI checks voice, video, images and documents in one platform.
4
Interview platforms covered
4
Interview platforms covered
<50ms
Audio detection latency
99.7%
Audio detection accuracy
120+
Languages
Remote hiring gave attackers a front door. A candidate can sit an entire interview behind a face swap and a cloned voice, pass onboarding with a forged ID, and land inside your systems on day one. Once they are in, the same tools let them call payroll as a senior leader. Raid AI checks the interview, the documents and the voice, so HR is not the only line between an impostor and an employee badge.
4 attacks being run against hr and hiring today
These are not projections. Each one has already been used against organisations in this position.
| Attack | Method | Modality | Who it lands on |
|---|---|---|---|
| 1Deepfaked candidates in interviews | A face swap and a cloned voice let one person interview as someone else, or let a stand in sit the technical round for a candidate who could never pass it. |
| Who it lands on: Recruiters |
| 2Forged identity at onboarding | Generated ID photos, edited passports and fabricated certificates are cheap to make and hard to spot at the pace onboarding runs. |
| Who it lands on: HR onboarding |
| 3Cloned voices on payroll changes | A voice note from a senior leader asking HR to change an employee's bank details, or to rush a payment, is now trivial to fake. |
| Who it lands on: Payroll teams |
| 4Insider access by an impostor | A hire who is not who they claimed gets laptops, credentials and customer data. The cost of a bad hire becomes the cost of a breach. |
| Who it lands on: Security teams |
How Raid AI answers it
Live interview checks
Meeting protection scores every participant while the interview runs, so a recruiter hears about a face swap before the offer, not after the first week.
Onboarding document forensics
Identity documents and certificates are checked for generated faces, edited fields and layouts that do not match the issuer.
Voice checks on change requests
Forward a voice note or upload a recording of the call asking for a bank detail change and get a verdict before payroll runs.
- One report for HR and security
- Joins interviews on Microsoft Teams, Zoom, Google Meet and Webex and flags a face swap or a cloned voice while the interview is running
- Document forensics on the IDs, certificates and payslips a candidate submits at onboarding
- WhatsApp voice notes and recorded calls checked before HR acts on a change request
- Verdicts with a confidence score and a report your recruiters and security team can both read
What this looks like on a normal day
Composite situations drawn from the pattern of reported attacks, not accounts of named customers.
Illustrative scenario
The candidate who was two people
A final round runs on Teams. Meeting protection flags the candidate's face as swapped halfway through the call, and the recruiter pauses the process before an offer goes out.
Illustrative scenario
The urgent bank detail change
HR receives a voice note from the CFO asking to update an employee's bank account before the payroll cut off. Forwarded to the WhatsApp bot, it comes back as a cloned voice, and the change is held.
Built for environments where security is not negotiable
From air gapped networks to strict data residency rules.
Retention you control
You choose how long media is kept. With zero retention, media is analysed and discarded once the verdict is returned and nothing is written to Raid AI storage. Otherwise media is kept for a window you set, 30 days by default, and then deleted. None of it is used to train a model, and enterprise tenants can keep their records inside their own database or infrastructure instead. Media goes only to the detection engines your tenant is configured to use, and only to produce the verdict.
Runs in your infrastructure
For air gapped and sovereign environments, the full detection stack runs inside your own network with no external connectivity.
TLS 1.3 encryption
All communication with the cloud API is encrypted using TLS 1.3. Media is protected from the moment it leaves your network.
Scoped API keys
Every integration is gated by a scoped key with configurable rate limits and IP allowlisting. Keys can be rotated at any time.
SOC 2 principles
Built around the five SOC 2 trust service criteria: security, availability, processing integrity, confidentiality and privacy.
Regional deployment
Cloud customers choose the region where their requests are processed. Media never leaves a specified jurisdiction.
Defence in depth
Infrastructure, application and model layers are each protected independently. A compromise at one layer does not expose customer data.
Audit logging
Every API call is written to a tamper evident audit trail, so you can reconstruct exactly what was processed, when, and by which key.
