You want to understand how a vulnerability case runs under Vultron
Every other part of this site assumes the ideas on this one: what a Coordinated Vulnerability Disclosure (CVD) case is, who takes part in it, and the processes that move it from a first report to publication. Read this path first if you are deciding which of the other tabs you need, or if you need the shared vocabulary before you go deeper. Each section builds on the ones before it; read a numbered list in order and a bulleted list in any order.
If you have been here before and want one page in particular, Look Something Up lists the reference pages of every tab: the specification, the requirements, the messages, and the glossary.
Reading path: You want to understand how a vulnerability case runs under Vultron
| Start | Previous | Current | Next |
|---|---|---|---|
|
--- |
|
Know what kind of thing Vultron is
- What Is Vultron? — a protocol your systems speak, not a platform you join, and what it leaves to you.
- CVD as a Coordination Problem — why coordinating a case across organizations is hard today.
You can stop here if this section answered your question.
Follow a case from report to publication
- A Case Under Vultron — a case from a participant's seat: who owns it, and what each participant sees and controls.
- Vultron Process Models — the report, embargo and case state processes that move every case.
- Capability Model — the decisions the protocol leaves to each organization, and where its own judgment plugs in.
Look up a term
- Glossary — Vultron — every term the rest of the site uses, defined once.
- Vultron Concept Taxonomy — the distinct concepts that together make up Vultron, and how they relate.
When you know what you came to do, the other tabs each open on a path of their own: coordinating cases, implementing the protocol, working on the reference implementation, and studying the process.