A CWT Claims Set Definition for RATS Endorsement Tokens
draft-birkholz-rats-endorsement-eat-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RATS Working Group                                           H. Birkholz
Internet-Draft                                                  M. Eckel
Intended status: Standards Track                          Fraunhofer SIT
Expires: September 11, 2020                               March 10, 2020

        A CWT Claims Set Definition for RATS Endorsement Tokens
                 draft-birkholz-rats-endorsement-eat-00

Abstract

   An Endorsement is defined by the RATS Architecture as a "secure
   statement that some entity (typically a manufacturer) vouches for the
   integrity of an Attester's signing capability".  This documents
   defines Claims to be used in CBOR Web Tokens in the same fashion
   attestation Evidence can be represented via Entity Attestation Tokens
   (EAT).  The defined Claims can be included in Endorsement Tokens.
   Endorsement Tokens can be provided by a manufacturer or a third party
   authority to vouch for the capabilities and characteristics of a
   hardware component a RATS Attester is not capable to create Evidence
   about.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 11, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Birkholz & Eckel       Expires September 11, 2020               [Page 1]
Internet-Draft               Endorsement EAT                  March 2020

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Endorsement Claims Definition . . . . . . . . . . . . . . . .   3
     2.1.  Component Manufacturer Claim  . . . . . . . . . . . . . .   3
     2.2.  Component Version Claim . . . . . . . . . . . . . . . . .   3
     2.3.  Component Model Claim . . . . . . . . . . . . . . . . . .   4
     2.4.  Field Upgradable Claim  . . . . . . . . . . . . . . . . .   4
     2.5.  Shielded Secret Origination Claim . . . . . . . . . . . .   4
     2.6.  Common Criteria Claim . . . . . . . . . . . . . . . . . .   4
   3.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Remote ATtestation procedureS (RATS) can be used to establish trust
   in the trustworthiness of a remote peer (the Attester).  As a Relying
   Party typically cannot evaluate every kind of Attester by itself, the
   RATS architecture [I-D.ietf-rats-architecture] defines the Verifier
   role, to off-load the burden of appraisal to another entity than the
   Relying Party itself.  The duty of a Verifier is to produce
   Attestation Results that are then easier to digest by a Relying Party
   in comparison to Evidence that can potentially be both large and/or
   esoteric for a generic Relying Party.  Evidence are believable Claims
   about the Attester.  Next to Evidence, a Verifier requires
   Endorsements.  Endorsements are signed documents that include Claims
   about components of an Attester that an Attester cannot create
   Evidence about.  Very prominent examples are Roots of Trust, such as
   a Static Code Root of Trust for Measurement as defined in the Trusted
   Computing Group (TCG) Glossary [TCGGLOSS].  These Endorsements of
   components of a composite device are typically provided by their
   manufacturer, a corresponding supply chain entity that assembles a
Show full document text