Key wrap

In the late 1990s, the National Institute of Standards and Technology (NIST) posed the "Key Wrap" problem: to develop secure and efficient cipher-based key encryption algorithms. The resulting algorithms would be formally evaluated by NIST, and eventually approved for use in NIST-certified cryptographic modules. NIST did not precisely define the security goals of the resulting algorithm, and left further refinement to the algorithm developers. Based on the resulting algorithms, the design requirements appear to be (1) confidentiality, (2) integrity protection (authentication), (3) efficiency, (4) use of standard (approved) underlying primitives such as the Advanced Encryption Standard (AES) and the Secure Hash Algorithm (SHA-1), and (5) consideration of additional circumstances (e.g., resilience to operator error, low-quality random number generators). Goals (3) and (5) are particularly important, given that many widely deployed authenticated encryption algorithms (e.g., AES-CCM) are already sufficient to accomplish the remaining goals.

NIST AES Key Wrap Specification

Several constructions have been proposed. These include:

• AES Key Wrap Specification (November 2001, RFC 3394)
  • Implemented by the WebCrypto subtle API.[2]
• American Standards Committee ANSX9.102, which defines four algorithms:
  • AESKW (a variant of the AES Key Wrap Specification)
  • TDKW (similar to AESKW, built from Triple DES rather than AES).
  • AKW1 (TDES, two rounds of CBC)
  • AKW2 (TDES, CBC then CBC-MAC)

Each of the proposed algorithms can be considered as a form of authenticated encryption algorithm providing confidentiality for highly entropic messages such as cryptographic keys. The AES Key Wrap Specification, AESKW, TDKW, and AKW1 are intended to maintain confidentiality under adaptive chosen ciphertext attacks, while the AKW2 algorithm is designed to be secure only under known-plaintext (or weaker) attacks. (The stated goal of AKW2 is for use in legacy systems and computationally limited devices where use of the other algorithms would be impractical.) AESKW, TDKW and AKW2 also provide the ability to authenticate cleartext "header", an associated block of data that is not encrypted.

Rogaway and Shrimpton evaluated the design of the ANSX9.102 algorithms with respect to the stated security goals. Among their general findings, they noted the lack of clearly stated design goals for the algorithms, and the absence of security proofs for all constructions.

In their paper, Rogaway and Shrimpton proposed a provable key-wrapping algorithm (SIV—the Synthetic Initialization Vector mode) that authenticates and encrypts an arbitrary string and authenticates, but does not encrypt, associated data which can be bound into the wrapped key. This has been standardized as a new AES mode in RFC 5297.

• Authenticated encryption
• Deterministic encryption
• Key management
• Offline private key protocol

• P. Rogaway, T. Shrimpton. A Provable-Security Treatment of the Key-Wrap Problem.
• NIST, AES Key Wrap Specification (November 2001)
• NIST Special Publication 800-38F, Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping (December 2012)
• American Standards Committee, Request for Review of Key Wrap Algorithms
• Dan Harkins (October 2008). "RFC 5297: Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES)". IETF.
• Krohn, Max; Coyne, Chris. "TripleSec". Keybase. Archived from the original on 3 June 2015. Retrieved 2 Jan 2021.