Device Identifier Authentication for Mobile Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current user authentication methods lack robust security measures, particularly in mobile computing devices, making them vulnerable to unauthorized access when users share or dispose of devices, and there is a need for enhanced verification processes.
Innovation Solution
Implementing a device identifier imprinted on a chip within personal computing devices that generates and verifies authentication codes, allowing users to securely associate and dissociate their identity with the device, enhancing security through code matching and disavowal processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional user authentication methods are used in mobile computing devices, then ease of operation is maintained, but security against unauthorized access deteriorates when devices are shared or disposed of
Solution Approach 1:
The system performs preliminary actions by associating the device identifier with the user account in advance during device setup. This preliminary association enables automatic authentication without requiring additional user actions during subsequent logins, thereby maintaining ease of operation while enhancing security through device-specific verification
Solution Approach 2:
The device identifier serves as an intermediary element that bridges the user account and the physical device. This intermediary enables secure authentication by verifying that the device presenting itself is the one originally associated with the account, without requiring direct user intervention beyond initial setup
2Reliability
If device identifier-based authentication is implemented, then security against unauthorized access is improved, but device complexity increases due to additional verification processes
Solution Approach 1:
The authentication verification process is extracted from the mobile device and relocated to the online system server. The device only needs to present its identifier, while the complex comparison and verification logic resides on the server side, thereby maintaining device simplicity while achieving enhanced security
Solution Approach 2:
The system uses a simplified copy of the device's unique characteristics (the device identifier) for authentication purposes, rather than requiring the device to implement complex security protocols. This copy approach enables security verification without adding complexity to the end device
3Reliability
If device identifier is permanently associated with user account, then authentication security is enhanced, but adaptability deteriorates when user sells or disposes of the device
Solution Approach 1:
The association between device identifier and user account is made dynamic rather than static. The system allows the association to be modified over time - initially created during device setup, and later dissociated when the user sells or disposes of the device. This dynamic approach maintains strong authentication security while providing necessary adaptability for device lifecycle changes
Data Source
AI summary
In particular embodiments, a computing device accesses a device identifier that is encoded in the hardware of the computing device. The device identifier is used to generate a device key that will uniquely identify the particular computing device. The computing device stores the device key in a data store, and sends the device key to be stored on a first computer server. The computing device subsequently requests a user action from a second computer server, and the second computing server requests user authentication. The computing device generates a first authentication code using a cryptographic hash algorithm and the device key, and sends the first authentication code to the second computer server. The computing device is authenticated based on a second authentication code generated by the first computer server using the device key.