Mobile Application Shielding Features
Layered protections that make it more difficult for an attacker to reverse-engineer the app in an effort to better understand it and identify ways to exploit it.
Detecting whether an attacker has duplicated the app and injected malicious functionality into it. If repackaging is detected, application shielding will render the corrupted app inoperable.
Encrypt and obfuscate encryption keys within the app independent of platform protections to add an extra layer of security and protect keys on jailbroken or rooted devices.
Overlay Detection and Prevention
Mobile banking Trojans will overlay apps with a malicious window, mimicking a legitimate log-in screen to steal banking credentials. By detecting that the shielded app has been pushed to the background, app shielding can terminate the app before theft can occur.
Jailbreaking or rooting a device disables default security controls within iOS and Android. Advanced jailbreak/root detection offers visibility that can help in risk decisions rather than denying service outright.
Debugger and Emulator Detection
Detecting and blocking debuggers, emulators, and other tools leveraged by malicious actors in their attempts to exploit a mobile app further mitigates the risks of reverse-engineering or interference with a mobile app as it executes.
Hooking Detection and Interception
By detecting and countering malware with hooking capabilities or hooking frameworks, such as Frida, app shielding maintains a tamper-resistant runtime and terminates the app before hooking can occur.
Anti-keylogging and Screen-reading
Mobile banking Trojans and other malware will attempt to log a user’s keystrokes or steal information displayed on app screens. If application shielding detects such activity, it can react in real time to interrupt it.
A Variety of Real-time Responses
App shielding reactions are configurable and can include blocking the execution of injected code, alerting administrators, feeding fraud prevention tools, or terminating the app.
Visibility for Risk Analytics
Application shielding provides contextual data about the security status of the client side that fraud prevention tools can ingest and combine with other inputs to make better risk decisions about a transaction. This results in an optimal user experience.