Cloud Image Digest Verification Excluding Altered Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud providers modifying predefined portions of cloud images prior to publication compromises the effectiveness of traditional digest verification methods, rendering them ineffective for ensuring the integrity of executable portions.
Innovation Solution
Excluding predefined altered portions from the signing and verification processes by generating signed digests without considering metadata and periodically performing automated and scheduled image verification to ensure the integrity of executable portions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional digest verification methods are used to verify cloud images, then verification simplicity is maintained, but verification effectiveness is compromised when cloud providers alter metadata portions
Solution Approach 1:
The cloud image is divided into two distinct portions: a predefined portion (metadata) that may be altered by the cloud provider, and a remaining portion (executable code) that must be verified for integrity. The digest verification process is segmented to only cover the remaining portion, excluding the predefined portion from both signing and verification operations. This segmentation allows the verification system to maintain effectiveness despite potential alterations to the metadata portion.
Solution Approach 2:
The predefined portion (metadata) is extracted and removed from the digest verification process. The signing operation is performed only on the remaining portion of the cloud image, and the verification operation only checks the remaining portion against the stored digest. This extraction of the problematic metadata portion from the verification chain resolves the contradiction by maintaining verification effectiveness while simplifying the process to only what can be trusted.
2Adaptability or versatility
If cloud providers modify metadata portions of cloud images, then operational flexibility is improved, but integrity verification of executable portions becomes unreliable
Solution Approach 1:
The cloud image is segmented into a predefined portion (metadata) and a remaining portion (executable code). The signing and verification operations are applied only to the remaining portion, which contains the executable code that needs integrity protection. This segmentation allows cloud providers to freely modify the metadata portion for operational flexibility while maintaining reliable integrity verification of the executable portions through the digest mechanism.
Solution Approach 2:
The metadata portion is extracted from the integrity verification process. By removing the predefined portion from both the signing input and verification target, the system allows cloud providers to modify metadata as needed for operational flexibility without compromising the reliability of integrity verification for the executable code, which remains protected through the digest comparison.
3Reliability
If complete image verification is performed including metadata portions, then verification thoroughness is maximized, but verification time and processing resources increase
Solution Approach 1:
Instead of performing complete verification of the entire cloud image including metadata, the system applies partial verification only to the remaining portion (executable code) that requires integrity protection. This partial action approach maintains sufficient verification thoroughness for the critical components while significantly reducing verification time and processing resources compared to full image verification.
Data Source
AI summary
Systems and methods for verifying an executable portion of a published cloud image represents an unaltered version of an executable portion of a corresponding original cloud image are provided. In one embodiment, modification of a predefined portion of a cloud image by a cloud provider prior to its publication via a marketplace of the cloud provider is proactively addressed as part of (i) an automated signing process performed by a software publisher on the original cloud image prior to delivery to the cloud provider and (ii) a corresponding background verification process performed on the published cloud image on behalf of users by a management platform. The signing and verification processes are operable to exclude the predefined portion when creating their respective digests, thereby allowing the signed digest created prior to the modification to remain useful as part of a subsequent digest comparison performed by the verification process.