There is a comforting belief in many offices: people who fall for scams are careless or not very bright, and we, being sensible, would never be fooled. It is wrong, and holding it makes an organisation weaker. Let us take it apart.

Myth one: it is about intelligence

Social engineering means manipulating people into actions or disclosures that help an attacker. Pretexting is the version built on a fabricated scenario, the pretext, that makes the request seem normal. The caller is not a stranger asking for a password. He is “from the IT helpdesk, working on the ticket you raised yesterday”. The email is not a random demand for money. It is “the new vendor bank details the CFO mentioned in the meeting”.

Smart people fall for these because the attack aims at ordinary habits, not at gaps in knowledge. The habits are useful in daily life, which is exactly why attackers lean on them:

  • Deference to authority. We comply with people who seem senior or official.
  • Urgency. Time pressure narrows thinking. “The payment must go before 3 p.m. or we lose the contract.”
  • Helpfulness. Most of us want to be cooperative, especially front-desk, support and accounts staff, whose jobs reward it.
  • Reciprocity and rapport. After a friendly chat or a small favour, a bigger request feels natural.
  • Fear of getting into trouble. “Your account will be suspended” lands harder than any technical warning.
  • Social proof. “Everyone in your team has already done this.”

Psychologists such as Robert Cialdini described several of these levers decades ago in the study of persuasion. Attackers did not need new science; they needed good research.

Myth two: the attacker is improvising

Good pretexts rest on research, often from public sources. Company websites, job postings that name the tools in use, LinkedIn pages showing reporting lines, press releases about new vendors, even a conference photo with a badge visible. This is open-source intelligence, and it is legal to collect and completely effective. An email that mentions the right project name, the right manager and last week’s real event will bypass the instinct that says “this looks off”.

Pretexts also move across channels. A fake email is followed by a phone call “to confirm you received it”. A voice call may now use an imitation of a known person’s voice produced with readily available software, so recognising a voice is no longer proof of identity. Treat voice and video as claims that need verification for any high-value request.

Myth three: it is mostly about email

Email is the bulk channel, but the same idea works in person (the confident stranger who follows employees through a secure door, called tailgating, or the “engineer” with a clipboard), by phone, by text, and on messaging apps. Helpdesk and password-reset lines are a favourite target: a convincing caller who knows an employee’s name, department and manager may persuade an agent to reset credentials or register a new authentication device. Several well-publicised breaches of large companies have started that way. If your helpdesk can bypass multi-factor authentication on a phone call, an attacker only needs to sound sure of themselves.

What actually helps

Telling people to “be more careful” fails, for the reasons above. What works is making the safe action easy and the risky action procedurally hard, so that nobody has to win an argument with a persuasive stranger.

  1. Out-of-band verification. For payment detail changes, credential resets and requests for sensitive data, confirm through a channel you already trust, such as a number from the staff directory, not the one in the message.
  2. Written procedures that remove discretion. “Bank detail changes require a callback and a second approver” is a rule an accounts clerk can point to when a senior person pushes back. It converts an awkward personal confrontation into “the process requires it”.
  3. Helpdesk identity checks that do not rely on facts available publicly or from a quick lookup (date of birth, manager’s name). Use callbacks to registered numbers, or manager approval through a ticket.
  4. A culture where reporting is rewarded. If staff who report a suspicious call are thanked, you learn about attempts early. If they get a reprimand for having answered, you learn nothing.
  5. Physical basics. Visitor badges, escorts, challenge-politely culture at doors, and screens that lock.
  6. Technical backstops. Phishing-resistant authentication, least privilege and payment approval limits mean that when one person is fooled, the damage is bounded.

A short illustration

An invented accounts assistant in Jaipur gets a message from “the managing director” on a messaging app: urgent, confidential, a supplier needs an advance transfer today. The tone is right, the name is right, and the sender says he is in a meeting and cannot take calls. Every lever is pulled at once: authority, urgency, secrecy. The correct response feels rude, which is the point. A company rule that says “no transfer above a set limit without callback verification and a second approver, whoever asks” lets her act correctly without needing courage. Notice that the control did the work, not her suspicion.

Anyone can be targeted on a bad day. The aim is a system in which a bad day is survivable.

Figures and names in the examples are illustrative.

Leave a Reply

Trending