Blockchain Device Authentication via Cryptographic Challenge
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for a secure system and method to authenticate devices that can perform actions on behalf of a user, particularly in the context of increasing numbers of intelligent devices connected to the internet, which poses new security challenges.
Innovation Solution
A blockchain-based authentication system and method using a processor to enable a second device to perform actions on a first device on behalf of a user, involving the creation and use of a blockchain-compatible public-private key pair, trust certificates signed with a user private key, and cryptographic challenges to verify device authenticity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods are used for device connectivity, then device integration is simple, but security against unauthorized access is insufficient
Solution Approach 1:
The system performs preliminary authentication actions by establishing trust relationships before devices interact. Trust certificates are pre-configured in the blockchain, and device identities are registered in advance, enabling secure authentication before actual device operations occur.
Solution Approach 2:
The blockchain serves as an intermediary layer between devices, mediating authentication and trust verification. Instead of direct device-to-device authentication, the blockchain acts as a neutral mediator that verifies identities and manages trust relationships, enhancing security while maintaining system organization.
2Reliability
If blockchain-based authentication with cryptographic challenges is implemented, then device authentication security is improved, but communication overhead and processing time increase
Solution Approach 1:
The system uses cryptographic challenges selectively rather than for all authentication scenarios. For established trust relationships, the system can use simplified verification, while cryptographic challenges are applied when needed to verify device identity or prevent replay attacks, balancing security with efficiency.
3Reliability
If hardware-based cryptographic processors are used for key management, then key security is improved, but device cost and manufacturing complexity increase
Solution Approach 1:
The hardware-based cryptographic processor is designed to perform multiple functions including key generation, signing operations, and verification. This multi-functionality reduces the need for separate dedicated hardware components, thereby reducing overall device complexity and manufacturing costs while maintaining strong security.
Data Source
AI summary
An embodiment herein provides a processor implemented method for blockchain-based device authentication by a user device to enable a second device to perform an action on a first device on behalf of a user linked to the user device, based on a command received from the second device. The method includes the steps of: (i) obtaining an identify information associated with an identity document of the user; (ii) storing the identity information, and a set of credentials, with a blockchain to link the identity information with the set of credentials for the user; (iii) signing a first trust certificate by a user private key on the blockchain to obtain a first signed trust certificate; and (iv) signing a second trust certificate by the user private key on the blockchain to obtain a second signed trust certificate. The first device receives the second trust certificate from the second device when the first device receives the command from the second device. The first device communicates a cryptographic challenge using a public key of the second device, to the second device. The second device transmits a response to the cryptographic challenge to the first device. The first device checks, using the public key of the second device, whether the response matches with a predetermined correct response or not, and the first device authenticates the second device and executes the command received from the second device only if the response matches with the predetermined correct response.