Management Controller TLS Handshake for Secure Endpoint Trust

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing endpoint devices face challenges in securely establishing trust and maintaining secure connections due to potential compromise of hardware components, which can lead to unauthorized access and compromise of sensitive information.

Innovation Solution

Implementing a management controller that generates and stores a private key independently of hardware resources, using an out-of-band communication channel to establish secure connections and maintain trust, while keeping the private key secure from hardware components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware components are used to establish secure connections, then communication functionality is enabled, but security is compromised due to potential hardware compromise

Engineering Contradiction:
ImprovesecurityVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the endpoint device into two independent segments: hardware resources (processor, memory, storage) and a management controller. The management controller operates independently with its own processing capabilities and securely stores the private key, separating security-critical functions from the main hardware resources that may be compromised.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The management controller acts as an intermediary between the hardware resources and external entities for security-critical operations. It mediates TLS handshakes, certificate verification, and private key protection, preventing direct exposure of security credentials to potentially compromised hardware components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If private key is stored in hardware resources, then access is simplified, but security is reduced due to potential unauthorized access

Engineering Contradiction:
Improvekey managementVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The private key is extracted from the main hardware resources and stored exclusively in the management controller's secure storage. This extraction isolates the private key from potential compromises in the processor, memory, or storage devices, while the management controller provides dedicated key management capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If hardware components manage security functions, then device functionality is integrated, but trust establishment is compromised

Engineering Contradiction:
Improvefunctional integrationVSAvoidtrust establishment
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments security functions from general hardware functions. The management controller handles all security-critical operations including TLS handshakes, certificate management, and private key protection, while hardware resources focus on data processing and application execution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The management controller serves as an intermediary that establishes trust between the endpoint device and external entities. It independently verifies certificates, performs cryptographic operations, and validates security credentials without relying on potentially compromised hardware components.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12574411B2Transport layer security management using a management controller
Publication Date: 2026.03.10 DELL PROD LP
  • US12574411B2 patent drawing
  • US12574411B2 patent drawing
  • US12574411B2 patent drawing

AI summary

Methods and systems for managing an endpoint device are disclosed. To do so, a key pair may be generated by a management controller of the endpoint device and a private key of the key pair may be kept secret by the management controller. A public key of the public private key pair may be provided to a first entity for use in generating a certificate for the endpoint device. The certificate may be provided to a second entity desiring a level of trust with the endpoint device. As a portion of establishing a secure connection between the second entity and the endpoint device, a TLS handshake may be performed. Performing the TLS handshake may include obtaining a TLS packet, signing the TLS packet using the private key, and providing the signed TLS packet to the second entity to demonstrate that the endpoint device is trustworthy for the level of trust.