Hardware Usage Pattern Matching for File Access Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Unauthorized access to files on computing devices often goes undetected by anti-virus applications and firewalls, as current security measures fail to effectively authorize file access events based on preceding hardware usage patterns.
Innovation Solution
An apparatus and method that record and correlate hardware usage patterns prior to file access events, comparing these patterns with established correlations to authorize or block file access events, thereby enhancing security by distinguishing between authorized and unauthorized access attempts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional anti-virus applications and firewalls are used to detect unauthorized access, then basic security coverage is provided, but unauthorized access remains undetected because these tools cannot analyze hardware usage patterns
Solution Approach 1:
The system records hardware usage patterns in advance before any file access event occurs. By capturing and storing the sequence of hardware operations (keyboard, mouse, camera, microphone usage) that precede legitimate file access, the system establishes a baseline of authorized user behavior. This preliminary recording enables later comparison to detect anomalies without requiring complex real-time analysis during actual access attempts.
Solution Approach 2:
The system implements a feedback mechanism by comparing hardware usage patterns before file access events against stored historical patterns. When a file access event occurs, the system analyzes the preceding hardware usage sequence and compares it with previously recorded patterns from authorized users. This feedback loop enables the system to learn and adapt to legitimate user behavior, improving detection accuracy over time while maintaining a manageable complexity level.
2Reliability
If hardware usage patterns are recorded and correlated with file access events to authorize access, then unauthorized access detection capability is improved, but the system complexity and computational requirements increase
Solution Approach 1:
The system segments the file access authorization process into distinct phases: (1) recording hardware usage patterns before access events, (2) storing these patterns with associated file identifiers, (3) receiving new file access events, (4) comparing preceding hardware patterns against stored patterns, and (5) making authorization decisions. This segmentation breaks down the complex pattern correlation task into manageable steps, improving reliability while controlling system complexity.
Solution Approach 2:
The system performs preliminary recording and correlation of hardware usage patterns with file access events before actual authorization decisions are needed. By pre-processing and storing the relationship between hardware patterns and file access in advance, the system reduces the computational burden during real-time authorization, improving both accuracy and efficiency without proportionally increasing complexity.
3Reliability
If the system compares hardware usage patterns to authorize file access events, then security against unauthorized access is enhanced, but processing time and computational resources increase
Solution Approach 1:
The system applies partial action by focusing the pattern comparison only on the specific hardware usage events that occur immediately before a file access event, rather than analyzing all hardware usage throughout the system. This targeted approach maintains high security effectiveness by examining the critical pre-access pattern window while minimizing unnecessary processing time and computational resource consumption.
Data Source
AI summary
An apparatus for authorizing file access events includes a processor and a memory that stores code executable by the processor. The code is executable by the processor to record hardware usage patterns prior to a file access event of a file, and correlate the hardware usage patterns with file access events targeting the file. The code is also executable to receive a file access event targeting the file, compare a hardware usage pattern preceding the received file access event targeting the file to the hardware usage patterns correlated with file access events targeting the file, and authorize the received file access event in response to the hardware usage pattern preceding the received file access event targeting the file matching a hardware usage pattern correlated to a file access event targeting the file.