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

Zebra Technologies Android 14 COPE Security Technical Implementation Guide

V1R2 · · · Released 13 May 2026 · 42 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 Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Supporting documents DISA companion ZIP · 2.5 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_Zebra_Android_14_Y26M05_STIG.zip
Digest of Updates vs. V1R1 · 26 Jan 2026 −1

Comparison against the immediately-prior release (V1R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Removed rules 1

  • V-283666 Medium Zebra Android must implement the management setting: disable the Bluetooth radio.
Sort by
b
Zebra Android 14 must be configured to enable audit logging.
AU-6 - Medium - CCI-000154 - V-283584 - SV-283584r1190163_rule
RMF Control
AU-6
Severity
M
CCI
CCI-000154
Version
ZEBR-14-002800
Vuln IDs
  • V-283584
Rule IDs
  • SV-283584r1190163_rule
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. To be useful, administrators must have the ability to view the audit logs. SFR ID: FMT_SMF_EXT.1.1 #32
Checks: C-88149r1190161_chk

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

Fix: F-88054r1190162_fix

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

b
Zebra Android 14 must be configured to enforce a minimum password length of six characters.
Medium - CCI-004066 - V-283609 - SV-283609r1190238_rule
RMF Control
Severity
M
CCI
CCI-004066
Version
ZEBR-14-006000
Vuln IDs
  • V-283609
Rule IDs
  • SV-283609r1190238_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, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting in device and data compromise. SFR ID: FMT_SMF_EXT.1.1 #1a
Checks: C-88174r1190236_chk

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

Fix: F-88079r1190237_fix

Configure the Zebra Android 14 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 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 the number of characters as "6".

b
Zebra Android 14 must be configured to not allow passwords that include more than four repeating or sequential characters.
Medium - CCI-004066 - V-283610 - SV-283610r1190241_rule
RMF Control
Severity
M
CCI
CCI-004066
Version
ZEBR-14-006100
Vuln IDs
  • V-283610
Rule IDs
  • SV-283610r1190241_rule
Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk. SFR ID: FMT_SMF_EXT.1.1 #1b
Checks: C-88175r1190239_chk

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

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

b
Zebra Android 14 must be configured to lock the display after 15 minutes (or less) of inactivity.
AC-11 - Medium - CCI-000057 - V-283611 - SV-283611r1190244_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000057
Version
ZEBR-14-006300
Vuln IDs
  • V-283611
Rule IDs
  • SV-283611r1190244_rule
The screen lock timeout must be set to a value that helps protect the device from unauthorized access. Having a too-long timeout would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device. SFR ID: FMT_SMF_EXT.1.1 #2b
Checks: C-88176r1190242_chk

Review managed Zebra 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: Zebra Android 14 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 both the EMM Administration Console and the Android 14 device. 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-88081r1190243_fix

Configure the Zebra Android 14 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: Zebra Android 14 Settings User Interface (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.

b
Zebra Android 14 must be configured to not allow more than 10 consecutive failed authentication attempts.
AC-7 - Medium - CCI-000044 - V-283612 - SV-283612r1190247_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
ZEBR-14-006400
Vuln IDs
  • V-283612
Rule IDs
  • SV-283612r1190247_rule
The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or fewer gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password. SFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5
Checks: C-88177r1190245_chk

Review managed Zebra Android 14 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 Zebra Android 14 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 Zebra Android 14 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 to the maximum number of consecutive failed authentication attempts at 10 or fewer, or if on the managed Zebra Android 14 device the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.

Fix: F-88082r1190246_fix

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

b
Zebra Android 14 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DOD-approved commercial app repository, MDM server, mobile application store].
CM-6 - Medium - CCI-000366 - V-283613 - SV-283613r1190250_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-006500
Vuln IDs
  • V-283613
Rule IDs
  • SV-283613r1190250_rule
Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DOD data accessible by these unauthorized/malicious applications. SFR ID: FMT_SMF_EXT.1.1 #8a
Checks: C-88178r1190248_chk

Review managed Zebra Android 14 device configuration settings to determine if the mobile device has only approved application repositories (DOD-approved commercial app repository, EMM server, and/or mobile application store). This validation procedure is performed on both the EMM Administration Console and the managed Zebra Android 14 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 Zebra Android 14 device: COBO and COPE: 1. Open Settings >> Apps >> Special app access. 2. Open Install unknown apps. 3. Verify 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 Zebra Android 14 device, the device policy is not set to allow connections to only approved application repositories, this is a finding.

Fix: F-88083r1190249_fix

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

b
Zebra Android 14 must be configured to enforce an application installation policy by specifying an application allowlist that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version].
CM-7 - Medium - CCI-001764 - V-283614 - SV-283614r1190253_rule
RMF Control
CM-7
Severity
M
CCI
CCI-001764
Version
ZEBR-14-006600
Vuln IDs
  • V-283614
Rule IDs
  • SV-283614r1190253_rule
The application allowlist, in addition to controlling the installation of applications on the mobile device (MD), must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. Core application: Any application integrated into the operating system (OS) by the OS or MD vendors. Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier. Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications. The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core applications (included in the OS by the OS vendor) and preinstalled applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. SFR ID: FMT_SMF_EXT.1.1 #8b
Checks: C-88179r1190251_chk

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

Fix: F-88084r1190252_fix

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

b
Zebra Android 14 allowlist must be configured to not include applications with the following characteristics: - Backs up mobile device (MD) data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits MD diagnostic data to non-DOD servers; - Voice assistant application if available when MD is locked; - Voice dialing application if available when MD is locked; - Allows synchronization of data or applications between devices associated with user; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs or printers; - Backs up own data to a remote system; - Renders TV shows and movies.
CM-6 - Medium - CCI-000366 - V-283615 - SV-283615r1190256_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-006700
Vuln IDs
  • V-283615
Rule IDs
  • SV-283615r1190256_rule
Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DOD data or have features with no known application in the DOD environment. Application note: The application allowlist, in addition to controlling the installation of applications on the mobile device (MD), must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. Core application: Any application integrated into the operating system (OS) by the OS or MD vendors. Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier. SFR ID: FMT_SMF_EXT.1.1 #8b
Checks: C-88180r1190254_chk

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

Fix: F-88085r1190255_fix

Configure the Zebra Android 14 device application allowlist to exclude applications with the following characteristics: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits MD diagnostic data to non-DOD servers; - Voice assistant application (if available) when MD is locked; - Voice dialing application (if available) when MD is locked; - Allows synchronization of data or applications between devices associated with user; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs, display screens (screen mirroring), or printers; - Backs up own data to a remote system; - Renders TV shows and movies. On the EMM console: 1. Go to the Android app catalog for managed Google Play. 2. Before selecting an app, review the app details and privacy policy to ensure the app does not include prohibited characteristics. Managed Google Play is always an allowlisted App Store.

b
Zebra Android 14 must be configured to not display the following (work profile) notifications when the device is locked: [selection: a. email notifications b. calendar appointments c. contact associated with phone call notification d. text message notification e. other application-based notifications f. all notifications].
AC-11 - Medium - CCI-000060 - V-283616 - SV-283616r1190259_rule
RMF Control
AC-11
Severity
M
CCI
CCI-000060
Version
ZEBR-14-006800
Vuln IDs
  • V-283616
Rule IDs
  • SV-283616r1190259_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. SFR ID: FMT_SMF_EXT.1.1 #18
Checks: C-88181r1190257_chk

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

Fix: F-88086r1190258_fix

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

b
Zebra Android 14 must be configured to disable trust agents.
IA-2 - Medium - CCI-000765 - V-283620 - SV-283620r1190271_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000765
Version
ZEBR-14-007200
Vuln IDs
  • V-283620
Rule IDs
  • SV-283620r1190271_rule
Trust agents allow a user to unlock a mobile device without entering a passcode when the mobile device is, for example, connected to a user-selected Bluetooth device or in a user-selected location. This technology would allow unauthorized users to have access to DOD sensitive data if compromised. By not permitting the use of nonpassword authentication mechanisms, users are forced to use passcodes that meet DOD passcode requirements. SFR ID: FMT_SMF_EXT.1.1 #22, FIA_UAU.5.1
Checks: C-88185r1190269_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 Zebra Android 14 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 Zebra Android 14 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 Zebra Android 14 device a trust agent can be enabled, this is a finding.

Fix: F-88090r1190270_fix

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

b
Zebra Android 14 must be configured to disable developer modes.
CM-7 - Medium - CCI-000381 - V-283622 - SV-283622r1190277_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
ZEBR-14-007400
Vuln IDs
  • V-283622
Rule IDs
  • SV-283622r1190277_rule
Developer modes expose features of the mobile operating system that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DOD sensitive information. Disabling developer modes mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #26
Checks: C-88187r1190275_chk

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

Fix: F-88092r1190276_fix

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

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

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

Fix: F-88095r1190285_fix

Configure the DOD warning banner by either of the following methods (required text is found in the Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each Zebra Android 14 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each Zebra Android 14 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.

b
Zebra Android 14 must be configured to generate audit records for the following auditable events: Detected integrity violations.
AU-12 - Medium - CCI-000169 - V-283626 - SV-283626r1190289_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
ZEBR-14-007800
Vuln IDs
  • V-283626
Rule IDs
  • SV-283626r1190289_rule
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Rule Title lists key events for which the system must generate an audit record. Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component. SFR ID: FMT_SMF_EXT.1.1 #37
Checks: C-88191r1190287_chk

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

Fix: F-88096r1190288_fix

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

b
Zebra Android 14 must be configured to disable USB mass storage mode.
SC-41 - Medium - CCI-002546 - V-283630 - SV-283630r1190301_rule
RMF Control
SC-41
Severity
M
CCI
CCI-002546
Version
ZEBR-14-008400
Vuln IDs
  • V-283630
Rule IDs
  • SV-283630r1190301_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-88195r1190299_chk

Review managed Zebra Android 14 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 Zebra Android 14 device. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow USB file transfer" is toggled to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Verify "Disallow USB file transfer" is toggled to "ON". ______________________________ On the managed Zebra Android 14 device: 1. Plug a USB cable into the managed Zebra Android 14 device and connect to a non-DOD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify "No data transfer" is selected. If the EMM console device policy is not set to disable USB mass storage mode or on the managed Zebra Android 14 device, the device policy is not set to disable USB mass storage mode, this is a finding.

Fix: F-88100r1190300_fix

Configure the Zebra Android 14 device to disable USB mass storage mode. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow USB file transfer" to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Toggle "Disallow USB file transfer" to "ON".

b
Zebra Android 14 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.
SC-4 - Medium - CCI-001090 - V-283631 - SV-283631r1190304_rule
RMF Control
SC-4
Severity
M
CCI
CCI-001090
Version
ZEBR-14-008500
Vuln IDs
  • V-283631
Rule IDs
  • SV-283631r1190304_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-88196r1190302_chk

Review managed Zebra Android 14 device configuration settings to determine if the capability to back up to a locally connected system has been disabled. This validation procedure is performed on both the EMM Administration Console and the managed Zebra Android 14 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify "Enable backup service" is toggled to "OFF". On the managed Zebra Android 14 device: COBO: 1. Go to Settings >> System >> Backup. 2. Verify Backup setting is "Not available". COPE: 1. Go to Settings >> System >> Backup. 2. Select "Work". 3. Verify Backup setting is "Not available". If the EMM console device policy is not set to disable the capability to back up to a locally connected system or on the managed Zebra Android 14 device, the device policy is not set to disable the capability to back up to a locally connected system, this is a finding.

Fix: F-88101r1190303_fix

Configure the Zebra Android 14 device to disable backup to locally connected systems. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to "OFF".

b
Zebra Android 14 must be configured to not allow backup of [all applications, configuration data] to remote systems.
SC-4 - Medium - CCI-001090 - V-283632 - SV-283632r1190307_rule
RMF Control
SC-4
Severity
M
CCI
CCI-001090
Version
ZEBR-14-008600
Vuln IDs
  • V-283632
Rule IDs
  • SV-283632r1190307_rule
Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system. Where the remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this case, DOD devices may synchronize DOD sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #40
Checks: C-88197r1190305_chk

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

Fix: F-88102r1190306_fix

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

b
Zebra Android 14 must be configured to enable authentication of personal hotspot connections to the device using a preshared key.
AC-18 - Medium - CCI-001443 - V-283633 - SV-283633r1190310_rule
RMF Control
AC-18
Severity
M
CCI
CCI-001443
Version
ZEBR-14-008700
Vuln IDs
  • V-283633
Rule IDs
  • SV-283633r1190310_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-88198r1190308_chk

This is a user-based enforcement (UBE) control. Check a sample of Zebra devices at the site and verify that the Wi-Fi hotspot preshared key (password) is set to "WPA2/WPA3-Personal" or "WPA3-Personal". 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. On the left of the slide, tap on "Wi-Fi Hotspot" to bring up the configuration options. 4. Click on the "Security" link and verify that either "WPA2/WPA3-Personal" or "WPA3-Personal" is selected. If the Wi-Fi hotspot security is not set to "WPA2/WPA3-Personal" or "WPA3-Personal", this is a finding.

Fix: F-88103r1190309_fix

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

b
Zebra Android 14 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].
AC-6 - Medium - CCI-002233 - V-283635 - SV-283635r1190316_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002233
Version
ZEBR-14-008900
Vuln IDs
  • V-283635
Rule IDs
  • SV-283635r1190316_rule
App data sharing gives apps the ability to access the data of other apps for enhanced user functionality. However, sharing also poses a significant risk that unauthorized users or apps will obtain access to DOD sensitive information. To mitigate this risk, there are data sharing restrictions, primarily prohibiting users 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-88200r1190314_chk

Review documentation on the managed Zebra Android 14 device and inspect the configuration on the Zebra Android device to verify 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-88105r1190315_fix

Configure the Zebra Android 14 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".

b
Zebra Android 14 must be configured to disable multiuser modes.
CM-6 - Medium - CCI-000366 - V-283636 - SV-283636r1190319_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-009000
Vuln IDs
  • V-283636
Rule IDs
  • SV-283636r1190319_rule
Multiuser mode allows multiple users to share a mobile device by providing a degree of separation between user data. To date, no mobile device with multiuser mode features meets DOD requirements for access control, data separation, and nonrepudiation for user accounts. In addition, the MDFPP does not include design requirements for multiuser account services. Disabling multiuser mode mitigates the risk of not meeting DOD multiuser account security policies. SFR ID: FMT_SMF_EXT.1.1 #47a
Checks: C-88201r1190317_chk

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

Fix: F-88106r1190318_fix

Configure the Zebra Android 14 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".

a
Zebra Android 14 must be configured to disable all Bluetooth profiles except for HSP (Headset Profile), HFP (Hands-Free Profile), SPP (Serial Port Profile), A2DP (Advanced Audio Distribution Profile), AVRCP (Audio/Video Remote Control Profile), and PBAP (Phone Book Access Profile).
CM-7 - Low - CCI-000381 - V-283640 - SV-283640r1190331_rule
RMF Control
CM-7
Severity
L
CCI
CCI-000381
Version
ZEBR-14-009400
Vuln IDs
  • V-283640
Rule IDs
  • SV-283640r1190331_rule
Some Bluetooth profiles provide the capability for remote transfer of sensitive DOD data without encryption or otherwise do not meet DOD IT security policies and therefore must be disabled. SFR ID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8
Checks: C-88205r1190329_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 Bluetooth has been disabled. On the EMM console: COBO: 1. Open "User restrictions" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". COPE: 1. Open "User restrictions on parent" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". On the managed Zebra Android 14 device: COBO and COPE: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Verify "Use Bluetooth" is set to "OFF" and cannot be toggled to "ON". If the AO has approved the use of Bluetooth, on the managed Android 14 device: 1. Go to Settings >> Connected Devices. 2. Verify only approved Bluetooth-connected devices using approved profiles are listed. If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an EMM-managed device policy, this is a finding. If the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under "Connected devices", this is a finding.

Fix: F-88110r1190330_fix

Configure the Zebra Android 14 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 "User restrictions" section. 2. Toggle "Disallow Bluetooth" to "ON". COPE: 1. Open "User restrictions on parent" section. 2. Toggle "Disallow Bluetooth" to "ON". The user training requirement is satisfied in requirement ZEBR-14-009800.

b
Zebra Android 14 must be configured to disable ad hoc wireless client-to-client connection capability.
SC-40 - Medium - CCI-002536 - V-283641 - SV-283641r1190334_rule
RMF Control
SC-40
Severity
M
CCI
CCI-002536
Version
ZEBR-14-009500
Vuln IDs
  • V-283641
Rule IDs
  • SV-283641r1190334_rule
Ad hoc wireless client-to-client connections allow mobile devices to communicate with each other directly, circumventing network security policies and making the traffic invisible. This could allow the exposure of sensitive DOD data and increase the risk of downloading and installing malware on the DOD mobile device. SFR ID: FMT_SMF_EXT.1.1/WLAN
Checks: C-88206r1190332_chk

This validation procedure is performed on both the management tool and the Zebra Android device. On the management tool, in the user restrictions, verify "Wi-Fi Direct" has been set to "Disallow". On the Zebra 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 Zebra Android device a Wi-Fi Direct device is listed that can be connected to, this is a finding.

Fix: F-88111r1190333_fix

Configure the Zebra Android devices to disallow Wi-Fi Direct. On the management tool, in the user restrictions, set "Wi-Fi Direct" to "Disallow". Wi-Fi Direct connections and pairing between devices will become unavailable.

b
Zebra Android 14 users must complete required training.
CM-6 - Medium - CCI-000366 - V-283643 - SV-283643r1190340_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-009800
Vuln IDs
  • V-283643
Rule IDs
  • SV-283643r1190340_rule
The security posture of Zebra 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 Zebra mobile device may become compromised, and DOD sensitive data may become compromised. SFR ID: NA
Checks: C-88208r1190338_chk

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

Fix: F-88113r1190339_fix

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

b
Zebra Android 14 must be configured to enforce that Wi-Fi Sharing is disabled.
CM-6 - Medium - CCI-000366 - V-283644 - SV-283644r1190343_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-009900
Vuln IDs
  • V-283644
Rule IDs
  • SV-283644r1190343_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-88209r1190341_chk

Review device configuration settings to confirm Wi-Fi Sharing is disabled. Mobile Hotspot must be enabled to enable Wi-Fi Sharing. If the authorizing official (AO) has not approved Mobile Hotspot, and it has been verified as disabled on the EMM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to verify Wi-Fi Sharing is disabled: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow config tethering" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON". On the managed Zebra Android 14 device: COBO and COPE: 1. Go to Settings >> Network & Internet. 2. Verify "Hotspot & tethering" is "Controlled by admin". 3. Verify that tapping "Hotspot & tethering" provides a prompt to the user specifying "Action not allowed". If on the managed Zebra Android 14 device "Hotspot & tethering" is enabled, this is a finding.

Fix: F-88114r1190342_fix

Configure the Zebra Android 14 device to disable Wi-Fi Sharing. Mobile Hotspot must be enabled to enable Wi-Fi Sharing. If the AO has not approved Mobile Hotspot, and it has been disabled on the EMM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config tethering" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON".

b
Zebra Android 14 must have the DOD root and intermediate PKI certificates installed.
CM-6 - Medium - CCI-000366 - V-283645 - SV-283645r1190346_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010000
Vuln IDs
  • V-283645
Rule IDs
  • SV-283645r1190346_rule
DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the DOD root and intermediate PKI certificates greatly diminishes the risk of this attack. SFR ID: FMT_SMF_EXT.1.1 #11
Checks: C-88210r1190344_chk

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

Fix: F-88115r1190345_fix

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

b
The Zebra Android 14 work profile must be configured to prevent users from adding personal email accounts to the work email app.
CM-6 - Medium - CCI-000366 - V-283646 - SV-283646r1190349_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010100
Vuln IDs
  • V-283646
Rule IDs
  • SV-283646r1190349_rule
If the user is able to add a personal email account (POP3, IMAP, EAS) to the work email app, it could be used to forward sensitive DOD data to unauthorized recipients. Restricting email account addition to the administrator or restricting email account addition to allowlisted accounts mitigates this vulnerability. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88211r1190347_chk

Review the managed Zebra Android 14 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 Zebra Android 14 device. COPE: On the EMM console: 1. Open "Set user restrictions". 2. Verify "Disallow modify accounts" is toggled to "ON". On the managed Zebra Android 14 device: 1. Open Settings. 2. Tap "Passwords & accounts". 3. Select "Work". 4. Tap "Add account". 5. Verify a message is displayed to the user stating, "Action not allowed" or "Blocked by work policy". If on the EMM console the restriction to "Disallow modify accounts" is not set, or on the managed Android 14 device the user is able to add an account in the Work section, this is a finding.

Fix: F-88116r1190348_fix

Configure the Zebra Android 14 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.

b
The Zebra Android 14 work profile must be configured to enforce the system application disable list.
CM-6 - Medium - CCI-000366 - V-283647 - SV-283647r1190352_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010200
Vuln IDs
  • V-283647
Rule IDs
  • SV-283647r1190352_rule
The system application disable list controls user access to/execution of all core and preinstalled applications. Core application: Any application integrated into Zebra Android 14 by Zebra. Preinstalled application: Additional noncore applications included in the Zebra Android 14 build by Zebra or the wireless carrier. Some system applications can compromise DOD data or upload users' information to non-DOD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DOD data or DOD user information. The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DOD use by configuring the system application disable list. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88212r1190350_chk

Review the managed Zebra Android 14 work profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. Verify only approved system apps have been placed on the core allowlist. This procedure is performed on the EMM Administration Console. Review the system app allowlist and verify only approved apps are on the list. COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Verify package names of apps are listed. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Verify package names of apps are listed. If on the EMM console the system app allowlist contains unapproved core apps, this is a finding.

Fix: F-88117r1190351_fix

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

b
Zebra Android 14 must be provisioned as a fully managed device and configured to create a work profile.
CM-6 - Medium - CCI-000366 - V-283648 - SV-283648r1190355_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010300
Vuln IDs
  • V-283648
Rule IDs
  • SV-283648r1190355_rule
The Android Enterprise work profile is the designated application group for the COPE use case. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88213r1190353_chk

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

Fix: F-88118r1190354_fix

Configure the Zebra Android 14 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 Zebra Android 14 work profile must be configured to disable automatic completion of workspace internet browser text input.
CM-6 - Medium - CCI-000366 - V-283649 - SV-283649r1190358_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010400
Vuln IDs
  • V-283649
Rule IDs
  • SV-283649r1190358_rule
The autofill functionality in the web browser allows the user to complete a form that contains sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill functionality, an adversary who learns a user's Android 14 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_EXT.1.1 #47
Checks: C-88214r1190356_chk

Review the work profile Chrome Browser app on the Zebra Android 14 autofill setting. This procedure is performed only on the EMM Administration Console. On the EMM console: COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify "PasswordManagerEnabled" is turned "OFF". 4. Verify "AutofillAddressEnabled" is turned "OFF". 5. Verify "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-88119r1190357_fix

Configure the Chrome browser on the Zebra Android 14 device work profile to disable autofill. On the EMM console: COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "PasswordManagerEnabled" is turned "OFF". 4. Ensure "AutofillAddressEnabled" is turned "OFF". 5. Ensure "AutofillCreditCardEnabled" is turned "OFF". Refer to the EMM documentation to determine how to configure Chrome Browser Settings.

b
The Zebra Android 14 work profile must be configured to disable the autofill services.
CM-6 - Medium - CCI-000366 - V-283650 - SV-283650r1190361_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010500
Vuln IDs
  • V-283650
Rule IDs
  • SV-283650r1190361_rule
The autofill services allow the user to complete text inputs that could contain sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill services, an adversary who learns a user's Android 14 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, Zebra, Dashlane, LastPass, and 1Password. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88215r1190359_chk

Review the Zebra Android 14 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: COPE: 1. Open "Set user restrictions". 2. Verify "Disable autofill" is toggled to "ON". If on the EMM console "disallow autofill" is not selected, this is a finding.

Fix: F-88120r1190360_fix

Configure the Zebra Android 14 device work profile to disable the autofill services. On the EMM console: COPE: 1. Open "Set user restrictions". 2. Toggle "Disable autofill" to "ON".

b
Zebra Android 14 must be configured to disallow configuration of date and time.
CM-6 - Medium - CCI-000366 - V-283651 - SV-283651r1190364_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-010600
Vuln IDs
  • V-283651
Rule IDs
  • SV-283651r1190364_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 Zebra Android 14 are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DOD network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier. Time stamps generated by the audit system in Zebra Android 14 must include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88216r1190362_chk

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

Fix: F-88121r1190363_fix

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

c
Zebra Android 14 devices must have the latest available Zebra Android 14 operating system installed.
CM-6 - High - CCI-000366 - V-283653 - SV-283653r1190370_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000366
Version
ZEBR-14-010800
Vuln IDs
  • V-283653
Rule IDs
  • SV-283653r1190370_rule
Required security features are not available in earlier operating system versions. In addition, earlier versions may have known vulnerabilities. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88218r1190368_chk

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

Fix: F-88123r1190369_fix

Install the latest released version of the Zebra Android 14 operating system on all managed Zebra devices. Note: Zebra Android device operating system updates are released directly by Zebra or can be distributed via the EMM. Check each device manufacturer and/or carriers for current updates.

a
Android 14 devices must be configured to disable the use of third-party keyboards.
CM-6 - Low - CCI-000366 - V-283654 - SV-283654r1190373_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
ZEBR-14-010900
Vuln IDs
  • V-283654
Rule IDs
  • SV-283654r1190373_rule
Many third-party keyboard applications are known to contain malware. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88219r1190371_chk

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

Fix: F-88124r1190372_fix

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

a
Android 14 devices must be configured to enable Common Criteria mode (CC mode).
CM-6 - Low - CCI-000366 - V-283655 - SV-283655r1190376_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
ZEBR-14-011000
Vuln IDs
  • V-283655
Rule IDs
  • SV-283655r1190376_rule
The CC mode feature is a superset of other features and behavioral changes that are mandatory MDFPP requirements. If CC mode is not implemented, the device will not be operating in the NIAP-certified compliant CC mode of operation. CC mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi keys are stored using different types of encryption. SFR ID: FMT_SMF_EXT.1.1 #47
Checks: C-88220r1190374_chk

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

Fix: F-88125r1190375_fix

Configure the Zebra Android 14 device to implement CC mode. On the EMM console: COBO and COPE: 1. Open Device owner management. 2. Toggle "Enable Common Criteria mode" to "ON".

b
Zebra Android 14 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-283656 - SV-283656r1190379_rule
RMF Control
AC-6
Severity
M
CCI
CCI-002235
Version
ZEBR-14-012200
Vuln IDs
  • V-283656
Rule IDs
  • SV-283656r1190379_rule
If a user is able to configure the security setting, the user could inadvertently or maliciously set it to a value that poses unacceptable risk to DOD information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information. SFR ID: FMT_MOF_EXT.1.2 #24
Checks: C-88221r1190377_chk

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

Fix: F-88126r1190378_fix

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

b
Zebra Android 14 must allow only the administrator (EMM) to install/remove DOD root and intermediate PKI certificates.
CM-6 - Medium - CCI-000366 - V-283657 - SV-283657r1190382_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-012300
Vuln IDs
  • V-283657
Rule IDs
  • SV-283657r1190382_rule
DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the user is allowed to remove root and intermediate certificates, the user could allow an adversary to falsely sign a certificate in such a way that it could not be detected. Restricting the ability to remove DOD root and intermediate PKI certificates to the administrator mitigates this risk. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88222r1190380_chk

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

Fix: F-88127r1190381_fix

Configure the Zebra Android 14 device to prevent a user from removing DOD root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Toggle "Disallow config credentials" to "ON".

a
Zebra Android 14 must allow only the administrator (MDM) to perform the following management function: Disable Phone Hub.
SC-4 - Low - CCI-001090 - V-283658 - SV-283658r1190385_rule
RMF Control
SC-4
Severity
L
CCI
CCI-001090
Version
ZEBR-14-012400
Vuln IDs
  • V-283658
Rule IDs
  • SV-283658r1190385_rule
It may be possible to transfer work profile data on a DOD Android device to an unauthorized Chromebook if the user has the same Zebra account set up on the Chromebook and in the work profile on the Android device. This could result in the exposure of sensitive DOD data. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88223r1190383_chk

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

Fix: F-88128r1190384_fix

Configure the Zebra Android 14 device to disable the nearby notification streaming policy to disable Phone Hub. COPE and COBO: On the EMM console: 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".

b
Zebra Android 14 must disable the user's ability to wipe the device.
CM-6 - Medium - CCI-000366 - V-283659 - SV-283659r1190388_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-013000
Vuln IDs
  • V-283659
Rule IDs
  • SV-283659r1190388_rule
This feature must be disabled to comply with DOD electronic records retention requirements for mobile devices. Otherwise, mobile device users could wipe the device, which would violate DOD policy. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88224r1190386_chk

Review configuration settings to confirm the user is unable to perform a factory reset and the admin has the ability to inject a recovery account on the device so they can unlock Factory Reset Protection (FRP). This check procedure is performed on the device management tool and the Zebra Android 14 device. On the MDM console: Verify factory reset configuration: COBO and COPE: 1. Open user restrictions. 2. Verify that "Disallow Factory Reset" is enabled. Verify factory reset protection policy configuration: From the Android Enterprise policy management: 1. Go to the Factory Reset Protection section. 2. Verify that "Factory Reset Protection" is set to "Allow/Enabled". 3. Verify that the correct Zebra Account ID(s) is/are listed as allowed to unlock the FRP. On the managed Zebra Android 14 device, verify factory reset configuration: COBO and COPE: 1. Open Settings >> General management >> Reset. 2. Tap the "Factory data reset" option. 3. Verify that the "Action not allowed" pop-up appears and factory data reset does not proceed. If the Android device user is able to perform a factory reset or the admin cannot unlock the Android phone after an FRP event, this is a finding.

Fix: F-88129r1190387_fix

Configure the Zebra Android 14 device to disable user's ability to wipe the Android device. Enable the admin to inject a recovery account on the device so they can unlock FRP. On the MDM console: Disallow factory reset: COBO and COPE: 1. Open user restrictions. 2. Enable "Disallow Factory Reset". Set factory reset protection policy: COBO and COPE: 1. Device owner management >> Set factory reset protection. 2. From Accounts section: Add Account >> Enter recovery account >> Press "OK". 3. From Enabled section: Select "Enabled" to enable FRP policy. 4. Press "Save" to confirm all changes. Configuration API: factoryResetDisabled, frpAdminEmails[ ]

a
Zebra Android 14 must disable the use of assistants (including Zebra Assistant) unless required to meet Section 508 compliance requirements.
CM-6 - Low - CCI-000366 - V-283660 - SV-283660r1190391_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
ZEBR-14-013100
Vuln IDs
  • V-283660
Rule IDs
  • SV-283660r1190391_rule
The use of assistants could expose sensitive DOD data to cloud-based servers during the processing of assistant requests. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88225r1190389_chk

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

Fix: F-88130r1190390_fix

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

a
Zebra Android 14 must disable wireless printing.
CM-6 - Low - CCI-000366 - V-283661 - SV-283661r1190394_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
ZEBR-14-013200
Vuln IDs
  • V-283661
Rule IDs
  • SV-283661r1190394_rule
Wireless printing allows the printing of sensitive DOD documents to non-DOD controlled printers, which may lead to the exposure of sensitive DOD information. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88226r1190392_chk

Review configuration settings to confirm that wireless printing has been disabled. This check procedure is performed on the device management tool and the Zebra Android 14 device. On the MDM console: COBO and COPE: 1. Open user restrictions. 2. Verify that "Disallow printing" is enabled. On the managed Zebra Android 14 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-88131r1190393_fix

Configure Zebra Android 14 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
Zebra Android 14 must disable screen capture.
CM-6 - Low - CCI-000366 - V-283662 - SV-283662r1190397_rule
RMF Control
CM-6
Severity
L
CCI
CCI-000366
Version
ZEBR-14-013300
Vuln IDs
  • V-283662
Rule IDs
  • SV-283662r1190397_rule
The screen capture feature could lead to the exposure of sensitive DOD information. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88227r1190395_chk

Review configuration settings to confirm that screen capture has been disabled. This check procedure is performed on the device management tool and the Zebra Android 14 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 Zebra Android 14 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-88132r1190396_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
Zebra Android 14 devices must have a Mobile Threat Detection (MTD) app installed.
CM-6 - Medium - CCI-000366 - V-283663 - SV-283663r1190400_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-013400
Vuln IDs
  • V-283663
Rule IDs
  • SV-283663r1190400_rule
DOD mobile devices are in constant risk of cyber threats. MTD apps mitigate these risks by providing real-time threat detection, malware prevention, and vulnerability analysis. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88228r1190398_chk

Confirm that an MTD app is installed on managed Zebra Android devices. This check procedure is performed on both the device management tool and the Zebra 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 Zebra Android device: 1. Open the Settings app. 2. Tap "Apps" and then "See all apps". 3. Verify that an MTD app is listed. If an MTD app is not installed on the device, this is a finding.

Fix: F-88133r1190399_fix

Install an MTD app on managed Zebra Android devices.

b
Zebra Android 14 must implement the management setting: disable Camera.
CM-6 - Medium - CCI-000366 - V-283664 - SV-283664r1190778_rule
RMF Control
CM-6
Severity
M
CCI
CCI-000366
Version
ZEBR-14-013500
Vuln IDs
  • V-283664
Rule IDs
  • SV-283664r1190778_rule
Authorizing official (AO) approval is required before the mobile device camera can be enabled for a specific user or group of users, based on a risk assessment of the operational environment. Camera use may lead to the exposure of sensitive DOD information in some operational environments. SFR ID: FMT_MOF_EXT.1.2 #47
Checks: C-88229r1190619_chk

Determine if the site AO has approved the use of device cameras. Look for a document showing approval for a specific user or group of users. If not approved, review configuration settings to confirm "Allow Camera" is disabled. If approved, this requirement is not applicable. Review configuration settings to confirm the device camera has been disabled. This check procedure is performed on the device management tool and the Zebra Android 14 device. On the MDM console: COBO and COPE: 1. Open Camera. 2. Verify that the "Disable camera" setting is disabled. On the managed Zebra Android 14 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-88134r1190402_fix

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