Intermediate Device Authentication Using Segmented Key Codes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data mule systems lack secure authentication mechanisms for communications connections between servers and remote terminals when using intermediate devices, particularly in scenarios where the intermediate device is not under the control of the WSN operator, risking security breaches if credentials are shared widely.
Innovation Solution
A method involving the server generating and transmitting key codes derived from a shared secret, allowing the remote terminal and intermediate device to verify each other's authenticity without sharing the secret, ensuring secure data transmission and preventing unauthorized access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data mules use shared credentials to authenticate with WSN nodes, then authentication capability is improved, but security risk increases due to potential credential exposure
Solution Approach 1:
The shared secret is segmented into two separate key codes through a one-way hash function. The server retains the original shared secret, while the data mule receives only the hashed key codes. This segmentation allows the data mule to authenticate with WSN nodes without having access to the actual shared secret, thus maintaining authentication capability while reducing security risk.
Solution Approach 2:
The server generates key codes that are functional copies of the shared secret's authentication capability. These key codes are derived from the shared secret through cryptographic hashing, allowing them to serve the same authentication purpose without being identical to or reversible from the original secret. This enables secure distribution of authentication credentials.
2Productivity
If multiple mules are deployed to collect data from remote terminals, then data collection efficiency is improved, but credential management complexity increases
Solution Approach 1:
The key code generation mechanism is designed to be universal and stateless. The server can generate key codes for any data mule on demand without requiring pre-provisioning or complex credential distribution. Any mule can obtain valid key codes by requesting them from the server, enabling multiple mules to operate independently with the same authentication mechanism.
Solution Approach 2:
Data mules can autonomously obtain their authentication key codes by requesting them from the server. The server automatically generates and provides key codes to mules without requiring manual credential distribution or complex setup procedures. This self-service approach simplifies credential management as mules deploy themselves without administrative overhead.
3Reliability
If key codes are transmitted from server to intermediate device, then authentication verification is enabled, but communication overhead increases
Solution Approach 1:
The key codes are generated and transmitted from the server to the data mule in advance, before the actual data collection process begins. This preliminary authentication setup allows the mule to immediately verify WSN node credentials without requiring real-time server communication during data collection, reducing communication overhead during operational phases.
Data Source
AI summary
An intermediate data transmission device arranges for mutual authentication between itself and a remote terminal to allow data to be exchanged between the remote terminal and a server through the device. The server sends first and second key codes to the intermediate device, the key codes both being derived from a shared secret known to the server and remote terminal but not to the intermediate device. In response to a challenge from the intermediate device the remote terminal uses the shared secret to generate a duplicate of the first key code and transmits the duplicate to the intermediate device. The intermediate device compares the first key code and the duplicate of the first key code received respectively from the server and the remote terminal to verify the authenticity of the remote terminal. The intermediate device then transmits the second key code to the remote terminal, to be compared by the remote terminal with a duplicate of the second key code to verify the authenticity of the intermediate device. This process allows the intermediate device to be used without itself having the shared secret. The codes generated by the server may be encoded with a network identity of the intermediate device using the shared secret, such that the remote terminal can only respond to the same intermediate device that transmitted the codes. This prevents a “man-in-the middle” attack by another intermediate device, as without the shared secret no intermediate device can modify the codes to include a different network identity.