Key features of the

BlackBerry AppSecure SDK

Detect whether the device is jailbroken.

Detect whether the device is rooted.

Detect whether debug mode is enabled on the device.

Detect inline hooking, a method used by malicious software to intercept calls to target functions.

Detect whether the app is running on an emulator.

Detect whether a screen lock is enabled on the device (for example, a password or PIN).

Detect whether developer mode is enabled on the device.

Detect whether disk encryption is enabled on the device.

Require users to set a password or PIN to access the app. Optionally, enable a user to unlock the app using biometrics.

Check whether the device satisfies a minimum OS requirement that you can configure.

Check whether the device satisfies a minimum security patch level that you can configure.

Use the local machine learning models that are built into the SDK or send the app files to the

BlackBerry Protect

cloud services to determine whether an app is safe or potentially malicious.

Detect whether the app is installed from a trusted source (for example,

Google Play

or the

Samsung Galaxy

Store); apps from an untrusted source are considered sideloaded.

Send URLs, including URLs in text messages (if access is permitted), to the

BlackBerry Protect

cloud services to determine whether the URLs are safe or potentially malicious.

Use secure data storage, allowing your app to store encrypted data that can be read by your app only.

Block app data backup to public cloud services such as

iCloud

and

Google Cloud

.

Require users to set a password or PIN to access the app.

Require users to use a biometric authentication method (for example, a fingerprint).

On

Android

and

iOS

devices, if the SDK is unable to connect to the

BlackBerry Protect

cloud services, it determines that the current network is not safe.

On

Android

devices, the SDK periodically checks the properties of the current Wi-Fi access point to determine if it is secure.