You study how vulnerability disclosure works and want the models behind it

You work on Coordinated Vulnerability Disclosure (CVD) as a process: how cases unfold, how to measure them, and how to make the ecosystem healthier. Vultron grew out of that research, and its protocol is built on formal models you can reuse on their own. This page is a reading path through the models, the measurements, and the formal definition. Each section builds on the ones before it; read a numbered list in order and a bulleted list in any order.

Start from the goals

1. What Is Vultron? — what the protocol is, and the research it formalizes.
2. The Need for Interoperability in Coordinated Vulnerability Disclosure — why independent organizations need shared meaning, not only shared formats.
3. What Does Success Mean in CVD? — the outcomes a case is trying to reach.

Work with the models

1. Vultron Process Models — the report, embargo and case state processes and how they interact.
2. CVD Case State Model — the state space of every possible case history.
3. Measuring CVD — metrics derived from those histories.
4. Other Uses of the Vultron Case State Model — applications of the model outside the protocol.

Go to the formal definition

• A Formal Protocol Definition for MPCVD — the Multi-Party Coordinated Vulnerability Disclosure (MPCVD) protocol as communicating hierarchical state machines.
• User Stories — the requirements the protocol was designed against.