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
Inspect the configuration on the managed Google Android 12 device to enable audit logging. This validation procedure is performed only on the EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Verify that "Enable security logging" is toggled to ON. If the EMM console device policy is not set to enable audit logging, this is a finding.
Configure the Google Android 12 device to enable audit logging. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Toggle "Enable security logging" to ON.
Review managed Google Android 12 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 EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Verify that Numeric Complex, Alphabetic, Alphanumeric, or Complex is selected. 5. Open "Minimum password length". 6. Verify that "6" is set for number of characters. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify that "Minimum password quality" is set to Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Verify the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 12 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Tap "Pin or Password". 4. Verify Password length required is at least "6". If the device password length is not set to six characters or more on EMM console or on the managed Google Android 12 device, this is a finding.
Configure the Google Android 12 device to enforce a minimum password length of six characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Enter in the number of characters as "6". COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Open "Minimum password quality". 5. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 6. Open "Minimum password length". 7. Enter in the number of characters as "6".
Review managed Google Android 12 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 EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Verify that quality is set to "Numeric (Complex)" or higher. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify that quality is set to "Numeric (Complex)" or higher. ____________________________ On the managed Google Android 12 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Select "PIN". 4. Try to enter a new PIN with repeating numbers. 5. Verify Password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed. If the EMM console device policy is set to a password with more than two repeating or sequential characters or on the managed Google Android 12 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 12 device to prevent passwords from containing more than two repeating or sequential characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Set password quality to "Numeric (Complex)". COPE: 1. Open "Password constraints". 2. Select "Personal Profile". 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 managed Google Android 12 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 EMM Administration Console and the managed Google Android 12 device. On the EMM Console: COBO 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Max time to screen lock" is set to any number desired, the units are in seconds. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Verify that "Max time to screen lock" is set to any number desired, the units are in seconds. ___________________________ On the managed Google Android 12 device: COBO and COPE: 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 EMM 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 managed Google Android 12 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 12 device to enable a screen-lock policy that will lock the display after a period of inactivity. On the EMM Console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Set "Max time to screen lock" to any number desired. Note: The units are in seconds. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Set "Max time to screen lock" to any number desired. Note: The units are in seconds.
Review managed 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 15 minutes or less of inactivity. Note: Google Android 12 does not support the 15 minute increment. The available allowable selection is 10 mins then increases to 30 minutes. Therefore, the control should be set to 10 minutes. This validation procedure is performed on both the EMM Administration Console and the Android 12 device. On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Max time to screen lock" is set to 600. Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Max time to screen lock" is set to 600. Note: The units are in seconds. On the managed Google Android 12 device: COBO and COPE: 1. Open Settings >> Display. 2. Tap "Screen timeout". 3. Ensure the Screen timeout value is set to 600 seconds. If the EMM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity of 600 seconds, this is a finding.
Configure the Google Android 12 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: Google Android 12 does not support the 15 minute increment. The available allowable selection is 10 mins then increases to 30 minutes. Therefore, the control will be set to 10 minutes. On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Set "Max time to screen lock" to 600. Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Set "Max time to screen lock" to 600. Note: The units are in seconds.
Review managed Google Android 12 device configuration settings to determine if the mobile device has the maximum number of consecutive failed authentication attempts set at ten or fewer. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 12 device. On the EMM Console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. _________________________ On the managed Google Android 12 device: COBO and COPE: 1. Lock the device screen. 2. Attempt to unlock the screen and validate that the device autowipes after specified number of invalid entries. Note: Perform this verification only with a test phone set up with a production profile. If the EMM console device policy is not set to the maximum number of consecutive failed authentication attempts at ten or fewer, or if on the managed Google Android 12 device the device policy is not set to the maximum number of consecutive failed authentication attempts at ten or fewer, this is a finding.
Configure the Google Android 12 device to allow only 10 or fewer consecutive failed authentication attempts. On the EMM Console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Set "Max password failures for local wipe" to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Set "Max password failures for local wipe" to a number between 1 and 10.
Review managed Google Android 12 device configuration settings to determine if the mobile device has only approved application repositories (DoD-approved commercial app repository, EMM server, and/or mobile application store). This validation procedure is performed on both the EMM Administration Console and the managed Google Android 12 device. On the EMM Console: COBO and COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow install unknown sources" is toggled to ON. 3. Verify that "Disallow installs from unknown sources globally" is toggled to ON. On the Google Android 12 device: COBO and COPE: 1. Open Settings >> Apps >> 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 EMM console device policy is not set to allow connections to Only approved application repositories or on the managed Google Android 12 device, the device policy is not set to allow connections to Only approved application repositories, this is a finding.
Configure the Google Android 12 device to disable unauthorized application repositories. On the EMM Console: COBO and COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow install unknown sources" to ON. 3. Toggle "Disallow installs from unknown sources globally" to ON.
Review managed Google Android 12 device configuration settings to determine if the mobile device has an application allowlist configured. Verify all applications listed on the allowlist have been approved by the Approving Official (AO). On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Verify all selected apps are AO approved. On the managed Google Android 12 device: COBO and COPE: 1. Open the managed Google Play Store. 2. Verify that only the approved apps are visible. Note: Managed Google Play is an allowed App Store. If the EMM console list of selected managed Google Play apps includes non-approved apps, this is a finding. Note: The application allowlist 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 12 device to use an application allowlist. On the EMM Console: COBO and COPE: 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 an allowed App Store.
Review managed Google Android 12 device configuration settings to determine if the mobile device has an application allowlist configured and that the application allowlist 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 EMM Administration Console. On the EMM console: 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 EMM console device policy includes applications with unauthorized characteristics, this is a finding.
Configure the Google Android 12 device application allowlist 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 EMM 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.
Review managed Google Android 12 device settings to determine if the Google Android 12 device displays (work profile) 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 EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Disable unredacted notifications" is toggled to ON. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Verify that "Disable unredacted notifications" is toggled to ON. ___________________________ On the managed Google Android 12 device: COBO: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "Privacy". 3. Verify that "Show sensitive content only when unlocked" is selected. COPE: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "When work profile is locked". 3. Verify that "Hide sensitive work content" is selected. If the EMM console device policy allows work notifications on the lock screen, or the managed Google Android 12 device allows work notifications on the lock screen, this is a finding.
Configure the Google Android 12 device to not display (work profile) notifications when the device is locked. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Toggle "Disable unredacted notifications". COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Toggle "Disable unredacted notifications".
Review device configuration settings to confirm that trust agents are disabled. This procedure is performed on both the EMM Administration console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Disable trust agents" is toggled to ON. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Disable trust agents" is toggled to ON. 4. Select "Work Profile". 5. Verify that "Disable trust agents" is toggled to ON. ____________________________ On the managed Google Android 12 device: COBO and COPE: 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 EMM console, "disable trust agents" is not selected, or on the managed Google Android 12 device a trust agent can be enabled, this is a finding.
Configure the Google Android 12 device to disable trust agents. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Toggle "Disable trust agents" to ON. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Toggle "Disable trust agents" to ON. 4. Select "Work Profile". 5. Toggle "Disable trust agents" to ON.
Review managed Google Android 12 device configuration settings to determine whether a developer mode is enabled. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 12 device. On the EMM Console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to ON. COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to ON. 3. Open "Set user restrictions on parent". 4. Verify that "Disallow debugging features" is toggled to ON. ____________________________ On the managed Google Android 12 device: COBO and COPE: 1. Go to Settings >> System. 2. Ensure "Developer Options" is not listed. 3. Go to Settings >> About Phone. 4. Tap on the Build Number to try to enable Developer Options and validate that action is blocked. If the EMM console device policy is not set to disable developer mode or on the managed Google Android 12 device, the device policy is not set to disable developer mode, this is a finding.
Configure the Google Android 12 device to disable developer modes. On the EMM Console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to ON. COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to ON. 3. Open "Set user restrictions on parent". 4. 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 Discussion): 1. By placing the DoD warning banner text in the user agreement signed by each managed Android 12 device user (preferred method) 2. By configuring the warning banner text on the EMM console and installing the banner on each managed Android 12 mobile device Determine which method is used at the Google Android 12 device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Google Android 12 device users and verify the agreement includes the required DoD warning banner text. Validation Procedure for Method #2: On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Verify the message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Verify the message. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the EMM console device policy is not set to display a warning banner with the appropriate designated wording or on the managed Google Android 12 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 Discussion): 1. By placing the DoD warning banner text in the user agreement signed by each Google Android 12 device user (preferred method) 2. By configuring the warning banner text on the EMM console and installing the banner on each Google Android 12 mobile device On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Enter in message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Enter in message.
Review managed Google Android 12 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 EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Verify that "Enable security logging" is toggled to ON. If the EMM console device policy is not set to enable security logging, this is a finding.
Configure the Google Android 12 device to generate audit records for the following auditable events: detected integrity violations. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Toggle "Enable security logging" to ON.
Review managed Google Android 12 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 EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow USB file transfer" is toggled to ON. COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Verify that "Disallow USB file transfer" is toggled to ON. ______________________________ On the managed Google Android 12 device: 1. Plug a USB cable into the managed Google Android 12 device and connect to a non-DoD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify that "No data transfer" is selected. If the EMM console device policy is not set to disable USB mass storage mode or on the managed Google Android 12 device, the device policy is not set to disable USB mass storage mode, this is a finding.
Configure the Google Android 12 device to disable USB mass storage mode. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow USB file transfer" to ON. COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Toggle "Disallow USB file transfer" to ON.
Review managed Google Android 12 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 EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify that "Enable backup service" is toggled to OFF. On the managed Google Android 12 device: COBO: 1. Go to Settings >> System >> Backup. 2. Verify that Backup settings is "Not available". COPE: 1. Go to Settings >> System >> Backup. 2. Select "Work". 3. Verify that Backup settings is "Not available". If the EMM console device policy is not set to disable the capability to back up to a locally connected system or on the managed Google Android 12 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 12 device to disable backup to locally connected systems. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to OFF.
Review managed Google Android 12 device configuration settings to determine if the capability to back up to a remote system has been disabled. Note: Since personal accounts cannot be added to the work profile (GOOG-12-010100), this control only impacts personal profile accounts. Site can allow backup based on local policy. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify that "Enable backup service" is toggled to OFF. On the managed Google Android 12 device: COBO: 1. Go to Settings >> System >> System >> Backup. 2. Verify that Backup settings is "Not available". COPE: 1. Go to Settings >> System >> System >> Backup. 2. Select "Work". 3. Verify that Backup settings is "Not available". If the EMM console device policy is not set to disable the capability to back up to a remote system or on the managed Google Android 12 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 12 device to disable backup to remote systems (including commercial clouds). On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to OFF. Note: Since personal accounts cannot be added to the work profile (GOOG-12-010100), this control only impacts personal profile accounts. Site can allow backup based on local policy.
Review documentation on the managed Google Android 12 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 EMM Administration Console. On the EMM console: COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow cross profile copy/paste" is toggled to ON. 4. Verify that "Disallow sharing data into the profile" is toggled to ON. If the EMM console device policy is not set to disable data sharing between profiles, this is a finding.
Configure the Google Android 12 device 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 EMM Console: COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow cross profile copy/paste" to ON. 4. Toggle "Disallow sharing data into the profile" to ON.
Review documentation on the managed Google Android 12 device and inspect the configuration on the Google Android device to disable multi-user modes. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 12 device. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow modify accounts" is toggled to ON. On the managed Google Android 12 device: COBO and COPE: 1. Go to Settings >> Passwords & accounts >> Accounts for Owner. 2. Tap "Add account". 3. Verify that the action is not allowed. If the EMM console device policy is not set to disable multi-user modes or on the managed Google Android 12 device, the device policy is not set to disable multi-user modes, this is a finding.
Configure the Google Android 12 device to disable multi-user modes. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow modify accounts" to ON.
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 EMM console: COBO: 1. Open "User restrictions" section. 2. Verify that "Disallow Bluetooth" is toggled to ON. COPE: 1. Open "User restrictions on parent" section. 2. Verify that "Disallow Bluetooth" is toggled to ON. On the managed Google Android 12 device: COBO and COPE: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Verify that "Use Bluetooth" is set to OFF and cannot be toggled to ON. If the AO has approved the use of Bluetooth, on the managed Android 12 device: 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 EMM-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 12 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 (UBE). To disable Bluetooth use the following procedure: On the EMM Console: COBO: 1. Open "User restrictions" section. 2. Toggle "Disallow Bluetooth" to ON. COPE: 1. Open "User restrictions on parent" section. 2. Toggle "Disallow Bluetooth" to ON. The user training requirement is satisfied in requirement GOOG-12-009800.
Review the managed Google Android 12 device configuration settings to determine if the mobile device is configured to disable ad hoc wireless client-to-client connection capability. This validation procedure is performed on both the MDM Administration console and the managed Google Android 12 device. On the MDM console: COBO: 1. Open "Settings Management". 2. Verify that "Set location" is toggled to OFF. COPE: 1. Open "User restrictions on parent". 2. Verify that "Disallow config location" is toggled to ON. 3. Verify that "Disallow share location" is toggled to ON. On the managed Google Android 12 device: COBO and COPE: 1. Go to Settings >> Network & Internet >> Network preferences. 2. Verify that "Wi-Fi Direct" is greyed out and unavailable. If the EMM console device policy is not set to disable Location sharing and configuration, this is a finding.
Configure the Google Android 12 device to disable ad hoc wireless client-to-client connection capability. On the MDM console: COBO: 1. Open "Settings Management". 2. Toggle "Set location" to OFF. COPE: 1. Open "User restrictions on parent". 2. Toggle "Disallow config location" to ON. 3. Toggle "Disallow share location" to ON. Note: Wi-Fi Direct and ad hoc requires Location services to function; therefore, disabling this setting will disable the ad hoc and Wi-Fi Direct feature.
Review a sample of site User Agreements for Google Android 12 device users or similar training records and training course content. Verify that the Google Android 12 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 Android 12 device user has not completed the required training, this is a finding.
All Google Android 12 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) **How to perform a full device wipe - 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 EMM 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 EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow config tethering" is toggled to ON. COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to ON. On the managed Google Android 12 device: COBO and COPE: 1. Go to Settings >> Network & Internet. 2. Verify that "Hotspot & tethering" is "Controlled by admin". 3. Verify that tapping "Hotspot & tethering" provides a prompt to the user specifying "Action not allowed". If on the managed Google Android 12 device "Hotspot & tethering" is enabled, this is a finding.
Configure the Google Android 12 device 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 EMM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config tethering" to ON. COPE: 1. Open "Set user restrictions on parent". 2. Toggle "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 EMM Administration console and the managed Google Android 12 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 EMM 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 managed Google Android 12 device: 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 EMM console the DoD root and intermediate certificates are not listed in a profile, or the managed Android 12 device does not list the DoD root and intermediate certificates under the user tab, this is a finding.
Configure the Google Android 12 device to install DoD root and intermediate certificates. On the EMM 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 managed Google Android 12 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 EMM Administrator console and the managed Google Android 12 device. COPE: On the EMM console: 1. Open "Set user restrictions". 2. Verify that "Disallow modify accounts" is toggled to ON. On the managed Google Android 12 device: 1. Open Settings. 2. Tap "Passwords & accounts". 3. Select "Work". 4. Tap "Add account". 5. Verify that message is displayed to the user stating "Action not allowed". If on the EMM console the restriction to "Disallow modify accounts" is not set, or on the managed Android 12 device the user is able to add an account in the Work section, this is a finding.
Configure the Google Android 12 device to prevent users from adding personal email accounts to the work email app. On the EMM console: COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow modify accounts" to ON. Refer to the EMM documentation to determine how to provision users' work email accounts for the work email app.
Review the managed Google Android 12 Work Profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. Verify only approved system apps have been placed on the core allowlist. This procedure is performed on the EMM Administrator console. Review the system app allowlist and verify only approved apps are on the list. COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Verify that package names of apps are listed. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Verify that package names of apps are listed. If on the EMM console the system app allowlist contains unapproved core apps, this is a finding.
Configure the Google Android 12 device 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 EMM console: COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Enter package names of apps to hide. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Enter package names of apps to hide. Configure a list of approved Google core and preinstalled apps in the core app allowlist.
Review that managed Google Android 12 is configured as Corporate Owned Work Managed. This procedure is performed on both the EMM Administrator console and the managed Google Android 12 device. On the EMM console, configure the default enrollment as Corporate Owned and select "Use for Work & Personal". On the managed Google Android 12 device: 1. Go to the application drawer. 2. Ensure a Personal tab and a Work tab are present. If on the EMM console the account the default enrollment is set to Corporate Owned Work Managed or on the managed Android 12 device the user does not have a Work tab, this is a finding.
Configure the Google Android 12 device as corporate owned with a work profile. On the EMM console, configure the default enrollment as Corporate Owned, and select "Use for Work & Personal". Refer to the EMM documentation to determine how to configure the device.
Review the work profile Chrome Browser app on the Google Android 12 autofill setting. This procedure is performed only on the EMM Administrator console. On the EMM console: COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify that "SearchSuggestEnabled" is turned OFF. If on the EMM console autofill is set to On in the Chrome Browser Settings, this is a finding.
Configure the Chrome browser on the Google Android 12 device Work Profile to disable autofill. On the EMM console: COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "SearchSuggestEnabled" is turned OFF. Refer to the EMM documentation to determine how to configure Chrome Browser Settings.
Review the Google Android 12 work profile configuration settings to confirm that autofill services are disabled. This procedure is performed only on the EMM Administration console. On the EMM console: COPE: 1. Open "Set user restrictions". 2. Verify that "Disable autofill" is toggled to ON. If on the EMM console "disallow autofill" is not selected, this is a finding.
Configure the Google Android 12 device work profile to disable the autofill services. On the EMM console: COPE: 1. Open "Set user restrictions". 2. Toggle "Disable autofill" to ON.
Review the managed Google Android 12 device configuration settings to confirm that autofill services are disabled. This procedure is performed on both the EMM Administration console and the managed Google Android 12 device. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow config date time" is toggled to ON. COPE: 1. Open "Set user restrictions on parent". 2. Verify that "Disallow config date time" is toggled to ON. On the managed Google Android 12 device: COBO and COPE: 1. Open Settings. 2. Tap "System". 3. Tap "Date & times". 4. Verify that "Set time automatically" is grayed out and is "Enabled by admin". If on the EMM console "Disallow config date time" is not set to On, or on the managed Android 12 device "User network-provided time" is not grayed out, this is a finding.
Configure the Google Android 12 device to set auto network time. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config date time" to ON. COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config date time" to ON.
Review device configuration settings to confirm the Google Android device has the mobile operating system (MOS)t recently released version of managed Google Android 12 installed. This procedure is performed on both the EMM console and the managed Google Android 12 device. In the EMM management console, review the version of Google Android 12 installed on a sample of managed devices. This procedure will vary depending on the EMM product. On the managed Google Android 12 device, to determine the installed operating system version: COBO and COPE: 1. Open Settings. 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Google Android 12 operating system on any reviewed 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/ Android versions for Pixel devices: https://developers.google.com/android/images
Install the latest released version of the Google Android 12 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 EMM. Check each device manufacturer and/or Carriers for current updates.
Review the managed Google Android 12 configuration settings to confirm that no third-party keyboards are enabled. This procedure is performed on the EMM console. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Verify only the approved keyboards are selected. If third-party keyboards are allowed, this is a finding.
Configure the Google Android 12 device to disallow the use of third-party keyboards. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Select only the approved keyboard. Additionally, Admins can configure application allowlists for Google Play that does not have any third-party keyboards for user installation.
Review the managed Google Android 12 configuration settings to confirm CC mode is enabled. This procedure is performed on the EMM console. COBO and COPE: 1. Open Device owner management. 2. Verify that "Enable Common Criteria mode" is toggled to ON. If CC mode is not enabled, this is a finding.
Configure the Google Android 12 device to implement CC Mode. On the EMM console: COBO and COPE: 1. Open Device owner management. 2. Toggle "Enable Common Criteria mode" to ON.
Review the device configuration to confirm that the user is unable to remove DoD root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Verify that "Disallow config credentials" is toggled to ON. On the Google Android 12 device: 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 12 device the user is able to remove certificates, this is a finding.
Configure Google Android 12 device to prevent a user from removing DoD root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions".. 2. Toggle "Disallow config credentials" to ON.
Review the device configuration to confirm that the USB port is disabled except for charging the device. On the EMM console: 1. Open "Set user restrictions".. 2. Verify that "Enable USB" is toggled to OFF. If on EMM console the USB port is not disabled, this is a finding.
Configure Google Android 12 device to disable the USB port (except for charging the device). COPE and COBO: On the EMM console: 1. Open "Set user restrictions".. 2. Toggle "Enable USB" to OFF.