Permission Request Segmentation for Mobile App Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users are overwhelmed by numerous permission requests when installing applications that access multiple computing resources, leading to potential security risks as they may hastily approve access without fully understanding the resources being requested, which can compromise security.
Innovation Solution
A method to categorize applications based on common permissions, where unusual resource access requests are flagged and visually distinguished from typical ones, allowing users to scrutinize atypical requests more carefully.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system displays all permission requests individually, then the user can make informed decisions about each resource access, but the user becomes overwhelmed and frustrated by the large number of requests
Solution Approach 1:
The patent segments permission requests into two distinct groups: common permissions (grouped together with a single approval action) and uncommon permissions (listed individually). This segmentation allows users to quickly approve routine requests while maintaining careful scrutiny of unusual requests, resolving the contradiction between security and ease of operation.
Solution Approach 2:
The patent applies different treatment to different types of permission requests based on their characteristics. Common permissions receive streamlined handling (grouped approval), while uncommon permissions receive enhanced scrutiny (individual listing). This local differentiation optimizes the user experience for each category without compromising overall security.
2Reliability
If the system requests permission for each computing resource separately, then the user can evaluate each request carefully, but the installation process becomes time-consuming and complex
Solution Approach 1:
By segmenting permissions into common and uncommon categories, the system eliminates redundant approval steps for common resources while maintaining individual evaluation for uncommon ones. This reduces installation time significantly while preserving careful evaluation where needed.
Solution Approach 2:
The system applies full individual review only to uncommon permissions (partial action) rather than all permissions. This partial application of stringent review maintains security for critical cases while avoiding unnecessary time consumption for routine permissions.
3Ease of operation
If the system groups all permission requests together for bulk approval, then the installation process becomes faster and simpler, but the user cannot distinguish between typical and atypical resource access requests
Solution Approach 1:
The patent segments the permission approval interface into distinct sections: a summary for common permissions and a detailed list for uncommon permissions. This segmentation maintains simplicity for routine approvals while preserving security awareness through highlighted unusual requests.
Solution Approach 2:
Different visual and interaction qualities are applied to common versus uncommon permissions. Common permissions use streamlined grouping, while uncommon permissions use distinctive formatting and individual listing, ensuring users maintain security awareness for atypical requests without sacrificing overall simplicity.
4Reliability
If the system highlights unusual permission requests, then security awareness is enhanced and users can identify potential risks, but the interface becomes more complex
Solution Approach 1:
The interface is segmented into two clear sections: common permissions (simple grouping) and uncommon permissions (detailed listing with highlights). This segmentation enhances security awareness for unusual requests while keeping the overall interface structure simple and intuitive.
Solution Approach 2:
Visual highlighting and detailed formatting are applied locally only to uncommon permissions rather than uniformly across all permissions. This localized enhancement improves security awareness for critical cases without unnecessarily complicating the entire interface.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and devices for managing permission requests to allow access to a computing resource are disclosed herein. In one example embodiment, the method comprises: for an application to be installed on the computing device, determining an application category that the application is associated with, and retrieving a common permissions list for the application category, wherein the common permissions list identifies at least one computing resource that applications associated with the application category are configured to access; during an installation of the application on the computing device, determining one or more computing resources on the computing device that the application is configured to access when the application is executed on the computing device; determining which computing resources, of the one or more computing resources on the computing device that the application is configured to access when the application is executed on the computing device, are not identified in the common permissions list; and for each computing resource that the application is configured to access when the application is executed on the computing device that is not identified in the common permissions list, providing, in a user interface of the computing device, a permission request to allow the application to access the computing resource.