34. Indian Cyber Law and Cyber Crime Awareness
34.6 What to Do If You Are a Victim
Speed matters most in financial fraud – the faster you report, the better the chance banks can freeze the money.
- Call 1930 immediately (national cyber crime helpline) for financial fraud, and also call your bank to block the card/account/UPI.
- File a complaint on cybercrime.gov.in (National Cyber Crime Reporting Portal). Choose financial fraud or other cyber crime; women and child related crimes can be reported there too, including anonymously for some categories.
- Save evidence: screenshots, transaction IDs (UTR numbers), phone numbers, URLs, emails with full headers, chat exports. Do not delete anything.
- Secure your accounts: change passwords, enable 2FA, log out all sessions, check email forwarding rules, uninstall any screen-sharing app you installed.
- Visit the local cyber police station / cyber cell if asked, and keep the complaint acknowledgement number.
- For organisations: follow the IR plan, report to CERT-In within 6 hours for specified incidents, and assess DPDP breach notification duties.
- Do not pay blackmailers or "recovery agents" who promise to get your money back for a fee – that is usually a second scam.
Ravindra Bagale's Tip
People don't file a complaint out of embarrassment, or because "it's only a small amount, let it go". But your complaint also saves that fraudster's other victims. Call 1930 within the first hour – that is the "golden hour".
Ravindra Bagale's Tip – मराठी
लोक लाजेमुळे किंवा "एवढे कमी पैसे, जाऊ दे" म्हणून complaint करत नाहीत. पण तुमच्या complaint मुळे त्याच fraudster चे इतर victims पण वाचतात. पहिल्या तासात 1930 ला phone करा – हा "golden hour" असतो.
Ravindra Bagale's Tip – हिंदी
लोग शर्म की वजह से या "इतने कम पैसे हैं, जाने दो" सोचकर complaint नहीं करते. पर आपकी complaint से उसी fraudster के दूसरे victims भी बचते हैं. पहले घंटे में 1930 पर phone करो – यह "golden hour" होता है.
Practice task
Role-play in class: one student is a victim of a fake KYC fraud that took ₹15,000 by UPI 20 minutes ago. The other student guides them through the seven steps above in the right order. Write down every piece of evidence they should collect.
Cyber law and reporting quick reference
| Need | Where / what |
|---|---|
| Official IT Act text | indiacode.gov.in |
| Report cyber crime | cybercrime.gov.in, helpline 1930 |
| Organisation incident reporting | CERT-In (cert-in.org.in), within 6 hours for specified incidents |
| Log retention (CERT-In) | 180 days, within India |
| Personal data law | DPDP Act, 2023 (check current rules on meity.gov.in) |
| Fraud calls, lost phone | Sanchar Saathi (sancharsaathi.gov.in), Chakshu |
| New criminal laws | BNS, BNSS, BSA from 1 July 2024 |
Extended teaching notes
Why this lesson matters
In India, unauthorised access can be a crime under the IT Act. CERT-In issues directions for certain organisations. The DPDP Act 2023 raises expectations around personal data. When unsure, stop testing and ask.
- Written permission and exact scope before any test.
- Report financial fraud quickly via 1930 / cybercrime.gov.in.
- Preserve evidence (screenshots, IDs, hashes) without altering originals.
- Bug bounties only on programmes that list the target.
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.