Mobile App Obfuscation Using Selective Automated Hardening
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile application obfuscation technologies primarily focus on obfuscating intermediate files during compilation, failing to effectively protect sensitive logic from external tracing and analysis, especially in the context of cyberattacks that modify code and add malicious components.
Innovation Solution
Implementing an aspect-oriented security system for mobile applications that uses introspection to detect abnormal calls, identify attacked nodes, and apply automated hardening solutions based on hardening strength, including static and dynamic obfuscation, while controlling performance impact within a threshold range.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If automated hardening is applied to protect sensitive logic from reverse engineering, then security is improved, but performance degradation occurs
Solution Approach 1:
The system applies hardening selectively only to identified sensitive logic nodes rather than the entire application. The aspect-oriented security system detects abnormal calls and identifies specific attacked nodes, then applies automated hardening solutions only at those locations, maintaining local security quality while preserving overall performance.
Solution Approach 2:
The hardening strength is dynamically adjusted based on the detected attack means and abnormal call patterns. The system selects different hardening solutions (static or dynamic obfuscation) depending on the threat level, allowing the security mechanism to adapt its intensity and minimize performance impact while maintaining adequate protection.
2Reliability
If comprehensive obfuscation is applied to intermediate files, then security coverage is improved, but obfuscation effectiveness against targeted attacks deteriorates
Solution Approach 1:
The aspect-oriented security system is integrated into the compilation phase to perform preliminary hardening of sensitive logic before the application is deployed. By identifying and protecting critical nodes during compilation rather than applying blanket obfuscation to all intermediate files, the system achieves precise protection where needed while maintaining code quality elsewhere.
Solution Approach 2:
The security system uses introspection capabilities to automatically detect abnormal calls and identify attacked nodes without external intervention. This self-service approach enables the system to dynamically determine where hardening is needed and apply appropriate protection measures, improving both coverage and effectiveness.
3Measurement precision
If manual obfuscation is applied to code and symbol levels, then protection precision is improved, but automation capability deteriorates
Solution Approach 1:
The system employs an aspect-oriented security framework with introspection capabilities that automatically detect abnormal method calls, identify attacked nodes, and select appropriate hardening solutions without manual intervention. This self-service automation maintains precision by using systematic detection and analysis while eliminating the need for manual obfuscation processes.
Solution Approach 2:
The security system continuously monitors method call patterns and uses feedback from detected abnormal calls to dynamically adjust hardening strategies. By analyzing call patterns and identifying attacked nodes through feedback loops, the system achieves automated precision that adapts to actual attack scenarios rather than relying on static manual configurations.
Data Source
AI summary
The present disclosure provides a method for intelligent obfuscation of mobile applications. The method includes: performing call detection on a method chain through aspect-oriented security to detect an abnormal call; identifying an attacked node in the method chain with respect to the abnormal call to determine a hardening location; identifying an attack means with respect to the abnormal call to determine hardening strength; selecting an automated hardening solution based on the hardening strength; and executing the selected automated hardening solution at the hardening location to control impact of the automated hardening on performance in a threshold range.