Release Notes – 2.0.57

Google has deprecated three settings options (Ensure Verify Apps Enabled, Debugging Features Allowed, and Safe Boot Disabled) and replaced them with two new options (Google Play Protect Verify Apps and Developer Settings):

Before resaving any existing Policies, please be sure the new Google Play Protect Verify Apps and Developer Settings are configured as desired
  1. The Ensure Verify Apps Enabled setting has been replaced by the new Google Play Protect Verify Apps setting.

    1. The new Google Play Protect Verify Apps setting is located in the Policy=>General Settings, near the bottom.
      1. Google_Play_Protect_Verify_Apps
    2. Rather than simply toggling on or off the Ensure Verify Apps Enabled setting, the new Google Play Protect Verify Apps setting offers the following options:
      1. Force-enable app verification – Play Protect App Verification will be turned on
      2. Allow user to choose enable app verification – User will be able to choose to turn on or off Play Protect App Verification
      3. Unspecified – The Policy will not make any adjustments to the device setting
    3. If a Policy previously had Ensure Verify Apps Enabled toggled ON, it has been updated to the “Force-enable app verification” settings option for the new Google Play Protect Verify Apps setting.
    4. If a Policy previously had Ensure Verify Apps Enabled toggled OFF, it has been updated to “Allow user to choose enable app verification” setting option for the new Google Play Protect Verify Apps setting.
  2. The Debugging Features Allowed and the Safe Boot Disabled settings have been replaced by the new Developer Settings option.

    1. The new Developer Settings option is located in the Policy=>General Settings, near the bottom.
      1. Developer_Settings_AE_Policy
    2. The new Developer Settings option offers the following options:
      1. Disable all developer settings – Safe Boot and Debugging Features will both be disabled, and will not be able to be enabled by a user on the device.
      2. Allow all developer settings – Safe Boot and Debugging Features will be allowed on the device, but a user can toggle Developer options off on the device
      3. Unspecified – The Policy will not make any adjustments to the device setting

A new Common Criteria Mode Policy setting option has been added

  1. Common Criteria Mode offers a new Policy setting option

    1. The new Common Criteria Mode setting is located in the Policy=>General Settings, near the bottom.
      1. Common_Criteria_Mode_AE
    2. The new Common Criteria Mode setting offers the following options:
      1. Enable – Enable Common Criteria Mode
      2. Disable – Disable Common Criteria Mode
      3. Unspecified – The Policy will not make any adjustments to the device setting
    3. Common Criteria Mode controls security standards defined in the Common Criteria for Information Technology Security Evaluation. Enabling Common Criteria Mode increases certain security components on a device, including AES-GCM encryption of Bluetooth Long Term Keys, and Wi-Fi configuration stores.
WARNING: Common Criteria Mode enforces a strict security model typically only required for IT products used in national security systems and other highly sensitive organizations. Standard device use may be affected. Only enable if required.
 

See Moki in Action

Request a Demo today with by phone, email, or just fill out the form

Contact Us