NIC Secure Enclave Key Architecture for Scalable Network Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In supercomputing systems, sensitive data is vulnerable to access by system administrators due to shared infrastructure, compromising user data privacy and authenticity.
Innovation Solution
Implementing a scalable key state system using a Network Interface Card (NIC) with a secure enclave that stores a Unique Device Secret (UDS) for generating public keys, and a key server for authenticating and distributing private/public key pairs, ensuring data-in-motion and data-at-rest encryption, with a Root-of-Trust (RoT) for hardware-level authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional shared infrastructure is used for supercomputing systems, then system accessibility and ease of operation are improved, but data security and privacy are compromised due to administrator access capabilities
Solution Approach 1:
The system segments the key management functionality by separating key generation, storage, and distribution across multiple components: the Root of Trust (RoT) in the NIC generates and stores private keys locally, the key server only distributes public keys and encrypted data, and no single component holds complete access capability. This segmentation ensures that even system administrators cannot access encrypted data without the private key stored in the isolated RoT.
Solution Approach 2:
The patent introduces a key server as an intermediary that mediates between the NIC and the encrypted data. The key server receives encrypted data from senders, stores it without the ability to decrypt, and only distributes public keys to authorized recipients. This intermediary architecture ensures that administrators cannot access user data as they lack the private key stored in the RoT.
2Reliability
If encryption is implemented at every node in distributed systems, then data security is improved, but system complexity and device complexity increase
Solution Approach 1:
The Root of Trust (RoT) in the NIC serves multiple functions: generating cryptographic key pairs, storing private keys securely, encrypting data before transmission, and decrypting received data. This multi-functional design consolidates what would otherwise require separate components, reducing overall system complexity while maintaining strong encryption at each node.
Solution Approach 2:
Each NIC equipped with RoT autonomously generates its own key pairs and manages its own encryption/decryption operations without requiring external key management infrastructure. This self-service capability eliminates the need for complex centralized key distribution systems, reducing system complexity while ensuring data security at every node.
3Reliability
If unique keys are stored in each NIC for authentication, then data authenticity and security are improved, but key management scalability and ease of operation deteriorate
Solution Approach 1:
The patent extracts the sensitive private key storage and management functionality from the NIC and places it in the isolated Root of Trust (RoT) component. The RoT generates and retains private keys locally without exposing them to the host system or network. Only public keys are extracted and distributed through the key server, simplifying key management scalability while maintaining strong authentication.
Solution Approach 2:
The system uses public key copies distributed through the key server for authentication and key exchange purposes, while the original private key remains securely stored in the RoT. This copying approach allows multiple nodes to verify authenticity using public key copies without compromising the security of the original private key, enabling scalable key management.
4Ease of operation
If private keys are distributed through the network, then ease of operation is improved, but security is compromised due to potential interception and unauthorized access
Solution Approach 1:
Instead of distributing private keys through the network (the conventional approach), the patent inverts the model by distributing only public keys and having each node generate and retain its own private key locally in the RoT. This inversion eliminates the security risk of private key interception while maintaining ease of operation through automated public key distribution via the key server.
Solution Approach 2:
The patent extracts the private key from the distribution process entirely, keeping it generated and stored locally in the RoT. Only public keys are extracted and distributed through the network via the key server. This extraction of the private key from the distribution chain eliminates interception risks while maintaining operational efficiency.
Data Source
AI summary
Systems and methods are provided for implementing encryption of data-in-motion and/or otherwise stored data using a key server and a secure enclave of a Network Interface Card (NIC). The NIC acts as a passthrough between the client device and the shared infrastructure of the supercomputer system to help ensure data security in a massively scaled and distributed system. For example, in response to an enrollment process that stores a decrypted key in the secure enclave of a NIC, the NIC can receive a data packet from a client device. The NIC can transmit a key request to a key server that includes an encrypted key corresponding to the decrypted key. The key server can look up the previously stored private/public key pair to authenticate the NIC. The key server can provide private/public key pair to the NIC to allow the NIC to later encrypt data-in-motion.