Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Review Motorola Android 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 MDM Administration Console and the Android Pie device. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Verify the minimum password length is set to "6" characters. On the Android Pie device: 1. Open Settings >> Security & location >> Screen lock. 2. Enter current password. 3. Tap on "Password". 4. Verify Password length listed is at least "6". If the device password length is not set to six characters or more on the MDM console or the Android Pie device, this is a finding.
Configure the Motorola Android device to enforce a minimum password length of six characters. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Enter the number of characters as "6".
Review Motorola Android device configuration settings to determine if the mobile device is prohibiting passwords with more than two repeating or sequential characters. This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Verify the password quality is set to "Complex". On the Android Pie device: 1. Open Settings >> Security & location >> Screen lock. 2. Enter current password. 3. Tap on "Password". 4. Verify Password complexity requirements are listed: must contain at least one letter, one numeric digit, one special symbol. If the MDM console device policy is set to a password with more than two repeating or sequential characters, or on the Android Pie device, the device policy is set to a password with more than two repeating or sequential characters, this is a finding.
Configure the Motorola Android device to prevent passwords from containing more than two repeating or sequential characters. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Set password quality to "Complex".
Review Motorola 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 inactivity. This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Verify "Device Lock Timeout" is set to any number desired. Units are in minutes. On the Android Pie device: 1. Open Settings >> Security & location. 2. Click the gear icon next to "Screen lock". 3. Verify "Automatically lock" is set to a required time. If the MDM console device policy is not set to enable a screen lock policy that will lock the display after a period of inactivity, or on the Android Pie device, the device policy is not set to enable a screen lock policy that will lock the display after a period of inactivity, this is a finding.
Configure the Motorola Android device to enable a screen lock policy that will lock the display after a period of inactivity. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Set "Device Lock Timeout" to any number desired. Units are in minutes.
Review Motorola Android device configuration settings to determine if the mobile device has the screen lock timeout set to 15 minutes or less. This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open passcode requirements. 2. Open device passcode section. 3. Verify "Device Lock Timeout" is set to any number between 1 and 15. On the Android Pie device: 1. Open Settings >> Security & location. 2. Click the gear icon next to "Screen lock". 3. Verify "Automatically lock" is set to between 0 and 15 minutes. If the MDM console device policy is not set to 15 minutes or less for the screen lock timeout, or on the Android Pie device, the device policy is not set to 15 minutes or less for the screen lock timeout, this is a finding.
Configure the Motorola Android device to lock the device display after 15 minutes (or less) of inactivity. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Set "Device Lock Timeout" to any number between 1 and 15.
Review Motorola Android 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 MDM Administration Console and the Android Pie device. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Review the policy configuration that was pushed down to the device and verify the "Maximum Number of Failed Attempts" is set to between 1 and 10. On the Android Pie device: 1. Open Setting >> Security & location >> Managed device info. 2. Verify "Failed password attempts before deleting all device data" is set to 10 or fewer attempts. If the MDM console device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer or on the Android Pie device, the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.
Configure the Motorola Android device to allow only 10 or fewer consecutive failed authentication attempts. On the MDM console: 1. Open password requirements. 2. Open device password section. 3. Set "Maximum Number of Failed Attempts" to a number between 1 and 10.
Review Motorola Android device configuration settings to determine if the mobile device has only approved application repositories (DoD-approved commercial app repository, MDM server, and/or mobile application store). This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open Restrictions section. 2. Set Allow "Google Play" (Uses only Managed Google Play). 3. Verify that Disallow is set for "Install unknown sources". On the Android Pie device: 1. Open Settings >> Apps and notifications >> Advanced >> 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 MDM console device policy is not set to allow connections to only approved application repositories, or on the Android Pie device, the device policy is not set to allow connections to only approved application repositories, this is a finding.
Configure the Motorola Android device to disable unauthorized application repositories. On the MDM console: 1. Open Restrictions section. 2. Set Allow "Google Play" (Uses only Managed Google Play). 3. Set Disallow "Install unknown sources".
Review Motorola Android device configuration settings to determine if the mobile device has an application whitelist configured. Verify all applications listed on the whitelist have been approved by the Approving Official (AO). This validation procedure is performed only on the MDM Administration Console. On the MDM console: 1. Go to the Android app catalog for managed Google Play. 2. Verify all selected apps are AO approved. NOTE: Managed Google Play is always a Whitelisted App Store. If on the MDM console the list of selected Managed Google Play apps includes non-approved apps, this is a finding. NOTE: The application whitelist will include approved core applications (included in the OS by the OS vendor) and pre-installed applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and pre-installed applications. For Google Android, there are no pre-installed applications.
Configure the Motorola Android device to use an application whitelist. On the MDM console: 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 always a Whitelisted App Store.
Review Motorola Android device configuration settings to determine if the mobile device has an application whitelist configured and that the application whitelist does not include applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; - payment processing; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. This validation procedure is performed only on the MDM Administration Console. On the MDM 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 MDM console device policy includes applications with unauthorized characteristics, this is a finding.
Configure the Motorola Android device application whitelist to exclude applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; - payment processing; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers. On the MDM 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.
Determine if the AO has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify Bluetooth has been disabled. On the MDM console: 1. Open Restrictions section. 2. Verify "Disallow Bluetooth" is set. On the Android Pie device: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Verify this is set to "Off" and cannot be toggled to "On". If the AO has approved the use of Bluetooth, on the Android Pie 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 MDM 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.
Configure the Motorola Android 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 (UBE). To disable Bluetooth, use the following procedure. On the MDM console: 1. Open Restrictions section. 2. Toggle "Disallow Bluetooth" to "On". The user training requirement is satisfied in requirement MOTO-09-008700.
Review device configuration settings to confirm that trust agents are disabled. This procedure is performed on both the MDM Administration console and the Motorola Android Pie device. On the MDM console: 1. Open Restrictions section. 2. Set "Disable trust agents" to "On". On the Android Pie device: 1. Open Settings. 2. Tap "Security & location". 3. Tap "Advanced". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the MDM console "disable trust agents" is not selected, or on the Android Pie device a trust agent can be enabled, this is a finding.
Configure Motorola Android Pie to disable trust agents. On the MDM console: 1. Open Lock screen restrictions section. 2. Set "Disable trust agents" to on.
Review Motorola Android device configuration settings to determine whether a developer mode is enabled. This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open Restrictions section. 2. Verify "Debugging Features" is set to "Disallow". On the Android Pie device: 1. Go to Settings >> System. 2. Verify "Developer Options" is not listed. If the MDM console device policy is not set to disable developer mode, or on the Android Pie device, the device policy is not set to disable developer mode, this is a finding.
Configure the Motorola Android device to disable developer modes. On the MDM console: 1. Open Restrictions section. 2. Set "Debugging Features" to "Disallow".
The DoD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Discussion): 1. By placing the DoD warning banner text in the user agreement signed by each Motorola Android device user (preferred method). 2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device. Determine which method is used at the Motorola Android device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Motorola Android device users and verify the agreement includes the required DoD warning banner text. Validation Procedure for Method #2: On the MDM console, ensure "Lock Screen Message" is set and the appropriate banner text is included. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the MDM console device policy is not set to display a warning banner with the appropriate designated wording or on the Android Pie device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.
Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Discussion): 1. By placing the DoD warning banner text in the user agreement signed by each Motorola Android device user (preferred method). 2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device. On the MDM console: Enable "Lock Screen Message" and enter the banner text.
Review Motorola Android 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 MDM Administration Console and the Android Pie device. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Verify "Disallow usb file transfer" is selected. On the Android Pie device: 1. Plug USB cable into Android Pie 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 MDM console device policy is not set to disable USB mass storage mode, or on the Android Pie device, the device policy is not set to disable USB mass storage mode, this is a finding.
Configure the Motorola Android device to disable USB mass storage mode. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Select "Disallow usb file transfer".
Review Motorola Android 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 MDM Administration Console and the Android Pie device. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Verify "Disallow usb file transfer" is selected. On the Android Pie device: 1. Plug USB cable into Android Pie 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 MDM console device policy is not set to disable the capability to back up to a locally connected system, or on the Android Pie device, the device policy is not set to disable the capability to back up to a locally connected system, this is a finding.
Configure the Motorola Android device to disable backup to locally connected systems. NOTE: On Restrictions, the backup features for Motorola are not in the framework. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Select "Disallow usb file transfer".
Review Motorola Android device configuration settings to determine if the capability to back up to a remote system has been disabled. This validation procedure is performed on both the MDM Administration Console and the Android Pie device. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Verify "Disallow backup service" is not selected. On the Android Pie device: 1. Go to Settings >> System. 2. Verify "Backup" is set to "Off". If the MDM console device policy is not set to disable the capability to back up to a remote system, or on the Android Pie device, the device policy is not set to disable the capability to back up to a remote system, this is a finding.
Configure the Motorola Android device to disable backup to remote systems (including commercial clouds). NOTE: On Restrictions, data in the work profile cannot be backed up by default. On the MDM console: 1. Open Device Restrictions. 2. Open Restrictions settings. 3. Ensure "Enable backup service" is not selected.
Review documentation on the Motorola Android device and inspect the configuration on the Motorola Android device to enable audit logging. This validation procedure is performed on only on the MDM Administration Console. On the MDM console: 1. Open the Restrictions settings. 2. Open User settings. 3. Select "Enable security logging". 4. Select "Enable network logging". If the MDM console device policy is not set to enable audit logging, this is a finding.
Configure the Motorola Android Pie to enable audit logging. On the MDM console: 1. Open the Restrictions settings. 2. Open User settings. 3. Select "Enable security logging". 4. Select "Enable network logging".
Review Motorola Android 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 MDM Administration Console. On the MDM console: 1. Go to Policy management. 2. Verify "Security Logging" is enabled. If the MDM console device policy is not set to enable security logging, this is a finding.
Configure the Motorola Android device to generate audit records for the following auditable events: detected integrity violations. On the MDM console: 1. Go to Policy management. 2. Enable "Security Logging".
Review a sample of site User Agreements for Motorola device users or similar training records and training course content. Verify that Motorola 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 Motorola device user has not completed the required training, this is a finding.
Have all Motorola device users complete training on the following topics. Users should acknowledge that they have reviewed training via a signed User Agreement or similar written record. Training topics: - 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 Motorola 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). - AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.) in the Motorola device personal space. Motorola provides an Administrative Guide for the LEX L11 device to NIAP customers (refer to https://www.niap-ccevs.org/MMO/Product/st_vid11002-agd.pdf). The guide includes procedures for configuring Common Criteria on the Motorola Solutions, Inc. LEX L11 device.
Review device configuration settings to confirm Wi-Fi Sharing is disabled. Mobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the Authorizing Official (AO) has not approved Mobile Hotspot, and it has been verified as disabled on the MDM 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 MDM console: 1. Open the User restrictions setting. 2. Verify "Disallow config tethering" is set to "On". On the Android Pie device: 1. Open Settings. 2. Tap "Networks & internet". 3. Verify that "Hotspots & tethering" is disabled. If On the Android Pie device "Wi-Fi sharing" is enabled, this is a finding.
Configure Motorola Android Pie to disable Wi-Fi Sharing. Mobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the AO has not approved Mobile Hotspot, and it has been disabled on the MDM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: On the MDM console: 1. Open the User restrictions setting. 2. Set "Disallow config tethering" to "On".
Review device configuration settings to confirm that the DoD root and intermediate PKI certificates are installed. This procedure is performed on both the MDM Administration console and the Motorola Android Pie 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 MDM 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 Android Pie device: 1. Open Settings. 2. Tap "Security & Location". 3. Tap on "Advanced". 4. Tap on "Encryption & credentials". 5. Tap on "Trusted credentials". 6. Verify that DoD root and intermediate PKI certificates are listed under the user tab. If on the MDM console the DoD root and intermediate certificates are not listed in a profile, or the Motorola Android Pie device does not list the DoD root and intermediate certificates under the user tab, this is a finding.
Configure Motorola Android Pie to install DoD root and intermediate certificates. On the MDM 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).
Review the device configuration to confirm that the user is unable to remove DoD root and intermediate PKI certificates. On the MDM console: 1. Open the User restrictions setting. 2. Verify that "Disallow config credentials" is set to "On" for the work profile. On the Android Pie device: 1. Open Settings. 2. Tap "Security & Location". 3. Tap on "Advanced". 4. Tap on "Encryption & credentials". 5. Tap on "Trusted credentials". 6. Verify that the user is unable to untrust or remove any work certificates. If on the Motorola Android Pie device the user is able to remove certificates, this is a finding.
Configure Motorola Android Pie to prevent a user from removing DoD root and intermediate PKI certificates. On the MDM console: 1. Open the User restrictions setting. 2. Set "Disallow config credentials" to "On" for the work profile.
Review the Motorola Android Pie Work Profile to confirm that user configuration of date and time is not allowed. This procedure is performed on both the MDM Administration console and the Motorola Android Pie device. On the MDM console, verify that "Set auto (network) time required" is set to "On". On the Android Pie device: 1. Open Settings. 2. Tap "System". 3. Tap "Date & times". 4. Verify that "Automatic date & time" is grayed out. If on the MDM console "Set auto (network) time required" is not set to "On", or on the Motorola Android Pie device, "Automatic date & time" is grayed out, this is a finding.
Configure Motorola Android Pie Work Profile to set auto network time. On the MDM console, in the Android user restrictions section, set "Set auto (network) time required" to "On".
Review the Motorola Android Pie device configuration settings to confirm that outgoing beam is disallowed. This procedure is performed on both the MDM Administration console and the Motorola Android Pie device. On the MDM console, in the Android user restrictions section, verify that "Disallow outgoing beam" is set to "On". On the Android Pie device: 1. Open Settings. 2. Tap "Connected devices". 3. Tap "Connection preferences". 4. Verify that "Android Beam" is off and grayed out. If on the MDM console "Disallow outgoing beam" is not set to "On", or on the Motorola Android Pie device "Android Beam" is not off and grayed out, this is a finding.
Configure the Motorola Android Pie device to disallow outgoing beam. On the MDM console, in the Android user restrictions section, set "Disallow outgoing beam" to "On".
Review device configuration settings to confirm that the most recently released version of Motorola Android Pie is installed. For Motorola Android Pie, LEXL11 current version: PIE.L11_P_30.22.01 uses latest Google Android 9.0 version (and Security Patches) as provided by Qualcomm (chipset vendor) based on Android OS 9.0. Linux Kernel version is 4.4.153. This procedure is performed on both the MDM console and the Motorola Android Pie device. In the MDM management console, review the version of Motorola Android Pie installed on a sample of managed devices. This procedure will vary depending on the MDM product. On the Android Pie device, to see the installed operating system version: 1. Open Settings. 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Android operating system on any reviewed Motorola devices is not the latest released by the wireless carrier, this is a finding.
Install the latest released version of the Motorola Android Pie operating system on all managed Motorola devices. For Motorola Android Pie, LEXL11 current version: PIE.L11_P_30.22.01 uses latest Google Android 9.0 version (and Security Patches) as provided by Qualcomm (chipset vendor) based on Android OS 9.0. Linux Kernel version is 4.4.153.
Review device configuration settings to confirm that version LEXL11 NIAP-approved build number (based on Android OS 9.0) is PIE.L11_P_R30.21.10 and Kernel version is 4.4.153. See: https://www.niap-ccevs.org/Product/Compliant.cfm?PID=11002 This procedure is performed on both the MDM console and the Motorola Android Pie device. In the MDM management console, review the version of Motorola Android Pie installed on a sample of managed devices. On the Android Pie device, to see the installed operating system version: 1. Open Settings. 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Android operating system on any reviewed Motorola device is not the latest released by the wireless carrier, this is a finding. See Motorola's Android operating system patch website: https://source.android.com/security/bulletin/ If the installed version of the Android Pie operating system is not the NIAP-approved version, this is a finding.
Install the latest released version of the Motorola Android Pie operating system on all managed Motorola devices. For Motorola Android Pie, LEXL11 NIAP-approved build number (based on Android OS 9.0) is PIE.L11_P_R30.21.10, and Kernel version is 4.4.153. See: https://www.niap-ccevs.org/Product/Compliant.cfm?PID=11002 LEX L11 current version: PIE.L11_P_30.22.01 is based on the LEX L11 NIAP version, with small additions. The changes are dedicated to support Verizon Wireless and AT&T carriers' requirements only.