]> University of Applied Sciences Bonn-Rhein-Sieg

Germany hannes.tschofenig@gmx.net

Transmute

United States orie@transmute.industries

bibital

Japan dajiaji@gmail.com

Security Theory LLC

United States lgl@securitytheory.com

Security COSE Internet-Draft This specification defines hybrid public-key encryption (HPKE) for use with CBOR Object Signing and Encryption (COSE). HPKE offers a variant of public-key encryption of arbitrary-sized plaintexts for a recipient public key. HPKE works for any combination of an asymmetric key encapsulation mechanism (KEM), key derivation function (KDF), and authenticated encryption with additional data (AEAD) function. Authentication for HPKE in COSE is provided by COSE-native security mechanisms or by one of the authenticated variants of HPKE. This document defines the use of the HPKE with COSE.

Introduction Hybrid public-key encryption (HPKE) is a scheme that provides public key encryption of arbitrary-sized plaintexts given a recipient's public key. This document defines the use of the HPKE with COSE (, ).

Conventions and Terminology 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. This specification uses the following abbreviations and terms:

• Content-encryption key (CEK), a term defined in CMS .
• Hybrid Public Key Encryption (HPKE) is defined in .
• pkR is the public key of the recipient, as defined in .
• skR is the private key of the recipient, as defined in .
• Key Encapsulation Mechanism (KEM), see .
• Key Derivation Function (KDF), see .
• Authenticated Encryption with Associated Data (AEAD), see .
• Additional Authenticated Data (AAD), see .

HPKE for COSE

Overview This specification supports two modes of HPKE in COSE, namely

• HPKE Direct Encryption mode, where HPKE is used to encrypt the plaintext. This mode can only be used with a single recipient. provides the details.
• HPKE Key Encryption mode, where HPKE is used to encrypt a content encryption key (CEK) and the CEK is subsequently used to encrypt the plaintext. This mode supports multiple recipients. provides the details.

In both cases a new COSE header parameter, called 'ek', is used to convey the content of the enc structure defined in the HPKE specification. "Enc" represents the serialized public key. For use with HPKE the 'ek' header parameter MUST be present in the unprotected header parameter and MUST contain the encapsulated key, which is output of the HPKE KEM, and it is a bstr.

HPKE Direct Encryption Mode This mode applies if the COSE_Encrypt0 structure uses a COSE-HPKE algorithm and has no recipients. Because COSE-HPKE supports header protection, if the 'alg' parameter is present, it MUST be included in the protected header and MUST be a COSE-HPKE algorithm. Although the use of the 'kid' parameter in COSE_Encrypt0 is discouraged by RFC 9052, this documents RECOMMENDS the use of the 'kid' parameter (or other parameters) to explicitly identify the static recipient public key used by the sender. If the COSE_Encrypt0 contains the 'kid' then the recipient may use it to select the appropriate private key. When encrypting, the inputs to the HPKE Seal operation are set as follows:

• kem_id: Depends on the COSE-HPKE algorithm used.
• pkR: The recipient public key, converted into an HPKE public key.
• kdf_id: Depends on the COSE-HPKE algorithm used.
• aead_id: Depends on the COSE-HPKE algorithm used.
• info: empty string.
• aad: Canonical encoding of the Enc_structure from ).
• pt: The raw message plaintext.

The outputs are used as follows:

• enc: MUST be placed raw into the 'ek' (encapsulated key) parameter in the unprotected bucket.
• ct: MUST be used as layer ciphertext. If not using detached content, this is directly placed as ciphertext in COSE_Encrypt0 structure. Otherwise, it is transported separately and the ciphertext field is nil. See Section 5 of for a description of detached payloads.

When decrypting, the inputs to the HPKE Open operation are set as follows:

• kem_id: Depends on the COSE-HPKE algorithm used.
• skR: The recipient private key, converted into an HPKE private key.
• kdf_id: Depends on the COSE-HPKE algorithm used.
• aead_id: Depends on the COSE-HPKE algorithm used.
• info: empty string.
• aad: Canonical encoding of the Enc_structure from ).
• enc: The contents of the layer 'ek' parameter.
• ct: The contents of the layer ciphertext.

The plaintext output is the raw message plaintext. The COSE_Encrypt0 MAY be tagged or untagged. An example is shown in .

HPKE Key Encryption Mode This mode is selected if the COSE_recipient structure uses a COSE-HPKE algorithm. In this approach the following layers are involved:

• Layer 0 (corresponding to the COSE_Encrypt structure) contains the content (plaintext) encrypted with the CEK. This ciphertext may be detached, and if not detached, then it is included in the COSE_Encrypt structure.
• Layer 1 (corresponding to a recipient structure) contains parameters needed for HPKE to generate a shared secret used to encrypt the CEK. This layer conveys the encrypted CEK in the COSE_recipient structure using a COSE-HPKE algorithm. The unprotected header MAY contain the kid parameter to identify the static recipient public key the sender has been using with HPKE.

This two-layer structure is used to encrypt content that can also be shared with multiple parties at the expense of a single additional encryption operation. As stated above, the specification uses a CEK to encrypt the content at layer 0.

Recipient Encryption This section describes the Recipient_structure. It serves instead of COSE_KDF_Context for COSE-HPKE recipients (and possibly other COSE algorithms defined outside this document). It MUST be used for COSE-HPKE recipients as it provides the protection for recipient protected headers. It is patterned after the Enc_structure in , but is specifically for a COSE_recipient, never a COSE_Encrypt. The COSE_KDF_Context MUST NOT be used in COSE-HPKE.

• "next_layer_alg" is the algorithm ID of the COSE layer for which the COSE_recipient is encrypting a key. It is the algorithm that the key MUST be used with. This value MUST match the alg parameter in the next lower COSE layer. (This serves the same purpose as the alg ID in the COSE_KDF_Context. It also mitigates attacks where a person-in-the-middle changes the following layer algorithm from an AEAD algorithm to one that is not foiling the protection of the following layer headers).
• "recipient_protected_header" contains the protected headers from the COSE_recipient CBOR-encoded deterministically with the "Core Deterministic Encoding Requirements", specified in Section 4.2.1 of RFC 8949 .
• "recipient_aad" contains any additional context the application wishes to protect. If none, it is a zero-length string. This is distinct from the external_aad for the whole COSE encrypt. It is per-recipient. Since it is not a header, it may be secret data that is not transmitted. It provides a means to convey many of the fields in COSE_KDF_Context.

COSE-HPKE Recipient Construction Because COSE-HPKE supports header protection, if the 'alg' parameter is present, it MUST be in the protected header and MUST be a COSE-HPKE algorithm. The unprotected header MAY contain the kid parameter to identify the static recipient public key the sender used. Use of the 'kid' parameter is RECOMMENDED to explicitly identify the static recipient public key used by the sender. When encrypting, the inputs to the HPKE Seal operation are set as follows:

• kem_id: Depends on the COSE-HPKE algorithm used.
• pkR: The recipient public key, converted into HPKE public key.
• kdf_id: Depends on the COSE-HPKE algorithm used.
• aead_id: Depends on the COSE-HPKE algorithm used.
• info: empty string.
• aad: Canonical encoding of the Recipient_structure.
• pt: The raw key for the next layer down.

The outputs are used as follows:

• enc: MUST be placed raw into the 'ek' (encapsulated key) parameter in the unprotected bucket.
• ct: MUST be placed raw in the ciphertext field in the COSE_recipient.

When decrypting, the inputs to the HPKE Open operation are set as follows:

• kem_id: Depends on the COSE-HPKE algorithm used.
• skR: The recipient private key, converted into HPKE private key.
• kdf_id: Depends on the COSE-HPKE algorithm used.
• aead_id: Depends on the COSE-HPKE algorithm used.
• info: empty string.
• aad: Canonical encoding of the Recipient_structure.
• enc: The contents of the layer 'ek' parameter.
• ct: The contents of the layer ciphertext field.

The plaintext output is the raw key for the next layer down. It is not necessary to fill in recipient_aad as HPKE itself covers the attacks that recipient_aad (and COSE_KDF_Context (and SP800-56A)) are used to mitigate. COSE-HPKE use cases may use it for any purpose they wish, but it should generally be for small identifiers, context or secrets, not to protect bulk external data. Bulk external data should be protected at layer 0 with external_aad. The COSE_recipient structure is repeated for each recipient. When encrypting the content at layer 0 then the instructions in Section 5.3 of MUST to be followed, which includes the calculation of the authenticated data strcture. An example is shown in .

Key Representation The COSE_Key with the existing key types can be used to represent KEM private or public keys. When using a COSE_Key for COSE-HPKE, the following checks are made:

• If the "kty" field is "AKP", then the public and private keys SHALL be raw HPKE public and private keys (respectively) for the KEM used by the algorithm.
• Otherwise, the key MUST be suitable for the KEM used by the algorithm. In case the "kty" parameter is "EC2" or "OKP", this means the value of "crv" parameter is suitable. For the algorithms defined in this document, the valid combinations of the KEM, "kty" and "crv" are shown in .
• If the "key_ops" field is present, it MUST include only "derive bits" for the private key and MUST be empty for the public key.

Examples of the COSE_Key for COSE-HPKE are shown in .

Ciphersuite Registration A ciphersuite is a group of algorithms, often sharing component algorithms such as hash functions, targeting a security level. A COSE-HPKE algorithm is composed of the following choices:

• HPKE Mode
• KEM Algorithm
• KDF Algorithm
• AEAD Algorithm

The "KEM", "KDF", and "AEAD" values are chosen from the HPKE IANA registry . For readability the algorithm ciphersuites labels are built according to the following scheme: ---- ]]> The "Mode" indicator may be populated with the following values from Table 1 of :

• "Base" refers to "mode_base" described in Section 5.1.1 of , which only enables encryption to the holder of a given KEM private key.
• "PSK" refers to "mode_psk", described in Section 5.1.2 of , which authenticates using a pre-shared key.
• "Auth" refers to "mode_auth", described in Section 5.1.3 of , which authenticates using an asymmetric key.
• "Auth_Psk" refers to "mode_auth_psk", described in Section 5.1.4 of , which authenticates using both a PSK and an asymmetric key.

For a list of ciphersuite registrations, please see . The following table summarizes the relationship between the ciphersuites registered in this document, which all use the "Base" mode and the values registered in the HPKE IANA registry . As the list indicates, the ciphersuite labels have been abbreviated at least to some extend to maintain the tradeoff between readability and length. The ciphersuite list above is a minimal starting point. Additional ciphersuites can be registered into the already existing registry. For example, once post-quantum cryptographic algorithms have been standardized it might be beneficial to register ciphersuites for use with COSE-HPKE. Additionally, ciphersuites utilizing the compact encoding of the public keys, as defined in , may be standardized for use in constrained environments. As a guideline for ciphersuite submissions to the IANA CoSE algorithm registry, the designated experts must only register combinations of (KEM, KDF, AEAD) triple that consitute valid combinations for use with HPKE, the KDF used should (if possible) match one internally used by the KEM, and components should not be mixed between global and national standards.

COSE_Keys for COSE-HPKE Ciphersuites The COSE-HPKE algorithm uniquely determines the KEM for which a COSE_Key is used. The following mapping table shows the valid combinations of the KEM used, COSE_Key type and its curve/key subtype.

COSE_Key Types and Curves for COSE-HPKE Ciphersuites

Examples This section provides a set of examples that shows all COSE message types (COSE_Encrypt0, COSE_Encrypt and COSE_MAC) to which the COSE-HPKE can be applied, and also provides some examples of key representation for HPKE KEM. Each example of the COSE message includes the following information that can be used to check the interoperability of COSE-HPKE implementations:

• plaintext: Original data of the encrypted payload.
• external_aad: Externally supplied AAD.
• skR: A recipient private key.
• skE: An ephemeral sender private key paired with the encapsulated key.

HPKE Direct Encryption Mode This example assumes that a sender wants to communicate an encrypted payload to a single recipient in the most efficient way. An example of the HPKE Direct Encryption Mode is shown in . Line breaks and comments have been inserted for better readability. This example uses the following:

• alg: HPKE-0
• plaintext: "This is the content."
• external_aad: "COSE-HPKE app"
• skR: h'57c92077664146e876760c9520d054aa93c3afb04e306705db6090308507b4d3'
• skE: h'42dd125eefc409c3b57366e721a40043fb5a58e346d51c133128a77237160218'

COSE_Encrypt0 Example for HPKE

HPKE Key Encryption Mode In this example we assume that a sender wants to transmit a payload to two recipients using the HPKE Key Encryption mode. Note that it is possible to send two single-layer payloads, although it will be less efficient.

COSE_Encrypt An example of the COSE_Encrypt structure using the HPKE scheme is shown in . Line breaks and comments have been inserted for better readability. This example uses the following: TODO: recompute this for Recipient_structure

• Encryption alg: AES-128-GCM
• plaintext: "This is the content."
• detatched ciphertext: h'cc168c4e148c52a83010a75250935a47ccb8682deebcef8fce5d60c161e849f53a2dc664'
• kid:"01"
  • alg: HPKE-0
  • external_aad: "COSE-HPKE app"
  • skR: h'57c92077664146e876760c9520d054aa93c3afb04e306705db6090308507b4d3'
  • skE: h'97ad883f949f4cdcb1301b9446950efd4eb519e16c4a3d78304eec832692f9f6'
• kid:"02"
  • alg: HPKE-4
  • external_aad: "COSE-HPKE app"
  • skR: h'bec275a17e4d362d0819dc0695d89a73be6bf94b66ab726ae0b1afe3c43f41ce'
  • skE: h'b8ed3f4df56c230e36fa6620a47f24d08856d242ea547c5521ff7bd69af8fd6f'

COSE_Encrypt Example for HPKE

To offer authentication of the sender the payload in is signed with a COSE_Sign1 wrapper, which is outlined in . The payload in is meant to contain the content of .

COSE_Encrypt Example for HPKE

COSE_MAC An example of the COSE_MAC structure using the HPKE scheme is shown in . This example uses the following:

• MAC alg: HMAC 256/256
• payload: "This is the content."
• kid:"01"
  • alg: HPKE-0
  • external_aad: "COSE-HPKE app"
  • skR: h'57c92077664146e876760c9520d054aa93c3afb04e306705db6090308507b4d3'
  • skE: h'e5dd9472b5807636c95be0ba2575020ba91cbb3561b52be141da89678c664307'
• kid:"02"
  • alg: HPKE-4
  • external_aad: "COSE-HPKE app"
  • skR: h'bec275a17e4d362d0819dc0695d89a73be6bf94b66ab726ae0b1afe3c43f41ce'
  • skE: h'78a49d7af71b5244498e943f361aa0250184afc48b8098a68ae97ccd2cd7e56f'

COSE_MAC Example for HPKE

Key Representation Examples of private and public KEM key representation are shown below.

KEM Public Key for HPKE-0

Key Representation Example for HPKE-0

KEM Private Key for HPKE-0

Key Representation Example for HPKE-0

KEM Public Key for HPKE-4

Key Representation Example for HPKE-4

Security Considerations This specification is based on HPKE and the security considerations of are therefore applicable also to this specification. HPKE assumes the sender is in possession of the public key of the recipient and HPKE COSE makes the same assumptions. Hence, some form of public key distribution mechanism is assumed to exist but outside the scope of this document. HPKE relies on a source of randomness to be available on the device. Additionally, with the two layer structure the CEK is randomly generated and it MUST be ensured that the guidelines in for random number generations are followed. HPKE in Base mode does not offer authentication as part of the HPKE KEM. In this case COSE constructs like COSE_Sign, COSE_Sign1, COSE_MAC, or COSE_MAC0 can be used to add authentication. HPKE also offers modes that offer authentication. If COSE_Encrypt or COSE_Encrypt0 is used with a detached ciphertext then the subsequently applied integrity protection via COSE_Sign, COSE_Sign1, COSE_MAC, or COSE_MAC0 does not cover this detached ciphertext. Implementers MUST ensure that the detached ciphertext also experiences integrity protection. This is, for example, the case when an AEAD cipher is used to produce the detached ciphertext but may not be guaranteed by non-AEAD ciphers.

IANA Considerations This document requests IANA to add new values to the 'COSE Algorithms' and to the 'COSE Header Parameters' registries.

COSE Algorithms Registry

• Name: HPKE-0
• Value: TBD1 (Assumed: 35)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(P-256, HKDF-SHA256) KEM, the HKDF-SHA256 KDF and the AES-128-GCM AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-1
• Value: TBD3 (Assumed: 37)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(P-384, HKDF-SHA384) KEM, the HKDF-SHA384 KDF, and the AES-256-GCM AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-2
• Value: TBD5 (Assumed: 39)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(P-521, HKDF-SHA512) KEM, the HKDF-SHA512 KDF, and the AES-256-GCM AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-3
• Value: TBD7 (Assumed: 41)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(X25519, HKDF-SHA256) KEM, the HKDF-SHA256 KDF, and the AES-128-GCM AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-4
• Value: TBD8 (Assumed: 42)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(X25519, HKDF-SHA256) KEM, the HKDF-SHA256 KDF, and the ChaCha20Poly1305 AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-5
• Value: TBD9 (Assumed: 43)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(X448, HKDF-SHA512) KEM, the HKDF-SHA512 KDF, and the AES-256-GCM AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes
• Name: HPKE-6
• Value: TBD10 (Assumed: 44)
• Description: Cipher suite for COSE-HPKE in Base Mode that uses the DHKEM(X448, HKDF-SHA512) KEM, the HKDF-SHA512 KDF, and the ChaCha20Poly1305 AEAD.
• Capabilities: [kty]
• Change Controller: IESG
• Reference: [[TBD: This RFC]]
• Recommended: Yes

COSE Header Parameters

• Name: ek
• Label: TBDX (Assumed: -4)
• Value type: bstr
• Value Registry: N/A
• Description: HPKE encapsulated key
• Reference: [[This specification]]

References Normative References In 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. RFC 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. This document describes a scheme for hybrid public key encryption (HPKE). This scheme provides a variant of public key encryption of arbitrary-sized plaintexts for a recipient public key. It also includes three authenticated variants, including one that authenticates possession of a pre-shared key and two optional ones that authenticate possession of a key encapsulation mechanism (KEM) private key. HPKE works for any combination of an asymmetric KEM, key derivation function (KDF), and authenticated encryption with additional data (AEAD) encryption function. Some authenticated variants may not be supported by all KEMs. We provide instantiations of the scheme using widely used and efficient primitives, such as Elliptic Curve Diffie-Hellman (ECDH) key agreement, HMAC-based key derivation function (HKDF), and SHA2. This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services 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. This document, along with RFC 9053, obsoletes RFC 8152. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines a set of algorithms that can be used with the CBOR Object Signing and Encryption (COSE) protocol (RFC 9052). This document, along with RFC 9052, obsoletes RFC 8152. 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. This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format. Informative References Randomness is a crucial ingredient for Transport Layer Security (TLS) and related security protocols. Weak or predictable "cryptographically secure" pseudorandom number generators (CSPRNGs) can be abused or exploited for malicious purposes. An initial entropy source that seeds a CSPRNG might be weak or broken as well, which can also lead to critical and systemic security problems. This document describes a way for security protocol implementations to augment their CSPRNGs using long-term private keys. This improves randomness from broken or otherwise subverted CSPRNGs. This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF. This document describes the Cryptographic Message Syntax. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK] Hewlett-Packard Enterprise This document describes enhancements to the Hybrid Public Key Encryption standard published by CFRG. These include use of "compact representation" of relevant public keys, support for key-wrapping, and two ways to address the use of HPKE on lossy networks: a determinstic, nonce-less AEAD scheme, and use of a rolling sequence number with existing AEAD schemes. IANA

Contributors We would like thank the following individuals for their contributions to the design of embedding the HPKE output into the COSE structure following a long and lively mailing list discussion:

• Richard Barnes
• Ilari Liusvaara

Finally, we would like to thank Russ Housley and Brendan Moran for their contributions to the draft as co-authors of initial versions.

Acknowledgements We would like to thank John Mattsson, Mike Prorock, Michael Richardson, and Goeran Selander for their review feedback.