Coordinated Disclosure Timelines
What you'll learn: How to manage the time-based choreography of vulnerability disclosure from private notification through public release.
Coordinated disclosure is like orchestrating a carefully timed product recall—vendors need time to fix the problem, but the public needs to know before bad actors exploit it.
The 90-Day Standard
Most security researchers and programs follow a 90-day disclosure window from initial vendor notification. This gives vendors time to:
- Acknowledge the issue (typically 1-5 business days)
- Investigate and reproduce the vulnerability (1-2 weeks)
- Develop and test a fix (varies widely)
- Deploy patches to affected systems (2-4 weeks)
Think of this timeline as a countdown clock: it creates urgency while respecting the complexity of software fixes.
Vendor Response Windows
After your initial report, expect:
- Initial acknowledgment: 3-5 days (if no response, escalate)
- Triage response: 7-14 days (severity assessment, timeline proposal)
- Status updates: Every 2-4 weeks during active remediation
If vendors ghost you beyond reasonable windows, you're justified in proceeding toward public disclosure.
Extension Requests
Vendors may request deadline extensions for legitimate reasons:
- Complexity requires architectural changes
- Multiple affected products need coordination
- Holiday/vacation periods impact response capacity
Evaluate these fairly—grant 30-60 day extensions for valid technical challenges, but resist indefinite delays. You control the clock, but flexibility builds trust.
Public Disclosure Timing
When the deadline arrives (or fix is deployed), coordinate final release:
- Schedule disclosure for weekdays (avoid Fridays/weekends)
- Give vendors 24-48 hours notice of exact publication time
- Allow simultaneous vendor advisory and researcher disclosure
- Include CVE identifiers and patch information
Key Takeaway: Coordinated disclosure timelines balance vendor remediation needs (90-day standard) with public safety, using clear deadlines, fair extension policies, and synchronized public release to minimize exploitation windows while maintaining researcher control.