| V-254764 | | 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 abil... |
| V-254765 | | 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 ... |
| V-254766 | | 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 s... |
| V-254767 | | 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 adversarie... |
| V-254768 | | 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 wi... |
| V-254769 | | 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 ... |
| V-254770 | | 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 insta... |
| V-254771 | | 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 p... |
| V-254772 | | 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) tha... |
| V-254773 | | 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 freque... |
| V-254774 | | 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 B... |
| V-254775 | | 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 vul... |
| V-254777 | | 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... |
| V-254778 | | 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 i... |
| V-254779 | | 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 u... |
| V-254780 | | 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... |
| V-254781 | | Google Android 13 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 ri... |
| V-254782 | | 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 mu... |
| V-254784 | | 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... |
| V-254785 | | 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 (UB... |
| V-254786 | | 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 wireles... |
| V-254787 | | 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 intermed... |
| V-254788 | | The Google Android 13 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 unautho... |
| V-254789 | | 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 ... |
| V-254790 | | Google Android 13 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-254791 | | The Google Android 13 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 ... |
| V-254792 | | The Google Android 13 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 (PI... |
| V-254793 | | 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 syste... |
| V-254797 | | 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... |
| V-254798 | | 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 t... |
| V-254776 | | Google Android 13 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 th... |
| V-254783 | | 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 p... |
| V-254795 | | 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-254796 | | 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 d... |
| V-254799 | | 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 ... |
| V-254794 | | 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... |
