Fully Encrypted Repository With Decentralized ECC Key Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing online transaction systems lack robust security measures to protect user identities and sensitive data from phishing, malware, and key logging attacks, particularly in the context of social networks, online banking, and e-commerce.
Innovation Solution
A fully encrypted repository system using Elliptic Curve Cryptography (ECC-160) public key pairs for secure authentication and encryption, with a decentralized architecture that generates and manages private keys on user devices, ensuring no single point of failure and protecting data through peer-to-peer authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional username and password authentication is used, then ease of operation is improved, but security against phishing, malware, and key logging attacks deteriorates
Solution Approach 1:
The patent replaces traditional mechanical authentication methods (username/password typing) with a biometric-based authentication system using accelerometers and gyroscopes to detect unique user device handling patterns. This substitution eliminates the security vulnerabilities of traditional authentication while maintaining ease of use, as users simply need to handle their device naturally for authentication.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that acts as a mediator between the user and the system. Instead of directly using passwords, the system uses accelerometer and gyroscope data as an intermediary to verify user identity through unique device handling patterns, thereby protecting against direct password exposure to phishing and key logging attacks.
2Ease of operation
If centralized data storage is used, then ease of operation is improved, but vulnerability to massive data breaches increases
Solution Approach 1:
The patent segments authentication data into two distinct components: sensitive biometric data (accelerometer and gyroscope patterns) is stored locally on the user's device, while only non-sensitive authentication tokens are stored on servers. This segmentation eliminates the risk of massive data breaches exposing sensitive biometric information, as the critical data never leaves the user's device.
Solution Approach 2:
The patent applies local quality by storing different types of data in different locations based on their sensitivity requirements. Sensitive biometric authentication data is stored locally on the user's device with high security protection, while non-sensitive transaction data can be stored centrally on servers. This differentiated storage approach maintains operational convenience for non-sensitive operations while protecting against data breaches for sensitive information.
3Reliability
If encryption keys are stored on user devices, then security is improved, but device loss or compromise becomes more critical
Solution Approach 1:
The patent segments the authentication system so that encryption keys never leave the user's device. Only encrypted authentication tokens are transmitted to servers, while the actual decryption keys remain segmented and stored exclusively on the user's local device. This segmentation ensures that even if device compromise occurs, attackers cannot extract keys from remote servers.
Solution Approach 2:
The patent converts the potential harm of device compromise into a benefit by designing a system where device loss actually strengthens security. Since encryption keys are tied to specific device hardware and never transmitted, a lost or stolen device automatically becomes useless to attackers, while the user can simply provision a new device with new keys. The system transforms the vulnerability of device dependency into a security advantage.
Data Source
AI summary
According to an embodiment of the present invention, a method for using information in conjunction with a data repository includes encrypting data associated with the information with an encryption key, sending at least the encrypted data to the data repository, and possibly deleting the information. The method also includes receiving a request for the information from a remote device, and sending a request for the encrypted data to the data repository. The method further includes receiving the encrypted data from the data repository, decrypting the encrypted data using the encryption key, and sending the information to the remote device.