A new Request for Comments is now available in online RFC libraries.
RFC 9783
Title: Arm's Platform Security Architecture (PSA)
Attestation Token
Author: H. Tschofenig,
S. Frost,
M. Brossard,
A. Shaw,
T. Fossati
Status: Informational
Stream: Independent
Date: June 2025
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 36
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-tschofenig-rats-psa-token-24.txt
URL: https://www.rfc-editor.org/info/rfc9783
DOI: 10.17487/RFC9783
Arm's Platform Security Architecture (PSA) is a family of hardware
and firmware security specifications, along with open-source
reference implementations, aimed at helping device makers and chip
manufacturers integrate best-practice security into their products.
Devices that comply with PSA can generate attestation tokens as
described in this document, which serve as the foundation for various
protocols, including secure provisioning and network access control.
This document specifies the structure and semantics of the PSA
attestation token.
The PSA attestation token is a profile of the Entity Attestation
Token (EAT). This specification describes the claims used in an
attestation token generated by PSA-compliant systems, how these
claims are serialized for transmission, and how they are
cryptographically protected.
This Informational document is published as an Independent Submission
to improve interoperability with Arm's architecture. It is not a
standard nor a product of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
