CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
Master the legal boundaries between good-faith security analysis, terms of service violations, and unlawful computer access under Indian IT Act 2000, US CFAA, and RFC 9116.
Technical accessibility is NOT authorization. You must verify that the asset is explicitly named in the program scope before executing non-standard requests.
Never disrupt production services. DoS testing, high-volume fuzzing, data deletion, and social engineering are universally excluded from bug bounties.
Stop as soon as vulnerability existence is confirmed. Never exfiltrate, dump, or retain third-party customer PII or confidential company records.
Respect the 90-day remediation window. Bounties are discretionary awards—never demand money under threat of public disclosure or embargo breach.
Understanding the distinction between programs prevents unrealistic reward expectations and scope confusion.
| Feature | Bug Bounty Program | Vulnerability Disclosure (VDP) | Educational Reference |
|---|---|---|---|
| Monetary Bounties | Yes (Tiered Cash Payouts) | No (Hall of Fame / Swag only) | None (Academic case study) |
| Safe Harbor Immunity | Standard or Gold Standard | Legal protection for good-faith CVD | N/A (Historical or synthetic target) |
| Testing Authorization | Strict In-Scope Assets Only | Organization Owned Assets | NO ACTIVE TESTING PERMITTED |
| Disclosure Protocol | Platform mediated (HackerOne, Bugcrowd) | Direct email / RFC 9116 security.txt | Classroom analysis only |
| Primary Goal | Crowdsourced offensive vulnerability discovery | Safe, coordinated intake of accidental findings | Pedagogical study of disclosure failures |
Analyze genuine ethical dilemmas and legal boundaries drawn from industry precedent.
A researcher discovered an unauthenticated SQL injection vulnerability on an e-commerce order lookup endpoint. Instead of running a single benign test query (e.g., SELECT @@version), the researcher ran an automated tool that dumped 50,000 customer records and downloaded the entire database to their local hard drive.
Dumped 50,000 customer records locally to "prove" the severity to the bug bounty triage team.
Safe Harbor Good-Faith Clause & IT Act Section 43/66
Extracting data beyond what is strictly necessary to demonstrate the existence of a vulnerability violates Safe Harbor rules and constitutes unauthorized computer access. Under the Indian IT Act (Section 43/66) and the Digital Personal Data Protection Act (DPDP 2023), possessing third-party customer personal data without consent is unlawful. Triage teams do NOT require a full data dump to confirm SQLi; a database version or current timestamp query is sufficient.
Test your understanding of safe harbor terms and legal scope boundaries before filing reports.
1. A company lists `*.example.com` in their scope. You discover that `blog.example.com` points to a third-party managed WordPress host. Are you authorized to run automated SQL injection scanners on the host provider?
2. While testing an authorized IDOR flaw, you can see invoice numbers. What should you do to document the proof-of-concept?
Our 5-step report builder performs automated pre-flight scope validation, scans evidence for sensitive credentials, and submits your draft to CSG faculty evaluators.