Google Android 17 must be configured to disable developer modes.

Developer modes expose features of the mobile operating system that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DoW sensitive information. Disabling developer modes mitigates this risk.

SFR ID: FMT_SMF_EXT.1.1 #26

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.

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