Embedded Controller Security Credential Derivation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Electronic devices face vulnerabilities to unauthorized access, particularly due to malware or users attempting to access sensitive information like wireless network passwords or encryption keys, which can be inconvenient for users and increase complexity with existing key derivation techniques.

Innovation Solution

An embedded controller generates a security credential, such as an encryption key, using one-time programmable information that is inaccessible to the processor, allowing secure data protection without user input, by deriving and transmitting the credential securely to program code for encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing key derivation techniques are used, then security credentials can be generated, but user inconvenience and system complexity increase

Engineering Contradiction:
Improvesecurity credential generationVSAvoiduser input requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The embedded controller automatically generates security credentials using one-time programmable information stored in its own memory, without requiring user input. The system serves itself by deriving encryption keys from OTP data that is inherently available to the controller, eliminating the need for manual credential entry or complex key derivation workflows that require user interaction.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent extracts the security credential generation function from the main processor to a dedicated embedded controller. This separation allows the embedded controller to independently manage one-time programmable information and generate security credentials without involving the user or complicating the main system architecture, thereby reducing user inconvenience while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If existing key derivation techniques are used, then security credentials can be generated, but system complexity increases

Engineering Contradiction:
Improvesecurity credential generationVSAvoidkey derivation system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional components: the embedded controller handles one-time programmable information storage and security credential generation, while the main processor handles other system functions. This segmentation simplifies the overall system architecture by dedicating specific security functions to a specialized component, reducing the complexity burden on the main processor and creating a cleaner system division of labor.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The embedded controller independently performs security credential generation using its own stored one-time programmable information, without requiring complex external key derivation systems. This self-service capability reduces system complexity by eliminating the need for elaborate key management infrastructure, external authentication servers, or complex cryptographic coordination between multiple components.

Inventive Principle:
Principle #25Self-service

3Reliability

If one-time programmable information is used for credential generation, then security is enhanced, but information accessibility is restricted

Engineering Contradiction:
Improvedata protectionVSAvoidinformation accessibility
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The embedded controller acts as an intermediary between the one-time programmable information and the security credential generation process. It securely accesses the OTP data stored in its own memory space, derives encryption keys without exposing the raw OTP information to the main processor or other system components, and provides the necessary security credentials to protected applications. This intermediary role enables data protection while maintaining controlled accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11418335B2Security credential derivation
Publication Date: 2022.08.16 HEWLETT PACKARD DEVELOPMENT COMPANY LP
  • US11418335B2 patent drawing
  • US11418335B2 patent drawing
  • US11418335B2 patent drawing

AI summary

In some examples, a device includes a memory, a processor, and a controller separate from the processor to derive a security credential based on information comprising a key accessible by the controller. The controller communicates the derived security credential in a secure manner to a program code executable on the processor, and uses the derived security credential to protect data stored in the memory against unauthorized access.