Protected VM Migration With Ordered State Import and TDX Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtualization systems fail to provide adequate security for data in memory, especially in cloud environments, as data is vulnerable to attacks and conventional systems do not effectively isolate customer workloads from cloud service provider software, increasing the Trusted Computing Base (TCB) and compromising data confidentiality and integrity.
Innovation Solution
The implementation of Intel Trust Domain Extensions (TDX) and Multi-Key Total Memory Encryption (MKTME) provides secure migration of protected virtual machines by using encryption, integrity protection, and hardware isolation to create cryptographically isolated trust domains, ensuring that customer workloads are protected from untrusted cloud infrastructure and reducing the TCB.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If data is stored in memory for processing in virtualized systems, then processing speed and accessibility are improved, but data becomes vulnerable to attacks and security breaches
Solution Approach 1:
The patent introduces an intermediary encryption layer between the memory and the data. Memory encryption engines encrypt data before it is written to memory and decrypt it when read, allowing fast processing while protecting data confidentiality. This intermediary encryption mechanism resolves the contradiction by enabling both fast access and security.
Solution Approach 2:
The patent changes the state of data in memory from plaintext to encrypted form through dynamic memory encryption. By changing the encryption parameters (using different encryption keys for different memory regions or tenants), the system maintains processing speed while protecting data from attacks, thus resolving the vulnerability issue.
2Adaptability or versatility
If cloud service provider software is included in the Trusted Computing Base to manage virtual machines, then system functionality and management capability are improved, but the TCB size increases and security is compromised
Solution Approach 1:
The patent segments the system into trusted and untrusted components using hardware-enforced isolation. The TCB is segmented to include only essential security-critical components, while cloud service provider management software is isolated in untrusted regions. This segmentation allows the system to maintain functionality through the untrusted software while preserving security through the minimized trusted core.
Solution Approach 2:
The patent extracts cloud service provider software from the Trusted Computing Base and places it in untrusted execution environments. By taking out the management software from the TCB, the system maintains its functionality (the software still manages VMs) while reducing the TCB size and improving security, as the extracted software can no longer compromise the trusted security functions.
3Adaptability or versatility
If data is migrated between different virtualization platforms, then workload flexibility and cloud mobility are improved, but data security and integrity during migration are compromised
Solution Approach 1:
The patent uses cryptographic copying mechanisms to migrate data between platforms. Instead of directly transferring plaintext data, the system copies encrypted data representations and uses hardware-enforced cryptographic verification to ensure integrity during migration. This allows workload flexibility while maintaining security, as the copied data can be verified for integrity without exposing it in plaintext during transfer.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for migration of a source protected virtual machine from a source platform to a destination platform are descried. A method of an aspect includes enforcing that bundles of state, of a first protected virtual machine (VM), received at a second platform over a stream, during an in-order phase of a migration of the first protected VM from a first platform to the second platform, are imported to a second protected VM of the second platform, in a same order that they were exported from the first protected VM. Receiving a marker over the stream marking an end of the in-order phase. Determining that all bundles of state exported from the first protected VM prior to export of the marker have been imported to the second protected VM. Starting an out-of-order phase of the migration based on the determination that said all bundles of the state exported have been imported.