Analysis and debugging
Detect tools that analyse the app while it runs.
MST AppGuard · Android protection
Your application.
Protected.
Protect Android apps and SDKs against reverse engineering and tampering. Code, data and runtime protection in one solution.
Code + Data + Runtime
Applications and SDKsJava / Kotlin · Native libraries
Protect what you have createdInside your application:
Inside your application:
your business value.
Algorithms, integrations, keys and user data. MST AppGuard helps make app analysis harder and detect tampering attempts.
- Intellectual property protection
- Payment workflow integrity checks
- Protection of sensitive components
- Settings for your product
For Android products
Mobile applicationsCustomer and enterprise apps
Payment applicationsSensitive business logic
Libraries and SDKsIntegration components
Multiple protection layersCode. Data. Runtime.
Code. Data. Runtime.
Protection at each stage.
Choose a layer to explore the mechanisms and the problems they address.
Your logic stays yours.
Obfuscation and encryption make it harder to analyse the app, extract its logic and reuse components.
- Names, arithmetic and control flow
- Classes, strings, assets and resources
- Native libraries and SDK calls
- Additional decoy constructs
App
→
Protective transformations
→
Protected build
Protection works alongside the application.
Environment checks help detect analysis and tampering attempts while the application runs.
- Debuggers and emulators
- Root access and tools that conceal it
- Hooking frameworks
- Configurable response to suspicious activity
Launch
→
Environment checks
→
Response policy
Protection beyond the interface.
Protect app data and verify server connections through SSL pinning, WebView SSL pinning and certificate checks.
- Confidential application data
- Network connection checks
- Configuration for your project infrastructure
- Certificate update workflow testing
App
→
Trust verification
→
Your server
While the application runsDetect tampering.
Detect tampering.
Respond according to your policy.
We configure checks and responses around security requirements and the user workflow.
Unsafe environments
Checks for emulators and rooted devices.
Hooking
Detect frameworks that interfere with app operation.
Threat response
The protective action depends on the selected configuration.
Possible responses include stopping the app, an isolated environment and code restoration. We assess the applicability of each mode in a pilot build.
CompatibilityYour Android stack.
Your Android stack.
Our protection tools.
We work with Java, Kotlin and native C/C++ libraries. We select a configuration for the application's components and test it on your builds.
JavaApplication code
KotlinApplication code
C/C++Native libraries
Android StudioDevelopment environment
Android NDKNative components
SDKEmbedded libraries
Fits into your development process.
Protective transformations are applied to the build without rewriting the source code. We assess compatibility and performance in a pilot.
Implementation in your productFrom application assessment.
From application assessment.
To a validated build.
First, we identify critical workflows. Then we select settings and test the protected version on target devices.
-
01
Study the application
The stack, libraries, build process and data requiring protection.
-
02
Select settings
Protection mechanisms and acceptable threat responses.
-
03
Run a pilot
Core workflows, compatibility, startup time and performance.
-
04
Prepare for releases
Document the configuration and validation process for future versions.
Questions answeredWhat to know
What to know
before starting.
Can protection be added to an existing app?+
Yes. We start with its components and build process, test the selected mechanisms in a pilot and agree on further use.
Can we select individual mechanisms?+
The configuration is tailored to the app: we protect critical components while considering compatibility, stability and performance requirements.
What should we check before release?+
Key user workflows, SDKs and native libraries, target devices and Android versions. Network protection also requires certificate update testing.
What do we need for the first meeting?+
An app description, stack, main libraries, target devices and protection requirements. We agree the process for sharing builds and technical materials with your team.
Start with your challengeStrengthen protection.
Strengthen protection.
For your Android product.
Tell us about the app and its critical workflows. We will discuss AppGuard mechanisms, integration terms and a pilot plan.
- Application, SDK and development stack
- Target devices and Android versions
- Protection and performance requirements
Scope and terms are defined after we understand your project.
Loading the contact form…