View STIG - Google Android 16 COBO Security Technical Implementation Guide V1R1

b

Google Android 16 must be configured to enable audit logging.

AU-6 - Medium - CCI-000154 - V-276748 - SV-276748r1140036_rule

RMF Control

AU-6

Severity

Medium

CCI

CCI-000154

Version

GOOG-16-002800

Vuln IDs

V-276748

Rule IDs

SV-276748r1140036_rule

Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. For the audit logs to be useful, administrators must have the ability to view them. SFR ID: FMT_SMF.1.1 #32

Checks: C-80903r1140034_chk

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

Fix: F-80808r1140035_fix

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

b

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

- Medium - CCI-004066 - V-276749 - SV-276749r1140039_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-16-006000

Vuln IDs

V-276749

Rule IDs

SV-276749r1140039_rule

Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. The ability to crack a password is a function of how many attempts an adversary is permitted, how quickly an adversary can perform each attempt, and the size of the password space. The longer the minimum length of the password, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting in device and data compromise. SFR ID: FMT_SMF.1.1 #1

Checks: C-80904r1140037_chk

Review managed Google Android 16 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 16 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 that the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 16 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 16 device, this is a finding.

Fix: F-80809r1140038_fix

Configure the Google Android 16 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

b

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

- Medium - CCI-004066 - V-276750 - SV-276750r1140042_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-16-006100

Vuln IDs

V-276750

Rule IDs

SV-276750r1140042_rule

Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk. SFR ID: FMT_SMF.1.1 #1

Checks: C-80905r1140040_chk

Review managed Google Android 16 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 16 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 16 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 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 16 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: F-80810r1140041_fix

Configure the Google Android 16 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

b

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

AC-11 - Medium - CCI-000057 - V-276751 - SV-276751r1140045_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000057

Version

GOOG-16-006300

Vuln IDs

V-276751

Rule IDs

SV-276751r1140045_rule

The screen lock timeout must be set to a value that helps protect the device from unauthorized access. Having a too-long timeout would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device. SFR ID: FMT_SMF.1.1 #2

Checks: C-80906r1140043_chk

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 16 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: F-80811r1140044_fix

Configure the Google Android 16 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: The Google Android 16 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

b

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

AC-7 - Medium - CCI-000044 - V-276752 - SV-276752r1140048_rule

RMF Control

AC-7

Severity

Medium

CCI

CCI-000044

Version

GOOG-16-006400

Vuln IDs

V-276752

Rule IDs

SV-276752r1140048_rule

The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or fewer gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password. SFR ID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5

Checks: C-80907r1140046_chk

Review managed Google Android 16 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 16 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 16 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 16 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: F-80812r1140047_fix

Configure the Google Android 16 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()

b

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

CM-6 - Medium - CCI-000366 - V-276753 - SV-276753r1140051_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-006500

Vuln IDs

V-276753

Rule IDs

SV-276753r1140051_rule

Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DOD data accessible by these unauthorized/malicious applications. SFR ID: FMT_SMF.1.1 #8

Checks: C-80908r1140049_chk

Review managed Google Android 16 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 16 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 16 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 16 device the device policy is not set to allow connections to only approved application repositories, this is a finding.

Fix: F-80813r1140050_fix

Configure the Google Android 16 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

b

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

CM-7 - Medium - CCI-001764 - V-276754 - SV-276754r1140054_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-001764

Version

GOOG-16-006600

Vuln IDs

V-276754

Rule IDs

SV-276754r1140054_rule

The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the mobile device (MD) must provide an alternate method of restricting user access/execution to core and preinstalled applications. Core application: Any application integrated into the operating system (OS) by the OS or MD vendors. Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier. Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications. The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all 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. SFR ID: FMT_SMF.1.1 #8

Checks: C-80909r1140052_chk

Review managed Google Android 16 device configuration settings to determine if the mobile device has an application allowlist configured. Verify that all applications listed on the allowlist 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 16 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 allowlist 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: F-80814r1140053_fix

Configure the Google Android 16 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.

b

Google Android 16 allowlist must be configured to not include applications with the following characteristics: - Backs up mobile device (MD) data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs or printers; - Backs up own data to a remote system; - Renders TV shows and movies.

IA-7 - Medium - CCI-000803 - V-276755 - SV-276755r1140057_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-16-006700

Vuln IDs

V-276755

Rule IDs

SV-276755r1140057_rule

Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DOD data or have features with no known application in the DOD environment. Application note: The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. Core application: Any application integrated into the operating system (OS) by the OS or MD vendors. Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier. SFR ID: FMT_SMF.1.1 #8

Checks: C-80910r1140055_chk

Review managed Google Android 16 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: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs, display screens (screen mirroring), or printers; - Backs up own data to a remote system. - Renders TV shows and movies. 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.

Fix: F-80815r1140056_fix

Configure the Google Android 16 device application allowlist to exclude applications with the following characteristics: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs, display screens (screen mirroring), or printers; - Backs up own data to a remote system; - Renders TV shows and movies. 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. Managed Google Play is always an allowlisted App Store.

b

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

IA-7 - Medium - CCI-000803 - V-276756 - SV-276756r1140662_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-16-006750

Vuln IDs

V-276756

Rule IDs

SV-276756r1140662_rule

Sensitive DOD data could be exposed when an AI app processes device data in the cloud. SFR ID: FMT_SMF.1.1 #8

Checks: C-80911r1140058_chk

Review managed Google Android 16 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 that 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 16 and processes device data on the device. Refer to the STIG Supplemental document, Section 2, Artificial Intelligence Restrictions, for more information.

Fix: F-80816r1140661_fix

Configure the Google Android 16 device application allowlist 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 16 and processes device data on the device. Refer to the STIG Supplemental document, Section 2, Artificial Intelligence Information, for more information.

b

Google Android 16 must be configured to not display the following (work profile) notifications when the device is locked: [selection: a. email notifications b. calendar appointments c. contact associated with phone call notification d. text message notification e. other application-based notifications f. all notifications].

AC-11 - Medium - CCI-000060 - V-276757 - SV-276757r1140063_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000060

Version

GOOG-16-006800

Vuln IDs

V-276757

Rule IDs

SV-276757r1140063_rule

Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the mobile operating system not to send notifications to the lock screen mitigates this risk. SFR ID: FMT_SMF.1.1 #18

Checks: C-80912r1140061_chk

Review managed Google Android 16 device settings to determine if the Google Android 16 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 16 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 16 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 16 device allows work notifications on the lock screen, this is a finding.

Fix: F-80817r1140062_fix

Configure the Google Android 16 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

b

Google Android 16 must be configured to disable trust agents.

IA-2 - Medium - CCI-000767 - V-276758 - SV-276758r1140066_rule

RMF Control

IA-2

Severity

Medium

CCI

CCI-000767

Version

GOOG-16-007200

Vuln IDs

V-276758

Rule IDs

SV-276758r1140066_rule

Trust agents allow a user to unlock a mobile device without entering a passcode when the mobile device is, for example, connected to a user-selected Bluetooth device or in a user-selected location. This technology would allow unauthorized users to have access to DOD sensitive data if compromised. By not permitting the use of nonpassword authentication mechanisms, users are forced to use passcodes that meet DOD passcode requirements. SFR ID: FMT_SMF.1.1 #22, FIA_UAU.5.1

Checks: C-80913r1140064_chk

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 16 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 16 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 16 device a trust agent can be enabled, this is a finding.

Fix: F-80818r1140065_fix

Configure the Google Android 16 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

b

Google Android 16 must be configured to disable developer modes.

CM-7 - Medium - CCI-000381 - V-276759 - SV-276759r1140069_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-000381

Version

GOOG-16-007400

Vuln IDs

V-276759

Rule IDs

SV-276759r1140069_rule

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 DOD sensitive information. Disabling developer modes mitigates this risk. SFR ID: FMT_SMF.1.1 #26

Checks: C-80914r1140067_chk

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

Fix: F-80819r1140068_fix

Configure the Google Android 16 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

a

Google Android 16 must be configured to display the DOD advisory warning message at startup or each time the user unlocks the device.

AC-8 - Low - CCI-000048 - V-276760 - SV-276760r1140072_rule

RMF Control

AC-8

Severity

Low

CCI

CCI-000048

Version

GOOG-16-007700

Vuln IDs

V-276760

Rule IDs

SV-276760r1140072_rule

Before granting access to the system, the mobile operating system is required to display the DOD-approved system use notification message or banner that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Required banners help ensure that DOD can audit and monitor the activities of mobile device users without legal restriction. System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a "click-through" banner at device unlock (to the extent permitted by the operating system). A "click-through" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating "OK." The approved DOD text must be used exactly as required in the Knowledge Service referenced in DODI 8500.01. For devices accommodating banners of 1300 characters, the banner text is: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. For devices with severe character limitations, the banner text is: I've read & consent to terms in IS user agreem't. The administrator must configure the banner text exactly as written without any changes. SFR ID: FMT_SMF.1.1 #36

Checks: C-80915r1140070_chk

The DOD warning banner can be displayed by either of the following methods (required text is found in the Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each managed Android 16 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each managed Android 16 mobile device. Determine which method is used at the Google Android 16 device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Google Android 16 device users and verify that 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 16 device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.

Fix: F-80820r1140071_fix

Configure the DOD warning banner by either of the following methods (required text is found in the Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each Google Android 16 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each Google Android 16 mobile device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Enter the message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Enter the message. Configuration API: setDeviceOwnerLockScreenInfo

b

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

AU-12 - Medium - CCI-000169 - V-276761 - SV-276761r1140075_rule

RMF Control

AU-12

Severity

Medium

CCI

CCI-000169

Version

GOOG-16-007800

Vuln IDs

V-276761

Rule IDs

SV-276761r1140075_rule

Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Rule Title lists key events for which the system must generate an audit record. Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component. SFR ID: FMT_SMF.1.1 #37

Checks: C-80916r1140073_chk

Review managed Google Android 16 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: F-80821r1140074_fix

Configure the Google Android 16 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

b

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

SC-41 - Medium - CCI-002546 - V-276762 - SV-276762r1140078_rule

RMF Control

SC-41

Severity

Medium

CCI

CCI-002546

Version

GOOG-16-008400

Vuln IDs

V-276762

Rule IDs

SV-276762r1140078_rule

USB mass storage mode enables the transfer of data and software from one device to another. This software can include malware. When USB mass storage is enabled on a mobile device, it becomes a potential vector for malware and unauthorized data exfiltration. Prohibiting USB mass storage mode mitigates this risk. SFR ID: FMT_SMF.1.1 #39

Checks: C-80917r1140076_chk

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

Fix: F-80822r1140077_fix

Configure the Google Android 16 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

b

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

SC-4 - Medium - CCI-001090 - V-276763 - SV-276763r1140081_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-16-008500

Vuln IDs

V-276763

Rule IDs

SV-276763r1140081_rule

Data on mobile devices is protected by numerous mechanisms, including user authentication, access control, and cryptography. When the data is backed up to an external system (either locally connected or cloud based), many if not all of these mechanisms are no longer present. This leaves the backed-up data vulnerable to attack. Disabling backup to external systems mitigates this risk. SFR ID: FMT_SMF.1.1 #40

Checks: C-80918r1140079_chk

Review managed Google Android 16 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 16 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 16 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 16 device the device policy is not set to disable the capability to back up to a locally connected system, this is a finding.

Fix: F-80823r1140080_fix

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

b

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

SC-4 - Medium - CCI-001090 - V-276764 - SV-276764r1140084_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-16-008600

Vuln IDs

V-276764

Rule IDs

SV-276764r1140084_rule

Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system. Where the remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this case, DOD devices may synchronize DOD sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk. SFR ID: FMT_SMF.1.1 #40

Checks: C-80919r1140082_chk

Review managed Google Android 16 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-16-009800), 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 16 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 16 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 16 device the device policy is not set to disable the capability to back up to a remote system, this is a finding.

Fix: F-80824r1140083_fix

Configure the Google Android 16 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-16-009800), this control impacts only personal profile accounts. Sites can allow backup based on local policy. Configuration API: setBackupServiceEnabled

b

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

AC-18 - Medium - CCI-001443 - V-276765 - SV-276765r1140087_rule

RMF Control

AC-18

Severity

Medium

CCI

CCI-001443

Version

GOOG-16-008700

Vuln IDs

V-276765

Rule IDs

SV-276765r1140087_rule

If no authentication is required to establish personal hotspot connections (Wi-Fi and Bluetooth), an adversary may be able to use that device to perform attacks on other devices or networks without detection. A sophisticated adversary may also be able to exploit unknown system vulnerabilities to access information and computing resources on the device. Requiring authentication to establish personal hotspot connections mitigates this risk. Application note: If hotspot functionality is permitted, it must be authenticated via a preshared key. There is no requirement to enable hotspot functionality, and it is recommended this functionality be disabled by default. SFR ID: FMT_SMF.1.1 #41

Checks: C-80920r1140085_chk

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 "WPA2/WPA3-Personal" or "WPA3-Personal". 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. On 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 either "WPA2/WPA3-Personal" or "WPA3-Personal" is selected. If the Wi-Fi hotspot security is not set to "WPA2/WPA3-Personal" or "WPA3-Personal", this is a finding.

Fix: F-80825r1140086_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) ("WPA2/WPA3-Personal" or WPA3-Personal"). (GOOG-16-009800) 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. On the left of the slide, tap on "Wi-Fi Hotspot" to bring up the configuration options. 4. Click on the "Security" link and select either "WPA2/WPA3-Personal" or "WPA3-Personal".

b

Google Android 16 must be configured to disable multiuser modes.

AC-2 - Medium - CCI-002110 - V-276766 - SV-276766r1140090_rule

RMF Control

AC-2

Severity

Medium

CCI

CCI-002110

Version

GOOG-16-009000

Vuln IDs

V-276766

Rule IDs

SV-276766r1140090_rule

Multiuser mode allows multiple users to share a mobile device by providing a degree of separation between user data. To date, no mobile device with multiuser mode features meets DOD requirements for access control, data separation, and nonrepudiation for user accounts. In addition, the MDFPP does not include design requirements for multiuser account services. Disabling multiuser mode mitigates the risk of not meeting DOD multiuser account security policies. SFR ID: FMT_SMF.1.1 #47a

Checks: C-80921r1140088_chk

Review documentation on the managed Google Android 16 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 16 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 16 device: COBO and COPE: 1. Go to Settings >> Passwords, passkeys & accounts >> Accounts for Owner. 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 16 device the device policy is not set to disable multiuser modes, this is a finding.

Fix: F-80826r1140089_fix

Configure the Google Android 16 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

a

Google Android 16 must be configured to disable Bluetooth or configured via User Based Enforcement (UBE) to allow Bluetooth for only Headset Profile (HSP), Hands-Free Profile (HFP), and Serial Port Profile (SPP).

CM-7 - Low - CCI-000381 - V-276767 - SV-276767r1140665_rule

RMF Control

CM-7

Severity

Low

CCI

CCI-000381

Version

GOOG-16-009400

Vuln IDs

V-276767

Rule IDs

SV-276767r1140665_rule

Some Bluetooth profiles provide the capability for remote transfer of sensitive DOD data without encryption or otherwise do not meet DOD IT security policies and therefore must be disabled. SFR ID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8

Checks: C-80922r1140664_chk

Determine if the authorizing official (AO) has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify that Bluetooth has been disabled. On the EMM console: COBO: 1. Open the "User restrictions" section. 2. Verify that "Disallow Bluetooth" is toggled to "ON". COPE: 1. Open the "User restrictions on parent" section. 2. Verify that "Disallow Bluetooth" is toggled to "ON". On the managed Google Android 16 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 16 device: 1. Go to Settings >> Connected Devices. 2. Verify that 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.

Fix: F-80827r1140092_fix

Configure the Google Android 16 device to disable Bluetooth, or if the AO has approved the use of Bluetooth (for example, for car hands-free use), train the user to connect to only authorized Bluetooth devices using only HSP, HFP, or SPP Bluetooth-capable devices (User-Based Enforcement). To disable Bluetooth, use the following procedure: On the EMM console: COBO: 1. Open the "User restrictions" section. 2. Toggle "Disallow Bluetooth" to "ON". COPE: 1. Open the "User restrictions on parent" section. 2. Toggle "Disallow Bluetooth" to "ON". The user training requirement is satisfied in GOOG-16-009800. Configuration API: DISALLOW_CONFIG_BLUETOOTH

b

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

SC-40 - Medium - CCI-002536 - V-276768 - SV-276768r1140096_rule

RMF Control

SC-40

Severity

Medium

CCI

CCI-002536

Version

GOOG-16-009500

Vuln IDs

V-276768

Rule IDs

SV-276768r1140096_rule

Ad hoc wireless client-to-client connections allow mobile devices to communicate with each other directly, circumventing network security policies and making the traffic invisible. This could allow the exposure of sensitive DOD data and increase the risk of downloading and installing malware on the DOD mobile device. SFR ID: FMT_SMF_EXT.1.1/WLAN

Checks: C-80923r1140094_chk

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: F-80828r1140095_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" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and toggle that to "ON". Configuration API: DISALLOW_WIFI_DIRECT

b

Google Android 16 users must complete required training.

CM-6 - Medium - CCI-000366 - V-276769 - SV-276769r1140099_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009800

Vuln IDs

V-276769

Rule IDs

SV-276769r1140099_rule

The security posture of Google devices requires the device user to configure several required policy rules on their device. User-Based Enforcement (UBE) is required for these controls. In addition, if the authorizing official (AO) has approved the use of an unmanaged personal space, the user must receive training on risks. If a user is not aware of their responsibilities and does not comply with UBE requirements, the security posture of the Google mobile device may become compromised, and DOD sensitive data may become compromised. SFR ID: NA

Checks: C-80924r1140097_chk

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

Fix: F-80829r1140098_fix

All Google Android 16 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 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 DOD contacts via smart call and caller ID services. **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. **Use default Wi-Fi hotspot password: 15-character complex Wi-Fi hotspot preshared password enabled ("WPA2/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.

b

Google Android 16 must be configured to disable Wi-Fi Sharing.

CM-6 - Medium - CCI-000366 - V-276770 - SV-276770r1140102_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009900

Vuln IDs

V-276770

Rule IDs

SV-276770r1140102_rule

Wi-Fi Sharing is an optional configuration of Wi-Fi Tethering/Mobile Hotspot, which allows the device to share its Wi-Fi connection with other wirelessly connected devices instead of its mobile (cellular) connection. Wi-Fi Sharing grants the other device access to a corporate Wi-Fi network and may possibly bypass the network access control mechanisms. This risk can be partially mitigated by requiring the use of a preshared key for personal hotspots. SFR ID: FMT_SMF_EXT.1.1 / WLAN #3

Checks: C-80925r1140100_chk

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: F-80830r1140101_fix

Configure the Google Android 16 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

b

Google Android 16 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.

CM-6 - Medium - CCI-000366 - V-276771 - SV-276771r1140105_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009950

Vuln IDs

V-276771

Rule IDs

SV-276771r1140105_rule

Wi-Fi and Bluetooth hotspot use may increase the risk for exposing sensitive DOD data for some use cases; therefore, it should be disabled unless approved by the AO. When a DOD mobile phone is used as a Wi-Fi or Bluetooth hotspot, a hotspot password must be enabled; otherwise, unauthorized devices could connect to the DOD hotspot, which may increase the risk of exposure of sensitive DOD data and/or a performance degradation of the DOD mobile phone. SFR ID: FMT_SMF_EXT.1.1 / WLAN #3

Checks: C-80926r1140103_chk

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 16 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 16 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-16-009800 for the procedure. If users are not trained to use the default hotspot password, this is a finding.

Fix: F-80831r1140104_fix

Disable hotspot functions on the DOD 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-16-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

b

Google Android 16 must have the DOD root and intermediate PKI certificates installed.

CM-6 - Medium - CCI-000366 - V-276772 - SV-276772r1140108_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010000

Vuln IDs

V-276772

Rule IDs

SV-276772r1140108_rule

DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the DOD root and intermediate PKI certificates greatly diminishes the risk of this attack. SFR ID: FMT_SMF.1.1 #11

Checks: C-80927r1140106_chk

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 16 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 16 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "Advanced". 4. Tap "More security & privacy". 5. Tap "Encryption & credentials". 6. Tap "Trusted credentials". 7. 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 16 device does not list the DOD root and intermediate certificates under the user tab, this is a finding.

Fix: F-80832r1140107_fix

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

b

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

CM-6 - Medium - CCI-000366 - V-276773 - SV-276773r1140111_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010200

Vuln IDs

V-276773

Rule IDs

SV-276773r1140111_rule

The system application disable list controls user access to/execution of all core and preinstalled applications. Core application: Any application integrated into Google Android 16 by Google. Preinstalled application: Additional noncore applications included in the Google Android 16 build by Google or the wireless carrier. Some system applications can compromise DOD data or upload users' information to non-DOD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DOD data or DOD user information. The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DOD use by configuring the system application disable list. SFR ID: FMT_SMF.1.1 #47

Checks: C-80928r1140109_chk

Review the managed Google Android 16 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 allowlist. This procedure is performed on the EMM Administration Console. Review the system app allowlist 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 allowlist contains unapproved core apps, this is a finding.

Fix: F-80833r1140110_fix

Configure the Google Android 16 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 allowlist. Configuration API: enableSystemApp, setApplicationHidden

b

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

CM-6 - Medium - CCI-000366 - V-276774 - SV-276774r1140114_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010400

Vuln IDs

V-276774

Rule IDs

SV-276774r1140114_rule

The autofill functionality in the web browser allows the user to complete a form that contains sensitive information, such as personally identifiable information, without previous knowledge of the information. By allowing the use of autofill functionality, an adversary who learns a user's Android 16 device password, or who otherwise is able to unlock the device, may be able to breach other systems by relying on the autofill feature to provide information unknown to the adversary. By disabling the autofill functionality, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated. SFR ID: FMT_SMF.1.1 #47

Checks: C-80929r1140112_chk

Review the work profile Chrome Browser app on the Google Android 16 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: F-80834r1140113_fix

Configure the Chrome browser on the Google Android 16 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.

c

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

CM-6 - High - CCI-000366 - V-276775 - SV-276775r1140673_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

GOOG-16-010500

Vuln IDs

V-276775

Rule IDs

SV-276775r1140673_rule

Wi-Fi Aware allows direct connections between nearby devices for fast data transfer, video streaming, and multiplayer gaming. It allows full peer-to-peer device discovery and communication where two or more devices are publishing and/or subscribing to the same known service name. There is risk that sensitive DOD information could be transferred from a DOD mobile device to a non-DOD device or from Work Profile apps on a DOD device to Personal Profile apps on a non-DOD device.

Checks: C-80930r1140671_chk

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: F-80835r1140672_fix

Configure the Google Android 16 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.

c

Google Android 16 must implement the management setting: disable the Bluetooth radio.

CM-6 - High - CCI-000366 - V-276776 - SV-276776r1140670_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

GOOG-16-010600

Vuln IDs

V-276776

Rule IDs

SV-276776r1140670_rule

Authorizing official (AO) approval is required before the Google device Bluetooth radio can be enabled. All AO approvals must be documented and based on critical mission need. Use of Bluetooth may lead to the exposure of sensitive DOD information in some operational environments. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80931r1140668_chk

Determine if the site AO has approved the use of Google device Bluetooth radios. Look for a document showing AO approval. All AO approvals must be documented and based on critical mission need. If not approved, review configuration settings on the MDM server to confirm Bluetooth has been disabled, and on the Google device, verify Bluetooth cannot be enabled. If approved, this requirement is not applicable. This check procedure is performed on both the device management tool and managed Google device. Note: If an organization has multiple configuration profiles, the Check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the management tool, verify Bluetooth is disabled ("DISALLOW_BLUETOOTH" enabled) in the configuration profile. On the managed Google device verify the Bluetooth radio is disabled and cannot be enabled: (Settings >> Connected devices >> Connection preferences > Bluetooth) If Bluetooth has not been disabled in the device's MDM configuration profile or if Bluetooth can be enabled on the Google device, this is a finding.

Fix: F-80836r1140669_fix

If the AO has not approved the use of the Google device Bluetooth radio, install a configuration profile to disable Bluetooth use. On the MDM console: In the configuration profile for the device, disable Bluetooth (enable "DISALLOW_BLUETOOTH").

c

Android 16 devices must have the latest available Google Android 16 operating system installed.

CM-6 - High - CCI-000366 - V-276777 - SV-276777r1140123_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

GOOG-16-010800

Vuln IDs

V-276777

Rule IDs

SV-276777r1140123_rule

Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions. SFR ID: FMT_SMF.1.1 #47

Checks: C-80932r1140121_chk

Review device configuration settings to confirm the Google Android device has the most recently released version of managed Google Android 16 installed. This procedure is performed on both the EMM Administration Console and the managed Google Android 16 device. On the EMM console, review the version of Google Android 16 installed on a sample of managed devices. This procedure will vary depending on the EMM product. On the managed Google Android 16 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 16 operating system on any reviewed device 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.

Fix: F-80837r1140122_fix

Install the latest released version of the Google Android 16 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.

a

Android 16 devices must be configured to disable the use of third-party keyboards.

CM-6 - Low - CCI-000366 - V-276778 - SV-276778r1140126_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-010900

Vuln IDs

V-276778

Rule IDs

SV-276778r1140126_rule

Many third-party keyboard applications are known to contain malware. SFR ID: FMT_SMF.1.1 #47

Checks: C-80933r1140124_chk

Review the managed Google Android 16 configuration settings to confirm that no third-party keyboards are enabled. This procedure is performed on the EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Verify that only the approved keyboards are selected. If third-party keyboards are allowed, this is a finding.

Fix: F-80838r1140125_fix

Configure the Google Android 16 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. Admins can also configure application allowlists for Google Play that do not have any third-party keyboards for user installation.

a

Android 16 devices must be configured to enable Common Criteria (CC) Mode.

CM-6 - Low - CCI-000366 - V-276779 - SV-276779r1140129_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-011000

Vuln IDs

V-276779

Rule IDs

SV-276779r1140129_rule

The CC Mode feature is a superset of other features and behavioral changes that are mandatory MDFPP requirements. If CC Mode is not implemented, the device will not be operating in the NIAP-certified compliant CC Mode of operation. CC Mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi keys are stored using different types of encryption. SFR ID: FMT_SMF.1.1 #47

Checks: C-80934r1140127_chk

Review the managed Google Android 16 configuration settings to confirm CC Mode is enabled. This procedure is performed on the EMM Administration 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.

Fix: F-80839r1140128_fix

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

b

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

AC-6 - Medium - CCI-002235 - V-276780 - SV-276780r1140132_rule

RMF Control

AC-6

Severity

Medium

CCI

CCI-002235

Version

GOOG-16-012200

Vuln IDs

V-276780

Rule IDs

SV-276780r1140132_rule

If a user is able to configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information. SFR ID: FMT_MOF_EXT.1.2 #24

Checks: C-80935r1140130_chk

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: F-80840r1140131_fix

Configure the Google Android 16 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

b

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

CM-6 - Medium - CCI-000370 - V-276781 - SV-276781r1140135_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000370

Version

GOOG-16-012300

Vuln IDs

V-276781

Rule IDs

SV-276781r1140135_rule

DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the user is allowed to remove root and intermediate certificates, the user could allow an adversary to falsely sign a certificate in such a way that it could not be detected. Restricting the ability to remove DOD root and intermediate PKI certificates to the administrator mitigates this risk. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80936r1140133_chk

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 16 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 16 device the user is able to remove certificates, this is a finding.

Fix: F-80841r1140134_fix

Configure Google Android 16 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". Configuration API: DISALLOW_CONFIG_CREDENTIALS

a

Google Android 16 must allow only the administrator (MDM) to perform the following management function: Disable Phone Hub.

SC-4 - Low - CCI-001090 - V-276782 - SV-276782r1140138_rule

RMF Control

SC-4

Severity

Low

CCI

CCI-001090

Version

GOOG-16-012400

Vuln IDs

V-276782

Rule IDs

SV-276782r1140138_rule

It may be possible to transfer work profile data on a DOD Android device to an unauthorized Chromebook if the user has the same Google Account set up on the Chromebook and in the work profile on the Android device. This may result in the exposure of sensitive DOD data. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80937r1140136_chk

Review the EMM configuration to confirm phone hub has been disabled. On the management tool: 1. Open "Nearby notification streaming policy". 2. Verify that "Nearby notification streaming policy" is set to "Disabled". 3. Open "Nearby app streaming policy". 4. Verify that "Nearby app streaming policy" is set to "Disabled". If on the management tool the "Nearby Streaming Policy" is not set to "Disabled" and "Nearby app streaming policy" is not set to "Disabled", this is a finding. Note: From a Chromebook, if a device is connected to the Phone Hub, try to set up the Notifications. It will fail to connect to the device to complete the setup if Phone Hub has been disabled on the DOD Android device.

Fix: F-80842r1140137_fix

Configure the Google Android 16 device to disable the nearby notification streaming policy to disable Phone Hub. On the EMM console: COBO and COPE: 1. Open "Nearby notification streaming policy". 2. Set "Nearby notification streaming policy" to "Disabled". 3. Open "Nearby app streaming policy". 4. Set "Nearby app streaming policy" to "Disabled". Configuration API: setNearbyNotificationStreamingPolicy to NEARBY_STREAMING_DISABLED

c

Google Android 16 must be configured to disable "Private Space" use.

CM-6 - High - CCI-000370 - V-276783 - SV-276783r1140141_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000370

Version

GOOG-16-012500

Vuln IDs

V-276783

Rule IDs

SV-276783r1140141_rule

Private Space is an Android feature that provides a separate encrypted container on the mobile device. Apps in Private Space show up in a separate container in the launcher and are hidden from the "Recents" view, notifications, settings, and other apps when the private space is locked. In addition, an MDM server allowlist or blocklist cannot control the installation of apps into Private Space. Malware and other unauthorized apps could be installed on a DOD mobile device, which could lead to the compromise of DOD sensitive information or to an attack on the DOD network. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80938r1140139_chk

Review the Google Android 16 work profile configuration settings to confirm that Private Space is 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 add private profile" is set to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow add private profile" is set to "ON". If on the EMM console "Disallow add private profile" is not selected, this is a finding.

Fix: F-80843r1140140_fix

Configure the Google Android 16 device to disable "Private Space". On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON". Configuration API: DISALLOW_ADD_PRIVATE_PROFILE

b

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

CM-6 - Medium - CCI-000366 - V-276784 - SV-276784r1140144_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013000

Vuln IDs

V-276784

Rule IDs

SV-276784r1140144_rule

This feature must be disabled to comply with DOD electronic records retention requirements for mobile devices. Otherwise, mobile device users could wipe the device, which would violate DOD policy. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80939r1140142_chk

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 16 device. On the MDM console: Verify factory reset configuration: COBO and COPE: 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 16 device, verify factory reset configuration: COBO and COPE: 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: F-80844r1140143_fix

Configure Google Android 16 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 and COPE: 1. Open user restrictions. 2. Enable "Disallow Factory Reset". Set factory reset protection policy: COBO and COPE: 1. 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[ ]

a

Google Android 16 must disable the use of assistants (including Google Assistant) unless required to meet Section 508 compliance requirements.

CM-6 - Low - CCI-000366 - V-276785 - SV-276785r1140147_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013100

Vuln IDs

V-276785

Rule IDs

SV-276785r1140147_rule

The use of assistants could expose sensitive DOD data to cloud-based servers during the processing of assistant requests. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80940r1140145_chk

Review configuration settings to confirm the use of assistants has been disabled. This check procedure is performed on the device management tool and the Google Android 16 device. On the MDM console: COBO and COPE: 1. Open user restrictions. 2. Verify that "Disallow assist content" is enabled. 3. Verify that the Gemini App in the Managed Google Play Store has not been added to the allowlist. On the managed Google Android 16 device: 1. Try to invoke the Google Assistant and note that it will not execute. 2. Verify that the Gemini app is not installed and that it is not listed in the Managed Google Play Store. If the use of assistants has not been disabled, this is a finding. Note: This control also disables Gemini from being invoked if it was previously installed.

Fix: F-80845r1140146_fix

Configure the Google Android 16 device to disable the use of all assistants. On the MDM console, do the following: COBO and COPE: 1. Open user restrictions. 2. Enable "Disallow assist content". 3. Do not allowlist the Gemini App in the Managed Google Play Store. Note: This control also disables Gemini from being invoked if it was previously installed. Configuration API: ASSIST_CONTENT_DISALLOWED

a

Google Android 16 must disable wireless printing.

CM-6 - Low - CCI-000366 - V-276786 - SV-276786r1140150_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013200

Vuln IDs

V-276786

Rule IDs

SV-276786r1140150_rule

Wireless printing allows the printing of sensitive DOD documents to non-DOD controlled printers, which may lead to the exposure of sensitive DOD information. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80941r1140148_chk

Review configuration settings to confirm that wireless printing has been disabled. This check procedure is performed on the device management tool and the Google Android 16 device. On the MDM console: COBO and COPE: 1. Open user restrictions. 2. Verify that "Disallow printing" is enabled. On the managed Google Android 16 device: COBO and COPE: 1. Open a document or image from the file app and try to print. 2. Verify that printing is not possible. If wireless printing has not been disabled, this is a finding.

Fix: F-80846r1140149_fix

Configure Google Android 16 device to disable wireless printing. On the MDM console, do the following: COBO and COPE: 1. Open user restrictions. 2. Enable "Disallow printing". Configuration API: PRINTING_DISALLOWED

a

Google Android 16 must disable screen capture.

CM-6 - Low - CCI-000366 - V-276787 - SV-276787r1140153_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013300

Vuln IDs

V-276787

Rule IDs

SV-276787r1140153_rule

The screen capture feature could lead to the exposure of sensitive DOD information. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80942r1140151_chk

Review configuration settings to confirm that screen capture has been disabled. This check procedure is performed on the device management tool and the Google Android 16 device. On the MDM console: COBO and COPE: 1. Open Camera, screen capture, and audio section. 2. Verify that the "Disable Screen Capture" setting is enabled. On the managed Google Android 16 device: COBO and COPE: 1. Press the Power button and the volume down button at the same time. 2. Verify that the message "Taking screenshots is blocked by your admin" appears. If screen capture has not been disabled, this is a finding.

Fix: F-80847r1140152_fix

Install a configuration profile to disable screen capture. On the MDM console, do the following: COBO and COPE: 1. Open Camera, screen capture, and audio section. 2. Enable the "Disable Screen Capture" setting. Configuration API: screenCaptureDisabled

b

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

CM-6 - Medium - CCI-000366 - V-276788 - SV-276788r1140156_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013400

Vuln IDs

V-276788

Rule IDs

SV-276788r1140156_rule

DOD mobile devices are in constant risk of cyber threats. MTD apps mitigate these risks by providing real-time threat detection, malware prevention, and vulnerability analysis. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80943r1140154_chk

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" and then "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: F-80848r1140155_fix

Install an MTD app on managed Google Android devices.

b

Google Android 16 must implement the management setting: disable Camera.

CM-6 - Medium - CCI-000366 - V-276789 - SV-276789r1140159_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013500

Vuln IDs

V-276789

Rule IDs

SV-276789r1140159_rule

Authorizing official (AO) approval is required before the mobile device camera can be enabled for a specific user or group of users, based on a risk assessment of the operational environment. Camera use may lead to the exposure of sensitive DOD information in some operational environments. SFR ID: FMT_MOF_EXT.1.2 #47

Checks: C-80944r1140157_chk

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 configuration settings to confirm "Allow Camera" is disabled. If approved, this requirement is not applicable. Review configuration settings to confirm the device camera has been disabled. This check procedure is performed on the device management tool and the Samsung Android 16 device. On the MDM console: COBO and COPE: 1. Open Camera. 2. Verify that the "Disable camera" setting is disabled. On the managed Samsung Android 16 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: F-80849r1140158_fix

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

Google Android 16 COBO Security Technical Implementation Guide - V1R1

Compare

View

Checks: C-80903r1140034_chk

Fix: F-80808r1140035_fix

Generate Mitigation Statement:

Checks: C-80904r1140037_chk

Fix: F-80809r1140038_fix

Generate Mitigation Statement:

Checks: C-80905r1140040_chk

Fix: F-80810r1140041_fix

Generate Mitigation Statement:

Checks: C-80906r1140043_chk

Fix: F-80811r1140044_fix

Generate Mitigation Statement:

Checks: C-80907r1140046_chk

Fix: F-80812r1140047_fix

Generate Mitigation Statement:

Checks: C-80908r1140049_chk

Fix: F-80813r1140050_fix

Generate Mitigation Statement:

Checks: C-80909r1140052_chk

Fix: F-80814r1140053_fix

Generate Mitigation Statement:

Checks: C-80910r1140055_chk

Fix: F-80815r1140056_fix

Generate Mitigation Statement:

Checks: C-80911r1140058_chk

Fix: F-80816r1140661_fix

Generate Mitigation Statement:

Checks: C-80912r1140061_chk

Fix: F-80817r1140062_fix

Generate Mitigation Statement:

Checks: C-80913r1140064_chk

Fix: F-80818r1140065_fix

Generate Mitigation Statement:

Checks: C-80914r1140067_chk

Fix: F-80819r1140068_fix

Generate Mitigation Statement:

Checks: C-80915r1140070_chk

Fix: F-80820r1140071_fix

Generate Mitigation Statement:

Checks: C-80916r1140073_chk

Fix: F-80821r1140074_fix

Generate Mitigation Statement:

Checks: C-80917r1140076_chk

Fix: F-80822r1140077_fix

Generate Mitigation Statement:

Checks: C-80918r1140079_chk

Fix: F-80823r1140080_fix

Generate Mitigation Statement:

Checks: C-80919r1140082_chk

Fix: F-80824r1140083_fix

Generate Mitigation Statement:

Checks: C-80920r1140085_chk

Fix: F-80825r1140086_fix

Generate Mitigation Statement:

Checks: C-80921r1140088_chk

Fix: F-80826r1140089_fix

Generate Mitigation Statement:

Checks: C-80922r1140664_chk

Fix: F-80827r1140092_fix

Generate Mitigation Statement:

Checks: C-80923r1140094_chk

Fix: F-80828r1140095_fix

Generate Mitigation Statement:

Checks: C-80924r1140097_chk

Fix: F-80829r1140098_fix

Generate Mitigation Statement:

Checks: C-80925r1140100_chk

Fix: F-80830r1140101_fix

Generate Mitigation Statement:

Checks: C-80926r1140103_chk

Fix: F-80831r1140104_fix

Generate Mitigation Statement:

Checks: C-80927r1140106_chk

Fix: F-80832r1140107_fix

Generate Mitigation Statement:

Checks: C-80928r1140109_chk

Fix: F-80833r1140110_fix