A Case Under Vultron
The specification governs
This page explains the design of the Vultron Protocol. It is informative: the normative text is the Vultron Protocol Specification. Where this page and the specification differ, the specification governs.
This page explains what a Coordinated Vulnerability Disclosure (CVD) case looks like from your seat when the organizations in it coordinate through Vultron. It covers these topics:
- Who owns the case, and who keeps its record.
- What you see of the case.
- How your own part of the case moves.
- What an embargo invitation asks of you.
This page is for people who handle vulnerability reports and coordinate cases. It does not cover the message formats or the record-keeping machinery, which have their own pages. If you have not yet read What Is Vultron?, start there.
Your seat in the case
A case is the coordination context around one vulnerability. It holds the participants, the shared state, the messages they exchange, and any embargo agreement (§2.1 Actors, Participants and Cases in the Vultron Protocol Specification). You take part in it as a participant, through the system your organization runs. Vultron does not replace that system. It gives it a way to exchange the case with the systems your partners run, in the way that mail servers exchange mail.
What you do in a case is described by the roles you hold in it. The roles are the ones the CVD process already uses (§2.2 Roles, glossary).
| Role | What it means in a case |
|---|---|
| Reporter | You submitted the report that the case is about |
| Vendor | You produce the affected product and are responsible for a fix |
| Coordinator | You facilitate the coordination without owning a fix |
| Deployer | You operate systems that need the fix applied |
| CVE Numbering Authority (CNA) | You assign Common Vulnerabilities and Exposures (CVE) IDs directly |
| Observer | You follow the case and are bound by its embargo, with no fix obligations |
Roles are not exclusive. A vendor that finds a vulnerability in its own product is both Reporter and Vendor.
Roles also belong to the case, not to your organization: you may be the Reporter in one case and a Vendor in the next. Vultron records who holds which role, so every participant reads the same answer. Roles are assigned through the case, never claimed. You do not become a Coordinator by saying so (§12.1 Role Assignment).
Who owns the case, and who keeps its record
Two further roles describe authority over the case itself rather than a part in the disclosure.
The Case Owner is the participant whose disclosure decision the case exists to serve. It decides who is admitted to the case, which roles they hold, and whether embargo terms are accepted or torn down (§2.2 Roles). When you open a case, you are its owner. Ownership can move. A vendor that opened a case can give it to a coordinator, and every participant learns who decides for the case now (Case Ownership Transfer).
The CASE_MANAGER keeps the case's authoritative history and passes case messages between participants. It acts for the Case Owner (The CASE_MANAGER and the Case Ledger). It is the one participant that writes the shared record of the case. Every other participant holds a copy of that record, and the CASE_MANAGER sends each admitted change to all of them.
In practice, the Case Owner's own system usually holds the CASE_MANAGER role. The owner may delegate it, for example to a coordinator that hosts cases for others (§12.1 Role Assignment).
The practical consequence is the one that matters to a practitioner. There is exactly one history of what happened in the case, and everyone in the case holds the same copy of it. No participant reconciles competing versions, and nobody edits the record directly, not even the organization that opened the case.
This is not a central clearinghouse. The CASE_MANAGER role is held per case, so a different case can go through a different organization. No service sees every case (§3.2 What a Deployment Looks Like).
What you see
Your system holds its own copy of the case, assembled from the messages that have reached it (§3.1 Coordination Model). Every admitted change comes from the CASE_MANAGER and goes to every participant. So after the messages have arrived, your copy and your partners' copies show the same case history.
The table below lists what that copy tells you, whose state each item is, and who can change it.
| What you see | Whose state it is | Who changes it |
|---|---|---|
| Who the participants are, and their roles | The case's | The Case Owner, through the CASE_MANAGER |
| Where you stand on the report: received, valid, accepted, closed | Yours | Only you |
| Where each other participant stands on the report | Theirs | Only that participant |
| Whether a fix is ready or deployed, per vendor or deployer | That participant's | That participant |
| Whether the case has an embargo, and its terms | The case's | The Case Owner, through the CASE_MANAGER |
| Whether you have agreed to the Active Embargo's terms | Yours | You, by accepting or declining |
| What is publicly known: the vulnerability, an exploit, attacks | The case's | Any participant may report it; the CASE_MANAGER records it |
Every message in a case states that something has already happened. An acceptance says we accepted this report. It does not tell you to accept it too (§3.2 What a Deployment Looks Like). The one exception is a proposal, such as an embargo invitation, which asks for a decision.
Two things stay as they are today. You still talk to your partners by mail, phone, or a shared channel. The protocol carries only the traffic that changes the case (§3.2 What a Deployment Looks Like). And you see nothing of a case you have not joined. An invitation carries a minimal description of the case, and the vulnerability detail follows only after you accept (§12.2 Invitation and Acceptance).
How your part of the case moves
Each participant handles the report in its own way, and Vultron does not dictate how. It carries the outcome: where you now stand on the report. Those positions are the Report Management (RM) states, and every participant has its own (Report Management Process Model).
| State | Meaning |
|---|---|
| Start | No report has been received |
| Received | A report has arrived; triage is not yet complete |
| Invalid | This participant assessed the report as invalid |
| Valid | This participant assessed the report as valid |
| Deferred | This participant is deferring further action |
| Accepted | This participant accepted the report for active work |
| Closed | This participant closed the report |
Only you move your own RM state. When you move it, your system tells the other participants, and their copies of the case update. A vendor learns that a coordinator has accepted a report from the coordinator's message, not by asking.
Nothing here decides for you. Whether a report is credible, how urgent it is, and when an advisory is ready to publish remain your organization's judgment calls. The protocol only records the answers. The Capability Model lists every such decision and where your own process supplies it.
What an embargo invitation asks of you
Embargo Definition
An embargo is an informal agreement among peer CVD case Participants to refrain from publishing information about a vulnerability until some future point in time.
A case has at most one embargo at a time, and its state belongs to the case as a whole (Embargo Management Process Model). Whether you have agreed to the current terms is a separate question. Vultron records that answer per participant as embargo consent. The reason is that a participant that joined late or declined is in the case without being bound (§9 Participant Embargo Consent (PEC) State Machine).
An embargo invitation reaches you in one of two ways. If you are invited to a case that already has an embargo, the invitation states the terms you would agree to. When you accept it, you join the case and your consent is recorded (§12.2 Invitation and Acceptance). If you are already in a case and a participant proposes an embargo or a change to one, you receive the proposed terms and are asked to answer.
In either form, the invitation asks for one decision, and the table below shows what follows from each answer.
| Your answer | What follows |
|---|---|
| Accept | You are a signatory to the terms once they are in force. You are expected not to disclose the vulnerability to anyone outside the case until the embargo ends (Embargo Principles). |
| Decline | You are not bound. You still receive the negotiation traffic, so you can accept later terms, but embargoed case content is withheld from you (§9.5 Embargo Traffic Reaches Non-Signatories, §9.7 Gating Full Case Delivery). |
| No answer by the deadline | Recorded as timed out, distinct from an explicit decline (§9.4 Deadlines and the Pocket Veto). |
| Propose different terms | The shortest proposed embargo is taken as accepted and the longer one as a proposed revision, so the case has an embargo while you negotiate (Default Embargoes). |
Three things happen without anyone asking you.
| Event | What it means for you |
|---|---|
| A case begins already under embargo | A report recipient that publishes a default embargo in its vulnerability disclosure policy has made a standing proposal, and a Reporter who submits without proposing other terms has accepted it (Default Embargoes). Publishing your own default is the most useful thing your organization can do before its first case. |
| The terms are revised | A proposed revision changes nothing for you: the old terms stay in force and so does your consent to them. When the Case Owner activates the revision, you are carried over if it ends no later than the terms you accepted; if it ends later and you have not accepted it, your consent lapses until you do. |
| The vulnerability, an exploit for it, or attacks using it become public | The embargo ends for everyone, and every participant's consent moves to a terminal state that no later invitation can leave (Early Termination). Be prepared for this before you accept. |
Who else to bring into an embargoed case, and when, is the subject of Adding Participants to an Embargoed Case. The rules on when a new embargo may still be proposed are in Negotiating Embargoes.
When the case ends for you
You close your own report when your work on it is done: the fix is shipped, the advisory is published, or the report was not valid for you. Closing is yours alone, and the case can continue for other participants after you close. Publication follows the embargo, not the other way round: once the embargo ends, no restriction on publishing remains. What a good outcome looks like across the whole case, and how the roles pull toward it, is the subject of What Does Success Mean in CVD?.
Summary
| Question | Answer |
|---|---|
| Who owns the case? | The Case Owner, whose disclosure decision the case serves. Ownership can be transferred. |
| Who keeps the record? | The CASE_MANAGER, the one participant that writes the shared history and sends every change to everyone. |
| What do I see? | The same case history as every other participant: who is in the case, where each stands on the report, the embargo, and what is public. |
| What do I control? | Your own report handling, your own fix status, and your own answer to embargo terms. |
| What does an embargo invitation ask? | One decision: accept the stated terms, decline them, or propose others. Silence counts as declining. |
| What decides for me? | Nothing. Validity, priority, embargo terms, and publication readiness stay your organization's calls. |
Further reading
- How to Adopt Vultron in Your CVD Program — the steps from this page to a program that coordinates through the protocol
- Embargo Principles — what it means to cooperate with an embargo
- Default Embargoes — declaring a default in your disclosure policy, and why a case starts under one
- Report Management Process Model — the report states in full
- Capability Model — every decision the protocol leaves to your organization
- The Case Model and The CASE_MANAGER and the Case Ledger — the objects and the record-keeping behind this page, written for the people who build the systems
- Vultron Protocol Specification, §3 Protocol Overview — the coordination model in normative terms
Reading path: You handle vulnerability reports and coordinate cases with other organizations
This page is part of See how a case moves.
Previous
Reading path: You want to understand how a vulnerability case runs under Vultron
This page is part of Follow a case from report to publication.
Previous