Sealed Container Policy Verification for Device Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Consumer devices connected to networks are vulnerable to malicious actors intercepting and falsifying software/firmware updates, allowing unauthorized access and exploitation of private data due to inadequate authentication and verification mechanisms.
Innovation Solution
Implementing a trusted platform module (TPM) within a trusted execution environment (TEE) that uses sealed containers and provisioning code segments with policies to authenticate and verify software updates, ensuring integrity by measuring and satisfying specific policies before unsealing and installing updates or data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication mechanisms are used for software updates, then device connectivity and update installation are maintained, but security vulnerability to malicious updates increases
Solution Approach 1:
The authentication mechanism is segmented into multiple independent components: a trusted platform module (TPM) for hardware-based security, a trusted execution environment (TEE) for isolated code execution, sealed containers for protected update packages, and provisioning code segments for verification. Each component performs a specific security function, collectively providing robust authentication without requiring a single complex security system.
2Reliability
If sealed containers with policy verification are implemented, then update integrity is ensured, but update installation time increases
Solution Approach 1:
The sealed container is prepared in advance with embedded provisioning code segments and policy definitions before distribution. The integrity verification logic is pre-configured within the sealed container itself, allowing the device to autonomously verify update integrity without requiring time-consuming external validation or complex real-time analysis during installation.
3Reliability
If measurement and policy satisfaction verification are performed before unsealing, then unauthorized access is prevented, but processing overhead increases
Solution Approach 1:
The trusted execution environment (TEE) acts as an intermediary between the sealed container and the device's main processing system. The TEE performs the computationally intensive measurement and policy verification operations in an isolated, secure environment, protecting the main system from processing overhead while ensuring rigorous access control. The TPM provides hardware-accelerated cryptographic operations to further optimize verification performance.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A device is configured with a trusted platform module (TPM) executing in a trusted execution environment (TEE). Software/firmware updates, user data, applications, etc. are pushed to the device as a payload. The payloads contain a sealed container (e.g., the software/firmware update, user data, applications, etc.), one or more policies, and one or more provisioning code segments corresponding to the one or more policies. The policies are checked by the TPM of the device. If the measurement of the one or more provisioning code segments satisfy the one or more policies, then the sealed container is unsealed by the TPM and released to the device.