Skip to content

Vulnerability Disclosure

Vulnerability disclosure is the process by which a researcher reports a discovered weakness to the affected vendor or, eventually, to the public. Under responsible or coordinated disclosure, the researcher notifies the vendor privately first and allows a defined window to develop and ship a fix before any technical details go public.

Two international standards describe the vendor’s side. ISO/IEC 29147:2018 covers the outward-facing part, receiving reports and publishing advisories, while ISO/IEC 30111:2019 covers the internal handling process between report and fix. The tension in the field is real: full immediate disclosure without warning arms attackers before a patch exists, yet silence can leave users exposed indefinitely if a vendor drags its feet.

How does coordinated vulnerability disclosure work?

A typical case runs in five steps. The researcher finds the reporting channel, often through a security.txt file, a format standardized in RFC 9116 in April 2022 that sits at a predictable path on a website. The vendor acknowledges the report and reproduces the flaw. Engineers build and test a fix, and the vendor usually requests a CVE identifier so everyone refers to the same bug. The advisory and patch ship together, often crediting the researcher. Only after users have had time to patch do full technical details appear.

Timelines keep both sides honest. Google Project Zero, one of the most watched research teams, uses a 90+30 policy: vendors get 90 days to fix a bug, then 30 more days for users to patch before details are published, with a seven-day deadline for flaws already being exploited in the wild.

What is the difference between a vulnerability disclosure program and a bug bounty?

Approach Who is invited Payment Main purpose
Vulnerability disclosure policy (VDP) Anyone who finds a flaw None, recognition at most A safe, legal channel to report
Bug bounty program Often scoped or invited researchers Cash rewards by severity Actively attracting testing effort
Full disclosure No vendor coordination None Forcing a fix through public pressure

Many vendors add bug bounty programs that reward researchers for reporting flaws the right way, but a bounty doesn’t replace a VDP. Every organization with an internet presence needs the policy, while a bounty makes sense only when there’s capacity to triage a steady flow of reports. Good programs set clear timelines and a safe harbor so researchers are not punished for acting in good faith.

What is an example of vulnerability disclosure in practice?

US federal agencies had to build exactly this. CISA’s Binding Operational Directive 20-01, issued September 2, 2020, required each agency to publish a VDP within 180 days, commit not to pursue legal action against good-faith research that follows the policy, and bring all internet-accessible systems into scope within two years. CISA recommends acknowledging reports within three business days and resolving them within 90 days. On the legal side, the US Department of Justice revised its Computer Fraud and Abuse Act charging policy in May 2022 so that good-faith security research should not be charged federally.

Why does vulnerability disclosure matter for the CISSP exam?

Disclosure straddles Domain 6: Security Assessment and Testing and the governance concerns of Domain 1. Objective 6.4, “Analyze test output and generate report,” lists ethical disclosure next to remediation and exception handling, and the ISC2 Code of Ethics in objective 1.1 shapes how a member should behave when they find a flaw. Candidates should understand disclosure frameworks, the legal footing of vulnerability research, and how an organization should receive and act on externally reported flaws.

Exam scenarios usually test both seats. If you find a flaw in a vendor’s product, the ethical answer is to report it privately to the vendor first, not post it online or quietly exploit it. If your organization receives a report, defenders should have a process ready to triage it rather than treating an incoming report as an accusation, and answering with legal threats is almost always the wrong choice. Feed confirmed issues into patch management like any other vulnerability.

Related terms: Vulnerability Assessment, Penetration Testing