Vulnerability Disclosure Policies
What you'll learn: How to read and understand a vulnerability disclosure policy (VDP) before reporting security issues to an organization.
What is a Vulnerability Disclosure Policy?
A Vulnerability Disclosure Policy (VDP) is an organization's public document that explains how security researchers should report vulnerabilities, what systems are in scope, and what protections researchers receive. Think of it as a "rules of engagement" document—it tells you where you're allowed to look, what methods are acceptable, and what happens after you report.
Before reporting any vulnerability, you must carefully read the target's VDP. Skipping this step can lead to legal trouble or miscommunication, even with good intentions.
Key Components to Understand
Scope Definition
The VDP explicitly lists which systems, domains, applications, or APIs are in scope (allowed for testing) and which are out of scope (prohibited). Never test out-of-scope systems, even if you find something interesting—you could face legal consequences.
Safe Harbor Provisions
This section offers legal protection to researchers who follow the policy. It typically states the organization won't pursue legal action against good-faith security research conducted within the guidelines. This is your shield—but only if you stay within the boundaries.
Prohibited Activities
VDPs list testing methods that are never allowed, such as:
- Denial of service attacks
- Social engineering or phishing
- Physical security testing
- Testing third-party services
- Accessing other users' data beyond proof-of-concept
Violating these restrictions voids your safe harbor protection.
Interpretation Tips
Always look for contact methods, expected response times, and disclosure timelines. If something is unclear, ask before testing. Ambiguity doesn't equal permission.
Key Takeaway: A VDP is your contract with an organization—read it thoroughly to understand scope, safe harbor protections, and prohibited activities before conducting any security research.