TPM Replacement Key Recovery for Encrypted Storage Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information handling systems face challenges in managing the replacement of a failed trusted platform module (TPM) without data loss, as the cryptographic keys associated with the TPM are not efficiently managed during the replacement process.

Innovation Solution

A method and system for managing TPM replacement involving registration with a management server, encryption and decryption using different keys, and synchronization of keys between the client and server to ensure seamless key restoration and minimal data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the TPM is replaced with a new TPM, then the system can continue to function with updated hardware, but the cryptographic keys associated with the old TPM are lost causing data access issues

Engineering Contradiction:
Improvesystem functionalityVSAvoidcryptographic keys
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by creating and storing backup cryptographic keys in secure external storage (HSM or cloud database) before the TPM is replaced. This ensures that when the old TPM is removed, the keys are already preserved and can be restored to the new TPM, preventing data access loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A key management server acts as an intermediary between the TPM and the cryptographic keys. Instead of keys being stored only in the TPM, the key management server maintains copies and facilitates key restoration when TPM replacement occurs, mediating the key transfer process securely.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If cryptographic keys are stored securely in the TPM, then security is maintained, but TPM replacement results in data loss and requires complex key recovery processes

Engineering Contradiction:
ImprovesecurityVSAvoidkey recovery process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system extracts cryptographic keys from the TPM and stores them in separate secure external locations (HSM or cloud database). This separation allows the TPM to be replaced without losing key access, as keys can be retrieved from external storage and restored to the new TPM through automated processes.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The key management system provides self-service capabilities where the automated key restoration process occurs without requiring manual intervention. When a TPM is replaced, the system automatically detects the change, retrieves the appropriate keys from secure storage, and restores them to the new TPM, making the process transparent to users.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If backup keys are stored externally, then TPM replacement becomes easier, but security risks increase from external key storage

Engineering Contradiction:
ImproveTPM replacementVSAvoidsecurity risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system implements beforehand cushioning by storing cryptographic keys in secure external storage (HSM or cloud database with encryption) before any TPM failure occurs. This preparatory measure ensures that key loss is prevented while maintaining security through hardened external storage infrastructure, allowing easy TPM replacement without compromising security.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12596849B2Managing trusted platform module (TPM) replacement at an information handling system
Publication Date: 2026.04.07 DELL PROD LP
  • US12596849B2 patent drawing
  • US12596849B2 patent drawing
  • US12596849B2 patent drawing

AI summary

Managing TPM replacement at a IHS, including encrypting, by the client IHS, a storage device at the client IHS utilizing a first TPM and first keys; providing, by the client IHS and to the management server IHS, the first keys; storing the first keys at a database; detecting replacement of the first TPM with a second TPM at the client IHS, and in response: requesting, by the client IHS, the first keys; receiving, from the management server IHS, the first keys; decrypting, by the client IHS, the storage device at the client IHS utilizing the second TPM and the first keys; encrypting, by the client IHS, the storage device at the client IHS utilizing the second TPM and second keys differing from the first keys; providing, to the management server IHS, the second keys; and storing the second keys at the database.