Skip to content

Chapter 7: Social Engineering

Social engineering attacks the human rather than the machine. Attackers exploit trust in authority, the wish to be helpful, fear, curiosity and social pressure. Because no software patch fixes a person, these attacks succeed even against organisations with strong technical defences. This chapter covers six tactics and the psychological trigger each one pulls.

Layman analogy

Technical hacking is like picking a lock. Social engineering is like convincing the homeowner to hand you the key willingly — while they think they're doing the right thing.

7.1 Pretexting

Creating an elaborate, fabricated scenario (the "pretext") to extract information or manipulate someone into taking a specific action. The attacker builds trust through a plausible cover story.

Example: "Good morning, I'm Dave from the IT Security team. We're rolling out a critical security patch today and need to verify your VPN credentials to ensure compatibility. Could I get your username and current password?"

Defence tip

Real IT departments will NEVER ask for your password — over email, phone, or in person. If someone asks, it is an attack. Always call back on a number you find independently.

7.2 Baiting

Luring victims with something enticing — free software offers, prizes, or physical media like USB drives — to get them to take an action that compromises security.

Famous experiment: A USB drive labelled "PAYROLL CONFIDENTIAL Q4 2024" is left "accidentally" in a company car park. Research studies consistently show that 45–60% of employees who find such drives plug them into company computers — out of curiosity or a sense of duty.

Example 7.2: Baiting

Stuxnet (2010): The malware is widely reported to have reached air-gapped (no internet connection) Iranian nuclear facilities on USB drives, plugged in by people who did not know what they carried. The exact route has never been officially confirmed. If it is right, it shows how a trusted-looking drive can carry an attack into the most secure networks.

Defence tip

Never plug in USB drives found in public places. Disable AutoRun/AutoPlay on all work computers.

7.3 Tailgating / Piggybacking

Physically following an authorised person through a badge-controlled, secure access point without swiping your own credentials. The attack relies on the natural human instinct to be polite and hold doors open.

Example: "Hi, sorry — could you hold that? My hands are completely full of boxes and my badge is in my pocket." The attacker walks straight through a secured entrance without any authentication.

Defence tip

Challenge everyone without a visible, valid badge — every single time. True security means being willing to be briefly impolite. "Politeness costs you your security."

7.4 Quid Pro Quo

The attacker offers something of value — usually a service — in exchange for information or access. The "helpful" act first creates a sense of obligation and trust.

"Hi, I'm from Microsoft IT Services. I can see from our monitoring that your computer is running very slowly. I can fix that for you right now, for free, if you just give me remote access for a few minutes."

The victim thinks: "Great, free IT help!" — but the attacker now has full remote access to install malware, steal data, or establish a persistent backdoor.

Defence tip

Your organisation has its own IT department. Unsolicited technical "help" from strangers is always a red flag. Refuse and report it immediately.

7.5 Urgency / Scarcity Tactics

Creating artificial time pressure that forces a victim to act immediately without taking time to think, question, or verify. Urgency short-circuits rational decision-making.

"CRITICAL ALERT: Your account has been compromised. You must verify your identity within the next 2 hours or your account will be PERMANENTLY and IRREVERSIBLY deleted along with all your data."

Defence tip

PAUSE. Any legitimate organisation will give you adequate time to verify. Artificial urgency is the single most reliable indicator of a social engineering attack. Slow down — verify independently through official channels.

7.6 Consensus / Social Proof

Making an unusual request seem normal and safe by claiming that peers, colleagues, or authority figures have already complied with the same request.

"This is HR. All employees have already submitted their updated login credentials for the new payroll system migration. You're one of the last few remaining. Please send yours by end of business today."

Defence tip

Verify independently by calling HR or IT directly on numbers you find yourself. Real system migrations never require employees to submit their passwords — that's what Single Sign-On (SSO) is for.

7.7 The psychology behind the tactics

Each tactic pulls a particular lever of human behaviour. Seeing the lever is the best protection, because once you can name the pressure you are under, you can step back from it.

Tactic Main psychological trigger
Pretexting Authority and trust
Baiting Curiosity and greed
Tailgating Social pressure and politeness
Quid pro quo Reciprocity
Urgency and scarcity Fear and fear of missing out
Consensus (social proof) Conformity

7.8 Defence tips

  • "Trust but verify" — always confirm unusual requests through a completely separate, independently sourced contact channel
  • Security awareness training is not optional — 91% of all cyberattacks begin with a human element
  • Establish clear, unambiguous policies: IT will NEVER ask for passwords; executives will NEVER bypass financial controls by email
  • Create a culture where questioning suspicious requests is actively encouraged, not seen as rude or paranoid
  • Report ALL suspicious contacts to the security team immediately, even if you're not sure — others may have received the same approach

7.9 Summary

  • Social engineers exploit authority, urgency, social proof, reciprocity, curiosity and scarcity.
  • The tactics are pretexting, baiting, tailgating, quid pro quo, urgency and consensus.
  • Artificial urgency is the most reliable indicator of an attack: legitimate organisations give time to verify.
  • Defences are policies and culture: IT never asks for a password, unusual requests are verified through a separate channel, and reporting is encouraged.

7.10 Exercises

  1. Match each tactic to the main psychological trigger: pretexting, baiting, tailgating, quid pro quo, urgency, consensus.

    Answer

    Pretexting: authority and trust. Baiting: curiosity and greed. Tailgating: social pressure and politeness. Quid pro quo: reciprocity. Urgency: fear and fear of missing out. Consensus: conformity (social proof).

  2. A caller says he is from IT and needs your VPN password to push a security update. What do you do?

    Answer

    Refuse. Real IT departments never ask for a password. Hang up, find the IT department's number independently and call back, and report the attempt.

  3. Why is artificial urgency considered the most reliable sign of social engineering?

    Answer

    Urgency short-circuits rational thought, and legitimate organisations give you adequate time to verify. A demand for immediate action under threat should itself trigger suspicion.

  4. Describe the baiting USB experiment and the policy that follows.

    Answer

    A USB drive labelled "PAYROLL CONFIDENTIAL" is left in a car park; studies reported that between 45% and 60% of finders plugged it in. Policy: never plug in unknown drives, and disable AutoRun on all work computers.

  5. How can an organisation make tailgating less effective without relying on individual courage?

    Answer

    Provide mantraps or turnstiles that admit one person per badge, and set a clear policy that everyone without a visible, valid badge is challenged, backed by a culture where doing so is expected and not rude.