User Configurable Security Permission Profiles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users are exposed to privacy risks due to applications being granted excessive and unnecessary permissions during installation, which can lead to malicious actions by rogue applications without their awareness, compromising sensitive information and services.
Innovation Solution
A customizable permissions framework that allows users to define permissions profiles on a global or per-application basis, enabling them to deny, grant, or request prompts for permissions before an application accesses device functionalities or data, using customized or global permissions manifest files instead of default permissions manifest files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If applications are configured by default to request permission access to functionalities and data, then application installation and functionality is improved, but user privacy security deteriorates due to excessive and unnecessary permissions being granted
Solution Approach 1:
The permission system is segmented into multiple permission profiles (first permission profile, second permission profile, third permission profile) with different permission sets. Users can select which profile to apply when installing an application, allowing them to granularly control which permissions are granted. This segmentation resolves the contradiction by providing default profiles that ease installation while allowing users to switch to more restrictive profiles to mitigate privacy risks.
Solution Approach 2:
The system dynamically switches between different permission profiles based on user selection. The permission manager can apply different permission sets depending on which profile the user chooses during application installation. This dynamic adaptability allows the system to maintain ease of operation with default profiles while enabling enhanced privacy protection when users actively select alternative profiles.
2Object-affected harmful factors
If users are prompted to grant permissions for application installation, then privacy protection is improved, but installation complexity increases due to multiple permission profiles and selection processes
Solution Approach 1:
Multiple permission profiles are pre-configured and stored in the system before application installation. The first permission profile includes a first set of permissions, the second includes a second set, and the third includes a third set, all prepared in advance. This preliminary action eliminates the need for users to configure permissions from scratch, reducing installation complexity while still providing multiple privacy protection options.
Solution Approach 2:
The permission manager serves multiple functions: it manages default permissions, handles profile selection, applies permission sets, and provides user guidance all within a single system component. This multi-functionality reduces overall system complexity by consolidating permission management tasks rather than requiring separate mechanisms for each function.
3Adaptability or versatility
If applications request excessive permissions during installation, then application functionality is improved, but security against rogue applications deteriorates
Solution Approach 1:
Permissions are segmented into distinct profiles with different permission sets. The first permission profile includes a first set of permissions, the second includes a second set, and the third includes a third set. Users can select which profile to apply based on the application's claimed functionality, allowing them to grant only the permissions necessary for the application to work, thereby maintaining functionality while improving security against rogue applications.
Solution Approach 2:
The system provides feedback to users about which permissions are being requested and allows them to review and select appropriate permission profiles. This feedback mechanism enables users to make informed decisions about which permissions to grant, balancing application functionality needs with security concerns and preventing rogue applications from exploiting excessive permissions.
Data Source
AI summary
Permissions specified within an application permission manifest file of an application may be superseded with customized permissions. A user may customize the permissions by denying permissions, granting permissions, or requesting a prompt prior to an application attempting to access functionality and/or data protected by a permission. A user may customize permissions on a global or per application basis. Upon receiving input to customize a permissions profile, a package manager module creates a new permissions manifest file associated with an application. Upon receiving input to execute an application, a runtime environment that may be provided by the runtime accesses the new permissions manifest file instead of an original permissions manifest file, and operates the application using permissions granted in the new permissions manifest file.