27. Social Engineering Awareness
27.4 The SET Toolkit (Awareness Only)
Kali madhe Social-Engineer Toolkit (SET) naav cha tool aahe. To phishing pages, fake emails ani payloads banavu shakto. Aapan to attack sathi vaparnar nahi – fakt he samajnyasathi ki attacker kiti sahajtene ek khari-disnari fake login page banavu shakto, mhanun aapan alert rahave.
- SET can clone a real login page so it looks identical to the original.
- It can craft phishing emails and malicious files.
- Authorised companies use it (with written permission) for awareness training – sending a safe fake phishing mail to staff and measuring who clicks, then training them.
SET is for authorised training only
Cloning a real login page and sending it to people is illegal without written authorisation, even as a "joke" or "test". We name SET so you understand how convincing fakes are made – so you and your students never fall for one.
Ravindra Bagale's Tip
After seeing SET, students realise that a fake login page looks exactly like the real one – apart from the URL, there is no difference. So always check the URL in the address bar and the HTTPS lock – that is the only real way to tell. However real a page looks, the URL can be fake.
Ravindra Bagale's Tip – मराठी
SET बघितल्यावर students ना कळते की fake login page खऱ्यासारखेच दिसते – URL सोडून काही फरक नसतो. म्हणून नेहमी address bar मधला URL आणि HTTPS lock चेक करा – तीच एकमेव खरी ओळख आहे. Page कितीही खरे दिसले तरी URL खोटा असू शकतो.
Ravindra Bagale's Tip – हिंदी
SET देखने के बाद students को समझ आता है कि fake login page बिलकुल असली जैसा दिखता है – URL के अलावा कोई फ़र्क नहीं होता. इसलिए हमेशा address bar का URL और HTTPS lock चेक करो – यही एकमात्र असली पहचान है. Page कितना भी असली दिखे, URL नकली हो सकता है.
Practice task
Without using SET, explain in your notes why you cannot trust how a login page looks, and what the only reliable check is (the exact URL and HTTPS). Give an example of a lookalike URL for a bank or wallet you use.
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.
- Prepare: asset list, contacts, runbooks.
- Detect: SIEM/EDR alerts with context.
- Contain: disable account, isolate host, block IOC.
- Eradicate & recover: patch, rebuild, restore.
- 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)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- 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.