HackBlue

Course · People · 04 / 18

Pretexting and impersonation: invented stories and borrowed identities

Pretexting builds a believable story, often impersonating a colleague, vendor, auditor, or official, to get information or action. How pretexts are built from public information, which roles are targeted, and the verification scripts that stop them.

11 min read · practice only with authorization

Diagram

A pretext call to payroll

Follow the path. One example at a time.
Story

The caller says they are an auditor from the parent company.

Illustration: Story
# Story
# The caller says they are an auditor from the parent
# company.

The example on the open step is one illustration, or the fix you can paste into an application you own.

What this page is made of

A short map of the pieces. Each piece says what fails, who is affected, what you would notice, and what you change.

  1. 01Informed pretexts
  2. 02Impersonated roles
  3. 03Pressure to skip process

Informed pretexts

What fails
Public details make a story sound inside-informed.
Who is affected
Staff who equate knowledge with legitimacy.
What you would notice
Callers who know names but not internal ticket numbers.
What you change
Teach that knowing names proves nothing; verify through the directory.

Impersonated roles

What fails
IT, executives, auditors, vendors, and law enforcement are common choices.
Who is affected
Finance, HR, help desk, and reception.
What you would notice
Requests from those roles outside normal systems.
What you change
Route those requests through tickets or known contacts.

Pressure to skip process

What fails
Urgency and irritation are used to stop verification.
Who is affected
Whoever is on the phone.
What you would notice
Callers objecting to a callback.
What you change
Make callback non-negotiable and back staff who use it.

Check yourself

Recognition and the fix. Nothing here is a procedure.

1 / 3

A caller knows the finance director’s name and a real project. Does that verify them?

Sibling techniques

Pages at the same depth, plus a lab and a glossary card for this one.

  1. MapSocial engineering: the levers attackers pull and the processes that resist themSocial engineering works by using authority, urgency, helpfulness, and familiarity to get people to skip a check.

Practice

  1. LabScope deskDecide whether a situation is in scope, needs a written change, or stops.

Glossary

  1. CardPretextingA made-up story, often a vendor or an executive, justifies skipping a check.