angr supports symbolic analysis and investigation of program behavior. Results for mobile binaries depend on the model, inputs and environmental assumptions.
Evaluation approach
Symbolically model inputs and states to explore paths. Path explosion and modeling external behavior are major challenges.
Application example
Choose a narrow target, such as boundary conditions in a small validation function in your native library.
Limits and considerations
Realistically modeling an entire mobile application is difficult. A path not found is not necessarily impossible.
Keep symbolic investigation focused
Searching for inputs that reach a particular output is more manageable than unbounded analysis of an application. Initial state and external-function models determine what a result means. State search limits and time budgets.
Validate a discovered input through concrete execution in your test environment. No result does not prove the path impossible. This distinction prevents unsupported assurance or failure claims about RASP.
Checks and decisions
- Narrow the target
- State assumptions
- Validate discovered inputs through execution
angr supports advanced analysis; it is not an automatic substitute for evaluating RASP products.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.