- This line was added.
- This line was removed.
- Formatting was changed.
This is the web edition of The CERT Guide to Coordinated Vulnerability Disclosure. We've reproduced the original report here in its entirety to make it easier to find the topic you're looking for. We're also in the process of revising the guide based on feedback we've received since its original publication. Got a suggestion? Submit it here.
Security vulnerabilities remain a problem for vendors and deployers of software-based systems alike. Vendors play a key role by providing fixes for vulnerabilities, but they have no monopoly on the ability to discover vulnerabilities in their products and services. Knowledge of those vulnerabilities can increase adversarial advantage if deployers are left without recourse to remediate the risks they pose. Coordinated Vulnerability Disclosure (CVD) is the process of gathering information from vulnerability finders, coordinating the sharing of that information between relevant stakeholders, and disclosing the existence of software vulnerabilities and their mitigations to various stakeholders including the public. The CERT Coordination Center has been coordinating the disclosure of software vulnerabilities since its inception in 1988. This document is intended to serve as a guide to those who want to initiate, develop, or improve their own CVD capability. In it, the reader will find an overview of key principles underlying the CVD process, a survey of CVD stakeholders and their roles, and a description of CVD process phases, as well as advice concerning operational considerations and problems that may arise in the provision of CVD and related services.
CVD Quick Start
When we finished the first version of The CERT® Guide to Coordinated Vulnerability Disclosure, we noticed folks kept commenting on its length. Feedback we have received in the intervening time has convinced us that there is a need for a more succinct way to get started with CVD without requiring someone to read every word in the Guide. To that end, we offer this CVD Quick Start to act as a meta-guide to the Guide.
The Executive Summary contains an overview of the entire document, and is a good place for all readers to become familiar with what's in the guide without necessarily poring over the details. Where you go from there depends on what you're trying to achieve.
- If you're a researcher, vendor, or coordinator trying to coordinate a disclosure and you need help, you might want to start with the 6.10 Troubleshooting Coordinated Vulnerability Disclosure Table to find the problem area(s) you're currently dealing with. From there you can follow the links into the document for more details.
- If you're a vendor trying to establish a vendor product security incident response team (PSIRT), you may be interested in 2. Principles of Coordinated Vulnerability Disclosure, 5. Process Variation Points, and 7. Operational Considerations as a starting points. Additionally, you can use the 6.10 Troubleshooting Coordinated Vulnerability Disclosure Table as a rubric of scenarios to consider when planning your operational processes.
- If you're a coordinator spinning up your CVD capability, you should become familiar with 2. Principles of Coordinated Vulnerability Disclosure, 3. Roles in CVD, 5. Process Variation Points, and 7. Operational Considerations. The Appendices may also be useful to you.
- If you're a policy-maker (or influencer thereof), the sections 1. Introduction , 2. Principles of Coordinated Vulnerability Disclosure, 3. Roles in CVD, and 4. Phases of CVD are probably most useful to you to start, but there are many edge cases in 6.10 Troubleshooting Coordinated Vulnerability Disclosure Table that are worth considering when you're thinking about writing policy that sets out how things are expected to be done.
Of course, we think it's best if you eventually become familiar with the entire document, but hopefully the hints above will help you find the most effective places to start. If you're already familiar with the guide and just want to see what's new, see the update log below.
Table of contents