OneSpan Mobile Application Shielding
- 23 Oct 2024
- 1 Minute à lire
- SombreLumière
OneSpan Mobile Application Shielding
- Mis à jour le 23 Oct 2024
- 1 Minute à lire
- SombreLumière
The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article
Avez-vous trouvé ce résumé utile ?
Merci pour vos commentaires
The Mobile Authenticator Studio app can be protected by the OneSpan Mobile Application Shielding feature, which provides countermeasures against attacks that target the running app.
The countermeasures offered by the App Shielding feature per platform include the following:
Threats | App Shielding countermeasures | |
|---|---|---|
Android | iOS | |
Debugger | Prevent Java Debugger Prevent Native Debugger | Prevent Debugger |
Emulator | Detect Emulator |
|
Hooking | Detect Java Hooking Framework Detect Native Code Hooking |
|
Repackaging | Detect Repackaging | Detect Repackaging |
User screenshot | Block User Screenshot |
|
System screenshot | Block System Screenshot | Block System Screenshot |
Runtime library injection |
| Prevent Library Injection on runtime |
Keyboard monitoring | Check Trusted Keyboard | Block Keyboard Cache |
When a countermeasure is triggered, the Mobile Authenticator Studio app is closed to prevent any further intrusion.
App Shielding is not configured in the Mobile Authenticator Studio configuration file. To use App Shielding, you need to first customize the Mobile Authenticator Studio app, and then submit the final app to OneSpan to activate the feature. Whenever Mobile Authenticator Studio customization settings are changed, App Shielding must be reactivated, i.e. the app must be re-submitted to OneSpan.
Cet article vous a-t-il été utile ?