Skip to content

Firmware Validation for a PC Component

For a PC component, a RIM may use XML (SWID) or Concise Binary Object Representation (CBOR) encoding, depending on the format. The RIM-Tool supports the CoSWID Tag, the TCG Component RIM, and the CoRIM.

CoSWID

CoSWID is defined by RFC 9393 . It is based on the SWID specification (ISO/IEC 19770-2:2015). NIST IR 8060 provides public guidance for creating interoperable SWID tags. CoSWID includes metadata such as edition, colloquial-version, and product. Key aspects of its structure are:

  1. Encoding: CoSWID drops the XML encoding specified in SWID in favor of CBOR - RFC 8949 .

  2. Structure: The CoSWID spec uses Concise Data Definition Language (CDDL) - RFC 8610 . CDDL uses both arrays and maps (which hold key value/pairs) to define data structures. Most CoSWID items are optional.

  3. Signature: CoSWID objects can be signed using the COSE signature envelope. RFC 9393 defines a COSE content type of “application/swid+cbor” to provide a hint to the parser that the payload is a CoSWID object.

TCG Component RIM Binding for SWID/CoSWID

The TCG Component RIM Binding for SWID/CoSWID defines two formats and encodings for component RIMs: SWID (XML) and CoSWID (CBOR). It provides extensions that support attestation of the DMTF’s Security Protocols and Data Model Specification . The attributes defined in this specification closely mimic those defined by the PC Client RIM specification. This specification is intended to support devices adhering to the TCG DICE specifications , which support devices that do not contain a TPM. DICE has definitions for CoRIM as well, so DICE may use either TCG Component RIM or CoRIM format.

CoRIM

Concise RIM (CoRIM) is defined by IETF. IETF sponsors the Remote ATtestation ProcedureS (RATS) working Group which promotes specifications that support attestation.

As shown in the corim.txt diagram, the CoRIM can contain a CoSWID, CoMID, or a Concise Tag List (CoTL). For the RIM-Tool’s create command, the use of the --rim-type parameter is used to denote which option it uses. Note that currently CoSWID and CoTL options with CoRIM creation are unsupported.

CoRIMs are digitally signed using COSE with extra requirements placed upon the protected header. Of interest is the content type defined as “application/rim+cbor” for CoRIM as opposed to “application/swid+cbor” when signing a CoSWID object. This helps the parser determine the type of data found in the payload.

Component RIM Specifications