Skip to content
Explanation

Embargo Principles

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.

An embargo is a way to delay public disclosure of a vulnerability while defenses are prepared. For example, an embargo can last until fix development is complete for a reasonable quorum of Vendors.

The goal of the EM process is not an exact publication schedule that every Participant follows. Rather,

Embargo Management Process Goal

The goal of the Embargo Management process is to establish a window from the present to some future time. During this window, Participants are expected to not publish or otherwise disclose information about the vulnerability to non-Participants outside of the CVD case.

So we define an embargo as follows:

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.

Embargoes Are a Social Agreement

An embargo is a social agreement between independent parties. These parties act so that users get vulnerability fixes in a timely manner, and so that attackers get as little advantage as possible in the interim. But an embargo is not always appropriate or useful in a given CVD case.

With this in mind, we give the following principles as guidance. We start with some norms of behavior. These norms define what it means to cooperate with an embargo.

Embargo Participants SHOULD NOT knowingly release information about an embargoed case until either

  1. all proposed embargoes have been explicitly rejected

  2. no proposed embargo has been explicitly accepted in a timely manner

  3. the expiration date/time of an accepted embargo has passed

  4. an accepted embargo has been terminated prior to the embargo expiration date and time due to other reasons (e.g., those outlined in Early Termination)

Additional Participants MAY be added to an existing embargo upon accepting the terms of that embargo.

Adding Participants to an existing embargo SHALL NOT constitute "release" or "publication" so long as those Participants accept the terms of the embargo.

For more information, see Adding Participants.

Embargoes are Limited Short-Term Agreements

When all other facts about a vulnerability report are equal, two factors have a large effect on the success or failure of an embargo. These factors are scale and duration. The more people that are part of an embargo, the more likely the embargo is to fail.

Embargo participation SHOULD be limited to the smallest possible set of individuals and organizations needed to adequately address the vulnerability report.

Similarly, the longer an embargo lasts, the more likely it is to fail.

Embargo duration SHOULD be limited to the shortest duration possible to adequately address the vulnerability report.

We also need to set a few norms for embargo timing.

An embargo SHALL specify an unambiguous date and time as its endpoint.

An embargo SHALL NOT be used to indefinitely delay publication of vulnerability information, whether through repeated extension or by setting a long-range endpoint.

An embargo SHALL begin at the moment it is accepted.

Embargoes SHOULD be of short duration, from a few days to a few months.

CVD Embargoes Are Not NDAs

CVD embargoes are not Non-Disclosure Agreements (NDAs). An NDA (also known as a Confidentiality agreement) is a legally binding contract between parties. An NDA often includes a reward for compliance, a penalty for unauthorized disclosure, or both.

NDAs sometimes have a place in CVD processes. But most MPCVD embargoes move relatively quickly and at a large scale, and this makes per-case NDAs prohibitively difficult. As a result, we intentionally set aside NDA negotiation as beyond the scope of this proposal.

At first look, many bug bounty programs can appear to be outside our scope, because they are often structured as NDAs that reward compliance. For some bounty programs, the only penalty for non-compliance or early disclosure is the loss of the reward. For other programs, non-compliance can cause the loss of a promise of amnesty. That promise gives protection from civil or criminal charges that security or acceptable-use policy violations might otherwise bring.

Nevertheless, we are optimistic that the bulk of this protocol will be found compatible with the full variety of bounty-oriented CVD programs, now and in the future. This bulk consists of the parts of the protocol that do not interfere with the contractual provisions of bounty-associated NDAs.

Embargo Participants Are Free to Engage or Disengage

As we just described, an embargo is not the same thing as an NDA, even if the two have similar effects. An NDA is a contract, so a party that breaks it can get civil or even criminal penalties. CVD embargoes have no such legal framework. So CVD Participants are free to enter or exit an embargo at any time, for any reason. In fact, CVD Participants do not have to agree to any embargo at all.

But whatever they choose, Participants should be clear with other Participants about their status and intentions. There are a few good reasons to exit an embargo early. For more information, see Early Termination.

Participants MAY propose a new embargo or revision to an existing embargo at any time within the constraints outlined in Negotiating Embargoes.

Participants MAY reject proposed embargo terms for any reason.

Participants in an embargo MAY exit the embargo at any time.

Leaving an Embargo is Not Embargo Termination

When a Participant leaves an embargo, this is not necessarily the same as the termination of the embargo itself. Embargo termination corresponds to the \(q^{em} \in \{A,R\} \xrightarrow{t} X\) transition in the EM formal model. It shows a consensus among the case Participants that the embargo no longer applies. When a Participant leaves an Active embargo, the embargo agreement between the other Participants stays intact. But the Participant that leaves is no longer involved in the case.

Participants stopping work on a case SHOULD notify remaining Participants of their intent to adhere to or disregard any existing embargo associated with the case.

Participants SHOULD continue to comply with any active embargoes to which they have been a part, even if they stop work on the case.

A Participant that leaves an Active embargo SHOULD be dropped by the CASE_MANAGER from its fan-out of further communication about the case.

Embargo Engagement and Adherence

We return to these concepts with the case_engagement attribute and the per-embargo consent rows described in Case Model. For the per-(participant, embargo) consent state machine, see Embargo Lifecycle.

These points mean that Participants need to track the status of other Participants. This status includes their adherence to the embargo and their engagement with the case.

Leaving an Embargo May Have Consequences

As we note in the CVD Guide, CVD is an iterated game, and actions have consequences. If a Participant leaves an embargo early in one case, this can affect how willing Participants are to cooperate in later cases.

A Participant's refusal to accept embargo terms MAY result in that Participant being left out of the CVD case entirely.

Participants SHOULD consider other Participants' history of cooperation when evaluating the terms of a proposed embargo.

Embargo Termination is Not the Same as Publication

Finally, embargo termination removes a constraint. It does not add an obligation.

Participants SHOULD NOT publish information about the vulnerability when there is an active embargo.

Participants MAY publish information about the vulnerability when there is no active embargo.

Embargo termination SHALL NOT be construed as an obligation to publish.

Adding Participants discusses how to decide whom to invite to a CVD case.

Doing It on the Wire

Reading path: You handle vulnerability reports and coordinate cases with other organizations

This page is part of See how a case moves.

Path overview