CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
CSG CYBER DEFENSE EDUCATION & RESEARCH FOUNDATION
Discovering a security vulnerability is only half the task; communicating it safely, lawfully, and professionally determines whether you strengthen defensive resilience or cause an unintended security incident. This module teaches the complete Coordinated Vulnerability Disclosure (CVD) workflow—from locating /.well-known/security.txt to assembling an actionable, non-destructive technical report.
Follow these seven sequential stages strictly from initial discovery through patch validation and closure. Skipping policy verification or collecting excessive evidence can convert responsible research into a statutory violation.
Before testing any anomaly or confirming a potential security flaw, locate and read the organization’s official Vulnerability Disclosure Policy (VDP) and `/.well-known/security.txt` file (RFC 9116).
If an organization has NO VDP and NO written authorization, you have zero legal permission to run active exploits or probes in India.
IT Act 2000 Section 43 penalizes unauthorized access; a published VDP defines the conditional scope of owner consent.
Determine the official escalation channel rather than emailing marketing addresses, random developers, or posting publicly.
Never send unencrypted vulnerability details or proof-of-concept exploits to public social media accounts or generic info@ support threads.
CERT-In is the statutory national coordinator for vulnerability disclosure under Section 70B of the IT Act, 2000.
Collect only the minimum non-sensitive evidence needed for the engineering team to verify and reproduce the issue inside authorized boundaries.
Never run `--dump-all`, download customer files, alter production records, or upload persistent webshells.
Downloading personal data breaches Section 43(b) and the Digital Personal Data Protection (DPDP) Act, 2023.
Evaluate the severity using industry standards (CVSS v3.1/v4.0) and realistic exploitation scenarios without exaggerating risk or demanding payouts.
Inflating severity or framing vulnerability disclosures with financial demands risks prosecution for extortion.
Demanding money to withhold vulnerability disclosure violates Section 308 of Bharatiya Nyaya Sanhita (BNS) 2023 (Extortion).
Transmit a single, well-organized report containing summary, affected asset, technical description, reproduction steps, impact, safe evidence, and remediation advice.
Do not spam multiple channels or follow up aggressively within the first 72 business hours.
Clear written reporting creates an evidentiary record of good-faith responsible conduct.
Collaborate professionally while the organization validates, patches, and deploys fixes across production environments.
Conducting unrequested follow-up scans after a vendor states "fixed" without permission can trigger fresh intrusion alerts.
Strict adherence to the agreed remediation window preserves mutual trust and coordinated disclosure ethics.
Public write-ups or CVE publications occur only after patches are deployed, embargoes expire, and both parties agree—or remain permanently confidential if required by NDA/VDP.
Publishing unpatched 0-day exploits before vendor remediation causes mass harm and destroys researcher credibility.
Breaching confidentiality obligations under an NDA or VDP triggers criminal liability under Section 72A of the IT Act.