Trust Anchor Context Verification for Embedded Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Unauthorized access to trust anchors in embedded systems can compromise the security of devices, allowing attacker applications to execute cryptographic operations, thereby impairing the security of the system.

Innovation Solution

A method and security module that integrate context information of the requesting application into the cryptographic security function, using this information as a parameter or modifying the security function's response, ensuring that only authorized applications receive the correct security values, thereby preventing unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a trust anchor is integrated into an embedded system to provide cryptographic security functions, then the security of the system is improved, but the system becomes vulnerable to unauthorized access by attacker applications that can execute arbitrary cryptographic operations

Engineering Contradiction:
ImprovesecurityVSAvoidunauthorized access
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by associating specific context information (such as application identifiers, security parameters, or runtime states) with each cryptographic operation request. This ensures that the trust anchor provides security functions tailored to the specific application context, making unauthorized operations detectable and preventable while maintaining secure functionality for authorized applications.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements feedback mechanisms by verifying context information against expected values before executing cryptographic operations. The trust anchor checks whether the requesting application has the appropriate context (such as valid security parameters or authorized identifiers) and only proceeds with the operation if verification succeeds, thereby preventing unauthorized access while allowing legitimate operations.

Inventive Principle:
Principle #23Feedback

2Reliability

If context information is integrated into cryptographic security functions to prevent unauthorized access, then security against attacker applications is improved, but the complexity of the security module increases

Engineering Contradiction:
ImprovesecurityVSAvoidsecurity module complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the security module into distinct functional components: one part responsible for receiving and verifying context information, another for executing cryptographic operations, and a third for managing security parameters. This modular structure reduces complexity by organizing functions into manageable, independent units that can be developed and verified separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the interface or driver) that mediates between applications and the trust anchor. This intermediary handles the complex tasks of context verification, parameter validation, and operation routing, thereby shielding the core cryptographic functions from complexity while maintaining security. The intermediary acts as a buffer that manages the interaction complexity without burdening the critical security core.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11106828B2Method and apparatus for providing a cryptographic security function for the operation of a device
Publication Date: 2021.08.31 SIEMENS MOBILITY GMBH
  • US11106828B2 patent drawing

AI summary

Provided is a method and apparatus for providing a cryptographic security function for the operation of a device, and to an associated computer program (product). The method for providing a cryptographic security function for the operation of a device carries out the following steps: receiving a request to provide such a security function, providing an interface to a point providing such a security function, said point being called a trust anchor, wherein said interface determines context information in accordance with the application initialing the request, providing the requested security function for the application initiating the request, wherein the determined context information influences the provision of said security function.