Network Device Access Control via Ultra-Narrow Band Radio Token
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current access control methods for network devices, relying on passwords or user certificates, are insecure and complex to manage, particularly vulnerable to 'man in the middle' attacks and do not effectively address authorization issues, leading to difficulties in protecting against illegitimate access.
Innovation Solution
A system utilizing an ultra-narrow band radio connection for secure communication between a network device, a control device, and an authentication server, where an access token is directly delivered to the network device for immediate authentication and authorization, using encryption and signatures to protect against interception and replay attacks, and a server-side hardware security chip for secure storage and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If passwords are used for access control, then ease of operation is improved, but security is worsened
Solution Approach 1:
The access control system is segmented into multiple independent components: a first security medium (password/certificate) for initial authentication and a second security medium (hardware token) for generating one-time passwords. This segmentation allows each component to have specialized security functions, combining the ease of password entry with the security of hardware-based one-time passwords.
Solution Approach 2:
A server acts as an intermediary between the user device and network device. The server receives the one-time password from the user device, verifies it against the stored value, and then grants access rights. This intermediary architecture centralizes security management and prevents direct exposure of security credentials between client devices.
2Reliability
If user certificates are used for access control, then security is improved, but device complexity is worsened
Solution Approach 1:
The complex certificate verification and management functions are extracted from the network device and集中ized in a dedicated server. The network device only needs to receive access rights from the server, while the server handles certificate validation, one-time password generation, and security token management. This extraction reduces the complexity burden on individual network devices.
Solution Approach 2:
The server is designed as a universal security management platform that can handle multiple authentication methods (passwords, certificates, hardware tokens) and provide centralized security management for multiple network devices. This multi-functionality consolidates what would otherwise require separate systems into a single unified platform.
3Ease of operation
If centralized Authentication Server is used, then ease of operation is improved, but vulnerability to man in the middle attacks is worsened
Solution Approach 1:
Instead of using static passwords or long-term certificates, the system implements periodic authentication using one-time passwords that are generated and consumed in each authentication session. The one-time password changes with each access request, making intercepted credentials immediately useless for future attacks. This periodic regeneration of credentials fundamentally undermines man-in-the-middle attack effectiveness.
Solution Approach 2:
The server generates a copy of the one-time password and stores it securely for verification, while the user device receives and uses the original copy for authentication. This copying mechanism allows the server to verify credentials without exposing the actual security secrets, and the use of ephemeral one-time passwords ensures that even if copies are intercepted, they cannot be reused.
4Ease of operation
If server-side certificate is compromised, then security is worsened, but management burden is improved through centralized control
Solution Approach 1:
When a security compromise is detected or a user leaves the organization, the system can immediately discard (invalidate) the affected user's access rights and one-time password generation capability on the server side. The user's hardware token remains intact and can be recovered or reassigned to a new user account, eliminating the need to physically retrieve or destroy tokens. This approach combines centralized control efficiency with security hardening.
Data Source
Figure 1
Figure 2
AI summary
For an access control to a network device (ND) from a user device (UD), the network device (ND): receives a request (ReqA) containing an identifier (IdU) of the user device, a one-time password (OTP) and an access request from the user device (UD), transmits another request (ReqC) to a control device (CD), said another request (ReqAT) containing the identifier (IdU) of the user device and an identifier (IdND) of the network device, the control device (CD) being able to transmit said another request (ReqAT) through an ultra narrow band radio connection to an authentication server (AS) that grants access rights attributed to the user device for the network device by checking the identifier (IdU) of the user device and the identifier (IdND) of the network device, and being able to receive an access token encrypted with the one-time password (OTP) and containing granted access rights from the authentication server (AS) through an ultra narrow band radio connection, receives the access token from the control device (CD), decrypts the access token with the one-time password (OTP) to apply the granted access rights attributed to the user device.