THE PRINCIPLES
Mobile applications have become the primary channel for banking, payments, and identity services.
This shift has also created new attack surfaces: reverse engineering, runtime tampering, credential theft, and fraud via compromised devices.
For regulated institutions, securing the backend is not enough.
The application itself - and the mobile session - must be protected with layered, adaptive controls that evolve as quickly as the threat landscape.
This guide provides a framework for evaluating mobile application security solutions. It outlines:
- Market drives
- Buyer challenges
- Evaluation criteria
- How Cryptomathic’s Mobile Application Security Core Solution (MASC) addresses these needs in regulated environments
MOBILE APPLICATION SECURITY MARKET DRIVERS
MOBILE-FIRST DELIVERY
Consumers expect full banking, payments, and eID services on mobile - often across multiple apps - making the mobile channel business-critical.
INCREASED FRAUD ACTIVITY
Attackers use rooting, overlays, hooking frameworks, and malware to exploit apps. Many root and jailbreak techniques can evade traditional or static controls.
PLATFORM & DEVICE FRAGMENTATION
Banks and payment providers must protect diverse device populations. Controls must remain effective across OS versions, device models, and manufacturer customizations - including scenarios with prolonged offline use.
COMPLIANCE PRESSURE & AUDIT EXPECTATIONS
Frameworks such as PSD2 SCA, PCI DSS, PCI MPoC, DORA, and NIS2 demand robust app-level and transaction-level protection - supported by governance, risk management, and evidence of control effectiveness. Institutions must be able to demonstrate how controls operate in practice and how to maintain them over time.
AGILE DELIVERY & MODERNIZATION
DevOps teams must release frequently without compromising security or compliance. In parallel, organizations are modernizing authentication (for examplÅe, moving from SMS OTP to biometrics), migrating mobile frameworks, and rationalizing legacy apps. Security must keep pace without becoming a maintenance bottleneck.
MOBILE APPLICATION SECURITY BUYER CHALLENGES
Organizations evaluating mobile application security solutions often face:
-
BALANCING SECURITY & RELEASE VELOCITY
Custom hardening slows release cycles and consumes engineering effort. Security must keep pace with CI/CD while remaining testable and maintainable across multiple apps.
-
CROSS-PLATFORM COMPLEXITY
Android and iOS require different defensive measures, often duplicating work. Hybrid and cross-platform frameworks further complicate consistent control deployment and testing.
-
UNTRUSTED DEVICE ENVIRONMENTS
Sensitive assets and credentials must remain protected even on compromised devices. Rooting techniques, malware, emulators, and bot activity can be difficult to detect reliably without false positives or degraded user experience.
-
FRAUD DETECTION GAPS
Risk and fraud systems rely on signals they cannot always trust. Weak attestation, undetected reverse engineering, and API misuse reduce confidence in device and session telemetry.
-
SECURITY VS. USER EXPERIENCE
Overly aggressive controls, high false-positive rates, and intrusive prompts frustrate users and can drive churn. Buyers need controls that are tunable, can be tested safely, and support a consistent UX across journeys and channels.
-
OPERATIONAL BURDEN (MAINTENANCE & TESTING)
Many solutions are difficult to maintain as apps evolve. OS updates, API changes, and architecture shifts can force repeated rework. Security teams need reliable ways to validate enforcement and detect regressions before production.
-
COMPLIANCE & AUDIT READINESS
Demonstrating compliance with PSD2, PCI DSS, DORA, NIS2, and national regulations requires clear mappings between controls and policies. Many tools provide limited audit support, leaving teams to fill gaps manually.
-
API & CERTIFICATE MANAGEMENT WEAKNESSES
API misuse, weak server binding, and inconsistent certificate practices can undermine otherwise strong security. Buyers need solutions that enforce secure patterns and support centralized management of keys and certificates.
-
MODERNIZATION & AUTHENTICATION RENEWAL
As institutions modernize authentication and mobile stacks, they must be able to renew and rotate security measures without rewriting apps from scratch.
MOBILE APPLICATION SECURITY EVALUATION CRITERIA
When assessing solutions, buyers should consider the following:
- Layered runtime defenses, including debugger blocking, root/jailbreak detection, emulator detection, and hooking/overlay detection.
- Integrity verification against tampering, instrumentation, and reverse engineering - including protection of code and configuration.
- Behavioral indicators of malware and advanced rooting techniques, with policies designed to reduce false positives and support good user experience.
- Policy-based enforcement with minimal code changes, enabling security teams to adjust controls without re-implementing business logic.
- Rapid updates in response to emerging threats, new OS versions, and regulatory changes.
- Built-in testing and validation so changes can be verified safely before broad rollout.
- Multi-layer protection for keys, tokens, credentials, and sensitive libraries - remaining effective even on compromised devices.
- White-box cryptography and hardware-backed keystores where available
- Support for major app development frameworks (Java, Kotlin, Swift, React Native, Flutter, Xamarin) with consistent policy semantics.
- Coverage across Android and iOS, with controls that adapt to device capabilities while maintaining a baseline level of protection.
- Backend assurance for attestation, telemetry, and policy enforcement - integrated with existing identity systems, fraud/risk engines, and API gateways.
- Mappings to OWASP MASVS, ENISA Mobile App Security guidance, and PCI MPoC requirements.
- Demonstrated control coverage for PSD2 SCA, PCI DSS, DORA, and NIS2 - with the ability to generate evidence and reports aligned to audit needs.
- Support for governance processes, including role-based access to policies and an auditable change history.
- Secure storage of tokens and cookies, gated by biometrics or PIN.
- Support for asymmetric key creation and transaction signing.
CRYPTOMATHIC MASC STRENGTHS
Cryptomathic MASC (Mobile Application Security Core) is designed to meet the criteria above. Its strengths include:
-
RUNTIME SELF-PROTECTION
Debugger and emulator blocking, root/jailbreak detection, hooking and overlay prevention, and app integrity checks.
-
SECRETS & SECURE STORAGE
Multi-layer obfuscation, white-box cryptography, hardware-backed keystores, and Virtual Cores for segregated access.
-
NETWORK & API HARDENING
Certificate pinning, host allowlisting, OAuth2, double encryption, and secure WebView/WebSocket support.
-
TRANSACTION SECURITY
Secure key creation for transaction signing and customer authentication.
-
ATTESTATION & VISIBILITY
Backend assurance verifies client integrity, captures device health and attack telemetry, and supports policy responses (allow, block, report, crash).
-
AGILITY
Telemetry-driven insights and policy updates reduce discovery-to-patch time.
-
PROVEN DEPLOYMENTS
Multi-year production rollouts at tier-1 European and multinational banks, securing millions of mobile sessions.
MOBILE APPLICATION SECURITY BUYER CHECKLIST
When shortlisting vendors, ensure solutions can:

