Arm Limited

brendan.moran.ietf@gmail.com

Security SUIT Internet-Draft This document specifies algorithm profiles for SUIT manifest parsers and authors to ensure better interoperability. These profiles apply specifically to a constrained node software update use case.

Mandatory algorithms may change over time due to an evolving threat landscape. Algorithms are grouped into algorithm profiles to account for this. Profiles may be deprecated over time. SUIT will define four choices of MTI profile specifically for constrained node software update. These profiles are: One Symmetric MTI profile Two “Current” Asymmetric MTI profiles One “Future” Asymmetric MTI profile At least one MTI algorithm in each category MUST be FIPS qualified. Because SUIT presents an asymmetric communication profile, with powerful/complex manifest authors and constrined manifest recipients, the requirements for Recipients and Authors are different. Recipients MAY choose which MTI profile they wish to implement. It is RECOMMENDED thaty they implement the “Future” Asymmetric MTI profile. Recipients MAY implement any number of other profiles. Authors MUST implement all MTI profiles. Authors MAY implement any number of other profiles. Other use-cases of SUIT MAY define their own MTI algorithms.

The algorithms that form a part of the profiles defined in this document are grouped into: Digest Algorithms Authentication Algorithms Key Exchange Algorithms Encryption Algorithms

SHA-256 (-16)

Authentication Algorithms are divided into three categories:

HMAC-256 (5)

ES256 (-7) EdDSA (-8)

HSS-LMS (-46)

Key Exchange Algorithms are divided into two three groups: Symmetric, Classical Asymmetric, and Post-Quantum Asymmetric

A128 (-3)

COSE HPKE (TBD) ECDH-ES + HKDF-256 (-25)

A128GCM (1)

Recognized profiles are defined below.

This profile requires the following algorithms: SHA-256 HMAC-256 A128W Key Wrap AES-CCM-16-128-128

This profile requires the following algorithms: SHA-256 ES256 HPKE AES-128-GCM

This profile requires the following algorithms: SHA-256 EDDSA HPKE AES-128-GCM

This profile requires the following algorithms: SHA-256 HSS-LMS HPKE AES-128-GCM

Optional classical and PQC profiles are defined below. suit-sha256-eddsa-ecdh-es-chacha-poly SHA-256 EdDSA ECDH-ES + HKDF-256 ChaCha20 + Poly1305 suit-sha256-falcon512-hpke-a128gcm SHA-256 HSS-LMS HPKE AES-128-GCM suit-shake256-dilithium-kyber-a128gcm SHAKE256 Crystals-Dilithium Crystal-Kyber AES-128GCM

TODO

TODO

Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined 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 specifies the conventions for using the Hierarchical Signature System (HSS) / Leighton-Micali Signature (LMS) hash-based signature algorithm with the CBOR Object Signing and Encryption (COSE) syntax. The HSS/LMS algorithm is one form of hash-based digital signature; it is described in RFC 8554. Arm Limited Arm Limited Fraunhofer SIT Inria Nordic Semiconductor This specification describes the format of a manifest. A manifest is a bundle of metadata about code/data obtained by a recipient (chiefly the firmware for an IoT device), where to find the that code/data, the devices to which it applies, and cryptographic information protecting the manifest. Software updates and Trusted Invocation both tend to use sequences of common operations, so the manifest encodes those sequences of operations, rather than declaring the metadata.