Mutual Authentication Flow for Sensitive Data Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authentication methods fail to ensure mutual authentication between a functional electronic device or system and its user, leading to potential security breaches when a fake device or unauthorized user interacts with sensitive or confidential data.

Innovation Solution

A method involving a preliminary device authentication phase and a user authentication phase, using secret question-and-answer processes, ensures that both the device and user are authenticated before allowing any operational phase, preventing unauthorized access and ensuring secure operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If only user authentication is performed without device authentication, then the authentication process is simple and quick, but the system cannot verify whether the device is genuine, leading to potential security breaches with fake devices

Engineering Contradiction:
Improvedevice authenticity verificationVSAvoidauthentication process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication process is divided into two independent but complementary phases: device authentication phase and user authentication phase. Each phase has its own verification mechanisms and secrets, allowing the system to verify both device and user identity separately while maintaining overall security

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Device authentication is performed as a preliminary action before user authentication. The device must first prove its authenticity using device-specific secrets stored in secure memory, establishing a trusted foundation before proceeding to user verification

Inventive Principle:
Principle #10Preliminary action

2Reliability

If mutual authentication is implemented for both device and user, then security is significantly improved, but the authentication process becomes more complex and time-consuming

Engineering Contradiction:
Improvemutual authentication securityVSAvoidauthentication duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Device authentication is performed as a preliminary action before user authentication. The device must first prove its authenticity using device-specific secrets stored in secure memory, establishing a trusted foundation before proceeding to user verification

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The device performs self-authentication by verifying its own identity credentials stored in secure memory against authentication data received from the server, eliminating the need for manual verification and reducing overall authentication time

Inventive Principle:
Principle #25Self-service

3Reliability

If authentication secrets are stored in the device, then device authentication can be performed, but the device must have secure memory protection to prevent unauthorized access to sensitive data

Engineering Contradiction:
Improveauthentication capabilityVSAvoidsecure memory requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Different types of data are stored with different security characteristics: device authentication secrets are stored in secure protected memory within the device, while user authentication data can be stored in less secure memory or transmitted dynamically, optimizing the balance between security and accessibility

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3788527B1Mutual authentication of a user-controllable device or system containing sensitive or confidential data
Publication Date: 2026.01.28 LEDGER SAS
  • EP3788527B1 patent drawingFigure 1

AI summary

Method of mutual authentication of a controllable electronic device (DE) and of its user (USER) able to control it so that it procures him a service (DS), the device (DE) containing sensitive or confidential data (DA) and being arranged so as to - in an operational phase (OP) including a preliminary step of authentication of the user (UAP) -, execute an operation (SO) so as to procure the service (DS), comprising, furthermore, a prior phase of authentication of the device (SDAP), in which the authenticity of the device (DE) is verified, so that if on completion of the prior phase of authentication of the device (SDAP), the device (DE) is confirmed to be authentic, the user (USER) can execute the operational phase (OP), whilst if the device (DE) is not confirmed to be authentic, the user (USER) can prevent the execution of the operational phase (OP).