Checklist Summary:

The Google Android 17 Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Google Android devices running Android 17 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 4.0 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) 0F1 and Corporate Owned Business Only (COBO) F2 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 and personal apps and data has been certified by the National Information Assurance Partnership (NIAP) and 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 17 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 7.2, Configuration of the 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 DoW 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 DoW mobile service providers consider deploying all Google Android devices via the Zero-Touch enrollment service to improve enterprise management, control, and enrollment of DoW-owned Google Android 17 phones and tablets. Refer to the STIG Supplemental document, Section 4.3.1, COPE Deployments and User Privacy, for more information. Note: If the AO has approved the use/storage of DoW data in one or more personal apps, allowing unrestricted user activity in downloading and installing personal apps on the Google Android 17 device may not be warranted due to the risk of possible loss of, or unauthorized access to, DoW data. This STIG assumes that if a DoW Wi-Fi network allows a Google Android 17 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 DoW and federal government’s computing environments can obtain the applicable STIG from the DoW 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 DoW 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:

Department of Defense Instruction (DODI) 8500.01

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

Not provided.

Product Support:

Comments or proposed revisions to this document should be sent via email to the following address: [email protected]. DISA will coordinate all change requests with the relevant DoW organizations before inclusion in this document. Approved changes will be made in accordance with the DISA maintenance release schedule.

Point of Contact:

[email protected]

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 07/17/2026