Concise Software Identification TagsFraunhofer SITRheinstrasse 75Darmstadt64295Germanyhenk.birkholz@sit.fraunhofer.deDepartment of Defense9800 Savage RoadFt. MeadeMarylandUSAjmfitz2@nsa.govThe MITRE Corporation202 Burlington RoadBedfordMaryland01730USAcmschmidt@mitre.orgNational Institute of Standards and Technology100 Bureau DriveGaithersburgMaryland20877USAdavid.waltermire@nist.gov
Security
SACM Working GroupInternet-DraftThis document defines a concise representation of ISO/IEC 19770-2:2015 Software Identification (SWID) tags
that are interoperable with the XML schema definition of ISO/IEC 19770-2:2015.
Next to the inherent capability of SWID tags to express
arbitrary context information, Concise SWID (CoSWID) tags support the definition of additional semantics via
well-defined data definitions incorporated by extension points.SWID tags have several use-applications including but not limited to:Software Inventory Management, a part of a Software Asset Management
process, which requires an accurate list of discernible deployed software
components.Vulnerability Assessment, which requires a semantic link between standardized
vulnerability descriptions and software components installed on IT-assets .Remote Attestation, which requires a link between reference integrity
measurements (RIM) and security logs of measured software components
.SWID tags, as defined in ISO-19770-2:2015 , provide a standardized
XML-based record format that identifies and describes a specific release of a
software component. Different software components, and even different releases of a
particular software component, each have a different SWID tag record associated
with them. SWID tags are meant to be flexible and able to express a broad set of metadata
about a software component.While there are very few required fields in SWID tags, there are many optional
fields that support different use scenarios. A
SWID tag consisting of only required fields might be a few hundred bytes in
size; however, a tag containing many of the optional fields can be many orders of
magnitude larger. Thus, real-world instances of SWID tags can be fairly large, and the communication of
SWID tags in use-applications, such as those described earlier, can cause a large
amount of data to be transported. This can be larger than acceptable for
constrained devices and networks. Concise SWID (CoSWID) tags significantly reduce the amount of
data transported as compared to a typical SWID tag. This reduction is enabled
through the use of CBOR, which maps the human-readable labels of SWID data items to
more concise integer labels (indices). The use of CBOR to express SWID information in CoSWID tags allows both CoSWID and SWID tags to be part of an
enterprise security solution for a wider range of endpoints and environments.In addition to defining the format of a SWID tag record, ISO/IEC 19770-2:2015
defines requirements concerning the SWID tag lifecycle. Specifically, when a
software component is installed on an endpoint, that software component’s SWID tag is also
installed. Likewise, when the software component is uninstalled or replaced, the SWID tag
is deleted or replaced, as appropriate. As a result, ISO/IEC 19770-2:2015 describes
a system wherein there is a correspondence between the set of installed software
components on an endpoint, and the presence of the corresponding SWID tags
for these components on that endpoint. CoSWIDs share the same lifecycle requirements
as a SWID tag.The SWID specification and supporting guidance provided in NIST Internal Report (NISTIR) 8060: Guidelines for the Creation of Interoperable SWID Tags defines four types of SWID tags: primary, patch, corpus, and supplemental.Primary Tag - A SWID or CoSWID tag that identifies and describes a software component is installed on a computing device. A primary tag is intended to be installed on an endpoint along with the corresponding software component.Patch Tag - A SWID or CoSWID tag that identifies and describes an installed patch which has made incremental changes to a software component installed on an endpoint. A patch tag is intended to be installed on an endpoint along with the corresponding software component patch.Corpus Tag - A SWID or CoSWID tag that identifies and describes an installable software component in its pre-installation state. A corpus tag can be used to represent metadata about an installation package or installer for a software component, a software update, or a patch.Supplemental Tag - A SWID or CoSWID tag that allows additional information to be associated with a referenced SWID tag. This helps to ensure that SWID Primary and Patch Tags provided by a software provider are not modified by software management tools, while allowing these tools to provide their own software metadata.The type of a tag is determined by specific data elements, which is discussed in .Corpus, primary, and patch tags have similar functions in that they describe the existence and/or presence of different types of software (e.g., software installers, software installations, software patches), and, potentially, different states of software components. In contrast, supplemental tags furnish additional information not contained in corpus, primary, or patch tags. All four tag types come into play at various points in the software lifecycle, and support software management processes that depend on the ability to accurately determine where each software component is in its lifecycle. illustrates the steps in the software lifecycle and the relationships among those lifecycle events supported by the four types of SWID and CoSWID tags, as follows:Software Deployment. Before the software component is installed (i.e., pre-installation), and while the product is being deployed, a corpus tag provides information about the installation files and distribution media (e.g., CD/DVD, distribution package).Software Installation. A primary tag will be installed with the software component (or subsequently created) to uniquely identify and describe the software component. Supplemental tags are created to augment primary tags with additional site-specific or extended information. While not illustrated in the figure, patch tags can also be installed during software installation to provide information about software fixes deployed along with the base software installation.Software Patching. When a new patch is applied to the software component, a new patch tag is provided, supplying details about the patch and its dependencies. While not illustrated in the figure, a corpus tag can also provide information about the patch installer, and patching dependencies that need to be installed before the patch.Software Upgrading. As a software component is upgraded to a new version, new primary and supplemental tags replace existing tags, enabling timely and accurate tracking of updates to software inventory. While not illustrated in the figure, a corpus tag can also provide information about the upgrade installer, and dependencies that need to be installed before the upgrade.Software Removal. Upon removal of the software component, relevant SWID tags are removed. This removal event can trigger timely updates to software inventory reflecting the removal of the product and any associated patch or supplemental tags.Note: While not fully illustrated in the figure, supplemental tags can be associated with any corpus, primary, or patch tag to provide additional metadata about an installer, installed software, or installed patch respectively.Understanding the use of CoSWIDs in the software lifecycle provides a basis for understanding the information provided in a CoSWID and the associated semantics of this information. Each of the different SWID and CoSWID tag types provide different sets of
information. For example, a “corpus tag” is used to
describe a software component’s installation image on an installation media, while a
“patch tag” is meant to describe a patch that modifies some other software component.This document defines the CoSWID tag format, a more concise representation of SWID information in the Concise
Binary Object Representation (CBOR) . The structure of a CoSWID is described via the Concise
Data Definition Language (CDDL) . The resulting CoSWID data
definition is aligned to the information able to be expressed with the XML schema definition of ISO-19770-2:2015
. This alignment allows both SWID and CoSWID tags to represent a common set of SWID information and to support all SWID tag use
cases. To achieve this end, the CDDL representation includes every SWID tag field and attribute.The vocabulary, i.e., the CDDL names of the types and members used in
the CoSWID data definition, are mapped to more concise labels represented as
small integer values. The names used in the CDDL data definition and the mapping to
the CBOR representation using integer labels is based on the vocabulary of the
XML attribute and element names defined in ISO/IEC 19770-2:2015.The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”,
“MAY”, and “OPTIONAL” in this document are to be interpreted as
described in BCP 14 when, and only when, they
appear in all capitals, as shown here.The following is a CDDL representation for a CoSWID tag. The CamelCase notation used in the XML schema definition is changed to a hyphen-separated
notation (e.g. ResourceCollection is named resource-collection) in the CoSWID data definition. In essence, “looks-like-this”.
This deviation from the original notation used in the XML representation reduces ambiguity when referencing
certain attributes in corresponding textual descriptions. An attribute referred to by its name in CamelCase
notation explicitly relates to XML SWID tags; an attribute referred to by its name in
KebabCase notation explicitly relates to CoSWID tags. This approach simplifies the
composition of further work that reference both XML SWID and CoSWID documents.Human-readable labels of members in CDDL map data definitions are mapped to integer indices via a block of rules at the bottom of the definition. The 57 character strings of the SWID vocabulary are replacesm which would have to be
stored or transported in full if using the original vocabulary.In CBOR, an array is encoded using bytes that identify the array, and the array’s length or stop point (see ). To make items that support 1 or more values, the following CDDL notion is used.The CDDL rule above allows for a more efficient CBOR encoding of the data when a single value is used. This is accomplished by avoiding the need to first encode the array. Conversely, hen two or more values are encoded, the bytes identifing the array are used. This modeling pattern is used frequently in the CoSWID CDDL data definition to allow for more effecient encoding of single values.The following subsections describe the different parts of the CoSWID model.The corresponding CoSWID data definition includes two kinds of augmentation.The explicit definition of types for attributes that are typically stored in
the “any attribute” of an ISO-19770-2:2015 in XML representation. These are
covered in .The inclusion of extension points in the CoSWID data definition using CDDL sockets (see section 3.9). The use of CDDL sockets allow for well-formed extensions to be defined in supplementary CDDL descriptions that support additional uses of CoSWID tags that go beyond the original scope of ISO-19770-2:2015 tags. This extension mechanism can also be used to update the CoSWID format as revisions to ISO-19770-2 are published.The following CDDL sockets (extension points) are defined in this document, which allow the addition of new information structures to their respective CDDL groups.Map NameCDDL SocketDefined inconcise-swid-tag$$coswid-extensionentity-entry$$entity-extensionlink-entry$$link-extensionsoftware-meta-entry$$meta-extensionfile-entry$$file-extensiondirectory-entry$$directory-extensionprocess-entry$$process-extensionresource-entry$$resource-extensionpayload-entry$$payload-extensionevidence-entry$$evidence-extensionThe CoSWID Items Registry defined in provides a registration mechanism allowing new items, and their associated index values, to be added to the CoSWID model through the use of the CDDL sockets described above. This registration mechanism provides for well-known index values for data items in CoSWID extensions, allowing these index values to be recognized by implementations supporting a given extension.The following CDDL sockets defined in this document allow for adding new values to corresponding type-choices (i.e. to represent enumerations) via custom CDDL data definitions.Enumeration NameCDDL SocketDefined inversion-scheme$version-schemerole$roleownership$ownershiprel$reluse$useA number of SWID/CoSWID value registries are also defined in that allow new valid values to be registered with IANA for the enumerations above. This registration mechanism supports the definition of new well-known index values and names for new enumeration values used by SWID and CoSWID. This registration mechanism allows new standardized enumerated values to be shared between both specifications (and implementations) over time.The CDDL data definition for the root concise-swid-tag map is as follows and this rule and its constraints MUST be followed when creating or validating a CoSWID tag:The following describes each member of the concise-swid-tag root map.global-attributes: A list of items including an optional language definition to support the
processing of text-string values and an unbounded set of any-attribute items. Described in .tag-id (index 0): A textual identifier uniquely referencing a (composite) software component. The tag
identifier MUST be globally unique. There are no strict guidelines on
how this identifier is structured, but examples include a 16 byte GUID (e.g.
class 4 UUID) , or a text string appended to a DNS domain name to ensure uniqueness across organizations.tag-version (index 12): An integer value that indicate the specific release revision of the tag. Typically, the initial value of this field is set to 0, and the value is monotonically increased for subsequent tags produced for the same software component release. This value allows a CoSWID tag producer to correct an incorrect tag previously released, without indicating a change to the underlying software component the tag represents. For example, the tag version would be changed to add new metadata, to correct a broken link, to add a missing payload entry, etc. When producing a revised tag, the new tag-version value MUST be greater than the old tag-version value.corpus (index 8): A boolean value that indicates if the tag identifies and describes an installable software component in its pre-installation state. Installable software includes a installation package or installer for a software component, a software update, or a patch. If the CoSWID tag represents installable software, the corpus item MUST be set to “true”. If not provided the default value MUST be considered “false”.patch (index 9): A boolean value that indicates if the tag identifies and describes an installed patch which has made incremental changes to a software component installed on a computing device. Typically, an installed patch has made a set of file modifications to pre-installed software, and does not alter the version number or the descriptive metadata of an installed software
component. If a CoSWID tag is for a patch, the patch item MUST be set to “true”. If not provided the default value MUST be considered “false”.supplemental (index 11): A boolean value that indicates if the tag is providing additional information to be associated with another referenced SWID or CoSWID tag. Tags using this item help to ensure that primary and patch tags provided by a software provider are not modified by software management tools, while allowing these tools to provide their own software metadata for a software component. If a CoSWID tag is a supplemental tag, the supplemental item MUST be set to “true”. If not provided the default value MUST be considered “false”.software-name (index 1): This textual item provides the software component’s name. This name is likely the same name that would appear in a package management tool.software-version (index 13): A textual value representing the specific release or development version of the software component.version-scheme (index 14): An 8-bit integer or textual value representing the versioning scheme used for the software-version item. If an integer value is used it MUST be a value from the SWID/CoSWID Version Scheme Value Registry (see section or a value in the private use range: 32768-65535.
An initial set of pre-defined version-scheme index and text values are defined in that are based on the version-scheme values defined in . These pre-defined version-scheme values are registered with IANA in the “SWID/CoSWID Version Scheme Value” registry , and MAY be expanded in the future.
The value of an ownership item MUST be one of the following: The index (preferred) or string value of a role from the IANA in the “SWID/CoSWID Version Scheme Value” registry.An index value in the range 32768 through 65535, to indicate that a private use index value is used.A string value prefixed with “x_”, to indicate that a private use string value is used.media (index 10): This text value is a hint to the tag consumer to understand what this tag
applies to. This item represents a
query as defined by the W3C Media Queries Recommendation (see ).software-meta (index 5): An open-ended map of key/value data pairs.
A number of predefined keys can be used within this item providing for
common usage and semantics across the industry. Use of this map allows any additional
attribute to be included in the tag. It is expected that industry groups will use a common set of attribute names to allow for interoperability within their communities. Described in .entity (index 2): Provides information about one or more organizations responsible for producing the CoSWID tag, and producing or releasing the software component referenced by this
CoSWID tag. Described in .link (index 4): Provides a means to establish relationship arcs between the tag and another items. A given link can be used to establish the relationship between tags or to reference another resource that is related to the
CoSWID tag, e.g.
vulnerability database association, ROLIE feed , MUD resource , software download location, etc).
This is modeled after the HTML “link” element. Described in .payload (index 6): This item represents the software artifacts that compose the target software. For example, the files included with an installer for a corpus tag or installed on an endpoint when the software component
is installed for a primary or patch tag. The artifacts listed in a payload may be a superset of the software artifacts that are actually installed. Based on user selections at install time,
an installation might not include every artifact that could be created or executed on the
endpoint when the software component is installed or run. Described in .evidence-entry (index 3): This item records the results of a software discovery process used to identify untagged software on an endpoint. This item provides a means to represent indicators for why software is believed to be installed on the endpoint. In such a case, a CoSWID tag is created when the endpoint is scanned by the tool performing the scan. Described in .$$coswid-extension: This CDDL socket is used to add new information structures to the concise-swid-tag root map. See .The following co-constraints apply to the information provided by in the concise-swid-tag group.The patch and supplemental items MUST NOT both be set to “true”.If the patch item is set to “true”, the tag SHOULD contain at least one link item with the rel(ation) item value of “patches” and an href item specifying an association with the software that was patched.If the supplemental item is set to “true”, the tag SHOULD contain at least one link item with the rel(ation) item value of “supplements” and an href item specifying an association with the software that is supplemented.If all of the corpus, patch, and supplemental items are “false”, or if the corpus item is set to “true”, then a software-version item MUST be included with a value set to the version of the software component. This ensures that primary and corpus tags have an identifiable software version.The global-attributes group provides a list of items including an optional
language definition to support the processing of text-string values and an
unbounded set of any-attribute items allowing for additional items to be
provided as a general point of extension in the model.The CDDL for the global-attributes follows:The following describes each child item of this group.lang (index 15): A textual language tag that
conforms with IANA “Language Subtag Registry” . The context of the specified language applies to all sibling and descendant textual values, unless a descendant object has defined a different language tag. Thus, a new context is established when a descendant object redefines a new language tag. All textual values within a given context MUST be considered expressed in the specified language.any-attribute: This sub-group provides a means to include arbitrary information
via label (“key”) value pairs. Labels can be either a single integer or text string. Values can be either a single integer or text string, or an array of integers or text strings.The CDDL for the entity-entry group follows:The following describes each child item of this group.global-attributes: The global-attributes group described in .entity-name (index 32): The textual name of the organizational entity claiming the roles specified by the role item for the CoSWID tag.reg-id (index 32): The registration id value is intended to uniquely identify a naming authority in a
given scope (e.g. global, organization, vendor, customer, administrative domain,
etc.) for the referenced entity. The value of an
registration ID MUST be a RFC 3986 URI. The scope SHOULD be the scope of an
organization. In a given scope, the registration id MUST be used consistently for CoSWID tag production.role (index 33): The relationship(s) between the entity, and this tag or the referenced software component. Use of index values instead of text for these pre-defined roles allows a CoSWID to be more concise.
An initial set of pre-defined role index and text values are defined in that are based on the roles defined in . These pre-defined roles are registered with IANA in the “SWID/CoSWID Entity Role Value” registry , and MAY be expanded in the future.
The value of a role item MUST be one of the following: The index (preferred) or string value of a role from the IANA in the “SWID/CoSWID Entity Role Value” registry.An index value in the range 128 through 255, to indicate that a private use index value is used.A string value prefixed with “x_”, to indicate that a private use string value is used.
The following additional requirements exist for the use of the “role” item: An entity item MUST be provided with the role of “tag-creator” for every CoSWID tag. This indicates the organization that created the CoSWID tag.An entity item SHOULD be provided with the role of “software-creator” for every CoSWID tag, if this information is known to the tag creator. This indicates the organization that created the referenced software component.thumbprint (index 34): The value of the thumbprint item provides an integer-based hash algorithm identifier (hash-alg-id) and a byte string value (hash-value) that contains the corresponding hash value (i.e. the
thumbprint) of the signing entity’s public key certificate. This provides an indicator of which entity signed the CoSWID tag, which will typically be the tag creator. If the hash-alg-id is not known, then the integer value “0” MUST be used. This ensures parity between the SWID tag specification , which does not allow an algorithm to be identified for this field. See for more details on the use of the hash-entry data structure.$$entity-extension: This CDDL socket can be used to extend the entity-entry group model. See .The CDDL for the link-entry map follows:The following describes each member of this map.global-attributes: The global-attributes group described in .artifact (index: 37): To be used with rel=”installation-media”, this item value can provide the path to the installer executable or script that can be run to launch the referenced installation. Links with the same artifact name MUST be considered mirrors of each other, allowing the installation media to be acquired from any of the described sources.href (index 38): A URI for the referenced resource. The “href” item’s value can be, but is not limited to, the following (which is a slightly modified excerpt from ):
If no URI scheme is provided, then the URI is to be interpreted as being relative to the URI of the CoSWID tag. For example, “./folder/supplemental.coswid”.a physical resource location with any acceptable URI scheme (e.g., file:// http:// https:// ftp://)a URI with “coswid:” as the scheme, which refers to another CoSWID by tag-id. This
URI would need to be resolved in the context of the endpoint by software
that can lookup other CoSWID tags. For example, “coswid:2df9de35-0aff-4a86-ace6-f7dddd1ade4c” references the tag with the tag-id value “2df9de35-0aff-4a86-ace6-f7dddd1ade4c”.a URI with “swidpath:” as the scheme, which refers to another CoSIWD via an
XPATH query. This URI would need to be resolved in the context of the system
entity via software components that can lookup other CoSWID tags and
select the appropriate tag based on an XPATH query . Examples include:swidpath://SoftwareIdentity[Entity/@regid=’http://contoso.com’] would retrieve all CoSWID tags that include an entity where the regid is “Contoso” or swidpath://SoftwareIdentity[Meta/@persistentId=’b0c55172-38e9-4e36-be86-92206ad8eddb’] would match CoSWID tags with the persistent-id value “b0c55172-38e9-4e36-be86-92206ad8eddb”.media (index 10): A hint to the consumer of the link to what the target item is applicable for. This item represents a
query as defined by the W3C Media Queries Recommendation (see ). See also media defined in .ownership (index 39): Used when the “href” item references another software component to indicate the degree of ownership between the software component referenced by the COSWID tag and the software component referenced by the link.
An initial set of pre-defined ownership index and text values are defined in that are based on the ownership values defined in . These pre-defined ownership values are registered with IANA in the “SWID/CoSWID Link Ownership Value” registry , and MAY be expanded in the future.
The value of an ownership item MUST be one of the following: The index (preferred) or string value of a role from the IANA in the “SWID/CoSWID Link Ownership Value” registry.An index value in the range 128 through 255, to indicate that a private use index value is used.A string value prefixed with “x_”, to indicate that a private use string value is used.rel (index 40): Identifies the relationship between this CoSWID and the target resource indicated by the “href” item.
An initial set of pre-defined rel index and text values are defined in that are based on the rel values defined in . These pre-defined rel values are registered with IANA in the “SWID/CoSWID Link Relationship Value” registry , and MAY be expanded in the future.
The value of a rel item MUST be one of the following: The index (preferred) or string value of a role from the IANA in the “SWID/CoSWID Link Relationship Value” registry.An index value in the range 128 through 255, to indicate that a private use index value is used.A string value prefixed with “x_”, to indicate that a private use string value is used.A string value, as defined by , corresponding to a “Relation Name” from the IANA “Link Relation Types” registry: https://www.iana.org/assignments/link-relations/link-relations.xhtml. When a string value defined in the IANA “SWID/CoSWID Link Relationship Value” registry matches a Relation Name defined in the IANA “Link Relation Types” registry, the value in the IANA “SWID/CoSWID Link Relationship Value” registry MUST be used instead, as this relationship has a specialized meaning in the context of a SWID/CoSWID tag.media-type (index 41): The media type for the target resource, providing a resource consumer with
a hint of what type of resource to expect. Media types are identified by referencing a “Name” from the IANA “Media Types” registry: http://www.iana.org/assignments/media-types/media-types.xhtml.use (index 42): Determines if the referenced software component has to be installed before installing the tagged software component.
An initial set of pre-defined use index and text values are defined in that are based on the use values defined in . These pre-defined use values are registered with IANA in the “SWID/CoSWID Link Use Value” registry , and MAY be expanded in the future.
The value of an ownership item MUST be one of the following: The index (preferred) or string value of a role from the IANA in the “SWID/CoSWID Link Use Value” registry.An index value in the range 128 through 255, to indicate that a private use index value is used.A string value prefixed with “x_”, to indicate that a private use string value is used.$$link-extension: This CDDL socket can be used to extend the link-entry map model. See .The CDDL for the software-meta-entry map follows:The following describes each child item of this group.global-attributes: The global-attributes group described in .activation-status (index 43): A textual value that identifies how the software component has been activated, which might relate to specific terms and conditions for its use (e.g. Trial, Serialized, Licensed, Unlicensed, etc) and relate to an entitlement. This attribute is typically used in supplemental tags as it contains information that might be selected during a specific install.channel-type (index 44): A textual value that identfies which sales, licensing, or marketing channel the software component has been targeted for (e.g. Volume, Retail, OEM, Academic, etc). This attribute is typically used in supplemental tags as it contains information that might be selected during a specific install.colloquial-version (index 45): A textual value for the software component’s informal or colloquial version. Examples may include a year value, a major version number, or similar value that are used to identify a group of specific software component releases that are part of the same release/support cycle. This version can be the same through multiple releases of a software component, while the software-version specified in the concise-swid-tag group is much more specific and will change for each software component release. This version is intended to be used for string comparison only, and is not intended to be used to determine if a specific value is earlier or later in a sequence.description (index 46): A textual value that provides a detailed description of the software component, which can be multiple sentences.edition (index 47): A textual value indicating that the software component represents a functional variation of the code base used to support multiple software components. For examplem, this item can be used to differentiate enterprise, standard, or professional variants of a software component.entitlement-data-required (index 48): A boolean value that proof of indicator to determine if accompanying proof of entitlement is needed when a software license reconciliation process is performed.entitlement-key (index 49): A vendor-specific textual key that can be used to identify and establish a relationship to an entitlement. Examples of an entitlement-key might include a serial number, product key, or license key). For values that relate to a given software component install (i.e., license key), a supplemental tag will typically contain this information. In other cases where a general-purpose key can be provided that applies to all possible installs of the software component on different endpoints, a primary tag will typically contain this information.generator (index 50): The name (or tag-id) of the software component that created the CoSWID tag. If the generating software component has a SWID or CoSWID tag, then the tag-id for the generating software component SHOULD be provided.persistent-id (index 51): A GUID used to identify a related set of software components. Software components sharing the same persistent-id can be different versions.product (index 52): A basic name for the software component that can be common across multiple tagged software components (e.g., Apache HTTPD).product-family (index 53): A textual value indicating the software components overall product family. This should be used when multiple related software components form a larger capability that is installed on multiple different endpoints. For example, some software families may consist of server, client, and shared service components that are part of a larger capability. Email systems, enterprise applications, backup services, web conferencing, and similar capabilities are examples of families.revision (index 54): A string value indicating an informal or colloquial release version of the software. This value can provide a different version value as compared to the software-version specified in the concise-swid-tag group. This is useful when one or more releases need to have an informal version label that differs from the specific exact version value specified by software-version. Examples can include SP1, RC1, Beta, etc.summary (index 55): A short description of the software component. This MUST be a single sentence suitable for display in a user interface.unspsc-code (index 56): An 8 digit UNSPSC classification code for the software component. For more information see, http://www.unspsc.org/.unspsc-version (index 57): The version of UNSPSC used to define the unspsc-code value.$$meta-extension: This CDDL socket can be used to extend the software-meta-entry group model. See .CoSWID adds explicit support for the representation of hash entries using algorithms that are
registered in the IANA “Named Information Hash Algorithm Registry” using the hash-entry member (label 58).The number used as a value for hash-alg-id MUST refer an ID in the “Named Information Hash Algorithm Registry” (see https://www.iana.org/assignments/named-information/named-information.xhtml); other hash algorithms MUST NOT be used. The hash-value MUST represent the raw hash value of the hashed resource generated using the hash algorithm indicated by the hash-alg-id.A list of items both used in evidence (created by a software discovery process) and
payload (installed in an endpoint) content of a CoSWID tag document to
structure and differentiate the content of specific CoSWID tag types. Potential
content includes directories, files, processes, or resources.The CDDL for the resource-collection group follows:The following describes each member of the groups and maps illustrated above.filesystem-item: A list of items both used in representing the nodes of a file-system hierarchy (i.e., directory items that allow one or more directories to be defined in the
file structure), and file items that allow one or more files to be specified for
a given location.global-attributes: The global-attributes group described in .directory (index 16): A directory item allows child directory and file items to be defined within a directory hierarchy for the software component.file (index 17): A file item allows details about a file to be provided for the software component.process (index 18): A process item allows details to be provided about the runtime behavior of the software component, such as information that will appear in a process listing on a device.resource (index 19): A resource item can be used to provide details about a resource expected to be found on an endpoint, or evidence collected related to the software component.size (index 20): The file’s size in bytes.file-version (index 21): The file’s version as reported by querying information on the file from the operating system.key (index 22): A boolean value indicating if a file or directory is significant or required for the software component to execute or function properly. These are files or directories that can be used to affirmatively determine if the software component is installed on an endpoint.location (index 23): The filesystem path where a file is expected to be located when installed or copied. This path SHOULD be relative to the location of the parent directory item, or if no parent is defined, the location MUST be relative to the location of the CoSWID tag. The location MUST not include a file’s name, which is provided by the fs-name item.fs-name (index 24): The name of the directory or file without any path information.root (index 25): A filesystem-specific name for the root of the filesystem. The location item is considered relative to this location if specified. If not provided, the value provided by the location item is expected to be relative to its parent or the location of the CoSWID tag if no parent is provided.path-elements (index 26): This group provides the ability to define a directory structure for
files defined in payload or evidence items.process-name (index 27): The software component’s process name as it will appear in an endpoint’s process list.pid (index 28): The process ID identified for a running instance of the software component in the endpoint’s process list. This is used as part of the evidence item.type (index 29): A string indicating the type of resource.$$resource-collection-extension: This CDDL socket can be used to extend the resource-collection group model. This can be used to add new specialized types of resources. See .$$file-extension: This CDDL socket can be used to extend the file-entry group model. See .$$directory-extension: This CDDL socket can be used to extend the directory-entry group model. See .$$process-extension: This CDDL socket can be used to extend the process-entry group model. See .$$resource-extension: This CDDL socket can be used to extend the group model. See .$$-extension: This CDDL socket can be used to extend the resource-entry group model. See .The CDDL for the payload-entry group follows:The following describes each child item of this group.global-attributes: The global-attributes group described in .resource-collection: The resource-collection group described in .$$payload-extension: This CDDL socket can be used to extend the payload-entry group model. See .The CDDL for the evidence-entry group follows:The following describes each child item of this group.global-attributes: The global-attributes group described in .resource-collection: The resource-collection group described in .date (index 35): The date and time the information was collected pertaining to the evidence item.device-id (index 36): The endpoint’s string identifier from which the evidence was collected.$$evidence-extension: This CDDL socket can be used to extend the evidence-entry group model. See .In order to create a valid CoSWID document the structure of the corresponding CBOR message MUST
adhere to the following CDDL data definition.The operational model for SWID and CoSWID tags was introduced in , which described four different CoSWID tag types. The following additional rules apply to the use of CoSWID tags to ensure that created tags properly identify the tag type.The first matching rule MUST determine the type of the CoSWID tag.Primary Tag: A CoSWID tag MUST be considered a primary tag if the corpus, patch, and supplemental items are “false”.Supplemental Tag: A CoSWID tag MUST be considered a supplemental tag if the supplemental item is set to “true”.Corpus Tag: A CoSWID tag MUST be considered a corpus tag if the corpus item is “true”.Patch Tag: A CoSWID tag MUST be considered a patch tag if the patch item is “true”.The following table contains a set of values for use in the concise-swid-tag group’s version-scheme item. These values match the version schemes defined in the ISO/IEC 19770-2:2015 specification. Index value indicates the value to use as the version-scheme item’s value. The Version Scheme Name provides human-readable text for the value. The Definition describes the syntax of allowed values for each entry.IndexVersion Scheme NameDefinition1multipartnumericNumbers separated by dots, where the numbers are interpreted as integers (e.g.,1.2.3, 1.4.5, 1.2.3.4.5.6.7)2multipartnumeric+suffixNumbers separated by dots, where the numbers are interpreted as integers with an additional textual suffix (e.g., 1.2.3a)3alphanumericStrictly a string, sorting is done alphanumerically4decimalA floating point number (e.g., 1.25 is less than 1.3)16384semverFollows the specificationThe values above are registered in the IANA “SWID/CoSWID Version Scheme Value” registry defined in section . Additional entires will likely be registered over time in this registry. Additionally, the index values 32768 through 65535 have been reserved for private use.The following table indicates the index value to use for the entity-entry group’s role item (see ). These values match the entity roles defined in the ISO/IEC 19770-2:2015 specification. The “Index” value indicates the value to use as the role item’s value. The “Role Name” provides human-readable text for the value. The “Definition” describes the semantic meaning of each entry.IndexRole NameDefinition1tagCreatorThe person or organization that created the containing SWID or CoSWID tag2softwareCreatorFrom , “person or organization that creates a software product (3.46) or package”3aggregatorFrom {{SWID}, “An organization or system that encapsulates software from their own and/or other organizations into a different distribution process (as in the case of virtualization), or as a completed system to accomplish a specific task (as in the case of a value added reseller).”4distributorFrom , “An entity that furthers the marketing, selling and/or distribution of software from the original place of manufacture to the ultimate user without modifying the software, its packaging or its labelling.”5licensorFrom as “software licensor”, a “person or organization who owns or holds the rights to issue a software license for a specific software package”The values above are registered in the IANA “SWID/CoSWID Entity Role Value” registry defined in section . Additional valid values will likely be registered over time. Additionally, the index values 128 through 255 have been reserved for private use.The following table indicates the index value to use for the link-entry group’s ownership item (see ). These values match the link ownership values defined in the ISO/IEC 19770-2:2015 specification. The “Index” value indicates the value to use as the link-entry group ownership item’s value. The “Ownership Type” provides human-readable text for the value. The “Definition” describes the semantic meaning of each entry.IndexOwnership TypeDefinition1abandonIf the software component referenced by the CoSWID tag is uninstalled, then the referenced software SHOULD not be uninstalled2privateIf the software component referenced by the CoSWID tag is uninstalled, then the referenced software SHOULD be uninstalled as well.3sharedIf the software component referenced by the CoSWID tag is uninstalled, then the referenced software SHOULD be uninstalled if no other components sharing the software.The values above are registered in the IANA “SWID/CoSWID Link Ownership Value” registry defined in section . Additional valid values will likely be registered over time. Additionally, the index values 128 through 255 have been reserved for private use.The following table indicates the index value to use for the link-entry group’s rel item (see ). These values match the link rel values defined in the ISO/IEC 19770-2:2015 specification. The “Index” value indicates the value to use as the link-entry group ownership item’s value. The “Relationship Type” provides human-readable text for the value. The “Definition” describes the semantic meaning of each entry.IndexRelationship TypeDefinition1ancestorThe link references a SWID/CoSWID tag for an ancestor of this software. This can be useful to define an upgrade path.2componentThe link references a SWID/CoSWID tag for a separate component of this software.3featureThe link references a configurable feature of this software, that can be enabled or disabled without changing the installed files.4installationmediaThe link references the installation package that can be used to install this software.5packageinstallerThe link references the installation software needed to install this software.6parentThe link references a SWID/CoSWID tag that is the parent of this SWID/CoSWID tag.7patchesThe link references a SWID/CoSWID tag that this software patches. Typically only used for patch SWID/CoSWID tags (see ).8requiresThe link references a prerequisite for installing this software. A patch SWID/CoSWID tag (see ) can use this to represent base software or another patch that needs to be installed first.9see-alsoThe link references other software that may be of interest that relates to this software.10supersedesThe link references another software that this software replaces. A patch SWID/CoSWID tag (see ) can use this to represent another patch that this patch incorporates or replaces.11supplementalThe link references a SWID/CoSWID tag that this tag supplements. Used on supplemental SWID/CoSWID tags (see ).The values above are registered in the IANA “SWID/CoSWID Link Relationship Value” registry defined in section . Additional valid values will likely be registered over time. Additionally, the index values 32768 through 65535 have been reserved for private use.The following table indicates the index value to use for the link-entry group’s use item (see ). These values match the link use values defined in the ISO/IEC 19770-2:2015 specification. The “Index” value indicates the value to use as the link-entry group use item’s value. The “Use Type” provides human-readable text for the value. The “Definition” describes the semantic meaning of each entry.IndexUse TypeDefinition1optionalFrom , “Not absolutely required; the [Link]‘d software is installed only when specified.”2requiredFrom , “The [Link]‘d software is absolutely required for an operation software installation.”3recommendedFrom , “Not absolutely required; the [Link]‘d software is installed unless specified otherwise.”The values above are registered in the IANA “SWID/CoSWID Link Use Value” registry defined in section . Additional valid values will likely be registered over time. Additionally, the index values 128 through 255 have been reserved for private use.This document has a number of IANA considerations, as described in
the following subsections.This document uses integer values as index values in CBOR maps.This document defines a new a new registry titled
“CoSWID Items”. Future registrations for this
registry are to be made based on as follows:RangeRegistration Procedures0-32767Standards Action32768-4294967295Specification RequiredAll negative values are reserved for Private Use.Initial registrations for the “CoSWID Items” registry
are provided below. Assignments consist of an integer index value, the item name, and a reference to the defining specification.IndexItem NameSpecification0tag-idRFC-AAAA1software-nameRFC-AAAA2entityRFC-AAAA3evidenceRFC-AAAA4linkRFC-AAAA5software-metaRFC-AAAA6payloadRFC-AAAA7hashRFC-AAAA8corpusRFC-AAAA9patchRFC-AAAA10mediaRFC-AAAA11supplementalRFC-AAAA12tag-versionRFC-AAAA13software-versionRFC-AAAA14version-schemeRFC-AAAA15langRFC-AAAA16directoryRFC-AAAA17fileRFC-AAAA18processRFC-AAAA19resourceRFC-AAAA20sizeRFC-AAAA21file-versionRFC-AAAA22keyRFC-AAAA23locationRFC-AAAA24fs-nameRFC-AAAA25rootRFC-AAAA26path-elementsRFC-AAAA27process-nameRFC-AAAA28pidRFC-AAAA29typeRFC-AAAA31entity-nameRFC-AAAA32reg-idRFC-AAAA33roleRFC-AAAA34thumbprintRFC-AAAA35dateRFC-AAAA36device-idRFC-AAAA37artifactRFC-AAAA38hrefRFC-AAAA39ownershipRFC-AAAA40relRFC-AAAA41media-typeRFC-AAAA42useRFC-AAAA43activation-statusRFC-AAAA44channel-typeRFC-AAAA45colloquial-versionRFC-AAAA46descriptionRFC-AAAA47editionRFC-AAAA48entitlement-data-requiredRFC-AAAA49entitlement-keyRFC-AAAA50generatorRFC-AAAA51persistent-idRFC-AAAA52productRFC-AAAA53product-familyRFC-AAAA54revisionRFC-AAAA55summaryRFC-AAAA56unspsc-codeRFC-AAAA57unspsc-versionRFC-AAAA58-4294967295UnassignedThe following IANA registries provide a mechanism for new valid values to be added over time to common enumerations used by SWID and CoSWID.This document uses unsigned 16-bit index values to represent version-scheme item values. The
initial set of version-scheme values are derived from the textual version scheme names
defined in the ISO/IEC 19770-2:2015 specification .This document defines a new a new registry titled
“SWID/CoSWID Version Scheme Values”. Future registrations for this
registry are to be made based on as follows:[TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid]RangeRegistration Procedures0-16383Standards Action16384-32767Specification Required32768-65535Reserved for Private UseInitial registrations for the “SWID/CoSWID Version Scheme Value” registry
are provided below. Assignments consist of an integer Index value, the Version Scheme Name, and a reference to the defining specification.IndexVersion Scheme NameSpecification0Reserved1multipartnumericSee 2multipartnumeric+suffixSee 3alphanumericSee 4decimalSee 5-16383Unassigned16384semver16385-32767Unassigned32768-65535Reserved for Private UseThis document uses unsigned 8-bit index values to represent entity-entry role item values. The
initial set of Entity roles are derived from the textual role names
defined in the ISO/IEC 19770-2:2015 specification .This document defines a new a new registry titled
“SWID/CoSWID Entity Role Values”. Future registrations for this
registry are to be made based on as follows:[TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid]RangeRegistration Procedures0-31Standards Action32-127Specification Required128-255Reserved for Private UseInitial registrations for the “SWID/CoSWID Entity Role Value” registry
are provided below. Assignments consist of an integer Index value, a Role Name, and a reference to the defining specification.IndexRole NameSpecification0Reserved1tagCreatorSee 2softwareCreatorSee 3aggregatorSee 4distributorSee 5licensorSee 6-127Unassigned128-255Reserved for Private UseThis document uses unsigned 8-bit index values to represent link-entry ownership item values. The
initial set of Link ownership values are derived from the textual ownership names
defined in the ISO/IEC 19770-2:2015 specification .This document defines a new a new registry titled
“SWID/CoSWID Link Ownership Values”. Future registrations for this
registry are to be made based on as follows:[TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid]RangeRegistration Procedures0-31Standards Action32-127Specification Required128-255Reserved for Private UseInitial registrations for the “SWID/CoSWID Link Ownership Value” registry
are provided below. Assignments consist of an integer Index value, an Ownership Type Name, and a reference to the defining specification.IndexOwnership Type NameDefinition0Reserved1abandonSee 2privateSee 3sharedSee 4-16384Unassigned16385-32767Unassigned32768-65535Reserved for Private UseThis document uses unsigned 16-bit index values to represent link-entry rel item values. The
initial set of rel values are derived from the textual rel names
defined in the ISO/IEC 19770-2:2015 specification .This document defines a new a new registry titled
“SWID/CoSWID Link Relationship Values”. Future registrations for this
registry are to be made based on as follows:[TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid]RangeRegistration Procedures0-16383Standards Action16384-32767Specification Required32768-65535Reserved for Private UseInitial registrations for the “SWID/CoSWID Link Relationship Value” registry
are provided below. Assignments consist of an integer Index value, the Relationship Type Name, and a reference to the defining specification.IndexRelationship Type NameSpecification0Reserved1ancestorSee 2componentSee 3featureSee 4installationmediaSee 5packageinstallerSee 6parentSee 7patchesSee 8requiresSee 9see-alsoSee 10supersedesSee 11supplementalSee 12-16384Unassigned16385-32767Unassigned32768-65535Reserved for Private UseThis document uses unsigned 8-bit index values to represent link-entry use item values. The
initial set of Link use values are derived from the textual names
defined in the ISO/IEC 19770-2:2015 specification .This document defines a new a new registry titled
“SWID/CoSWID Link Use Values”. Future registrations for this
registry are to be made based on as follows:[TO BE REMOVED: This registration should take place at the following
location: https://www.iana.org/assignments/swid]RangeRegistration Procedures0-31Standards Action32-127Specification Required128-255Reserved for Private UseInitial registrations for the “SWID/CoSWID Entity Role Value” registry
are provided below. Assignments consist of an integer Index value, the Link Use Type Name, and a reference to the defining specification.IndexLink Use Type NameSpecification0Reserved1optionalSee 2requiredSee 3recommendedSee 4-127Unassigned128-255Reserved for Private UseIANA is requested add the following to the IANA “Media Types” registry.Type name: applicationSubtype name: swid+cborRequired parameters: noneOptional parameters: noneEncoding considerations: Must be encoded as using . See
RFC-AAAA for details.Security considerations: See of RFC-AAAA.Interoperability considerations: Applications MAY ignore any key
value pairs that they do not understand. This allows
backwards compatible extensions to this specification.Published specification: RFC-AAAAApplications that use this media type: The type is used by Software
asset management systems, Vulnerability assessment systems, and in
applications that use remote integrity verification.Fragment identifier considerations: Fragment identification for
application/swid+cbor is supported by using fragment identifiers as
specified by RFC-AAAA. [Section to be defined]Additional information:Magic number(s): first five bytes in hex: da 53 57 49 44File extension(s): coswidMacintosh file type code(s): noneMacintosh Universal Type Identifier code: org.ietf.coswid
conforms to public.dataPerson & email address to contact for further information:
Henk Birkholz <henk.birkholz@sit.fraunhofer.de>Intended usage: COMMONRestrictions on usage: NoneAuthor: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>Change controller: IESGIANA is requested to assign a CoAP Content-Format ID for the CoSWID
media type in the “CoAP Content-Formats” sub-registry, from the “IETF
Review or IESG Approval” space (256..999), within the “CoRE
Parameters” registry :Media typeEncodingIDReferenceapplication/swid+cbor-TBD1RFC-AAAAIANA is requested to allocate a tag in the “CBOR Tags” registry”,
preferably with the specific value requested:TagData ItemSemantics1398229316mapConcise Software Identifier (CoSWID) [RFC-AAAA]SWID and CoSWID tags contain public information about software components and, as
such, do not need to be protected against disclosure on an endpoint.
Similarly, SWID tags are intended to be easily discoverable by
applications and users on an endpoint in order to make it easy to
identify and collect all of an endpoint’s SWID tags. As such, any
security considerations regarding SWID tags focus on the application
of SWID tags to address security challenges, and the possible
disclosure of the results of those applications.A signed SWID tag whose signature has been validated can be relied upon to be
unchanged since it was signed. If the SWID tag was created by the
software provider, is signed, and the software provider can be authenticated as the originator of the signature, then the tag can be considered authoritative.
In this way, an authoritative SWID tag contains information about a software product provided by the maintainer of the product, who is expected to be an expert in their own product. Thus, authoritative SWID tags can be trusted to represent authoritative information about the software product. Having an authoritative SWID tag can be useful when the information in the
tag needs to be trusted, such as when the tag is being used to convey
reference integrity measurements for software components. By contrast, the data contained in unsigned
tags cannot be trusted to be unmodified.SWID tags are designed to be easily added and removed from an
endpoint along with the installation or removal of software components.
On endpoints where addition or removal of software components is
tightly controlled, the addition or removal of SWID tags can be
similarly controlled. On more open systems, where many users can
manage the software inventory, SWID tags can be easier to add or
remove. On such systems, it can be possible to add or remove SWID
tags in a way that does not reflect the actual presence or absence of
corresponding software components. Similarly, not all software
products automatically install SWID tags, so products can be present
on an endpoint without providing a corresponding SWID tag. As such,
any collection of SWID tags cannot automatically be assumed to
represent either a complete or fully accurate representation of the
software inventory of the endpoint. However, especially on devices
that more strictly control the ability to add or remove applications,
SWID tags are an easy way to provide an preliminary understanding of
that endpoint’s software inventory.Any report of an endpoint’s SWID tag collection provides
information about the software inventory of that endpoint. If such a
report is exposed to an attacker, this can tell them which software
products and versions thereof are present on the endpoint. By
examining this list, the attacker might learn of the presence of
applications that are vulnerable to certain types of attacks. As
noted earlier, SWID tags are designed to be easily discoverable by an
endpoint, but this does not present a significant risk since an
attacker would already need to have access to the endpoint to view
that information. However, when the endpoint transmits its software
inventory to another party, or that inventory is stored on a server
for later analysis, this can potentially expose this information to
attackers who do not yet have access to the endpoint. For this reason, it is
important to protect the confidentiality of SWID tag information that
has been collected from an endpoint, not because those tags
individually contain sensitive information, but because the
collection of SWID tags and their association with an endpoint
reveals information about that endpoint’s attack surface.Finally, both the ISO-19770-2:2015 XML schema definition and the
Concise SWID data definition allow for the construction of “infinite”
SWID tags or SWID tags that contain malicious content with the intent
if creating non-deterministic states during validation or processing of SWID tags. While software
product vendors are unlikely to do this, SWID tags can be created by any party and the SWID tags
collected from an endpoint could contain a mixture of vendor and non-vendor created tags. For this
reason, tools that consume SWID tags ought to treat the tag contents as potentially malicious and
employ input sanitizing on the tags they ingest.TBDChanges from version 03 to version 09:Reduced representation complexity of the media-entry type and removed the section describing the older data structure.Added more signature schemes from COSEIncluded a minimal required set of normative languageReordering of attribute name to integer label by priority according to semantics.Added an IANA registry for CoSWID items supporting future extension.Cleaned up IANA registrations, fixing some inconsistencies in the table labels.Added additional CDDL sockets for resource collection entries providing for additional extension points to address future SWID/CoSWID extensions.Updated section on extension points to address new CDDL sockets and to reference the new IANA registry for items.Removed unused references and added new references to address placeholder comments.Added table with semantics for the link ownership item.Clarified language, made term use more consistent, fixed references, and replacing lowercase RFC2119 keywords.Changes from version 02 to version 03:Updated core CDDL including the CDDL design pattern according to RFC 8428.Changes from version 01 to version 02:Enforced a more strict separation between the core CoSWID definition and additional usage by
moving content to corresponding appendices.Removed artifacts inherited from the reference schema provided by ISO (e.g. NMTOKEN(S))Simplified the core data definition by removing group and type choices where possibleMinor reordering of map membersAdded a first extension point to address requested flexibility for extensions beyond the
any-elementChanges from version 00 to version 01:Ambiguity between evidence and payload eliminated by introducing explicit members (while stillallowing for “empty” SWID tags)Added a relatively restrictive COSE envelope using cose_sign1 to define signed CoSWID (single signer only, at the moment)Added a definition how to encode hashes that can be stored in the any-member using existing IANA tables to reference hash-algorithmsChanges since adopted as a WG I-D -00:Removed redundant any-attributes originating from the ISO-19770-2:2015 XML schema definitionFixed broken multi-map membersIntroduced a more restrictive item (any-element-map) to represent custom maps, increased restriction on types for the any-attribute, accordinglyFixed X.1520 referenceMinor type changes of some attributes (e.g. NMTOKENS)Added semantic differentiation of various name types (e,g. fs-name)Changes from version 06 to version 07:Added type choices/enumerations based on textual definitions in 19770-2:2015Added value registry requestAdded media type registration requestAdded content format registration requestAdded CBOR tag registration requestRemoved RIM appedix to be addressed in complementary draftRemoved CWT appendixFlagged firmware resource colletion appendix for revisionMade use of terminology more consistentBetter defined use of extension points in the CDDLAdded definitions for indexed valuesAdded IANA registry for Link use indexed valuesChanges from version 05 to version 06:Improved quantitiesIncluded proposals for implicet enumerations that were NMTOKENSAdded extension pointsImproved exemplary firmware-resource extensionChanges from version 04 to version 05:Clarified language around SWID and CoSWID to make more consistent use of these terms.Added language describing CBOR optimizations for single vs. arrays in the model front matter.Fixed a number of grammatical, spelling, and wording issues.Documented extension points that use CDDL sockets.Converted IANA registration tables to markdown tables, reserving the 0 value for use when a value is not known.Updated a number of references to their current versions.Changes from version 03 to version 04:Re-index label values in the CDDL.Added a section describing the CoSWID model in detail.Created IANA registries for entity-role and version-schemeChanges from version 02 to version 03:Updated CDDL to allow for a choice between a payload or evidenceRe-index label values in the CDDL.Added item definitionsUpdated references for COSE, CBOR Web Token, and CDDL.Changes from version 01 to version 02:Added extensions for Firmware and CoSWID use as Reference Integrity Measurements (CoSWID RIM)Changes meta handling in CDDL from use of an explicit use of items to a more flexible unconstrained collection of items.Added sections discussing use of COSE Signatures and CBOR Web TokensChanges from version 00 to version 01:Added CWT usage for absolute SWID paths on a deviceFixed cardinality of type-choices including arraysIncluded first iteration of firmware resource-collectionKey words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Tags for Identifying LanguagesThis document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Concise Binary Object Representation (CBOR)The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.The Constrained Application Protocol (CoAP)The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments.Guidelines for Writing an IANA Considerations Section in RFCsMany protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.This is the third edition of this document; it obsoletes RFC 5226.CBOR Object Signing and Encryption (COSE)Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.Web LinkingThis specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types").It also defines the serialisation of such links in HTTP headers with the Link header field.Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data StructuresThis document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.Recommendation ITU-T X.1520 (2014), Common vulnerabilities and exposuresInformation technology - Software asset management - Part 5: Overview and vocabularyInformation technology - Software asset management - Part 2: Software identification tagGuidelines for the Creation of Interoperable Software Identification (SWID) TagsNational Institute for Standards and TechnologyThe MITRE CorporationG2, IncG2, IncSemantic Versioning 2.0.0XML Path Language (XPath) 2.0 (Second Edition)Media QueriesAmbiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.A Universally Unique IDentifier (UUID) URN NamespaceThis specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms.This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document. [STANDARDS-TRACK]Resource-Oriented Lightweight Information Exchange (ROLIE)This document defines a resource-oriented approach for security automation information publication, discovery, and sharing. Using this approach, producers may publish, share, and exchange representations of software descriptors, security incidents, attack indicators, software vulnerabilities, configuration checklists, and other security automation information as web-addressable resources. Furthermore, consumers and other stakeholders may access and search this security information as needed, establishing a rapid and on-demand information exchange network for restricted internal use or public access repositories. This specification extends the Atom Publishing Protocol and Atom Syndication Format to transport and share security automation resource representations.Manufacturer Usage Description SpecificationThis memo specifies a component-based architecture for Manufacturer Usage Descriptions (MUDs). The goal of MUD is to provide a means for end devices to signal to the network what sort of access and network functionality they require to properly function. The initial focus is on access control. Later work can delve into other aspects.This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate extension, and a means to sign and verify the descriptions.Time-Based Uni-Directional AttestationThis memo documents the method and bindings used to conduct time- based uni-directional attestation between distinguishable endpoints over the network.UpperCamelCaseKebabCaseSWID tags, as defined in the ISO-19770-2:2015 XML schema, can include cryptographic signatures to
protect the integrity of the SWID tag. In general, tags are signed by the tag creator (typically,
although not exclusively, the vendor of the software component that the SWID tag identifies).
Cryptographic signatures can make any modification of the tag detectable, which is especially
important if the integrity of the tag is important, such as when the tag is providing reference
integrity measurements for files.The ISO-19770-2:2015 XML schema uses XML DSIG to support cryptographic signatures. CoSWID tags
require a different signature scheme than this. COSE (CBOR Object Signing and Encryption) provides the required mechanism . Concise SWID can be wrapped in a COSE Single Signer Data Object
(COSE_Sign1) that contains a single signature. The following CDDL defines a more restrictive subset
of header attributes allowed by COSE tailored to suit the requirements of Concise SWID tags.Optionally, the COSE_Sign structure that allows for more than one signature to be applied to a CoSWID tag MAY be used. The corresponding usage scenarios are domain-specific and require well-defined application guidance. Representation of the corresponding guidance is out-of-scope of this document.Additionally, the COSE Header counter signature MAY be used as an attribute in the unprotected header map of the COSE envelope of a CoSWID. The application of counter signing enables second parties to provide a signature on a signature allowing for a proof that a signature existed at a given time (i.e., a timestamp).