| Finding ID |
Severity |
Title |
Description |
|
V-254758
|
High |
Android 13 devices must have the latest available Google Android 13 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-254762
|
Medium |
The Google Android 13 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, the user could allow an adversary to falsely sign a certificate in such a way that it could not... |
|
V-254761
|
Medium |
Google Android 13 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 exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.
SFR ID: FMT_MOF_EXT.1.2 #24 |
|
V-254757
|
Medium |
Google Android 13 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 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... |
|
V-254756
|
Medium |
The Google Android 13 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 13 by Google.
Preinstalled application: Additional noncore applications included in the Google Android 13 build by Google or the wireless carrier.
Some system applications can compromise DOD... |
|
V-254755
|
Medium |
Google Android 13 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 adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the... |
|
V-254754
|
Medium |
Google Android 13 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 (cellular) connection.
Wi-Fi Sharing grants the "other" device access to a corporate Wi-Fi network and may possibly bypass the network access control... |
|
V-254753
|
Medium |
Google Android 13 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 addition, if the authorizing official (AO) has approved the use of an unmanaged personal space, the user must receive training on risks.... |
|
V-254752
|
Medium |
Google Android 13 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 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 |
|
V-254750
|
Medium |
Google Android 13 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 for access control, data separation, and nonrepudiation for user accounts. In addition, the MDFPP does not include design requirements... |
|
V-254749
|
Medium |
Google Android 13 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 remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this... |
|
V-254748
|
Medium |
Google Android 13 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 connected or cloud based), many if not all of these mechanisms are no longer present. This leaves the backed-up data vulnerable to... |
|
V-254747
|
Medium |
Google Android 13 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 potential vector for malware and unauthorized data exfiltration. Prohibiting USB mass storage mode mitigates this risk.... |
|
V-254746
|
Medium |
Google Android 13 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 facilitate analysis to improve performance and security. The Requirement Statement lists key events for which the system must generate an audit... |
|
V-254744
|
Medium |
Google Android 13 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 compromise the confidentiality, integrity, and availability of DOD sensitive information. Disabling developer modes mitigates this risk.
SFR ID: FMT_SMF_EXT.1.1 #26 |
|
V-254743
|
Medium |
Google Android 13 must be configured to disable trust agents. |
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... |
|
V-254742
|
Medium |
Google Android 13 must be configured to not display the following (work profile) notifications when the device is locked: [selection:
a. email notifications
b. calendar appointments
c. contact associated with phone call notification
d. text message notification
e. other application-based notifications
f. all notifications]. |
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... |
|
V-254741
|
Medium |
Google Android 13 allowlist must be configured to not include applications with the following characteristics:
1. Back up mobile device (MD) data to non-DOD cloud servers (including user and application access to cloud backup services);
2. Transmit MD diagnostic data to non-DOD servers;
3. Voice assistant application if available when MD is locked;
4. Voice dialing application if available when MD is locked;
5. Allows synchronization of data or applications between devices associated with user; and
6. Allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs or printers. |
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... |
|
V-254740
|
Medium |
Google Android 13 must be configured to enforce an application installation policy by specifying an application allowlist that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version]. |
The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.
Core application: Any application integrated into the OS by... |
|
V-254739
|
Medium |
Google Android 13 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DOD-approved commercial app repository, MDM server, mobile application store]. |
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 |
|
V-254738
|
Medium |
Google Android 13 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 attempts mitigates this risk. Setting the limit at 10 or less gives authorized users the... |
|
V-254737
|
Medium |
Google Android 13 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 physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be... |
|
V-254736
|
Medium |
Google Android 13 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 device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus... |
|
V-254735
|
Medium |
Google Android 13 must be configured to not allow passwords that include more than four 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 to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and... |
|
V-254734
|
Medium |
Google Android 13 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 permitted, how quickly an adversary can do each attempt, and the size of the password space.... |
|
V-254733
|
Medium |
Google Android 13 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: FMT_SMF_EXT.1.1 #32 |
|
V-254763
|
Low |
Google Android 13 must allow only the Administrator (MDM) to perform the following management function: Disable Phone Hub. |
It may be possible to transfer work profile data on a DOD Android device to an unauthorized ChromeBook if the user has the same Google Account set up on the ChromeBook and in the work profile on the Android device. This may result in the exposure of sensitive DOD data.... |
|
V-254760
|
Low |
Android 13 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 NIAP-certified compliant CC Mode of operation.
CC Mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi... |
|
V-254759
|
Low |
Android 13 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-254751
|
Low |
Google Android 13 must be configured to disable Bluetooth or configured via User Based Enforcement (UBE) to allow Bluetooth for only Headset Profile (HSP), Hands-Free Profile (HFP), and Serial Port Profile (SPP). |
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 |
|
V-254745
|
Low |
Google Android 13 must be configured to display the DOD advisory warning message at startup or each time the user unlocks the device. |
|