Firmware Image Authentication Using Hash-Based Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional security mechanisms struggle to detect subtle modifications in device images that introduce security vulnerabilities, making it difficult to maintain the security of secure operating environments.

Innovation Solution

Implement a firmware validation infrastructure with a validation server and API that calculates and compares hash values of firmware locations to detect any changes, using a database to store known hash values and trigger security responses for manipulated firmware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional security mechanisms are used to detect device changes, then reactive security responses can be provided, but subtle modifications in device images that introduce security vulnerabilities cannot be effectively detected

Engineering Contradiction:
Improvedetection precisionVSAvoidsecurity reliability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent changes the detection parameter from superficial image properties (file name, file size) to cryptographic hash values. By calculating and comparing hash values of the entire firmware image, the system can detect even single-byte modifications, thereby resolving the contradiction between detection precision and security reliability.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If firmware images are validated using hash value comparison, then even minor changes can be detected, but the complexity of the validation infrastructure increases

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidvalidation infrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-calculating and storing the expected hash value of the authentic firmware image in a database before deployment. This allows the validation server to quickly compare against the known good value without complex analysis, reducing validation infrastructure complexity while maintaining high security reliability.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If the validation server stores known hash values in a database, then authenticated firmware can be verified, but the system requires additional storage and database management infrastructure

Engineering Contradiction:
Improvefirmware verification accuracyVSAvoidinfrastructure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent uses copying by creating a cryptographic fingerprint (hash value) of the firmware image rather than storing the entire image. This copy is sufficiently precise to verify authenticity while requiring minimal storage space and infrastructure complexity, resolving the contradiction between verification accuracy and infrastructure complexity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12585786B2Authentication of device configurations for authenticated devices
Publication Date: 2026.03.24 FORTINET INC
  • US12585786B2 patent drawing
  • US12585786B2 patent drawing
  • US12585786B2 patent drawing

AI summary

Validation of a firmware image on a client device is disclosed. Information corresponding to one or more addresses of an image stored on a client device is periodically requested via an application program interface (API) configured to provide access to the image on the client device. The requested information from the image on the client device is compared with the image stored on the server image with stored validation information corresponding to a valid version of the image. An indication is generated if the information from the image on the client device does not match the stored validation information.