# US 2010/0169645 A1 · Key transport in authentication or cryptography

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0169645 A1
- Document ID: US20100169645A1
- Status: Published application
- Kind: A1
- Application number: 12/604,221
- Filed: 2009-10-22
- Published: 2010-07-01
- Earliest claimed: 2008-12-30
- Assignees: Cisco Technology, Inc.
- Inventors: David A. McGrew; Brian E. Weis; Fabio R. Maino
- Web page: https://patentgrep.com/patent/US20100169645A1

## CPC

- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/0822: {using key encryption key}
- H04L 9/0833: {involving conference or group key (network architectures or network communication protocols for key management in group communication in a packet data network H04L63/065)}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A computer system for authenticating, encrypting, and transmitting a secret communication, where the encryption key is transmitted along with the encrypted message, is disclosed. In an embodiment, a first transmitting processor encrypts a plaintext message to a ciphertext message using a data key, encrypts the data key using a key encrypting key, and sends a communication comprising the encrypted data key and the ciphertext message. A second receiving processor receives the communication and then decrypts the encrypted data key using the key encrypting key and decrypts the ciphertext message using the data key to recover the plaintext message.

## Claims

### Claim 1

A computer-implemented method comprising:
selecting a plaintext message to be authenticated and encrypted;
selecting an associated data to be authenticated and transmitted, but not encrypted;
creating and storing a data key to encrypt the plaintext message in a uniformly random or pseudorandom manner;
creating and storing a ciphertext message, wherein the ciphertext message is at least as long as the plaintext message and is derived from at least the plaintext message, and the data key;
creating and storing an encrypted data key, wherein the encrypted data key is derived from at least the data key, and a key encrypting key;
generating a communication comprising at least the encrypted data key and the ciphertext message;
wherein each of the above steps is performed by one or more processors.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
parsing the communication into at least the encrypted data key and the ciphertext message;
regenerating the data key, wherein the data key is a function of at least the encrypted data key, and the key encrypting key;
performing an authentication test on the encrypted data key, and the key encrypting key;
determining that the data key is authentic only when all of the encrypted data key, and the key encrypting key are authentic according to the authentication test;
generating and communicating a failure indication when at least one of the encrypted data key and the key encrypting key is not authentic according to the authentication test;
regenerating the plaintext message, wherein the plaintext message is a function of at least the ciphertext message, and the data key, wherein the plaintext message comprises a failure indication if at least one of the ciphertext message and the data key is not authentic according to the authentication test;
wherein each of the above steps is performed by one or more processors.

### Claim 3 (depends on 1)

The method of claim 1, wherein the communication comprises a data packet comprising an internet protocol header, an encapsulating security payload header, an initialization vector, a decryption context, an encrypted region, and an integrity check value.

### Claim 4 (depends on 3)

The method of claim 3, wherein the decryption context comprises the encrypted data key and instructions regarding how a decryptor can decrypt and process the encrypted data key.

### Claim 5 (depends on 4)

The method of claim 4, wherein the instructions comprise key management information received from a Logical Key Hierarchy (LKH) group key management protocol or a Subset-Difference key management method.

### Claim 6 (depends on 1)

The method of claim 1, wherein the encrypted data key is derived using any of AES-CCM (Advanced Encryption Standard, Counter with Cipher Block Chaining Message Authentication Code), AES-CBC and AES-GCM (Galois/Counter Mode).

### Claim 7 (depends on 3)

The method of claim 3, wherein an Internet Protocol security (IPsec) Encapsulating Security Payload (ESP) Transform describes the decryption context (DC) in a ciphertext field, following an initialization vector (IV) and optionally a sequence number and preceding the ciphertext, and wherein the IV and the DC are in an ESP Payload Data field.

### Claim 8 (depends on 1)

The method of claim 1, further comprising creating the key encrypting key using any of Electronic Codebook (ECB) encryption of Advanced Encryption Standard 128-bit (AES-128) keys, and AES in Key Wrap mode with a 256-bit encryption key.

### Claim 9 (depends on 1)

The method of claim 1, further comprising distributing the key encrypting key to a plurality of group members using Group Domain of Interpretation (GDOI).

### Claim 10 (depends on 1)

The method of claim 1, performed as part of a transport layer security (TLS) protocol, or as part of secure real time protocol (RTP), or as part of secure shell (SSH) communications.

### Claim 11 (depends on 3)

The method of claim 3, performed as part of Internet Key Exchange (IKE) or as part of Group Domain of Interpretation (GDOI) and in which the decryption context is conveyed as an octet string to be associated with a Encapsulating Security Payload (ESP) Security Association (SA).

### Claim 12 (depends on 1)

The method of claim 1, further comprising setting the key encrypting key as expired, continuing to use the key encrypting key for decryption but not for encryption, and initiating using a new key encrypting key for both decryption and encryption.

### Claim 13

An apparatus, comprising:
a data storage medium storing: a key encrypting key; a plaintext message to be authenticated, encrypted, and transmitted; an associated data to be authenticated and transmitted, but not encrypted;
logic configured to generate: a data key in a uniformly random or pseudorandom manner;
a nonce that is either unique for any particular value of the data key or zero-length; a ciphertext message, wherein the ciphertext message is at least as long as the plaintext message and is determined from at least the plaintext message, the data key, and the nonce; an encrypted data key, wherein the encrypted data key is derived from at least the data key and the key encrypting key;
logic configured to generate the communication comprising at least the encrypted data key, the ciphertext message and the associated data.

### Claim 14 (depends on 13)

The apparatus of claim 13, further comprising:
logic configured to parse the communication into at least the encrypted data key, the ciphertext message and the associated data, and to reconstruct or receive the nonce;
logic configured to regenerate the data key, wherein the data key is a function of at least the encrypted data key and the key encrypting key, and to regenerate the authentic data key if all of the encrypted data key, the key encrypting key, and the nonce are authentic and to generate a failure indication if at least one of the encrypted data key, the key encrypting key, and the nonce is not authentic;
logic configured to regenerate the plaintext message, wherein the plaintext message is a function of at least the ciphertext message, the data key, and the nonce, and to regenerate the authentic plaintext message if all of the ciphertext message, the data key, and the nonce are authentic and to generate a failure indication if at least one of the ciphertext message, the data key, and the nonce is not authentic.

### Claim 15 (depends on 13)

The apparatus of claim 13, wherein a first device contains logic configured to generate the data key and to encrypt the data, and a second device comprises a data storage medium storing the key encrypting key and is configured to generate the decryption context associated to the data key and to return the decryption context to the first device.

### Claim 16 (depends on 13)

The apparatus of claim 13, wherein the communication comprises a data packet comprising an internet protocol header, an encapsulating security payload header, an initialization vector, a decryption context, an encrypted region, and an integrity check value.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the decryption context comprises the encrypted data key and instructions regarding how a decryptor can decrypt and process the encrypted data key.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein the instructions comprise key management information received from a Logical Key Hierarchy (LKH) group key management protocol or a Subset-Difference key management method.

### Claim 19 (depends on 13)

The apparatus of claim 13, further comprising logic configured to derive the encrypted data key using any of AES-CCM (Advanced Encryption Standard, Counter with Cipher Block Chaining Message Authentication Code), AES-CBC and AES-GCM (Galois/Counter Mode).

### Claim 20 (depends on 16)

The apparatus of claim 16, wherein an Internet Protocol security (IPsec) Encapsulating Security Payload (ESP) Transform describes the decryption context (DC) in a ciphertext field, following an initialization vector (IV) and optionally a sequence number and preceding the ciphertext, and wherein the IV and the DC are in an ESP Payload Data field.

### Claim 21 (depends on 13)

The apparatus of claim 13, further comprising logic configured to create the key encrypting key using any of Electronic Codebook (ECB) encryption of Advanced Encryption Standard 128-bit (AES-128) keys, and AES in Key Wrap mode with a 256-bit encryption key.

### Claim 22 (depends on 13)

The apparatus of claim 13, further comprising logic configured to distribute the key encrypting key to a plurality of group members using Group Domain of Interpretation (GDOI).

### Claim 23 (depends on 13)

The apparatus of claim 13, further comprising logic configured to operate the apparatus as part of a transport layer security (TLS) protocol, or as part of secure real time protocol (RTP), or as part of secure shell (SSH) communications.

### Claim 24 (depends on 16)

The apparatus of claim 16, further comprising logic configured to operate the apparatus as part of Internet Key Exchange (IKE) or as part of Group Domain of Interpretation (GDOI) and in which the decryption context is conveyed as an octet string to be associated with a single Encapsulating Security Payload (ESP) Security Association (SA).

### Claim 25 (depends on 13)

The apparatus of claim 13, further comprising logic configured to cause setting the key encrypting key as expired, continuing to use the key encrypting key for decryption but not for encryption, and initiating using a new key encrypting key for both decryption and encryption.

### Claim 26

A computer-readable storage medium storing one or more sequences of instructions which, when executed by one or more processors, cause performing:
selecting a plaintext message to be authenticated, encrypted and transmitted;
selecting an associated data to be authenticated and transmitted, but not encrypted;
creating and storing a data key to encrypt the plaintext message in a uniformly random or pseudorandom manner;
creating and storing a ciphertext message, wherein the ciphertext message is at least as long as the plaintext message and is derived from at least the plaintext message and the data key;
creating and storing an encrypted data key, wherein the encrypted data key is derived from at least the data key, and a key encrypting key;
generating a communication comprising at least the encrypted data key, the ciphertext message, and the associated data;
wherein each of the above steps is performed by one or more processors.

### Claim 27 (depends on 26)

The computer-readable storage medium of claim 26, further comprising instructions which when executed cause:
parsing the communication into at least the encrypted data key, the ciphertext message, and the associated data;
regenerating the data key, wherein the data key is a function of at least the encrypted data key, and the key encrypting key;
performing an authentication test on the encrypted data key and the key encrypting key;
determining that the data key is authentic only when all of the encrypted data key and the key encrypting key are authentic according to the authentication test;
generating and communicating a failure indication when at least one of the encrypted data key and the key encrypting key is not authentic according to the authentication test;
regenerating a plaintext message, wherein the plaintext message is a function of at least the ciphertext message and the data key, wherein the plaintext message comprises a failure indication if at least one of the ciphertext message and the data key is not authentic according to the authentication test;
wherein each of the above steps is performed by one or more processors.

### Claim 28 (depends on 26)

The computer-readable data storage medium of claim 26, wherein the communication comprises a data packet comprising an internet protocol header, an encapsulating security payload header, an initialization vector, a decryption context, an encrypted region, and an integrity check value.

### Claim 29 (depends on 28)

The computer-readable data storage medium of claim 28, wherein the decryption context comprises the encrypted data key and instructions regarding how a decryptor can decrypt and process the encrypted data key.

### Claim 30 (depends on 29)

The computer-readable medium of claim 29, wherein the instructions comprise key management information received from a Logical Key Hierarchy (LKH) group key management protocol or a Subset-Difference key management method.
