Tamper-Resistant Mutual Authentication for M2M Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods for machine-to-machine devices, particularly in electric vehicle charging scenarios, are inadequate in providing tamper-resistant and scalable solutions, leading to vulnerabilities in secure vehicle-to-grid communications and potential cyber-attacks that threaten grid stability and safety.
Innovation Solution
A tamper-resistant and scalable mutual authentication framework (TSAF) is introduced, utilizing an authentication token and a key obfuscation block to protect client devices, which enables stateless authentication and mobility support, eliminating the need for external databases and reducing reliance on expensive PKI certificates, thereby enhancing security and scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods are used for machine-to-machine devices, then device compatibility and ease of operation are maintained, but security against tamper attacks and cyber-attacks is insufficient
Solution Approach 1:
The authentication framework is segmented into distinct functional components: a key obfuscation block embedded in the client device for secure key storage and session key computation, an authentication server for issuing tokens and verifying authentication, and an application server for resource access control. This segmentation allows each component to specialize in specific security functions, improving overall security without requiring complete system redesign.
Solution Approach 2:
The patent introduces an authentication server as an intermediary between the client device and application server. This intermediary handles the complex authentication logic, issuing tokens that the client device can use for resource access. The intermediary approach centralizes security management, reducing the burden on individual devices while maintaining strong security credentials.
2Adaptability or versatility
If scalable authentication solutions are implemented to support large numbers of devices, then system capacity increases, but security against physical attacks and tampering may be compromised
Solution Approach 1:
The key obfuscation block is pre-configured with cryptographic keys and authentication credentials during device manufacturing or initial provisioning. This preliminary setup ensures that security credentials are established before the device enters service, allowing for secure authentication from day one without requiring ongoing security management infrastructure for each individual device.
Solution Approach 2:
The client device's key obfuscation block autonomously computes session keys using stored cryptographic material and received challenges, without requiring external assistance or continuous connection to security infrastructure. This self-service capability enables each device to independently maintain strong security credentials, supporting scalable deployment across numerous devices while preserving tamper-resistance.
3Reliability
If external databases and PKI certificates are used for authentication, then device verification is possible, but system cost and infrastructure requirements increase
Solution Approach 1:
The patent extracts the essential authentication verification capability from complex external infrastructure (databases and PKI certificates) and embeds it directly in the client device through the key obfuscation block. By taking out only the necessary cryptographic verification functions and placing them in the device, the system maintains strong authentication verification while eliminating dependence on expensive external infrastructure.
Solution Approach 2:
The system uses short-lived session tokens instead of long-term PKI certificates for authentication. These tokens are computationally inexpensive to generate and verify, replacing the need for expensive certificate management infrastructure. The tokens have limited validity periods, providing security without requiring costly long-term credential management systems.
Data Source
AI summary
An authentication request message is sent from a first computing device to a second computing device, wherein the first computing device and the second computing device communicate via a machine-to-machine communication protocol, and wherein the authentication request comprises a token issued by the second computing device and stored in a key obfuscation block of the first computing device. A challenge message is received at the first computing device from the second computing device. In response to the challenge message, a session key is computed at the key obfuscation block of the first computing device, wherein the session key is computed based on a secret shared between the first computing device and the second computing device. Upon generating the session key, the first computing device extracts a value from the challenge message and generates an authentication delegate based on the extracted value. The authentication delegate is sent from the first computing device to a third computing device for verification to allow the first computing device access to the third computing device.