Kernel-Level File Verification for Virtual Resource Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information processing systems face challenges in preventing malicious or unauthorized software from being downloaded as part of virtual resource templates, which can compromise system security and lead to unauthorized access or Denial-of-Service attacks.
Innovation Solution
Implementing a kernel-level write interception and verification module that calculates file-specific values, such as hash values, and compares them to a list of designated values to initiate automated actions like writing, notification, deletion, or access limitation for files being downloaded to processing devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If file download is allowed without verification, then productivity and ease of operation are improved, but system security and reliability deteriorate due to malicious software
Solution Approach 1:
The system performs file verification before allowing the file to be written to the file system. The kernel-level entity intercepts the write request, calculates the hash value of the file data, compares it against designated hash values, and only allows the write operation if the file is verified as legitimate. This preliminary verification action prevents malicious software from being executed while maintaining efficient file downloads.
2Reliability
If kernel-level write interception is implemented, then system security is improved, but device complexity increases
Solution Approach 1:
The kernel-level entity is designed to handle multiple functions within the existing operating system framework. It intercepts write requests, calculates hash values, compares against designated values, and manages automated actions (allowing, blocking, notifying, deleting) all within a single integrated component. This multi-functional design improves security without proportionally increasing complexity, as the entity leverages existing kernel mechanisms rather than adding separate complex subsystems.
3Reliability
If automated actions are implemented for file verification, then system security is improved, but loss of time increases due to verification process
Solution Approach 1:
The system implements feedback mechanisms where the kernel-level entity receives the file data, calculates its hash value, compares it against stored designated hash values, and provides feedback by allowing or blocking the write operation. Additional feedback includes generating notifications when files are blocked. This feedback loop ensures security verification is completed efficiently with minimal time overhead, as the verification process is optimized and parallelized where possible.
Data Source
AI summary
Techniques are provided for file protection using evaluation of file-specific values. One method comprises obtaining, by an entity of a device, at least a portion of a file to be written to the device; obtaining, by the entity, a file-specific value associated the portion of the file; comparing, by the entity, the file-specific value to a list of designated values; and initiating, by the entity, an automated action based on a result of the comparison. The file-specific value may comprise a hash value calculated in response to receiving a request to write the portion of the file to the device. The file may comprise a template for a virtual machine and/or a container. The automated action May comprise generating a notification; deleting the portion of the file from the device; preventing access to the portion of the file; and/or limiting access to the portion of the file.