Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Google Android 17 COPE Security Technical Implementation Guide

V1R1 · · · Released 29 Jun 2026 · 47 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of War (DoW) 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.
Supporting documents DISA companion ZIP · 2.7 MB 5 PDFs

Bundled by DISA alongside this STIG release: overview, revision history, and readme files. Download the full archive or open an individual PDF.

Download full ZIP U_Google_Android_17_Y26M06_STIG.zip
Sort by
b
Google Android 17 must be configured to enforce a minimum password length of six characters.
Medium - CCI-004066 - V-284794 - SV-284794r1240379_rule
RMF Control
Severity
M
CCI
CCI-004066
Version
GOOG-17-005000
Vuln IDs
  • V-284794
Rule IDs
  • SV-284794r1240379_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 #1
Checks: C-89364r1240378_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device is enforcing a minimum password length of six characters. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Verify that Numeric Complex, Alphabetic, Alphanumeric, or Complex is selected. 5. Open "Minimum password length". 6. Verify the number of characters is set to "6". COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify that "Minimum password quality" is set to Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Verify that the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 17 device: COBO and COPE: 1. Open Settings >> Security & privacy >> Device unlock >> Screen lock. 2. Enter current password. 3. Tap "Pin or Password". 4. Verify that password length required is at least "6". If the device password length is not set to six characters or more on the EMM console or on the managed Google Android 17 device, this is a finding.

Fix: F-89269r1240088_fix

Configure the Google Android 17 device to enforce a minimum password length of six characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Enter in the number of characters as "6". COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Open "Minimum password quality". 5. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 6. Open "Minimum password length". 7. Enter in the number of characters as "6". Configuration API: setPasswordMinimumLength

b
Google Android 17 must be configured to not allow passwords that include more than four repeating or sequential characters.
Medium - CCI-004066 - V-284795 - SV-284795r1240381_rule
RMF Control
Severity
M
CCI
CCI-004066
Version
GOOG-17-005100
Vuln IDs
  • V-284795
Rule IDs
  • SV-284795r1240381_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 #1
Checks: C-89365r1240380_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device is prohibiting passwords with more than four repeating or sequential characters. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Verify that quality is set to "Numeric (Complex)" or higher. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify that quality is set to "Numeric (Complex)" or higher. ____________________________ On the managed Google Android 17 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Select "PIN". 4. Try to enter a new PIN using repeating numbers. 5. Verify that password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed. If the EMM console device policy is set to a password with more than two repeating or sequential characters, or if on the managed Google Android 17 device the device policy is set to a password with more than two repeating or sequential characters, this is a finding. Note: Alphabetic, Alphanumeric, and Complex are also acceptable selections, but these selections will cause the user to select a complex password, which is not required by the STIG.

Fix: F-89270r1240091_fix

Configure the Google Android 17 device to prevent passwords from containing more than four repeating or sequential characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Set password quality to "Numeric (Complex)". COPE: 1. Open "Password constraints". 2. Select "Personal Profile". 3. Set password quality to "Numeric (Complex)". Note: Alphabetic, Alphanumeric, and Complex are also acceptable selections, but these selections will cause the user to select a complex password, which is not required by the STIG. Configuration API: setRequiredPasswordComplexity

b
Google Android 17 must be configured to lock the display after 15 minutes (or less) of inactivity.
AC-11 - Medium - CCI-000057 - V-284796 - SV-284796r1240383_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000057
Version
GOOG-17-005200
Vuln IDs
  • V-284796
Rule IDs
  • SV-284796r1240383_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 #2
Checks: C-89366r1240382_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 17 settings user interface (UI) does not support the 15-minute increment, but this value can be set by the MDM. This validation procedure is performed on the EMM administration console. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Max time to screen lock" is set to "900". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Max time to screen lock" is set to "900". Note: The units are in seconds. If the EMM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity of 900 seconds, this is a finding.

Fix: F-89271r1240094_fix

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

b
Google Android 17 must be configured to not allow more than 10 consecutive failed authentication attempts.
AC-7 - Medium - CCI-000044 - V-284797 - SV-284797r1240385_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
GOOG-17-005300
Vuln IDs
  • V-284797
Rule IDs
  • SV-284797r1240385_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 #2
Checks: C-89367r1240384_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device has the maximum number of consecutive failed authentication attempts set at 10 or fewer. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. _________________________ On the managed Google Android 17 device: COBO and COPE: 1. Lock the device screen. 2. Attempt to unlock the screen and validate that the device autowipes after the specified number of invalid entries. Note: Perform this verification only with a test phone set up with a production profile. If the EMM console device policy is not set for a maximum number of consecutive failed authentication attempts of 10 or fewer, or if on the managed Google Android 17 device the device policy is not set for a maximum number of consecutive failed authentication attempts of 10 or fewer, this is a finding.

Fix: F-89272r1240097_fix

Configure the Google Android 17 device to allow only 10 or fewer consecutive failed authentication attempts. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Set "Max password failures for local wipe" to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Set "Max password failures for local wipe" to a number between 1 and 10. Configuration API: setMaximumFailedPasswordsForWipe()

b
Google Android 17 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DoW-approved commercial app repository, MDM server, mobile application store].
CM-6 - Medium - CCI-000366 - V-284798 - SV-284798r1240658_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-005400
Vuln IDs
  • V-284798
Rule IDs
  • SV-284798r1240658_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 DoW data accessible by these unauthorized/malicious applications. SFR ID: FMT_SMF_EXT.1.1 #8
Checks: C-89368r1240657_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device has only approved application repositories (DoW-approved commercial app repository, EMM server, and/or mobile application store). This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow install unknown sources" is toggled to "ON". 3. Verify that "Disallow installs from unknown sources globally" is toggled to "ON". On the Google Android 17 device: COBO and COPE: 1. Open Settings >> Apps >> Special app access. 2. Open "Install unknown apps". 3. Ensure the list of apps is blank, or if an app is on the list, "Disabled by admin" is listed under the app name. If the EMM console device policy is not set to allow connections to only approved application repositories, or on the managed Google Android 17 device the device policy is not set to allow connections to only approved application repositories, this is a finding.

Fix: F-89273r1240100_fix

Configure the Google Android 17 device to disable unauthorized application repositories. On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow install unknown sources" to "ON". 3. Toggle "Disallow installs from unknown sources globally" to "ON". Configuration API: DISALLOW_INSTALL_UNKNOWN_SOURCES

b
Google Android 17 must be configured to enforce an application installation policy by specifying an application allow list that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version].
CM-7 - Medium - CCI-001764 - V-284799 - SV-284799r1240659_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001764
Version
GOOG-17-005500
Vuln IDs
  • V-284799
Rule IDs
  • SV-284799r1240659_rule
The application allow list, 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 allow list prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allow list. Failure to configure an application allow list properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoW data accessible by these applications. The application allow list, 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 #8
Checks: C-89369r1240388_chk

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

Fix: F-89274r1240389_fix

Configure the Google Android 17 device to use an application allow list. On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Select apps to be available (only approved apps). 3. Push updated policy to the device. Note: Managed Google Play is an allowed app store.

b
Google Android 17 allow list must be configured to not include applications with the following characteristics: - Backs up MD data to non-DoW cloud servers (including user and application access to cloud backup services); - Transmits MD diagnostic data to non-DoW servers; - Voice assistant application if available when MD is locked; - Voice dialing application if available when MD is locked; - Allows synchronization of data or applications between devices associated with user; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-3 validated) data sharing with other MDs or printers; - Backs up its own data to a remote system; and - Renders TV shows and movies.
IA-7 - Medium - CCI-000803 - V-284800 - SV-284800r1240660_rule
RMF Control
IA-7
Severity
M
CCI
CCI-000803
Version
GOOG-17-005600
Vuln IDs
  • V-284800
Rule IDs
  • SV-284800r1240660_rule
Requiring all authorized applications to be in an application allow list prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allow list. Failure to configure an application allow list properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoW data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DoW data or have features with no known application in the DoW environment. Application note: The application allow list, 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 #8
Checks: C-89370r1240391_chk

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

Fix: F-89275r1240392_fix

Configure the Google Android 17 device to use an application allow list. On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Select apps to be available (only approved apps). 3. Push updated policy to the device. Note: Managed Google Play is an allowed app store.

b
Google Android 17 allow list must be configured to not include artificial intelligence (AI) applications that process device data in the cloud, including Google Gemini.
IA-7 - Medium - CCI-000803 - V-284801 - SV-284801r1240661_rule
RMF Control
IA-7
Severity
M
CCI
CCI-000803
Version
GOOG-17-005700
Vuln IDs
  • V-284801
Rule IDs
  • SV-284801r1240661_rule
Sensitive DoW data could be exposed when an AI app processes device data in the cloud. SFR ID: FMT_SMF_EXT.1.1 #8
Checks: C-89371r1240394_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device has an AI application that processes device data in the cloud, including Google Gemini. This validation procedure is performed only on the EMM administration console. On the EMM console: 1. Review the list of selected managed Google Play apps. 2. Verify no AI applications that process device data in the cloud, including Google Gemini, are listed. If the EMM console device policy includes AI applications that process device data in the cloud, including Google Gemini, this is a finding. Note: This restriction does not include Gemini Nano. Gemini Nano is a built-in capability of Android 17 and processes device data on the device. Refer to the STIG Supplemental document, Section 2, Artificial Intelligence Restrictions, for more information.

Fix: F-89276r1240109_fix

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

b
Google Android 17 must be configured to not display the following (work profile) notifications when the device is locked: [selection: - Email notifications - Calendar appointments - Contact associated with phone call notifications - Text message notifications - Other application-based notifications - All notifications].
AC-11 - Medium - CCI-000060 - V-284802 - SV-284802r1240662_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000060
Version
GOOG-17-005800
Vuln IDs
  • V-284802
Rule IDs
  • SV-284802r1240662_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 to not send notifications to the lock screen mitigates this risk. The requirement statement specifies the DoW-mandated configuration of this MDFPP element. The STIG author must select "all notifications" if there is no other means to administratively restrict applications from issuing notifications in the locked state where those notifications could include DoW sensitive information. SFR ID: FMT_SMF_EXT.1.1 #18
Checks: C-89372r1240396_chk

Review managed Google Android 17 device settings to determine if the Google Android 17 device displays (work profile) notifications on the lock screen. Notifications of incoming phone calls are acceptable even when the device is locked. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Disable unredacted notifications" is toggled to "ON". COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Verify that "Disable unredacted notifications" is toggled to "ON". ___________________________ On the managed Google Android 17 device: COBO: 1. Go to Settings >> Display & touch >> Lock screen. 2. Tap on "Privacy". 3. Verify that "Show sensitive content only when unlocked" is selected. COPE: 1. Go to Settings >> Display & touch >> Lock screen. 2. Tap on "When work profile is locked". 3. Verify that "Hide sensitive work content" is selected. If the EMM console device policy allows work notifications on the lock screen, or the managed Google Android 17 device allows work notifications on the lock screen, this is a finding.

Fix: F-89277r1240112_fix

Configure the Google Android 17 device to not display (work profile) notifications when the device is locked. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Toggle "Disable unredacted notifications". COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Toggle "Disable unredacted notifications". Configuration API: KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS

b
Google Android 17 must be configured to disable trust agents.
IA-2 - Medium - CCI-000765 - V-284806 - SV-284806r1240664_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000765
Version
GOOG-17-006200
Vuln IDs
  • V-284806
Rule IDs
  • SV-284806r1240664_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 DoW sensitive data if compromised. By not permitting the use of nonpassword authentication mechanisms, users are forced to use passcodes that meet DoW passcode requirements. SFR ID: FMT_SMF_EXT.1.1 #22, FIA_UAU.5.1
Checks: C-89376r1240399_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 17 device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Disable trust agents" is toggled to "ON". COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Disable trust agents" is toggled to "ON". 4. Select "Work Profile". 5. Verify that "Disable trust agents" is toggled to "ON". ____________________________ On the managed Google Android 17 device: COBO and COPE: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the EMM console "disable trust agents" is not selected, or on the managed Google Android 17 device a trust agent can be enabled, this is a finding.

Fix: F-89281r1240124_fix

Configure the Google Android 17 device to disable trust agents. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Toggle "Disable trust agents" to "ON". COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Toggle "Disable trust agents" to "ON". 4. Select "Work Profile". 5. Toggle "Disable trust agents" to "ON". Configuration API: KEYGUARD_DISABLE_TRUST_AGENTS

b
Google Android 17 must be configured to disable developer modes.
CM-7 - Medium - CCI-000381 - V-284808 - SV-284808r1240666_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
GOOG-17-006400
Vuln IDs
  • V-284808
Rule IDs
  • SV-284808r1240666_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 DoW sensitive information. Disabling developer modes mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #26
Checks: C-89378r1240401_chk

Review managed Google Android 17 device configuration settings to determine whether a developer mode is enabled. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to "ON". 3. Open "Set user restrictions on parent". 4. Verify that "Disallow debugging features" is toggled to "ON". ____________________________ On the managed Google Android 17 device: COBO and COPE: 1. Go to Settings >> System. 2. Ensure "Developer Options" is not listed. 3. Go to Settings >> About Phone. 4. Tap on the Build Number to try to enable Developer Options and validate that action is blocked. If the EMM console device policy is not set to disable developer mode, or on the managed Google Android 17 device the device policy is not set to disable developer mode, this is a finding.

Fix: F-89283r1240130_fix

Configure the Google Android 17 device to disable developer modes. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to "ON". 3. Open "Set user restrictions on parent". 4. Toggle "Disallow debugging features" to "ON". Configuration API: DISALLOW_DEBUGGING_FEATURES

b
Google Android 17 must be configured to enable audit logging.
AU-6 - Medium - CCI-000154 - V-284810 - SV-284810r1240404_rule
RMF Control
AU-6
Severity
M
CCI
CCI-000154
Version
GOOG-17-006600
Vuln IDs
  • V-284810
Rule IDs
  • SV-284810r1240404_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_EXT1.1 #32
Checks: C-89380r1240403_chk

Inspect the configuration on the managed Google Android 17 device to enable audit logging. This validation procedure is performed only on the EMM administration console. On the EMM console: COBO and COPE: 1. Open the "Device owner management" section. 2. Verify that "Enable security logging" is toggled to "ON". If the EMM console device policy is not set to enable audit logging, this is a finding.

Fix: F-89285r1240136_fix

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

a
Google Android 17 must be configured to display the DoW advisory warning message at startup or each time the user unlocks the device.
AC-8 - Low - CCI-000048 - V-284812 - SV-284812r1240671_rule
RMF Control
AC-8
Severity
L
CCI
CCI-000048
Version
GOOG-17-006800
Vuln IDs
  • V-284812
Rule IDs
  • SV-284812r1240671_rule
Before granting access to the system, Google Android 17 is required to display the DoW-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 DoW 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 DoW 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-89382r1240669_chk

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

Fix: F-89287r1240670_fix

Configure the DoW warning banner by either of the following methods (required text is found in the Discussion): 1. By placing the DoW warning banner text in the user agreement signed by each Google Android 17 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each Google Android 17 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 17 must be configured to generate audit records for the following auditable events: Detected integrity violations.
AU-12 - Medium - CCI-000169 - V-284813 - SV-284813r1240408_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
GOOG-17-006900
Vuln IDs
  • V-284813
Rule IDs
  • SV-284813r1240408_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. Application note: Requirement applies only to integrity violation detections that can be logged by the audit logging component. SFR ID: FMT_SMF_EXT.1.1 #37, FAU_GEN.1.1 (FPT_TST_EXT.2/PREKERNAL)
Checks: C-89383r1240407_chk

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

Fix: F-89288r1240145_fix

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

b
Google Android 17 must be configured to disable USB mass storage mode.
SC-41 - Medium - CCI-002546 - V-284814 - SV-284814r1240673_rule
RMF Control
SC-41
Severity
M
CCI
CCI-002546
Version
GOOG-17-007000
Vuln IDs
  • V-284814
Rule IDs
  • SV-284814r1240673_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-89384r1240672_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device has a USB mass storage mode and whether it has been disabled. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow USB file transfer" is toggled to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Verify that "Disallow USB file transfer" is toggled to "ON". ______________________________ On the managed Google Android 17 device: 1. Plug a USB cable into the managed Google Android 17 device and connect to a non-DoW network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify that "No data transfer" is selected. If the EMM console device policy is not set to disable USB mass storage mode, or on the managed Google Android 17 device the device policy is not set to disable USB mass storage mode, this is a finding.

Fix: F-89289r1240148_fix

Configure the Google Android 17 device to disable USB mass storage mode. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow USB file transfer" to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Toggle "Disallow USB file transfer" to "ON". Configuration API: DISALLOW_MOUNT_PHYSICAL_MEDIA, DISALLOW_USB_FILE_TRANSFER

b
Google Android 17 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.
SC-4 - Medium - CCI-001090 - V-284815 - SV-284815r1240675_rule
RMF Control
SC-4
Severity
M
CCI
CCI-001090
Version
GOOG-17-007100
Vuln IDs
  • V-284815
Rule IDs
  • SV-284815r1240675_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-89385r1240674_chk

Review managed Google Android 17 device configuration settings to determine if the mobile device has a USB mass storage mode and whether it has been disabled. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow USB file transfer" is toggled to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Verify that "Disallow USB file transfer" is toggled to "ON". ______________________________ On the managed Google Android 17 device: 1. Plug a USB cable into the managed Google Android 17 device and connect to a non-DoW network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify that "No data transfer" is selected. If the EMM console device policy is not set to disable USB mass storage mode, or on the managed Google Android 17 device the device policy is not set to disable USB mass storage mode, this is a finding.

Fix: F-89290r1240151_fix

Configure the Google Android 17 device to disable USB mass storage mode. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow USB file transfer" to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Toggle "Disallow USB file transfer" to "ON". Configuration API: DISALLOW_MOUNT_PHYSICAL_MEDIA, DISALLOW_USB_FILE_TRANSFER

b
Google Android 17 must be configured to not allow backup of [all applications, configuration data] to remote systems.
SC-4 - Medium - CCI-001090 - V-284816 - SV-284816r1240676_rule
RMF Control
SC-4
Severity
M
CCI
CCI-001090
Version
GOOG-17-007200
Vuln IDs
  • V-284816
Rule IDs
  • SV-284816r1240676_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, DoW devices may synchronize DoW 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-89386r1240413_chk

Review managed Google Android 17 device configuration settings to determine if the capability to back up to a remote system has been disabled. Note: Because personal accounts cannot be added to the work profile (GOOG-17-008300), this control impacts only personal profile accounts. Sites can allow backup based on local policy. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify that "Enable backup service" is toggled to "OFF". On the managed Google Android 17 device: COBO: 1. Go to Settings >> Accounts & backup. 2. Verify that Backup settings is "Not available". COPE: 1. Go to Settings >> Accounts & backup. 2. Select "Work". 3. Verify that Backup settings is "Not available". If the EMM console device policy is not set to disable the capability to back up to a remote system, or on the managed Google Android 17 device the device policy is not set to disable the capability to back up to a remote system, this is a finding.

Fix: F-89291r1240154_fix

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

b
Google Android 17 must be configured to enable authentication of personal hotspot connections to the device using a preshared key.
AC-18 - Medium - CCI-001443 - V-284817 - SV-284817r1240158_rule
RMF Control
AC-18
Severity
M
CCI
CCI-001443
Version
GOOG-17-007300
Vuln IDs
  • V-284817
Rule IDs
  • SV-284817r1240158_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_EXT.1.1 #41
Checks: C-89387r1240156_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 "WPA3-Personal". 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. To the left of the slide, tap on "Wi-Fi Hotspot" to bring up the configuration options. 4. Click on the "Security" link and verify that "WPA3-Personal" is selected. If the Wi-Fi hotspot security is not set to "WPA3-Personal", this is a finding.

Fix: F-89292r1240157_fix

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

b
Google Android 17 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-284819 - SV-284819r1240677_rule
RMF Control
SC-39
Severity
M
CCI
CCI-002530
Version
GOOG-17-007500
Vuln IDs
  • V-284819
Rule IDs
  • SV-284819r1240677_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 DoW 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_EXT.1.1 #42, FDP_ACF_EXT.1.2
Checks: C-89389r1240416_chk

Review documentation on the managed Google Android 17 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-89294r1240163_fix

Configure the Google Android 17 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 17 must be configured to disable multiuser modes.
AC-2 - Medium - CCI-002110 - V-284820 - SV-284820r1240678_rule
RMF Control
AC-2
Severity
M
CCI
CCI-002110
Version
GOOG-17-007600
Vuln IDs
  • V-284820
Rule IDs
  • SV-284820r1240678_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 DoW 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 DoW multiuser account security policies. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-89390r1240418_chk

Review documentation on the managed Google Android 17 device and inspect the configuration on the Google Android device to disable multiuser modes. This validation procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow modify accounts" is toggled to "ON". On the managed Google Android 17 device: COBO and COPE: 1. Go to Settings >> Accounts and backup. 2. Tap "Add account" (work profile). 3. Verify that the action is not allowed. If the EMM console device policy is not set to disable multiuser modes, or on the managed Google Android 17 device the device policy is not set to disable multiuser modes, this is a finding.

Fix: F-89295r1240166_fix

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

a
Google Android 17 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-284824 - SV-284824r1240680_rule
RMF Control
CM-7
Severity
L
CCI
CCI-000381
Version
GOOG-17-008000
Vuln IDs
  • V-284824
Rule IDs
  • SV-284824r1240680_rule
Some Bluetooth profiles provide the capability for remote transfer of sensitive DoW data without encryption or otherwise do not meet DoW IT security policies and therefore must be disabled. SFR ID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8
Checks: C-89394r1240177_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 17 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 17 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-89299r1240178_fix

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

b
Google Android 17 must be configured to disable ad hoc wireless client-to-client connection capability.
SC-40 - Medium - CCI-002536 - V-284825 - SV-284825r1240681_rule
RMF Control
SC-40
Severity
M
CCI
CCI-002536
Version
GOOG-17-008100
Vuln IDs
  • V-284825
Rule IDs
  • SV-284825r1240681_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 DoW data and increase the risk of downloading and installing malware of the DoW mobile device. SFR ID: FMT_SMF_EXT.1.1 WL-5/PP-Module for WLAN Clients
Checks: C-89395r1240180_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-89300r1240181_fix

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

b
Google Android 17 users must complete required training.
CM-6 - Medium - CCI-000366 - V-284827 - SV-284827r1243757_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008300
Vuln IDs
  • V-284827
Rule IDs
  • SV-284827r1243757_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 DoW sensitive data may become compromised. SFR ID: NA
Checks: C-89397r1240186_chk

Review a sample of site User Agreements for Google Android 17 device users or similar training records and training course content. Verify the Google Android 17 device users have completed the required training. The intent is that required training is renewed on a periodic basis in a time period determined by the AO. If any Google Android 17 device user has not completed the required training, this is a finding.

Fix: F-89302r1243756_fix

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

b
Google Android 17 must be configured to disable Wi-Fi sharing.
CM-6 - Medium - CCI-000366 - V-284828 - SV-284828r1240424_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008400
Vuln IDs
  • V-284828
Rule IDs
  • SV-284828r1240424_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-89398r1240422_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-89303r1240423_fix

Configure the Google Android 17 device to disable Wi-Fi sharing. Mobile hotspot must be enabled to enable Wi-Fi sharing. If the AO has not approved mobile hotspot, and it has been disabled on the EMM console, no further action is needed. If mobile hotspot is being used, use the following procedure to disable Wi-Fi sharing: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". Configuration API: DISALLOW_SHARING_ADMIN_CONFIGURED_WIFI

b
Google Android 17 must be configured to enforce a password for Wi-Fi and Bluetooth hotspot if approved for use by the authorizing official (AO). If not approved for use, Wi-Fi and Bluetooth hotspot must be disabled.
CM-6 - Medium - CCI-000366 - V-284829 - SV-284829r1240686_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008500
Vuln IDs
  • V-284829
Rule IDs
  • SV-284829r1240686_rule
Wi-Fi and Bluetooth hotspot use may increase the risk for exposing sensitive DoW data for some use cases; therefore, it should be disabled unless approved by the AO. When a DoW mobile phone is used as a Wi-Fi or Bluetooth hotspot, a hotspot password must be enabled; otherwise, unauthorized devices could connect to the DoW hotspot, which may increase the risk of exposure of sensitive DoW data and/or a performance degradation of the DoW mobile phone. SFR ID: FMT_SMF_EXT.1.1 / WLAN #3
Checks: C-89399r1240192_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 17 device: COBO and COPE: 1. Go to Settings >> Network & Internet. 2. Verify that "Hotspot & tethering" is "Controlled by admin". 3. Verify that tapping "Hotspot & tethering" provides a prompt to the user specifying "Action not allowed". If on the managed Google Android 17 device "Hotspot & tethering" is enabled, this is a finding. If hotspot use has been approved, verify that the user has been trained to use the default hotspot password. Refer to GOOG-17-009800 for the procedure. If users are not trained to use the default hotspot password, this is a finding.

Fix: F-89304r1240685_fix

Disable hotspot functions on the DoW phone if not approved by the AO. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config tethering" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON". If the AO has approved the use of Wi-Fi and Bluetooth hotspots, train the user to not change the default hotspot password (refer to GOOG-17-009800). By default, when Wi-Fi Hotspot is enabled, a 15-character complex password is automatically configured for the hotspot. Configuration API: DISALLOW_CONFIG_TETHERING

b
Google Android 17 must have the DoW root and intermediate PKI certificates installed.
CM-6 - Medium - CCI-000366 - V-284830 - SV-284830r1240689_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008600
Vuln IDs
  • V-284830
Rule IDs
  • SV-284830r1240689_rule
DoW 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 DoW root and intermediate PKI certificates greatly diminishes the risk of this attack. SFR ID: FMT_SMF.1.1 #11
Checks: C-89400r1240687_chk

Review device configuration settings to confirm that the DoW root and intermediate PKI certificates are installed. This procedure is performed on both the EMM administration console and the managed Google Android 17 device. The current DoW root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet). On the EMM console, verify that the DoW root and intermediate certificates are part of a device and/or work profile that is being pushed down to the devices. On the managed Google Android 17 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that DoW root and intermediate PKI certificates are listed under the "User" tab in the "Work" section. If on the EMM console the DoW root and intermediate certificates are not listed in a profile, or the managed Android 17 device does not list the DoW root and intermediate certificates under the user tab, this is a finding.

Fix: F-89305r1240688_fix

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

b
The Google Android 17 work profile must be configured to prevent users from adding personal email accounts to the work email app.
CM-6 - Medium - CCI-000366 - V-284831 - SV-284831r1240690_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008700
Vuln IDs
  • V-284831
Rule IDs
  • SV-284831r1240690_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 DoW 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-89401r1240519_chk

Review the managed Google Android 17 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 17 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 17 device: 1. Open Settings. 2. Tap "Accounts and backup". 3. Select "Work">>"Manage accounts". 4. Tap "Add account". 5. Verify "Add account" is grayed out and cannot be selected. If on the EMM console the restriction to "Disallow modify accounts" is not set, or on the managed Android 17 device the user is able to add an account in the "Work" section, this is a finding.

Fix: F-89306r1240199_fix

Configure the Google Android 17 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 17 work profile must be configured to enforce the system application disable list.
CM-6 - Medium - CCI-000366 - V-284832 - SV-284832r1240691_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008800
Vuln IDs
  • V-284832
Rule IDs
  • SV-284832r1240691_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 17 by Google. Preinstalled application: Additional noncore applications included in the Google Android 17 build by Google or the wireless carrier. Some system applications can compromise DoW data or upload users' information to non-DoW-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DoW data or DoW user information. The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DoW use by configuring the system application disable list. SFR ID: FMT_SMF.1.1 #47
Checks: C-89402r1240429_chk

Review the managed Google Android 17 work profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. Verify that only approved system apps have been placed on the core allow list. This procedure is performed on the EMM administration console. Review the system app 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 allow list contains unapproved core apps, this is a finding.

Fix: F-89307r1240430_fix

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

b
Google Android 17 must be provisioned as a fully managed device and configured to create a work profile.
CM-6 - Medium - CCI-000366 - V-284833 - SV-284833r1240433_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-008900
Vuln IDs
  • V-284833
Rule IDs
  • SV-284833r1240433_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-89403r1240432_chk

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

Fix: F-89308r1240205_fix

Configure the Google Android 17 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 17 work profile must be configured to disable automatic completion of workspace internet browser text input.
CM-6 - Medium - CCI-000366 - V-284834 - SV-284834r1240436_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-009000
Vuln IDs
  • V-284834
Rule IDs
  • SV-284834r1240436_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 17 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-89404r1240434_chk

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

Fix: F-89309r1240435_fix

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

b
The Google Android 17 work profile must be configured to disable the autofill services.
CM-6 - Medium - CCI-000366 - V-284835 - SV-284835r1240438_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-009100
Vuln IDs
  • V-284835
Rule IDs
  • SV-284835r1240438_rule
The autofill services allow the user to complete text inputs that could contain sensitive information, such as personally identifiable information, without previous knowledge of the information. By allowing the use of autofill services, an adversary who learns a user's Android 17 device password, or who otherwise is able to unlock the device, may be able to breach other systems by relying on the autofill services to provide information unknown to the adversary. By disabling the autofill services, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated. Examples of apps that offer autofill services include Samsung Pass, Google, Dashlane, LastPass, and 1Password. SFR ID: FMT_SMF.1.1 #47
Checks: C-89405r1240437_chk

Review the Google Android 17 work profile configuration settings to confirm that autofill services are disabled. This procedure is performed only on the EMM administration console. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow autofill" is toggled to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow autofill" is toggled to "ON". If on the EMM console "disallow autofill" is not selected, this is a finding.

Fix: F-89310r1240211_fix

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

b
Google Android 17 must be configured to disallow configuration of date and time.
CM-6 - Medium - CCI-000366 - V-284836 - SV-284836r1240692_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-009200
Vuln IDs
  • V-284836
Rule IDs
  • SV-284836r1240692_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 17 are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoW network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier. Time stamps generated by the audit system in Google Android 17 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.1.1 #47
Checks: C-89406r1240439_chk

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

Fix: F-89311r1240214_fix

Configure the Google Android 17 device to set auto network time. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config date time" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config date time" to "ON". Configuration API: SetAutoTimeRequired – on Parent DISALLOW_CONFIG_DATE_TIME – on User

c
Android 17 devices must have the latest available Google Android 17 operating system installed.
CM-6 - High - CCI-000366 - V-284838 - SV-284838r1240509_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000366
Version
GOOG-17-009400
Vuln IDs
  • V-284838
Rule IDs
  • SV-284838r1240509_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-89408r1240508_chk

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

Install the latest released version of the Google Android 17 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 17 devices must be configured to disable the use of third-party keyboards.
CM-6 - Low - CCI-000366 - V-284839 - SV-284839r1240444_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
GOOG-17-009500
Vuln IDs
  • V-284839
Rule IDs
  • SV-284839r1240444_rule
Many third-party keyboard applications are known to contain malware. SFR ID: FMT_SMF.1.1 #47
Checks: C-89409r1240443_chk

Review the managed Google Android 17 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-89314r1240223_fix

Configure the Google Android 17 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 17 devices must be configured to enable Common Criteria (CC) mode.
CM-6 - Low - CCI-000366 - V-284840 - SV-284840r1240447_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
GOOG-17-009600
Vuln IDs
  • V-284840
Rule IDs
  • SV-284840r1240447_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-89410r1240445_chk

Review the managed Google Android 17 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-89315r1240446_fix

Configure the Google Android 17 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 17 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-284841 - SV-284841r1240693_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002235
Version
GOOG-17-009700
Vuln IDs
  • V-284841
Rule IDs
  • SV-284841r1240693_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 DoW information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DoW sensitive information. SFR ID: FMT_MOF_EXT.1.2 #24
Checks: C-89411r1240228_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-89316r1240229_fix

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

b
Google Android 17 must allow only the administrator (EMM) to install/remove DoW root and intermediate PKI certificates.
CM-6 - Medium - CCI-000370 - V-284842 - SV-284842r1240696_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000370
Version
GOOG-17-009800
Vuln IDs
  • V-284842
Rule IDs
  • SV-284842r1240696_rule
DoW 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 DoW root and intermediate PKI certificates to the administrator mitigates this risk. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89412r1240694_chk

Review the device configuration to confirm that the user is unable to remove DoW root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Verify that "Disallow config credentials" is toggled to "ON". On the Google Android 17 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify that the user is unable to untrust or remove any work certificates. If on the Google Android 17 device the user is able to remove certificates, this is a finding.

Fix: F-89317r1240695_fix

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

a
Google Android 17 must allow only the administrator (MDM) to perform the following management function: Disable Phone Hub.
SC-4 - Low - CCI-001090 - V-284843 - SV-284843r1240698_rule
RMF Control
SC-4
Severity
L
CCI
CCI-001090
Version
GOOG-17-009900
Vuln IDs
  • V-284843
Rule IDs
  • SV-284843r1240698_rule
It may be possible to transfer work profile data on a DoW 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 DoW data. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89413r1240697_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 DoW Android device.

Fix: F-89318r1240235_fix

Configure the Google Android 17 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 17 must be configured to disable Private Space use.
CM-6 - High - CCI-000370 - V-284844 - SV-284844r1240699_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000370
Version
GOOG-17-010000
Vuln IDs
  • V-284844
Rule IDs
  • SV-284844r1240699_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 allow list or block list cannot control the installation of apps into Private Space. Malware and other unauthorized apps could be installed on a DoW mobile device, which could lead to the compromise of DoW sensitive information or to an attack on the DoW network. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89414r1240450_chk

Review the Google Android 17 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-89319r1240451_fix

Configure the Google Android 17 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 17 must disable the user's ability to wipe the device.
CM-6 - Medium - CCI-000366 - V-284845 - SV-284845r1240700_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-010200
Vuln IDs
  • V-284845
Rule IDs
  • SV-284845r1240700_rule
This feature must be disabled to comply with DoW electronic records retention requirements for mobile devices. Otherwise, mobile device users could wipe the device, which would violate DoW policy. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89415r1240240_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-89320r1240241_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 17 must disable wireless printing.
CM-6 - Low - CCI-000366 - V-284847 - SV-284847r1240701_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
GOOG-17-010400
Vuln IDs
  • V-284847
Rule IDs
  • SV-284847r1240701_rule
Wireless printing allows the printing of sensitive DoW documents to non-DoW controlled printers, which may lead to the exposure of sensitive DoW information. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89417r1240456_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 17 device. On the MDM console: COBO and COPE: 1. Open User Restrictions. 2. Verify that "Disallow printing" is enabled. On the managed Google Android 17 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-89322r1240457_fix

Configure Google Android 17 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 17 must disable screen capture.
CM-6 - Low - CCI-000366 - V-284848 - SV-284848r1240702_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
GOOG-17-010500
Vuln IDs
  • V-284848
Rule IDs
  • SV-284848r1240702_rule
The screen capture feature could lead to the exposure of sensitive DoW information. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89418r1240249_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 17 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 17 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-89323r1240250_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 17 devices must have a Mobile Threat Detection (MTD) app installed.
CM-6 - Medium - CCI-000366 - V-284849 - SV-284849r1240703_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-010600
Vuln IDs
  • V-284849
Rule IDs
  • SV-284849r1240703_rule
DoW 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-89419r1240252_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" >> "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-89324r1240253_fix

Install an MTD app on managed Google Android devices.

b
Google Android 17 must implement the management setting: Disable Camera.
CM-6 - Medium - CCI-000366 - V-284850 - SV-284850r1240704_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-010700
Vuln IDs
  • V-284850
Rule IDs
  • SV-284850r1240704_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 DoW information in some operational environments. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-89420r1240255_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 the configuration settings to confirm "Allow Camera" is disabled. If approved, this requirement is not applicable. Review the configuration settings to confirm the device camera has been disabled. This check procedure is performed on the device management tool and the Google Android 17 device. On the MDM console: COBO and COPE: 1. Open Camera. 2. Verify that the "Disable camera" setting is disabled. On the managed Google Android 17 device: COBO and COPE: Verify that the camera cannot be used on the mobile device. If the device camera has not been disabled, this is a finding.

Fix: F-89325r1240256_fix

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

b
The Google Android device must be configured to disable Wi-Fi Aware for work profile apps.
CM-6 - Medium - CCI-000366 - V-284851 - SV-284851r1240705_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-010800
Vuln IDs
  • V-284851
Rule IDs
  • SV-284851r1240705_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 DoW information could be transferred from a DoW mobile device to a non-DoW device or from work profile apps on a DoW device to personal profile apps on a non-DoW device. SFR ID: FMT_SMF.1.1 #47
Checks: C-89421r1240258_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-89326r1240259_fix

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

b
The Google Android device must be configured to disable Cross-Device Handoff (also called "Continuity On").
CM-6 - Medium - CCI-000366 - V-284852 - SV-284852r1240706_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-010900
Vuln IDs
  • V-284852
Rule IDs
  • SV-284852r1240706_rule
Cross-Device Handoff (also called "Continuity On") permits a user of an Android phone to transition user activities from one device to another. Handoff passes sufficient information between the devices to describe the activity, but app data synchronization associated with the activity is handled though the cloud, which should be disabled on a compliant Android devices. If a user associates both DoW and personal devices to the same Google account, the user may improperly reveal information about the nature of the user's activities on an unprotected device. Disabling Cross-Device Handoff mitigates this risk. SFR ID: FMT_SMF.1.1 #47
Checks: C-89422r1240528_chk

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

Fix: F-89327r1240529_fix

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

b
The Google Android 17 device must be configured to disable web-based artificial intelligence (AI) interactions.
CM-6 - Medium - CCI-000366 - V-285857 - SV-285857r1244384_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
GOOG-17-011000
Vuln IDs
  • V-285857
Rule IDs
  • SV-285857r1244384_rule
Sensitive DoW data could be exposed when an AI app processes device data in the cloud. SFR ID: FMT_SMF.1.1 #47
Checks: C-90538r1240713_chk

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

Fix: F-90443r1244278_fix

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