Google Android 12 STIG Ver 1, Rel 1 Checklist Details (Checklist Revisions)
NOTE
This is not the current revision of this Checklist, view the current revision.
Supporting Resources:
-
Download Standalone XCCDF 1.1.4 - Google Android 12
- Defense Information Systems Agency
Target:
Target | CPE Name |
---|---|
Google Android 12 | cpe:/o:google:android:12.0 (View CVEs) |
Checklist Highlights
- Checklist Name:
- Google Android 12 STIG
- Checklist ID:
- 1008
- Version:
- Ver 1, Rel 1
- Type:
- Compliance
- Review Status:
- Candidate
- Authority:
- Governmental Authority: Defense Information Systems Agency
- Original Publication Date:
- 10/29/2021
Checklist Summary:
The Google Android 12 Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Google Android devices running Android 12 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.2 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) and Corporate Owned Business Only (COBO)1 use cases. This STIG assumes that for the COPE use cases, 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 MDFPP2. As of the publication date of this STIG, the only data separation technology or application that is NIAP-certified for a Google Android 12 device is the native Android Enterprise work profile technology. The configuration requirements and controls implemented by this STIG allow unrestricted activity by the user 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. See 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 manually set up each device. 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 12 phones and tablets (see Section 2.9.2 in the Supplemental document).
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 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:
Not provided.
Product Support:
Not provided.
Point of Contact:
disa.stig_spt@mail.mil
Sponsor:
Not provided.
Licensing:
Not provided.
Change History:
null
Dependency/Requirements:
URL | Description |
---|
References:
Reference URL | Description |
---|
NIST checklist record last modified on 10/29/2021
* This checklist is still undergoing review for inclusion into the NCP.