Secure Memory Transaction Unit Key Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer systems lack effective security measures to protect data from passive and active attacks, particularly in microprocessor-based systems where memory and processors share a circuit board, leading to potential illicit access and tampering.

Innovation Solution

A Secure Memory Transaction Unit (SMTU) is introduced, which uses unique encryption keys for each memory location and incorporates a global write counter to ensure that data is encrypted differently for each transaction, providing high security by changing keys with every write operation and authenticating data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single encryption key is used for all memory locations, then the system is simpler to implement, but security is compromised as adversaries can access all locations once they break the key

Engineering Contradiction:
Improvedata securityVSAvoidkey management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the encryption key into multiple independent segments, with each memory location having its own unique key. This segmentation ensures that compromising one key does not affect other locations, directly resolving the contradiction between security reliability and key management complexity by making the complexity manageable through modular design

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each memory location is assigned a unique encryption key tailored to its specific requirements, rather than using a uniform key for all locations. This local quality approach enhances security at each location while maintaining overall system manageability through systematic key assignment

Inventive Principle:
Principle #3Local quality

2Reliability

If the same encryption key is used for multiple write operations to the same location, then the system is simpler to operate, but security is weakened as patterns can be detected

Engineering Contradiction:
Improvedata protection against pattern analysisVSAvoidwrite operation complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The encryption key is dynamically changed for each write operation to the same memory location. The key evolution function generates a new key based on the previous key and operation counter, creating a dynamic security mechanism that prevents pattern detection while maintaining operational flow through automated key generation

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements periodic key changes for each write operation, using the operation counter to generate successive keys. This periodic action ensures that even repeated writes to the same location use different keys, preventing security weaknesses while maintaining systematic operation

Inventive Principle:
Principle #19Periodic action

3Reliability

If data is read and rewritten with new keys for each write operation, then security is enhanced, but transaction speed is reduced

Engineering Contradiction:
Improvedata integrity and securityVSAvoidmemory transaction speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs a read operation before each write to retrieve the current data, then uses this data in conjunction with the new key to create the encrypted write. This preliminary action ensures data integrity and proper key usage while enabling efficient read-modify-write operations that maintain security without excessive speed loss

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the encryption key parameter for each write operation while maintaining the read-modify-write transaction structure. This parameter change approach enhances security through key variation while preserving transaction efficiency by maintaining the established operational flow

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8843767B2Secure memory transaction unit
Publication Date: 2014.09.23 THE BOEING CO
  • US8843767B2 patent drawing
  • US8843767B2 patent drawing
  • US8843767B2 patent drawing

AI summary

A method for providing security for plaintext data being transferred between units in a computer system includes steps of dividing a memory into a series of addressable locations, each of the addressable locations having an address at which can be stored version information, a data authentication tag, and ciphertext corresponding to the plaintext. The system retrieves the ciphertext, the version information, and the data authentication tag, and generates encryption keys for decrypting the information stored at the address. If the data authentication tag indicates the plaintext data are valid, then the system provides the decrypted plaintext to the requestor, or encrypts new plaintext data and stores the corresponding ciphertext with new authentication and version information at the first address.