Immutable Property Validation for Isolated Digital Assets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for evaluating system integrity of isolated digital assets are vulnerable to adversarial penetration and require complex, resource-intensive processes that can be compromised.
Innovation Solution
A self-contained method using two scripts that perform localized integrity evaluations, generating unique and immutable properties, and storing them securely to assess the integrity of isolated digital assets, with the scripts removing themselves after execution to reduce vulnerability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If complex, resource-intensive integrity evaluation processes are used, then measurement precision is improved, but device complexity and resource consumption increase
Solution Approach 1:
The integrity evaluation process is segmented into two distinct scripts: a first script that generates immutable properties by searching and analyzing digital assets, and a second script that validates these properties. This segmentation divides the complex evaluation process into manageable, independent components that can be executed separately, reducing overall system complexity while maintaining evaluation accuracy.
Solution Approach 2:
The first script creates immutable property copies of digital assets that can be stored and validated without requiring access to the original assets during validation. These property copies serve as lightweight representations that preserve integrity information while reducing the resource intensity of the evaluation process.
2Ease of operation
If scripts are retained after execution, then ease of operation is improved, but reliability decreases due to increased vulnerability to adversarial compromise
Solution Approach 1:
The evaluation scripts are designed as disposable, single-use objects. After the first script generates immutable properties and the second script validates them, both scripts are deleted from the isolated system. This disposable approach ensures that no persistent code remains that could be exploited by adversaries, while the immutability of the generated properties ensures that the evaluation results remain reliable and tamper-proof.
Solution Approach 2:
The harmful element (the executable scripts) is extracted and removed from the system after completing their useful function. The scripts perform their integrity evaluation task and then self-delete, leaving only the immutable property data that serves as evidence of the evaluation without the security risks associated with retaining executable code.
3Measurement precision
If thorough integrity assessment of multiple properties is performed, then measurement precision is improved, but loss of time increases
Solution Approach 1:
The first script performs preliminary actions by searching for digital assets, analyzing their properties, and generating immutable property data before the validation phase. This preliminary generation of all necessary property information allows the second script to perform rapid validation without needing to re-analyze the original assets, significantly reducing the time required for comprehensive integrity assessment.
Data Source
AI summary
A device, method, and computer readable medium for conducting data integrity analyses is disclosed. Illustratively, the method includes transmitting a first script to a target device. The target device is at least in part isolated from an enterprise storing data elements on the target device to isolate them from subsystems of the enterprise. In some examples, the data elements may comprise data generated through machine learning. The first script includes instructions to search a target device for one or more properties, to create a data file based on found properties, to create a unique immutable property based on each data file, and to create an aggregated immutable property list for all data files generated by the first script. The first script is configured to locally store information generated by the first script upon execution, and remove the first script after execution. The method includes transmitting a second script, complementary to the first script, to evaluate integrity of information generated by the first script.