Creating and Publishing a VDP
What you'll learn: How to design an effective vulnerability disclosure policy and make it discoverable to security researchers who want to report vulnerabilities responsibly.
Designing Your VDP
A Vulnerability Disclosure Policy (VDP) must be clear, complete, and welcoming. Think of it as a "bug bounty without payment"—you're inviting researchers to help you find security issues without legal risk.
Your VDP should include:
- Scope: Which systems, domains, and applications are covered (and which are explicitly out-of-scope)
- Rules of engagement: What testing methods are allowed, data handling requirements, and prohibited actions (no DoS, no social engineering, etc.)
- Submission process: Where and how to report findings (secure email, web form, PGP key)
- Response expectations: Timeline for acknowledgment and typical remediation windows
- Legal safe harbor: Clear statement that good-faith researchers won't face legal action
Publishing and Discoverability
The best VDP is worthless if researchers can't find it. Use these standard locations:
security.txt file: Place at https://yourdomain.com/.well-known/security.txt following RFC 9116. This is the first place researchers check. Include fields like Contact:, Expires:, and Policy:.
Dedicated security page: Host your full VDP at https://yourdomain.com/security or similar memorable URL, linked from your main website footer.
Email: Maintain security@yourdomain.com as a monitored inbox.
Think of discoverability like putting up clear signs to your front door—researchers shouldn't need to guess how to reach you.
Key Takeaway:
A well-designed VDP combines clear scope, safe harbor protections, and discoverable publication (especially via security.txt) to encourage responsible vulnerability reporting and build trust with the security community.