Container Integrity Verification via TPM and IMS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In server-less computing environments, verifying the integrity of applications and containers is challenging due to the dynamic nature of resource allocation and the need to ensure that files are not corrupted or tampered with, which is essential for maintaining expected behavior and security.
Innovation Solution
A system architecture that includes an application layer, an operating system layer, and a hardware layer, utilizing an Integrity Measurement System (IMS) and a Trusted Platform Module (TPM) to measure and log file integrity, generate hash values, and protect the system log, enabling attestation and verification of containers by comparing measurements with expected values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional file verification methods are used in server-less computing environments, then verification simplicity is maintained, but reliability of container integrity is insufficient due to dynamic resource allocation and shared computing environments
Solution Approach 1:
The system performs preliminary measurement of file integrity attributes before containers are launched or modified. Hash values of critical system files are calculated and stored in advance in a protection register, creating a baseline for later verification without interfering with the dynamic nature of server-less computing.
Solution Approach 2:
A hardware-based protection register (TPM) acts as an intermediary between the file system and the verification process. This mediator securely stores hash values and provides a trusted reference point for integrity verification, isolating the complexity of verification from the container management system.
2Measurement precision
If comprehensive file measurement is performed for all files in the system, then measurement precision of container integrity is improved, but loss of time increases due to the large number of files in shared computing environments
Solution Approach 1:
The system extracts and measures only the most critical files that directly impact container integrity and security, rather than measuring all files in the system. This selective approach focuses verification efforts on essential system binaries, configuration files, and library files that would affect container behavior if modified.
Solution Approach 2:
Different verification strategies are applied to different files based on their importance. Critical system files receive comprehensive hashing and protection register storage, while less critical files use simpler verification methods or are verified on-demand, creating a tiered verification approach that balances precision and performance.
3Reliability
If security measures are enhanced to protect against software-based attacks in shared environments, then reliability of computing operations is improved, but ease of operation deteriorates due to additional verification steps
Solution Approach 1:
The integrity verification system operates autonomously without requiring manual intervention. The protection register automatically stores hash values, and the verification process occurs transparently in the background during container launch and operation, maintaining security while preserving ease of operation for developers and operators.
Solution Approach 2:
Security verification is performed preliminarily during container image building and registration, rather than during runtime deployment. This allows containers to be pre-validated for integrity, and the verification results are cached and reused during deployment, eliminating security checks as a barrier to rapid deployment.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Examples relate to integrity reports. In an implementation, an entity for executing a function is launched, the entity operating one or more files for executing the function. In response to the entity being launched, an entity image integrity report is generated comprising, for one or more files operated by the entity, a reference to the file measurement in a first integrity report the first integrity report containing measurements of a plurality of files operable in one or more entities. Alternatively, in response to the entity being launched, an entity integrity report is generated comprising a file measurement for each of the files operated by the entity.