Skip to content

Social Engineering Attacks — Phishing, Pretexting, and Human Hacking

What Is Social Engineering and Why Does It Matter?

Section titled “What Is Social Engineering and Why Does It Matter?”

According to the Verizon 2024 Data Breach Investigations Report, the human element was involved in 68% of all data breaches, making social engineering the single most exploited attack vector in cybersecurity today.

Social engineering attacks are the most common initial attack vector in cybersecurity breaches today. Rather than exploiting software vulnerabilities, attackers exploit human psychology — trust, fear, urgency, and helpfulness — to trick people into handing over credentials, clicking malicious links, or granting unauthorised access. According to Verizon’s Data Breach Investigations Report, the human element is involved in the majority of breaches, with phishing consistently ranking as a top attack action.

Understanding social engineering is critical for several reasons:

  • SOC analysts triage phishing reports, investigate suspicious emails, and respond to credential compromise incidents caused by social engineering daily.
  • Security awareness is the first line of defence. Technical controls alone cannot stop an employee from willingly entering their password on a fake login page.
  • Certification exams including CompTIA Security+ SY0-701 and CEH v13 dedicate significant coverage to social engineering attack types, psychological principles, and countermeasures.
  • Career changers from non-IT backgrounds often have strong communication and people skills — understanding social engineering lets you apply those strengths in a security context.

This page covers phishing variants, pretexting, baiting, tailgating, and the psychological principles attackers exploit, along with practical defence strategies.

When I first started learning cybersecurity, I assumed it was all about code and networks. Then I studied social engineering and realised that the most devastating attacks often bypass every firewall and encryption layer by simply asking a human being to open the door. As someone who came from a non-IT background, this was the topic that made me understand why cybersecurity needs diverse perspectives — because understanding people is just as important as understanding technology.

Ethical and legal warning: Social engineering techniques should only be used in authorised security assessments (such as phishing simulations) with explicit written permission. Using these techniques to deceive people without authorisation is illegal and unethical. Study these methods to defend against them, not to exploit people.

What Do Real-World Social Engineering Attacks Look Like?

Section titled “What Do Real-World Social Engineering Attacks Look Like?”

According to the FBI Internet Crime Complaint Center (IC3) 2023 Annual Report, business email compromise (BEC) alone caused over $2.9 billion in reported losses, making it the costliest category of cybercrime reported to the FBI.

Social engineering attacks happen across every industry and at every organisational level.

ScenarioAttack methodImpact
Executive wire fraudAttacker impersonates the CEO via email, instructs finance to wire funds urgentlyMillions of dollars lost in business email compromise (BEC)
Credential harvestingEmployee receives a fake Microsoft 365 login page via phishing emailAttacker gains access to email, SharePoint, and internal systems
Optus data breach (2022)Exposed API exploited; social engineering used in follow-up scams targeting affected customers9.8 million Australian records exposed; phishing campaigns targeted victims
Help desk pretextingAttacker calls IT support pretending to be an employee who forgot their passwordPassword reset grants attacker access to corporate systems
USB baitingAttacker leaves infected USB drives in the car park labelled “Salary Review Q4”Curious employee plugs it in, malware executes automatically
Tailgating into a data centreAttacker follows an employee through a badge-secured door carrying coffee cupsPhysical access to servers, network equipment, and sensitive areas

The common thread is that every attack exploits a human decision rather than a technical flaw.

What Are the Key Concepts Behind Social Engineering?

Section titled “What Are the Key Concepts Behind Social Engineering?”

Social engineering is defined by NIST SP 800-61 as an attack that relies on human interaction and social manipulation to trick individuals into breaking security procedures, rather than exploiting technical vulnerabilities.

To understand social engineering, think of it like a con artist working a crowd. A pickpocket does not overpower their victim — they distract, misdirect, and exploit moments of inattention. Social engineers do the same thing digitally: they create a context where the target’s natural behaviour leads them to compromise their own security.

Dr Robert Cialdini identified six principles of persuasion that social engineers weaponise:

PrincipleHow attackers use itExample
AuthorityImpersonate someone with power (CEO, IT admin, law enforcement)“This is the IT department — we need your password to fix a critical issue”
Urgency/ScarcityCreate time pressure so the target acts without thinking”Your account will be locked in 30 minutes unless you verify now”
Social proofImply that others have already complied”Everyone in your department has already completed this security update”
ReciprocityOffer something first to create an obligation”I fixed your printer issue — could you just hold the door for me?”
LikingBuild rapport before making the requestAttacker researches your hobbies on LinkedIn, opens with small talk
CommitmentGet small agreements that lead to bigger ones”Can you confirm your name? Great. And your employee ID? Perfect. Now your password…”

Social engineering is an umbrella term covering many specific techniques:

  • Phishing — Fraudulent emails designed to trick recipients into clicking links, downloading attachments, or entering credentials. This is the most common social engineering attack.
  • Spear phishing — Targeted phishing aimed at a specific individual, using personal details gathered from reconnaissance.
  • Whaling — Spear phishing targeting senior executives (the “big fish”) with high-value requests like wire transfers.
  • Clone phishing — Attacker copies a legitimate email the target previously received and replaces the attachment or link with a malicious one.
  • Smishing — Phishing via SMS text messages (“Your parcel could not be delivered — click here to reschedule”).
  • Vishing — Voice phishing via phone calls. Attacker impersonates a bank, government agency, or IT support.
  • Pretexting — Creating a fabricated scenario (pretext) to extract information. The attacker assumes a false identity with a believable backstory.
  • Baiting — Offering something enticing (free USB drive, free download, prize) that contains malware or leads to credential theft.
  • Tailgating/Piggybacking — Physically following an authorised person through a secured door without presenting credentials.
  • Quid pro quo — Offering a service in exchange for information (“I am from IT support, let me fix your computer — I just need your login”).
  • Watering hole attack — Compromising a website that the target group frequently visits, so the malware is delivered when they browse normally.

Step-by-Step: Anatomy of a Phishing Attack

Section titled “Step-by-Step: Anatomy of a Phishing Attack”

Understanding how a phishing attack unfolds from the attacker’s perspective helps you recognise and defend against each stage.

The attacker gathers information about the target organisation and specific individuals. They use LinkedIn to find employee names, roles, and reporting structures. They check the organisation’s website for email formats (firstname.lastname@company.com). Social media reveals personal interests, recent events, and communication styles. The more detail the attacker collects, the more convincing the phishing email will be.

The attacker crafts the phishing email and supporting infrastructure. This includes registering a lookalike domain (e.g., mycornpany.com instead of mycompany.com), building a convincing fake login page that mirrors the target’s real portal, and writing the email copy using the organisation’s actual communication style. For spear phishing, the email references real projects, colleagues, or events the target would recognise.

The phishing email is sent. It may appear to come from a trusted colleague, a vendor, or a service the target uses (Microsoft 365, Dropbox, Australia Post). The email creates urgency: “Your account has been compromised — verify your identity immediately” or “Invoice attached — payment overdue.”

The target clicks the link and lands on the fake login page, which looks identical to the real one. They enter their username and password. The attacker captures these credentials in real time. In some cases, the fake page even forwards the credentials to the real login and passes the user through — so the target never realises anything happened.

With valid credentials, the attacker logs into the target’s actual account. From there, they may read confidential emails, send phishing emails from the compromised account to other employees (increasing trust), set up email forwarding rules to maintain access, or escalate to other systems using the same credentials.

Phishing Attack Lifecycle

How a targeted phishing attack progresses from research to account compromise

Reconnaissance
Gather intelligence
LinkedIn profiling
Email format discovery
Identify key targets
Weaponisation
Build the trap
Register lookalike domain
Clone login page
Craft convincing email
Delivery
Send the email
Spoofed sender address
Urgency trigger
Malicious link or attachment
Exploitation
Capture credentials
Victim clicks link
Enters credentials
Attacker captures in real time
Post-Compromise
Leverage access
Access victim's account
Lateral phishing
Data exfiltration
Idle

How Does Social Engineering Fit Into a Security Architecture?

Section titled “How Does Social Engineering Fit Into a Security Architecture?”

The MITRE ATT&CK framework classifies social engineering techniques — including phishing (T1566) and trusted relationship exploitation (T1199) — as primary Initial Access methods, placing human manipulation alongside technical exploits as a core attack surface.

Social engineering targets the human layer — the one layer that cannot be patched with a software update. Understanding where social engineering fits relative to technical attacks clarifies why both technical and human defences are necessary.

Technical Attacks vs Social Engineering Attacks

Section titled “Technical Attacks vs Social Engineering Attacks”

Technical Attacks vs Social Engineering Attacks

Technical Attacks
  • Target software and systemsExploit vulnerabilities in code, protocols, and configurations
  • Detectable by technical controlsIDS, firewalls, and antivirus can identify and block many attacks
  • PatchableSoftware updates and configuration changes can eliminate the vulnerability
  • Requires technical skillAttacker needs knowledge of programming, networking, and exploit development
VS
Social Engineering Attacks
  • Target human psychologyExploit trust, fear, urgency, and helpfulness in people
  • Bypass technical controlsA user willingly entering credentials on a fake page bypasses all technical defences
  • Cannot be patchedHumans cannot be updated — training reduces risk but never eliminates it
  • Low technical barrierPhishing kits are available as a service; minimal skill required
Verdict: Most successful breaches combine both approaches. Social engineering provides the initial foothold; technical exploitation expands the damage.
Use case
Defenders must address both attack surfaces. Technical controls reduce the technical attack surface; security awareness training reduces the human attack surface.

What Does Social Engineering Look Like in Practice?

Section titled “What Does Social Engineering Look Like in Practice?”

According to the SANS Institute, email header analysis and URL inspection are the two most critical skills for SOC analysts triaging phishing reports, forming the foundation of every phishing investigation workflow.

When you receive a suspicious email, checking the headers reveals whether the sender is legitimate.

Terminal window
# View full email headers in Thunderbird: View > Message Source
# Key headers to check:
# 1. Return-Path — where bounces go (should match sender domain)
Return-Path: <alert@microsoft-security-update.com>
# RED FLAG: Not a real Microsoft domain
# 2. Received: — shows the actual mail servers that handled the message
Received: from mail.suspicious-server.ru (203.0.113.50)
# RED FLAG: Russian server for a "Microsoft" email
# 3. SPF/DKIM/DMARC results
Authentication-Results: spf=fail; dkim=none; dmarc=fail
# RED FLAG: All authentication checks failed
# 4. Reply-To — where responses go (may differ from From:)
From: security@microsoft.com
Reply-To: helpdesk@microsoft-support-team.com
# RED FLAG: Reply-To domain does not match From domain
# Legitimate URL:
https://login.microsoftonline.com/common/oauth2/authorize
# Phishing URLs — spot the differences:
https://login.microsoftonline.com.evil-domain.com/auth
# Subdomain trick — the real domain is evil-domain.com
https://login.microsoflonline.com/common/oauth2/authorize
# Typosquatting — "microsof" missing the 't'
https://login-microsoftonline.com/common/oauth2/authorize
# Hyphen trick — looks close but is a different domain entirely
https://192.168.1.50/microsoft/login.html
# IP address — legitimate services never use raw IP addresses for login

Simulating a Phishing Assessment (Authorised Only)

Section titled “Simulating a Phishing Assessment (Authorised Only)”
Terminal window
# GoPhish — open-source phishing simulation framework
# Used by security teams for authorised awareness testing
# 1. Install GoPhish (on your authorised assessment server)
wget https://github.com/gophish/gophish/releases/download/v0.12.1/gophish-v0.12.1-linux-64bit.zip
unzip gophish-v0.12.1-linux-64bit.zip
# 2. Configure the campaign
# - Create email template mimicking common phishing patterns
# - Set up landing page (credential capture page for metrics)
# - Import target list (employees who have consented to testing)
# - Schedule send time
# 3. Track results
# GoPhish dashboard shows: emails sent, opened, links clicked,
# credentials submitted — all without actual credential storage
# IMPORTANT: Only run phishing simulations with:
# - Written authorisation from management
# - Legal team approval
# - HR involvement for awareness training follow-up
# - No punitive consequences for employees who fail

What Are the Limitations of Social Engineering Defences?

Section titled “What Are the Limitations of Social Engineering Defences?”

According to the Verizon 2024 DBIR, even organisations with mature security awareness programmes still experience successful phishing attacks, confirming that no single control can eliminate the human element risk.

FactorLimitationHow to handle it
Training fatigueEmployees become desensitised to repeated awareness training and stop paying attentionVary training formats (gamification, real-world examples, short videos); test with realistic simulations
Sophisticated attacksHighly targeted spear phishing with accurate personal details is extremely difficult to detectLayer defences: email filtering + MFA + anomaly detection + reporting culture
Insider threatsNo amount of external phishing training helps if a trusted insider is the attackerImplement least privilege, separation of duties, and behavioural monitoring
MFA bypassAttackers use real-time phishing proxies (Evilginx2) that capture MFA tokens mid-sessionDeploy phishing-resistant MFA (FIDO2/WebAuthn hardware keys)
OverconfidenceBelieving “I would never fall for phishing” increases vulnerabilityEveryone is susceptible — simulations should include all levels including executives
Cultural sensitivityPunishing employees who fail phishing tests creates fear and discourages reportingPhishing simulations should be educational, not punitive; reward reporting

The most dangerous assumption is believing that awareness training alone solves the problem. Defence in depth — combining technical controls, training, policies, and monitoring — is the only reliable approach.

What Interview Questions Should You Expect About Social Engineering?

Section titled “What Interview Questions Should You Expect About Social Engineering?”

The CompTIA Security+ SY0-701 exam objectives dedicate Domain 2 (Threats, Vulnerabilities, and Mitigations) to social engineering attack types and countermeasures, making these topics standard interview questions for entry-level security roles.

Social engineering questions are common in security interviews because they test your understanding of the human element — relevant to every security role.

Q1: What is social engineering in cybersecurity?

Strong answer: “Social engineering is the manipulation of people into performing actions or divulging confidential information. Instead of exploiting technical vulnerabilities, attackers exploit human psychology — trust, urgency, fear, and helpfulness. Common techniques include phishing, pretexting, baiting, and tailgating. It is consistently the most common initial attack vector in data breaches.”

Q2: What is the difference between phishing, spear phishing, and whaling?

Strong answer: “Phishing is a broad, untargeted attack sent to many recipients — like casting a wide net. Spear phishing targets a specific individual using personal details gathered from reconnaissance to make the email more convincing. Whaling is spear phishing specifically targeting senior executives or high-value individuals, often involving requests for wire transfers or sensitive data. The progression is: phishing (mass), spear phishing (individual), whaling (executive).”

Q3: An employee reports a suspicious email. Walk me through how you would investigate it.

Strong answer: “First, I would ask the employee not to click any links or open attachments and thank them for reporting. Then I would examine the full email headers to check the actual sending server, SPF/DKIM/DMARC results, and whether the Reply-To differs from the From address. I would analyse any URLs using a sandbox or URL checker without clicking them directly. If the email contains an attachment, I would submit it to a malware sandbox. I would search our email gateway logs to see if other employees received the same email. If confirmed malicious, I would quarantine all copies, block the sending domain, and alert any users who may have interacted with it.”

Q4: How would you defend an organisation against social engineering attacks?

Strong answer: “I would recommend a layered approach. Technical controls include email filtering with SPF, DKIM, and DMARC enforcement, web filtering to block known phishing domains, and mandatory multi-factor authentication — preferably phishing-resistant MFA like FIDO2 keys. Human controls include regular security awareness training with realistic phishing simulations, a clear and easy reporting process for suspicious messages, and a culture that rewards reporting rather than punishing mistakes. Policy controls include verification procedures for sensitive requests like wire transfers, callback verification for password resets, and visitor escort policies for physical security.”

How Is Social Engineering Used in Real Security Operations?

Section titled “How Is Social Engineering Used in Real Security Operations?”

According to the ASD Essential Eight maturity model, multi-factor authentication and user application hardening are two of the eight baseline mitigation strategies that directly reduce the risk of social engineering compromising Australian organisations.

As a new SOC analyst, social engineering incidents will be among the most common events you handle:

  • Phishing triage. Users forward suspicious emails to the security team. You analyse headers, URLs, and attachments to determine if the email is malicious, then quarantine copies across the organisation and block the sender.
  • Credential compromise response. When a user enters credentials on a phishing page, you force a password reset, revoke active sessions, check for unauthorised login activity, and review whether any email forwarding rules were created.
  • Business email compromise (BEC). If an executive’s email is compromised, the attacker may send fraudulent wire transfer requests. Time-critical response: notify finance, lock the account, and trace all emails sent from the compromised account.
  • Phishing simulation review. Many organisations run regular phishing simulations. SOC analysts help review results, identify high-risk departments, and support targeted training follow-up.

The Australian Cyber Security Centre (ACSC) identifies phishing as one of the most reported cybercrime types in Australia. The ASD Essential Eight maturity model includes multi-factor authentication and user application hardening as mitigations that directly reduce social engineering risk.

The Privacy Act 1988 and the Notifiable Data Breaches (NDB) scheme mean that organisations suffering a data breach from a phishing attack must notify affected individuals and the Office of the Australian Information Commissioner (OAIC) if the breach is likely to result in serious harm. This creates a strong regulatory incentive to invest in anti-phishing controls.

The Optus breach (2022) and Medibank breach (2022) — while primarily technical exploits — led to widespread phishing campaigns targeting affected Australians. As a security professional in Australia, understanding the intersection of data breaches and follow-up social engineering campaigns is essential.

For organisations operating under the Security of Critical Infrastructure Act (SOCI Act), social engineering resilience including personnel security and access control is part of the critical infrastructure risk management framework.

Social engineering is the art of hacking humans rather than systems, and it remains the most successful initial attack vector in cybersecurity.

  • Phishing is the dominant attack type. Email-based phishing (including spear phishing, whaling, and clone phishing) accounts for the majority of social engineering incidents. Learn to analyse headers, URLs, and sender authenticity.
  • Psychology is the weapon. Attackers exploit authority, urgency, scarcity, social proof, reciprocity, and commitment. Recognising these triggers in real time is a learnable skill.
  • Technical controls are necessary but insufficient. Email filtering, MFA, and URL blocking reduce risk but cannot eliminate it. A determined attacker crafting a convincing spear phishing email will eventually get through.
  • Awareness training must be ongoing and realistic. One-off annual training is ineffective. Regular phishing simulations with educational follow-up build real resilience.
  • Phishing-resistant MFA is the gold standard. FIDO2/WebAuthn hardware keys prevent credential theft even if a user clicks a phishing link because they are bound to the legitimate domain.
  • Reporting culture saves organisations. Making it easy and safe to report suspicious messages means threats are caught faster. Punishing reporters creates silence.
  • Social engineering is on every certification exam. CompTIA Security+ SY0-701, CEH v13, and CISSP all cover social engineering extensively.

Individual results vary. Career timelines, salary outcomes, and job availability depend on your location, experience, market conditions, and effort. The information on this page is educational, not a guarantee of employment outcomes.

Frequently Asked Questions

What is the most common type of social engineering attack?

Phishing via email is the most common social engineering attack. It involves sending fraudulent messages that appear to come from a trusted source, designed to trick recipients into clicking malicious links, downloading malware, or entering credentials on fake login pages. Phishing accounts for the majority of initial access in data breaches.

What is the difference between social engineering and hacking?

Social engineering targets human psychology — it manipulates people into revealing information or performing actions. Traditional hacking targets technical vulnerabilities in software and systems. In practice, most attacks combine both: social engineering provides initial access (such as stolen credentials via phishing), and technical exploitation expands that access further into the network.

Can multi-factor authentication stop phishing?

Standard MFA (SMS codes, authenticator app codes) significantly reduces phishing risk but can be bypassed by real-time phishing proxy tools like Evilginx2 that capture the MFA token during the session. Phishing-resistant MFA using FIDO2/WebAuthn hardware keys is the strongest defence because the key is cryptographically bound to the legitimate domain and cannot be captured by a proxy.

What is pretexting in social engineering?

Pretexting is creating a fabricated scenario to justify a request for information or access. The attacker adopts a false identity — such as an IT technician, auditor, or vendor — with a believable backstory. For example, calling an employee and saying 'I am from the IT helpdesk and need to verify your account details due to a system migration' is pretexting.

What is a watering hole attack?

A watering hole attack compromises a website that the target group is known to visit regularly. Instead of sending phishing emails directly, the attacker infects a trusted website with malware. When members of the target group visit the site during normal browsing, their systems are compromised. The name comes from predators waiting at a watering hole for prey to arrive.

How do you report a phishing email?

Most organisations have a dedicated phishing report button in their email client or a specific email address like phishing@company.com. Forward the suspicious email as an attachment (not inline) to preserve headers. Do not click any links, open attachments, or reply to the sender. If you have already clicked a link or entered credentials, report this immediately and change your password.

What is business email compromise (BEC)?

Business email compromise is a targeted social engineering attack where an attacker gains access to or impersonates a business email account to conduct fraud. Common BEC scenarios include fake wire transfer requests from a compromised executive account, invoice fraud where payment details are changed to attacker-controlled accounts, and data theft requests targeting HR or payroll.

Is social engineering covered on CompTIA Security+ SY0-701?

Yes. CompTIA Security+ SY0-701 covers social engineering extensively under Domain 2 (Threats, Vulnerabilities, and Mitigations). Topics include phishing, vishing, smishing, pretexting, impersonation, watering hole attacks, and social engineering principles like authority, urgency, and consensus. Understanding attack types and appropriate countermeasures is required.

What is the best defence against social engineering?

The best defence is a layered approach combining technical controls (email filtering, MFA, URL filtering), human controls (regular awareness training, realistic phishing simulations), and policy controls (verification procedures for sensitive requests, callback procedures for password resets). No single control is sufficient because social engineering exploits human behaviour, which cannot be fully controlled by technology alone.

Can AI make social engineering attacks worse?

Yes. Generative AI enables attackers to craft more convincing phishing emails at scale, with correct grammar, personalised details, and appropriate tone. AI can also generate deepfake voice and video for vishing attacks, making it harder to verify caller identity. Defenders must adapt by deploying AI-powered email analysis, strengthening verification procedures, and training users to recognise AI-enhanced attacks.


Technical content verified in March 2026 against CompTIA Security+ SY0-701 exam objectives, CEH v13 syllabus, Verizon 2025 DBIR, and ACSC threat advisories.