Application Integrity Verification Using Hash and Signature Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application integrity verification methods in enterprise resource access are vulnerable to security threats, particularly in bring your own device (BYOD) scenarios, where compromised executables can gain access by renaming files, and existing solutions to revoke file access are intrusive.
Innovation Solution
Implementing a system that verifies application integrity using application file hash and signature data, in addition to traditional checks like executable name and path, to ensure secure access to enterprise resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional verification methods (path and executable name) are used to identify applications, then ease of operation is improved, but security is worsened because compromised executables can gain access by renaming files
Solution Approach 1:
The patent changes the verification parameter from executable name and path to cryptographic hash values of the executable file and its certificate signature. This transformation allows reliable security verification while maintaining ease of operation, as the hash verification process is automated and does not require user intervention.
Solution Approach 2:
The patent replaces the mechanical file system approach (relying on file paths and names) with a cryptographic verification system. Instead of checking where a file is located or what it is called, the system uses hash functions and digital signatures to verify the file's integrity and authenticity, substituting cryptographic mechanisms for traditional file system mechanisms.
2Reliability
If access to file location and rename capability are revoked to prevent security threats, then security is improved, but ease of operation is worsened for users needing such access for enterprise tasks
Solution Approach 1:
The patent introduces cryptographic hash verification as an intermediary mechanism between the security requirement and user operation. Instead of directly restricting user access to file locations, the system uses hash verification as a mediator that allows users to rename and move files freely while still ensuring security through automated verification of the executable's cryptographic signature.
3Reliability
If cryptographic verification (hash and signature) is implemented to prevent unauthorized access, then security is improved, but device complexity is worsened
Solution Approach 1:
The patent implements self-service through automated cryptographic verification. The system automatically computes hash values, verifies digital signatures, and validates certificate chains without requiring user intervention or manual configuration. This automation masks the underlying complexity while providing robust security.
Solution Approach 2:
The patent performs preliminary cryptographic verification before allowing application execution. By verifying the executable's hash and certificate signature in advance, the system prevents unauthorized applications from running, thereby simplifying the overall security model by catching potential threats before they can cause harm.
4Ease of operation
If traditional file path verification is used, then ease of operation is maintained, but measurement precision is worsened because it cannot reliably distinguish genuine from compromised executables
Solution Approach 1:
The patent changes the verification parameter from file path (which can be easily altered) to cryptographic hash values (which are computationally infeasible to forge). This parameter transformation dramatically improves measurement precision in application identity verification while maintaining ease of operation through automated verification processes.
Data Source
AI summary
Disclosed are various approaches for ensuring application integrity for enterprise resource access. In some examples, a client device extracts installed application data from a local instance of an application that is installed on the client device. The installed application data includes actual certificate-based signature information for the local instance of the application. An application verification status is generated using the actual certificate-based signature information and the expected certificate-based signature information; and network access to a protected set of enterprise resources is permitted or denied using the application verification status.