On Feb 12, 2016, at 12:50 PM, Booth, Harold <harold.booth@nist.gov> wrote:

We welcome and encourage participation from any vendor to provide us with this information. We will be happy to work with Debian to accept their CPE submissions for products that they release. What would help you to get started? We can set-up a quick

call if that would help, otherwise the cpe_dictionary@nist.gov email is the correct place for submissions.

Related to CPE, is another software identification scheme, Software ID (SWID) Tags (ISO 19770-2:2015) that we think provides more capability and benefit. We have a document currently in draft, NIST IR 8060 (http://csrc.nist.gov/publications/PubsDrafts.

html#NIST-IR-8060), that describes how to create and use SWID tags as well as some use cases. I mention the SWID tags since we can also auto generate CPEs from those, and we see SWID tags as longer term solution to the problem of software product
identification and inventory.

FYI: For longer-term identification of software components, I would suggest considering purls instead. These are *MUCH* simpler for identification of OSS components, which matters for the millions of OSS components that exist. The purl format is
supported in SPDX, CycloneDX, OSV, and many other formats.
Specification for purl here:
https://github.com/package-url/purl-spec

For Debian specifically, there's already a format specifically for it. An example (with extras):
pkg:deb/debian/curl@7.50.3-1?arch=i386&distro=jessie

The OpenSSF responded to CISA about naming issues in 2023 (I facilitated the report). Summary here:
https://openssf.org/blog/2023/12/11/openssf-responds-to-the-cisa-rfc-on-software-identification-ecosystem-analysis/
It notes that "Purl is currently in use as a de facto standard in many situations" and
the value of using DNS-based approaches (purl is one).

--- David A. Wheeler

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)