Lockable Hardware Register for Secure System State Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing systems face vulnerabilities during initialization due to susceptibility to glitching and buffer overflow attacks on system state data stored in volatile memory, which can lead to unauthorized access.

Innovation Solution

Storing system state data in a lockable hardware register with at least one lockable until reset bit, allowing the data to be locked until the next system reset, and verifying its contents to detect fault conditions, thereby enhancing security against malicious attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If system state data is stored in volatile memory (SRAM) during initialization, then the system can access and modify the data freely, but the system becomes vulnerable to glitching attacks, data replacement attacks, and buffer overflow attacks

Engineering Contradiction:
Improvedata accessibilityVSAvoidsecurity vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent divides the storage system into two separate components: a lockable hardware register for secure storage of system state data and volatile memory (SRAM) for temporary storage during processing. This segmentation allows the system to maintain both security and operational accessibility by storing data in different locations with different access characteristics

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The lockable hardware register acts as an intermediary between the volatile memory and the system's security-critical operations. During initialization, data flows from volatile memory to the lockable register, which then protects the data until reset. This intermediary structure prevents direct attacks on the system state data while maintaining necessary access during the initialization process

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If system state data is stored in a lockable hardware register, then security against attacks is enhanced, but the system requires additional hardware components and complexity

Engineering Contradiction:
Improvesecurity resistanceVSAvoidhardware structure
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The lockable hardware register is designed to serve multiple functions: storing system state data during initialization, protecting against glitching attacks, preventing data replacement attacks, and providing a secure storage mechanism that persists until reset. By making this single component multi-functional, the patent reduces the need for multiple separate security mechanisms

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If the hardware register is lockable until reset, then attackers cannot modify the data during operation, but the system cannot update the data without a full reset

Engineering Contradiction:
Improvedata integrityVSAvoiddata update flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions during the initialization phase by storing system state data in the lockable hardware register before normal operation begins. This preliminary storage ensures that critical initialization data is protected from modification during subsequent operations, while the locking mechanism is deliberately designed to release only on reset to maintain integrity

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20230237156A1System and method for storing system state data in a hardware register
Publication Date: 2023.07.27 INFINEON TECHNOLOGIES AMERICAS CORP
  • US20230237156A1 patent drawing
  • US20230237156A1 patent drawing
  • US20230237156A1 patent drawing

AI summary

One or more computing devices, systems, and/or methods are provided. In an example, a method comprises executing an application image to initialize a computing system. System state data associated with the initializing of the computing system is stored in a hardware register having at least one lockable until reset bit. A fault condition is identified responsive to the system state data not matching an expected value.