View STIG - Google Android 16 COPE Security Technical Implementation Guide V1R2

b

Google Android 16 must be configured to enable audit logging.

AU-6 - Medium - CCI-000154 - V-276850 - SV-276850r1140342_rule

RMF Control

AU-6

Severity

Medium

CCI

CCI-000154

Version

GOOG-16-002800

Vuln IDs

V-276850

Rule IDs

SV-276850r1140342_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-81005r1140340_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-80910r1140341_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-276851 - SV-276851r1140345_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-16-006000

Vuln IDs

V-276851

Rule IDs

SV-276851r1140345_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-81006r1140343_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-80911r1140344_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-276852 - SV-276852r1140348_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-16-006100

Vuln IDs

V-276852

Rule IDs

SV-276852r1140348_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-81007r1140346_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-80912r1140347_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-276853 - SV-276853r1140351_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000057

Version

GOOG-16-006300

Vuln IDs

V-276853

Rule IDs

SV-276853r1140351_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-81008r1140349_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-80913r1140350_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-276854 - SV-276854r1140354_rule

RMF Control

AC-7

Severity

Medium

CCI

CCI-000044

Version

GOOG-16-006400

Vuln IDs

V-276854

Rule IDs

SV-276854r1140354_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-81009r1140352_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-80914r1140353_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-276855 - SV-276855r1140357_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-006500

Vuln IDs

V-276855

Rule IDs

SV-276855r1140357_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-81010r1140355_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-80915r1140356_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-276856 - SV-276856r1140360_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-001764

Version

GOOG-16-006600

Vuln IDs

V-276856

Rule IDs

SV-276856r1140360_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-81011r1140358_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-80916r1140359_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-276857 - SV-276857r1140363_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-16-006700

Vuln IDs

V-276857

Rule IDs

SV-276857r1140363_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-81012r1140361_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-80917r1140362_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-276858 - SV-276858r1140366_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-16-006750

Vuln IDs

V-276858

Rule IDs

SV-276858r1140366_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-81013r1140364_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-80918r1140365_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 Restrictions, 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-276859 - SV-276859r1140369_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000060

Version

GOOG-16-006800

Vuln IDs

V-276859

Rule IDs

SV-276859r1140369_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-81014r1140367_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-80919r1140368_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-276860 - SV-276860r1140372_rule

RMF Control

IA-2

Severity

Medium

CCI

CCI-000767

Version

GOOG-16-007200

Vuln IDs

V-276860

Rule IDs

SV-276860r1140372_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-81015r1140370_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-80920r1140371_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-276861 - SV-276861r1140375_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-000381

Version

GOOG-16-007400

Vuln IDs

V-276861

Rule IDs

SV-276861r1140375_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-81016r1140373_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-80921r1140374_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-276862 - SV-276862r1140378_rule

RMF Control

AC-8

Severity

Low

CCI

CCI-000048

Version

GOOG-16-007700

Vuln IDs

V-276862

Rule IDs

SV-276862r1140378_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-81017r1140376_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-80922r1140377_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-276863 - SV-276863r1140381_rule

RMF Control

AU-12

Severity

Medium

CCI

CCI-000169

Version

GOOG-16-007800

Vuln IDs

V-276863

Rule IDs

SV-276863r1140381_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-81018r1140379_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-80923r1140380_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-276864 - SV-276864r1140384_rule

RMF Control

SC-41

Severity

Medium

CCI

CCI-002546

Version

GOOG-16-008400

Vuln IDs

V-276864

Rule IDs

SV-276864r1140384_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-81019r1140382_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-80924r1140383_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-276865 - SV-276865r1140387_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-16-008500

Vuln IDs

V-276865

Rule IDs

SV-276865r1140387_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-81020r1140385_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-80925r1140386_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-276866 - SV-276866r1140390_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-16-008600

Vuln IDs

V-276866

Rule IDs

SV-276866r1140390_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-81021r1140388_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-80926r1140389_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-276867 - SV-276867r1140393_rule

RMF Control

AC-18

Severity

Medium

CCI

CCI-001443

Version

GOOG-16-008700

Vuln IDs

V-276867

Rule IDs

SV-276867r1140393_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-81022r1140391_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-80927r1140392_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 exceptions to the access control policy that prevent [selection: application processes, groups of application processes] from accessing [selection: all, private] data stored by other [selection: application processes, groups of application processes].

SC-39 - Medium - CCI-002530 - V-276868 - SV-276868r1140396_rule

RMF Control

SC-39

Severity

Medium

CCI

CCI-002530

Version

GOOG-16-008900

Vuln IDs

V-276868

Rule IDs

SV-276868r1140396_rule

App data sharing gives apps the ability to access the data of other apps for enhanced user functionality. However, sharing also poses a significant risk that unauthorized users or apps will obtain access to DOD sensitive information. To mitigate this risk, there are data sharing restrictions, primarily from sharing data from personal (unmanaged) apps and work (managed) apps. If a user is allowed to make exceptions to the data sharing restriction policy, the user could enable unauthorized sharing of data, leaving it vulnerable to breach. Limiting the granting of exceptions to either the administrator or common application developer mitigates this risk. Copy/paste of data between applications in different application processes or groups of application processes is considered an exception to the access control policy and therefore, the administrator must be able to enable/disable the feature. Other exceptions include allowing any data or application sharing between process groups. SFR ID: FMT_SMF.1.1 #42, FDP_ACF_EXT.1.2

Checks: C-81023r1140394_chk

Review documentation on the managed Google Android 16 device and inspect the configuration on the Google Android device to verify that the access control policy that prevents [selection: application processes] from accessing [selection: all] data stored by other [selection: application processes] is enabled. This validation procedure is performed only on the EMM Administration Console. On the EMM console: COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow cross profile copy/paste" is toggled to "ON". If the EMM console device policy is not set to disable data sharing between profiles, this is a finding.

Fix: F-80928r1140395_fix

Configure the Google Android 16 device to enable the access control policy that prevents [selection: application processes, groups of application processes] from accessing [selection: all, private] data stored by other [selection: application processes, groups of application processes]. Note: All application data is inherently sandboxed and isolated from other applications. To disable copy/paste on the EMM console: COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow cross profile copy/paste" to "ON". Configuration API: DISALLOW_CROSS_PROFILE_COPY_PASTE

b

Google Android 16 must be configured to disable multiuser modes.

AC-2 - Medium - CCI-002110 - V-276869 - SV-276869r1140399_rule

RMF Control

AC-2

Severity

Medium

CCI

CCI-002110

Version

GOOG-16-009000

Vuln IDs

V-276869

Rule IDs

SV-276869r1140399_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-81024r1140397_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-80929r1140398_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-276870 - SV-276870r1140667_rule

RMF Control

CM-7

Severity

Low

CCI

CCI-000381

Version

GOOG-16-009400

Vuln IDs

V-276870

Rule IDs

SV-276870r1140667_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-81025r1140666_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-80930r1140401_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-276871 - SV-276871r1140405_rule

RMF Control

SC-40

Severity

Medium

CCI

CCI-002536

Version

GOOG-16-009500

Vuln IDs

V-276871

Rule IDs

SV-276871r1140405_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-81026r1140403_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-80931r1140404_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-276872 - SV-276872r1140408_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009800

Vuln IDs

V-276872

Rule IDs

SV-276872r1140408_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-81027r1140406_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-80932r1140407_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-276873 - SV-276873r1140411_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009900

Vuln IDs

V-276873

Rule IDs

SV-276873r1140411_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-81028r1140409_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-80933r1140410_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-276874 - SV-276874r1140414_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-009950

Vuln IDs

V-276874

Rule IDs

SV-276874r1140414_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-81029r1140412_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-80934r1140413_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-276875 - SV-276875r1140417_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010000

Vuln IDs

V-276875

Rule IDs

SV-276875r1140417_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-81030r1140415_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-80935r1140416_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 prevent users from adding personal email accounts to the work email app.

CM-6 - Medium - CCI-000366 - V-276876 - SV-276876r1140420_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010100

Vuln IDs

V-276876

Rule IDs

SV-276876r1140420_rule

If the user is able to add a personal email account (POP3, IMAP, EAS) to the work email app, it could be used to forward sensitive DOD data to unauthorized recipients. Restricting email account addition to the administrator or restricting email account addition to allowlisted accounts mitigates this vulnerability. SFR ID: FMT_SMF.1.1 #47

Checks: C-81031r1140418_chk

Review the managed Google Android 16 work profile configuration settings to confirm that users are prevented from adding personal email accounts to the work email app. This procedure is performed on both the EMM Administration Console and the managed Google Android 16 device. COPE: On the EMM console: 1. Open "Set user restrictions". 2. Verify that "Disallow modify accounts" is toggled to "ON". On the managed Google Android 16 device: 1. Open Settings. 2. Tap "Passwords, passkeys & accounts". 3. Select "Work". 4. Tap "Add account". 5. Verify that a message is displayed to the user stating, "Action not allowed". If on the EMM console the restriction to "Disallow modify accounts" is not set, or on the managed Android 16 device the user is able to add an account in the Work section, this is a finding.

Fix: F-80936r1140419_fix

Configure the Google Android 16 device to prevent users from adding personal email accounts to the work email app. On the EMM console: COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow modify accounts" to "ON". Refer to the EMM documentation to determine how to provision users' work email accounts for the work email app. Configuration API: DISALLOW_MODIFY_ACCOUNTS

b

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

CM-6 - Medium - CCI-000366 - V-276877 - SV-276877r1140423_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010200

Vuln IDs

V-276877

Rule IDs

SV-276877r1140423_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-81032r1140421_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-80937r1140422_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

Google Android 16 must be provisioned as a fully managed device and configured to create a work profile.

CM-6 - Medium - CCI-000366 - V-276878 - SV-276878r1140426_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010300

Vuln IDs

V-276878

Rule IDs

SV-276878r1140426_rule

The Android Enterprise work profile is the designated application group for the COPE use case. SFR ID: FMT_SMF.1.1 #47

Checks: C-81033r1140424_chk

Verify that managed Google Android 16 is configured as Corporate Owned Work Managed. This procedure is performed on both the EMM Administration Console and the managed Google Android 16 device. On the EMM console, configure the default enrollment as Corporate Owned and select "Use for Work & Personal". On the managed Google Android 16 device: 1. Go to the application drawer. 2. Ensure a Personal tab and a Work tab are present. If on the EMM console the account the default enrollment is set to Corporate Owned Work Managed, or on the managed Android 16 device the user does not have a Work tab, this is a finding.

Fix: F-80938r1140425_fix

Configure the Google Android 16 device as corporate owned with a work profile. On the EMM console, configure the default enrollment as Corporate Owned, and select "Use for Work & Personal". Refer to the EMM documentation to determine how to configure the device.

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-276879 - SV-276879r1140429_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010400

Vuln IDs

V-276879

Rule IDs

SV-276879r1140429_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-81034r1140427_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-80939r1140428_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.

b

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

CM-6 - Medium - CCI-000366 - V-276880 - SV-276880r1140679_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010500

Vuln IDs

V-276880

Rule IDs

SV-276880r1140679_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-81035r1140677_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-80940r1140678_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.

b

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

CM-6 - Medium - CCI-000366 - V-276881 - SV-276881r1140676_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-010600

Vuln IDs

V-276881

Rule IDs

SV-276881r1140676_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-81036r1140674_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-80941r1140675_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-276882 - SV-276882r1140438_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

GOOG-16-010800

Vuln IDs

V-276882

Rule IDs

SV-276882r1140438_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-81037r1140436_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-80942r1140437_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-276883 - SV-276883r1140441_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-010900

Vuln IDs

V-276883

Rule IDs

SV-276883r1140441_rule

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

Checks: C-81038r1140439_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-80943r1140440_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-276884 - SV-276884r1140444_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-011000

Vuln IDs

V-276884

Rule IDs

SV-276884r1140444_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-81039r1140442_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-80944r1140443_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-276885 - SV-276885r1140447_rule

RMF Control

AC-6

Severity

Medium

CCI

CCI-002235

Version

GOOG-16-012200

Vuln IDs

V-276885

Rule IDs

SV-276885r1140447_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-81040r1140445_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-80945r1140446_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-276886 - SV-276886r1140450_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000370

Version

GOOG-16-012300

Vuln IDs

V-276886

Rule IDs

SV-276886r1140450_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-81041r1140448_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-80946r1140449_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-276887 - SV-276887r1140453_rule

RMF Control

SC-4

Severity

Low

CCI

CCI-001090

Version

GOOG-16-012400

Vuln IDs

V-276887

Rule IDs

SV-276887r1140453_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-81042r1140451_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-80947r1140452_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-276888 - SV-276888r1140456_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000370

Version

GOOG-16-012500

Vuln IDs

V-276888

Rule IDs

SV-276888r1140456_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-81043r1140454_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-80948r1140455_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-276889 - SV-276889r1188340_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013000

Vuln IDs

V-276889

Rule IDs

SV-276889r1188340_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-81044r1183778_chk

Verify the Android device user has been trained to not perform a factory wipe without the approval of the authorizing official (AO). Confirm by reviewing the site's mobile device training records or the User Agreement. This is a User-Based Enforcement (UBE) control. If the Android device user has not been trained to not perform a factory wipe without the approval of the AO, this is a finding.

Fix: F-80949r1188339_fix

Train users to not perform a factory reset on the Android device without AO approval. Document training via the site's mobile device training records or the User Agreement. This is a UBE control. Note: It is not possible for the MDM to enforce this control when the Android device is deployed in COPE mode.

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-276890 - SV-276890r1140462_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013100

Vuln IDs

V-276890

Rule IDs

SV-276890r1140462_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-81045r1140460_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-80950r1140461_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-276891 - SV-276891r1140465_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013200

Vuln IDs

V-276891

Rule IDs

SV-276891r1140465_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-81046r1140463_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-80951r1140464_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-276892 - SV-276892r1140468_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-16-013300

Vuln IDs

V-276892

Rule IDs

SV-276892r1140468_rule

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

Checks: C-81047r1140466_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-80952r1140467_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-276893 - SV-276893r1140471_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013400

Vuln IDs

V-276893

Rule IDs

SV-276893r1140471_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-81048r1140469_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-80953r1140470_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-276894 - SV-276894r1140474_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-16-013500

Vuln IDs

V-276894

Rule IDs

SV-276894r1140474_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-81049r1140472_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-80954r1140473_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 COPE Security Technical Implementation Guide - V1R2

Compare

View

Checks: C-81005r1140340_chk

Fix: F-80910r1140341_fix

Generate Mitigation Statement:

Checks: C-81006r1140343_chk

Fix: F-80911r1140344_fix

Generate Mitigation Statement:

Checks: C-81007r1140346_chk

Fix: F-80912r1140347_fix

Generate Mitigation Statement:

Checks: C-81008r1140349_chk

Fix: F-80913r1140350_fix

Generate Mitigation Statement:

Checks: C-81009r1140352_chk

Fix: F-80914r1140353_fix

Generate Mitigation Statement:

Checks: C-81010r1140355_chk

Fix: F-80915r1140356_fix

Generate Mitigation Statement:

Checks: C-81011r1140358_chk

Fix: F-80916r1140359_fix

Generate Mitigation Statement:

Checks: C-81012r1140361_chk

Fix: F-80917r1140362_fix

Generate Mitigation Statement:

Checks: C-81013r1140364_chk

Fix: F-80918r1140365_fix

Generate Mitigation Statement:

Checks: C-81014r1140367_chk

Fix: F-80919r1140368_fix

Generate Mitigation Statement:

Checks: C-81015r1140370_chk

Fix: F-80920r1140371_fix

Generate Mitigation Statement:

Checks: C-81016r1140373_chk

Fix: F-80921r1140374_fix

Generate Mitigation Statement:

Checks: C-81017r1140376_chk

Fix: F-80922r1140377_fix

Generate Mitigation Statement:

Checks: C-81018r1140379_chk

Fix: F-80923r1140380_fix

Generate Mitigation Statement:

Checks: C-81019r1140382_chk

Fix: F-80924r1140383_fix

Generate Mitigation Statement:

Checks: C-81020r1140385_chk

Fix: F-80925r1140386_fix

Generate Mitigation Statement:

Checks: C-81021r1140388_chk

Fix: F-80926r1140389_fix

Generate Mitigation Statement:

Checks: C-81022r1140391_chk

Fix: F-80927r1140392_fix

Generate Mitigation Statement:

Checks: C-81023r1140394_chk

Fix: F-80928r1140395_fix

Generate Mitigation Statement:

Checks: C-81024r1140397_chk

Fix: F-80929r1140398_fix

Generate Mitigation Statement:

Checks: C-81025r1140666_chk

Fix: F-80930r1140401_fix

Generate Mitigation Statement:

Checks: C-81026r1140403_chk

Fix: F-80931r1140404_fix

Generate Mitigation Statement:

Checks: C-81027r1140406_chk

Fix: F-80932r1140407_fix

Generate Mitigation Statement:

Checks: C-81028r1140409_chk

Fix: F-80933r1140410_fix

Generate Mitigation Statement:

Checks: C-81029r1140412_chk

Fix: F-80934r1140413_fix

Generate Mitigation Statement:

Checks: C-81030r1140415_chk

Fix: F-80935r1140416_fix