IoT Bootstrap Using Signed Public Key Certificates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional bootstrap processes for IoT devices pose a security risk by transferring private keys from a bootstrap server to the device, which can be intercepted, allowing unauthorized access to the network.

Innovation Solution

A secure bootstrap mechanism that avoids generating and distributing private keys, instead using a digitally signed public key certificate verified by the server to authenticate the device, ensuring secure communication without exposing the private key.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If private keys are transferred from bootstrap server to device, then device authentication is enabled, but security risk increases due to potential key interception

Engineering Contradiction:
Improvedevice authenticationVSAvoidsecurity risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the private key from the authentication process entirely. Instead of transferring private keys to devices, the system uses public key certificates that are signed by the bootstrap server. The device only needs to store and present its public key certificate, while the private key remains securely stored on the bootstrap server, eliminating the security risk of key interception during transfer.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a public key certificate as an intermediary between the device and the authentication system. The certificate serves as a mediator that proves the device's identity without requiring the private key to be transferred. The bootstrap server signs the device's public key to create this certificate, which then acts as the authentication credential.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If private key transfer is implemented, then device registration is completed, but network security is compromised

Engineering Contradiction:
Improvedevice registrationVSAvoidunauthorized access
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent removes the private key transfer step from the device registration process. The registration is completed using only public key certificates, which contain no sensitive information that could enable unauthorized access. The private key never leaves the bootstrap server, eliminating the vulnerability to interception while maintaining registration functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses public key certificates as disposable authentication credentials. These certificates can be freely distributed to devices during registration without compromising security, as they contain only public information. If a certificate is compromised, it can be revoked and a new one issued, unlike private keys which must be kept secret indefinitely.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Adaptability or versatility

If private keys are distributed to devices, then authentication capability is provided, but key interception becomes possible

Engineering Contradiction:
Improveauthentication capabilityVSAvoidprivate key confidentiality
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent extracts the confidential private key from the authentication capability provision process. Devices receive only public key certificates, which provide full authentication capability without containing any confidential information. The private key remains exclusively on the bootstrap server, maintaining its confidentiality while devices still gain robust authentication capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses copies of the public key (in certificate form) instead of the original private key for authentication. Multiple devices can receive identical or different public key certificates without affecting the security of the original private key. These certificates are safe to distribute widely as they contain no secret information that could be exploited.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10885198B2Bootstrapping without transferring private key
Publication Date: 2021.01.05 ARM LTD
  • US10885198B2 patent drawing
  • US10885198B2 patent drawing
  • US10885198B2 patent drawing

AI summary

A machine implemented method of communication between server and remote device, the method comprising: determining an availability and address of the remote device on a network for communication with the server; obtaining a public key attributed to the remote device; signing the public key attributed to the remote device with a private key of the server and so generating a digitally signed certificate to verify the ownership of the public key as the remote device; and transmitting the digitally signed certificate to the remote device.