BlackBerry Dynamics Bindings for Xamarin.Android

 7.0

This version of the SDK integrates the 

CylancePROTECT

 library to support CylancePROTECT in BlackBerry UEM. 

CylancePROTECT

 is a licensed service that offers a suite of features that enhances 

BlackBerry UEM

’s ability to detect, prevent, and resolve security threats without disrupting the productivity of your workforce.

CylancePROTECT

 uses a combination of advanced technologies, including:

The cloud-based 
CylanceINFINITY
 service that uses AI and machine learning to identify malware and unsafe URL
The 
UEM
 server that provides a complete device management and compliance infrastructure for your organization
BlackBerry
 apps that monitor and enforce security standards at the device and user level

The seamless integration of these technologies establishes a secure ecosystem where data is protected and malicious activities are identified at all endpoints and eliminated proactively.

CylancePROTECT

 includes the following features:

Malware detection for apps (including 
BlackBerry Dynamics
 apps) that are uploaded to 
UEM
 for internal deployment
Malware detection on 
Android
 devices
Sideloaded app detection on 
iOS
 devices (requires the 
UEM Client
 or 
BlackBerry Work
)
Safe browsing with 
BlackBerry Dynamics
 apps
Integrity checking for 
BlackBerry Dynamics
 apps on 
iOS
 devices using the 
Apple
 DeviceCheck framework
Hardware certificate attestation for 
BlackBerry Dynamics
 apps on 
Android
 devices

For more information about 

CylancePROTECT

, see the CylancePROTECT documentation.

In new installations of 

UEM

 version 12.12 and later, all 

BlackBerry Dynamics Runtime

 connections to application servers now use TLS 1.2 by default. If you upgrade to 

UEM

 version 12.12, the existing communication settings are not changed.

You can change the permitted TLS connections to application servers in the 

UEM

 management console (Settings > 

BlackBerry Dynamics

).

Note that SSL version 3 or older is no longer supported.

UEM

 version 12.12 adds support for using proxy auto-config (PAC) files for 

BlackBerry Dynamics

 app connections to application servers. The administrator configures global PAC file support in Settings > Infrastructure > BlackBerry Router and proxy > Global settings > BlackBerry Dynamics proxy settings. The administrator can configure PAC file support at the cluster level in Settings > 

BlackBerry Dynamics

 > Clusters (select Override global settings > Enable PAC).

This feature is applicable only to 

BlackBerry Dynamics

 apps with SDK version 7.0 or later.

If the PAC file is applied through the 

BlackBerry Proxy

 configuration, the administrator must configure a 

BlackBerry Dynamics

 connectivity profile to direct connections to the 

BlackBerry Proxy

.

For more information about this feature, including limitations and conditions, see the UEM Configuration content ("Sending 

BlackBerry Dynamics

 app data through an HTTP proxy").

Note the following:

Only HTTPS proxy is supported in PAC files.
This feature does not support proxy servers that use Kerberos.
This feature does not support user-provided authentication credentials.
If a custom 
BlackBerry Dynamics
 app implements its own method of proxy support, you can use the setWebProxyAppliedByApp function to override the PAC support configured in 
UEM
 (typically this is not required).

In 

UEM

 version 12.12, when an administrator creates a new compliance profile to define compliance enforcement actions for 

BlackBerry Dynamics

 apps, the default action is now "Monitor and log".

If a user is locked out of a 

BlackBerry Dynamics

 app, or if the user's access to the app is blocked, the user now has an option on the lock or block screen to upload the log file. The log can help the 

UEM

 administrator troubleshoot if the user was locked out or blocked unexpectedly.

This release adds support for a new compliance option in 

UEM

 12.11 MR1 and later. In 

UEM

 12.11 MR1, if you enable the “Rooted OS or failed attestation” compliance option, there is a new sub-setting “Enable anti-debugging for 

BlackBerry Dynamics

 apps”. Previously, this feature was enabled by default if you enabled the “Rooted OS or failed attestation” option. This new option allows you to choose whether you want the 

BlackBerry Dynamics Runtime

 to perform a check for an active debugging tool. If it detects a debugging tool it stops the app. You may want to disable this option if you are currently testing a custom 

BlackBerry Dynamics

 app and are using a debugging tool in your environment.