BaselineWatch
5 STIGs
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

Mobile STIGs

5 STIGs followed · All platforms
All 44 CAT I 2CAT II 35CAT III 7 Browse in the Register

CAT II 35

Any vulnerability, the exploitation of which has a potential to result in loss of confidentiality, availability or integrity.

  1. GOOG-17-005000 CAT II V-284689 · PP-MDF-401490

    Google Android 17 must be configured to enforce a minimum password length of six characters.

    Maps to IA-5(1) via CCI-004066
    Check

    Review managed Google Android 17 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 17 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 the number of characters is set to "6". 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 that the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 17 device: COBO and COPE: 1. Open Settings >> Security & privacy >> Device unlock >> Screen lock. 2. Enter current password. 3. Tap "Pin or Password". 4. Verify that password length required is at least "6". If the device password length is not set to six characters or more on the EMM console or on the managed Google Android 17 device, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: setPasswordMinimumLength

  2. GOOG-17-005100 CAT II V-284690 · PP-MDF-401500

    Google Android 17 must be configured to not allow passwords that include more than four repeating or sequential characters.

    Maps to IA-5(1) via CCI-004066
    Check

    Review managed Google Android 17 device configuration settings to determine if the mobile device is prohibiting passwords with more than four repeating or sequential characters. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 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 17 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Select "PIN". 4. Try to enter a new PIN using repeating numbers. 5. Verify that 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 if on the managed Google Android 17 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.

    Fix

    Configure the Google Android 17 device to prevent passwords from containing more than four 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. Configuration API: setRequiredPasswordComplexity

  3. GOOG-17-005200 CAT II V-284691 · PP-MDF-401510

    Google Android 17 must be configured to lock the display after 15 minutes (or less) of inactivity.

    Maps to AC-11 via CCI-000057
    Check

    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: The Google Android 17 settings user interface (UI) does not support the 15-minute increment, but this value can be set by the MDM. This validation procedure is performed on the EMM administration console. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Max time to screen lock" is set to "900". 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 "900". Note: The units are in 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 900 seconds, this is a finding.

    Fix

    Configure the Google Android 17 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: The Google Android 17 settings UI does not support the 15-minute increment, but this value can be set by the MDM. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Set "Max time to screen lock" to "900". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Set "Max time to screen lock" to "900". Note: The units are in seconds. Configuration API: setMaximumTimeToLock

  4. GOOG-17-005300 CAT II V-284692 · PP-MDF-401520

    Google Android 17 must be configured to not allow more than 10 consecutive failed authentication attempts.

    Maps to AC-7 via CCI-000044
    Check

    Review managed Google Android 17 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 EMM administration console and the managed Google Android 17 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 17 device: COBO and COPE: 1. Lock the device screen. 2. Attempt to unlock the screen and validate that the device autowipes after the 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 for a maximum number of consecutive failed authentication attempts of 10 or fewer, or if on the managed Google Android 17 device the device policy is not set for a maximum number of consecutive failed authentication attempts of 10 or fewer, this is a finding.

    Fix

    Configure the Google Android 17 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. Configuration API: setMaximumFailedPasswordsForWipe()

  5. GOOG-17-005400 CAT II V-284693 · PP-MDF-401530

    Google Android 17 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DoW-approved commercial app repository, MDM server, mobile application store].

    Maps to CM-6 via CCI-000366
    Check

    Review managed Google Android 17 device configuration settings to determine if the mobile device has only approved application repositories (DoW-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 17 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 17 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 17 device the device policy is not set to allow connections to only approved application repositories, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: DISALLOW_INSTALL_UNKNOWN_SOURCES

  6. GOOG-17-005500 CAT II V-284694 · PP-MDF-401540

    Google Android 17 must be configured to enforce an application installation policy by specifying an application allow list that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version].

    Maps to CM-7(2) via CCI-001764
    Check

    Review managed Google Android 17 device configuration settings to determine if the mobile device has an application allow list configured. Verify that all applications listed on the allow list have been approved by the authorizing official (AO). On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Verify that all selected apps are AO-approved. On the managed Google Android 17 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 nonapproved apps, this is a finding. Note: The application allow list will include approved core applications (included in the OS by the OS vendor) and preinstalled 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 preinstalled applications. For Google Android, there are no preinstalled applications.

    Fix

    Configure the Google Android 17 device to use an application allow list. 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.

  7. GOOG-17-005600 CAT II V-284695 · PP-MDF-401550

    Google Android 17 allow list must be configured to not include applications with the following characteristics: - Backs up MD data to non-DoW cloud servers (including user and application access to cloud backup services); - Transmits MD diagnostic data to non-DoW 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 process…

    Maps to IA-7 via CCI-000803
    Check

    Review managed Google Android 17 device configuration settings to determine if the mobile device has an application allow list configured. Verify that all applications listed on the allow list have been approved by the authorizing official (AO). On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Verify that all selected apps are AO-approved. On the managed Google Android 17 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 nonapproved apps, this is a finding. Note: The application allow list will include approved core applications (included in the OS by the OS vendor) and preinstalled 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 preinstalled applications. For Google Android, there are no preinstalled applications.

    Fix

    Configure the Google Android 17 device to use an application allow list. 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.

  8. GOOG-17-005700 CAT II V-284696 · PP-MDF-401550

    Google Android 17 allow list must be configured to not include artificial intelligence (AI) applications that process device data in the cloud, including Google Gemini.

    Maps to IA-7 via CCI-000803
    Check

    Review managed Google Android 17 device configuration settings to determine if the mobile device has an AI application that processes device data in the cloud, including Google Gemini. 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. Verify no AI applications that process device data in the cloud, including Google Gemini, are listed. If the EMM console device policy includes AI applications that process device data in the cloud, including Google Gemini, this is a finding. Note: This restriction does not include Gemini Nano. Gemini Nano is a built-in capability of Android 17 and processes device data on the device. Refer to the STIG Supplemental document, Section 2, Artificial Intelligence Restrictions, for more information.

    Fix

    Configure the Google Android 17 device application allow list to exclude AI applications that process device data in the cloud, including Google Gemini. Note: This restriction does not include Gemini Nano. Gemini Nano is a built-in capability of Android 17 and processes device data on the device. Refer to the STIG Supplemental document, Section 2, Artificial Intelligence Restrictions, for more information.

  9. GOOG-17-005800 CAT II V-284697 · PP-MDF-401560

    Google Android 17 must be configured to not display the following (work profile) notifications when the device is locked: [selection: - Email notifications - Calendar appointments - Contact associated with phone call notifications - Text message notifications - Other application-based notifications - All notifications].

    Maps to AC-11(1) via CCI-000060
    Check

    Review managed Google Android 17 device settings to determine if the Google Android 17 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 A\administration C\console and the managed Google Android 17 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 17 device: COBO: 1. Go to Settings >> Display & touch >> Lock screen. 2. Tap on "Privacy". 3. Verify that "Show sensitive content only when unlocked" is selected. COPE: 1. Go to Settings >> Display & touch >> 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 17 device allows work notifications on the lock screen, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS

  10. GOOG-17-006200 CAT II V-284701 · PP-MDF-401590

    Google Android 17 must be configured to disable trust agents.

    Maps to IA-2(1) via CCI-000765
    Check

    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 17 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 17 device: COBO and COPE: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 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 17 device a trust agent can be enabled, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: KEYGUARD_DISABLE_TRUST_AGENTS

  11. GOOG-17-006400 CAT II V-284703 · PP-MDF-401610

    Google Android 17 must be configured to disable developer modes.

    Maps to CM-7 via CCI-000381
    Check

    Review managed Google Android 17 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 17 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 17 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 17 device the device policy is not set to disable developer mode, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: DISALLOW_DEBUGGING_FEATURES

  12. GOOG-17-006600 CAT II V-284705 · PP-MDF-401630

    Google Android 17 must be configured to enable audit logging.

    Maps to AU-6(4) via CCI-000154
    Check

    Inspect the configuration on the managed Google Android 17 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 the "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.

    Fix

    Configure the Google Android 17 device to enable audit logging. On the EMM console: COBO and COPE: 1. Open the "Device owner management" section. 2. Toggle "Enable security logging" to "ON". Configuration API: setSecurityLoggingEnabled

  13. GOOG-17-006900 CAT II V-284708 · PP-MDF-401660

    Google Android 17 must be configured to generate audit records for the following auditable events: Detected integrity violations.

    Maps to AU-12 via CCI-000169
    Check

    Review managed Google Android 17 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 the "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.

    Fix

    Configure the Google Android 17 device to generate audit records for the following auditable events: Detected integrity violations. On the EMM console: COBO and COPE: 1. Open the "Device owner management" section. 2. Toggle "Enable security logging" to "ON". Configuration API: setSecurityLoggingEnabled

  14. GOOG-17-007000 CAT II V-284709 · PP-MDF-401670

    Google Android 17 must be configured to disable USB mass storage mode.

    Maps to SC-41 via CCI-002546
    Check

    Review managed Google Android 17 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 17 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 17 device: 1. Plug a USB cable into the managed Google Android 17 device and connect to a non-DoW 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 17 device the device policy is not set to disable USB mass storage mode, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: DISALLOW_MOUNT_PHYSICAL_MEDIA, DISALLOW_USB_FILE_TRANSFER

  15. GOOG-17-007100 CAT II V-284710 · PP-MDF-401680

    Google Android 17 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.

    Maps to SC-4 via CCI-001090
    Check

    Review managed Google Android 17 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 17 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 17 device: 1. Plug a USB cable into the managed Google Android 17 device and connect to a non-DoW 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 17 device the device policy is not set to disable USB mass storage mode, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: DISALLOW_MOUNT_PHYSICAL_MEDIA, DISALLOW_USB_FILE_TRANSFER

  16. GOOG-17-007200 CAT II V-284711 · PP-MDF-401690

    Google Android 17 must be configured to not allow backup of [all applications, configuration data] to remote systems.

    Maps to SC-4 via CCI-001090
    Check

    Review managed Google Android 17 device configuration settings to determine if the capability to back up to a remote system has been disabled. Note: Because personal accounts cannot be added to the work profile (GOOG-17-008300), this control impacts only personal profile accounts. Sites can allow backup based on local policy. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 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 17 device: COBO: 1. Go to Settings >> Accounts & backup. 2. Verify that Backup settings is "Not available". COPE: 1. Go to Settings >> Accounts & 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 17 device the device policy is not set to disable the capability to back up to a remote system, this is a finding.

    Fix

    Configure the Google Android 17 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: Because personal accounts cannot be added to the work profile (GOOG-17-008700), this control impacts only personal profile accounts. Sites can allow backup based on local policy. Configuration API: setBackupServiceEnabled

  17. GOOG-17-007300 CAT II V-284712 · PP-MDF-401700

    Google Android 17 must be configured to enable authentication of personal hotspot connections to the device using a preshared key.

    Maps to AC-17(1), AC-18(1) via CCI-001443, CCI-002314
    Check

    This is a User-Based Enforcement (UBE) control. Check a sample of Pixel phones at the site and verify that the Wi-Fi hotspot preshared key (password) is set to "WPA3-Personal". 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. To the left of the slide, tap on "Wi-Fi Hotspot" to bring up the configuration options. 4. Click on the "Security" link and verify that "WPA3-Personal" is selected. If the Wi-Fi hotspot security is not set to "WPA3-Personal", this is a finding.

    Fix

    This is a UBE control. Train users to not change the default Wi-Fi hotspot security setting: 15-character complex Wi-Fi hotspot preshared key (password) ("WPA3-Personal"). (GOOG-17-008300) If the required preshared key is not set up, train users to use the following procedure to configure the required setting: 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. To the left of the slide, tap on "Wi-Fi Hotspot" to bring up the configuration options. 4. Click on the "Security" link and select "WPA3-Personal".

  18. GOOG-17-007600 CAT II V-284714 · PP-MDF-401730

    Google Android 17 must be configured to disable multiuser modes.

    Maps to AC-2 via CCI-002110
    Check

    Review documentation on the managed Google Android 17 device and inspect the configuration on the Google Android device to disable multiuser modes. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 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 17 device: COBO and COPE: 1. Go to Settings >> Accounts and backup. 2. Tap "Add account" (work profile). 3. Verify that the action is not allowed. If the EMM console device policy is not set to disable multiuser modes, or on the managed Google Android 17 device the device policy is not set to disable multiuser modes, this is a finding.

    Fix

    Configure the Google Android 17 device to disable multiuser modes. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow modify accounts" to "ON". Configuration API: DISALLOW_MODIFY_ACCOUNTS

  19. GOOG-17-008100 CAT II V-284719 · PP-MDF-401770

    Google Android 17 must be configured to disable ad hoc wireless client-to-client connection capability.

    Maps to SC-40 via CCI-002536
    Check

    Review the configuration to determine if the Google Android devices are disallowing Wi-Fi Direct. This validation procedure is performed on both the management tool and the Google Android device. On the management tool in the user restrictions, verify that "Wi-Fi Direct" has been set to "Disallow": COBO: 1. Find "User Restrictions" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and verify that it is set to "ON". COPE: 1. Find "User Restrictions on Parent" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and verify that it is set to "ON". On the Google Android device: 1. Open Settings >> Connections >> Wi-Fi. 2. From the hamburger menu, select Wi-Fi Direct. 3. Verify that Wi-Fi Direct cannot be selected. If on the management tool "Wi-Fi Direct" is not set to "Disallow", or on the Google Android device a Wi-Fi Direct device is listed that can be connected to, this is a finding.

    Fix

    Configure the Google Android devices to disallow Wi-Fi Direct. On the management tool, do the following: COBO: 1. Find "User Restrictions" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and toggle that to "ON". COPE: 1. Find "User Restrictions on Parent". 2. Scroll down to "Disallow Wi-Fi Direct" and toggle that to "ON". Configuration API: DISALLOW_WIFI_DIRECT

  20. GOOG-17-008300 CAT II V-284721 · PP-MDF-994000

    Google Android 17 users must complete required training.

    Maps to CM-6 via CCI-000366
    Check

    Review a sample of site User Agreements for Google Android 17 device users or similar training records and training course content. Verify the Google Android 17 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 17 device user has not completed the required training, this is a finding.

    Fix

    All Google Android 17 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 DoW 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 DoW PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and 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 handoff. 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 DoW contacts via smart call and caller ID services. **Do not configure a DoW 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. **Use a default Wi-Fi hotspot password: 15-character complex Wi-Fi hotspot preshared password enabled ("WPA3-personal"). - 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. - User may not perform a factory reset of Android device unless directed by an AO (COPE mode only).

  21. GOOG-17-008400 CAT II V-284722 · PP-MDF-994000

    Google Android 17 must be configured to disable Wi-Fi sharing.

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration settings to confirm Wi-Fi sharing is disabled. Mobile hotspot must be enabled 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 that Wi-Fi sharing is disabled: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow sharing admin configured Wi-Fi" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". If on the EMM console "Disallow sharing admin configured Wi-Fi" is not enabled, this is a finding.

    Fix

    Configure the Google Android 17 device to disable Wi-Fi sharing. Mobile hotspot must be enabled 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 sharing admin configured Wi-Fi" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". Configuration API: DISALLOW_SHARING_ADMIN_CONFIGURED_WIFI

  22. GOOG-17-008500 CAT II V-284723 · PP-MDF-994000

    Google Android 17 must be configured to enforce a password for Wi-Fi and Bluetooth hotspot if approved for use by the authorizing official (AO). If not approved for use, Wi-Fi and Bluetooth hotspot must be disabled.

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration and user training and determine if the AO has approved hotspot use. If the AO has not approved hotspot use, verify that hotspot use has been 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 17 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 17 device "Hotspot & tethering" is enabled, this is a finding. If hotspot use has been approved, verify that the user has been trained to use the default hotspot password. Refer to GOOG-17-009800 for the procedure. If users are not trained to use the default hotspot password, this is a finding.

    Fix

    Disable hotspot functions on the DoW phone if not approved by the AO. 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". If the AO has approved the use of Wi-Fi and Bluetooth hotspots, train the user to not change the default hotspot password (refer to GOOG-17-009800). By default, when Wi-Fi Hotspot is enabled, a 15-character complex password is automatically configured for the hotspot. Configuration API: DISALLOW_CONFIG_TETHERING

  23. GOOG-17-008600 CAT II V-284724 · PP-MDF-994000

    Google Android 17 must have the DoW root and intermediate PKI certificates installed.

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration settings to confirm that the DoW root and intermediate PKI certificates are installed. This procedure is performed on both the EMM administration console and the managed Google Android 17 device. The current DoW 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 DoW 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 17 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that DoW root and intermediate PKI certificates are listed under the "User" tab in the "Work" section. If on the EMM console the DoW root and intermediate certificates are not listed in a profile, or the managed Android 17 device does not list the DoW root and intermediate certificates under the user tab, this is a finding.

    Fix

    Configure the Google Android 17 device to install DoW root and intermediate certificates. On the EMM console, upload DoW root and intermediate certificates as part of a device and/or work profile. The current DoW root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet). Configuration API: installCaCert()

  24. GOOG-17-008800 CAT II V-284725 · PP-MDF-994000

    The Google Android 17 work profile must be configured to enforce the system application disable list.

    Maps to CM-6 via CCI-000366
    Check

    Review the managed Google Android 17 work profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. Verify that only approved system apps have been placed on the core allow list. This procedure is performed on the EMM administration console. Review the system app allow list and verify that only approved apps are on the list. COBO: 1. Open the "Apps management" section. 2. Select "Hide apps". 3. Verify that package names of apps are listed. COPE: 1. Open the "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 allow list contains unapproved core apps, this is a finding.

    Fix

    Configure the Google Android 17 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 the "Apps management" section. 2. Select "Hide apps". 3. Enter package names of apps to hide. COPE: 1. Open the "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 allow list. Configuration API: enableSystemApp, setApplicationHidden

  25. GOOG-17-009000 CAT II V-284726 · PP-MDF-994000

    The Google Android 17 work profile must be configured to disable automatic completion of workspace internet browser text input.

    Maps to CM-6 via CCI-000366
    Check

    Review the work profile Chrome Browser app on the Google Android 17 autofill setting. This procedure is performed only on the EMM administration console. On the EMM console: COBO: 1. Open the "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify that "PasswordManagerEnabled" is turned "OFF". 4. Verify that "AutofillAddressEnabled" is turned "OFF". 5. Verify that "AutofillCreditCardEnabled" is turned "OFF". COPE: 1. Open the "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify that "PasswordManagerEnabled" is turned "OFF". 4. Verify that "AutofillAddressEnabled" is turned "OFF". 5. Verify that "AutofillCreditCardEnabled" is turned "OFF". If on the EMM console any of the browser autofill settings are set to "On" in the Chrome Browser settings, this is a finding.

    Fix

    Configure the Chrome browser on the Google Android 17 device work profile to disable autofill. On the EMM console: COBO: 1. Open the "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "PasswordManagerEnabled" is turned "OFF". 4. Ensure "AutofillAddressEnabled" is turned "OFF". 5. Ensure "AutofillCreditCardEnabled" is turned "OFF". COPE: 1. Open the "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "PasswordManagerEnabled" is turned "OFF". 4. Ensure "AutofillAddressEnabled" is turned "OFF". 5. Ensure "AutofillCreditCardEnabled" is turned "OFF". Refer to the EMM documentation to determine how to configure Chrome Browser settings. Configuration API: PasswordManagerEnabled, AutofillAddressEnabled, AutofillCreditCardEnabled

  26. GOOG-17-009100 CAT II V-284727 · PP-MDF-994000

    The Google Android 17 work profile must be configured to disable the autofill services.

    Maps to CM-6 via CCI-000366
    Check

    Review the Google Android 17 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: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow autofill" is toggled to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow autofill" is toggled to "ON". If on the EMM console "disallow autofill" is not selected, this is a finding.

    Fix

    Configure the Google Android 17 device work profile to disable the autofill services. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow autofill" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow autofill" to "ON". Configuration API: DISALLOW_AUTOFILL

  27. GOOG-17-009200 CAT II V-284728 · PP-MDF-994000

    Google Android 17 must be configured to disallow configuration of date and time.

    Maps to CM-6 via CCI-000366
    Check

    Review the managed Google Android 17 device configuration settings to confirm that configuration of date and time are disabled. This procedure is performed on both the EMM administration console and the managed Google Android 17 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 17 device: COBO and COPE: 1. Open Settings. 2. Tap "System". 3. Tap "Date & time". 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 17 device "Set time automatically" is not grayed out, this is a finding.

    Fix

    Configure the Google Android 17 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". Configuration API: SetAutoTimeRequired – on Parent DISALLOW_CONFIG_DATE_TIME – on User

  28. GOOG-17-009700 CAT II V-284733 · PP-MDF-994000

    Google Android 17 must be configured to disable all data signaling over [assignment: list of externally accessible hardware ports (for example, USB)].

    Maps to AC-6(10) via CCI-002235
    Check

    Review the device configuration to confirm that the USB port is disabled except for charging the device. On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow USB file transfer" is set to "ON". If on the EMM console the USB port is not disabled ("Disallow USB file transfer" is set to "ON"), this is a finding.

    Fix

    Configure the Google Android 17 device to disable the USB port (except for charging the device). On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow USB file transfer" to "ON". Configuration API: DISALLOW_USB_FILE_TRANSFER

  29. GOOG-17-009800 CAT II V-284734 · PP-MDF-994000

    Google Android 17 must allow only the administrator (EMM) to install/remove DoW root and intermediate PKI certificates.

    Maps to CM-6(1) via CCI-000370
    Check

    Review the device configuration to confirm that the user is unable to remove DoW 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 17 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 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 17 device the user is able to remove certificates, this is a finding.

    Fix

    Configure Google Android 17 device to prevent a user from removing DoW root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Toggle "Disallow config credentials" to "ON". Configuration API: DISALLOW_CONFIG_CREDENTIALS

  30. GOOG-17-010100 CAT II V-284737 · PP-MDF-994000

    Google Android 17 must disable the user's ability to wipe the device.

    Maps to CM-6 via CCI-000366
    Check

    Review configuration settings to confirm the user is unable to perform a factory reset and the admin has the ability to inject a recovery account on the device so they can unlock Factory Reset Protection (FRP). This check procedure is performed on the device management tool and the Google Android 17 device. On the MDM console: Verify factory reset configuration: COBO: 1. Open user restrictions. 2. Verify that "Disallow Factory Reset" is enabled. Verify factory reset protection policy configuration: From the Android Enterprise policy management: 1. Go to the "Factory Reset Protection" section. 2. Verify that "Factory Reset Protection" is set to "Allow/Enabled". 3. Verify that the correct Google Account ID(s) is/are listed as allowed to unlock the FRP. On the managed Google Android 17 device, verify factory reset configuration: COBO: 1. Open Settings >> General management >> Reset. 2. Tap the "Factory data reset" option. 3. Verify that the "Action not allowed" pop-up appears and factory data reset does not proceed. If the Android device user is able to perform a factory reset or the admin cannot unlock the Android phone after an FRP event, this is a finding.

    Fix

    Configure the Google Android 17 device to disable the ability of the user to wipe the Android device. Enable the admin to inject a recovery account on the device so they can unlock FRP. On the MDM console: Disallow factory reset: COBO: 1. Open User Restrictions. 2. Enable "Disallow Factory Reset". Set factory reset protection policy: COBO: 1. Open Device owner management >> Set factory reset protection. 2. From "Accounts" Section: Add Account >> Enter recovery account >> press "Ok". 3. From Enabled Section: Select "Enabled" to enable FRP policy. 4. Press "Save" to confirm all changes. Configuration API: factoryResetDisabled, frpAdminEmails[ ]

  31. GOOG-17-010600 CAT II V-284741 · PP-MDF-994000

    Google Android 17 devices must have a Mobile Threat Detection (MTD) app installed.

    Maps to CM-6 via CCI-000366
    Check

    Confirm an MTD app is installed on managed Google Android devices. This check procedure is performed on both the device management tool and the Google Android device. In the MDM console, verify that an MTD app is listed as a managed app being deployed to site-managed devices. On the Google Android device: 1. Open the Settings app. 2. Tap "Apps" >> "See all apps". 3. Verify that an MTD app is listed. If an MTD app is not installed on the device, this is a finding.

    Fix

    Install an MTD app on managed Google Android devices.

  32. GOOG-17-010700 CAT II V-284742 · PP-MDF-994000

    Google Android 17 must implement the management setting: Disable Camera.

    Maps to CM-6 via CCI-000366
    Check

    Determine if the site AO has approved the use of device cameras. Look for a document showing approval for a specific user or group of users. If not approved, review the configuration settings to confirm "Allow Camera" is disabled. If approved, this requirement is not applicable. Review the configuration settings to confirm the device camera has been disabled. This check procedure is performed on the device management tool and the Google Android 17 device. On the MDM console: COBO and COPE: 1. Open Camera. 2. Verify that the "Disable camera" setting is disabled. On the managed Google Android 17 device: COBO and COPE: Verify that the camera cannot be used on the mobile device. If the device camera has not been disabled, this is a finding.

    Fix

    If the AO has not approved the use of the Google device camera, configure Android 17 to disable the device camera. On the MDM console: COBO and COPE: 1. Open Camera. 2. Select "Disable camera". Configuration API: cameraDisabled

  33. GOOG-17-010800 CAT II V-284743 · PP-MDF-994000

    The Google Android device must be configured to disable Wi-Fi Aware for work profile apps.

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration settings to confirm Wi-Fi Aware is disabled for each work profile app. This procedure is performed on the EMM console. For each work profile app, verify the app is configured to deny the NEARBY_WIFI_DEVICE permission. Note: Not all apps will support Wi-Fi Aware and have the NEARBY_WIFI_DEVICE permission. If on the EMM console, the NEARBY_WIFI_DEVICE permission is not set to "deny" for all work profile apps that support Wi-Fi Aware, this is a finding.

    Fix

    Configure the Google Android 17 device to disable Wi-Fi Aware for all work profile apps. On the EMM console: For each work profile app, configure the NEARBY_WIFI_DEVICE permission to "deny" to block the use of Wi-Fi Aware if the app supports this feature. If the app does not support Wi-Fi Aware, there may not be a NEARBY_WIFI_DEVICE permission available. API: NEARBY_WIFI_DEVICE

  34. GOOG-17-010900 CAT II V-284744 · PP-MDF-994000

    The Google Android device must be configured to disable Cross-Device Handoff (also called "Continuity On").

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration settings to disable Cross-Device Handoff (also called "Continuity On"). This procedure is performed on the EMM console. Verify "TASK_CONTINUITY_HANDOFF_DISABLED" is enabled. If on the EMM console Cross-Device Handoff is not disabled, this is a finding.

    Fix

    Configure the Google Android 17 device to disable Cross-Device Handoff (also called "Continuity On"). On the EMM console: COBO and COPE: 1. Open User Restrictions. 2. Enable "TASK_CONTINUITY_HANDOFF_DISABLED". API: TASK_CONTINUITY_HANDOFF_DISABLED

  35. GOOG-17-011000 CAT II V-285856 · PP-MDF-994000

    The Google Android 17 device must be configured to disable web-based artificial intelligence (AI) interactions.

    Maps to CM-6 via CCI-000366
    Check

    Verify the Google Android 17 device has been configured to disable web-based AI interactions. On the Android 17 phone, try to browse to unauthorized AI URLs. Examples to input are chatgpt.com, claude.ai, gemini.google.com, and v0.dev. Verify the unauthorized AI websites cannot be reached. If the Google Android 17 device has not been configured to disable web-based AI interactions, this is a finding.

    Fix

    Configure the Google Android 17 device to disable web-based AI interactions. For web-based AI in the browser: Create an App Configuration Policy (Requires EMM Admin access): Navigate to your EMM's Policy/App Configuration section and create a new policy targeted at Managed Devices/Android Enterprise. Select the browser (Google Chrome) as the targeted application. Configure the URL blocklist: Locate the URL blocklist setting. Add the domains of the AI tools you want to block. Examples to input include chatgpt.com, claude.ai, gemini.google.com, and v0.dev. Block Incognito Mode: In the same Chrome configuration layout, look for IncognitoModeAvailability. Set Incognito mode to disabled. This ensures users cannot bypass the URL blocklist by launching an anonymous browsing session. Assign and Push: Save the configuration and assign it to the device groups containing the COBO and COPE profiles. For other browsers it depends on deployment type. For COBO: Because the first step limits the managed Google Play store to only approved apps, ensure that no other browsers (Firefox, Opera, or Edge) are approved in the app allowlist. For COPE: Create a Device Restrictions Policy for the personal profile and set "Disallow install of applications from unknown sources" to True.