Skip to content

User Story 2022_104

As a Participant, I want to address multiple related vulnerabilities across multiple vendors simultaneously.

Notes

(as of v0.4.0) This story represents MPCVD in hard mode. But there are two ways to approach it: As a single case, or as individual cases with correlated states. The latter is essentially a post-split version of the former. Either way should work, but the Participants will need to maintain a degree of sync across cases if the case is split. GI messages carry most of the burden here.

Metadata

Following is additional information compiled from our original design materials. We are including it here for future reference and traceability.

  • Potential future process or service: Case merge or split
  • Roles: Participant
  • Phases: Reporting, Validation and Prioritization, Analysis and Remediation, Public Awareness, Deployment
  • Categories: Policy, Community
  • File: story_2022_104.md
  • Original ID: 128.0
  • 2022 Whitepaper ID: nan
  • Support Level: (as of v0.4.0) Allowed