Risk-Based Authentication for OAuth Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face challenges in remembering multiple usernames and passwords for different types of websites and are susceptible to abuse when granting access to their information through OAuth, as the permissions requested by consumers are often vague and broad, leading to potential misuse.

Innovation Solution

Implementing risk-based authentication methods that analyze access requests from consumers to service providers on behalf of users, prompting users to approve or deny access and set rules for future similar transactions, thereby reducing the risk of abuse and enhancing security without modifying existing applications or communication protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If OAuth is used to allow consumers to access service provider information on behalf of users, then ease of operation is improved, but security is worsened due to vague and broad permissions that leave potential for abuse

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary risk analysis on access requests before granting permission. The authentication manager analyzes the consumer's request against stored risk data and user rules before the actual access occurs, allowing preventive security measures to be taken in advance while maintaining the OAuth convenience model

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback loops where access requests are monitored, risk analyses are performed, and results are used to update user rules and risk profiles. Users receive notifications about access requests and can provide feedback that refines future risk assessments, creating an adaptive security system that learns from interactions

Inventive Principle:
Principle #23Feedback

2Reliability

If users are prompted to approve each access request individually, then security is improved, but ease of operation deteriorates due to increased user burden

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies partial user involvement by automatically approving low-risk requests based on pre-established rules while only prompting users for high-risk requests that exceed automated decision thresholds. This partial action approach maintains security for critical decisions while automating routine approvals to reduce user burden

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Users pre-configure their risk tolerance and access rules in advance, establishing their security preferences before actual access requests occur. This preliminary configuration allows the system to automatically handle routine decisions according to user preferences, reducing the need for ongoing user intervention

Inventive Principle:
Principle #10Preliminary action

3Reliability

If risk analysis is performed on every access request, then security is improved, but productivity deteriorates due to increased processing time

Engineering Contradiction:
ImprovesecurityVSAvoidproductivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs risk analysis selectively rather than on every request. Automated rules handle routine low-risk requests without full risk analysis, while only triggering comprehensive risk assessments for requests that exceed predefined thresholds or exhibit unusual patterns, optimizing the balance between security and performance

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Risk profiles, user rules, and baseline behavior patterns are established in advance through preliminary setup and learning phases. This pre-computed information enables rapid risk assessment during actual access requests, reducing processing time while maintaining thorough security evaluation

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If broad permissions are granted to consumers for accessing service provider information, then ease of operation is improved, but susceptibility to abuse increases

Engineering Contradiction:
Improveease of operationVSAvoidsusceptibility to abuse
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary risk analysis on access requests before granting permission. The authentication manager analyzes the consumer's request against stored risk data and user rules before the actual access occurs, allowing preventive security measures to be taken in advance while maintaining the OAuth convenience model

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback loops where access requests are monitored, risk analyses are performed, and results are used to update user rules and risk profiles. Users receive notifications about access requests and can provide feedback that refines future risk assessments, creating an adaptive security system that learns from interactions

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10592978B1Methods and apparatus for risk-based authentication between two servers on behalf of a user
Publication Date: 2020.03.17 EMC IP HLDG CO LLC
  • US10592978B1 patent drawing
  • US10592978B1 patent drawing
  • US10592978B1 patent drawing

AI summary

Methods and apparatus are provided for risk-based authentication between two servers on behalf of a user. A method is provided for controlling access by a consumer to a service provider on behalf of a user. An authentication request is issued responsive to an initial access request from the consumer to access the service provider on behalf of the user. An access token is provided to the consumer upon approval from the user to grant access to the consumer. Upon receiving a subsequent access request from the consumer with the access token to access the service provider on behalf of the user; a risk analysis is performed to determine if the subsequent access request should be granted. The risk analysis can determine if the subsequent access complies with one or more rules of the user. The user is optionally prompted to specify whether to allow the subsequent access request and/or future similar transactions.