Functional Security Firmware Version Control With Signed Allowlists

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing firmware management systems for functional security components in electrical devices are complex and require specialized knowledge for updates, making it difficult for non-experts to manage firmware versions securely and efficiently.

Innovation Solution

A method for managing firmware versions using cryptographic signatures and non-volatile memory to ensure only authorized firmware updates are applied, with a firmware list that cannot be manipulated, allowing updates to be performed by non-specialist users using standard tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware updates require specialized knowledge and complex management systems, then security and reliability are improved, but ease of operation deteriorates

Engineering Contradiction:
Improvefirmware update securityVSAvoidfirmware update complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a firmware list as an intermediary data structure that mediates between the firmware update process and the security verification system. This firmware list contains pre-approved firmware version information and acts as a reference that simplifies the update process while maintaining security through automated verification against the list, eliminating the need for specialists to manually verify firmware authenticity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The functional security component is designed to autonomously verify firmware authenticity and manage update permissions without requiring external specialist intervention. The component automatically checks firmware signatures, validates against the firmware list, and controls the update process itself, enabling non-experts to perform updates safely while maintaining high security standards.

Inventive Principle:
Principle #25Self-service

2Reliability

If strict firmware authorization checks are implemented, then device security is improved, but productivity deteriorates due to additional verification steps

Engineering Contradiction:
Improvedevice securityVSAvoidfirmware update speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-populating the firmware list with authorized firmware version information before the update process begins. This pre-prepared reference data allows for rapid verification during the actual update process, as the system can quickly check against the pre-validated list rather than performing complex analysis in real-time, thus maintaining security while improving update speed.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If firmware lists are stored in non-volatile memory, then reliability against manipulation is improved, but device complexity increases

Engineering Contradiction:
Improvefirmware list integrityVSAvoidmemory management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the firmware list storage with the existing non-volatile memory infrastructure of the functional security component. Rather than introducing a separate secure storage system, the firmware list is integrated into the existing memory architecture, combining the integrity requirements of the firmware list with the proven reliability of the device's non-volatile memory, thus maintaining security without significantly increasing overall device complexity.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260111551A1Method for Managing Firmware Versions for Functional Security Components, and Electric Device
Publication Date: 2026.04.23 LENZE SE
  • US20260111551A1 patent drawing

AI summary

A method for managing firmware versions for functional security components includes the steps of: transmitting a firmware packet to a functional security component, wherein the firmware packet has a signature and a firmware list which has a firmware list version number, and the firmware list includes permissible firmware version numbers; checking the author of the firmware packet by means of the functional security component using the signature; if the author is a permissible author, using the functional security component to check whether no firmware list is stored in a non-volatile storage region of the functional security component or if a firmware list which has an older firmware list version number than the firmware list version number of the transmitted firmware list is stored in the non-volatile storage region; and when no firmware list is stored or when a firmware list which has an older firmware list version number is stored, storing the transmitted firmware list or overwriting the firmware list having the older firmware list version number with the transmitted firmware list.