Security Data Processing Device for Anti-Cloning IoT Programming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the production of programmable devices, such as IoT devices, there is a challenge in ensuring that only the agreed-upon number of devices are programmed with secret information like cryptographic keys and digital certificates, as existing Hardware Security Modules (HSMs) do not have the capability to check programming requirements before programming, leading to the risk of producing cloned devices.

Innovation Solution

A security data processing device that acts as a Hardware Security Module (HSM) or similar processing device, which enforces digital documents containing programming requirements, ensuring that only the specified number of devices are programmed and adheres to contractual terms, including time limits and configuration options, while securely storing and managing cryptographic keys and providing signed reports for verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If the factory controller is given access to secret information for programming, then the programmable devices can be programmed, but the risk of producing cloned devices increases

Engineering Contradiction:
Improveprogramming capabilityVSAvoidanti-cloning security
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The secret information is segmented into multiple parts: a first part is stored in the HSM, and a second part is provided to the factory controller. This segmentation ensures that the factory controller cannot obtain complete secret information to produce cloned devices, while still having sufficient information to program legitimate devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The HSM acts as an intermediary between the OEM and the factory controller. It verifies programming requests against contractual terms and only releases the second part of secret information when requirements are met, preventing unauthorized cloning while enabling legitimate programming.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the factory controller is given unrestricted access to secret information, then programming can be performed without limitations, but cloned devices can be produced beyond the agreed number

Engineering Contradiction:
Improveprogramming throughputVSAvoidcloned device production
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The HSM performs preliminary verification of programming requests against stored contractual terms before releasing secret information. This includes checking the number of devices programmed, time limits, and other requirements, preventing over-programming before it occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the HSM monitors programming activities and compares them against contractual requirements. When limits are approached or exceeded, the HSM stops releasing secret information, providing real-time control over device production numbers.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If multiple intermediaries are involved between the OEM and factory controller, then more parties can be accommodated, but authentication complexity increases

Engineering Contradiction:
Improveproduction chain flexibilityVSAvoidauthentication system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The HSM serves multiple functions: it stores contractual terms, verifies programming requests, manages secret information distribution, and provides audit trails. This multi-functionality simplifies the overall system architecture despite involving multiple intermediaries, as the HSM handles all authentication and authorization centrally.

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

Data Source

PatentEP4113346B1Security data processing device
Publication Date: 2024.03.20 SECURE THINGZ
  • EP4113346B1 patent drawingFigure 1
  • EP4113346B1 patent drawingFigure 2
  • EP4113346B1 patent drawingFigure 3

AI summary

A security data processing device comprising a processor and a memory coupled to the processor, the processor configured to: receive a digital document, said digital document comprising at least one primary programming requirement specified by a first party for programming at least one programmable device; determine if there is a record stored in the memory that corresponds to the digital document; receive a programming request from a programming module of a programming machine in communication with said processor, said programming request requesting the programming of the at least one programmable device; determine if the programming request complies with the at least one primary programming requirement in the digital document; and wherein if said programming request complies with the at least one primary programming requirement in the digital document and if there is no record stored in the memory that corresponds to the digital document, the processor is further configured to: output programming information to the programming module for programming the at least one programmable device; and permanently store a further record in the memory, wherein the further record corresponds to said digital document.