Processor Module Initialization with SCM Swap Authentication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In computing environments, the swapping of security control modules (SCMs) between different processor modules (HPMs) can lead to unauthorized access and security breaches, as existing protocols like OCP do not ensure trust between these modules, making it difficult to detect and prevent unauthorized actions.

Innovation Solution

Implementing a secure initialization process that verifies the authenticity of the SCM by comparing authentication keys generated during a binding process, ensuring that the same SCM is used for initialization, and preventing initialization if a swap is detected.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If security control modules are allowed to be swapped between processor modules for flexibility and resource sharing, then adaptability improves, but security and reliability deteriorate due to unauthorized access risks

Engineering Contradiction:

ImproveflexibilityVSAvoidsecurity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary binding between the security control module and processor module before allowing swaps. Authentication keys are generated and stored in advance during the binding process, enabling subsequent verification to detect unauthorized swaps while still permitting legitimate flexibility in module configuration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback through authentication key verification after each swap attempt. The security control module checks whether the authentication key matches the expected value, providing immediate feedback on whether the swap is authorized, thus maintaining security while allowing controlled adaptability.

Inventive Principle:

Principle #23Feedback

2Reliability

If authentication key verification is implemented to detect SCM swaps, then security improves, but device complexity increases due to additional verification protocols

Engineering Contradiction:

ImprovesecurityVSAvoidcomplexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The authentication verification functionality is extracted into a separate security control module, isolating the complex verification logic from the main processor module. This allows the verification protocol to be implemented without complicating the core processing architecture.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The security control module acts as an intermediary between the processor module and the verification protocol. It handles the authentication key generation, storage, and verification processes, shielding the main system from the complexity of security protocols while maintaining strong security guarantees.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250350459A1Processor module initialization based on authentication key generation at a security module

Publication Date: 2025.11.13 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In some examples, a first security module includes a connector interface to removably connect to a processor module. The first security module includes a controller that retrieves information stored at the processor module, the information set by a second security module when binding the second security module with the processor module. The controller reads a first authentication key from a memory of the first security module, and computes a second authentication key based on the information retrieved from the processor module. The controller determines whether to allow an initialization of the processor module based on the first authentication key and the second authentication key.