Skip Navigation
  1. BlackBerry Docs
  2. CylancePROTECT Mobile for UEM
  3. CylancePROTECT Mobile Overview and Administration Guide
  4. Detecting sideloaded apps on devices
  5. Android sideload detection: Behavior by activation type

Android
 sideload detection: Behavior by activation type

The scope of sideload detection depends on the user’s activation type:
Activation type
Scope of sideload detection
Android Enterprise
: Work and personal - user privacy (
Android Enterprise
 with work profile)
  • Apps in the work profile only
Android Enterprise
: Work and personal - full control (
Android Enterprise
 fully managed device with work profile)
  • Apps in the work profile only
Android Enterprise
: Work space only (
Android Enterprise
 fully managed device)
  • All apps on the device
MDM controls
  • All apps on the device (work and personal)
User privacy
  • All apps on the device (work and personal)
  • The
    UEM Client
     or a
    BlackBerry Dynamics
     app must be installed on the device
  • The user is prompted with a request to allow sideload detection on the device. If the user does not accept, sideload detection does not occur and the user's device is considered out of compliance.
Samsung Knox
 (all types)
  • Apps in the
    Knox
     work space only
For the User privacy activation type, the name, package name, and hash of sideloaded apps are partially obfuscated in the management console,
UEM
 logs, and device logs for privacy purposes. For fully managed devices, you can view the full details of sideloaded apps in the management console. For more information about data collection for different activation types, visit support.blackberry.com/community to read article 60890 (note that you require a
BlackBerry Online Account
 and an active support entitlement to view KB articles).