Social Engineering

  • Home
  • Social Engineering
Social Engineering
Social Engineering — Phishing Series 02 | Safety Is A Mindset
Safety Is A
Mindset
Active Threat Category
Phishing Series · 02 of 06
Phishing Series · 02 of 06
Safety Is A Mindset · Cybersecurity Awareness

Social Engineering The Attack Is Human.

Social engineering is not a technology problem. It is a psychology problem. Attackers study human behaviour — trust, authority, fear, urgency, reciprocity — and weaponise it. No firewall stops a manipulated employee. Only a trained mind does. Safety Is A Mindset builds that mind.

Social Engineering — Attack Prevalence

0%

of cyberattacks involve a social engineering component (Proofpoint State of the Phish, 2024)

74% Of all data breaches involve a human element — phishing, stolen credentials, or misuse (Verizon DBIR 2024)
$17M Average annual cost of social engineering attacks to an enterprise (Ponemon Institute)
82 sec Median time before first click on a phishing email after deployment — faster than most detection tools respond

The Attacker's Toolkit

6 Psychological Triggers Attackers Exploit

Every social engineering attack weaponises one or more of these six psychological principles. They are not weaknesses — they are normal human cognitive functions. Safety Is A Mindset teaches people to recognise when these triggers are being activated against them.

01

Authority

People comply with requests from figures of authority — real or fabricated. Attackers impersonate the CEO, IT department, government agencies, auditors, or law enforcement. The perceived status of the requester short-circuits normal scepticism.

Real-World Attack Script "This is the CFO. I need you to process an urgent wire transfer before 5pm today. Keep this confidential — I'm in a board meeting."
02

Urgency & Scarcity

Time pressure disables critical thinking. When people believe they must act immediately or face serious consequences, they bypass verification steps and act on instinct. Attackers manufacture deadlines, crises, and limited windows to force hasty decisions.

Real-World Attack Script "Your account will be permanently locked in 15 minutes unless you verify now. Click here immediately."
03

Social Proof

Humans look to others' behaviour as a guide for their own actions. Attackers reference colleagues, departments, or industry peers to normalise the request: "Everyone in finance has already completed this security update." The implied consensus removes the sense of individual risk.

Real-World Attack Script "The rest of your team has already verified their credentials. You're the last one outstanding."
04

Liking & Rapport

People are more likely to comply with requests from people they like or with whom they share something in common. Attackers build rapport by researching targets on LinkedIn, referencing real colleagues, shared experiences, or local events — making the interaction feel familiar and trustworthy before the ask.

Real-World Attack Script "I saw you were also at the Melbourne conference last week — great keynote! Quick question while I have you..."
05

Reciprocity

The human tendency to return favours creates a powerful vulnerability. Attackers provide something first — helpful information, a compliment, a small favour — to create a felt obligation. The target then feels socially compelled to return the favour, often by providing access, data, or credentials.

Real-World Attack Script "I just fixed that VPN issue you were having. While I'm in your system — can you confirm your access credentials for the audit trail?"
06

Fear & Threat

Fear of negative consequences — job loss, legal action, account suspension, breach notification — drives people to act quickly and without verification. Attackers frame inaction as dangerous and immediate action as the only escape, exploiting the survival instinct that prioritises avoidance over analysis.

Real-World Attack Script "Our system detected illegal activity from your IP address. Law enforcement has been notified. Call this number immediately to avoid arrest."

Attack Taxonomy

How Social Engineering Arrives

Social engineering isn't limited to email. It arrives through every communication channel your team uses — phone, text, social media, in person, and through physical access. Safety Is A Mindset trains awareness across all vectors.

Critical

Phishing Email

Mass or targeted emails impersonating trusted entities. The most common vector — 3.4 billion phishing emails sent daily. Exploits authority, urgency, and fear. Often the entry point for ransomware, credential theft, and Business Email Compromise.

Frequency91%
⚡ Key tell: Mismatched sender domain, artificial deadline, request for credentials or payment
Critical

Vishing (Voice Phishing)

Phone-based attacks where attackers impersonate IT support, banks, government bodies, or internal executives. Voice deepfake technology now allows convincing audio impersonation of real known individuals. Caller ID spoofing masks the true origin number.

Frequency69%
⚡ Key tell: Unsolicited call requesting remote access, passwords, or immediate action — regardless of caller identity
High

Smishing (SMS Phishing)

Text message attacks exploiting the informal, high-trust nature of SMS. Commonly impersonates delivery services, banks, or internal IT. Mobile users click links faster than email users. Short URLs mask destinations and evade traditional filters.

Frequency61%
⚡ Key tell: Unexpected delivery notification, link to unfamiliar domain, request for personal details via text
High

Pretexting

The attacker fabricates a convincing scenario — a false identity or situation — to extract information. May involve weeks of research and multiple interactions to build credibility before the actual request. Often used for insider access, account takeover, and corporate espionage.

Frequency47%
⚡ Key tell: Unfamiliar contact needing unusual information or access; story that feels slightly off-script
High

Tailgating & Piggybacking

Physical social engineering — following an authorised person through a secured door without credentials. Exploits politeness (holding doors) and the reluctance to challenge someone who looks like they belong. Results in physical access to server rooms, restricted areas, or sensitive materials.

Frequency32%
⚡ Key tell: Someone following closely at an access point, hands full (preventing badge swipe), claiming to be a contractor
Medium

Baiting

An attacker leaves infected USB drives, QR codes, or enticing downloads where targets will find them. Curiosity and greed override security instincts. Studies show 45–90% of found USB drives are plugged into organisational computers — without verification.

Frequency28%
⚡ Key tell: Unknown USB found in car park, lift, or desk area; QR codes on unsolicited materials or public signage
Medium

Quid Pro Quo

Offering a service or benefit in exchange for information. Attackers impersonate IT support, offering to "fix" a problem the target didn't know they had. In exchange, they request login credentials, remote access, or sensitive configuration information. Exploits reciprocity and helpfulness.

Frequency22%
⚡ Key tell: Unsolicited offer to fix or improve something in exchange for access or information you haven't requested

How It Actually Happens

The Social Engineering Attack Lifecycle

Phase 1 — OSINT & Targeting

Research & Reconnaissance

Before any contact, the attacker builds a comprehensive profile of the target organisation and individuals. LinkedIn reveals org charts, reporting lines, and employee backgrounds. Company websites reveal suppliers, partners, and systems. Social media reveals personal interests, travel patterns, and relationships. This phase can take days to weeks — and it's entirely invisible to the target. The more sophisticated the attacker, the deeper the research goes.

⚠ What you share publicly online is the raw material for your own attack. Review your digital footprint — and your team's.

Phase 2 — Pretext Construction

Hook Development

Using the intelligence gathered, the attacker builds a convincing cover story — the "pretext." This may involve creating fake email accounts using actual employee names, registering lookalike domains, building a LinkedIn persona with mutual connections, or scripting a plausible reason for the request. The hook is designed around the specific psychological triggers most likely to work on the specific target — their role, their responsibilities, their known concerns.

⚠ The reason an attack feels legitimate is because it was specifically designed around what you're likely to believe.

Phase 3 — Approach

Initial Contact

The attacker makes first contact through the chosen vector — email, phone, in person, text, or social media. The initial contact may not include the actual malicious request. Many sophisticated attacks spend the first interaction purely building rapport and credibility, gathering more information, or priming the target emotionally before the hook is set. Multi-stage attacks are designed to feel like a series of normal interactions.

⚠ Attackers rarely reveal their true intent in the first contact. The relationship-building phase is part of the attack.

Phase 4 — The Ask

Exploitation

Once trust is established and the psychological groundwork is laid, the attacker makes their actual request — a credential, a wire transfer, a clicked link, a door held open, a document shared. This phase is often brief, because all the preparation work was done to ensure the answer is yes. For the target, the request arrives in a context that has already been made to feel legitimate, urgent, and reasonable.

⚠ The moment of compliance is often the least suspicious moment. The attack has been designed to make the ask feel obvious and safe.

Phase 5 — Disappearance

Exit & Cover

After obtaining what they need, the attacker disappears — the email address stops responding, the phone number is disconnected, the social account is deleted. In some cases, attackers actively cover their tracks by providing a plausible explanation for any anomaly noticed by the target. Many victims don't realise they've been attacked until weeks later, when a breach is discovered that traces back to that one phone call or email.

⚠ Time is always on the attacker's side. The average breach takes 204 days to identify — long after the social engineer has moved on.

Recognition Training

Red Flags Every Employee Should Know

Social engineering attacks share patterns that a trained eye can recognise. Safety Is A Mindset builds the recognition reflex through repeated exposure to these patterns — until spotting them becomes automatic.

Manufactured Urgency

Any request that includes a tight, artificial deadline — "act now," "within the hour," "before end of day or consequences" — is applying the urgency trigger. Legitimate organisations almost never require you to bypass normal verification on a time-critical basis.

🛡️ Pause. The urgency is the manipulation. Slow down deliberately — it breaks the psychological pressure cycle.

Requests for Secrecy

"Don't tell anyone," "keep this between us," "don't contact IT directly" — instructions to conceal the interaction are among the clearest red flags in social engineering. Legitimate internal requests are never designed to prevent you from verifying them with colleagues.

🛡️ The instruction not to verify is the verification that something is wrong. Tell someone immediately.

Unusual Channel for Sensitive Requests

Your CEO doesn't ask for wire transfers via WhatsApp. Your IT team doesn't request passwords by text. When a request for sensitive action arrives through an informal, non-standard, or unexpected channel, the channel mismatch itself is a red flag regardless of how legitimate the message looks.

🛡️ Call back the requester on a number you look up independently — never the number provided in the suspicious message.

Unexpected Windfall or Fear Trigger

Offers that seem too good (you've won something, you're being offered exclusive access) and threats that trigger fear (your account is compromised, legal action is pending) both bypass rational analysis in the same way. Both exploit emotional arousal to override critical thinking.

🛡️ Strong emotional reactions — excitement or fear — are the attacker's signal that the hook is working. That feeling IS the red flag.

Credentials or Access Requested

No legitimate IT system, financial institution, or internal team ever needs you to provide your password. If any communication — email, phone, text, chat — asks for login credentials, this is always an attack. No exceptions. No legitimate reason exists for anyone to need your password.

🛡️ Your password is yours alone. Anyone asking for it — regardless of claimed identity — is attempting to compromise you.

Unsolicited Attachment or Link

Unexpected attachments, file shares, or URLs arriving without prior context are the delivery mechanism for the majority of malware and credential phishing. Even from a known sender — whose account may be compromised — unsolicited attachments demand verification through a separate channel before opening.

🛡️ Contact the sender through a known channel — not by replying to the same message — and verify they intentionally sent it before clicking anything.

Test Your Instincts

Social Engineering Mindset Check

Recognising social engineering in the abstract is different from recognising it under real-world conditions. Work through these scenarios — the same way Safety Is A Mindset trains teams to think, not just what to remember.

Social Engineering Mindset Check

5 real-world scenarios · Immediate feedback · Safety Is A Mindset

Question 1 of 5

What is the correct immediate response?

You receive a phone call from someone claiming to be your IT helpdesk. They say your account has been flagged for suspicious activity and they need your password to run a security check before they can lock down the threat. The caller ID shows your company's internal IT number.
A Provide the password — the caller ID confirms it's your IT team and the situation sounds urgent.
B Ask the caller to email you the request so you have it in writing before proceeding.
C Politely end the call, then contact IT directly using the internal number from your company directory — not the number that called you.
D Ask for the caller's employee ID and name, then provide the password after they confirm it.

Question 2 of 5

Which response is correct?

You find a USB drive in the company car park with a label that reads "SALARY REVIEW — CONFIDENTIAL — 2024." You do not recognise it as belonging to anyone in your team.
A Plug it in to see whose it is so you can return it to the owner.
B Hand it to IT security without plugging it into any device. Report where and when you found it.
C Plug it into a personal device instead of a work computer to keep company systems safe.
D Leave it where you found it — it's not your problem and you don't want to get involved.

Question 3 of 5

What should you do?

Your CEO sends you a WhatsApp message while travelling: "I'm in back-to-back meetings all day and can't take calls. I need you to urgently process a $12,000 gift card purchase for a client deal — buy the cards and send me the codes. Don't tell finance yet, I'll explain later."
A Process it — the CEO travels often and this kind of urgent request happens sometimes.
B Reply asking for more details about the client before proceeding.
C Do not process. This is a classic Business Email Compromise (BEC) pattern — gift card requests from "leadership" via informal channel with secrecy instruction are always fraudulent. Report to IT security and finance immediately.
D Call the CEO's mobile to verify — if it really is them, they'll explain.

Question 4 of 5

How do you respond?

A well-dressed person carrying a large box arrives at your office's secure entrance. They say they're from the printer maintenance company and have a service appointment. They look official and explain they're running late — the door is closing and they ask you to hold it for them as they can't badge in with their hands full.
A Hold the door — they look legitimate and it would be rude not to help.
B Ask their name and company, then hold the door if their answers seem reasonable.
C Politely decline to hold the door. Let them know you'll contact reception to verify their appointment and escort them in through proper channels. Apologise for the process — and stick to it.
D Hold the door but immediately tell your manager so it's documented.

Question 5 of 5

What is the right action?

A new LinkedIn connection messages you: "Hi! I work in cybersecurity consulting and noticed we have several mutual connections. I'm doing a benchmarking report on IT infrastructure in your sector — would you be willing to share what software platforms your company uses? It'll only take 5 minutes and I can share the finished report with you."
A Share the information — it's publicly available information and helping builds good professional relationships.
B Ask for more details about the report first, then decide whether to share.
C Decline to share internal platform or infrastructure information. Report the interaction to your security team — this is a classic OSINT and pretexting approach used in corporate reconnaissance before targeted attacks.
D Accept the report offer and provide general information about your industry but not your specific company.
0/5

Loading result…

The Defence

Building Your Human Firewall

Technical defences stop technical attacks. Social engineering requires a human defence — trained, culturally reinforced, and psychologically aware. These are the layers Safety Is A Mindset builds into every organisation.

Safety Is A Mindset

The Phishing Series — All Six Issues

safetyisamindset.com · Cybersecurity Awareness

Series · 01 · Cybersecurity

What Is Phishing? An Introduction

Before social engineering comes the foundational understanding of what phishing is, why it works, and how Safety Is A Mindset frames the entire category as a human behaviour challenge — not a technical one.

safetyisamindset.com/online-course-training-for-phishing-03-email-phishing

Series · 03 · Cybersecurity

Email Phishing — The Inbox Is a Battlefield

The most common delivery mechanism for social engineering attacks. Learn the anatomy of a phishing email, the 8 red flags every employee should recognise, and the response protocol if you click.

safetyisamindset.com/online-course-training-for-phishing-03-email-phishing

Cybersecurity · Incident Response

Ransomware Response Planning

Social engineering is the primary ransomware delivery mechanism. When the attack succeeds, your response plan determines how much damage is done. Build the plan before you need it.

safetyisamindset.com/online-course-training-for-ransomware

Cybersecurity · Best Practices

Password Security & Multi-Factor Authentication

When social engineering harvests credentials, strong passwords and MFA are the second line of defence. Understand why MFA is non-negotiable in a social engineering threat environment.

safetyisamindset.com/online-course-training-for-using-strong-passwords

Safety Culture

Building an Incident Reporting Culture

The fastest defence against social engineering is immediate reporting. This page explores how Safety Is A Mindset builds the psychological safety that makes workers report incidents within minutes — not after the damage is done.

safetyisamindset.com/online-course-training-for-employee-safety-orientation

Training Programmes

Cybersecurity Awareness Training

Explore Safety Is A Mindset's full cybersecurity awareness programmes — built to change how employees think and respond, not just what they know. Simulation-based. Behaviour-focused. Measurable.

safetyisamindset.com/online-course-training-for-defining-cybersecurity

Frequently Asked Questions

Small businesses are disproportionately targeted by social engineering. Attackers know that small organisations typically have less formal verification protocols, fewer security staff, and employees who wear multiple hats — meaning one person controls access to many systems. The 2024 Verizon DBIR found that small businesses experience higher rates of social engineering per employee than large enterprises. The Business Email Compromise (BEC) attacks that cost companies billions annually frequently target mid-sized and small firms where a single employee can authorise significant transactions without multi-level sign-off. The assumption that "we're too small to be a target" is itself a social engineering vulnerability — it lowers guard. Safety Is A Mindset's training is designed to scale effectively for teams of any size.
This is the core challenge of executive impersonation and Business Email Compromise defence. The training answer is to establish clear, pre-agreed verification protocols for specific categories of action — particularly financial transactions and access requests — so that the procedure, not the person's identity, governs the action. If your organisation has a rule that no wire transfer over $5,000 is processed without two in-person or verified verbal confirmations, then no impersonation email, regardless of how convincing, can bypass that rule. Workers are trained to understand: "My CEO knows the procedures too. If they're asking me to bypass them, that itself is suspicious." Safety Is A Mindset works with leadership teams to establish and communicate these protocols so employees feel empowered — not insubordinate — when they enforce them.
Deepfake social engineering involves the use of AI-generated audio or video to impersonate real individuals. The technology has advanced dramatically: audio deepfakes of executives can be generated from minutes of publicly available speech (earnings calls, interviews, conference recordings) and used in vishing attacks with convincing voice quality. In early 2024, a finance employee at a multinational firm was tricked into transferring $25 million after a video call with what appeared to be multiple colleagues — all of whom were AI-generated deepfakes. This is no longer theoretical. Defending against deepfake attacks requires establishing out-of-band verification procedures that don't rely on voice or visual recognition alone — code words, callback procedures to pre-established numbers, and multi-layer authorisation for high-value requests are all relevant mitigations. Safety Is A Mindset incorporates deepfake awareness into advanced social engineering training.
Phishing simulation click rates are the most commonly used metric — and they are useful, but incomplete. A more comprehensive measurement framework tracks: phishing simulation click rate over time (declining is good), report rate (the percentage of simulated attacks that are actively reported, not just ignored), time-to-report (how quickly employees escalate suspicious contacts), near-miss reporting volume (increasing volume indicates improving culture), and security culture survey scores. The most important metric that most organisations don't measure is report rate — because a workforce that clicks less but also reports less has a much weaker defence than one that clicks less and reports everything. Safety Is A Mindset's programme design incorporates all of these measurement touchpoints and uses them to adapt training content to observed behaviour gaps.
Susceptibility research has identified several consistent risk factors that are not about intelligence — they're about cognitive state and context. People are more susceptible when: they're time-pressured and multitasking; they're in a cooperative, helping mindset (common in customer-facing roles); they're new to a role and reluctant to challenge senior-seeming requests; they're fatigued (end of day or end of week attacks show higher success rates); or they're dealing with an emotionally charged or novel situation. High-value targets like finance, HR, and executive assistants have unique risk profiles because their jobs require responsiveness to authority requests. Safety Is A Mindset training addresses these specific contexts — not just abstract awareness. Role-specific training that addresses the particular social engineering scenarios most relevant to each team's function produces significantly better outcomes than generic awareness programmes.
This response defines your security culture. Punishing, blaming, or shaming an employee who falls for a social engineering attack produces two catastrophic outcomes: the employee delays reporting future incidents out of fear, and the entire workforce learns that incidents come with personal consequences rather than organisational learning. Both outcomes make you significantly less secure. The appropriate response is: immediate support for the affected individual; rapid escalation to IT security to contain the breach; a no-blame incident debrief that focuses on what organisational or process factors made the attack successful; updated training or procedures based on the findings; and transparent communication to the team about the incident and what's changing — without identifying the individual. Safety Is A Mindset builds its training culture on the same psychological safety principles that govern this response: the goal is learning and prevention, not attribution and punishment.

Duration: 9 minutes

Format: Video

Tier: 2

Course ID: 8298

Languages: English

Get Started with Safety Is A Mindset Training

Complete the form below to request more information, schedule your training, or ask questions about any of our professional safety programs. Let us help you take the next step toward a safer and more compliant workplace.