Third-Party Access Privilege Management via Permission Interception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users often grant access privileges to third-party applications without fully understanding the risks, leading to potential malicious activities such as spam, information leakage, and reputation damage, as the existing systems do not effectively manage access privileges securely.

Innovation Solution

A system that automatically manages security policies for third-party applications by intercepting permission requests, comparing them with user-defined profiles, and either denying or warning users about risky permissions, thereby preventing unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually review and understand permission requests before granting access, then security against malicious applications is improved, but user time and operational convenience deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoiduser time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of permission requests by comparing them against stored security policies and risk databases before presenting them to users. This pre-screening process identifies high-risk permissions that require user attention while allowing low-risk permissions to be granted automatically, thus protecting users from malicious applications without requiring manual review of every permission request.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary permission management layer between the user and third-party applications. This intermediary automatically evaluates permission requests against security policies, filters out malicious requests, and presents only approved permissions to users for confirmation. This mediator handles the security analysis work, freeing users from having to manually evaluate each permission while maintaining strong security protections.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If users grant broad access privileges to third-party applications, then application functionality and versatility are improved, but security risk and potential harm increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidsecurity risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments permission requests into distinct categories and evaluates each against specific security policies. Instead of treating permission grants as monolithic decisions, the system breaks down permissions into individual scopes (e.g., read access, write access, sensitive data access) and applies granular security rules to each segment, allowing legitimate functionality while blocking harmful permission combinations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different security evaluation criteria to different types of permissions based on their inherent risk levels. Sensitive permissions such as those accessing contact information, messages, or personal data are subject to stricter security policies and require additional user confirmation, while less sensitive permissions are granted more automatically. This localized quality control allows broad application functionality while maintaining security against harmful access.

Inventive Principle:
Principle #3Local quality

3Loss of information

If users are presented with detailed permission explanations, then understanding of granted privileges is improved, but user attention and time required for decision-making increase

Engineering Contradiction:
ImproveunderstandingVSAvoidease of granting permission
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system applies partial explanation by providing detailed permission information only when necessary - specifically when a permission request matches patterns known to be malicious or high-risk. For routine, low-risk permissions, the system provides minimal or no explanation and allows automatic granting. This selective approach maintains user understanding for critical decisions while preserving ease of operation for routine permissions.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system provides targeted feedback to users based on the risk assessment of each permission request. When a permission is flagged as potentially harmful, the system delivers specific explanations about the risks and consequences. For safe permissions, no feedback is needed. This feedback mechanism ensures users have adequate understanding when it matters most without cluttering the interface with unnecessary information for routine operations.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9473505B1Management of third party access privileges to web services
Publication Date: 2016.10.18 TREND MICRO INC
  • US9473505B1 patent drawing
  • US9473505B1 patent drawing
  • US9473505B1 patent drawing

AI summary

A user clicks on a link on a third-party Web site from his computer in order to utilize a third-party application with a Web service with which the user has an account. The application contacts the Web service and requests permissions from the user's account. The Web service sends the request to the user's computer asking to grant these permissions to the application. A software module on the user's computer intercepts this request, retrieves a user profile for this Web service, and compares the permissions requested with the permissions allowed from the profile. If any requested permissions are not allowed then the module automatically denies granting permissions and the user is not presented with an option of granting the request. A warning screen may be displayed. If all requested permissions are allowed then the request is presented to the user. A profile may apply to more than one Web service.