Proprietary Data Protection via Hash Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing risk mitigation processes for proprietary healthcare data in client environments can be circumvented, necessitating improved systems and methods for protecting confidential information.
Innovation Solution
A system and method that involves identifying a file of computer-executable code, performing hashing operations to generate representative values, obtaining and storing approvals, and selectively permitting execution based on matching representative values and available approvals to ensure secure processing and delivery of proprietary data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hashing operations and approval validation are implemented to protect proprietary data, then security and reliability are improved, but device complexity and processing time increase
Solution Approach 1:
The system performs hashing operations on files before they are executed to generate representative values, and stores approvals in advance. This preliminary validation ensures that only authorized and unmodified files can be executed, thereby improving data security without requiring complex runtime checks.
Solution Approach 2:
The system compares the hash value of a file against a stored representative value and checks for associated approvals before permitting execution. This feedback mechanism ensures that any modification to the file is detected and prevents unauthorized execution, enhancing reliability through continuous validation.
2Reliability
If hashing operations and approval validation are implemented to protect proprietary data, then security and reliability are improved, but processing speed decreases
Solution Approach 1:
The hashing and approval validation process is performed in advance before file execution. By pre-computing and storing the representative hash values and approvals, the system minimizes the processing time required at execution time, thus maintaining faster file execution speeds while ensuring security.
3Ease of operation
If existing risk mitigation processes are used, then ease of operation is maintained, but security effectiveness deteriorates because processes can be circumvented
Solution Approach 1:
The system introduces hashing operations and approval validation as intermediary steps between file storage and execution. These intermediaries act as additional security layers that are difficult to circumvent, as they transform the file into a unique hash value that must match the stored representative value for execution to be permitted.
Data Source
AI summary
Systems and methods for protecting proprietary data are provided. A file of computer-executable code that facilitates the processing of proprietary information when executed may be identified. At least one hashing operation may be performed on the file to generate a first representative value associated with the file. At least one approval associated with validation of the file may be received by the computing system. The at least one approval may be stored in association with the generated representative value. Prior to the execution of the file, the at least one hashing operation may be utilized to determine a second representative value associated with the file. Execution of the file may be selectively permitted based at least in part upon a determination of whether the second representative value matches the stored first representative value and whether the at least one approval is available.