Arm's Platform Security Architecture (PSA) Attestation Token
draft-tschofenig-rats-psa-token-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Hannes Tschofenig , Simon Frost , Mathias Brossard , Adrian L. Shaw , Thomas Fossati | ||
| Last updated | 2020-09-07 (Latest revision 2020-03-06) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Platform Security Architecture (PSA) is a family of hardware and firmware security specifications, as well as open-source reference implementations, to help device makers and chip manufacturers build best-practice security into products. Devices that are PSA compliant are able to produce attestation tokens as described in this memo, which are the basis for a number of different protocols, including secure provisioning and network access control. This document specifies the PSA attestation token structure and semantics. At its core, the CWT (COSE Web Token) format is used and populated with a set of claims in a way similar to EAT (Entity Attestation Token). This specification describes what claims are used by PSA compliant systems.
Authors
Hannes Tschofenig
Simon Frost
Mathias Brossard
Adrian L. Shaw
Thomas Fossati
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)