Checklist Summary:

The Google Android 14 Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Google Android devices running Android 14 that process, store, or transmit unclassified data marked as Controlled Unclassified Information (CUI) or below. The STIG is based on the Protection Profile for Mobile Device Fundamentals (MDFPP) version 3.3 STIG template. Requirements compliance is achieved by leveraging a combination of configuration profiles, user-based enforcement (UBE), and reporting. The scope of this STIG covers Corporate Owned Personally Enabled (COPE)1 and Corporate Owned Business Only (COBO)2 use cases. The Bring Your Own Approved Devices (BYOAD)3 use case is not included. This STIG assumes that for the COPE use case, the technology used for data separation between work apps, data and personal apps, and data that has been certified by the National Information Assurance Partnership (NIAP) is compliant with the data separation requirements of the MDFPP4. As of the publication date of this STIG, the only data separation technology or application that is NIAP-certified for a Google Android 14 device is the native Android Enterprise work profile technology. The configuration requirements and controls implemented by this STIG allow unrestricted user activity in downloading and installing personal (unmanaged) apps and data (music, photos, etc.) with Authorizing Official (AO) approval and within any restrictions imposed by the AO. Refer to the STIG Supplemental document, Section 6.2, Configuration of Personal Space, for more information. Zero-touch enrollment enables large-scale Android deployments across multiple device makers so organizations can mobilize their employees with ease. Zero-touch enrollment allows DOD mobile service providers to deploy corporate-owned devices (COBO and COPE) in bulk without having to set up each device manually. It is recommended that DOD mobile service providers consider deploying all Google Android devices via the zero-touch enrollment service to improve enterprise management, control, and enrollment of DOD-owned Google Android 14 phones and tablets. Refer to the STIG Supplemental document, Section 3.3.1, COPE Deployments and User Privacy, for more information. Note: If the AO has approved the use/storage of DOD data in one or more personal apps, allowing unrestricted user activity in downloading and installing personal apps on the Google Android 14 device may not be warranted due to the risk of possible loss of, or unauthorized access to, DOD data. 1 Work profile for mixed-used company-owned devices. 2 Full management for work-only company-owned devices. 3 Also called Choose Your Own Device (CYOD). 4 The primary Protection Profile requirement is FDP_ACF_EXT.1.2. This STIG assumes that if a DOD Wi-Fi network allows a Google Android 14 device to connect to the network, the Wi-Fi network complies with the Network Infrastructure STIG; for example, wireless access points and bridges must not be connected directly to the enclave network.

Checklist Role:

• Operating System

Known Issues:

Not provided.

Target Audience:

Parties within the DOD and federal government’s computing environments can obtain the applicable STIG from the DOD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DOD Certificates can obtain the STIG from https://public.cyber.mil/.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

This document is provided under the authority of DODI 8500.01.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DOD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level due to the fact that some settings may not be configurable in environments outside the DOD architecture.

Product Support:

Not provided.

Point of Contact:

Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

NEW checklist - 10/16/23
updated to final - 11/13/2023

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 11/13/2023