Self-Correcting Secure Computer System Memory Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current secure computer systems are vulnerable to persistent attacks due to the execution of operating systems from persistent memory, which is resource-intensive and time-consuming to verify, and encryption processes are susceptible to reverse-engineering if certain aspects are known.

Innovation Solution

A self-correcting secure computer system that loads a trusted operating system configuration from read-only memory (ROM) into volatile random access memory (RAM) during boot, automatically erases volatile memory upon shutdown or reboot, and disconnects from networks before accessing persistent storage or encryption protocols to prevent data exposure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the operating system is executed from persistent memory, then the system can maintain data across power cycles, but the system becomes vulnerable to persistent attacks and verification becomes resource-intensive and time-consuming

Engineering Contradiction:
Improvedata persistenceVSAvoidvulnerability to persistent attacks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system divides memory into persistent memory (for data storage) and volatile memory (for OS execution). The OS is segmented into configuration data stored in persistent memory and executable code loaded into volatile memory, allowing data persistence while eliminating attack vectors in the execution environment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention extracts the OS executable code from persistent memory and places it in volatile memory for execution. Only the essential configuration data remains in persistent memory, removing the vulnerability of having the entire OS stored and executable from persistent storage.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the operating system is verified for integrity, then security is improved, but the process becomes resource-intensive and time-consuming

Engineering Contradiction:
ImprovesecurityVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates a trusted copy of the OS configuration in volatile memory from persistent memory. Verification is performed on this copy during the brief window before execution, rather than continuously verifying the entire OS from persistent memory, reducing time and resource requirements.

Inventive Principle:
Principle #26Copying

3Reliability

If encryption keys are stored and accessed, then data security is improved, but the system becomes susceptible to reverse-engineering if encryption processes are known

Engineering Contradiction:
Improvedata securityVSAvoidencryption process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The encryption suite is extracted from persistent memory and executed in isolation in volatile memory. This separates the encryption process from the main system, making reverse-engineering more difficult while maintaining security functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system uses an intermediary execution environment (volatile memory) to run the encryption suite. This intermediary layer protects the encryption processes from direct observation or analysis by the main system, reducing reverse-engineering risks.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If volatile memory is automatically erased upon shutdown, then security against persistent attacks is improved, but data loss occurs and system productivity is reduced

Engineering Contradiction:
ImprovesecurityVSAvoidsystem efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments data storage and execution memory. Volatile memory is used exclusively for OS execution and is safely erased on shutdown, while persistent memory retains essential data and configuration. This segmentation allows automatic erasure without productivity loss, as no user data is stored in the erasable portion.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11669389B1Systems and methods for secure deletion of information on self correcting secure computer systems
Publication Date: 2023.06.06 KEEP SECURITY LLC
  • US11669389B1 patent drawing
  • US11669389B1 patent drawing
  • US11669389B1 patent drawing

AI summary

A self-correcting secure computer system is provided. The computer system includes a read-only memory (ROM) device, a random access memory (RAM) device, and at least one processor in communication with the ROM device and the RAM device. The at least one processor is programmed to receive an activation signal; retrieve, from the ROM device, data to execute an operating system; execute, on the RAM device, the operating system based on the data from the ROM device; receive a clear RAM signal; end execution of the operating system on the RAM device; and depower the RAM device such that all data on the RAM device is deleted.