Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 38 ยท Reconnaissance

Human Factors and Social Engineering

Understand social engineering as part of the attack surface: phishing, pretexting and vishing, how authorized simulations are run, and how organizations train and measure resilience.

Firewalls and patches protect machines, but people operate the machines. An email that looks like it came from the finance director, a phone call from "IT support", a stranger holding a box who follows an employee through a secure door: these succeed because they use normal human behavior such as helpfulness, trust in authority and fear of getting in trouble. Social engineering is the manipulation of people to gain access or information, and a complete penetration test sometimes includes an authorized simulation of it.

This lesson explains the common techniques so you can recognize and measure them, shows how an ethical simulation is run, and focuses on defense. It deliberately gives no ready-made deceptive messages: the goal is understanding and resilience, not instructions to deceive real people.

Why people are part of the attack surface

Attackers choose the easiest route. Breaking into a hardened server may take weeks; a convincing email might take an afternoon. Real incident reports repeatedly show that stolen credentials and tricked users are among the most common ways in. Recon feeds this: public staff lists, email patterns and org charts, collected during OSINT, tell an attacker whom to target and what story is believable.

Common techniques

Phishing Deceptive email or message.
Vishing Phone-based pretexts.
Smishing Text-message lures.
Physical Tailgating, fake badges.

All use trust, urgency or authority.

1 / 2

Psychological levers

Social engineers rely on a small set of triggers:

  • Authority: "This is the CEO's office."
  • Urgency: "Your account closes in one hour."
  • Familiarity: a name or detail from the target's real life.
  • Helpfulness: people want to assist someone with a problem.
  • Fear and reward: threats of penalties or offers of prizes.
  • Reciprocity and social proof: "Everyone else already did this."

Defensive training teaches people to notice the pressure, not only the content, and to pause when a message combines urgency with a request for credentials, payment or secrets.

Phishing, in defender terms

Phishing messages try to make you click a link, open a file or reply with secrets. Their typical warning signs include: a sender address that does not match the display name, links whose real destination differs from the visible text, requests for passwords or payment changes, generic greetings, spelling oddities (less reliable now than before) and unexpected attachments. Spear phishing targets a specific person with personal details; whaling targets executives; business email compromise impersonates a supplier or executive to redirect payments.

Technical controls matter as much as awareness: SPF, DKIM and DMARC to make spoofing harder, link and attachment scanning, multi-factor authentication (preferably phishing-resistant, such as hardware keys or passkeys), and easy reporting buttons.

Running an authorized simulation ethically

A phishing simulation or phone test is allowed only when the contract names it. Good practice includes:

  1. Written approval from someone with authority, plus agreement on who in the organization is told in advance.
  2. A target list agreed in advance, and exclusions such as staff on leave or in sensitive situations.
  3. No harm: no real malware, no threats, no fake messages about layoffs, bonuses, bereavement or health. Scenarios should be realistic but not cruel.
  4. Credential handling: capture the fact that someone entered a password, not the password. Discard or hash any entries.
  5. A safe landing page that educates, not shames.
  6. Aggregate reporting: report rates and trends, not names, unless the client explicitly asks for individual follow-up.
  7. An escape hatch: an emergency contact in case a message spreads or a real employee panics.

The aim is learning. A good result is a high report rate: staff who flagged the message.

Physical and phone tests

Physical tests (tailgating, badge cloning, unlocked doors) carry real risk of confrontation. They need an authorization letter carried on site and a call-in number for security staff. Phone tests need clear rules about what information may be requested. Both are covered in the rules of engagement described in Rules of Engagement.

Stand-in: score a message for phishing signals

The first example is a simple rule-based detector that counts warning signs in an invented message. Real filters are far more sophisticated, but the idea of scoring several weak signals is the same.

Python Score warning signs in a message

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second example computes the metrics of a (simulated, invented) awareness exercise. Rates, not blame, are the output.

Python Measure an awareness exercise

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Defense in depth for people

  • Training that respects people: short, frequent, scenario-based, and never punitive.
  • Clear procedures: how to verify a payment change or password reset by a second channel.
  • Easy reporting: one button, quick feedback.
  • Technical backstops: MFA, email authentication, least privilege, and monitoring for unusual logins.
  • Physical controls: badge policies, visitor logs, locked server rooms.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is spear phishing?

    Spear phishing is targeted. Details from OSINT make the message more believable.
  2. 2. In an authorized simulation, what should you record when a user enters a password on the landing page?

    Capture the event for metrics but avoid storing real credentials.
  3. 3. Which is the best sign of a healthy awareness program?

    Reporting turns every employee into a sensor. Shaming discourages reporting.
  4. 4. Which control reduces damage even if a user is tricked into giving a password?

    A stolen password alone is not enough when a second factor is required.

Summary

  • People are part of the attack surface: social engineering uses authority, urgency, familiarity and helpfulness.
  • Phishing, vishing, smishing and physical intrusion are the main techniques; recon supplies the targets and stories.
  • Simulations need written approval, agreed targets, no harmful scenarios, careful credential handling and aggregate reporting.
  • Defend with respectful training, verification procedures, easy reporting, MFA and email authentication.

Next: Host Discovery