idnits 2.17.1 draft-ietf-sacm-coswid-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 4 instances of too long lines in the document, the longest one being 11 characters in excess of 72. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (1 May 2020) is 1456 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Link' is mentioned on line 1940, but not defined == Missing Reference: 'RFC-AAAA' is mentioned on line 2557, but not defined ** Obsolete normative reference: RFC 7049 (Obsoleted by RFC 8949) -- Duplicate reference: RFC8126, mentioned in 'RFC8126', was also mentioned in 'BCP26'. ** Obsolete normative reference: RFC 8152 (Obsoleted by RFC 9052, RFC 9053) -- Possible downref: Non-RFC (?) normative reference: ref. 'SAM' -- Possible downref: Non-RFC (?) normative reference: ref. 'SEMVER' -- Possible downref: Non-RFC (?) normative reference: ref. 'SWID' == Outdated reference: A later version (-07) exists of draft-birkholz-rats-tuda-02 Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SACM Working Group H. Birkholz 3 Internet-Draft Fraunhofer SIT 4 Intended status: Standards Track J. Fitzgerald-McKay 5 Expires: 2 November 2020 Department of Defense 6 C. Schmidt 7 The MITRE Corporation 8 D. Waltermire 9 NIST 10 1 May 2020 12 Concise Software Identification Tags 13 draft-ietf-sacm-coswid-15 15 Abstract 17 ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an 18 extensible XML-based structure to identify and describe individual 19 software components, patches, and installation bundles. SWID tag 20 representations can be too large for devices with network and storage 21 constraints. This document defines a concise representation of SWID 22 tags: Concise SWID (CoSWID) tags. CoSWID supports the same features 23 as SWID tags, as well as additional semantics that allow CoSWIDs to 24 describe additional types of information, all in a more memory 25 efficient format. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on 2 November 2020. 44 Copyright Notice 46 Copyright (c) 2020 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 51 license-info) in effect on the date of publication of this document. 52 Please review these documents carefully, as they describe your rights 53 and restrictions with respect to this document. Code Components 54 extracted from this document must include Simplified BSD License text 55 as described in Section 4.e of the Trust Legal Provisions and are 56 provided without warranty as described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. The SWID and CoSWID Tag Lifecycle . . . . . . . . . . . . 4 62 1.2. Concise SWID Format . . . . . . . . . . . . . . . . . . . 7 63 1.3. Requirements Notation . . . . . . . . . . . . . . . . . . 7 64 2. Concise SWID Data Definition . . . . . . . . . . . . . . . . 7 65 2.1. Character Encoding . . . . . . . . . . . . . . . . . . . 8 66 2.2. Concise SWID Extensions . . . . . . . . . . . . . . . . . 9 67 2.3. The concise-swid-tag Map . . . . . . . . . . . . . . . . 11 68 2.4. concise-swid-tag Co-constraints . . . . . . . . . . . . . 16 69 2.5. The global-attributes Group . . . . . . . . . . . . . . . 16 70 2.6. The entity-entry Map . . . . . . . . . . . . . . . . . . 17 71 2.7. The link-entry Map . . . . . . . . . . . . . . . . . . . 19 72 2.8. The software-meta-entry Map . . . . . . . . . . . . . . . 23 73 2.9. The Resource Collection Definition . . . . . . . . . . . 26 74 2.9.1. The hash-entry Array . . . . . . . . . . . . . . . . 26 75 2.9.2. The resource-collection Group . . . . . . . . . . . . 26 76 2.9.3. The payload-entry Map . . . . . . . . . . . . . . . . 30 77 2.9.4. The evidence-entry Map . . . . . . . . . . . . . . . 30 78 2.10. Full CDDL Definition . . . . . . . . . . . . . . . . . . 31 79 3. Determining the Type of CoSWID . . . . . . . . . . . . . . . 37 80 4. CoSWID Indexed Label Values . . . . . . . . . . . . . . . . . 37 81 4.1. Version Scheme . . . . . . . . . . . . . . . . . . . . . 37 82 4.2. Entity Role Values . . . . . . . . . . . . . . . . . . . 39 83 4.3. Link Ownership Values . . . . . . . . . . . . . . . . . . 41 84 4.4. Link Rel Values . . . . . . . . . . . . . . . . . . . . . 42 85 4.5. Link Use Values . . . . . . . . . . . . . . . . . . . . . 44 86 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 87 5.1. CoSWID Items Registry . . . . . . . . . . . . . . . . . . 44 88 5.2. SWID/CoSWID Value Registries . . . . . . . . . . . . . . 47 89 5.2.1. Registration Proceedures . . . . . . . . . . . . . . 48 90 5.2.2. Private Use of Index and Name Values . . . . . . . . 48 91 5.2.3. Expert Review Guidelines . . . . . . . . . . . . . . 48 92 5.2.4. SWID/CoSWID Version Scheme Value Registry . . . . . . 49 93 5.2.5. SWID/CoSWID Entity Role Value Registry . . . . . . . 50 94 5.2.6. SWID/CoSWID Link Ownership Value Registry . . . . . . 52 95 5.2.7. SWID/CoSWID Link Relationship Value Registry . . . . 53 96 5.2.8. SWID/CoSWID Link Use Value Registry . . . . . . . . . 54 98 5.3. swid+cbor Media Type Registration . . . . . . . . . . . . 55 99 5.4. CoAP Content-Format Registration . . . . . . . . . . . . 57 100 5.5. CBOR Tag Registration . . . . . . . . . . . . . . . . . . 57 101 5.6. URI Scheme Registrations . . . . . . . . . . . . . . . . 57 102 5.6.1. "swid" URI Scheme Registration . . . . . . . . . . . 57 103 5.6.2. "swidpath" URI Scheme Registration . . . . . . . . . 58 104 5.7. CoSWID Model for use in SWIMA Registration . . . . . . . 59 105 6. Security Considerations . . . . . . . . . . . . . . . . . . . 60 106 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61 107 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 62 108 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 67 109 9.1. Normative References . . . . . . . . . . . . . . . . . . 67 110 9.2. Informative References . . . . . . . . . . . . . . . . . 69 111 Appendix A. Signed Concise SWID Tags using COSE . . . . . . . . 70 112 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 71 114 1. Introduction 116 SWID tags, as defined in ISO-19770-2:2015 [SWID], provide a 117 standardized XML-based record format that identifies and describes a 118 specific release of software, a patch, or an installation bundle, 119 which are referred to as software components in this document. 120 Different software components, and even different releases of a 121 particular software component, each have a different SWID tag record 122 associated with them. SWID tags are meant to be flexible and able to 123 express a broad set of metadata about a software component. 125 SWID tags are used to support a number of processes including but not 126 limited to: 128 * Software Inventory Management, a part of a Software Asset 129 Management [SAM] process, which requires an accurate list of 130 discernible deployed software components. 132 * Vulnerability Assessment, which requires a semantic link between 133 standardized vulnerability descriptions and software components 134 installed on IT-assets [X.1520]. 136 * Remote Attestation, which requires a link between reference 137 integrity measurements (RIM) and security logs of measured 138 software components [I-D.birkholz-rats-tuda]. 140 While there are very few required fields in SWID tags, there are many 141 optional fields that support different uses. A SWID tag consisting 142 of only required fields might be a few hundred bytes in size; 143 however, a tag containing many of the optional fields can be many 144 orders of magnitude larger. Thus, real-world instances of SWID tags 145 can be fairly large, and the communication of SWID tags in usage 146 scenarios, such as those described earlier, can cause a large amount 147 of data to be transported. This can be larger than acceptable for 148 constrained devices and networks. Concise SWID (CoSWID) tags 149 significantly reduce the amount of data transported as compared to a 150 typical SWID tag. This reduction is enabled through the use of the 151 Concise Binary Object Representation (CBOR) [RFC7049], which maps the 152 human-readable labels of SWID data items to more concise integer 153 labels (indices). The use of CBOR to express SWID information in 154 CoSWID tags allows both CoSWID and SWID tags to be part of an 155 enterprise security solution for a wider range of endpoints and 156 environments. 158 1.1. The SWID and CoSWID Tag Lifecycle 160 In addition to defining the format of a SWID tag record, ISO/IEC 161 19770-2:2015 defines requirements concerning the SWID tag lifecycle. 162 Specifically, when a software component is installed on an endpoint, 163 that software component's SWID tag is also installed. Likewise, when 164 the software component is uninstalled or replaced, the SWID tag is 165 deleted or replaced, as appropriate. As a result, ISO/IEC 166 19770-2:2015 describes a system wherein there is a correspondence 167 between the set of installed software components on an endpoint, and 168 the presence of the corresponding SWID tags for these components on 169 that endpoint. CoSWIDs share the same lifecycle requirements as a 170 SWID tag. 172 The SWID specification and supporting guidance provided in NIST 173 Internal Report (NISTIR) 8060: Guidelines for the Creation of 174 Interoperable SWID Tags [SWID-GUIDANCE] defines four types of SWID 175 tags: primary, patch, corpus, and supplemental. The following text 176 is paraphrased from these sources. 178 1. Primary Tag - A SWID or CoSWID tag that identifies and describes 179 an installed software component on an endpoint. A primary tag is 180 intended to be installed on an endpoint along with the 181 corresponding software component. 183 2. Patch Tag - A SWID or CoSWID tag that identifies and describes an 184 installed patch that has made incremental changes to a software 185 component installed on an endpoint. A patch tag is intended to 186 be installed on an endpoint along with the corresponding software 187 component patch. 189 3. Corpus Tag - A SWID or CoSWID tag that identifies and describes 190 an installable software component in its pre-installation state. 191 A corpus tag can be used to represent metadata about an 192 installation package or installer for a software component, a 193 software update, or a patch. 195 4. Supplemental Tag - A SWID or CoSWID tag that allows additional 196 information to be associated with a referenced SWID tag. This 197 allows tools and users to record their own metadata about a 198 software component without modifying SWID primary or patch tags 199 created by a software provider. 201 The type of a tag is determined by specific data elements, which are 202 discussed in Section 3. 204 Corpus, primary, and patch tags have similar functions in that 205 they describe the existence and/or presence of different types of 206 software components (e.g., software installers, software 207 installations, software patches), and, potentially, different 208 states of these software components. Supplemental tags have the 209 same structure as other tags, but are used to provide information 210 not contained in the referenced corpus, primary, and patch tags. 211 All four tag types come into play at various points in the 212 software lifecycle and support software management processes that 213 depend on the ability to accurately determine where each software 214 component is in its lifecycle. 216 +------------+ 217 v | 218 Software Software Software Software Software 219 Deployment -> Installation -> Patching -> Upgrading -> Removal 221 Corpus Primary Primary xPrimary xPrimary 222 Supplemental Supplemental Supplemental xSupplemental xSuplemental 223 Patch xPatch 224 Primary 225 Supplemental 227 Figure 1: Use of Tag Types in the Software Lifecycle 229 Figure 1 illustrates the steps in the software lifecycle and the 230 relationships among those lifecycle events supported by the four 231 types of SWID and CoSWID tags. The figure identifies the types of 232 tags that can be deployed and previously deployed tags that are 233 typically removed (indicated by an "x" prefix) at each lifecycle 234 stage, as follows: 236 - Software Deployment. Before the software component is 237 installed (i.e., pre-installation), and while the product is 238 being deployed, a corpus tag provides information about the 239 installation files and distribution media (e.g., CD/DVD, 240 distribution package). 242 - Software Installation. A primary tag will be installed with 243 the software component (or subsequently created) to uniquely 244 identify and describe the software component. Supplemental 245 tags are created to augment primary tags with additional site- 246 specific or extended information. While not illustrated in the 247 figure, patch tags can also be installed during software 248 installation to provide information about software fixes 249 deployed along with the base software installation. 251 - Software Patching. A new patch tag is provided, when a patch 252 is applied to the software component, supplying details about 253 the patch and its dependencies. While not illustrated in the 254 figure, a corpus tag can also provide information about the 255 patch installer and patching dependencies that need to be 256 installed before the patch. 258 - Software Upgrading. As a software component is upgraded to a 259 new version, new primary and supplemental tags replace existing 260 tags, enabling timely and accurate tracking of updates to 261 software inventory. While not illustrated in the figure, a 262 corpus tag can also provide information about the upgrade 263 installer and dependencies that need to be installed before the 264 upgrade. 266 - Software Removal. Upon removal of the software component, 267 relevant SWID tags are removed. This removal event can trigger 268 timely updates to software inventory reflecting the removal of 269 the product and any associated patch or supplemental tags. 271 As illustrated in the figure, supplemental tags can be associated 272 with any corpus, primary, or patch tag to provide additional metadata 273 about an installer, installed software, or installed patch 274 respectively. 276 Understanding the use of CoSWIDs in the software lifecycle provides a 277 basis for understanding the information provided in a CoSWID and the 278 associated semantics of this information. Each of the different SWID 279 and CoSWID tag types provide different sets of information. For 280 example, a "corpus tag" is used to describe a software component's 281 installation image on an installation media, while a "patch tag" is 282 meant to describe a patch that modifies some other software 283 component. 285 1.2. Concise SWID Format 287 This document defines the CoSWID tag format, which is based on CBOR. 288 CBOR-based CoSWID tags offer a more concise representation of SWID 289 information as compared to the XML-based SWID tag representation in 290 ISO-19770-2:2015. The structure of a CoSWID is described via the 291 Concise Data Definition Language (CDDL) [RFC8610]. The resulting 292 CoSWID data definition is aligned to the information able to be 293 expressed with the XML schema definition of ISO-19770-2:2015 [SWID]. 294 This alignment allows both SWID and CoSWID tags to represent a common 295 set of software component information and allows CoSWID tags to 296 support the same uses as a SWID tag. To achieve this end, the CDDL 297 representation includes every SWID tag field and attribute. 299 The vocabulary, i.e., the CDDL names of the types and members used in 300 the CoSWID data definition, are mapped to more concise labels 301 represented as small integer values (indices). The names used in the 302 CDDL data definition and the mapping to the CBOR representation using 303 integer indices is based on the vocabulary of the XML attribute and 304 element names defined in ISO/IEC 19770-2:2015. 306 1.3. Requirements Notation 308 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 309 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 310 "OPTIONAL" in this document are to be interpreted as described in 311 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 312 capitals, as shown here. 314 2. Concise SWID Data Definition 316 The following describes the general rules and processes for encoding 317 data using CDDL representation. Prior familiarity with CBOR and CDDL 318 concepts will be helpful in understanding this CoSWID data 319 definition. 321 This section describes the rules by which SWID tag XML is represented 322 in the CoSWID CDDL structure. The CamelCase [CamelCase] notation 323 used in the XML schema definition is changed to a hyphen-separated 324 notation [KebabCase] (e.g. ResourceCollection is named resource- 325 collection) in the CoSWID data definition. This deviation from the 326 original notation used in the XML representation reduces ambiguity 327 when referencing certain attributes in corresponding textual 328 descriptions. An attribute referred to by its name in CamelCase 329 notation explicitly relates to XML SWID tags; an attribute referred 330 to by its name in KebabCase notation explicitly relates to CBOR 331 CoSWID tags. This approach simplifies the composition of further 332 work that reference both XML SWID and CBOR CoSWID documents. 334 In most cases, mapping attribute names between SWID and CoSWID can be 335 done automatically by converting between CamelCase and KebabCase 336 attribute names. However, some CoSWID CDDL attribute names show 337 greater variation relative to their corresponding SWID XML Schema 338 attributes. This is done when the change improves clarity in the 339 specification. For example the "name" and "version" SWID fields 340 corresponds to the "software-name" and "software-version" CoSWID 341 fields, respectively. As such, it is not always possible to 342 mechanically translate between corresponding attribute names in the 343 two formats. In such cases, a manual mapping will need to be used. 345 The 57 human-readable text labels of the CDDL-based CoSWID vocabulary 346 are mapped to integer indices via a block of rules at the bottom of 347 the definition. This allows a more concise integer-based form to be 348 stored or transported, as compared to the less efficient text-based 349 form of the original vocabulary. 351 In CBOR, an array is encoded using bytes that identify the array, and 352 the array's length or stop point (see [RFC7049]). To make items that 353 support 1 or more values, the following CDDL notion is used. 355 _name_ = (_label_ => _data_ / [ 2* _data_ ]) 357 The CDDL rule above allows either a single data item or an array of 2 358 or more data values to be provided. When a singleton data value is 359 provided, the CBOR markers for the array, array length, and stop 360 point are not needed, saving bytes. When two or more data values are 361 provided, these values are encoded as an array. This modeling 362 pattern is used frequently in the CoSWID CDDL data definition to 363 allow for more efficient encoding of singleton values. 365 The following subsections describe the different parts of the CoSWID 366 model. 368 2.1. Character Encoding 370 The CDDL "text" type is represented in CBOR as a major type 3, which 371 represents "a string of Unicode characters that [are] encoded as 372 UTF-8 [RFC3629]" (see [RFC7049] section 2.1). Thus both SWID and 373 CoSWID use UTF-8 for the encoding of characters in text strings. 375 To ensure that UTF-8 character strings are able to be encoded/decoded 376 and exchanged interoperably, text strings in CoSWID MUST be encoded 377 consistent with the Net-Unicode definition defined in [RFC5198]. 379 All names registered with IANA according to requirements in section 380 Section 5.2 also need to be valid according to the XML Schema NMToken 381 data type (see [W3C.REC-xmlschema-2-20041028] section 3.3.4) to 382 ensure compatibility with the SWID specification where these names 383 are used. 385 2.2. Concise SWID Extensions 387 The CoSWID data definition contains two features that are not 388 included in the SWID data definition on which it is based. These 389 features are: 391 * The explicit definition of types for some attributes in the ISO- 392 19770-2:2015 XML representation that are typically represented by 393 the "any attribute" in the SWID model. These are covered in 394 Section 2.5. 396 * The inclusion of extension points in the CoSWID data definition 397 using CDDL sockets (see [RFC8610] section 3.9). The use of CDDL 398 sockets allow for well-formed extensions to be defined in 399 supplementary CDDL descriptions that support additional uses of 400 CoSWID tags that go beyond the original scope of ISO-19770-2:2015 401 tags. This extension mechanism can also be used to update the 402 CoSWID format as revisions to ISO-19770-2 are published. 404 The following CDDL sockets (extension points) are defined in this 405 document, which allow the addition of new information structures to 406 their respective CDDL groups. 408 +---------------------+---------------------------+---------------+ 409 | Map Name | CDDL Socket | Defined in | 410 +=====================+===========================+===============+ 411 | concise-swid-tag | $$coswid-extension | Section 2.3 | 412 +---------------------+---------------------------+---------------+ 413 | entity-entry | $$entity-extension | Section 2.6 | 414 +---------------------+---------------------------+---------------+ 415 | link-entry | $$link-extension | Section 2.7 | 416 +---------------------+---------------------------+---------------+ 417 | software-meta-entry | $$software-meta-extension | Section 2.8 | 418 +---------------------+---------------------------+---------------+ 419 | file-entry | $$file-extension | Section 2.9.2 | 420 +---------------------+---------------------------+---------------+ 421 | directory-entry | $$directory-extension | Section 2.9.2 | 422 +---------------------+---------------------------+---------------+ 423 | process-entry | $$process-extension | Section 2.9.2 | 424 +---------------------+---------------------------+---------------+ 425 | resource-entry | $$resource-extension | Section 2.9.2 | 426 +---------------------+---------------------------+---------------+ 427 | payload-entry | $$payload-extension | Section 2.9.3 | 428 +---------------------+---------------------------+---------------+ 429 | evidence-entry | $$evidence-extension | Section 2.9.4 | 430 +---------------------+---------------------------+---------------+ 432 Table 1: CoSWID CDDL Group Extension Points 434 The CoSWID Items Registry defined in Section 5.1 provides a 435 registration mechanism allowing new items, and their associated index 436 values, to be added to the CoSWID model through the use of the CDDL 437 sockets described in the table above. This registration mechanism 438 provides for well-known index values for data items in CoSWID 439 extensions, allowing these index values to be recognized by 440 implementations supporting a given extension. 442 The following additional CDDL sockets are defined in this document to 443 allow for adding new values to corresponding type-choices (i.e. to 444 represent enumerations) via custom CDDL data definitions. 446 +------------------+-----------------+-------------+ 447 | Enumeration Name | CDDL Socket | Defined in | 448 +==================+=================+=============+ 449 | version-scheme | $version-scheme | Section 4.1 | 450 +------------------+-----------------+-------------+ 451 | role | $role | Section 4.2 | 452 +------------------+-----------------+-------------+ 453 | ownership | $ownership | Section 4.3 | 454 +------------------+-----------------+-------------+ 455 | rel | $rel | Section 4.4 | 456 +------------------+-----------------+-------------+ 457 | use | $use | Section 4.5 | 458 +------------------+-----------------+-------------+ 460 Table 2: CoSWID CDDL Enumeration Extension Points 462 A number of SWID/CoSWID value registries are also defined in 463 Section 5.2 that allow new values to be registered with IANA for the 464 enumerations above. This registration mechanism supports the 465 definition of new well-known index values and names for new 466 enumeration values used by both SWID and CoSWID. This registration 467 mechanism allows new standardized enumerated values to be shared 468 between both specifications (and implementations) over time, and 469 references to the IANA registries will be added to the next revision 470 of [SWID]. 472 2.3. The concise-swid-tag Map 474 The CDDL data definition for the root concise-swid-tag map is as 475 follows and this rule and its constraints MUST be followed when 476 creating or validating a CoSWID tag: 478 concise-swid-tag = { 479 global-attributes, 480 tag-id => text / bstr .size 16, 481 tag-version => integer, 482 ? corpus => bool, 483 ? patch => bool, 484 ? supplemental => bool, 485 software-name => text, 486 ? software-version => text, 487 ? version-scheme => $version-scheme, 488 ? media => text, 489 ? software-meta => software-meta-entry / [ 2* software-meta-entry ], 490 entity => entity-entry / [ 2* entity-entry ], 491 ? link => link-entry / [ 2* link-entry ], 492 ? (( payload => payload-entry ) // ( evidence => evidence-entry )), 493 * $$coswid-extension, 494 } 496 tag-id = 0 497 software-name = 1 498 entity = 2 499 evidence = 3 500 link = 4 501 software-meta = 5 502 payload = 6 503 corpus = 8 504 patch = 9 505 media = 10 506 supplemental = 11 507 tag-version = 12 508 software-version = 13 509 version-scheme = 14 511 $version-scheme /= multipartnumeric 512 $version-scheme /= multipartnumeric-suffix 513 $version-scheme /= alphanumeric 514 $version-scheme /= decimal 515 $version-scheme /= semver 516 $version-scheme /= uint / text 517 multipartnumeric = 1 518 multipartnumeric-suffix = 2 519 alphanumeric = 3 520 decimal = 4 521 semver = 16384 523 The following describes each member of the concise-swid-tag root map. 525 * global-attributes: A list of items including an optional language 526 definition to support the processing of text-string values and an 527 unbounded set of any-attribute items. Described in Section 2.5. 529 * tag-id (index 0): A 16 byte binary string or textual identifier 530 uniquely referencing a software component. The tag identifier 531 MUST be globally unique. If represented as a 16 byte binary 532 string, the identifier MUST be a valid universally unique 533 identifier as defined by [RFC4122]. There are no strict 534 guidelines on how this identifier is structured, but examples 535 include a 16 byte GUID (e.g. class 4 UUID) [RFC4122], or a text 536 string appended to a DNS domain name to ensure uniqueness across 537 organizations. 539 * tag-version (index 12): An integer value that indicate the 540 specific release revision of the tag. Typically, the initial 541 value of this field is set to 0 and the value is monotonically 542 increased for subsequent tags produced for the same software 543 component release. This value allows a CoSWID tag producer to 544 correct an incorrect tag previously released without indicating a 545 change to the underlying software component the tag represents. 546 For example, the tag version could be changed to add new metadata, 547 to correct a broken link, to add a missing payload entry, etc. 548 When producing a revised tag, the new tag-version value MUST be 549 greater than the old tag-version value. 551 * corpus (index 8): A boolean value that indicates if the tag 552 identifies and describes an installable software component in its 553 pre-installation state. Installable software includes a 554 installation package or installer for a software component, a 555 software update, or a patch. If the CoSWID tag represents 556 installable software, the corpus item MUST be set to "true". If 557 not provided, the default value MUST be considered "false". 559 * patch (index 9): A boolean value that indicates if the tag 560 identifies and describes an installed patch that has made 561 incremental changes to a software component installed on an 562 endpoint. Typically, an installed patch has made a set of file 563 modifications to pre-installed software and does not alter the 564 version number or the descriptive metadata of an installed 565 software component. If a CoSWID tag is for a patch, the patch 566 item MUST be set to "true". If not provided, the default value 567 MUST be considered "false". 569 Note: If the software component's version number is modified, then 570 the correct course of action would be to replace the previous 571 primary tag for the component with a new primary tag that 572 reflected this new version. In such a case, the new tag would 573 have a patch item value of "false" or would omit this item 574 completely. 576 * supplemental (index 11): A boolean value that indicates if the tag 577 is providing additional information to be associated with another 578 referenced SWID or CoSWID tag. This allows tools and users to 579 record their own metadata about a software component without 580 modifying SWID primary or patch tags created by a software 581 provider. If a CoSWID tag is a supplemental tag, the supplemental 582 item MUST be set to "true". If not provided, the default value 583 MUST be considered "false". 585 * software-name (index 1): This textual item provides the software 586 component's name. This name is likely the same name that would 587 appear in a package management tool. 589 * software-version (index 13): A textual value representing the 590 specific release or development version of the software component. 592 * version-scheme (index 14): An integer or textual value 593 representing the versioning scheme used for the software-version 594 item. If an integer value is used it MUST be an index value in 595 the range -256 to 65535. Integer values in the range -256 to -1 596 are reserved for testing and use in closed environments (see 597 section Section 5.2.2). Integer values in the range 0 to 65535 598 correspond to registered entries in the IANA "SWID/CoSWID Version 599 Scheme Value" registry (see section Section 5.2.4. If a string 600 value is used it MUST be a private use name as defined in section 601 Section 5.2.2. String values based on a Version Scheme Name from 602 the IANA "SWID/CoSWID Version Scheme Value" registry MUST NOT be 603 used, as these values are less concise than their index value 604 equivalent. 606 * media (index 10): This text value is a hint to the tag consumer to 607 understand what target platform this tag applies to. This item 608 represents a query as defined by the W3C Media Queries 609 Recommendation (see [W3C.REC-css3-mediaqueries-20120619]). 611 * software-meta (index 5): An open-ended map of key/value data 612 pairs. A number of predefined keys can be used within this item 613 providing for common usage and semantics across the industry. Use 614 of this map allows any additional attribute to be included in the 615 tag. It is expected that industry groups will use a common set of 616 attribute names to allow for interoperability within their 617 communities. Described in Section 2.8. 619 * entity (index 2): Provides information about one or more 620 organizations responsible for producing the CoSWID tag, and 621 producing or releasing the software component referenced by this 622 CoSWID tag. Described in Section 2.6. 624 * link (index 4): Provides a means to establish relationship arcs 625 between the tag and another items. A given link can be used to 626 establish the relationship between tags or to reference another 627 resource that is related to the CoSWID tag, e.g. vulnerability 628 database association, ROLIE feed [RFC8322], MUD resource 629 [RFC8520], software download location, etc). This is modeled 630 after the HTML "link" element. Described in Section 2.7. 632 * payload (index 6): This item represents a collection of software 633 artifacts (described by child items) that compose the target 634 software. For example, these artifacts could be the files 635 included with an installer for a corpus tag or installed on an 636 endpoint when the software component is installed for a primary or 637 patch tag. The artifacts listed in a payload may be a superset of 638 the software artifacts that are actually installed. Based on user 639 selections at install time, an installation might not include 640 every artifact that could be created or executed on the endpoint 641 when the software component is installed or run. Described in 642 Section 2.9.3. 644 * evidence-entry (index 3): This item can be used to record the 645 results of a software discovery process used to identify untagged 646 software on an endpoint or to represent indicators for why 647 software is believed to be installed on the endpoint. In either 648 case, a CoSWID tag can be created by the tool performing an 649 analysis of the software components installed on the endpoint. 650 Described in Section 2.9.4. 652 * $$coswid-extension: This CDDL socket is used to add new 653 information structures to the concise-swid-tag root map. See 654 Section 2.2. 656 2.4. concise-swid-tag Co-constraints 658 The following co-constraints apply to the information provided in the 659 concise-swid-tag group. 661 * The patch and supplemental items MUST NOT both be set to "true". 663 * If the patch item is set to "true", the tag SHOULD contain at 664 least one link item (see section Section 2.7) with both the rel 665 item value of "patches" and an href item specifying an association 666 with the software that was patched. 668 * If the supplemental item is set to "true", the tag SHOULD contain 669 at least one link item with both the rel item value of 670 "supplemental" and an href item specifying an association with the 671 software that is supplemented. 673 * If all of the corpus, patch, and supplemental items are "false", 674 or if the corpus item is set to "true", then a software-version 675 item MUST be included with a value set to the version of the 676 software component. This ensures that primary and corpus tags 677 have an identifiable software version. 679 2.5. The global-attributes Group 681 The global-attributes group provides a list of items, including an 682 optional language definition to support the processing of text-string 683 values, and an unbounded set of any-attribute items allowing for 684 additional items to be provided as a general point of extension in 685 the model. 687 The CDDL for the global-attributes follows: 689 global-attributes = ( 690 ? lang, 691 * any-attribute, 692 ) 694 any-attribute = ( 695 label => text / int / [ 2* text ] / [ 2* int ] 696 ) 698 label = text / int 700 The following describes each child item of this group. 702 * lang (index 15): A textual language tag that conforms with IANA 703 "Language Subtag Registry" [RFC5646]. The context of the 704 specified language applies to all sibling and descendant textual 705 values, unless a descendant object has defined a different 706 language tag. Thus, a new context is established when a 707 descendant object redefines a new language tag. All textual 708 values within a given context MUST be considered expressed in the 709 specified language. 711 * any-attribute: This sub-group provides a means to include 712 arbitrary information via label/index ("key") value pairs. Labels 713 can be either a single integer or text string. Values can be a 714 single integer, a text string, or an array of integers or text 715 strings. 717 2.6. The entity-entry Map 719 The CDDL for the entity-entry map follows: 721 entity-entry = { 722 global-attributes, 723 entity-name => text, 724 ? reg-id => any-uri, 725 role => $role / [ 2* $role ], 726 ? thumbprint => hash-entry, 727 * $$entity-extension, 728 } 730 entity-name = 31 731 reg-id = 32 732 role = 33 733 thumbprint = 34 735 $role /= tag-creator 736 $role /= software-creator 737 $role /= aggregator 738 $role /= distributor 739 $role /= licensor 740 $role /= maintainer 741 $role /= uint / text 742 tag-creator=1 743 software-creator=2 744 aggregator=3 745 distributor=4 746 licensor=5 747 maintainer=6 749 The following describes each child item of this group. 751 * global-attributes: The global-attributes group described in 752 Section 2.5. 754 * entity-name (index 32): The textual name of the organizational 755 entity claiming the roles specified by the role item for the 756 CoSWID tag. 758 * reg-id (index 32): The registration id value is intended to 759 uniquely identify a naming authority in a given scope (e.g. 760 global, organization, vendor, customer, administrative domain, 761 etc.) for the referenced entity. The value of an registration ID 762 MUST be a RFC 3986 URI. The scope SHOULD be the scope of an 763 organization. In a given scope, the registration id MUST be used 764 consistently for CoSWID tag production. 766 * role (index 33): An integer or textual value representing the 767 relationship(s) between the entity, and this tag or the referenced 768 software component. If an integer value is used it MUST be an 769 index value in the range -256 to 255. Integer values in the range 770 -256 to -1 are reserved for testing and use in closed environments 771 (see section Section 5.2.2). Integer values in the range 0 to 255 772 correspond to registered entries in the IANA "SWID/CoSWID Entity 773 Role Value" registry (see section Section 5.2.5. If a string 774 value is used it MUST be a private use name as defined in section 775 Section 5.2.2. String values based on a Role Name from the IANA 776 "SWID/CoSWID Entity Role Value" registry MUST NOT be used, as 777 these values are less concise than their index value equivalent. 779 The following additional requirements exist for the use of the 780 "role" item: 782 - An entity item MUST be provided with the role of "tag-creator" 783 for every CoSWID tag. This indicates the organization that 784 created the CoSWID tag. 786 - An entity item SHOULD be provided with the role of "software- 787 creator" for every CoSWID tag, if this information is known to 788 the tag creator. This indicates the organization that created 789 the referenced software component. 791 * thumbprint (index 34): The value of the thumbprint item provides 792 an integer-based hash algorithm identifier (hash-alg-id) and a 793 byte string value (hash-value) that contains the corresponding 794 hash value (i.e. the thumbprint) of the signing entity's public 795 key certificate. This provides an indicator of which entity 796 signed the CoSWID tag, which will typically be the tag creator. 797 If the hash-alg-id is not known, then the integer value "0" MUST 798 be used. This ensures parity between the SWID tag specification 800 [SWID], which does not allow an algorithm to be identified for 801 this field. See Section 2.9.1 for more details on the use of the 802 hash-entry data structure. 804 * $$entity-extension: This CDDL socket can be used to extend the 805 entity-entry group model. See Section 2.2. 807 2.7. The link-entry Map 809 The CDDL for the link-entry map follows: 811 link-entry = { 812 global-attributes, 813 ? artifact => text, 814 href => any-uri, 815 ? media => text, 816 ? ownership => $ownership, 817 rel => $rel, 818 ? media-type => text, 819 ? use => $use, 820 * $$link-extension, 821 } 823 media = 10 824 artifact = 37 825 href = 38 826 ownership = 39 827 rel = 40 828 media-type = 41 829 use = 42 831 $ownership /= shared 832 $ownership /= private 833 $ownership /= abandon 834 $ownership /= uint / text 835 shared=1 836 private=2 837 abandon=3 839 $rel /= ancestor 840 $rel /= component 841 $rel /= feature 842 $rel /= installationmedia 843 $rel /= packageinstaller 844 $rel /= parent 845 $rel /= patches 846 $rel /= requires 847 $rel /= see-also 848 $rel /= supersedes 849 $rel /= supplemental 850 $rel /= uint / text 851 ancestor=1 852 component=2 853 feature=3 854 installationmedia=4 855 packageinstaller=5 856 parent=6 857 patches=7 858 requires=8 859 see-also=9 860 supersedes=10 861 supplemental=11 863 $use /= optional 864 $use /= required 865 $use /= recommended 866 $use /= uint / text 867 optional=1 868 required=2 869 recommended=3 871 The following describes each member of this map. 873 * global-attributes: The global-attributes group described in 874 Section 2.5. 876 * artifact (index: 37): To be used with rel="installation-media", 877 this item's value provides the path to the installer executable or 878 script that can be run to launch the referenced installation. 879 Links with the same artifact name MUST be considered mirrors of 880 each other, allowing the installation media to be acquired from 881 any of the described sources. 883 * href (index 38): A URI for the referenced resource. The "href" 884 item's value can be, but is not limited to, the following (which 885 is a slightly modified excerpt from [SWID]): 887 - If no URI scheme is provided, then the URI is to be interpreted 888 as being relative to the URI of the CoSWID tag. For example, 889 "./folder/supplemental.coswid". 891 - a physical resource location with any acceptable URI scheme 892 (e.g., file:// http:// https:// ftp://) 894 - a URI with "swid:" as the scheme refers to another SWID or 895 CoSWID by the referenced tag's tag-id. This URI needs to be 896 resolved in the context of the endpoint by software that can 897 lookup other SWID or CoSWID tags. For example, "swid:2df9de35- 898 0aff-4a86-ace6-f7dddd1ade4c" references the tag with the tag-id 899 value "2df9de35-0aff-4a86-ace6-f7dddd1ade4c". 901 - a URI with "swidpath:" as the scheme, which refers to another 902 CoSIWD via an XPATH query. This URI would need to be resolved 903 in the context of the system entity via software components 904 that can lookup other CoSWID tags and select the appropriate 905 tag based on an XPATH query [W3C.REC-xpath20-20101214]. 907 Examples include: 909 o swidpath://SoftwareIdentity[Entity/@regid='http://contoso.co 910 m'] would retrieve all SWID or CoSWID tags that include an 911 entity where the regid is "Contoso" 913 o swidpath://SoftwareIdentity[Meta/@persistentId='b0c55172-38e 914 9-4e36-be86-92206ad8eddb'] would match all SWID or CoSWID 915 tags with the persistent-id value 916 "b0c55172-38e9-4e36-be86-92206ad8eddb" 918 * media (index 10): A hint to the consumer of the link to what 919 target platform the link is applicable to. This item represents a 920 query as defined by the W3C Media Queries Recommendation (see 921 [W3C.REC-css3-mediaqueries-20120619]). See also media defined in 922 Section 2.3. 924 * ownership (index 39): An integer or textual value used when the 925 "href" item references another software component to indicate the 926 degree of ownership between the software component referenced by 927 the COSWID tag and the software component referenced by the link. 928 If an integer value is used it MUST be an index value in the range 929 -256 to 255. Integer values in the range -256 to -1 are reserved 930 for testing and use in closed environments (see section 931 Section 5.2.2). Integer values in the range 0 to 255 correspond 932 to registered entries in the IANA "SWID/CoSWID Link Ownership 933 Value" registry (see section Section 5.2.6. If a string value is 934 used it MUST be a private use name as defined in section 935 Section 5.2.2. String values based on a Ownership Type Name from 936 the IANA "SWID/CoSWID Link Ownership Value" registry MUST NOT be 937 used, as these values are less concise than their index value 938 equivalent. 940 * rel (index 40): An integer or textual value that identifies the 941 relationship between this CoSWID and the target resource 942 identified by the "href" item. If an integer value is used it 943 MUST be an index value in the range -256 to 65535. Integer values 944 in the range -256 to -1 are reserved for testing and use in closed 945 environments (see section Section 5.2.2). Integer values in the 946 range 0 to 65535 correspond to registered entries in the IANA 947 "SWID/CoSWID Link Relationship Value" registry (see section 948 Section 5.2.7. If a string value is used it MUST be either a 949 private use name as defined in section Section 5.2.2 or a 950 "Relation Name" from the IANA "Link Relation Types" registry: 951 https://www.iana.org/assignments/link-relations/link- 952 relations.xhtml as defined by [RFC8288]. When a string value 953 defined in the IANA "SWID/CoSWID Link Relationship Value" registry 954 matches a Relation Name defined in the IANA "Link Relation Types" 955 registry, the index value in the IANA "SWID/CoSWID Link 956 Relationship Value" registry MUST be used instead, as this 957 relationship has a specialized meaning in the context of a SWID/ 958 CoSWID tag. String values based on a Relationship Type Name from 959 the IANA "SWID/CoSWID Link Relationship Value" registry MUST NOT 960 be used, as these values are less concise than their index value 961 equivalent. 963 * media-type (index 41): A link can point to arbitrary resources on 964 the endpoint, local network, or Internet using the href item. Use 965 of this item supplies the resource consumer with a hint of what 966 type of resource to expect. Media types are identified by 967 referencing a "Name" from the IANA "Media Types" registry: 968 http://www.iana.org/assignments/media-types/media-types.xhtml. 970 * use (index 42): An integer or textual value used to determine if 971 the referenced software component has to be installed before 972 installing the software component identified by the COSWID tag. 973 If an integer value is used it MUST be an index value in the range 974 -256 to 255. Integer values in the range -256 to -1 are reserved 975 for testing and use in closed environments (see section 976 Section 5.2.2). Integer values in the range 0 to 255 correspond 977 to registered entries in the IANA "Link Use Value Value" registry 978 (see section Section 5.2.8. If a string value is used it MUST be 979 a private use name as defined in section Section 5.2.2. String 980 values based on an Link Use Type Name from the IANA "SWID/CoSWID 981 Link Use Value" registry MUST NOT be used, as these values are 982 less concise than their index value equivalent. 984 * $$link-extension: This CDDL socket can be used to extend the link- 985 entry map model. See Section 2.2. 987 2.8. The software-meta-entry Map 989 The CDDL for the software-meta-entry map follows: 991 software-meta-entry = { 992 global-attributes, 993 ? activation-status => text, 994 ? channel-type => text, 995 ? colloquial-version => text, 996 ? description => text, 997 ? edition => text, 998 ? entitlement-data-required => bool, 999 ? entitlement-key => text, 1000 ? generator => text, 1001 ? persistent-id => text, 1002 ? product => text, 1003 ? product-family => text, 1004 ? revision => text, 1005 ? summary => text, 1006 ? unspsc-code => text, 1007 ? unspsc-version => text, 1008 * $$software-meta-extension, 1009 } 1011 activation-status = 43 1012 channel-type = 44 1013 colloquial-version = 45 1014 description = 46 1015 edition = 47 1016 entitlement-data-required = 48 1017 entitlement-key = 49 1018 generator = 50 1019 persistent-id = 51 1020 product = 52 1021 product-family = 53 1022 revision = 54 1023 summary = 55 1024 unspsc-code = 56 1025 unspsc-version = 57 1027 The following describes each child item of this group. 1029 * global-attributes: The global-attributes group described in 1030 Section 2.5. 1032 * activation-status (index 43): A textual value that identifies how 1033 the software component has been activated, which might relate to 1034 specific terms and conditions for its use (e.g. Trial, 1035 Serialized, Licensed, Unlicensed, etc) and relate to an 1036 entitlement. This attribute is typically used in supplemental 1037 tags as it contains information that might be selected during a 1038 specific install. 1040 * channel-type (index 44): A textual value that identfies which 1041 sales, licensing, or marketing channel the software component has 1042 been targeted for (e.g. Volume, Retail, OEM, Academic, etc). 1043 This attribute is typically used in supplemental tags as it 1044 contains information that might be selected during a specific 1045 install. 1047 * colloquial-version (index 45): A textual value for the software 1048 component's informal or colloquial version. Examples may include 1049 a year value, a major version number, or similar value that are 1050 used to identify a group of specific software component releases 1051 that are part of the same release/support cycle. This version can 1052 be the same through multiple releases of a software component, 1053 while the software-version specified in the concise-swid-tag group 1054 is much more specific and will change for each software component 1055 release. This version is intended to be used for string 1056 comparison only and is not intended to be used to determine if a 1057 specific value is earlier or later in a sequence. 1059 * description (index 46): A textual value that provides a detailed 1060 description of the software component. This value MAY be multiple 1061 paragraphs separated by CR LF characters as described by 1062 [RFC5198]. 1064 * edition (index 47): A textual value indicating that the software 1065 component represents a functional variation of the code base used 1066 to support multiple software components. For example, this item 1067 can be used to differentiate enterprise, standard, or professional 1068 variants of a software component. 1070 * entitlement-data-required (index 48): A boolean value that can be 1071 used to determine if accompanying proof of entitlement is needed 1072 when a software license reconciliation process is performed. 1074 * entitlement-key (index 49): A vendor-specific textual key that can 1075 be used to identify and establish a relationship to an 1076 entitlement. Examples of an entitlement-key might include a 1077 serial number, product key, or license key. For values that 1078 relate to a given software component install (i.e., license key), 1079 a supplemental tag will typically contain this information. In 1080 other cases, where a general-purpose key can be provided that 1081 applies to all possible installs of the software component on 1082 different endpoints, a primary tag will typically contain this 1083 information. 1085 * generator (index 50): The name (or tag-id) of the software 1086 component that created the CoSWID tag. If the generating software 1087 component has a SWID or CoSWID tag, then the tag-id for the 1088 generating software component SHOULD be provided. 1090 * persistent-id (index 51): A globally unique identifier used to 1091 identify a set of software components that are related. Software 1092 components sharing the same persistent-id can be different 1093 versions. This item can be used to relate software components, 1094 released at different points in time or through different release 1095 channels, that may not be able to be related through use of the 1096 link item. 1098 * product (index 52): A basic name for the software component that 1099 can be common across multiple tagged software components (e.g., 1100 Apache HTTPD). 1102 * product-family (index 53): A textual value indicating the software 1103 components overall product family. This should be used when 1104 multiple related software components form a larger capability that 1105 is installed on multiple different endpoints. For example, some 1106 software families may consist of server, client, and shared 1107 service components that are part of a larger capability. Email 1108 systems, enterprise applications, backup services, web 1109 conferencing, and similar capabilities are examples of families. 1110 Use of this item is not intended to represent groups of software 1111 that are bundled or installed together. The persistent-id or link 1112 items SHOULD be used to relate bundled software components. 1114 * revision (index 54): A string value indicating an informal or 1115 colloquial release version of the software. This value can 1116 provide a different version value as compared to the software- 1117 version specified in the concise-swid-tag group. This is useful 1118 when one or more releases need to have an informal version label 1119 that differs from the specific exact version value specified by 1120 software-version. Examples can include SP1, RC1, Beta, etc. 1122 * summary (index 55): A short description of the software component. 1123 This MUST be a single sentence suitable for display in a user 1124 interface. 1126 * unspsc-code (index 56): An 8 digit UNSPSC classification code for 1127 the software component. For more information see 1128 https://www.unspsc.org/. 1130 * unspsc-version (index 57): The version of UNSPSC used to define 1131 the unspsc-code value. 1133 * $$meta-extension: This CDDL socket can be used to extend the 1134 software-meta-entry group model. See Section 2.2. 1136 2.9. The Resource Collection Definition 1138 2.9.1. The hash-entry Array 1140 CoSWID adds explicit support for the representation of hash entries 1141 using algorithms that are registered in the IANA "Named Information 1142 Hash Algorithm Registry" using the hash member (index 7) and the 1143 corresponding hash-entry type. 1145 hash-entry = [ 1146 hash-alg-id: int, 1147 hash-value: bytes, 1148 ] 1150 The number used as a value for hash-alg-id MUST refer an ID in the 1151 "Named Information Hash Algorithm Registry" (see 1152 https://www.iana.org/assignments/named-information/named- 1153 information.xhtml); other hash algorithms MUST NOT be used. The 1154 hash-value MUST represent the raw hash value of the hashed resource 1155 generated using the hash algorithm indicated by the hash-alg-id. 1157 2.9.2. The resource-collection Group 1159 A list of items both used in evidence (created by a software 1160 discovery process) and payload (installed in an endpoint) content of 1161 a CoSWID tag document to structure and differentiate the content of 1162 specific CoSWID tag types. Potential content includes directories, 1163 files, processes, or resources. 1165 The CDDL for the resource-collection group follows: 1167 path-elements-group = ( ? directory => directory-entry / [ 2* directory-entry ], 1168 ? file => file-entry / [ 2* file-entry ], 1169 ) 1171 esource-collection = ( 1172 path-elements-group, 1173 ? process => process-entry / [ 2* process-entry ], 1174 ? resource => resource-entry / [ 2* resource-entry ], 1175 * $$resource-collection-extension, 1176 ) 1178 filesystem-item = ( 1179 global-attributes, 1180 ? key => bool, 1181 ? location => text, 1182 fs-name => text, 1183 ? root => text, 1184 ) 1186 file-entry = { 1187 filesystem-item, 1188 ? size => integer, 1189 ? file-version => text, 1190 ? hash => hash-entry, 1191 * $$file-extension, 1192 } 1194 directory-entry = { 1195 filesystem-item, 1196 path-elements => { path-elements-group }, 1197 * $$directory-extension, 1198 } 1200 process-entry = { 1201 global-attributes, 1202 process-name => text, 1203 ? pid => integer, 1204 * $$process-extension, 1205 } 1207 resource-entry = { 1208 global-attributes, 1209 type => text, 1210 * $$resource-extension, 1211 } 1213 directory = 16 1214 file = 17 1215 process = 18 1216 resource = 19 1217 size = 20 1218 file-version = 21 1219 key = 22 1220 location = 23 1221 fs-name = 24 1222 root = 25 1223 path-elements = 26 1224 process-name = 27 1225 pid = 28 1226 type = 29 1228 The following describes each member of the groups and maps 1229 illustrated above. 1231 * filesystem-item: A list of common items used for representing the 1232 filesystem root, relative location, name, and significance of a 1233 file or directory item. 1235 * global-attributes: The global-attributes group described in 1236 Section 2.5. 1238 * directory (index 16): A directory item allows child directory and 1239 file items to be defined within a directory hierarchy for the 1240 software component. 1242 * file (index 17): A file item allows details about a file to be 1243 provided for the software component. 1245 * process (index 18): A process item allows details to be provided 1246 about the runtime behavior of the software component, such as 1247 information that will appear in a process listing on an endpoint. 1249 * resource (index 19): A resource item can be used to provide 1250 details about an artifact or capability expected to be found on an 1251 endpoint or evidence collected related to the software component. 1252 This can be used to represent concepts not addressed directly by 1253 the directory, file, or process items. Examples include: registry 1254 keys, bound ports, etc. The equivalent construct in [SWID] is 1255 currently under specified. As a result, this item might be 1256 further defined through extension in the future. 1258 * size (index 20): The file's size in bytes. 1260 * file-version (index 21): The file's version as reported by 1261 querying information on the file from the operating system. 1263 * key (index 22): A boolean value indicating if a file or directory 1264 is significant or required for the software component to execute 1265 or function properly. These are files or directories that can be 1266 used to affirmatively determine if the software component is 1267 installed on an endpoint. 1269 * location (index 23): The filesystem path where a file is expected 1270 to be located when installed or copied. The location MUST be 1271 either relative to the location of the parent directory item 1272 (preferred) or relative to the location of the CoSWID tag if no 1273 parent is defined. The location MUST NOT include a file's name, 1274 which is provided by the fs-name item. 1276 * fs-name (index 24): The name of the directory or file without any 1277 path information. 1279 * root (index 25): A filesystem-specific name for the root of the 1280 filesystem. The location item is considered relative to this 1281 location if specified. If not provided, the value provided by the 1282 location item is expected to be relative to its parent or the 1283 location of the CoSWID tag if no parent is provided. 1285 * path-elements (index 26): This group allows a hierarchy of 1286 directory and file items to be defined in payload or evidence 1287 items. 1289 * process-name (index 27): The software component's process name as 1290 it will appear in an endpoint's process list. 1292 * pid (index 28): The process ID identified for a running instance 1293 of the software component in the endpoint's process list. This is 1294 used as part of the evidence item. 1296 * type (index 29): A string indicating the type of resource. 1298 * $$resource-collection-extension: This CDDL socket can be used to 1299 extend the resource-collection group model. This can be used to 1300 add new specialized types of resources. See Section 2.2. 1302 * $$file-extension: This CDDL socket can be used to extend the file- 1303 entry group model. See Section 2.2. 1305 * $$directory-extension: This CDDL socket can be used to extend the 1306 directory-entry group model. See Section 2.2. 1308 * $$process-extension: This CDDL socket can be used to extend the 1309 process-entry group model. See Section 2.2. 1311 * $$resource-extension: This CDDL socket can be used to extend the 1312 resource-entry group model. See Section 2.2. 1314 2.9.3. The payload-entry Map 1316 The CDDL for the payload-entry map follows: 1318 payload-entry = { 1319 global-attributes, 1320 resource-collection, 1321 * $$payload-extension, 1322 } 1324 The following describes each child item of this group. 1326 * global-attributes: The global-attributes group described in 1327 Section 2.5. 1329 * resource-collection: The resource-collection group described in 1330 Section 2.9.2. 1332 * $$payload-extension: This CDDL socket can be used to extend the 1333 payload-entry group model. See Section 2.2. 1335 2.9.4. The evidence-entry Map 1337 The CDDL for the evidence-entry map follows: 1339 evidence-entry = { 1340 global-attributes, 1341 resource-collection, 1342 ? date => time, 1343 ? device-id => text, 1344 * $$evidence-extension, 1345 } 1347 date = 35 1348 device-id = 36 1350 The following describes each child item of this group. 1352 * global-attributes: The global-attributes group described in 1353 Section 2.5. 1355 * resource-collection: The resource-collection group described in 1356 Section 2.9.2. 1358 * date (index 35): The date and time the information was collected 1359 pertaining to the evidence item. 1361 * device-id (index 36): The endpoint's string identifier from which 1362 the evidence was collected. 1364 * $$evidence-extension: This CDDL socket can be used to extend the 1365 evidence-entry group model. See Section 2.2. 1367 2.10. Full CDDL Definition 1369 In order to create a valid CoSWID document the structure of the 1370 corresponding CBOR message MUST adhere to the following CDDL data 1371 definition. 1373 concise-swid-tag = { 1374 global-attributes, 1375 tag-id => text / bstr .size 16, 1376 tag-version => integer, 1377 ? corpus => bool, 1378 ? patch => bool, 1379 ? supplemental => bool, 1380 software-name => text, 1381 ? software-version => text, 1382 ? version-scheme => $version-scheme, 1383 ? media => text, 1384 ? software-meta => software-meta-entry / [ 2* software-meta-entry ], 1385 entity => entity-entry / [ 2* entity-entry ], 1386 ? link => link-entry / [ 2* link-entry ], 1387 ? (( payload => payload-entry ) // ( evidence => evidence-entry )), 1388 * $$coswid-extension, 1389 } 1391 any-uri = text 1392 label = text / int 1394 $version-scheme /= multipartnumeric 1395 $version-scheme /= multipartnumeric-suffix 1396 $version-scheme /= alphanumeric 1397 $version-scheme /= decimal 1398 $version-scheme /= semver 1399 $version-scheme /= uint / text 1401 any-attribute = ( 1402 label => text / int / [ 2* text ] / [ 2* int ] 1403 ) 1405 global-attributes = ( 1406 ? lang => text, 1407 * any-attribute, 1408 ) 1410 hash-entry = [ 1411 hash-alg-id: int, 1412 hash-value: bytes, 1413 ] 1415 entity-entry = { 1416 global-attributes, 1417 entity-name => text, 1418 ? reg-id => any-uri, 1419 role => $role / [ 2* $role ], 1420 ? thumbprint => hash-entry, 1421 * $$entity-extension, 1422 } 1424 $role /= tag-creator 1425 $role /= software-creator 1426 $role /= aggregator 1427 $role /= distributor 1428 $role /= licensor 1429 $role /= maintainer 1430 $role /= uint / text 1432 link-entry = { 1433 global-attributes, 1434 ? artifact => text, 1435 href => any-uri, 1436 ? media => text, 1437 ? ownership => $ownership, 1438 rel => $rel, 1439 ? media-type => text, 1440 ? use => $use, 1441 * $$link-extension 1442 } 1444 $ownership /= shared 1445 $ownership /= private 1446 $ownership /= abandon 1447 $ownership /= uint / text 1449 $rel /= ancestor 1450 $rel /= component 1451 $rel /= feature 1452 $rel /= installationmedia 1453 $rel /= packageinstaller 1454 $rel /= parent 1455 $rel /= patches 1456 $rel /= requires 1457 $rel /= see-also 1458 $rel /= supersedes 1459 $rel /= supplemental 1460 $rel /= uint / text 1462 $use /= optional 1463 $use /= required 1464 $use /= recommended 1465 $use /= uint / text 1467 software-meta-entry = { 1468 global-attributes, 1469 ? activation-status => text, 1470 ? channel-type => text, 1471 ? colloquial-version => text, 1472 ? description => text, 1473 ? edition => text, 1474 ? entitlement-data-required => bool, 1475 ? entitlement-key => text, 1476 ? generator => text, 1477 ? persistent-id => text, 1478 ? product => text, 1479 ? product-family => text, 1480 ? revision => text, 1481 ? summary => text, 1482 ? unspsc-code => text, 1483 ? unspsc-version => text, 1484 * $$software-meta-extension, 1485 } 1487 path-elements-group = ( ? directory => directory-entry / [ 2* directory-entry ], 1488 ? file => file-entry / [ 2* file-entry ], 1489 ) 1491 resource-collection = ( 1492 path-elements-group, 1493 ? process => process-entry / [ 2* process-entry ], 1494 ? resource => resource-entry / [ 2* resource-entry ], 1495 * $$resource-collection-extension, 1496 ) 1498 file-entry = { 1499 filesystem-item, 1500 ? size => uint, 1501 ? file-version => text, 1502 ? hash => hash-entry, 1503 * $$file-extension, 1504 } 1506 directory-entry = { 1507 filesystem-item, 1508 ? path-elements => { path-elements-group }, 1509 * $$directory-extension, 1510 } 1512 process-entry = { 1513 global-attributes, 1514 process-name => text, 1515 ? pid => integer, 1516 * $$process-extension, 1517 } 1519 resource-entry = { 1520 global-attributes, 1521 type => text, 1522 * $$resource-extension, 1523 } 1525 filesystem-item = ( 1526 global-attributes, 1527 ? key => bool, 1528 ? location => text, 1529 fs-name => text, 1530 ? root => text, 1531 ) 1533 payload-entry = { 1534 global-attributes, 1535 resource-collection, 1536 * $$payload-extension, 1537 } 1539 evidence-entry = { 1540 global-attributes, 1541 resource-collection, 1542 ? date => time, 1543 ? device-id => text, 1544 * $$evidence-extension, 1545 } 1547 ; "global map member" integer indexes 1548 tag-id = 0 1549 software-name = 1 1550 entity = 2 1551 evidence = 3 1552 link = 4 1553 software-meta = 5 1554 payload = 6 1555 hash = 7 1556 corpus = 8 1557 patch = 9 1558 media = 10 1559 supplemental = 11 1560 tag-version = 12 1561 software-version = 13 1562 version-scheme = 14 1563 lang = 15 1564 directory = 16 1565 file = 17 1566 process = 18 1567 resource = 19 1568 size = 20 1569 file-version = 21 1570 key = 22 1571 location = 23 1572 fs-name = 24 1573 root = 25 1574 path-elements = 26 1575 process-name = 27 1576 pid = 28 1577 type = 29 1578 entity-name = 31 1579 reg-id = 32 1580 role = 33 1581 thumbprint = 34 1582 date = 35 1583 device-id = 36 1584 artifact = 37 1585 href = 38 1586 ownership = 39 1587 rel = 40 1588 media-type = 41 1589 use = 42 1590 activation-status = 43 1591 channel-type = 44 1592 colloquial-version = 45 1593 description = 46 1594 edition = 47 1595 entitlement-data-required = 48 1596 entitlement-key = 49 1597 generator = 50 1598 persistent-id = 51 1599 product = 52 1600 product-family = 53 1601 revision = 54 1602 summary = 55 1603 unspsc-code = 56 1604 unspsc-version = 57 1606 ; "version-scheme" integer indexes 1607 multipartnumeric = 1 1608 multipartnumeric-suffix = 2 1609 alphanumeric = 3 1610 decimal = 4 1611 semver = 16384 1613 ; "role" integer indexes 1614 tag-creator=1 1615 software-creator=2 1616 aggregator=3 1617 distributor=4 1618 licensor=5 1619 maintainer=6 1621 ; "ownership" integer indexes 1622 shared=1 1623 private=2 1624 abandon=3 1626 ; "rel" integer indexes 1627 ancestor=1 1628 component=2 1629 feature=3 1630 installationmedia=4 1631 packageinstaller=5 1632 parent=6 1633 patches=7 1634 requires=8 1635 see-also=9 1636 supersedes=10 1637 ; supplemental=11 ; this is already defined earlier 1639 ; "use" integer indexes 1640 optional=1 1641 required=2 1642 recommended=3 1644 3. Determining the Type of CoSWID 1646 The operational model for SWID and CoSWID tags was introduced in 1647 Section 1.1, which described four different CoSWID tag types. The 1648 following additional rules apply to the use of CoSWID tags to ensure 1649 that created tags properly identify the tag type. 1651 The first matching rule MUST determine the type of the CoSWID tag. 1653 1. Primary Tag: A CoSWID tag MUST be considered a primary tag if the 1654 corpus, patch, and supplemental items are "false". 1656 2. Supplemental Tag: A CoSWID tag MUST be considered a supplemental 1657 tag if the supplemental item is set to "true". 1659 3. Corpus Tag: A CoSWID tag MUST be considered a corpus tag if the 1660 corpus item is "true". 1662 4. Patch Tag: A CoSWID tag MUST be considered a patch tag if the 1663 patch item is "true". 1665 Note: Multiple of the corpus, patch, and supplemental items can have 1666 values set as "true". The rules above provide a means to determine 1667 the tag's type in such a case. For example, a SWID or CoSWID tag for 1668 a patch installer might have both corpus and patch items set to 1669 "true". In such a case, the tag is a "Corpus Tag". The tag 1670 installed by this installer would have only the patch item set to 1671 "true", making the installed tag type a "Patch Tag". 1673 4. CoSWID Indexed Label Values 1675 4.1. Version Scheme 1677 The following table contains a set of values for use in the concise- 1678 swid-tag group's version-scheme item. These values match the version 1679 schemes defined in the ISO/IEC 19770-2:2015 [SWID] specification. 1680 Index value indicates the value to use as the version-scheme item's 1681 value. The Version Scheme Name provides human-readable text for the 1682 value. The Definition describes the syntax of allowed values for 1683 each entry. 1685 +-------+-------------------------+--------------------------------+ 1686 | Index | Version Scheme Name | Definition | 1687 +=======+=========================+================================+ 1688 | 1 | multipartnumeric | Numbers separated by dots, | 1689 | | | where the numbers are | 1690 | | | interpreted as integers (e.g., | 1691 | | | 1.2.3, 1.4.5, 1.2.3.4.5.6.7) | 1692 +-------+-------------------------+--------------------------------+ 1693 | 2 | multipartnumeric+suffix | Numbers separated by dots, | 1694 | | | where the numbers are | 1695 | | | interpreted as integers with | 1696 | | | an additional textual suffix | 1697 | | | (e.g., 1.2.3a) | 1698 +-------+-------------------------+--------------------------------+ 1699 | 3 | alphanumeric | Strictly a string, sorting is | 1700 | | | done alphanumerically | 1701 +-------+-------------------------+--------------------------------+ 1702 | 4 | decimal | A floating point number (e.g., | 1703 | | | 1.25 is less than 1.3) | 1704 +-------+-------------------------+--------------------------------+ 1705 | 16384 | semver | Follows the [SEMVER] | 1706 | | | specification | 1707 +-------+-------------------------+--------------------------------+ 1709 Table 3: Version Scheme Values 1711 The values above are registered in the IANA "SWID/CoSWID Version 1712 Scheme Value" registry defined in section Section 5.2.4. Additional 1713 entries will likely be registered over time in this registry. 1715 These version schemes have partially overlapping value spaces. The 1716 following gudelines help to ensure that the most specific version- 1717 scheme is used: 1719 * "decimal" and "multipartnumeric" partially overlap in their value 1720 space when a value matches a decimal number . When a corresponding 1721 software-version item's value falls within this overlapping value 1722 space, the "decimal" version scheme SHOULD be used. 1724 * "multipartnumeric" and "semver" partially overlap in their value 1725 space when a "multipartnumeric" value matches the semantic 1726 versioning syntax. When a corresponding software-version item's 1727 value falls within this overlapping value space, the "semver" 1728 version scheme SHOULD be used. 1730 * "alphanumeric" and other version schemes might overlap in their 1731 value space. When a corresponding software-version item's value 1732 falls within this overlapping value space, the other version 1733 scheme SHOULD be used instead of "alphanumeric". 1735 4.2. Entity Role Values 1737 The following table indicates the index value to use for the entity- 1738 entry group's role item (see Section 2.6). These values match the 1739 entity roles defined in the ISO/IEC 19770-2:2015 [SWID] 1740 specification. The "Index" value indicates the value to use as the 1741 role item's value. The "Role Name" provides human-readable text for 1742 the value. The "Definition" describes the semantic meaning of each 1743 entry. 1745 +-------+-----------------+----------------------------------------+ 1746 | Index | Role Name | Definition | 1747 +=======+=================+========================================+ 1748 | 1 | tagCreator | The person or organization that | 1749 | | | created the containing SWID or CoSWID | 1750 | | | tag | 1751 +-------+-----------------+----------------------------------------+ 1752 | 2 | softwareCreator | The person or organization entity that | 1753 | | | created the software component. | 1754 +-------+-----------------+----------------------------------------+ 1755 | 3 | aggregator | From [SWID], "An organization or | 1756 | | | system that encapsulates software from | 1757 | | | their own and/or other organizations | 1758 | | | into a different distribution process | 1759 | | | (as in the case of virtualization), or | 1760 | | | as a completed system to accomplish a | 1761 | | | specific task (as in the case of a | 1762 | | | value added reseller)." | 1763 +-------+-----------------+----------------------------------------+ 1764 | 4 | distributor | From [SWID], "An entity that furthers | 1765 | | | the marketing, selling and/or | 1766 | | | distribution of software from the | 1767 | | | original place of manufacture to the | 1768 | | | ultimate user without modifying the | 1769 | | | software, its packaging or its | 1770 | | | labelling." | 1771 +-------+-----------------+----------------------------------------+ 1772 | 5 | licensor | From [SAM] as "software licensor", a | 1773 | | | "person or organization who owns or | 1774 | | | holds the rights to issue a software | 1775 | | | license for a specific software | 1776 | | | [component]" | 1777 +-------+-----------------+----------------------------------------+ 1778 | 6 | maintainer | The person or organization that is | 1779 | | | responsible for coordinating and | 1780 | | | making updates to the source code for | 1781 | | | the software component. This SHOULD | 1782 | | | be used when the "maintainer" is a | 1783 | | | different person or organization than | 1784 | | | the original "softwareCreator". | 1785 +-------+-----------------+----------------------------------------+ 1787 Table 4: Entity Role Values 1789 The values above are registered in the IANA "SWID/CoSWID Entity Role 1790 Value" registry defined in section Section 5.2.5. Additional values 1791 will likely be registered over time. Additionally, the index values 1792 128 through 255 and the name prefix "x_" have been reserved for 1793 private use. 1795 4.3. Link Ownership Values 1797 The following table indicates the index value to use for the link- 1798 entry group's ownership item (see Section 2.7). These values match 1799 the link ownership values defined in the ISO/IEC 19770-2:2015 [SWID] 1800 specification. The "Index" value indicates the value to use as the 1801 link-entry group ownership item's value. The "Ownership Type" 1802 provides human-readable text for the value. The "Definition" 1803 describes the semantic meaning of each entry. 1805 +-------+-----------+-----------------------------------------------+ 1806 | Index | Ownership | Definition | 1807 | | Type | | 1808 +=======+===========+===============================================+ 1809 | 1 | abandon | If the software component referenced by the | 1810 | | | CoSWID tag is uninstalled, then the | 1811 | | | referenced software SHOULD NOT be | 1812 | | | uninstalled | 1813 +-------+-----------+-----------------------------------------------+ 1814 | 2 | private | If the software component referenced by the | 1815 | | | CoSWID tag is uninstalled, then the | 1816 | | | referenced software SHOULD be uninstalled as | 1817 | | | well. | 1818 +-------+-----------+-----------------------------------------------+ 1819 | 3 | shared | If the software component referenced by the | 1820 | | | CoSWID tag is uninstalled, then the | 1821 | | | referenced software SHOULD be uninstalled if | 1822 | | | no other components sharing the software. | 1823 +-------+-----------+-----------------------------------------------+ 1825 Table 5: Link Ownership Values 1827 The values above are registered in the IANA "SWID/CoSWID Link 1828 Ownership Value" registry defined in section Section 5.2.6. 1829 Additional values will likely be registered over time. Additionally, 1830 the index values 128 through 255 and the name prefix "x_" have been 1831 reserved for private use. 1833 4.4. Link Rel Values 1835 The following table indicates the index value to use for the link- 1836 entry group's rel item (see Section 2.7). These values match the 1837 link rel values defined in the ISO/IEC 19770-2:2015 [SWID] 1838 specification. The "Index" value indicates the value to use as the 1839 link-entry group ownership item's value. The "Relationship Type" 1840 provides human-readable text for the value. The "Definition" 1841 describes the semantic meaning of each entry. 1843 +-------+-------------------+---------------------------------------+ 1844 | Index | Relationship Type | Definition | 1845 +=======+===================+=======================================+ 1846 | 1 | ancestor | The link references a SWID/CoSWID | 1847 | | | tag for a previous release of this | 1848 | | | software. This can be useful to | 1849 | | | define an upgrade path. | 1850 +-------+-------------------+---------------------------------------+ 1851 | 2 | component | The link references a SWID/CoSWID | 1852 | | | tag for a separate component of | 1853 | | | this software. | 1854 +-------+-------------------+---------------------------------------+ 1855 | 3 | feature | The link references a configurable | 1856 | | | feature of this software that can | 1857 | | | be enabled or disabled without | 1858 | | | changing the installed files. | 1859 +-------+-------------------+---------------------------------------+ 1860 | 4 | installationmedia | The link references the | 1861 | | | installation package that can be | 1862 | | | used to install this software. | 1863 +-------+-------------------+---------------------------------------+ 1864 | 5 | packageinstaller | The link references the | 1865 | | | installation software needed to | 1866 | | | install this software. | 1867 +-------+-------------------+---------------------------------------+ 1868 | 6 | parent | The link references a SWID/CoSWID | 1869 | | | tag that is the parent of this | 1870 | | | SWID/CoSWID tag. This | 1871 | | | relationship can be used when | 1872 | | | multiple software components are | 1873 | | | part of a software bundle, where | 1874 | | | the "parent" is the SWID/CoSWID | 1875 | | | tag for the bundle, and each child | 1876 | | | is a "component". In such a case, | 1877 | | | each child component can provide a | 1878 | | | "parent" link relationship to the | 1879 | | | bundle's SWID/CoSWID tag, and the | 1880 | | | bundle can provide a "component" | 1881 | | | link relationship to each child | 1882 | | | software component. | 1883 +-------+-------------------+---------------------------------------+ 1884 | 7 | patches | The link references a SWID/CoSWID | 1885 | | | tag that this software patches. | 1886 | | | Typically only used for patch | 1887 | | | SWID/CoSWID tags (see | 1888 | | | Section 1.1). | 1889 +-------+-------------------+---------------------------------------+ 1890 | 8 | requires | The link references a prerequisite | 1891 | | | for installing this software. A | 1892 | | | patch SWID/CoSWID tag (see | 1893 | | | Section 1.1) can use this to | 1894 | | | represent base software or another | 1895 | | | patch that needs to be installed | 1896 | | | first. | 1897 +-------+-------------------+---------------------------------------+ 1898 | 9 | see-also | The link references other software | 1899 | | | that may be of interest that | 1900 | | | relates to this software. | 1901 +-------+-------------------+---------------------------------------+ 1902 | 10 | supersedes | The link references another | 1903 | | | software that this software | 1904 | | | replaces. A patch SWID/CoSWID tag | 1905 | | | (see Section 1.1) can use this to | 1906 | | | represent another patch that this | 1907 | | | patch incorporates or replaces. | 1908 +-------+-------------------+---------------------------------------+ 1909 | 11 | supplemental | The link references a SWID/CoSWID | 1910 | | | tag that this tag supplements. | 1911 | | | Used on supplemental SWID/CoSWID | 1912 | | | tags (see Section 1.1). | 1913 +-------+-------------------+---------------------------------------+ 1915 Table 6: Link Relationship Values 1917 The values above are registered in the IANA "SWID/CoSWID Link 1918 Relationship Value" registry defined in section Section 5.2.7. 1919 Additional values will likely be registered over time. Additionally, 1920 the index values 32768 through 65535 and the name prefix "x_" have 1921 been reserved for private use. 1923 4.5. Link Use Values 1925 The following table indicates the index value to use for the link- 1926 entry group's use item (see Section 2.7). These values match the 1927 link use values defined in the ISO/IEC 19770-2:2015 [SWID] 1928 specification. The "Index" value indicates the value to use as the 1929 link-entry group use item's value. The "Use Type" provides human- 1930 readable text for the value. The "Definition" describes the semantic 1931 meaning of each entry. 1933 +-------+-------------+----------------------------------------+ 1934 | Index | Use Type | Definition | 1935 +=======+=============+========================================+ 1936 | 1 | optional | From [SWID], "Not absolutely required; | 1937 | | | the [Link]'d software is installed | 1938 | | | only when specified." | 1939 +-------+-------------+----------------------------------------+ 1940 | 2 | required | From [SWID], "The [Link]'d software is | 1941 | | | absolutely required for an operation | 1942 | | | software installation." | 1943 +-------+-------------+----------------------------------------+ 1944 | 3 | recommended | From [SWID], "Not absolutely required; | 1945 | | | the [Link]'d software is installed | 1946 | | | unless specified otherwise." | 1947 +-------+-------------+----------------------------------------+ 1949 Table 7: Link Use Values 1951 The values above are registered in the IANA "SWID/CoSWID Link Use 1952 Value" registry defined in section Section 5.2.8. Additional values 1953 will likely be registered over time. Additionally, the index values 1954 128 through 255 and the name prefix "x_" have been reserved for 1955 private use. 1957 5. IANA Considerations 1959 This document has a number of IANA considerations, as described in 1960 the following subsections. In summary, 6 new registries are 1961 established with this request, with initial entries provided for each 1962 registry. New values for 5 other registries are also requested. 1964 5.1. CoSWID Items Registry 1966 This registry uses integer values as index values in CBOR maps. 1968 This document defines a new registry titled "CoSWID Items". Future 1969 registrations for this registry are to be made based on [RFC8126] as 1970 follows: 1972 +------------------+-------------------------+ 1973 | Range | Registration Procedures | 1974 +==================+=========================+ 1975 | 0-32767 | Standards Action | 1976 +------------------+-------------------------+ 1977 | 32768-4294967295 | Specification Required | 1978 +------------------+-------------------------+ 1980 Table 8: CoSWID Items Registration Proceedures 1982 All negative values are reserved for Private Use. 1984 Initial registrations for the "CoSWID Items" registry are provided 1985 below. Assignments consist of an integer index value, the item name, 1986 and a reference to the defining specification. 1988 +---------------+---------------------------+---------------+ 1989 | Index | Item Name | Specification | 1990 +===============+===========================+===============+ 1991 | 0 | tag-id | RFC-AAAA | 1992 +---------------+---------------------------+---------------+ 1993 | 1 | software-name | RFC-AAAA | 1994 +---------------+---------------------------+---------------+ 1995 | 2 | entity | RFC-AAAA | 1996 +---------------+---------------------------+---------------+ 1997 | 3 | evidence | RFC-AAAA | 1998 +---------------+---------------------------+---------------+ 1999 | 4 | link | RFC-AAAA | 2000 +---------------+---------------------------+---------------+ 2001 | 5 | software-meta | RFC-AAAA | 2002 +---------------+---------------------------+---------------+ 2003 | 6 | payload | RFC-AAAA | 2004 +---------------+---------------------------+---------------+ 2005 | 7 | hash | RFC-AAAA | 2006 +---------------+---------------------------+---------------+ 2007 | 8 | corpus | RFC-AAAA | 2008 +---------------+---------------------------+---------------+ 2009 | 9 | patch | RFC-AAAA | 2010 +---------------+---------------------------+---------------+ 2011 | 10 | media | RFC-AAAA | 2012 +---------------+---------------------------+---------------+ 2013 | 11 | supplemental | RFC-AAAA | 2014 +---------------+---------------------------+---------------+ 2015 | 12 | tag-version | RFC-AAAA | 2016 +---------------+---------------------------+---------------+ 2017 | 13 | software-version | RFC-AAAA | 2018 +---------------+---------------------------+---------------+ 2019 | 14 | version-scheme | RFC-AAAA | 2020 +---------------+---------------------------+---------------+ 2021 | 15 | lang | RFC-AAAA | 2022 +---------------+---------------------------+---------------+ 2023 | 16 | directory | RFC-AAAA | 2024 +---------------+---------------------------+---------------+ 2025 | 17 | file | RFC-AAAA | 2026 +---------------+---------------------------+---------------+ 2027 | 18 | process | RFC-AAAA | 2028 +---------------+---------------------------+---------------+ 2029 | 19 | resource | RFC-AAAA | 2030 +---------------+---------------------------+---------------+ 2031 | 20 | size | RFC-AAAA | 2032 +---------------+---------------------------+---------------+ 2033 | 21 | file-version | RFC-AAAA | 2034 +---------------+---------------------------+---------------+ 2035 | 22 | key | RFC-AAAA | 2036 +---------------+---------------------------+---------------+ 2037 | 23 | location | RFC-AAAA | 2038 +---------------+---------------------------+---------------+ 2039 | 24 | fs-name | RFC-AAAA | 2040 +---------------+---------------------------+---------------+ 2041 | 25 | root | RFC-AAAA | 2042 +---------------+---------------------------+---------------+ 2043 | 26 | path-elements | RFC-AAAA | 2044 +---------------+---------------------------+---------------+ 2045 | 27 | process-name | RFC-AAAA | 2046 +---------------+---------------------------+---------------+ 2047 | 28 | pid | RFC-AAAA | 2048 +---------------+---------------------------+---------------+ 2049 | 29 | type | RFC-AAAA | 2050 +---------------+---------------------------+---------------+ 2051 | 31 | entity-name | RFC-AAAA | 2052 +---------------+---------------------------+---------------+ 2053 | 32 | reg-id | RFC-AAAA | 2054 +---------------+---------------------------+---------------+ 2055 | 33 | role | RFC-AAAA | 2056 +---------------+---------------------------+---------------+ 2057 | 34 | thumbprint | RFC-AAAA | 2058 +---------------+---------------------------+---------------+ 2059 | 35 | date | RFC-AAAA | 2060 +---------------+---------------------------+---------------+ 2061 | 36 | device-id | RFC-AAAA | 2062 +---------------+---------------------------+---------------+ 2063 | 37 | artifact | RFC-AAAA | 2064 +---------------+---------------------------+---------------+ 2065 | 38 | href | RFC-AAAA | 2066 +---------------+---------------------------+---------------+ 2067 | 39 | ownership | RFC-AAAA | 2068 +---------------+---------------------------+---------------+ 2069 | 40 | rel | RFC-AAAA | 2070 +---------------+---------------------------+---------------+ 2071 | 41 | media-type | RFC-AAAA | 2072 +---------------+---------------------------+---------------+ 2073 | 42 | use | RFC-AAAA | 2074 +---------------+---------------------------+---------------+ 2075 | 43 | activation-status | RFC-AAAA | 2076 +---------------+---------------------------+---------------+ 2077 | 44 | channel-type | RFC-AAAA | 2078 +---------------+---------------------------+---------------+ 2079 | 45 | colloquial-version | RFC-AAAA | 2080 +---------------+---------------------------+---------------+ 2081 | 46 | description | RFC-AAAA | 2082 +---------------+---------------------------+---------------+ 2083 | 47 | edition | RFC-AAAA | 2084 +---------------+---------------------------+---------------+ 2085 | 48 | entitlement-data-required | RFC-AAAA | 2086 +---------------+---------------------------+---------------+ 2087 | 49 | entitlement-key | RFC-AAAA | 2088 +---------------+---------------------------+---------------+ 2089 | 50 | generator | RFC-AAAA | 2090 +---------------+---------------------------+---------------+ 2091 | 51 | persistent-id | RFC-AAAA | 2092 +---------------+---------------------------+---------------+ 2093 | 52 | product | RFC-AAAA | 2094 +---------------+---------------------------+---------------+ 2095 | 53 | product-family | RFC-AAAA | 2096 +---------------+---------------------------+---------------+ 2097 | 54 | revision | RFC-AAAA | 2098 +---------------+---------------------------+---------------+ 2099 | 55 | summary | RFC-AAAA | 2100 +---------------+---------------------------+---------------+ 2101 | 56 | unspsc-code | RFC-AAAA | 2102 +---------------+---------------------------+---------------+ 2103 | 57 | unspsc-version | RFC-AAAA | 2104 +---------------+---------------------------+---------------+ 2105 | 58-4294967295 | Unassigned | | 2106 +---------------+---------------------------+---------------+ 2108 Table 9: CoSWID Items Inital Registrations 2110 5.2. SWID/CoSWID Value Registries 2112 The following IANA registries provide a mechanism for new values to 2113 be added over time to common enumerations used by SWID and CoSWID. 2115 5.2.1. Registration Proceedures 2117 The following registries allow for the registration of index values 2118 and names. New registrations will be permitted through either the 2119 Standards Action policy or the Specification Required policy [BCP26]. 2120 The latter SHOULD be used only for registrations requested by SDOs 2121 outside the IETF. New index values will be provided on a First Come 2122 First Served as defined by [BCP26]. 2124 The following registries also reserve the integer-based index values 2125 in the range of -1 to -256 for private use as defined by [BCP26] in 2126 section 4.1. This allows values -1 to -24 to be expressed as a 2127 single uint_8t in CBOR, and values -25 to -256 to be expressed using 2128 an additional uint_8t in CBOR. 2130 5.2.2. Private Use of Index and Name Values 2132 The integer-based index values in the private use range (-1 to -256) 2133 are intended for testing purposes and closed environments; values in 2134 other ranges SHOULD NOT be assigned for testing. 2136 For names that correspond to private use index values, an 2137 Internationalized Domain Name prefix MUST be used to prevent name 2138 conflicts using the form: 2140 "domain.prefix-name" 2142 Where "domain.prefix" MUST be a valid Internationalized Domain Name 2143 as defined by [RFC5892], and "name" MUST be a unique name within the 2144 namespace defined by the "domain.prefix". Use of a prefix in this 2145 way allows for a name to be used initially in the private use range, 2146 and to be registered at a future point in time. This is consistent 2147 with the guidance in [BCP178]. 2149 5.2.3. Expert Review Guidelines 2151 Designated experts MUST ensure that new registration requests meet 2152 the following additional guidelines: 2154 * The requesting specification MUST provide a clear semantic 2155 definition for the new entry. This definition MUST clearly 2156 differentiate the requested entry from other previously registered 2157 entries. 2159 * The requesting specification MUST describe the intended use of the 2160 entry, including any co-constraints that exist between the use of 2161 the entry's index value or name, and other values defined within 2162 the SWID/CoSWID model. 2164 * Index values and names outside the private use space MUST NOT be 2165 used without registration. This is considered squatting and 2166 SHOULD be avoided. Designated experts MUST ensure that reviewed 2167 specifications register all appropriate index values and names. 2169 * Standards track documents MAY include entries registered in the 2170 range reserved for entries under the Specification Required 2171 policy. This can occur when a standards track document provides 2172 further guidance on the use of index values and names that are in 2173 common use, but were not registered with IANA. This situation 2174 SHOULD be avoided. 2176 * All registered names MUST be valid according to the XML Schema 2177 NMTOKEN data type (see [W3C.REC-xmlschema-2-20041028] section 2178 3.3.4). This ensures that registered names are compatible with 2179 the SWID format [SWID] where they are used. 2181 * Registration of vanity names SHOULD be discouraged. The 2182 requesting specification MUST provide a description of how a 2183 requested name will allow for use by multiple stakeholders. 2185 5.2.4. SWID/CoSWID Version Scheme Value Registry 2187 This document establishes a new registry titled "SWID/CoSWID Version 2188 Scheme Values". This registry provides index values for use as 2189 version-scheme item values in this document and version scheme names 2190 for use in [SWID]. 2192 [TO BE REMOVED: This registration should take place at the following 2193 location: https://www.iana.org/assignments/swid] 2195 This registry uses the registration proceedures defined in 2196 Section 5.2.1 with the following associated ranges: 2198 +-------------+-------------------------+ 2199 | Range | Registration Procedures | 2200 +=============+=========================+ 2201 | 0-16383 | Standards Action | 2202 +-------------+-------------------------+ 2203 | 16384-65535 | Specification Required | 2204 +-------------+-------------------------+ 2206 Table 10: CoSWID Version Scheme 2207 Registration Proceedures 2209 Assignments MUST consist of an integer Index value, the Version 2210 Scheme Name, and a reference to the defining specification. 2212 Initial registrations for the "SWID/CoSWID Version Scheme Value" 2213 registry are provided below, which are derived from the textual 2214 version scheme names defined in [SWID]. 2216 +-------------+-------------------------+-----------------+ 2217 | Index | Version Scheme Name | Specification | 2218 +=============+=========================+=================+ 2219 | 0 | Reserved | | 2220 +-------------+-------------------------+-----------------+ 2221 | 1 | multipartnumeric | See Section 4.1 | 2222 +-------------+-------------------------+-----------------+ 2223 | 2 | multipartnumeric+suffix | See Section 4.1 | 2224 +-------------+-------------------------+-----------------+ 2225 | 3 | alphanumeric | See Section 4.1 | 2226 +-------------+-------------------------+-----------------+ 2227 | 4 | decimal | See Section 4.1 | 2228 +-------------+-------------------------+-----------------+ 2229 | 5-16383 | Unassigned | | 2230 +-------------+-------------------------+-----------------+ 2231 | 16384 | semver | [SEMVER] | 2232 +-------------+-------------------------+-----------------+ 2233 | 16385-65535 | Unassigned | | 2234 +-------------+-------------------------+-----------------+ 2236 Table 11: CoSWID Version Scheme Inital Registrations 2238 Registrations MUST conform to the expert review guidelines defined in 2239 Section 5.2.3. 2241 Designated experts MUST also ensure that newly requested entries 2242 define a value space for the corresponding version item that is 2243 unique from other previously registered entries. Note: The inital 2244 registrations violate this requirement, but are included for 2245 backwards compatibility with [SWID]. Guidelines on how to deconflict 2246 these value spaces are defined in section Section 4.1. 2248 5.2.5. SWID/CoSWID Entity Role Value Registry 2250 This document establishes a new registry titled "SWID/CoSWID Entity 2251 Role Values". This registry provides index values for use as entity- 2252 entry role item values in this document and entity role names for use 2253 in [SWID]. 2255 [TO BE REMOVED: This registration should take place at the following 2256 location: https://www.iana.org/assignments/swid] 2258 This registry uses the registration proceedures defined in 2259 Section 5.2.1 with the following associated ranges: 2261 +---------+-------------------------+ 2262 | Range | Registration Procedures | 2263 +=========+=========================+ 2264 | 0-127 | Standards Action | 2265 +---------+-------------------------+ 2266 | 128-255 | Specification Required | 2267 +---------+-------------------------+ 2269 Table 12: CoSWID Entity Role 2270 Registration Proceedures 2272 Assignments consist of an integer Index value, a Role Name, and a 2273 reference to the defining specification. 2275 Initial registrations for the "SWID/CoSWID Entity Role Value" 2276 registry are provided below, which are derived from the textual 2277 entity role names defined in [SWID]. 2279 +-------+-----------------+-----------------+ 2280 | Index | Role Name | Specification | 2281 +=======+=================+=================+ 2282 | 0 | Reserved | | 2283 +-------+-----------------+-----------------+ 2284 | 1 | tagCreator | See Section 4.2 | 2285 +-------+-----------------+-----------------+ 2286 | 2 | softwareCreator | See Section 4.2 | 2287 +-------+-----------------+-----------------+ 2288 | 3 | aggregator | See Section 4.2 | 2289 +-------+-----------------+-----------------+ 2290 | 4 | distributor | See Section 4.2 | 2291 +-------+-----------------+-----------------+ 2292 | 5 | licensor | See Section 4.2 | 2293 +-------+-----------------+-----------------+ 2294 | 6 | maintainer | See Section 4.2 | 2295 +-------+-----------------+-----------------+ 2296 | 7-255 | Unassigned | | 2297 +-------+-----------------+-----------------+ 2299 Table 13: CoSWID Entity Role Inital 2300 Registrations 2302 Registrations MUST conform to the expert review guidlines defined in 2303 Section 5.2.3. 2305 5.2.6. SWID/CoSWID Link Ownership Value Registry 2307 This document establishes a new registry titled "SWID/CoSWID Link 2308 Ownership Values". This registry provides index values for use as 2309 link-entry ownership item values in this document and link ownership 2310 names for use in [SWID]. 2312 [TO BE REMOVED: This registration should take place at the following 2313 location: https://www.iana.org/assignments/swid] 2315 This registry uses the registration proceedures defined in 2316 Section 5.2.1 with the following associated ranges: 2318 +---------+-------------------------+ 2319 | Range | Registration Procedures | 2320 +=========+=========================+ 2321 | 0-127 | Standards Action | 2322 +---------+-------------------------+ 2323 | 128-255 | Specification Required | 2324 +---------+-------------------------+ 2326 Table 14: CoSWID Link Ownership 2327 Registration Proceedures 2329 Assignments consist of an integer Index value, an Ownership Type 2330 Name, and a reference to the defining specification. 2332 Initial registrations for the "SWID/CoSWID Link Ownership Value" 2333 registry are provided below, which are derived from the textual 2334 entity role names defined in [SWID]. 2336 +-------+---------------------+-----------------+ 2337 | Index | Ownership Type Name | Definition | 2338 +=======+=====================+=================+ 2339 | 0 | Reserved | | 2340 +-------+---------------------+-----------------+ 2341 | 1 | abandon | See Section 4.3 | 2342 +-------+---------------------+-----------------+ 2343 | 2 | private | See Section 4.3 | 2344 +-------+---------------------+-----------------+ 2345 | 3 | shared | See Section 4.3 | 2346 +-------+---------------------+-----------------+ 2347 | 4-255 | Unassigned | | 2348 +-------+---------------------+-----------------+ 2350 Table 15: CoSWID Link Ownership Inital 2351 Registrations 2353 Registrations MUST conform to the expert review guidlines defined in 2354 Section 5.2.3. 2356 5.2.7. SWID/CoSWID Link Relationship Value Registry 2358 This document establishes a new registry titled "SWID/CoSWID Link 2359 Relationship Values". This registry provides index values for use as 2360 link-entry rel item values in this document and link ownership names 2361 for use in [SWID]. 2363 [TO BE REMOVED: This registration should take place at the following 2364 location: https://www.iana.org/assignments/swid] 2366 This registry uses the registration proceedures defined in 2367 Section 5.2.1 with the following associated ranges: 2369 +-------------+-------------------------+ 2370 | Range | Registration Procedures | 2371 +=============+=========================+ 2372 | 0-32767 | Standards Action | 2373 +-------------+-------------------------+ 2374 | 32768-65535 | Specification Required | 2375 +-------------+-------------------------+ 2377 Table 16: CoSWID Link Relationship 2378 Registration Proceedures 2380 Assignments consist of an integer Index value, the Relationship Type 2381 Name, and a reference to the defining specification. 2383 Initial registrations for the "SWID/CoSWID Link Relationship Value" 2384 registry are provided below, which are derived from the link 2385 relationship values defined in [SWID]. 2387 +----------+------------------------+-----------------+ 2388 | Index | Relationship Type Name | Specification | 2389 +==========+========================+=================+ 2390 | 0 | Reserved | | 2391 +----------+------------------------+-----------------+ 2392 | 1 | ancestor | See Section 4.4 | 2393 +----------+------------------------+-----------------+ 2394 | 2 | component | See Section 4.4 | 2395 +----------+------------------------+-----------------+ 2396 | 3 | feature | See Section 4.4 | 2397 +----------+------------------------+-----------------+ 2398 | 4 | installationmedia | See Section 4.4 | 2399 +----------+------------------------+-----------------+ 2400 | 5 | packageinstaller | See Section 4.4 | 2401 +----------+------------------------+-----------------+ 2402 | 6 | parent | See Section 4.4 | 2403 +----------+------------------------+-----------------+ 2404 | 7 | patches | See Section 4.4 | 2405 +----------+------------------------+-----------------+ 2406 | 8 | requires | See Section 4.4 | 2407 +----------+------------------------+-----------------+ 2408 | 9 | see-also | See Section 4.4 | 2409 +----------+------------------------+-----------------+ 2410 | 10 | supersedes | See Section 4.4 | 2411 +----------+------------------------+-----------------+ 2412 | 11 | supplemental | See Section 4.4 | 2413 +----------+------------------------+-----------------+ 2414 | 12-65535 | Unassigned | | 2415 +----------+------------------------+-----------------+ 2417 Table 17: CoSWID Link Relationship Inital Registrations 2419 Registrations MUST conform to the expert review guidlines defined in 2420 Section 5.2.3. 2422 Designated experts MUST also ensure that a newly requested entry 2423 documents the URI schemes allowed to be used in an href associated 2424 with the link relationship and the expected resolution behavior of 2425 these URI schemes. This will help to ensure that SWID/CoSWID 2426 applications are able to interoperate when resolving resources 2427 referenced by a link of a given type. 2429 5.2.8. SWID/CoSWID Link Use Value Registry 2431 This document establishes a new registry titled "SWID/CoSWID Link Use 2432 Values". This registry provides index values for use as link-entry 2433 use item values in this document and link use names for use in 2434 [SWID]. 2436 [TO BE REMOVED: This registration should take place at the following 2437 location: https://www.iana.org/assignments/swid] 2439 This registry uses the registration proceedures defined in 2440 Section 5.2.1 with the following associated ranges: 2442 +---------+-------------------------+ 2443 | Range | Registration Procedures | 2444 +=========+=========================+ 2445 | 0-127 | Standards Action | 2446 +---------+-------------------------+ 2447 | 128-255 | Specification Required | 2448 +---------+-------------------------+ 2450 Table 18: CoSWID Link Use 2451 Registration Proceedures 2453 Assignments consist of an integer Index value, the Link Use Type 2454 Name, and a reference to the defining specification. 2456 Initial registrations for the "SWID/CoSWID Link Use Value" registry 2457 are provided below, which are derived from the link relationship 2458 values defined in [SWID]. 2460 +-------+--------------------+-----------------+ 2461 | Index | Link Use Type Name | Specification | 2462 +=======+====================+=================+ 2463 | 0 | Reserved | | 2464 +-------+--------------------+-----------------+ 2465 | 1 | optional | See Section 4.5 | 2466 +-------+--------------------+-----------------+ 2467 | 2 | required | See Section 4.5 | 2468 +-------+--------------------+-----------------+ 2469 | 3 | recommended | See Section 4.5 | 2470 +-------+--------------------+-----------------+ 2471 | 4-255 | Unassigned | | 2472 +-------+--------------------+-----------------+ 2474 Table 19: CoSWID Link Use Inital Registrations 2476 Registrations MUST conform to the expert review guidlines defined in 2477 Section 5.2.3. 2479 5.3. swid+cbor Media Type Registration 2481 IANA is requested to add the following to the IANA "Media Types" 2482 registry. 2484 Type name: application 2486 Subtype name: swid+cbor 2488 Required parameters: none 2490 Optional parameters: none 2492 Encoding considerations: Must be encoded as using [RFC7049]. See 2493 RFC-AAAA for details. 2495 Security considerations: See Section 6 of RFC-AAAA. 2497 Interoperability considerations: Applications MAY ignore any key 2498 value pairs that they do not understand. This allows backwards 2499 compatible extensions to this specification. 2501 Published specification: RFC-AAAA 2503 Applications that use this media type: The type is used by software 2504 asset management systems, vulnerability assessment systems, and in 2505 applications that use remote integrity verification. 2507 Fragment identifier considerations: Fragment identification for 2508 application/swid+cbor is supported by using fragment identifiers as 2509 specified by RFC-7049 section 7.5. 2511 Additional information: 2513 Magic number(s): first five bytes in hex: da 53 57 49 44 2515 File extension(s): coswid 2517 Macintosh file type code(s): none 2519 Macintosh Universal Type Identifier code: org.ietf.coswid conforms to 2520 public.data 2522 Person & email address to contact for further information: Henk 2523 Birkholz 2525 Intended usage: COMMON 2527 Restrictions on usage: None 2529 Author: Henk Birkholz 2531 Change controller: IESG 2533 5.4. CoAP Content-Format Registration 2535 IANA is requested to assign a CoAP Content-Format ID for the CoSWID 2536 media type in the "CoAP Content-Formats" sub-registry, from the "IETF 2537 Review or IESG Approval" space (256..999), within the "CoRE 2538 Parameters" registry [RFC7252]: 2540 +-----------------------+----------+------+-----------+ 2541 | Media type | Encoding | ID | Reference | 2542 +=======================+==========+======+===========+ 2543 | application/swid+cbor | - | TBD1 | RFC-AAAA | 2544 +-----------------------+----------+------+-----------+ 2546 Table 20: CoAP Content-Format IDs 2548 5.5. CBOR Tag Registration 2550 IANA is requested to allocate a tag in the "CBOR Tags" registry, 2551 preferably with the specific value requested: 2553 +------------+-----------+-----------------------------+ 2554 | Tag | Data Item | Semantics | 2555 +============+===========+=============================+ 2556 | 1398229316 | map | Concise Software Identifier | 2557 | | | (CoSWID) [RFC-AAAA] | 2558 +------------+-----------+-----------------------------+ 2560 Table 21: CoSWID CBOR Tag 2562 5.6. URI Scheme Registrations 2564 The ISO 19770-2:2015 SWID specification describes use of the "swid" 2565 and "swidpath" URI schemes, which are currently in use in 2566 implementations. This document continues this use for CoSWID. The 2567 following subsections provide registrations for these schemes in to 2568 ensure that a permanent registration exists for these schemes that is 2569 suitable for use in the SWID and CoSWID specifications. 2571 5.6.1. "swid" URI Scheme Registration 2573 There is a need for a scheme name that can be used in URIs that point 2574 to a specific SWID/CoSWID tag by that tag's tag-id, such as the use 2575 of the link entry as described in section Section 2.7) of this 2576 document. Since this scheme is used in a standards track document 2577 and an ISO standard, this scheme needs to be used without fear of 2578 conflicts with current or future actual schemes. The scheme "swid" 2579 is hereby registered as a 'permanent' scheme for that purpose. 2581 The "swid" scheme is specified as follows: 2583 Scheme syntax: The scheme speific part consists of a SWID or CoSWID 2584 tag's tag-id that is URI encoded according to [RFC3986] section 2.1. 2585 The following expression is a valid example: 2587 2589 Scheme semantics: URIs in the "swid" scheme are to be used to 2590 reference a SWID or CoSWID tag by its tag-id. A tag-id referenced in 2591 this way can be used to indentify the tag resource in the context of 2592 where it is referenced from. For example, when a tag is installed on 2593 a given device, that tag can reference related tags on the same 2594 device using this URI scheme. 2596 Encoding considerations: See Section 2.5 of [RFC3986] for guidelines. 2598 Interoperability considerations: None. 2600 Security considerations: None. 2602 5.6.2. "swidpath" URI Scheme Registration 2604 There is a need for a scheme name that can be used in URIs to 2605 indentify a collection of specific SWID/CoSWID tags with data 2606 elements that match an XPath expression, such as the use of the link 2607 entry as described in section Section 2.7) of this document. Since 2608 this scheme is used in a standards track document and an ISO 2609 standard, this scheme needs to be used without fear of conflicts with 2610 current or future actual schemes. The scheme "swidpath" is hereby 2611 registered as a 'permanent' scheme for that purpose. 2613 The "swidpath" scheme is specified as follows: 2615 Scheme syntax: The scheme speific part consists of an XPath 2616 expression as defined by [W3C.REC-xpath20-20101214]. The included 2617 XPath expression will be URI encoded according to [RFC3986] section 2618 2.1. 2620 Scheme semantics: URIs in the "swidpath" scheme are to be used 2621 specify the data that must be found in a given SWID/CoSWID tag for 2622 that tag to be considered a matching tag to be included in the 2623 identified tag collection. Tags to be evaluated include all tags in 2624 the context of where the tag is referenced from. For example, when a 2625 tag is installed on a given device, that tag can reference related 2626 tags on the same device using this URI scheme. A tag is matching if 2627 the XPath evaluation result value has an effective boolean value of 2628 "true" according to [W3C.REC-xpath20-20101214] section 2.4.3. rence 2629 related tags on the same device using this URI scheme. 2631 Encoding considerations: See Section 2.5 of [RFC3986] for guidelines. 2633 Interoperability considerations: None. 2635 Security considerations: None. 2637 5.7. CoSWID Model for use in SWIMA Registration 2639 The Software Inventory Message and Attributes (SWIMA) for PA-TNC 2640 specification [RFC8412] defines a standardized method for collecting 2641 an endpoint device's software inventory. A CoSWID can provide 2642 evidence of software installation which can then be used and 2643 exchanged with SWIMA. This registration adds a new entry to the IANA 2644 "Software Data Model Types" registry defined by [RFC8412] to support 2645 CoSWID use in SWIMA as follows: 2647 Pen: 0 2649 Integer: TBD2 2651 Name: Concise Software Identifier (CoSWID) 2653 Defining Specification: RFC-AAAA 2655 Deriving Software Identifiers: 2657 A Software Identifier generated from a CoSWID tag is expressed as a 2658 concatenation of the form: 2660 TAG_CREATOR_REGID "_" "_" UNIQUE_ID 2662 Where TAG_CREATOR_REGID is the reg-id ietm value of the tag's entity 2663 item having the role value of 1 (corresponding to "tag creator"), and 2664 the UNIQUE_ID is the same tag's tag-id item. If the tag-id item's 2665 value is expressed as a 16 byte binary string, the UNIQUE_ID MUST be 2666 represented using the UUID string representation defined in [RFC4122] 2667 including the "urn:uuid:" prefix. 2669 The TAG_CREATOR_REGID and the UNIQUE_ID are connected with a double 2670 underscore (_), without any other connecting character or whitespace. 2672 6. Security Considerations 2674 SWID and CoSWID tags contain public information about software 2675 components and, as such, do not need to be protected against 2676 disclosure on an endpoint. Similarly, SWID/CoSWID tags are intended 2677 to be easily discoverable by applications and users on an endpoint in 2678 order to make it easy to identify and collect all of an endpoint's 2679 SWID tags. As such, any security considerations regarding SWID/ 2680 CoSWID tags focus on the application of SWID/CoSWID tags to address 2681 security challenges, and the possible disclosure of the results of 2682 those applications. 2684 A tag is considered "authoritative" if the SWID/CoSWID tag was 2685 created by the software provider. An authoritative SWID/CoSWID tag 2686 contains information about a software component provided by the 2687 maintainer of the software component, who is expected to be an expert 2688 in their own software. Thus, authoritative SWID/CoSWID tags can be 2689 trusted to represent authoritative information about the software 2690 component. 2692 A signed SWID/CoSWID tag (see Appendix A) whose signature has been 2693 validated can be relied upon to be unchanged since it was signed. By 2694 contrast, the data contained in unsigned tags cannot be trusted to be 2695 unmodified. 2697 When an authoritative tag is signed, the software provider can be 2698 authenticated as the originator of the signature. Having a signed 2699 authoritative SWID/CoSWID tag can be useful when the information in 2700 the tag needs to be trusted, such as when the tag is being used to 2701 convey reference integrity measurements for software components. 2703 SWID/CoSWID tags are designed to be easily added and removed from an 2704 endpoint along with the installation or removal of software 2705 components. On endpoints where addition or removal of software 2706 components is tightly controlled, the addition or removal of SWID 2707 tags can be similarly controlled. On more open systems, where many 2708 users can manage the software inventory, SWID/CoSWID tags can be 2709 easier to add or remove. On such systems, it can be possible to add 2710 or remove SWID/CoSWID tags in a way that does not reflect the actual 2711 presence or absence of corresponding software components. Similarly, 2712 not all software products automatically install SWID/CoSWID tags, so 2713 products can be present on an endpoint without providing a 2714 corresponding SWID tag. As such, any collection of SWID/CoSWID tags 2715 cannot automatically be assumed to represent either a complete or 2716 fully accurate representation of the software inventory of the 2717 endpoint. However, especially on endpoint devices that more strictly 2718 control the ability to add or remove applications, SWID/CoSWID tags 2719 are an easy way to provide an preliminary understanding of that 2720 endpoint's software inventory. 2722 Any report of an endpoint's SWID/CoSWID tag collection provides 2723 information about the software inventory of that endpoint. If such a 2724 report is exposed to an attacker, this can tell them which software 2725 products and versions thereof are present on the endpoint. By 2726 examining this list, the attacker might learn of the presence of 2727 applications that are vulnerable to certain types of attacks. As 2728 noted earlier, SWID/CoSWID tags are designed to be easily 2729 discoverable by an endpoint, but this does not present a significant 2730 risk since an attacker would already need to have access to the 2731 endpoint to view that information. However, when the endpoint 2732 transmits its software inventory to another party, or that inventory 2733 is stored on a server for later analysis, this can potentially expose 2734 this information to attackers who do not yet have access to the 2735 endpoint. For this reason, it is important to protect the 2736 confidentiality of SWID/CoSWID tag information that has been 2737 collected from an endpoint, not because those tags individually 2738 contain sensitive information, but because the collection of SWID/ 2739 CoSWID tags and their association with an endpoint reveals 2740 information about that endpoint's attack surface. 2742 Finally, both the ISO-19770-2:2015 XML schema SWID definition and the 2743 CoSWID data definition allow for the construction of "infinite" tags 2744 with link item loops or tags that contain malicious content with the 2745 intent of creating non-deterministic states during validation or 2746 processing of those tags. While software providers are unlikely to 2747 do this, SWID/CoSWID tags can be created by any party and the SWID/ 2748 CoSWID tags collected from an endpoint could contain a mixture of 2749 vendor and non-vendor created tags. For this reason, tools that 2750 consume SWID/CoSWID tags ought to treat the tag contents as 2751 potentially malicious and employ input sanitizing and loop detection 2752 on the tags they ingest. 2754 7. Acknowledgments 2756 This document draws heavily on the concepts defined in the ISO/IEC 2757 19770-2:2015 specification. The authors of this document are 2758 grateful for the prior work of the 19770-2 contributors. 2760 We are also grateful to the careful reviews provided by ... 2762 8. Change Log 2764 [THIS SECTION TO BE REMOVED BY THE RFC EDITOR.] 2766 Changes from version 12 to version 14: 2768 * Moved key identifier to protected COSE header 2770 * Fixed index reference for hash 2772 * Removed indirection of CDDL type definition for filesystem-item 2774 * Fixed quantity of resource and process 2776 * Updated resource-collection 2778 * Renamed socket name in software-meta to be consistent in naming 2780 * Aligned excerpt examples in I-D text with full CDDL 2782 * Fixed titels where title was referring to group instead of map 2784 * Added missig date in SEMVER 2786 * Fixed root cardinality for file and directory, etc. 2788 * Transformed path-elements-entry from map to group for re-usability 2790 * Scrubbed IANA section 2792 * Removed redundant supplemental rule 2794 * Aligned discrepancy with ISO spec. 2796 * Addressed comments on typos. 2798 * Fixed kramdown nits and BCP reference. 2800 * Addressed comments from WGLC reviewers. 2802 Changes in version 12: 2804 * Addressed a bunch of minor editorial issues based on WGLC 2805 feedback. 2807 * Added text about the use of UTF-8 in CoSWID. 2809 * Adjusted tag-id to allow for a UUID to be provided as a bstr. 2811 * Cleaned up descriptions of index ranges throughout the document, 2812 removing discussion of 8 bit, 16 bit, etc. 2814 * Adjusted discussion of private use ranges to use negative integer 2815 values and to be more clear throughout the document. 2817 * Added discussion around resolving overlapping value spaces for 2818 version schemes. 2820 * Added a set of expert review guidelines for new IANA registries 2821 created by this document. 2823 * Added new registrations for the "swid" and "swidpath" URI schemes, 2824 and for using CoSWID with SWIMA. 2826 Changes from version 03 to version 11: 2828 * Reduced representation complexity of the media-entry type and 2829 removed the section describing the older data structure. 2831 * Added more signature schemes from COSE 2833 * Included a minimal required set of normative language 2835 * Reordering of attribute name to integer label by priority 2836 according to semantics. 2838 * Added an IANA registry for CoSWID items supporting future 2839 extension. 2841 * Cleaned up IANA registrations, fixing some inconsistencies in the 2842 table labels. 2844 * Added additional CDDL sockets for resource collection entries 2845 providing for additional extension points to address future SWID/ 2846 CoSWID extensions. 2848 * Updated section on extension points to address new CDDL sockets 2849 and to reference the new IANA registry for items. 2851 * Removed unused references and added new references to address 2852 placeholder comments. 2854 * Added table with semantics for the link ownership item. 2856 * Clarified language, made term use more consistent, fixed 2857 references, and replacing lowercase RFC2119 keywords. 2859 Changes from version 02 to version 03: 2861 * Updated core CDDL including the CDDL design pattern according to 2862 RFC 8428. 2864 Changes from version 01 to version 02: 2866 * Enforced a more strict separation between the core CoSWID 2867 definition and additional usage by moving content to corresponding 2868 appendices. 2870 * Removed artifacts inherited from the reference schema provided by 2871 ISO (e.g. NMTOKEN(S)) 2873 * Simplified the core data definition by removing group and type 2874 choices where possible 2876 * Minor reordering of map members 2878 * Added a first extension point to address requested flexibility for 2879 extensions beyond the any-element 2881 Changes from version 00 to version 01: 2883 * Ambiguity between evidence and payload eliminated by introducing 2884 explicit members (while still 2886 * allowing for "empty" SWID tags) 2888 * Added a relatively restrictive COSE envelope using cose_sign1 to 2889 define signed CoSWID (single signer only, at the moment) 2891 * Added a definition how to encode hashes that can be stored in the 2892 any-member using existing IANA tables to reference hash-algorithms 2894 Changes since adopted as a WG I-D -00: 2896 * Removed redundant any-attributes originating from the ISO- 2897 19770-2:2015 XML schema definition 2899 * Fixed broken multi-map members 2901 * Introduced a more restrictive item (any-element-map) to represent 2902 custom maps, increased restriction on types for the any-attribute, 2903 accordingly 2905 * Fixed X.1520 reference 2906 * Minor type changes of some attributes (e.g. NMTOKENS) 2908 * Added semantic differentiation of various name types (e,g. fs- 2909 name) 2911 Changes from version 06 to version 07: 2913 * Added type choices/enumerations based on textual definitions in 2914 19770-2:2015 2916 * Added value registry request 2918 * Added media type registration request 2920 * Added content format registration request 2922 * Added CBOR tag registration request 2924 * Removed RIM appendix to be addressed in complementary draft 2926 * Removed CWT appendix 2928 * Flagged firmware resource collection appendix for revision 2930 * Made use of terminology more consistent 2932 * Better defined use of extension points in the CDDL 2934 * Added definitions for indexed values 2936 * Added IANA registry for Link use indexed values 2938 Changes from version 05 to version 06: 2940 * Improved quantities 2942 * Included proposals for implicit enumerations that were NMTOKENS 2944 * Added extension points 2946 * Improved exemplary firmware-resource extension 2948 Changes from version 04 to version 05: 2950 * Clarified language around SWID and CoSWID to make more consistent 2951 use of these terms. 2953 * Added language describing CBOR optimizations for single vs. arrays 2954 in the model front matter. 2956 * Fixed a number of grammatical, spelling, and wording issues. 2958 * Documented extension points that use CDDL sockets. 2960 * Converted IANA registration tables to markdown tables, reserving 2961 the 0 value for use when a value is not known. 2963 * Updated a number of references to their current versions. 2965 Changes from version 03 to version 04: 2967 * Re-index label values in the CDDL. 2969 * Added a section describing the CoSWID model in detail. 2971 * Created IANA registries for entity-role and version-scheme 2973 Changes from version 02 to version 03: 2975 * Updated CDDL to allow for a choice between a payload or evidence 2977 * Re-index label values in the CDDL. 2979 * Added item definitions 2981 * Updated references for COSE, CBOR Web Token, and CDDL. 2983 Changes from version 01 to version 02: 2985 * Added extensions for Firmware and CoSWID use as Reference 2986 Integrity Measurements (CoSWID RIM) 2988 * Changes meta handling in CDDL from use of an explicit use of items 2989 to a more flexible unconstrained collection of items. 2991 * Added sections discussing use of COSE Signatures and CBOR Web 2992 Tokens 2994 Changes from version 00 to version 01: 2996 * Added CWT usage for absolute SWID paths on a device 2998 * Fixed cardinality of type-choices including arrays 3000 * Included first iteration of firmware resource-collection 3002 9. References 3004 9.1. Normative References 3006 [BCP178] Saint-Andre, P., Crocker, D., and M. Nottingham, 3007 "Deprecating the "X-" Prefix and Similar Constructs in 3008 Application Protocols", BCP 178, RFC 6648, 3009 DOI 10.17487/RFC6648, June 2012, 3010 . 3012 [BCP26] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 3013 Writing an IANA Considerations Section in RFCs", BCP 26, 3014 RFC 8126, DOI 10.17487/RFC8126, June 2017, 3015 . 3017 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3018 Requirement Levels", BCP 14, RFC 2119, 3019 DOI 10.17487/RFC2119, March 1997, 3020 . 3022 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 3023 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 3024 2003, . 3026 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 3027 Resource Identifier (URI): Generic Syntax", STD 66, 3028 RFC 3986, DOI 10.17487/RFC3986, January 2005, 3029 . 3031 [RFC5198] Klensin, J. and M. Padlipsky, "Unicode Format for Network 3032 Interchange", RFC 5198, DOI 10.17487/RFC5198, March 2008, 3033 . 3035 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 3036 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 3037 September 2009, . 3039 [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and 3040 Internationalized Domain Names for Applications (IDNA)", 3041 RFC 5892, DOI 10.17487/RFC5892, August 2010, 3042 . 3044 [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object 3045 Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, 3046 October 2013, . 3048 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 3049 Application Protocol (CoAP)", RFC 7252, 3050 DOI 10.17487/RFC7252, June 2014, 3051 . 3053 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 3054 Writing an IANA Considerations Section in RFCs", BCP 26, 3055 RFC 8126, DOI 10.17487/RFC8126, June 2017, 3056 . 3058 [RFC8152] Schaad, J., "CBOR Object Signing and Encryption (COSE)", 3059 RFC 8152, DOI 10.17487/RFC8152, July 2017, 3060 . 3062 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 3063 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 3064 May 2017, . 3066 [RFC8288] Nottingham, M., "Web Linking", RFC 8288, 3067 DOI 10.17487/RFC8288, October 2017, 3068 . 3070 [RFC8412] Schmidt, C., Haynes, D., Coffin, C., Waltermire, D., and 3071 J. Fitzgerald-McKay, "Software Inventory Message and 3072 Attributes (SWIMA) for PA-TNC", RFC 8412, 3073 DOI 10.17487/RFC8412, July 2018, 3074 . 3076 [RFC8610] Birkholz, H., Vigano, C., and C. Bormann, "Concise Data 3077 Definition Language (CDDL): A Notational Convention to 3078 Express Concise Binary Object Representation (CBOR) and 3079 JSON Data Structures", RFC 8610, DOI 10.17487/RFC8610, 3080 June 2019, . 3082 [SAM] "Information technology - Software asset management - Part 3083 5: Overview and vocabulary", ISO/IEC 19770-5:2015, 15 3084 November 2013. 3086 [SEMVER] Preston-Werner, T., "Semantic Versioning 2.0.0", 3087 . 3089 [SWID] "Information technology - Software asset management - Part 3090 2: Software identification tag", ISO/IEC 19770-2:2015, 1 3091 October 2015. 3093 [W3C.REC-css3-mediaqueries-20120619] 3094 Rivoal, F., "Media Queries", World Wide Web Consortium 3095 Recommendation REC-css3-mediaqueries-20120619, 19 June 3096 2012, . 3099 [W3C.REC-xmlschema-2-20041028] 3100 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 3101 Second Edition", World Wide Web Consortium Recommendation 3102 REC-xmlschema-2-20041028, 28 October 2004, 3103 . 3105 [W3C.REC-xpath20-20101214] 3106 Berglund, A., Boag, S., Chamberlin, D., Fernandez, M., 3107 Kay, M., Robie, J., and J. Simeon, "XML Path Language 3108 (XPath) 2.0 (Second Edition)", World Wide Web Consortium 3109 Recommendation REC-xpath20-20101214, 14 December 2010, 3110 . 3112 [X.1520] "Recommendation ITU-T X.1520 (2014), Common 3113 vulnerabilities and exposures", 20 April 2011. 3115 9.2. Informative References 3117 [CamelCase] 3118 "UpperCamelCase", 29 August 2014, 3119 . 3121 [I-D.birkholz-rats-tuda] 3122 Fuchs, A., Birkholz, H., McDonald, I., and C. Bormann, 3123 "Time-Based Uni-Directional Attestation", Work in 3124 Progress, Internet-Draft, draft-birkholz-rats-tuda-02, 9 3125 March 2020, . 3128 [KebabCase] 3129 "KebabCase", 18 December 2014, 3130 . 3132 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 3133 Unique IDentifier (UUID) URN Namespace", RFC 4122, 3134 DOI 10.17487/RFC4122, July 2005, 3135 . 3137 [RFC8322] Field, J., Banghart, S., and D. Waltermire, "Resource- 3138 Oriented Lightweight Information Exchange (ROLIE)", 3139 RFC 8322, DOI 10.17487/RFC8322, February 2018, 3140 . 3142 [RFC8520] Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage 3143 Description Specification", RFC 8520, 3144 DOI 10.17487/RFC8520, March 2019, 3145 . 3147 [SWID-GUIDANCE] 3148 Waltermire, D., Cheikes, B.A., Feldman, L., and G. Witte, 3149 "Guidelines for the Creation of Interoperable Software 3150 Identification (SWID) Tags", NISTIR 8060, April 2016, 3151 . 3153 Appendix A. Signed Concise SWID Tags using COSE 3155 SWID tags, as defined in the ISO-19770-2:2015 XML schema, can include 3156 cryptographic signatures to protect the integrity of the SWID tag. 3157 In general, tags are signed by the tag creator (typically, although 3158 not exclusively, the vendor of the software component that the SWID 3159 tag identifies). Cryptographic signatures can make any modification 3160 of the tag detectable, which is especially important if the integrity 3161 of the tag is important, such as when the tag is providing reference 3162 integrity measurements for files. 3164 The ISO-19770-2:2015 XML schema uses XML DSIG to support 3165 cryptographic signatures. CoSWID tags require a different signature 3166 scheme than this. COSE (CBOR Object Signing and Encryption) provides 3167 the required mechanism [RFC8152]. Concise SWID can be wrapped in a 3168 COSE Single Signer Data Object (COSE_Sign1) that contains a single 3169 signature. The following CDDL defines a more restrictive subset of 3170 header attributes allowed by COSE tailored to suit the requirements 3171 of Concise SWID tags. 3173 3174 signed-coswid = #6.18(COSE-Sign1-coswid) 3176 cose-label = int / tstr 3177 cose-values = any 3179 protected-signed-coswid-header = { 3180 1 => int, ; algorithm identifier 3181 3 => "application/swid+cbor", 3182 4 => bstr, ; key identifier 3183 * cose-label => cose-values, 3184 } 3186 unprotected-signed-coswid-header = { 3187 * cose-label => cose-values, 3188 } 3190 COSE-Sign1-coswid = [ 3191 protected: bstr .cbor protected-signed-coswid-header, 3192 unprotected: unprotected-signed-coswid-header, 3193 payload: bstr .cbor concise-swid-tag, 3194 signature: bstr, 3195 ] 3196 3198 Optionally, the COSE_Sign structure that allows for more than one 3199 signature to be applied to a CoSWID tag MAY be used. The 3200 corresponding usage scenarios are domain-specific and require well- 3201 defined application guidance. Representation of the corresponding 3202 guidance is out-of-scope of this document. 3204 Additionally, the COSE Header counter signature MAY be used as an 3205 attribute in the unprotected header map of the COSE envelope of a 3206 CoSWID. The application of counter signing enables second parties to 3207 provide a signature on a signature allowing for a proof that a 3208 signature existed at a given time (i.e., a timestamp). 3210 Authors' Addresses 3212 Henk Birkholz 3213 Fraunhofer SIT 3214 Rheinstrasse 75 3215 64295 Darmstadt 3216 Germany 3218 Email: henk.birkholz@sit.fraunhofer.de 3219 Jessica Fitzgerald-McKay 3220 Department of Defense 3221 9800 Savage Road 3222 Ft. Meade, Maryland 3223 United States of America 3225 Email: jmfitz2@nsa.gov 3227 Charles Schmidt 3228 The MITRE Corporation 3229 202 Burlington Road 3230 Bedford, Maryland 01730 3231 United States of America 3233 Email: cmschmidt@mitre.org 3235 David Waltermire 3236 National Institute of Standards and Technology 3237 100 Bureau Drive 3238 Gaithersburg, Maryland 20877 3239 United States of America 3241 Email: david.waltermire@nist.gov