Contact Preference Authentication Challenge Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing online user authentication systems lack effective methods to differentiate between legitimate and fraudulent login attempts, particularly in scenarios where secondary authentication information is suspicious, leading to potential unauthorized access.
Innovation Solution
A system and method that generates a user authentication challenge based on the preferences of the account owner's contacts, utilizing a fraudulent authentication detection engine, close contact identifier, contact preference engine, and challenge generation engine to create personalized challenges for users attempting to log in, thereby enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods (passwords, CAPTCHAs) are used, then the authentication process is simple and fast, but the system cannot effectively differentiate between legitimate and fraudulent login attempts
Solution Approach 1:
The system pre-collects and stores preference information about the account owner's contacts before authentication is needed. This preliminary data gathering enables the authentication challenge to be quickly generated based on known preferences, rather than requiring real-time complex analysis during the authentication process itself
Solution Approach 2:
The patent introduces preference information about contacts as an intermediary element between the user and the authentication system. Instead of directly verifying user credentials, the system uses the contact's preferences as a mediator to indirectly verify the user's identity, making it difficult for fraudsters to bypass
2Reliability
If secondary authentication information is required to detect fraudulent attempts, then authentication security improves, but the authentication process becomes more complex and time-consuming
Solution Approach 1:
Preference information about contacts is collected and stored in advance during normal account usage. When authentication is required, the system simply retrieves this pre-stored information to generate the challenge, avoiding time-consuming data collection during the critical authentication moment
Solution Approach 2:
The system uses the account owner's own preference information (about their contacts) to create the authentication challenge. This self-referential approach means the data already exists in the system from the user's own profile, eliminating the need for additional external verification services or time-consuming queries
Data Source
AI summary
Generating user authentication challenges based in part on preferences of one or more contacts of a user includes receiving an authentication request from a user. One or more contacts of the user associated with the authentication request are determined. One or more preferences of the close contact or contacts are determined. An authentication challenge based on the one or more preferences of one or more of the user's contacts is generated. The authentication request is allowed or denied based on the completion on the authentication challenge.


