Compiled Application Auditing for Permission Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users and administrators face challenges in setting appropriate access permissions for mobile applications, as it is unclear which permissions restrict the proper operation of trusted applications, leading to a time-consuming trial-and-error process to identify the source of issues.
Innovation Solution
A method to audit compiled applications by analyzing method calls and correlating them with controllable activities, generating a report that indicates potential activities an application may attempt, allowing users to set informed permission settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If access permissions are set to limit application activities, then security is improved, but it becomes difficult to identify which permissions restrict trusted applications
Solution Approach 1:
The system performs preliminary analysis of the application code to identify potential method calls before execution. By pre-auditing the application and generating a report of potential activities, the system enables users to understand which permissions might be needed before installing or running the application, thus avoiding trial-and-error permission setting.
Solution Approach 2:
The patent introduces an intermediary auditing mechanism that acts as a mediator between the application and the permission system. The auditor analyzes the application code, identifies potential method calls, and generates a report that serves as an intermediary information source, helping users make informed decisions about permission settings without directly configuring complex permission rules.
2Reliability
If comprehensive permission settings are provided, then application control is improved, but the time to configure and test permissions increases
Solution Approach 1:
The system performs preliminary analysis of the application code to identify potential method calls before execution. By pre-auditing the application and generating a report of potential activities, the system enables users to understand which permissions might be needed before installing or running the application, thus avoiding trial-and-error permission setting.
Solution Approach 2:
The auditing system provides feedback by analyzing the application code and generating a report that indicates potential activities the application may attempt. This feedback mechanism helps users quickly understand the permission requirements without having to test each permission setting individually, significantly reducing the time needed for configuration.
3Ease of operation
If applications are allowed to execute with full permissions, then ease of operation is improved, but security risks increase
Solution Approach 1:
The system performs preliminary analysis of the application code to identify potential method calls before execution. By pre-auditing the application and generating a report of potential activities, the system enables users to understand which permissions might be needed before installing or running the application, thus avoiding trial-and-error permission setting.
Solution Approach 2:
The auditing mechanism serves the user by automatically analyzing the application code and generating permission recommendations. Instead of requiring users to manually review complex permission settings or test applications extensively, the system performs self-service analysis to provide informed permission configuration recommendations.
Data Source
AI summary
A compiled application may be audited by analyzing the compiled application to identify methods that may be called during execution of the compiled application. The identified methods may be correlated with controllable activities, i.e., those activities facilitated by public APIs. An audit report may be used to report to a user or administrator indications that the compiled application may attempt certain activities.