SOC 2 Readiness
24/7 Security Monitoring
Canadian-Based SOC
Back to Glossary
Emerging Technology

What Is Deepfake?

Definition

A Deepfake is synthetic media created using deep learning techniques to replace a person's likeness or voice with someone else's, posing significant risks for disinformation, fraud, and social engineering attacks.

People Also Ask

Common questions about Deepfake answered by our security experts.

Deepfake in Practice

Synthetic media crossed a threshold that matters operationally: a convincing clone of a specific person's voice now needs only a short sample from a conference talk, a podcast, a voicemail greeting or a social video.

This does not create a new attack. It removes the friction from an old one. Pretexting over the phone has always worked; sounding exactly like the finance director makes it work far more often.


Where it is used against organisations

UseMechanism
Payment fraudA call apparently from an executive authorising an urgent transfer
Help desk compromiseA call apparently from staff requesting an MFA reset
Vendor detail changesA voice call that was supposed to be the verification step
Meeting impersonationSynthetic video or voice joining a call
Reputational attackFabricated statements attributed to a named individual

The help desk case is currently the most damaging, because it converts a phone call directly into authenticated access. An MFA reset is the highest-value request an attacker can make.


Why detection is the wrong first answer

Detection tooling exists and improves; so does generation. A control that depends on spotting the fake fails the moment the technology moves, and it places the decision with a person on a call who has no tooling at all.

More fundamentally, the weakness is process. If a payment approval depends on recognising a voice, that control was always weak — voice was never a good authenticator, merely hard enough to imitate that nobody examined it.

Controls that work regardless of how convincing the voice isCallback on a known number, dual authorisation and non-knowledge-based help desk verification, supported by an explicit rule against urgent exceptions.Callback on a number held on fileDefeats the attack entirely; costs a minuteDual authorisation through a systemNot verbal, above a defined thresholdNon-knowledge-based help desk checksEnrolled device or manager, not security questionsAn explicit no-urgent-exceptions ruleRemoves the lever the attack depends onA code word for executive requestsSimple, and effective for payment authorisationStated permission to refuseOr agents will not use it when pressed
None of these require anyone to detect anything.
Stop training staff to listen for the fake
Advice to listen for flat intonation or odd pauses describes a generation of the technology that has passed. It teaches an unreliable method and builds false confidence. Train the verification procedure instead, which holds however good the audio becomes.

Designing verification that survives pressure

The attack works by manufacturing urgency and seniority simultaneously, so the verification step has to be one that a junior member of staff can invoke against a senior person without social cost. That is a management design problem more than a security one.

Design choiceEffect
Verification is mandatory, not discretionaryRemoves the judgement call from the individual
Applies to everyone, including executivesNo exception to be pressured into
Leadership visibly follows itMakes compliance safe rather than career-limiting
Refusal is explicitly supportedAgents will not use a right they doubt
Stated in the procedure, not impliedAn unwritten norm collapses under pressure

Most help desk compromises succeed because an agent felt unable to say no to someone senior and insistent. Publishing that following the procedure will never be held against them does more than any detection tooling.

Finally, reduce the raw material where it is cheap to do so. Executive voice and video are widely published and cannot be withdrawn, so this is not a defence on its own — but unnecessary recordings of finance and approval staff, and voicemail greetings using a named individual’s voice, are avoidable contributions to the attacker’s sample set.

Where to start

Ask your help desk what they would do if a senior executive called, urgently, asking for an MFA reset. The answer is your actual exposure, and if it is “reset it”, that is a fifteen-minute policy change away from being fixed.

See defending approvals against a convincing call and business email compromise defence. GuardsArm runs phishing simulation including voice pretexting.

Need Help With Deepfake?

Our certified security professionals can help you implement the right deepfake strategy for your organization. Get a free assessment today.

Book a Free Consultation