Electronic Certificate Security via Hardware Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for securing electronic certificates are vulnerable to copying and fraudulent use by third parties, leading to potential financial and security risks, as they rely on data that can be replicated for unauthorized access to services.

Innovation Solution

A method that involves determining a unique network identifier for each user unit during initialization, which is stored with the certificate data by the authority, and verified during operation to ensure only the legitimate owner can use the certificate, using identifiers like MAC addresses or IMEI numbers, and optionally requiring a PIN code for secure registration and use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If certificate data is stored in user unit memory without hardware binding, then ease of operation is improved (certificate can be used on any device), but security deteriorates (certificate can be copied and used by third parties)

Engineering Contradiction:
Improvecertificate usabilityVSAvoidcertificate security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The certificate security system is segmented into two independent components: the certificate data itself and the hardware identifier binding. The certificate remains in the user unit while the authority maintains a separate binding between the certificate and the hardware identifier in its database. This segmentation allows the certificate to be used on different devices (maintaining ease of operation) while the authority verifies the binding to prevent unauthorized use (maintaining security).

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authority acts as an intermediary between the user unit and service suppliers. Instead of directly binding the certificate to hardware in the user unit (which would reduce flexibility), the authority maintains the binding information centrally and verifies it during service access. This intermediary role enables both flexible certificate usage and strong security verification without requiring direct hardware-certificate binding in the user unit.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If certificate is bound to specific hardware identifier, then security is improved (prevents copying to other devices), but adaptability deteriorates (certificate cannot be used on different units)

Engineering Contradiction:
Improvecertificate securityVSAvoidcertificate portability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically manages the binding between certificates and hardware identifiers through the authority's database. The binding is not static or permanently fixed in the user unit, but can be updated, modified, or revoked by the authority as needed. This dynamic approach allows the certificate to be securely bound to specific hardware for security purposes while maintaining the flexibility to change bindings when users legitimately switch devices, thus resolving the contradiction between security and adaptability.

Inventive Principle:
Principle #15Dynamics

3Object-affected harmful factors

If hardware identifier verification is implemented, then fraud prevention is improved, but device complexity increases (requires additional verification steps)

Engineering Contradiction:
Improvefraud preventionVSAvoidverification process complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The hardware identifier verification process is designed to be self-service and automated. The user unit automatically transmits its hardware identifier to the authority during the certificate verification process, and the authority automatically checks the binding in its database. This self-service approach prevents fraud through automated verification without requiring complex manual intervention or additional user actions, thus minimizing the perceived complexity while maintaining strong fraud prevention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7958348B2Method for securing an electronic certificate
Publication Date: 2011.06.07 NAGRAVISION SA
  • US7958348B2 patent drawing
  • US7958348B2 patent drawing

AI summary

A method is for securing and verifying an electronic certificate issued by an authority to an owner. The certificate is stored in the memory of a user unit operated by the owner. The user unit transmits all or part of the data of the certificate to the authority. Further, during an initialization phase, the method includes determining, by the authority, a network identifier pertaining to the user unit, and storing, by the authority, the identifier in connection with the data of the certificate. As such, the use of an electronic certificate by individuals other than the owner may be prevented. Further, damages to the owner, in the case of the theft or copying of a certificate, may be avoided.