Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Review Google Android device configuration settings to determine if the mobile device is enforcing a minimum password length of six characters. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Ensure the minimum password length is set to 6 characters. On the Android 10 device, do the following: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Tap "Password". 4. Verify Password length listed is at least 6. If the device password length is not set to six characters or more on MDM console or on the Android 10 device, this is a finding.
Configure the Google Android device to enforce a minimum password length of six characters. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Enter in the number of characters as "6".
Review Google Android device configuration settings to determine if the mobile device is prohibiting passwords with more than two repeating or sequential characters. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Ensure the password quality is set to "Numeric (Complex)". On the Android 10 device, do the following: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Tap "Password". 4. Verify Password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed. If the MDM console device policy is set to a password with more than two repeating or sequential characters or on the Android 10 device, the device policy is set to a password with more than two repeating or sequential characters, this is a finding. Note: Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.
Configure the Google Android device to prevent passwords from containing more than two repeating or sequential characters. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Set password quality to "Numeric (Complex)". Note: Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.
Review Google Android device configuration settings to determine if the mobile device is enforcing a screen-lock policy that will lock the display after a period of inactivity. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open password requirements. 2. Open device password section. 3. Ensure "Max time to screen lock" is set to any number desired. Units are in Seconds. On the Android 10 device, do the following: 1. Open Settings >> Display. 2. Tap "Screen timeout". 3. Ensure the Screen timeout value is set to the desired value and cannot be set to a larger value. If the MDM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity or on the Android 10 device, the device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity, this is a finding.
Configure the Google Android device to enable a screen-lock policy that will lock the display after a period of inactivity. On the MDM Console: 1. Open password requirements. 2. Open device password section. 3. Set "Max time to screen lock" to any number desired. Units are in Seconds.
Review Google Android device configuration settings to determine if the mobile device has the screen lock timeout set to 15 minutes or less. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open passcode requirement 2. Open device passcode section. 3. Ensure "Max time to screen lock" is set to any number between 1 and 15. On the Android 10 device, do the following: 1. Open settings >> Security. 2. Tap on "Screen timeout". 3. Ensure the Screen timeout value is set to between 0 and 15 minutes. If the MDM console device policy is not set to 15 minutes or less for the screen lock timeout or on the Android 10 device, the device policy is not set to 15 minutes or less for the screen lock timeout, this is a finding.
Configure the Google Android device to lock the device display after 15 minutes (or less) of inactivity. On the MDM Console: 1. Open password requirements. 2. Open device password section. 3. Set "Max time to screen lock" to any number between 1 and 15.
Review Google Android device configuration settings to determine if the mobile device has the maximum number of consecutive failed authentication attempts set at 10 or fewer. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open password requirements. 2. Open device password section. 3. Review the policy configuration that was pushed down to the device and ensure the "Max password failures for local wipe" is set between 1 and 10. On the Android 10 device, do the following: 1. Open Setting >> Security >> Managed device info. 2. Verify "Failed password attempts before deleting all device data" is set to 10 or fewer attempts. If the MDM console device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, or if on the Android 10 device the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.
Configure the Google Android device to allow only 10 or fewer consecutive failed authentication attempts. On the MDM Console: 1. Open password requirements. 2. Open device password section. 3. Set "Max password failures for local wipe" to a number between 1 and 10.
Review Google Android device configuration settings to determine if the mobile device has only approved application repositories (DoD-approved commercial app repository, MDM server, and/or mobile application store). This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open Restrictions Section. 2 Toggle "Disallow installs from unknown sources globally" to on. On the Google device, do the following: 1. Open Settings >> Apps and notifications >> Advanced >> Special app access. 2. Open Install unknown apps. 3. Ensure the list of apps is blank or if an app is on the list, "Disabled by admin" is listed under the app name. If the MDM console device policy is not set to allow connections to only approved application repositories or on the Android 10 device, the device policy is not set to allow connections to only approved application repositories, this is a finding.
Configure the Google Android device to disable unauthorized application repositories. On the MDM Console: 1. Open Restrictions section. 2 Toggle "Disallow installs from unknown sources globally" to on.
Review Google Android device configuration settings to determine if the mobile device has an application whitelist configured. Verify all applications listed on the whitelist have been approved by the Approving Official (AO). This validation procedure is performed only on the MDM Administration Console. On the MDM console, do the following: 1. Go to the Android app catalog for managed Google Play. 2. Verify all selected apps are AO approved. NOTE: Managed Google Play is always a Whitelisted App Store. If on the MDM console the list of selected Managed Google Play apps included non-approved apps, this is a finding. Note: The application whitelist will include approved core applications (included in the OS by the OS vendor) and pre-installed applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and pre-installed applications. For Google Android, there are no pre-installed applications.
Configure the Google Android device to use an application whitelist. On the MDM Console: 1. Go to the Android app catalog for managed Google Play. 2. Select apps to be available (only approved apps). 3. Push updated policy to the device. NOTE: Managed Google Play is always a Whitelisted App Store.
Review Google Android device configuration settings to determine if the mobile device has an application whitelist configured and that the application whitelist does not include applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; - payment processing; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. This validation procedure is performed only on the MDM Administration Console. On the MDM console, do the following: 1. Review the list of selected Managed Google Play apps. 2. Review the details and privacy policy of each selected app to ensure the app does not include prohibited characteristics. If the MDM console device policy includes applications with unauthorized characteristics, this is a finding.
Configure the Google Android device application whitelist to exclude applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; - payment processing; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. On the MDM Console: 1. Go to the Android app catalog for managed Google Play. 2. Before selecting an app, review the app details and privacy policy to ensure the app does not include prohibited characteristics.
Determine if the AO has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify Bluetooth has been disabled: On the MDM console, do the following: 1. Open restrictions Section. 2. Ensure "Disallow Bluetooth" is set. On the Android 10 device, do the following: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Ensure that it is set to Off and cannot be toggled to On. If the AO has approved the use of Bluetooth, on the Google Android 10 device do the following: 1. Go to Settings >> Connected Devices. 2. Verify only approved Bluetooth connected devices using approved profiles are listed. If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an MDM managed device policy, this is a finding. If the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under "Connected devices", this is a finding.
Configure the Google Android device to disable Bluetooth or if the AO has approved the use of Bluetooth (for example, for car hands-free use), train the user to connect to only authorized Bluetooth devices using only HSP, HFP, or SPP Bluetooth capable devices (User Based Enforcement [UBE]). To disable Bluetooth use the following procedure: On the MDM Console: 1. Open restrictions section. 2. Toggle "Disallow Bluetooth" to on. The user training requirement is satisfied in requirement GOOG-10-008700.
Review Google Android device settings to determine if the Google Android device displays (work container) notifications on the lock screen. Notifications of incoming phone calls are acceptable even when the device is locked. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open restrictions Section. 2. Open Work Managed Section. 3. Ensure "Disable Unredacted Notifications" is selected. On the Android 10 device, do the following: 1. Go to Settings >> Display >> Advanced. 2. Tap on Lock screen display. 3. Ensure "Hide sensitive work content" is listed under "When work profile is locked". If the MDM console device policy allows work notifications on the lock screen, or the Android 10 device allows work notifications on the lock screen, this is a finding.
Configure the Google Android device to not display (work profile) notifications when the device is locked. On the MDM console: 1. Open restrictions section. 2. Open Work Managed Section. 3. Select "Disable Unredacted Notifications".
Review device configuration settings to confirm that trust agents are disabled. This procedure is performed on both the MDM Administration console and the Google Android 10 device. On the MDM console: 1. Open restrictions section. 2. Set "Disable trust agents" to on. On the Google Android 10 device: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the MDM console "disable trust agents" is not selected, or on the Android 10 device a trust agent can be enabled, this is a finding.
Configure Google Android 10 to disable trust agents. On the MDM console: 1. Open Lock screen restrictions section. 2. Set "Disable trust agents" to on.
Review Google Android device configuration settings to determine whether a developer mode is enabled. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open restrictions section. 2. Open Restrictions section. 3. Toggle "Disallow debugging Features" to on. On the Android 10 device, do the following: 1. Go to Settings >> System. 2. Ensure Developer Options is not listed. If the MDM console device policy is not set to disable developer mode or on the Android 10 device, the device policy is not set to disable developer mode, this is a finding.
Configure the Google Android device to disable developer modes. On the MDM Console: 1. Open restrictions section. 2. Open Restrictions section. 3. Toggle "Disallow debugging Features" to on.
The DoD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Description): 1. By placing the DoD warning banner text in the user agreement signed by each Google Android device user (preferred method). 2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device. Determine which method is used at the Google Android device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Google Android device users and verify the agreement includes the required DoD warning banner text. Validation Procedure for Method #2: On the MDM console, do the following: Ensure "Lock Screen Message" and the appropriate banner text is included. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the MDM console device policy is not set to display a warning banner with the appropriate designated wording or on the Android 10 device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.
Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Description): 1. By placing the DoD warning banner text in the user agreement signed by each Google Android device user (preferred method). 2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device. On the MDM Console: Enable "Lock Screen Message" and enter the banner text.
Review Google Android device configuration settings to determine if the mobile device has a USB mass storage mode and whether it has been disabled. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open User restrictions. 2. Open User restrictions. 3. Ensure "Disallow usb file transfer" is selected. On the Android 10 device, do the following: 1. Plug a USB cable into Android 10 device and connect to a non-DoD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Ensure “No data transfer” is selected. If the MDM console device policy is not set to disable USB mass storage mode or on the Android 10 device, the device policy is not set to disable USB mass storage mode, this is a finding.
Configure the Google Android device to disable USB mass storage mode. On the MDM console: 1. Open User restrictions. 2. Open User restrictions. 3. Select "Disallow usb file transfer".
Review Google Android device configuration settings to determine if the capability to back up to a locally connected system has been disabled. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open User restrictions. 2. Select "Disallow usb file transfer". On the Android 10 device, do the following: 1. Plug a USB cable into Android 10 device and connect to a non-DoD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Ensure “No data transfer” is selected. If the MDM console device policy is not set to disable the capability to back up to a locally connected system or on the Android 10 device, the device policy is not set to disable the capability to back up to a locally connected system, this is a finding.
Configure the Google Android device to disable backup to locally connected systems. NOTE: On Restrictions, the backup features for Google are not in the framework. On the MDM console: 1. Open User restrictions. 2. Select "Disallow usb file transfer".
Review Google Android device configuration settings to determine if the capability to back up to a remote system has been disabled. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open User restrictions. 2. Ensure "Disallow backup servicer" is not selected. On the Android 10 device, do the following: 1. Go to Settings >> System. 2. Ensure Backup is set to "Off". If the MDM console device policy is not set to disable the capability to back up to a remote system or on the Android 10 device, the device policy is not set to disable the capability to back up to a remote system, this is a finding.
Configure the Google Android device to disable backup to remote systems (including commercial clouds). NOTE: On a Restrictions, data in the work profile cannot be backed up by default. On the MDM console: 1. Open User restrictions. 2. Ensure "Enable backup service" is not selected.
Review documentation on the Google Android device and inspect the configuration on the Google Android device to verify the access control policy that prevents [selection: application processes] from accessing [selection: all] data stored by other [selection: application processes] is enabled. This validation procedure is performed only on the MDM Administration Console. On the MDM console, do the following: 1. Open User restrictions. 2. Select "Disallow cross profile copy/paste". 3. Select "Disallow sharing data into the profile". If the MDM console device policy is not set to disable data sharing between profiles, this is a finding.
Configure the Google Android 10 to enable the access control policy that prevents [selection: application processes, groups of application processes] from accessing [selection: all, private] data stored by other [selection: application processes, groups of application processes]. NOTE: All application data is inherently sandboxed and isolated from other applications. In order to disable copy/paste on the MDM Console: 1. Open User restrictions. 2. Select "Disallow cross profile copy/paste". 3. Select "Disallow sharing data into the profile".
Review documentation on the Google Android device and inspect the configuration on the Google Android device to disable multi-user modes. This validation procedure is performed on both the MDM Administration Console and the Android 10 device. On the MDM console, do the following: 1. Open the User restrictions. 2. Open user settings. 3. Confirm "Disallow Add User" is selected. On the Android 10 device, do the following: 1. Go to Settings >> System >> Advanced >> Multiple users. 2. Ensure that there is no option to add a user. If the MDM console device policy is not set to disable multi-user modes or on the Android 10 device, the device policy is not set to disable multi-user modes, this is a finding.
Configure the Google Android 10 to disable multi-user modes. On the MDM console: 1. Open the User restrictions. 2. Open user settings. 3. Select "Disallow Add User".
Review documentation on the Google Android device and inspect the configuration on the Google Android device to enable audit logging. This validation procedure is performed on only on the MDM Administration Console. On the MDM console, do the following: 1. Open the User restrictions. 2. Open user settings. 3. Select "Enable security logging". 4. Select "Enable network logging". If the MDM console device policy is not set to enable audit logging, this is a finding.
Configure the Google Android 10 to enable audit logging. On the MDM console: 1. Open the User restrictions. 2. Open user settings. 3. Select "Enable security logging". 4. Select "Enable network logging".
Review Google Android device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: detected integrity violations. This validation procedure is performed only on the MDM Administration Console. On the MDM console, do the following: 1. Go to Policy management. 2. Confirm Security Logging is enabled. If the MDM console device policy is not set to enable security logging, this is a finding.
Configure the Google Android device to generate audit records for the following auditable events: detected integrity violations. On the MDM console, do the following: On the MDM Console: 1. Go to Policy management. 2. Enable Security Logging.
Review a sample of site User Agreements for Google device users or similar training records and training course content. Verify that Google device users have completed the required training. The intent is that required training is renewed on a periodic basis in a time period determined by the AO. If any Google device user has not completed the required training, this is a finding.
All Google device users must complete training on the following training topics. (Users must acknowledge that they have reviewed training via a signed User Agreement or similar written record): - Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. - Need to ensure no DoD data is saved to the personal space or transmitted from a personal app (for example, from personal email). - If the Purebred key management app is used, users are responsible for maintaining positive control of their credentialed device at all times. The DoD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and to report any loss of control so the credentials can be revoked. Upon device retirement, turn-in, or reassignment, ensure that a factory data reset is performed prior to device hand-off. Follow mobility service provider decommissioning procedures as applicable. - How to configure the following UBE controls (users must configure the control) on the Google device: **Secure use of Calendar Alarm **Local screen mirroring and Mirroring procedures (authorized/not authorized for use) **Do not upload DoD contacts via smart call and caller ID services **Do not remove DoD intermediate and root PKI digital certificates **Disable Wi-Fi Sharing **Do not configure a DoD network (work) VPN profile on any third-party VPN client installed in the personal space **If Bluetooth connections are approved for mobile device, types of allowed connections (for example car hands-free, but not Bluetooth wireless keyboard) - AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.) in the Google device personal space.
Review device configuration settings to confirm Wi-Fi Sharing is disabled. Mobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the Authorizing Official (AO) has not approved Mobile Hotspot, and it has been verified as disabled on the MDM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to verify Wi-Fi Sharing is disabled: On the MDM console: 1. Open the User restrictions setting. 2. Verify "Disallow config tethering" to on. On the Google Android 10 device, do the following: 1. Open Settings. 2. Tap "Networks & internet". 3. Verify that "Hotspots & tethering" is disabled. If on the Google Android 10 device "Wi-Fi sharing" is enabled, this is a finding.
Configure Google Android 10 to disable Wi-Fi Sharing. Mobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the AO has not approved Mobile Hotspot, and it has been disabled on the MDM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: On the MDM console: 1. Open the User restrictions setting. 2. Set "Disallow config tethering" to on.
Review device configuration settings to confirm that the DoD root and intermediate PKI certificates are installed. This procedure is performed on both the MDM Administration console and the Google Android 10 device. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet). On the MDM console verify that the DoD root and intermediate certificates are part of a device and/or work profile that is being pushed down to the devices. On the Google Android 10 device, do the following: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that DoD root and intermediate PKI certificates are listed under the User tab in the Work section. If on the MDM console the DoD root and intermediate certificates are not listed in a profile, or the Google Android 10 device does not list the DoD root and intermediate certificates under the user tab, this is a finding.
Configure Google Android 10 to install DoD root and intermediate certificates. On the MDM console upload DoD root and intermediate certificates as part of a device and/or work profile. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet).
Review the device configuration to confirm that the user is unable to remove DoD root and intermediate PKI certificates. On the MDM console: 1. Open the User restrictions setting. 2. Verify that "Disallow config credentials" to on for the work profile. On the Google Android 10 device, do the following: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that the user is unable to untrust or remove any work certificates. If on the Google Android 10 device the user is able to remove certificates, this is a finding.
Configure Google Android 10 to prevent a user from removing DoD root and intermediate PKI certificates. On the MDM console: 1. Open User restrictions. 2. Set "Disallow config credentials" to on for the work profile.
Review the Google Android 10 Work Profile configuration settings to confirm that users are prevented from adding personal email accounts to the work email app. This procedure is performed on both the MDM Administrator console and the Google Android 10 device. On the MDM console: 1. Open User restrictions. 2. Verify that "Disallow modify accounts" is set to on. On the Google Android 10 device, do the following: 1. Open Settings. 2. Tap "Accounts". 3. Verify that "Add account" is grayed out under the Work section. If on the MDM console the restriction to "Disallow modify accounts" is not set, or on the Google Android 10 device the user is able to add an account in the Work section, this is a finding.
Configure Google Android 10 Work Profile to prevent users from adding personal email accounts to the work email app. On the MDM console, for the Work Profile, do the following: 1. Open User restrictions. 2. Set "Disallow modify accounts" to on. Refer to the MDM documentation to determine how to provision users' work email accounts for the work email app.
Review the Google Android 10 Work Profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. What needs to happen is to verify only approved system apps have been placed on the core whitelist. This procedure is performed on the MDM Administrator console. Review the system app white list and verify only approved apps are on the list. If on the MDM console the system app white list contains unapproved core apps, this is a finding.
Configure Google Android 10 Work Profile to enforce the system application disable list. The required configuration is the default configuration when the device is enrolled. If the device configuration is changed, use the following procedure to bring the device back into compliance: On the MDM, configure a list of approved Google core and preinstalled apps in the core app white list.
Review that Google Android 10 is configured as Corporate Owned Work Managed. This procedure is performed on both the MDM Administrator console and the Google Android 10 device. On the MDM console, verify that the default enrollment is set to Corporate Owned Work Managed. On the Google Android 10 device, do the following: 1. Go to the application drawer. 2. Ensure a Personal tab and a Work tab are present. If on the MDM console the account the default enrollment is set to Corporate Owned Work Managed or on the Google Android 10 device the user does not see a Work tab, this is a finding.
Configure Google Android 10 in a Corporate Owned Work Managed configuration. On the MDM console, configure the default enrollment as Corporate Owned Work Managed. Refer to the MDM documentation to determine how to configure the device to enroll as Corporate Owned Work Managed.
Review Chrome Browser in Google Android 10 Work Profile autofill setting. This procedure is performed only on the MDM Administrator console. On the MDM console, for the Work Profile, do the following: 1. Open the Chrome Browser Settings. 2. Verify "Enable autofill" is set to off. If on the MDM console autofill is set to on in the Chrome Browser Settings, this is a finding.
Configure Chrome Browser in Google Android 10 Work Profile to disable autofill. On the MDM console, for the Work Profile, do the following: 1. Open the Chrome Browser Settings. 2. Set "Enable autofill" to off. Refer to the MDM documentation to determine how to configure Chrome Browser Settings.
Review the Google Android 10 Workspace configuration settings to confirm that autofill services are disabled. This procedure is performed only on the MDM Administration console. On the MDM console, for the Workspace, in the "Android user restrictions" group, under the work profile, verify that "disallow autofill" is selected. If on the MDM console "disallow autofill" is selected, this is a finding.
Configure Google Android 10 Workspace to disable the autofill services. On the MDM console, in the Android work profile restrictions, select "disallow autofill".
Review the Google Android 10 Work Profile configuration settings to confirm that autofill services are disabled. This procedure is performed on both the MDM Administration console and the Google Android 10 device. On the MDM console, verify that "Set auto (network) time required to on" is selected. On the Google Android 10 device, do the following: 1. Open Settings. 2. Tap "System". 3. Tap "Date & times". 4. Verify that "User network-provided time" is grayed out. If on the MDM console "Set auto (network) time required" to "on", or on the Google Android 10 device "User network-provided time" is grayed out, this is a finding.
Configure Google Android 10 Work Profile to set auto network time. On the MDM console, in the Android user restrictions section, select "Set auto (network) time required" to on".
Review device configuration settings to confirm that the Google Android device recently released version of Google Android 10 is installed. This procedure is performed on both the MDM console and the Google Android 10 device. In the MDM management console, review the version of Google Android 10 installed on a sample of managed devices. This procedure will vary depending on the MDM product. On the Google Android 10 device, to see the installed operating system version: 1. Open Settings. 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Android operating system on any reviewed Google devices is not the latest released by Google, this is a finding. Google's Android operating system patch website: https://source.android.com/security/bulletin/
Install the latest released version of the Google Android 10 operating system on all managed Google devices. Note: Google Android device operating system updates are released directly by Google or can be distributed via the MDM.
Review device configuration settings to confirm that no third-party keyboards are enabled. This procedure is performed on both the MDM console and the Google Android 10 device. In the MDM management console, review the user restrictions section. Select "Set input methods" and insure no third-party keyboards are installed. On the Google Android 10 device, to see if a third-party keyboard is enabled: 1. Open Settings>>System>>Languages & input. 2. Tap "Virtual keyboard". 3. Tap "Manage keyboard". 4. Ensure no third-party keyboards are listed, or if third-party keyboards are present they are "Disabled by admin". If third-party keyboards are enabled, this is a finding. Google's Android operating system patch website: https://source.android.com/security/bulletin/
Configure Google Android 10 device to disallow the use of third-party keyboards. On the MDM console, in the Android user restrictions section, select "Set input methods" and ensure no third-party keyboards are installed.