| V-250448 | High | Android 12 devices must have the latest available Google Android 12 operating system installed. | Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions.
SFR ID: FMT_SMF_EXT.1.1 #47 |
| V-250453 | Medium | Google Android 12 must allow only the administrator (EMM) to install/remove DoD root and intermediate PKI certificates. | 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,... |
| V-250419 | Medium | Google Android 12 must be configured to enforce a minimum password length of six characters. | 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... |
| V-250418 | Medium | Google Android 12 must be configured to enable audit logging. | 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:... |
| V-250428 | Medium | Google Android 12 must be configured to disable trust agents.
Note: This requirement is not applicable (NA) for specific biometric authentication factors included in the product's Common Criteria evaluation. | 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... |
| V-250429 | Medium | Google Android 12 must be configured to disable developer modes. | Developer modes expose features of the mobile operating system (MOS) that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to... |
| V-250422 | Medium | Google Android 12 must be configured to lock the display after 15 minutes (or less) of inactivity. | 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... |
| V-250423 | Medium | Google Android 12 must be configured to not allow more than 10 consecutive failed authentication attempts. | 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... |
| V-250420 | Medium | Google Android 12 must be configured to not allow passwords that include more than two repeating or sequential characters. | 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... |
| V-250421 | Medium | Google Android 12 must be configured to enable a screen-lock policy that will lock the display after a period of inactivity. | The screen-lock timeout helps protect the device from unauthorized access. Devices without a screen-lock timeout provide an opportunity for adversaries who gain physical access to the mobile... |
| V-250426 | Medium | Google Android 12 allowlist must be configured to not include applications with the following characteristics: 1. Back up mobile device (MD) data to non-DoD cloud servers (including user and application access to cloud backup services);2. Transmit MD diagnostic data to non-DoD servers;3. Voice assistant application if available when MD is locked;4. Voice dialing application if available when MD is locked;5. Allows synchronization of data or applications between devices associated with user; and6. Allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs or printers. | 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... |
| V-250427 | Medium | Google Android 12 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]. | 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... |
| V-250424 | Medium | Google Android 12 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]. | 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... |
| V-250425 | Medium | Google Android 12 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]. | The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must... |
| V-250440 | Medium | Google Android 12 must be configured to enforce that Wi-Fi Sharing is disabled. | 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... |
| V-250441 | Medium | Google Android 12 must have the DoD root and intermediate PKI certificates installed. | 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... |
| V-250442 | Medium | The Google Android 12 Work Profile must be configured to prevent users from adding personal email accounts to the work email app. | 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... |
| V-250443 | Medium | Google Android 12 work profile must be configured to enforce the system application disable list. | The system application disable list controls user access to/execution of all core and preinstalled applications.
Core application: Any application integrated into Google Android 12 by Google.
... |
| V-250444 | Medium | Google Android 12 must be provisioned as a fully managed device and configured to create a work profile. | The Android Enterprise Work Profile is the designated application group for the COPE use case.
SFR ID: FMT_SMF_EXT.1.1 #47 |
| V-250445 | Medium | Google Android 12 work profile must be configured to disable automatic completion of work space Internet browser text input. | 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... |
| V-250446 | Medium | Google Android 12 Work Profile must be configured to disable the autofill services. | 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... |
| V-250447 | Medium | Google Android 12 must be configured to disallow configuration of date and time. | Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events.
Periodically synchronizing... |
| V-250454 | Medium | Google Android 12 must be configured to disable all data signaling over [assignment: list of externally accessible hardware ports (for example, USB)]. | 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... |
| V-250439 | Medium | Google Android 12 users must complete required training. | The security posture of Google devices requires the device user to configure several required policy rules on their device. User-Based Enforcement (UBE) is required for these controls. In... |
| V-250438 | Medium | Google Android 12 must be configured to disable ad hoc wireless client-to-client connection capability. | 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... |
| V-250435 | Medium | Google Android 12 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]. | 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... |
| V-250434 | Medium | Google Android 12 must be configured to not allow backup of [all applications, configuration data] to remote systems. | Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system (MOS). Where the... |
| V-250436 | Medium | Google Android 12 must be configured to disable multiuser modes. | 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... |
| V-250431 | Medium | Google Android 12 must be configured to generate audit records for the following auditable events: detected integrity violations. | 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... |
| V-250433 | Medium | Google Android 12 must be configured to not allow backup of [all applications, configuration data] to locally connected systems. | 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... |
| V-250432 | Medium | Google Android 12 must be configured to disable USB mass storage mode. | 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... |
| V-250450 | Low | Android 12 devices must be configured to enable Common Criteria Mode (CC Mode). | 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... |
| V-250449 | Low | Android 12 devices must be configured to disable the use of third-party keyboards. | Many third-party keyboard applications are known to contain malware.
SFR ID: FMT_SMF_EXT.1.1 #47 |
| V-250437 | Low | Google Android 12 must be configured to disable Bluetooth or configured via User Based Enforcement (UBE) to allow Bluetooth for only Headset Profile (HSP), Hands-Free Profile (HFP), and Serial Port Profile (SPP). | 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... |
| V-250430 | Low | Google Android 12 must be configured to display the DoD advisory warning message at startup or each time the user unlocks the device. | 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... |
