Client Device Digital Fingerprint Authentication via Dynamic Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for verifying the identity of client devices accessing a network are vulnerable to unauthorized access, as they rely on easily compromised computer names, user names, or installed software, leading to potential misdirection of sensitive information.

Innovation Solution

A method that computes a unique registration ID code using a client device's network address and hardware components, generating a digital certificate and public/private key pair during initial registration, and re-computing and digitally signing this ID code for each communication session to authenticate the device's identity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If computer names, user names, or installed software are used for device identification, then the identification process is simple, but the security against unauthorized access is weak

Engineering Contradiction:
ImprovesecurityVSAvoididentification process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically generates device fingerprints by reading hardware identifiers (MAC addresses, serial numbers) and cryptographic keys from the client device without requiring user intervention. The cryptographic program autonomously computes registration ID codes and manages digital certificates, eliminating the need for users to manually configure security settings while maintaining strong security through hardware-bound identification.

Inventive Principle:
Principle #25Self-service

2Reliability

If digital certificates and cryptographic key pairs are generated for each device, then the security is strengthened, but the registration and authentication process becomes more complex

Engineering Contradiction:
ImprovesecurityVSAvoidregistration process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by pre-generating cryptographic key pairs and digital certificates during the initial registration phase. The registration program automatically creates these security credentials and stores them securely in the client device's cryptographic module, so that subsequent authentication operations can proceed efficiently without requiring repeated key generation or complex user setup procedures.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If hardware components are used to generate unique device identifiers, then the uniqueness and security are improved, but the cost and complexity of the system increases

Engineering Contradiction:
Improvedevice uniquenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses universal cryptographic algorithms and standard hardware components (network interface cards, storage devices with serial numbers) that are already present in most client devices. The cryptographic program leverages existing hardware identifiers and built-in cryptographic capabilities to generate unique device fingerprints, avoiding the need for specialized expensive hardware while maintaining strong uniqueness and security guarantees.

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

Data Source

PatentEP2115993B1Method for generating digital fingerprint
Publication Date: 2017.11.15 THE BOEING CO
  • EP2115993B1 patent drawingFigure 1
  • EP2115993B1 patent drawingFigure 2
  • EP2115993B1 patent drawingFigure 3

AI summary

A method and system for authenticating the identity of a client device that is calling a remotely located server over a network. A client device inputs information pertaining to a hardware characteristic and a network address thereof into a cryptographic hash function stored on the client device. The hash function computes a unique registration ID hash code and presents it to the system server during a registration process. The system server then generates a digital certificate having a system-side key (i.e., public key). A client-side key (i.e., private key) is provided to the client device. For all future calls to the system server, the client device re-computes its registration ID hash code and then digitally signs it using its client-side key. The system server then uses its system-side key to examine the digitally signed registration ID hash code to authenticate the identity of the client device. Since the registration ID hash code is not stored on the client device, but rather re-computed each time the client device makes a call to the system server, a high degree of security is achieved.