Trusted Execution Remote Attestation With Pre-Boot Filesystem Measurement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote attestation methods fail to verify the integrity and security of applications running in trusted execution environments due to the inability to measure and verify the operating system code and data, leading to uncertainty about the consistency of services provided by cloud service providers.
Innovation Solution
A method involving obtaining a first metric value for a read-only target file system, booting a kernel with this value, measuring the kernel and other components to obtain a second metric value, and performing remote attestation based on this value to ensure the integrity and security of the trusted execution environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional remote attestation methods are used, then the attestation process can be completed, but the operating system code and data cannot be measured, resulting in inability to verify application consistency
Solution Approach 1:
The patent segments the measurement process into two distinct phases: (1) measuring the read-only target file system to obtain a first metric value before kernel boot, and (2) measuring the kernel and other components to obtain a second metric value after boot. This segmentation enables comprehensive measurement of OS code and data that were previously inaccessible, thereby improving measurement precision and enabling verification of application consistency.
Solution Approach 2:
The patent performs preliminary measurement of the target file system to obtain a first metric value before the kernel boots. This preliminary action captures the state of the file system before any potential modifications during kernel execution, establishing a baseline for later verification and enabling complete OS measurement.
2Measurement precision
If the target file system is made read-only, then the first metric value can be obtained for verification, but the system flexibility and write operations are restricted
Solution Approach 1:
The patent divides the file system into two distinct segments: a read-only target file system used for measurement and verification, and a separate writable file system for normal operations. This segmentation allows the system to maintain both integrity verification capability and operational flexibility simultaneously, resolving the contradiction between measurement precision and adaptability.
Solution Approach 2:
The patent introduces an intermediary mechanism where the read-only target file system serves as a reference copy for measurement purposes, while the actual operational file system remains writable. This intermediary approach enables integrity verification without restricting normal write operations, as the read-only copy is used solely for measurement while the operational copy handles all write requests.
3Reliability
If comprehensive measurement of kernel and components is performed, then remote attestation accuracy improves, but the measurement and verification process complexity increases
Solution Approach 1:
The patent implements self-service measurement mechanisms where the system automatically measures itself during the boot process. The kernel and components perform self-measurement to generate metric values, reducing the need for external measurement infrastructure and simplifying the overall process while maintaining high attestation accuracy.
Solution Approach 2:
The patent establishes a feedback loop where metric values are measured, compared against reference values, and used to determine attestation results. This automated feedback mechanism streamlines the verification process by systematically comparing measured values with expected values, reducing manual intervention complexity while improving reliability.
Data Source
AI summary
The present disclosure provides a method, an apparatus, an electronic device, and a storage medium of remote attestation. The method is applied to a first trusted execution environment, and includes: obtaining a first file for a first application, the first file being used to deploy the first application in the first trusted execution environment, and the first file including a read-only target file system; obtaining a first metric value for the target file system; loading the first file, and writing the first metric value into a command line for booting a kernel, and booting a kernel in the first file based on the command line, to deploy the first application in the first trusted execution environment; and measuring the kernel and other components to obtain a second metric value, and performing remote attestation on the first application based on the second metric value.