Device Fingerprint Authenticated Encryption Key Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current encryption standards like SSL/TLS and HTTPS require costly key management and authentication mechanisms, especially for mobile devices, and expose data security risks when switching from HTTPS to HTTP, as they involve heavy key management and overhead, and do not effectively utilize device fingerprints for client authentication.
Innovation Solution
A method involving a user computing device sending a device fingerprint to a root secret server to calculate a device secret code, which is used to generate a data key for encrypting and decrypting data, with the encrypted data packet encoded with the device fingerprint, application name, and timestamp, allowing for lightweight key management and authentication based on device fingerprints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SSL/TLS or HTTPS encryption standards are used to protect data transmission, then data security is improved, but key management complexity and operational overhead increase significantly
Solution Approach 1:
The patent extracts the key management burden from the server side by using device fingerprints to generate keys locally on client devices. The server only needs to store and manage device fingerprint templates, while actual encryption keys are derived client-side through biometric authentication, eliminating the need for complex server-side key distribution and storage infrastructure.
Solution Approach 2:
Each client device performs self-service key generation and management using its own device fingerprint and biometric data. The device autonomously derives encryption keys without requiring server intervention for key distribution, reducing server operational overhead while maintaining strong security through device-specific key generation.
2Reliability
If client authentication is implemented using account and password verification or security tokens, then server authentication of client is improved, but ease of deployment and key management deteriorates
Solution Approach 1:
The system uses device fingerprints and biometric data that are inherently present on each client device to perform self-service authentication. No external authentication infrastructure, account management systems, or token distribution mechanisms are needed, as each device authenticates itself using its own unique biological and hardware characteristics.
Solution Approach 2:
The patent changes the authentication parameter from traditional account/password or token-based systems to biometric and device fingerprint-based parameters. This transformation enables more secure and easier-to-deploy authentication by leveraging immutable biological characteristics and device-specific hardware identifiers that cannot be easily replicated or compromised.
3Reliability
If HTTPS is used to encrypt all transport-layer traffic, then data protection is improved, but network overhead and processing load increase
Solution Approach 1:
The patent applies encryption selectively based on data sensitivity rather than encrypting all transport-layer traffic. Sensitive data is encrypted using device-specific keys derived from fingerprints, while non-sensitive data can be transmitted in plaintext. This localized approach to encryption reduces overall network overhead and processing requirements compared to universal HTTPS encryption.
Data Source
AI summary
A method and system for encryption and decryption. The system includes a user computing device, a root secret server, and a backend server. The root secret server has a root secret code, and when receiving a fingerprint of the user computing device, calculates a device secret code for that device using the fingerprint. When sensitive data needs to be encrypted, the user computing device calculates a data key for the data based on the device secret code and the data information, and encrypts the data. The backend server retrieves the root secret code from the root secret server, and in response to receiving the encrypted data, retrieves data information and calculates the data key to decrypt the data. Similarly, the backend server can encrypt data and the user computing device can decrypt data. The root secret code, the device code, and the data key form a three level encryption mechanism.