Compute Node Merging via TPM Secure Channel Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-node server environments are vulnerable to security threats such as spoofing, tampering, information disclosure, denial of service, and code and TPM event log integrity issues due to the untrusted nature of service processors during node merging processes.
Innovation Solution
Implementing an authentication protocol that utilizes provisioned node certificates and trusted platform modules (TPMs) to establish a secure channel for merging compute nodes, where each node is assigned a role and exchanges quote requests and responses to authenticate and validate the integrity of the nodes, thereby enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If service processor controls node merge operation, then node merging capability is improved, but security vulnerability increases due to untrusted service processor
Solution Approach 1:
The patent introduces a secure channel as an intermediary between compute nodes during the merge operation. This secure channel mediates the authentication and certificate exchange processes, preventing the untrusted service processor from accessing or tampering with sensitive cryptographic materials. The secure channel acts as a protected communication path that isolates the trustworthiness of the service processor from the critical authentication operations.
Solution Approach 2:
The patent segments the merge operation into distinct phases: initial authentication phase using secure channel, certificate validation phase, and final merge phase. By separating the authentication operations from the general service processor control, the system ensures that even if the service processor is untrusted, it cannot compromise the security-critical authentication steps. This segmentation isolates the harmful influence of the untrusted service processor to non-critical operations only.
2Adaptability or versatility
If traditional authentication methods are used during node merge, then compatibility is maintained, but authentication overhead and complexity increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring each compute node with a TPM containing cryptographic credentials (endorsement keys and attestation keys) before the merge operation. The secure channel is also pre-established using these credentials. This preliminary setup eliminates the need for complex runtime authentication negotiations, as the nodes already possess verified identities and the communication path is pre-secured, thereby reducing authentication overhead while maintaining compatibility.
3Reliability
If service processor is treated as untrusted, then security is improved, but loss of information increases due to inability to rely on service processor for integrity verification
Solution Approach 1:
The patent implements feedback mechanisms where compute nodes continuously verify each other's identities and the integrity of communication through the secure channel. The TPMs provide cryptographic feedback (attestation quotes) that confirm the identity and state of each node. This feedback loop ensures that even without trusting the service processor, nodes can independently verify integrity, preventing information loss while maintaining high security.
Data Source
AI summary
Method, apparatus, and computer program product are provided for merging multiple compute nodes with trusted platform modules utilizing provisioned node certificates. In some embodiments, compute nodes are connected to be available for merger into a single multi-node system. Each compute node includes a trusted platform module (TPM) provisioned with a platform certificate and a signed attestation key (AK) certificate and is accessible to firmware on the compute node. One compute node is assigned the role of master compute node (MCN), with the other compute node(s) each assigned the role of slave compute node (SCN). A quote request is sent from the MCN to each SCN under control of firmware on the MCN. In response to receiving the quote request, a quote response is sent from each respective SCN to the MCN under control of firmware on the respective SCN, wherein the quote response includes the AK certificate of the respective SCN's TPM.