Ravindra BagaleCourses & study guides मराठी Track your progress

27. Social Engineering Awareness

By Last updated:

Quick answer: the short, self-contained version of this lesson is the guide AI Security: Defend Prompt Injection and Data Leakage.

Chala mitrano, aaj sarvat mahatvacha ani sarvat durlakshit vishay – social engineering. Aataparyant aapan machines hack kelya, pan attacker cha sarvat sopa target machine nahi, manus aahe! Firewall, HTTPS, strong password – he sagle asun suddha ek phone call kiwa ek fake email madhe manus fasto ani sagli suraksha vaya jate. Ha chapter attack karaycha nahi, tar olakhaycha ani thambavaycha aahe – tumhi, tumche students, tumcha kutumb ani business surakshit rahava mhanun. Ha bahutek rojcha, practical dhada aahe. Samjla ka? Chala!

What you will learn in this chapter

  • What social engineering is and why it works (the psychology)
  • The main types: phishing, vishing, smishing, pretexting, baiting, tailgating
  • How to spot a phishing email or message, step by step
  • The SET toolkit – named for awareness only, not for attacking anyone
  • Building awareness: what to teach students, staff and family
  • What to do if you or someone clicked

Awareness only – never target real people

This chapter is about recognising and stopping social engineering. Sending phishing emails, fake calls or fake login pages to real people (even "as a test") without written authorisation is fraud and a crime under the IT Act (sections 66C, 66D). Only authorised, agreed awareness programs run simulated tests.

Concepts in this chapter

  1. 27.1What Social Engineering Is and Why It Works
  2. 27.2Types of Social Engineering
  3. 27.3How to Spot a Phishing Message
  4. 27.4The SET Toolkit (Awareness Only)
  5. 27.5Building Awareness and Responding
  6. 27.6Red vs Blue, Project and Real Incidents

The chapter recap is at the end of the last concept page.

Chapter 27: Social engineering awareness — practice tasks

Open chapter lessons · Full guided lab: spot the phish sample emails headers (not repeated here)

27.1 Spot the phish (paper)

EasyBanking

Why: Most breaches start with a click.

What: Mark each email Safe or Phish.

Data file: emails.csv

FromSubjectLink host
security@sbi-secure-login.comUrgent: verify accountsbi-secure-login.com
alerts@hdfcbank.comYour monthly statementhdfcbank.com
it-help@micros0ft.comPassword expires todaymicros0ft.com

About this file: Made-up email samples. Each row is one email. Columns: From = sender; Subject = subject line; Link host = domain the link goes to.

How:

  1. Check From domain, urgency, links.
  2. Look at the data file.

Expected output: Rows 1 and 3 Phish; 2 Safe.

Hint

Hover links; don't click.

Answer / how to check
  1. Phish rows have mismatched domains or urgency.

27.2 Read email headers

MediumIT

Why: Headers show the real path.

What: Inspect Received and Authentication-Results on a real mail to you.

How:

  1. Open a mail → Show original / View headers.
  2. Find SPF, DKIM, DMARC results.
  3. List the Received hops.

Expected output: pass/fail lines for SPF/DKIM/DMARC.

Hint

fail + urgent ask = high risk.

Answer / how to check
  1. You can say if SPF passed.

27.3 Write a reporting checklist

EasyHealthcare

Why: Staff need a clear next step.

What: Make a 5-step 'I got a phish' card.

How:

  1. Include: don't click, screenshot, forward to security@, delete, tell a manager.
  2. Add India's 1930 cybercrime helpline as optional.

Expected output: A one-page checklist.

Hint

See the linked reporting lab.

Answer / how to check
  1. A new joiner could follow it.

Extended teaching notes

Why this lesson matters

A SOC turns logs into action. Good juniors triage with playbooks: what fired, which asset, how bad, contain or escalate, write the timeline.

  1. Prepare: asset list, contacts, runbooks.
  2. Detect: SIEM/EDR alerts with context.
  3. Contain: disable account, isolate host, block IOC.
  4. Eradicate & recover: patch, rebuild, restore.
  5. Lessons: one improvement ticket per incident.

Indian company (sample)

A 24×7 SOC at a large Indian IT services firm handles phishing and malware for many clients. Tier-1 analysts follow a script; they do not freestyle on production.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.