35. Careers, Certifications and Bug Bounty
35.6 Responsible Disclosure and Staying Legal
Sometimes you notice a security problem on a site without a bug bounty programme, for example while using it normally.
- Stop at the first sign. Do not dig further, do not download data, do not "prove" more than you already saw.
- Find the right contact:
https://example.com/.well-known/security.txt, a "responsible disclosure" page, or the company's security email. - Report privately and politely with minimal details needed to understand the issue. Never demand money – asking for payment in exchange for not publishing can be treated as extortion.
- Give them time to fix it, and do not publish without permission.
- Government systems: report vulnerabilities in Indian government or critical systems to CERT-In (see its vulnerability reporting instructions on cert-in.org.in) or NCIIPC for critical infrastructure.
- Keep your own notes of what you did and when, in case questions come later.
Ravindra Bagale's Tip
"I was only trying to help" is no excuse in the eyes of the law if you tested without permission. If you find a bug by accident – stop, note it, and report it. And never send a company a message like "pay me or I'll publish" – that is not a service, it is a crime.
Ravindra Bagale's Tip – मराठी
"मी फक्त help करत होतो" हे कायद्यासमोर कारण नाही, जर तुम्ही permission शिवाय test केले तर. चुकून bug दिसला – थांबा, note करा, report करा. आणि कधीच company ला "पैसे द्या नाहीतर publish करतो" असा message पाठवू नका – ती सेवा नाही, गुन्हा आहे.
Ravindra Bagale's Tip – हिंदी
"मैं तो बस help कर रहा था" कानून के सामने बहाना नहीं है, अगर आपने permission के बिना test किया. गलती से bug दिख गया – रुको, note करो, report करो. और कभी भी company को "पैसे दो वरना publish कर दूँगा" ऐसा message मत भेजो – वह सेवा नहीं, अपराध है.
Practice task
Check whether three well-known websites publish a security.txt file at /.well-known/security.txt (just open the URL in a browser – this is public). Draft a polite responsible-disclosure email for a fictional issue on "Sahyadri Travels" with only the minimum details.
Career quick reference
| Goal | Next step |
|---|---|
| First job | SOC L1 or VAPT trainee; strong networking + Linux + one SIEM |
| Foundation certificate | Security+, ISC2 CC or AWS Cloud Practitioner |
| Hands-on pentest | eJPT or CEH, then OSCP or PNPT |
| Cloud security | AWS Security Specialty with a real AWS hardening project |
| Practice | TryHackMe, PortSwigger Academy, Hack The Box, local labs |
| Proof | GitHub lab notes, write-ups, honest LinkedIn profile |
| Earn legally | Bug bounty within scope; responsible disclosure otherwise |
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.