Memory Structure Segmentation for Malware Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computing platforms lack the capability to prevent malicious software from being loaded and executed by restricting executable applications to read-only storage and data storage to writable memory only, which is essential to prevent malware execution.
Innovation Solution
Structuring computer hardware and firmware to test aspects of code and its environment before loading and executing it, with a memory structure comprising separate executable and data storage areas, where the executable area is switchable between read-write and read-only states, and using a hash verification to ensure integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If executable applications are stored in read-only storage space and data storage is restricted to writable memory space, then malware execution is prevented, but current computing platforms lack this capability
Solution Approach 1:
The memory structure is divided into separate executable application storage area and data storage area with distinct access permissions. This segmentation prevents malware from being executed by restricting executable code to read-only storage while allowing data operations in writable memory space.
Solution Approach 2:
The executable application storage area is made dynamically switchable between read-write and read-only states through a memory state switch structure. This allows the system to transition from a writable state during legitimate application installation to a read-only state for malware prevention, providing flexibility while maintaining security.
2Adaptability or versatility
If the executable application storage area is made writable to allow application installation, then adaptability is improved, but security deteriorates as malware can be loaded
Solution Approach 1:
The system performs preliminary actions by switching the executable application storage area to read-only state before allowing application installation. This ensures that once applications are installed, the storage area automatically becomes read-only, preventing malware from being loaded while still allowing legitimate applications to be installed during the writable phase.
Solution Approach 2:
The binary loader tests whether the executable application storage area is in read-only state before loading applications. This feedback mechanism ensures that applications are only loaded when the storage area is in the appropriate read-only state, preventing malware execution while allowing legitimate application installation when conditions are met.
3Productivity
If the binary loader loads and executes applications without testing memory state, then productivity is maintained, but security is compromised
Solution Approach 1:
The binary loader performs a simple test to determine if the executable application storage area is in read-only state before loading applications. This partial action provides sufficient security verification without requiring complex checks, thereby maintaining productivity while ensuring code integrity through the read-only state verification.
Data Source
AI summary
A computer system comprising a processor in communication with a memory structure; the processor retrieving and executing executable code stored in the memory structure thereby to process data stored in and retrieved from the memory structure; the memory structure including at least an area designated as an executable application code storage area and a separate area designated as a data storage area; structuring computer hardware and firmware on a computing platform of the computer system so as to test certain aspects of a block of code and the environment in which it is located prior to a binary loader of the computing platform loading and executing the block of code. In instances where the block of code fails one or more of the tests then the block of code is not loaded and/or is not executed by the binary loader.