Skip to content
How-to guide

How to Revise or Terminate an Embargo

Use this guide once a case already has an active embargo. A revision runs the same propose, accept, or reject cycle that established the embargo. A termination removes the embargo outright. You finish with the case at Embargo Management (EM) state EM.ACTIVE under new terms, or at EM.EXITED. A participant that no longer wants to be bound by the embargo can also withdraw from it. A withdrawal does not change the EM state of the case.


Prerequisites

  • A running Vultron instance you can drive. The demo containers are the quickest route — see Tutorial: Run the Receive-Report Demo for the two steps that get you a container shell.
  • An actor identity on that instance, holding the role each step names.
  • Working knowledge of the ActivityStreams verb, object, and target shape, summarized in Vultron and ActivityPub.
  • Working knowledge of the case model: the objects a case is made of, in The Case Model, and who is allowed to change them, in The CASE_MANAGER and the Case Ledger. Where a guide's messages are case-scoped, they route through the CASE_MANAGER and their results appear on the case ledger.

  • A case at EM.ACTIVE. See How to Establish an Embargo.

  • The Case Owner role, for activating a revision or terminating the embargo. Any participant can propose a revision.

Embargo Management is a model of its own

The Vultron protocol gives much detail about Embargo Management and about how the protocol expects participants to interact with embargoes. Read that section before designing embargo behavior.


The exchange

The flowchart below extends the establishment flow with the moves available once an embargo is active. The Terminate? branch is where an active embargo ends. The Propose? branch is where an active embargo changes.

---
title: Revising or Terminating an Active Embargo
---
flowchart TB
    subgraph as:Invite
        EmProposeEmbargo["Embargo Proposal (EP) / Embargo Revision Proposal (EV)<br/>Invite(EmbargoEvent)"]
    end
    subgraph participant answers
        EmAcceptEmbargo["Agree to the revision<br/>Accept(Invite(EmbargoEvent))"]
        EmRejectEmbargo["Refuse the revision<br/>Reject(Invite(EmbargoEvent))"]
    end
    subgraph Case Owner decides
        ActivateEmbargo["Embargo Revision Acceptance (EC)<br/>Add(EmbargoEvent)[target=VulnerabilityCase]"]
        RejectEmbargoProposal["Embargo Revision Rejection (EJ)<br/>Reject(EmbargoEvent)[target=VulnerabilityCase]"]
    end
    subgraph as:Remove
        RemoveEmbargoFromCase["Embargo Termination (ET)<br/>Remove(EmbargoEvent)"]
    end
    subgraph as:Announce
        AnnounceEmbargo["Announce the embargo terms<br/>Announce(EmbargoEvent)"]
    end
    start([Start]) --> t{Terminate?}
    t -->|n| p{Propose?}
    p -->|y| EmProposeEmbargo
    p -->|n| t
    EmProposeEmbargo --> EmAcceptEmbargo
    EmProposeEmbargo --> EmRejectEmbargo
    EmAcceptEmbargo --> d{Owner activates?}
    EmRejectEmbargo --> d
    d -->|y| ActivateEmbargo
    d -->|n| RejectEmbargoProposal
    ActivateEmbargo --> t
    RejectEmbargoProposal --> t
    t -->|y| RemoveEmbargoFromCase
    RemoveEmbargoFromCase --> AnnounceEmbargo
    AnnounceEmbargo --> exited([EM.EXITED])

Revise the terms

Embargo Revision Proposal (EV) is implemented in ActivityStreams as Invite(EmbargoEvent). An initial proposal, Embargo Proposal (EP), uses the same activity.

  1. Send Invite(EmbargoEvent) to the CASE_MANAGER, with the revised EmbargoEvent as its object and the CASE_MANAGER as its target. The case moves to EM.REVISE.

    Embargo Revision Proposal (EV)

    Proposes a revision to the terms of the active embargo. The wire form is the same as a first proposal; the receiver's EM state makes it a revision.

    • When… a Participant proposes revised terms for the active embargo
    • Send: Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase]
    • Send to: the CASE_MANAGER
    • Sent by: the CASE_MANAGER or an active participant
    • Distinguished by: EM state ACTIVE or REVISE
    • Reference: Embargo Revision Proposal (EV)
    Example activity
    {
      "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://certcc.github.io/Vultron/ns/context.jsonld",
        "https://w3id.org/security/data-integrity/v2"
      ],
      "type": "Invite",
      "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
      "name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
      "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "published": "2026-06-01T19:12:00.000000+00:00",
      "updated": "2026-06-01T19:12:00.000000+00:00",
      "summary": "We propose to extend the embargo on case 1 to 120 days.",
      "to": [
        "https://vultron.example/case-actors/vendorco-case-actor"
      ],
      "actor": "https://vultron.example/organizations/vendorco",
      "target": "https://vultron.example/case-actors/vendorco-case-actor",
      "object": {
        "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
        "type": "EmbargoEvent",
        "name": "Embargo for VendorCo Case #20260601",
        "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
        "startTime": "2026-06-01T19:12:00.000000+00:00",
        "endTime": "2026-09-29T00:00:00.000000+00:00",
        "published": "2026-06-01T19:12:00.000000+00:00",
        "updated": "2026-06-01T19:12:00.000000+00:00",
        "content": "We propose to embargo VendorCo Case #20260601 for 120 days."
      },
      "proof": {
        "@context": [
          "https://www.w3.org/ns/activitystreams",
          "https://certcc.github.io/Vultron/ns/context.jsonld",
          "https://w3id.org/security/data-integrity/v2"
        ],
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
        "proofPurpose": "assertionMethod",
        "created": "2026-06-01T19:12:00.000000+00:00",
        "proofValue": "z28Ts1Ti5BTXXvPx2U6s2HesycG8QcgVLvEmFYpShXecUKAPwbfW9sVu5v6CmmFc5ewFjppxVhDTKxhVP6SMoLA3s"
      }
    }
    
  2. Each participant answers with Agree to an embargo revision, Accept(Invite(EmbargoEvent)), or Refuse an embargo revision, Reject(Invite(EmbargoEvent)). Either answer records only the consent of that participant to the revision, so it carries no protocol shorthand. This rule also applies to an answer from the Case Owner. The active embargo does not change.

    Agree to an embargo revision

    Records the sender's own consent to the revision. The revision replaces the active embargo only when the Case Owner sends its decision.

    • When… a Participant agrees to a proposed embargo revision
    • Send: Accept(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase])
    • Send to: the CASE_MANAGER
    • Sent by: the invitee
    • Distinguished by: EM state REVISE
    • Reference: Agree to an embargo revision
    Example activity
    {
      "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://certcc.github.io/Vultron/ns/context.jsonld",
        "https://w3id.org/security/data-integrity/v2"
      ],
      "type": "Accept",
      "id": "urn:uuid:b87bd5e5-e4c3-46dc-ab5b-bb0cea856ce9",
      "name": "https://vultron.example/organizations/vendorco Accept https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
      "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
      "published": "2026-06-01T19:12:00.000000+00:00",
      "updated": "2026-06-01T19:12:00.000000+00:00",
      "to": "https://vultron.example/cases/1/participants",
      "actor": "https://vultron.example/organizations/vendorco",
      "object": {
        "type": "Invite",
        "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
        "name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
        "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
        "published": "2026-06-01T19:12:00.000000+00:00",
        "updated": "2026-06-01T19:12:00.000000+00:00",
        "summary": "We propose to extend the embargo on case 1 to 120 days.",
        "to": [
          "https://vultron.example/case-actors/vendorco-case-actor"
        ],
        "actor": "https://vultron.example/organizations/vendorco",
        "target": "https://vultron.example/case-actors/vendorco-case-actor",
        "object": {
          "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
          "type": "EmbargoEvent",
          "name": "Embargo for VendorCo Case #20260601",
          "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
          "startTime": "2026-06-01T19:12:00.000000+00:00",
          "endTime": "2026-09-29T00:00:00.000000+00:00",
          "published": "2026-06-01T19:12:00.000000+00:00",
          "updated": "2026-06-01T19:12:00.000000+00:00",
          "content": "We propose to embargo VendorCo Case #20260601 for 120 days."
        }
      },
      "proof": {
        "@context": [
          "https://www.w3.org/ns/activitystreams",
          "https://certcc.github.io/Vultron/ns/context.jsonld",
          "https://w3id.org/security/data-integrity/v2"
        ],
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
        "proofPurpose": "assertionMethod",
        "created": "2026-06-01T19:12:00.000000+00:00",
        "proofValue": "zAZLAytcYfxXJDm7oAvFcgbQ24xyR9WHf3qv91TXJ9je8Ryoa8AXzBJPPcDUig5JVSfk6nfT1TdkNRuJJwdroQzc"
      }
    }
    

    Refuse an embargo revision

    Records the sender's own refusal of the revision. The Case Owner keeps the prior terms by sending its decision.

    • When… a Participant refuses a proposed embargo revision
    • Send: Reject(Invite(EmbargoEvent)[target=Actor, context=VulnerabilityCase])
    • Send to: the CASE_MANAGER
    • Sent by: the invitee
    • Distinguished by: EM state REVISE
    • Reference: Refuse an embargo revision
    Example activity
    {
      "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://certcc.github.io/Vultron/ns/context.jsonld",
        "https://w3id.org/security/data-integrity/v2"
      ],
      "type": "Reject",
      "id": "urn:uuid:f928d8ab-7019-4574-914a-1b6b377eac24",
      "name": "https://vultron.example/organizations/vendorco Reject https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
      "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
      "published": "2026-06-01T19:12:00.000000+00:00",
      "updated": "2026-06-01T19:12:00.000000+00:00",
      "to": "https://vultron.example/cases/1/participants",
      "actor": "https://vultron.example/organizations/vendorco",
      "object": {
        "type": "Invite",
        "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
        "name": "https://vultron.example/organizations/vendorco Invite Embargo for VendorCo Case #20260601 to https://vultron.example/case-actors/vendorco-case-actor",
        "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
        "published": "2026-06-01T19:12:00.000000+00:00",
        "updated": "2026-06-01T19:12:00.000000+00:00",
        "summary": "We propose to extend the embargo on case 1 to 120 days.",
        "to": [
          "https://vultron.example/case-actors/vendorco-case-actor"
        ],
        "actor": "https://vultron.example/organizations/vendorco",
        "target": "https://vultron.example/case-actors/vendorco-case-actor",
        "object": {
          "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
          "type": "EmbargoEvent",
          "name": "Embargo for VendorCo Case #20260601",
          "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
          "startTime": "2026-06-01T19:12:00.000000+00:00",
          "endTime": "2026-09-29T00:00:00.000000+00:00",
          "published": "2026-06-01T19:12:00.000000+00:00",
          "updated": "2026-06-01T19:12:00.000000+00:00",
          "content": "We propose to embargo VendorCo Case #20260601 for 120 days."
        }
      },
      "proof": {
        "@context": [
          "https://www.w3.org/ns/activitystreams",
          "https://certcc.github.io/Vultron/ns/context.jsonld",
          "https://w3id.org/security/data-integrity/v2"
        ],
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
        "proofPurpose": "assertionMethod",
        "created": "2026-06-01T19:12:00.000000+00:00",
        "proofValue": "z4nry1wXgKo9hQ2uf9ih51Ys7FuAobE7TJtvsNBQXZihLmRo3Eao19Y2vC4cCwD88erjbGryMeQS74Vn7f2mxzm4J"
      }
    }
    
  3. When you judge that the revision has carried, send Embargo Revision Acceptance (EC), Add(EmbargoEvent), as Case Owner, with the revised EmbargoEvent as its object and the case as its target. Name the revision's Invite(EmbargoEvent) in inReplyTo. Then send Announce(EmbargoEvent). The revision replaces the active embargo. Your own consent to the revision is recorded too. If the revision ends no later than the embargo it replaces, every participant that agreed to the old terms is bound by the new ones too.

    Embargo Revision Acceptance (EC)

    Activates the revision for the case. It replaces the active embargo in the same register step.

    • When… the Case Owner decides to replace the active embargo with a proposed revision
    • Send: Add(EmbargoEvent)[target=VulnerabilityCase]
    • Send to: the CASE_MANAGER
    • Sent by: the Case Owner
    • Distinguished by: EM state REVISE
    • Reference: Embargo Revision Acceptance (EC)
    Example activity
    {
      "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://certcc.github.io/Vultron/ns/context.jsonld",
        "https://w3id.org/security/data-integrity/v2"
      ],
      "type": "Add",
      "id": "urn:uuid:1f3c5c2a-3890-47b4-a2b2-ff90df1e0966",
      "name": "https://vultron.example/organizations/vendorco Add Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
      "published": "2026-06-01T19:12:00.000000+00:00",
      "updated": "2026-06-01T19:12:00.000000+00:00",
      "actor": "https://vultron.example/organizations/vendorco",
      "target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "object": {
        "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
        "type": "EmbargoEvent",
        "name": "Embargo for VendorCo Case #20260601",
        "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
        "startTime": "2026-06-01T19:12:00.000000+00:00",
        "endTime": "2026-09-29T00:00:00.000000+00:00",
        "published": "2026-06-01T19:12:00.000000+00:00",
        "updated": "2026-06-01T19:12:00.000000+00:00",
        "content": "We propose to embargo VendorCo Case #20260601 for 120 days."
      },
      "proof": {
        "@context": [
          "https://www.w3.org/ns/activitystreams",
          "https://certcc.github.io/Vultron/ns/context.jsonld",
          "https://w3id.org/security/data-integrity/v2"
        ],
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
        "proofPurpose": "assertionMethod",
        "created": "2026-06-01T19:12:00.000000+00:00",
        "proofValue": "z3HRjnq2WZvnKodwEsUnEndQPrJkd42JyYZkLQgciqFsojfjV4TApxLXtkrf6GsxYJZKPQVBfKBp4xJgtKpErxyfB"
      }
    }
    

    Announce embargo

    Tells participants the terms of the active embargo. It proposes nothing.

    • When… the CASE_MANAGER states the terms of the embargo in force
    • Send: Announce(EmbargoEvent)[context=VulnerabilityCase]
    • Send to: a participant
    • Sent by: the CASE_MANAGER
    • Distinguished by: register status of the named embargo ACTIVE
    • Reference: Announce embargo
    Example activity
    {
      "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://certcc.github.io/Vultron/ns/context.jsonld",
        "https://w3id.org/security/data-integrity/v2"
      ],
      "type": "Announce",
      "id": "urn:uuid:69214ea7-3c09-4982-98b8-c3bfa77b4da4",
      "name": "https://vultron.example/organizations/vendorco Announce Embargo for VendorCo Case #20260601",
      "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
      "published": "2026-06-01T19:12:00.000000+00:00",
      "updated": "2026-06-01T19:12:00.000000+00:00",
      "to": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/participants",
      "actor": "https://vultron.example/organizations/vendorco",
      "object": {
        "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
        "type": "EmbargoEvent",
        "name": "Embargo for VendorCo Case #20260601",
        "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
        "startTime": "2026-06-01T19:12:00.000000+00:00",
        "endTime": "2026-08-30T00:00:00.000000+00:00",
        "published": "2026-06-01T19:12:00.000000+00:00",
        "updated": "2026-06-01T19:12:00.000000+00:00",
        "content": "We propose to embargo VendorCo Case #20260601 for 90 days."
      },
      "proof": {
        "@context": [
          "https://www.w3.org/ns/activitystreams",
          "https://certcc.github.io/Vultron/ns/context.jsonld",
          "https://w3id.org/security/data-integrity/v2"
        ],
        "type": "DataIntegrityProof",
        "cryptosuite": "eddsa-jcs-2022",
        "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
        "proofPurpose": "assertionMethod",
        "created": "2026-06-01T19:12:00.000000+00:00",
        "proofValue": "z4yCvpQfmqbpZokzy9Z6A4RQf8Yk94DYG1WGuPqKgoReWW9a7uw38iGw8PAr75HDjjjx6uvHUVdnamW6nFXaQSdRK"
      }
    }
    

A revision uses the same activities as an initial proposal. The receiver uses the EM state of the case to distinguish a revision from an initial proposal. A proposal that arrives while the embargo is active is a revision (MSM-02).

To keep the current terms, send Embargo Revision Rejection (EJ), Reject(EmbargoEvent), with the same object, target and inReplyTo as Case Owner instead. The case returns to EM.ACTIVE under the original terms. The consent of every participant stays the same. The embargo does not lapse because a revision failed. One exception applies: if the case is public, an exploit is public, or attacks are observed when you reject the last open revision, the CASE_MANAGER also ends the embargo in the same act (EMB-04-002).

Embargo Revision Rejection (EJ)

Rejects the revision for the case. The active embargo stays in force on its prior terms, unless the case is public, an exploit is public or attacks are observed, when the CASE_MANAGER also ends it.

  • When… the Case Owner decides to reject a proposed revision
  • Send: Reject(EmbargoEvent)[target=VulnerabilityCase]
  • Send to: the CASE_MANAGER
  • Sent by: the Case Owner
  • Distinguished by: EM state REVISE
  • Reference: Embargo Revision Rejection (EJ)
Example activity
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://certcc.github.io/Vultron/ns/context.jsonld",
    "https://w3id.org/security/data-integrity/v2"
  ],
  "type": "Reject",
  "id": "urn:uuid:9bc8e575-53b1-4788-8328-855d64c5ebe8",
  "name": "https://vultron.example/organizations/vendorco Reject Embargo for VendorCo Case #20260601 to urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "inReplyTo": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_proposals/2",
  "published": "2026-06-01T19:12:00.000000+00:00",
  "updated": "2026-06-01T19:12:00.000000+00:00",
  "actor": "https://vultron.example/organizations/vendorco",
  "target": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "object": {
    "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-09-29T00:00:00+00:00",
    "type": "EmbargoEvent",
    "name": "Embargo for VendorCo Case #20260601",
    "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
    "startTime": "2026-06-01T19:12:00.000000+00:00",
    "endTime": "2026-09-29T00:00:00.000000+00:00",
    "published": "2026-06-01T19:12:00.000000+00:00",
    "updated": "2026-06-01T19:12:00.000000+00:00",
    "content": "We propose to embargo VendorCo Case #20260601 for 120 days."
  },
  "proof": {
    "@context": [
      "https://www.w3.org/ns/activitystreams",
      "https://certcc.github.io/Vultron/ns/context.jsonld",
      "https://w3id.org/security/data-integrity/v2"
    ],
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
    "proofPurpose": "assertionMethod",
    "created": "2026-06-01T19:12:00.000000+00:00",
    "proofValue": "z3rCVev1krWPyaHokqwU72KxJ5pWSaaZ2e3xU8Rfboo2aojnWYxZkC9ys797YK9nNqcYxf56gycoaFYaAAPQ266Ef"
  }
}

Terminate the embargo

Embargo Termination (ET) is implemented in ActivityStreams as Remove(EmbargoEvent).

Send Remove(EmbargoEvent). The case moves to EM.EXITED, with immediate effect.

Set content to the reason that the embargo ends. Use EARLY to end the embargo before its end time. Use END_TIME_REACHED after its end time has passed. A receiver refuses a Remove(EmbargoEvent) whose content has any other value. A receiver also refuses an END_TIME_REACHED that is sent before the end time. If you want a human-readable account, put it in summary. The protocol does not read summary.

With EARLY, you may also use terminationCause to say why the embargo ends. Set its kind to one of these:

  • FIX_READY, with vendors listing the actor IDs of the Vendors whose readiness made the quorum, each once.
  • FIX_DEPLOYED, with no detail.
  • OTHER, with no detail. Give the account in summary.

The CASE_MANAGER records the cause as you give it. If you end the embargo with the terminate-embargo trigger, give the cause as cause in the request body. Use the same kind and detail. An EARLY request with no cause is sent with an OTHER cause. The trigger refuses a THREAT_SIGNAL cause, and any cause with END_TIME_REACHED. Do not send terminationCause with END_TIME_REACHED. A receiver refuses a Remove(EmbargoEvent) with an unknown kind, a missing or malformed detail, or a cause on END_TIME_REACHED.

Do not use THREAT_SIGNAL. The CASE_MANAGER refuses THREAT_SIGNAL on every Remove(EmbargoEvent) except its own. To end the embargo because the vulnerability is public, an exploit is public or attacks are observed, send a case status update setting P, X or A instead. The CASE_MANAGER then ends the embargo itself, with a THREAT_SIGNAL cause naming the signals the case carries.

Embargo Termination (ET)

Terminates the embargo with immediate effect.

  • When… the Case Owner terminates the active embargo
  • Send: Remove(EmbargoEvent)
  • Send to: the CASE_MANAGER
  • Sent by: the CASE_MANAGER or the Case Owner
  • Reference: Embargo Termination (ET)
Example activity
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://certcc.github.io/Vultron/ns/context.jsonld",
    "https://w3id.org/security/data-integrity/v2"
  ],
  "type": "Remove",
  "id": "urn:uuid:7eff95a9-44a6-4079-8313-aa90e5526cdd",
  "name": "https://vultron.example/organizations/vendorco Remove Embargo for VendorCo Case #20260601 from urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "published": "2026-06-01T19:12:00.000000+00:00",
  "updated": "2026-06-01T19:12:00.000000+00:00",
  "content": "EARLY",
  "summary": "The embargo ended before its end time.",
  "actor": "https://vultron.example/organizations/vendorco",
  "origin": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "object": {
    "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
    "type": "EmbargoEvent",
    "name": "Embargo for VendorCo Case #20260601",
    "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
    "startTime": "2026-06-01T19:12:00.000000+00:00",
    "endTime": "2026-08-30T00:00:00.000000+00:00",
    "published": "2026-06-01T19:12:00.000000+00:00",
    "updated": "2026-06-01T19:12:00.000000+00:00",
    "content": "We propose to embargo VendorCo Case #20260601 for 90 days."
  },
  "terminationCause": {
    "kind": "FIX_DEPLOYED"
  },
  "proof": {
    "@context": [
      "https://www.w3.org/ns/activitystreams",
      "https://certcc.github.io/Vultron/ns/context.jsonld",
      "https://w3id.org/security/data-integrity/v2"
    ],
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "https://vultron.example/organizations/vendorco#main-key",
    "proofPurpose": "assertionMethod",
    "created": "2026-06-01T19:12:00.000000+00:00",
    "proofValue": "zVuueqE4HwQ8imN8DY6qXgnYBJktQL9nQ5CsQk6idMBrgEzEaPxqhUi3VhSyyzhWDfJ14JkFZBySE5akUCcjbLrw"
  }
}

Only the CASE_MANAGER changes the case's EM state (EP-09-008). If you are not the CASE_MANAGER, address Remove(EmbargoEvent) to the CASE_MANAGER. If you are the CASE_MANAGER, address Remove(EmbargoEvent) to every other participant and never to yourself (EMB-19-001).

Tell a participant the embargo has ended

Tells one participant that the embargo has ended, with immediate effect. The CASE_MANAGER sends one to each participant other than itself, naming the Case Owner in attributedTo and the Case Owner's request in inReplyTo when the Case Owner asked for the termination.

  • When… the CASE_MANAGER ends the active embargo, on its own decision or on the Case Owner's
  • Send: Remove(EmbargoEvent)
  • Send to: a participant
  • Sent by: the CASE_MANAGER
  • Reference: Tell a participant the embargo has ended
Example activity
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://certcc.github.io/Vultron/ns/context.jsonld",
    "https://w3id.org/security/data-integrity/v2"
  ],
  "type": "Remove",
  "id": "urn:uuid:bf0aab95-bcd6-4b3e-ac09-554ffbc3243a",
  "name": "https://vultron.example/case-actors/vendorco-case-actor Remove Embargo for VendorCo Case #20260601 from urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "inReplyTo": "urn:uuid:6c3be136-e8db-4a8f-91e6-c8a97aa0b7b7",
  "published": "2026-06-01T19:12:00.000000+00:00",
  "updated": "2026-06-01T19:12:00.000000+00:00",
  "content": "EARLY",
  "summary": "The embargo ended before its end time.",
  "to": [
    "https://vultron.example/organizations/coordinator"
  ],
  "attributedTo": "https://vultron.example/organizations/vendorco",
  "actor": "https://vultron.example/case-actors/vendorco-case-actor",
  "origin": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "object": {
    "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
    "type": "EmbargoEvent",
    "name": "Embargo for VendorCo Case #20260601",
    "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
    "startTime": "2026-06-01T19:12:00.000000+00:00",
    "endTime": "2026-08-30T00:00:00.000000+00:00",
    "published": "2026-06-01T19:12:00.000000+00:00",
    "updated": "2026-06-01T19:12:00.000000+00:00",
    "content": "We propose to embargo VendorCo Case #20260601 for 90 days."
  },
  "proof": {
    "@context": [
      "https://www.w3.org/ns/activitystreams",
      "https://certcc.github.io/Vultron/ns/context.jsonld",
      "https://w3id.org/security/data-integrity/v2"
    ],
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
    "proofPurpose": "assertionMethod",
    "created": "2026-06-01T19:12:00.000000+00:00",
    "proofValue": "zJvydv4hcqsqaiKinphYB17ApHayqHDC6aryz8Km4JmDamuVrLucn7DTgy4VaQjw5rQBzicDkvzhBFdtRjQwDM1X"
  }
}

The CASE_MANAGER commits the termination to the case ledger and sends the entry to every participant. Your own copy of the case moves to EM.EXITED when the CASE_MANAGER's ledger entry for the termination reaches you. Your copy does not move when you send.

When the CASE_MANAGER applies a Case Owner's termination that arrives before the end time, it then sends Announce(EmbargoEvent) naming the terminated embargo. It sends this announcement to every other active participant except a Closed Participant, the Case Owner included (EMB-19-001, CM-23-004). A termination the CASE_MANAGER starts itself sends no Announce(EmbargoEvent). The CASE_MANAGER also sends no Announce(EmbargoEvent) for a Case Owner's termination that arrives after the end time. In that case, the CASE_MANAGER's own end-time check has already ended the embargo when the Remove(EmbargoEvent) arrives.

Announce embargo termination

Tells the active participants other than the CASE_MANAGER and any Closed Participant that the embargo it names is terminated. It proposes nothing.

  • When… the CASE_MANAGER has applied an Embargo Termination a Case Owner sent before the end time
  • Send: Announce(EmbargoEvent)[context=VulnerabilityCase]
  • Send to: a participant
  • Sent by: the CASE_MANAGER
  • Distinguished by: register status of the named embargo TERMINATED
  • Reference: Announce embargo termination
Example activity
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://certcc.github.io/Vultron/ns/context.jsonld",
    "https://w3id.org/security/data-integrity/v2"
  ],
  "type": "Announce",
  "id": "urn:uuid:1dbd4608-ec99-4fbc-9b55-caf8512cd9b8",
  "name": "https://vultron.example/case-actors/vendorco-case-actor Announce Embargo for VendorCo Case #20260601",
  "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "published": "2026-06-01T19:12:00.000000+00:00",
  "updated": "2026-06-01T19:12:00.000000+00:00",
  "to": [
    "https://vultron.example/organizations/vendorco",
    "https://vultron.example/organizations/coordinator",
    "https://vultron.example/users/finndervul"
  ],
  "actor": "https://vultron.example/case-actors/vendorco-case-actor",
  "object": {
    "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
    "type": "EmbargoEvent",
    "name": "Embargo for VendorCo Case #20260601",
    "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
    "startTime": "2026-06-01T19:12:00.000000+00:00",
    "endTime": "2026-08-30T00:00:00.000000+00:00",
    "published": "2026-06-01T19:12:00.000000+00:00",
    "updated": "2026-06-01T19:12:00.000000+00:00",
    "content": "We propose to embargo VendorCo Case #20260601 for 90 days."
  },
  "proof": {
    "@context": [
      "https://www.w3.org/ns/activitystreams",
      "https://certcc.github.io/Vultron/ns/context.jsonld",
      "https://w3id.org/security/data-integrity/v2"
    ],
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "https://vultron.example/case-actors/vendorco-case-actor#main-key",
    "proofPurpose": "assertionMethod",
    "created": "2026-06-01T19:12:00.000000+00:00",
    "proofValue": "zVhkFEbgoWa4yDaTamkQWChf6Gyn3khE1HEB9vAQN1KLUTPZz6vTqRQag9f1kKicfrTPzrhWrGokSeBRuKKNUeGc"
  }
}

Termination is not a revision

Remove(EmbargoEvent) ends the embargo now. It does not propose a shorter embargo. If you want the embargo to end sooner but still exist, propose a revision with an earlier end time.

An embargo also terminates when the case reaches public awareness. See Early Termination.

End the embargo at its end time

You do not need to send anything when the end time passes. The CASE_MANAGER ends the embargo with END_TIME_REACHED the next time it handles the case. To end the embargo on time without that wait, have the CASE_MANAGER call the terminate-embargo trigger with reason set to END_TIME_REACHED, for example from a Sentinel that watches embargo timers. If the embargo has already ended, the trigger answers with no activity and commits nothing.


Withdraw from the embargo

A participant bound by the active embargo can stop complying with it at any time (VP-13-017). Withdrawal is implemented in ActivityStreams as Leave(EmbargoEvent), with the embargo in force as its object and the case as its context (MSM-07-010). A withdrawal is not an answer to an Invite, so you do not need an Invite(EmbargoEvent) to withdraw. A Reporter whose consent was recorded when the case was created can withdraw too.

  1. Call withdraw-embargo with the case's ID. The trigger reads the embargo in force from your copy of the case.
  2. The trigger sends Leave(EmbargoEvent) to the CASE_MANAGER. The CASE_MANAGER marks your consent row for the embargo in force DECLINED. It also marks DECLINED every row that you had marked AGREED for an open revision. The reason is that each open revision replaces the embargo that you left. The CASE_MANAGER commits the withdrawal to the case ledger. Then it commits each consent row that it declines as a separate entry. Your own copy of the case changes when those entries reach you.

Withdraw from embargo

Ends the sender's own consent to the embargo in force, and to any revision it had agreed to. The embargo stays in force for every other participant.

  • When… a Participant bound by the active embargo stops complying with it
  • Send: Leave(EmbargoEvent)[context=VulnerabilityCase]
  • Send to: the CASE_MANAGER
  • Sent by: a participant
  • Reference: Withdraw from embargo
Example activity
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://certcc.github.io/Vultron/ns/context.jsonld",
    "https://w3id.org/security/data-integrity/v2"
  ],
  "type": "Leave",
  "id": "urn:uuid:51c5ebbb-9095-47be-b49c-b854df2a2ec6",
  "name": "https://vultron.example/users/finndervul Leave Embargo for VendorCo Case #20260601",
  "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
  "published": "2026-06-01T19:12:00.000000+00:00",
  "updated": "2026-06-01T19:12:00.000000+00:00",
  "to": "https://vultron.example/case-actors/vendorco-case-actor",
  "actor": "https://vultron.example/users/finndervul",
  "object": {
    "id": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a/embargo_events/2026-08-30T00:00:00+00:00",
    "type": "EmbargoEvent",
    "name": "Embargo for VendorCo Case #20260601",
    "context": "urn:uuid:e54656f1-e9c8-4ec5-9a69-6cbf725e510a",
    "startTime": "2026-06-01T19:12:00.000000+00:00",
    "endTime": "2026-08-30T00:00:00.000000+00:00",
    "published": "2026-06-01T19:12:00.000000+00:00",
    "updated": "2026-06-01T19:12:00.000000+00:00",
    "content": "We propose to embargo VendorCo Case #20260601 for 90 days."
  },
  "proof": {
    "@context": [
      "https://www.w3.org/ns/activitystreams",
      "https://certcc.github.io/Vultron/ns/context.jsonld",
      "https://w3id.org/security/data-integrity/v2"
    ],
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "verificationMethod": "https://vultron.example/users/finndervul#main-key",
    "proofPurpose": "assertionMethod",
    "created": "2026-06-01T19:12:00.000000+00:00",
    "proofValue": "zgcq1sCotoFPHUiEh52q2mTCXJEu2cj4Vz99Wc4qWkNLHZEPaUC6sEPK5avq1TNtKV4yRWLTcufd8TfcRns71XE4"
  }
}

The embargo stays in force for every other participant, and the case's EM state does not move. You are no longer bound by the embargo. The CASE_MANAGER therefore stops sending you case content until the embargo ends, or until you are invited to it again and agree (CM-10-005).

The trigger refuses the withdrawal in three cases:

  • No embargo is in force.
  • Your consent row for the embargo in force is not AGREED. To refuse terms that you never agreed to, reject the Invite instead (see How to Establish an Embargo).
  • You are the Case Owner. A Case Owner ends an embargo by terminating it, as the previous section shows.

A Reject never withdraws

Reject(Invite(EmbargoEvent)) refuses terms. It is not a way to leave an embargo that you agreed to. A Reject of the embargo in force from an AGREED row is refused. A reject-embargo with no proposal_id rejects an open revision, and your consent to the embargo in force stays AGREED (MSM-07-015).


Verify

What you sent What to confirm
Invite(EmbargoEvent) on an active embargo The case em_state is REVISE.
Add(EmbargoEvent) with the case as target, as Case Owner The case em_state is ACTIVE and the active embargo carries the new terms.
Reject(EmbargoEvent) with the case as target, as Case Owner The case em_state is ACTIVE and the terms are unchanged.
Reject(Invite(EmbargoEvent)) on a revision Your consent row for the revision is DECLINED. The case em_state is still REVISE.
Remove(EmbargoEvent) Once the CASE_MANAGER's ledger entry arrives, the case em_state is EXITED and no embargo is active.
Leave(EmbargoEvent) Once the CASE_MANAGER's ledger entry arrives, your consent row for the embargo in force is DECLINED. The case em_state does not change.

See it end to end

Try it: vultron-demo manage-embargo

vultron-demo manage-embargo

Or with Docker Compose:

DEMO=manage-embargo docker compose -f docker/docker-compose.yml run --rm demo

The scenario runs an activate-then-terminate path and a reject-then-repropose path.


Further reading