IP Library Granted Patent US 11,599,378
Granted Patent B2
US 11,599,378 · App. 17/115,998 · Granted Mar 7, 2023

Data encryption key management system

Inventors: Naman Goel (Bangalore, IN); Ravishankar Kanakapura Nanjundaswamy (Bangalore, IN); Sharad Awasthi (Bangalore, IN)
Assignee: Dell Products L.P.
G06F9/45558H04L9/0819H04L9/0897H04L9/3247H04L9/3263H04L63/0428G06F2009/45587
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,599,378
App. No.
17/115,998
Granted
Mar 7, 2023
Kind
B2
Abstract

A data encryption key management system includes an application layer with a hypervisor and a virtual machine, a host operating system coupled to the application layer and including a key management agent, and a Baseboard Management Controller (BMC) device coupled to the host operating system and including a BMC storage device providing a key vault. The BMC device receives a first stored data encryption key that was generated by the hypervisor for the virtual machine from the key management agent, and stores the first stored data encryption key in the key vault provided by the BMC storage device. The BMC device subsequently receives a stored data encryption key request from the key management agent and, in response, retrieves the first stored data encryption key from the key vault provided by the BMC storage device, and transmits the first stored data encryption key to the key management agent.

Claims (63)

1. A data encryption key management system, comprising:

an application layer including a hypervisor and a virtual machine;

a host operating system that is coupled to the application layer and that includes a key management agent; and

a Baseboard Management Controller (BMC) device that is coupled to the host operating system and that includes a BMC storage device providing a key vault, wherein the BMC device is configured to:

receive, from the key management agent, a first stored data encryption key generated by the hypervisor for the virtual machine;

store the first stored data encryption key in the key vault provided by the BMC storage device;

receive, from the key management agent subsequent to storing the first stored data encryption key in the key vault provided by the BMC storage device, a stored data encryption key request; and

retrieve, in response to receiving the stored data encryption key request, the first stored data encryption key from the key vault provided by the BMC storage device, and transmit the first stored data encryption key to the key management agent.

2. The system of claim 1 , further comprising:

a communication system coupled to the BMC device, wherein the BMC device is configured to:

receive, from the communication system, a transmitted data encryption key request; and

generate, in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for encrypting data received from the host operating system for transmission via a network.

3. The system of claim 2 , wherein the BMC device is configured to:

sign, using a hardware certificate, encrypted data prior to transmission of the encrypted data via the network.

4. The system of claim 1 , further comprising:

a communication system coupled to the BMC device, wherein the BMC device is configured to:

receive, from the communication system, a transmitted data encryption key request; and

generate, in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for decrypting data received via a network.

5. The system of claim 4 , wherein the BMC device is configured to:

verify a signature provided with data included in the transmitted data encryption key request and, in response, generate the transmitted data encryption key.

6. The system of claim 1 , further comprising:

an initialization system coupled to the BMC device, wherein the BMC device is configured to:

provide, in a pre-boot environment, a BMC operating system that is configured to configure the initialization system to access a second stored data encryption key while in the pre-boot environment.

7. An Information Handling System (IHS), comprising:

a processing system; and

a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a Baseboard Management Controller (BMC) engine that is configured to:

receive, from a key management agent included in a host operating system provided on a computing system, a first stored data encryption key generated by a hypervisor provided on the computing system for a virtual machine provided on the computing system;

store the first stored data encryption key in a key vault provided by a BMC storage device included in the computing system;

receive, from the key management agent subsequent to storing the first stored data encryption key in the key vault provided by the BMC storage device, a stored data encryption key request; and

retrieve, in response to receiving the stored data encryption key request, the first stored data encryption key from the key vault provided by the BMC storage device, and transmit the first stored data encryption key to the key management agent.

8. The IHS of claim 7 , wherein the BMC engine is configured to:

receive, from a communication system included in the computing system, a transmitted data encryption key request; and

generate, in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for encrypting data received from the host operating system for transmission via a network.

9. The IHS of claim 8 , wherein the BMC engine is configured to:

sign, using a hardware certificate, encrypted data prior to transmission of the encrypted data via the network.

10. The IHS of claim 7 , wherein the BMC engine is configured to:

receive, from a communication system included in the computing system, a transmitted data encryption key request; and

generate, in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for decrypting data received via a network.

11. The IHS of claim 10 , wherein the BMC engine is configured to:

verify a signature provided with data included in the transmitted data encryption key request and, in response, generate the transmitted data encryption key.

12. The IHS of claim 7 , wherein the BMC engine is configured to:

provide, in a pre-boot environment, a BMC operating system that is configured to configure an initialization system included in the computing system to access a second stored data encryption key while in the pre-boot environment.

13. The IHS of claim 7 , wherein the BMC engine is configured to:

encrypt, using a Trusted Platform Module (TPM) included in the computing system and prior to storing the first stored data encryption key in the key vault, the first stored data encryption key.

14. A method for managing data encryption keys, comprising:

receiving, by a Baseboard Management Controller (BMC) device included in a computing system from a key management agent included in a host operating system provided on the computing system, a first stored data encryption key generated by a hypervisor provided on the computing system for a virtual machine provided on the computing system;

storing, by the BMC device, the first stored data encryption key in a key vault provided by a BMC storage device included in the BMC device;

receiving, by the BMC device from the key management agent subsequent to storing the first stored data encryption key in the key vault provided by the BMC storage device, a stored data encryption key request; and

retrieving, by the BMC device in response to receiving the stored data encryption key request, the first stored data encryption key from the key vault provided by the BMC storage device, and transmitting the first stored data encryption key to the key management agent.

15. The method of claim 14 , further comprising:

receiving, by the BMC device from a communication system included in the computing system, a transmitted data encryption key request; and

generating, by the BMC device in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for encrypting data received from the host operating system for transmission via a network.

16. The method of claim 15 , further comprising:

signing, by the BMC device using a hardware certificate, encrypted data prior to transmission of the encrypted data via the network.

17. The method of claim 14 , further comprising:

receiving, by the BMC device from a communication system included in the computing system, a transmitted data encryption key request; and

generating, by the BMC device in response to receiving the transmitted data encryption key request, a transmitted data encryption key that is configured for use by the communication system for decrypting data received via a network.

18. The method of claim 17 , further comprising:

verifying, by the BMC device, a signature provided with data included in the transmitted data encryption key request and, in response, generating the transmitted data encryption key.

19. The method of claim 14 , further comprising:

providing, by the BMC device in a pre-boot environment, a BMC operating system that is configured to configure an initialization system included in the computing system to access a second stored data encryption key while in the pre-boot environment.

20. The method of claim 14 , further comprising:

encrypting, by the BMC device using a Trusted Platform Module (TPM) included in the computing system and prior to storing the first stored data encryption key in the key vault, the first stored data encryption key.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (055479/0342) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0460 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (055479/0051) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0663 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (056136/0752) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0771 →
RELEASE OF SECURITY INTEREST AT REEL 055408 FRAME 0697 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0553 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 056136/0752 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 055479/0051 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 055479/0342 →
SECURITY AGREEMENT Recorded Feb 25, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 055408/0697 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2020
From: GOEL, NAMAN; NANJUNDASWAMY, RAVISHANKAR KANAKAPURA; AWASTHI, SHARAD
To: DELL PRODUCTS L.P.
Reel/Frame 054589/0150 →
Continuity (1)
Related Publication 20220179674A1 · Jun 9, 2022