IoT Device Onboarding via Hardware Token Whitelisting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enrolling connected devices into a management system is difficult and time-consuming, especially for devices without user interfaces, and poses security risks due to the need for similar usernames and passwords, and the potential for insecure remote access.
Innovation Solution
A method involving loading a management agent onto devices, receiving inventory information, and using a whitelist mechanism for secure onboarding, where devices can be authorized and managed without requiring unique configurations or enabling SSH ports, using hardware tokens for authentication and allowing whitelisting from any location.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional enrollment process is used for connected devices, then administrator can manage devices, but enrollment becomes difficult and time-consuming for devices without user interfaces
Solution Approach 1:
The connected device performs self-enrollment by automatically sending a enrollment request to the management server upon booting, eliminating the need for manual administrator intervention. The device uses its hardware identifier for automatic identification and enrollment, transforming a manual process into an automated self-service operation.
Solution Approach 2:
The device is pre-configured with a hardware identifier during manufacturing. This preliminary action ensures that when the device is deployed and boots up, it can immediately initiate the enrollment process without requiring any preliminary manual setup or configuration by the administrator.
2Reliability
If administrator creates unique names and passwords for each device, then security is improved, but enrollment complexity and time increase
Solution Approach 1:
Instead of administrators manually creating credentials, the system uses the device's inherent hardware identifier as its authentication credential. The device automatically presents this identifier during enrollment, and the management server uses it to authenticate and enroll the device, eliminating manual credential creation entirely.
Solution Approach 2:
The hardware identifier serves as a unique copy of the device's physical identity that can be electronically transmitted and used for authentication. This replaces the need for manually created usernames and passwords with an automated identification process based on the device's inherent hardware characteristics.
3Ease of operation
If SSH port is enabled for remote access, then administrator can access device remotely, but device becomes vulnerable to connections from any source
Solution Approach 1:
The management server acts as an intermediary between the administrator and the connected device. Instead of allowing direct SSH access to the device, all management operations are routed through the server, which authenticates requests and manages the connection, eliminating direct exposure of the device to external access attempts.
Solution Approach 2:
The SSH capability is extracted from the connected device and relocated to the management server. The device no longer needs to have SSH enabled for remote access, as all remote management operations are performed through the server's interface, removing the security vulnerability from the device itself.
Data Source
AI summary
Examples described herein include systems and methods for onboarding a device into a management system. An example method can include loading a management agent onto the device and receiving inventory information for the device. The example method can further include receiving a request to whitelist the device. In some examples, the request originates from a different device, such as a device used by a technician installing the connected device. The management server can authorize the device and add it to the whitelist. After authorizing the device, the management server can onboard the device by sending management information to the management agent on the device. The management server can then exercise management control of the device through the management agent installed on the device.