Personal Launch Code Integrated Anonymous Access Key Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital access security methods, particularly for Internet accounts and IoT devices, often rely on inadequate two-factor authentication, making them vulnerable to unauthorized access, as they typically require stored values for verification, which can be breached.
Innovation Solution
The integration of a Personal Launch Code (PLC) within the Anonymous Access Key (AAK) creation process, which is unique to the account owner and not stored, adds an additional authentication factor based on something only the owner knows, enhancing multi-factor authentication by eliminating the need for stored value matching and thus reducing the risk of unauthorized access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If stored values are used for authentication verification, then authentication can be performed, but the system becomes vulnerable to data breaches and unauthorized access
Solution Approach 1:
The patent extracts the authentication value from stored form to computed form. Instead of storing and verifying passwords or keys, the system computes a one-time token from the user's data and device information, then verifies against this computed value. This removes the vulnerable stored values from the system while maintaining authentication capability.
Solution Approach 2:
The system performs preliminary computation of the authentication token before the actual authentication verification. The token is computed in advance from user data and device identifiers, then used for verification. This preliminary action eliminates the need for stored credentials while enabling secure authentication.
2Reliability
If multi-factor authentication is implemented, then access security is enhanced, but the complexity of the authentication process increases
Solution Approach 1:
The patent merges multiple authentication factors into a single integrated token. Instead of separately handling passwords, device identifiers, and timing information, the system combines all these factors into one computed authentication token. This reduces the complexity of implementing multi-factor authentication while maintaining its security benefits.
Solution Approach 2:
The authentication token serves multiple functions simultaneously: it verifies user identity, validates device authenticity, ensures timing accuracy, and provides one-time use protection. This multi-functionality reduces the need for separate authentication mechanisms, simplifying the overall process while enhancing security.
3Reliability
If random values and one-time tokens are used for authentication, then vulnerability to brute force attacks is reduced, but the computational requirements increase
Solution Approach 1:
The system changes the parameter of authentication from stored credentials to computed one-time tokens with expiration. This transforms the authentication mechanism to use temporary, randomly generated values that are computationally expensive to brute force but inexpensive to generate and verify, balancing security with computational efficiency.
Data Source
AI summary
A Personal Launch Code (PLC) known only by the rightful account owner becomes an included element within the construction of an Anonymous Access Key (AAK) used to validate and authenticate digital account access and whereby said PLC is never stored for matching against another representation of said PLC.