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

27. Social Engineering Awareness

27.5 Building Awareness and Responding

By Last updated:

What to teach (students, staff, family):

  • Never share OTP, password, PIN or card details with anyone, ever.
  • Do not click links in messages to log in; open the official app/site yourself.
  • Verify unusual requests by calling back on an official number you looked up (not the one in the message).
  • Slow down – urgency is the attacker's main weapon.
  • Report suspicious messages; do not be embarrassed to ask.
  • Lock devices, do not plug in unknown USBs, do not let strangers "tailgate" into secure areas.

If you (or someone) clicked or shared something:

  1. Do not panic, act fast. Disconnect the device from the internet if malware may have run.
  2. Change passwords from a different, safe device – the affected account first, then any account sharing that password.
  3. Enable MFA everywhere.
  4. Call the bank to block cards/transactions if financial details were shared.
  5. Report: cybercrime.gov.in and the 1930 helpline (India), and inform your IT/security team.
  6. Learn from it – note what the message looked like so others can be warned.

Why this matters for security

You can spend lakhs on firewalls and still be breached by one convincing phone call. Awareness is the cheapest and most effective control against social engineering, because it fixes the weakest link – the human – across every attack in this book.

Ravindra Bagale's Tip

If you have been cheated, the biggest mistake is staying quiet out of embarrassment. Don't panic and don't be embarrassed – change your password right away, inform your bank, and report it on 1930. The sooner you act, the smaller the loss. Tell your family this clearly.

Practice task

Write a short one-page "safety card" in simple language for your family or students: the top five rules and the exact steps (and the 1930 number) to follow if they get tricked. This is a real, useful thing you can hand out.

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.