Skip to content

Standards Crosswalks

This page is not normative

This page is not considered a core part of the Vultron Protocol as proposed in the main documentation. Although within the page we might provide guidance in terms of SHOULD, MUST, etc., the content here is not normative.

Three ISO/IEC standards, one prioritization framework, and one advisory format overlap with the Vultron Protocol. Each ISO/IEC crosswalk below maps that document's clauses to two places: the explanation page that covers the same ground, and the section of the Vultron Protocol Specification that states the normative requirement. A program that already follows one of these standards can use its crosswalk to find which protocol behavior each clause it satisfies corresponds to. Each crosswalk opens with a link to the document it maps. The CSAF 2.1 crosswalk maps concepts instead of clauses, because CSAF is a document format and not a process standard.

  • ISO 30111 — Clause-by-clause mapping of ISO/IEC 30111:2019 vulnerability handling processes to the Vultron Protocol's states, messages, and specification sections.
  • ISO 29147 — Clause-by-clause mapping of ISO/IEC 29147:2018 vulnerability disclosure to the Vultron Protocol's states, messages, and specification sections.
  • ISO 5895 — Clause-by-clause mapping of ISO/IEC TR 5895:2022 multi-party coordinated vulnerability disclosure to the Vultron Protocol's states, messages, and specification sections.
  • CSAF 2.1 Crosswalk
    • CSAF 2.1 and Vultron — How the Common Security Advisory Framework (CSAF) 2.1 draft relates to a Vultron case, and a summary of where the two models are the same, close, or different.
    • Proposals — Changes that the Common Security Advisory Framework (CSAF) 2.1 draft and the Vultron Protocol could make, each with its reason and its cost if nothing changes.
    • Conclusions — What the comparison of the Common Security Advisory Framework (CSAF) 2.1 draft with Vultron shows, and the follow-up work it opens on each side.
    • Concept Mapping — Each Vultron concept with its counterpart in the Common Security Advisory Framework (CSAF) 2.1 draft, the granularity of the match, and the type of mapping in each direction.
    • Coverage Differences — Concepts that Vultron has and the Common Security Advisory Framework (CSAF) 2.1 draft does not, and concepts that CSAF has and Vultron does not.
  • SSVC Crosswalk — A crosswalk of the Vultron Protocol against Stakeholder-Specific Vulnerability Categorization (SSVC).

The specification's own account of how it relates to these standards is §1.3 Relationship to Existing Standards.

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

This page is part of Map it onto what you already do.

Before this page:

After this page:

Back to the start of this reading path