Blockchain Secure Customized Software Catalog Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information handling systems lack a secure method to verify customized software catalogs created by customers, as these catalogs are not cryptographically signed by the provider, leaving systems vulnerable to malicious software installations.
Innovation Solution
Implementing a blockchain-based system that generates a customized software catalog hash and smart contract for each customized catalog, allowing verification through a blockchain transaction, ensuring the integrity and safety of software updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized software catalogs are created at customer sites without cryptographic signing, then the catalogs can be customized to match specific computing system components, but the computing systems become vulnerable to malicious software installations
Solution Approach 1:
The patent introduces a blockchain-based intermediary verification mechanism that mediates between the customized catalog creator and the computing system. The blockchain stores cryptographic hashes of approved software catalogs and provides a trusted verification layer, allowing customized catalogs to be safely verified without requiring direct cryptographic signing by the original provider.
Solution Approach 2:
The system performs preliminary cryptographic hashing of the original signed catalog and stores it on the blockchain before customization occurs. This preliminary action creates a trusted reference point that enables subsequent verification of customized versions without compromising security.
2Reliability
If traditional cryptographic signing is used for software catalogs, then the integrity and safety of software updates can be verified, but customized catalogs created at customer sites cannot be signed by the provider
Solution Approach 1:
The verification process is segmented into two independent parts: the original catalog signing (performed by the provider) and the customization process (performed by the customer). The blockchain stores the hash of the original signed catalog, allowing the customization to occur separately while maintaining verifiable integrity through hash comparison.
Solution Approach 2:
The system creates and stores a cryptographic copy (hash) of the original signed catalog on the blockchain. This copy serves as an immutable reference that enables verification of customized catalogs without requiring the original provider to re-sign or directly involvement in the customization process.
3Productivity
If customized software catalogs are distributed without verification capability, then the customization process is simple and fast, but the computing systems are exposed to security risks from malicious catalogs
Solution Approach 1:
The computing system performs self-verification of customized catalogs by comparing the catalog's cryptographic hash against the reference hash stored on the blockchain. This self-service verification mechanism enables fast distribution without requiring intermediary verification for each transaction, while still providing security against malicious software.
Data Source
AI summary
A blockchain-based secure customized catalog system includes a catalog customization system that receives a request to customize a first software catalog, and modifies the first software catalog to create a second software catalog that is customized for computing devices in a computing system. The catalog customization system then generates and broadcasts a first blockchain transaction that includes a smart contract having a second software catalog hash created from the second software catalog. A blockchain device receives the first blockchain transaction and, in response, provides the smart contract on a blockchain. When the blockchain device receives a second blockchain transaction broadcast by the computing system and including a hash value, it executes the smart contract. If the blockchain device determines that the execution of the smart contract indicates that the hash value matches the second software catalog hash, it transmits a second software catalog verification to the computing system.