Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

Google Android 13 COBO Security Technical Implementation Guide

  • Version/Release: V2R1
  • Published: 2024-06-05
  • Released: 2024-07-24
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
Google Android 13 must be configured to enable audit logging.
AU-6 - Medium - CCI-000154 - V-254733 - SV-254733r959010_rule
RMF Control
AU-6
Severity
Medium
CCI
CCI-000154
Version
GOOG-13-002800
Vuln IDs
  • V-254733
Rule IDs
  • SV-254733r959010_rule
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. To be useful, administrators must have the ability to view the audit logs. SFR ID: FMT_SMF_EXT.1.1 #32
Checks: C-58344r862396_chk

Inspect the configuration on the managed Google Android 13 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-58290r862397_fix

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

b
Google Android 13 must be configured to enforce a minimum password length of six characters.
- Medium - CCI-004066 - V-254734 - SV-254734r997346_rule
RMF Control
Severity
Medium
CCI
CCI-004066
Version
GOOG-13-006000
Vuln IDs
  • V-254734
Rule IDs
  • SV-254734r997346_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 do each attempt, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise. SFR ID: FMT_SMF_EXT.1.1 #1a
Checks: C-58345r862399_chk

Review managed Google Android 13 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 13 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Verify Numeric Complex, Alphabetic, Alphanumeric, or Complex is selected. 5. Open "Minimum password length". 6. Verify "6" is set for number of characters. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify "Minimum password quality" is set to Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Verify the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 13 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Tap "Pin or Password". 4. Verify Password length required is at least "6". If the device password length is not set to six characters or more on EMM console or on the managed Google Android 13 device, this is a finding.

Fix: F-58291r862400_fix

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

b
Google Android 13 must be configured to not allow passwords that include more than four repeating or sequential characters.
CM-6 - Medium - CCI-000366 - V-254735 - SV-254735r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-006100
Vuln IDs
  • V-254735
Rule IDs
  • SV-254735r959010_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_EXT.1.1 #1b
Checks: C-58346r862402_chk

Review managed Google Android 13 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 13 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 13 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Select "PIN". 4. Try to enter a new PIN with repeating numbers. 5. Verify Password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed. If the EMM console device policy is set to a password with more than two repeating or sequential characters or on the managed Google Android 13 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-58292r862403_fix

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

b
Google Android 13 must be configured to enable a screen-lock policy that will lock the display after a period of inactivity.
AC-11 - Medium - CCI-000057 - V-254736 - SV-254736r958402_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000057
Version
GOOG-13-006200
Vuln IDs
  • V-254736
Rule IDs
  • SV-254736r958402_rule
The screen-lock timeout helps protect the device from unauthorized access. Devices without a screen-lock timeout provide an 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 and possibly access to DOD networks. SFR ID: FMT_SMF_EXT.1.1 #2a
Checks: C-58347r862405_chk

Review managed Google Android 13 device configuration settings to determine if the mobile device is enforcing a screen-lock policy that will lock the display after a period of inactivity. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 13 device. On the EMM Console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Max time to screen lock" is set to any number desired, the units are in seconds. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Verify that "Max time to screen lock" is set to any number desired, the units are in seconds. ___________________________ On the managed Google Android 13 device: COBO and COPE: 1. Open Settings >> Display. 2. Tap "Screen timeout". 3. Ensure the Screen timeout value is set to the desired value and cannot be set to a larger value. If the EMM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity or on the managed Google Android 13 device, the device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity, this is a finding.

Fix: F-58293r862406_fix

Configure the Google Android 13 device to enable a screen-lock policy that will lock the display after a period of inactivity. On the EMM Console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Set "Max time to screen lock" to any number desired. Note: The units are in seconds. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Set "Max time to screen lock" to any number desired. Note: The units are in seconds.

b
Google Android 13 must be configured to lock the display after 15 minutes (or less) of inactivity.
AC-11 - Medium - CCI-000057 - V-254737 - SV-254737r958402_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000057
Version
GOOG-13-006300
Vuln IDs
  • V-254737
Rule IDs
  • SV-254737r958402_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_EXT.1.1 #2b
Checks: C-58348r862408_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: Google Android 13 does not support the 15 minute increment. The available allowable selection is 10 mins then increases to 30 minutes. Therefore, the control should be set to 10 minutes. This validation procedure is performed on both the EMM Administration Console and the Android 13 device. On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Max time to screen lock" is set to "600". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Max time to screen lock" is set to "600". Note: The units are in seconds. On the managed Google Android 13 device: COBO and COPE: 1. Open Settings >> Display. 2. Tap "Screen timeout". 3. Ensure the Screen timeout value is set to "600" seconds. If the EMM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity of 600 seconds, this is a finding.

Fix: F-58294r862409_fix

Configure the Google Android 13 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: Google Android 13 does not support the 15 minute increment. The available allowable selection is 10 mins then increases to 30 minutes. Therefore, the control will be set to 10 minutes. On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Set "Max time to screen lock" to "600". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Set "Max time to screen lock" to "600". Note: The units are in seconds.

b
Google Android 13 must be configured to not allow more than 10 consecutive failed authentication attempts.
AC-7 - Medium - CCI-000044 - V-254738 - SV-254738r958388_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
GOOG-13-006400
Vuln IDs
  • V-254738
Rule IDs
  • SV-254738r958388_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 less 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_EXT.1.1 #2c, FIA_AFL_EXT.1.5
Checks: C-58349r862411_chk

Review managed Google Android 13 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 13 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 13 device: COBO and COPE: 1. Lock the device screen. 2. Attempt to unlock the screen and validate that the device autowipes after specified number of invalid entries. Note: Perform this verification only with a test phone set up with a production profile. If the EMM console device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, or if on the managed Google Android 13 device the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.

Fix: F-58295r862412_fix

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

b
Google Android 13 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-254739 - SV-254739r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-006500
Vuln IDs
  • V-254739
Rule IDs
  • SV-254739r959010_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_EXT.1.1 #8a
Checks: C-58350r862414_chk

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

Fix: F-58296r862415_fix

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

b
Google Android 13 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-254740 - SV-254740r959010_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-001764
Version
GOOG-13-006600
Vuln IDs
  • V-254740
Rule IDs
  • SV-254740r959010_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 MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. Core application: Any application integrated into the 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_EXT.1.1 #8b
Checks: C-58351r862417_chk

Review managed Google Android 13 device configuration settings to determine if the mobile device has an application allowlist configured. Verify all applications listed on the allowlist have been approved by the Approving Official (AO). On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Verify all selected apps are AO approved. On the managed Google Android 13 device: COBO and COPE: 1. Open the managed Google Play Store. 2. Verify that only the approved apps are visible. Note: Managed Google Play is an allowed App Store. If the EMM console list of selected managed Google Play apps includes non-approved apps, this is a finding. Note: The application allowlist will include approved core applications (included in the OS by the OS vendor) and pre-installed applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and pre-installed applications. For Google Android, there are no pre-installed applications.

Fix: F-58297r862418_fix

Configure the Google Android 13 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 13 allowlist must be configured to not include applications with the following characteristics: 1. Back up mobile device (MD) data to non-DOD cloud servers (including user and application access to cloud backup services); 2. Transmit MD diagnostic data to non-DOD servers; 3. Voice assistant application if available when MD is locked; 4. Voice dialing application if available when MD is locked; 5. Allows synchronization of data or applications between devices associated with user; and 6. Allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs or printers.
CM-6 - Medium - CCI-000366 - V-254741 - SV-254741r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-006700
Vuln IDs
  • V-254741
Rule IDs
  • SV-254741r959010_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 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_EXT.1.1 #8b
Checks: C-58352r862420_chk

Review managed Google Android 13 device configuration settings to determine if the mobile device has an application allowlist configured and that the application allowlist does not include applications with the following characteristics: - Back up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmit MD diagnostic data to non-DOD servers; - Voice assistant application if available when MD is locked; - Voice dialing application if available when MD is locked; - Allows synchronization of data or applications between devices associated with user; - Payment processing; and - Allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. This validation procedure is performed only on the EMM Administration Console. On the EMM console: 1. Review the list of selected Managed Google Play apps. 2. Review the details and privacy policy of each selected app to ensure the app does not include prohibited characteristics. If the EMM console device policy includes applications with unauthorized characteristics, this is a finding.

Fix: F-58298r862421_fix

Configure the Google Android 13 device application allowlist to exclude applications with the following characteristics: - Back up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmit MD diagnostic data to non-DOD servers; - Voice assistant application if available when MD is locked; - Voice dialing application if available when MD is locked; - Allows synchronization of data or applications between devices associated with user; - Payment processing; and - Allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. On the EMM Console: 1. Go to the Android app catalog for managed Google Play. 2. Before selecting an app, review the app details and privacy policy to ensure the app does not include prohibited characteristics.

b
Google Android 13 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-254742 - SV-254742r959010_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000060
Version
GOOG-13-006800
Vuln IDs
  • V-254742
Rule IDs
  • SV-254742r959010_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 (MOS) to not send notifications to the lock screen mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #18
Checks: C-58353r862423_chk

Review managed Google Android 13 device settings to determine if the Google Android 13 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 13 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 13 device: COBO: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "Privacy". 3. Verify that "Show sensitive content only when unlocked" is selected. COPE: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "When work profile is locked". 3. Verify that "Hide sensitive work content" is selected. If the EMM console device policy allows work notifications on the lock screen, or the managed Google Android 13 device allows work notifications on the lock screen, this is a finding.

Fix: F-58299r862424_fix

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

b
Google Android 13 must be configured to disable trust agents.
IA-2 - Medium - CCI-000765 - V-254743 - SV-254743r997347_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000765
Version
GOOG-13-007200
Vuln IDs
  • V-254743
Rule IDs
  • SV-254743r997347_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 non-password authentication mechanisms, users are forced to use passcodes that meet DOD passcode requirements. SFR ID: FMT_SMF_EXT.1.1 #22, FIA_UAU.5.1
Checks: C-58354r862426_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 13 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 13 device: COBO and COPE: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the EMM console, "disable trust agents" is not selected, or on the managed Google Android 13 device a trust agent can be enabled, this is a finding.

Fix: F-58300r862427_fix

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

b
Google Android 13 must be configured to disable developer modes.
CM-7 - Medium - CCI-000381 - V-254744 - SV-254744r958478_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
GOOG-13-007400
Vuln IDs
  • V-254744
Rule IDs
  • SV-254744r958478_rule
Developer modes expose features of the mobile operating system (MOS) 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_EXT.1.1 #26
Checks: C-58355r862429_chk

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

Fix: F-58301r862430_fix

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

a
Google Android 13 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-254745 - SV-254745r958390_rule
RMF Control
AC-8
Severity
Low
CCI
CCI-000048
Version
GOOG-13-007700
Vuln IDs
  • V-254745
Rule IDs
  • SV-254745r958390_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_EXT.1.1 #36
Checks: C-58356r862432_chk

The DOD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each managed Android 13 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each managed Android 13 mobile device. Determine which method is used at the Google Android 13 device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Google Android 13 device users and verify the agreement includes the required DOD warning banner text. Validation Procedure for Method #2: On the EMM Console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Verify the message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Verify the message. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the EMM console device policy is not set to display a warning banner with the appropriate designated wording or on the managed Google Android 13 device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.

Fix: F-58302r862433_fix

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

b
Google Android 13 must be configured to generate audit records for the following auditable events: Detected integrity violations.
AU-12 - Medium - CCI-000169 - V-254746 - SV-254746r958442_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000169
Version
GOOG-13-007800
Vuln IDs
  • V-254746
Rule IDs
  • SV-254746r958442_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 Requirement Statement 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_EXT.1.1 #37
Checks: C-58357r862435_chk

Review managed Google Android 13 device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: Detected integrity violations. This validation procedure is performed only on the EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Verify that "Enable security logging" is toggled to "ON". If the EMM console device policy is not set to enable security logging, this is a finding.

Fix: F-58303r862436_fix

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

b
Google Android 13 must be configured to disable USB mass storage mode.
SC-41 - Medium - CCI-002546 - V-254747 - SV-254747r958478_rule
RMF Control
SC-41
Severity
Medium
CCI
CCI-002546
Version
GOOG-13-008400
Vuln IDs
  • V-254747
Rule IDs
  • SV-254747r958478_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_EXT.1.1 #39
Checks: C-58358r862438_chk

Review managed Google Android 13 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 13 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 "Disallow USB file transfer" is toggled to "ON". ______________________________ On the managed Google Android 13 device: 1. Plug a USB cable into the managed Google Android 13 device and connect to a non-DOD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify "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 13 device, the device policy is not set to disable USB mass storage mode, this is a finding.

Fix: F-58304r862439_fix

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

b
Google Android 13 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.
SC-4 - Medium - CCI-001090 - V-254748 - SV-254748r959010_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
GOOG-13-008500
Vuln IDs
  • V-254748
Rule IDs
  • SV-254748r959010_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_EXT.1.1 #40
Checks: C-58359r862441_chk

Review managed Google Android 13 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 13 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify "Enable backup service" is toggled to "OFF". On the managed Google Android 13 device: COBO: 1. Go to Settings >> System >> Backup. 2. Verify Backup settings is "Not available". COPE: 1. Go to Settings >> System >> Backup. 2. Select "Work". 3. Verify 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 13 device, the device policy is not set to disable the capability to back up to a locally connected system, and this is a finding.

Fix: F-58305r862442_fix

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

b
Google Android 13 must be configured to not allow backup of [all applications, configuration data] to remote systems.
SC-4 - Medium - CCI-001090 - V-254749 - SV-254749r959010_rule
RMF Control
SC-4
Severity
Medium
CCI
CCI-001090
Version
GOOG-13-008600
Vuln IDs
  • V-254749
Rule IDs
  • SV-254749r959010_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 (MOS). 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_EXT.1.1 #40
Checks: C-58360r862444_chk

Review managed Google Android 13 device configuration settings to determine if the capability to back up to a remote system has been disabled. Note: Since personal accounts cannot be added to the work profile (GOOG-13-009800), this control only impacts personal profile accounts. Site can allow backup based on local policy. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 13 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify "Enable backup service" is toggled to "OFF". On the managed Google Android 13 device: COBO: 1. Go to Settings >> System >> System >> Backup. 2. Verify Backup settings is "Not available". COPE: 1. Go to Settings >> System >> System >> Backup. 2. Select "Work". 3. Verify 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 13 device, the device policy is not set to disable the capability to back up to a remote system, this is a finding.

Fix: F-58306r862445_fix

Configure the Google Android 13 device to disable backup to remote systems (including commercial clouds). On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to "OFF". Note: Since personal accounts cannot be added to the work profile (GOOG-13-009800), this control only impacts personal profile accounts. Site can allow backup based on local policy.

b
Google Android 13 must be configured to disable multiuser modes.
CM-6 - Medium - CCI-000366 - V-254750 - SV-254750r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-009000
Vuln IDs
  • V-254750
Rule IDs
  • SV-254750r959010_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_EXT.1.1 #47a
Checks: C-58361r862447_chk

Review documentation on the managed Google Android 13 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 13 device. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify "Disallow modify accounts" is toggled to "ON". On the managed Google Android 13 device: COBO and COPE: 1. Go to Settings >> Passwords & accounts >> Accounts for Owner. 2. Tap "Add account". 3. Verify the action is not allowed. If the EMM console device policy is not set to disable multi-user modes or on the managed Google Android 13 device, the device policy is not set to disable multi-user modes, this is a finding.

Fix: F-58307r862448_fix

Configure the Google Android 13 device to disable multi-user modes. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow modify accounts" to "ON".

a
Google Android 13 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-6 - Low - CCI-000366 - V-254751 - SV-254751r959010_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GOOG-13-009400
Vuln IDs
  • V-254751
Rule IDs
  • SV-254751r959010_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-58362r862450_chk

Determine if the AO has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify Bluetooth has been disabled. On the EMM console: COBO: 1. Open "User restrictions" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". COPE: 1. Open "User restrictions on parent" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". On the managed Google Android 13 device: COBO and COPE: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Verify "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 13 device: 1. Go to Settings >> Connected Devices. 2. Verify only approved Bluetooth connected devices using approved profiles are listed. If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an EMM-managed device policy, this is a finding. If the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under "Connected devices", this is a finding.

Fix: F-58308r862451_fix

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

b
Google Android 13 must be configured to disable ad hoc wireless client-to-client connection capability.
SC-40 - Medium - CCI-002536 - V-254752 - SV-254752r987886_rule
RMF Control
SC-40
Severity
Medium
CCI
CCI-002536
Version
GOOG-13-009500
Vuln IDs
  • V-254752
Rule IDs
  • SV-254752r987886_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 of the DOD mobile device. SFR ID: FMT_SMF_EXT.1.1/WLAN
Checks: C-58363r862453_chk

Review the managed Google Android 13 device configuration settings to determine if the mobile device is configured to disable ad hoc wireless client-to-client connection capability. This validation procedure is performed on both the MDM Administration console and the managed Google Android 13 device. On the MDM console: COBO: 1. Open "Settings Management". 2. Verify "Set location" is toggled to "OFF". COPE: 1. Open "User restrictions on parent". 2. Verify "Disallow config location" is toggled to "ON". 3. Verify "Disallow share location" is toggled to "ON". On the managed Google Android 13 device: COBO and COPE: 1. Go to Settings >> Network & Internet >> Network preferences. 2. Verify "Wi-Fi Direct" is greyed out and unavailable. If the EMM console device policy is not set to disable Location sharing and configuration, this is a finding.

Fix: F-58309r862454_fix

Configure the Google Android 13 device to disable ad hoc wireless client-to-client connection capability. On the MDM console: COBO: 1. Open "Settings Management". 2. Toggle "Set location" to "OFF". COPE: 1. Open "User restrictions on parent". 2. Toggle "Disallow config location" to "ON". 3. Toggle "Disallow share location" to "ON". Note: Ad hoc and Wi-Fi Direct requires Location services to function; therefore, disabling this setting will disable the ad hoc and Wi-Fi Direct feature.

b
Google Android 13 users must complete required training.
CM-6 - Medium - CCI-000366 - V-254753 - SV-254753r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-009800
Vuln IDs
  • V-254753
Rule IDs
  • SV-254753r959010_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-58364r862456_chk

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

Fix: F-58310r862457_fix

All Google Android 13 device users must complete training on the following training topics (users must acknowledge that they have reviewed training via a signed User Agreement or similar written record): - Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. - Need to ensure no DOD data is saved to the personal space or transmitted from a personal app (for example, from personal email). - If the Purebred key management app is used, users are responsible for maintaining positive control of their credentialed device at all times. The DOD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and to report any loss of control so the credentials can be revoked. Upon device retirement, turn-in, or reassignment, ensure that a factory data reset is performed prior to device hand-off. Follow mobility service provider decommissioning procedures as applicable. - How to configure the following UBE controls (users must configure the control) on the Google device: **Secure use of Calendar Alarm **Local screen mirroring and Mirroring procedures (authorized/not authorized for use) **Do not upload DOD contacts via smart call and caller ID services **Do not remove DOD intermediate and root PKI digital certificates **Disable Wi-Fi Sharing **Do not configure a DOD network (work) VPN profile on any third-party VPN client installed in the personal space **If Bluetooth connections are approved for mobile device, types of allowed connections (for example car hands-free, but not Bluetooth wireless keyboard) **How to perform a full device wipe - AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.) in the Google device personal space.

b
Google Android 13 must be configured to enforce that Wi-Fi Sharing is disabled.
CM-6 - Medium - CCI-000366 - V-254754 - SV-254754r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-009900
Vuln IDs
  • V-254754
Rule IDs
  • SV-254754r959010_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 #47
Checks: C-58365r862459_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 Wi-Fi Sharing is disabled: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "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 13 device: COBO and COPE: 1. Go to Settings >> Network & Internet. 2. Verify "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 13 device "Hotspot & tethering" is enabled, this is a finding.

Fix: F-58311r862460_fix

Configure the Google Android 13 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 config tethering" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON".

b
Google Android 13 must have the DOD root and intermediate PKI certificates installed.
CM-6 - Medium - CCI-000366 - V-254755 - SV-254755r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-010000
Vuln IDs
  • V-254755
Rule IDs
  • SV-254755r959010_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_EXT.1.1 #47
Checks: C-58366r862462_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 13 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 13 device: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that DOD root and intermediate PKI certificates are listed under the User tab in the Work section. If on the EMM console the DOD root and intermediate certificates are not listed in a profile, or the managed Android 13 device does not list the DOD root and intermediate certificates under the user tab, this is a finding.

Fix: F-58312r862463_fix

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

b
The Google Android 13 work profile must be configured to enforce the system application disable list.
CM-6 - Medium - CCI-000366 - V-254756 - SV-254756r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-010200
Vuln IDs
  • V-254756
Rule IDs
  • SV-254756r959010_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 13 by Google. Preinstalled application: Additional noncore applications included in the Google Android 13 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_EXT.1.1 #47
Checks: C-58367r862465_chk

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

Configure the Google Android 13 device to enforce the system application disable list. The required configuration is the default configuration when the device is enrolled. If the device configuration is changed, use the following procedure to bring the device back into compliance: On the EMM console: COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Enter package names of apps to hide. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Enter package names of apps to hide. Configure a list of approved Google core and preinstalled apps in the core app allowlist.

b
Google Android 13 must be configured to disallow configuration of date and time.
CM-6 - Medium - CCI-000366 - V-254757 - SV-254757r959010_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-010600
Vuln IDs
  • V-254757
Rule IDs
  • SV-254757r959010_rule
Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events. Periodically synchronizing internal clocks with an authoritative time source is necessary to correctly correlate the timing of events that occur across the enterprise. The three authoritative time sources for Google Android 13 are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DOD network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier. Time stamps generated by the audit system in Google Android 13 must include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-58368r862468_chk

Review the managed Google Android 13 device configuration settings to confirm that autofill services are disabled. This procedure is performed on both the EMM Administration console and the managed Google Android 13 device. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow config date time" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Verify "Disallow config date time" is toggled to "ON". On the managed Google Android 13 device: COBO and COPE: 1. Open Settings. 2. Tap "System". 3. Tap "Date & times". 4. Verify "Set time automatically" is grayed out and is "Enabled by admin". If on the EMM console "Disallow config date time" is not set to "On", or on the managed Android 13 device "User network-provided time" is not grayed out, this is a finding.

Fix: F-58314r862469_fix

Configure the Google Android 13 device to set auto network time. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config date time" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config date time" to "ON".

c
Android 13 devices must have the latest available Google Android 13 operating system installed.
CM-6 - High - CCI-000366 - V-254758 - SV-254758r959010_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GOOG-13-010800
Vuln IDs
  • V-254758
Rule IDs
  • SV-254758r959010_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_EXT.1.1 #47
Checks: C-58369r862471_chk

Review device configuration settings to confirm the Google Android device has the most recently released version of managed Google Android 13 installed. This procedure is performed on both the EMM console and the managed Google Android 13 device. In the EMM management console, review the version of Google Android 13 installed on a sample of managed devices. This procedure will vary depending on the EMM product. On the managed Google Android 13 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 13 operating system on any reviewed devices is not the latest released by Google, this is a finding. Google's Android operating system patch website: https://source.android.com/security/bulletin/ Android versions for Pixel devices: https://developers.google.com/android/images

Fix: F-58315r862472_fix

Install the latest released version of the Google Android 13 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 13 devices must be configured to disable the use of third-party keyboards.
CM-6 - Low - CCI-000366 - V-254759 - SV-254759r959010_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GOOG-13-010900
Vuln IDs
  • V-254759
Rule IDs
  • SV-254759r959010_rule
Many third-party keyboard applications are known to contain malware. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-58370r862474_chk

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

Fix: F-58316r862475_fix

Configure the Google Android 13 device to disallow the use of third-party keyboards. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Select only the approved keyboard. Additionally, Admins can configure application allowlists for Google Play that do not have any third-party keyboards for user installation.

a
Android 13 devices must be configured to enable Common Criteria Mode (CC Mode).
CM-6 - Low - CCI-000366 - V-254760 - SV-254760r959010_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GOOG-13-011000
Vuln IDs
  • V-254760
Rule IDs
  • SV-254760r959010_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_EXT.1.1 #47
Checks: C-58371r862477_chk

Review the managed Google Android 13 configuration settings to confirm CC mode is enabled. This procedure is performed on the EMM console. COBO and COPE: 1. Open Device owner management. 2. Verify "Enable Common Criteria mode" is toggled to "ON". If CC mode is not enabled, this is a finding.

Fix: F-58317r862478_fix

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

b
Google Android 13 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-254761 - SV-254761r959010_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002235
Version
GOOG-13-012200
Vuln IDs
  • V-254761
Rule IDs
  • SV-254761r959010_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-58372r862480_chk

Review the device configuration to confirm that the USB port is disabled except for charging the device. On the EMM console: 1. Open "Set user restrictions". 2. Verify "Enable USB" is toggled to "OFF". If on EMM console the USB port is not disabled, this is a finding.

Fix: F-58318r862481_fix

Configure Google Android 13 device to disable the USB port (except for charging the device). COPE and COBO: On the EMM console: 1. Open "Set user restrictions". 2. Toggle "Enable USB" to "OFF".

b
The Google Android 13 must allow only the administrator (EMM) to install/remove DOD root and intermediate PKI certificates.
CM-6 - Medium - CCI-000366 - V-254762 - SV-254762r970707_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GOOG-13-012300
Vuln IDs
  • V-254762
Rule IDs
  • SV-254762r970707_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-58373r862483_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 "Disallow config credentials" is toggled to "ON". On the Google Android 13 device: 1. Open Settings. 2. Tap "Security". 3. Tap "Advanced". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify the user is unable to untrust or remove any work certificates. If on the Google Android 13 device the user is able to remove certificates, this is a finding.

Fix: F-58319r862484_fix

Configure Google Android 13 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".

a
Google Android 13 must allow only the Administrator (MDM) to perform the following management function: Disable Phone Hub.
SC-4 - Low - CCI-001090 - V-254763 - SV-254763r959010_rule
RMF Control
SC-4
Severity
Low
CCI
CCI-001090
Version
GOOG-13-012400
Vuln IDs
  • V-254763
Rule IDs
  • SV-254763r959010_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-58374r862486_chk

Review the EMM configuration to confirm phone hub has been disabled. On the EMM console: 1. Open "Set user restrictions". 2. Verify "Nearby notification streaming policy" is set to "NEARBY_STREAMING_DISABLED". If on EMM console the "Nearby Streaming Policy" is not set to "NEARBY_STREAMING_DISABLED", this is a finding. Note: From a Chromebook, if a device is connected to the Phone Hub, try to set up the Notifications and it will fail to connect to the device to complete the set up if phone hub has been disabled on the DOD Android device.

Fix: F-58320r862487_fix

Configure Google Android 13 device to disable the nearby notification streaming policy to disable Phone Hub. COPE and COBO: On the EMM console: 1. Open "Set user restrictions". 2. Toggle "Nearby Streaming Policy" to "NEARBY_STREAMING_DISABLED".