Google Android 13 MDFPP 3.3 BYOAD Security Technical Implementation Guide

Overview

VersionDateFinding Count (14)Downloads
12023-09-19CAT I (High): 3CAT II (Medium): 10CAT III (Low): 1
STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
ClassifiedPublicSensitive
I - Mission Critical ClassifiedI - Mission Critical PublicI - Mission Critical Sensitive
II - Mission Support ClassifiedII - Mission Support PublicII - Mission Support Sensitive
III - Administrative ClassifiedIII - Administrative PublicIII - Administrative Sensitive

Findings - MAC II - Mission Support Sensitive

Finding IDSeverityTitleDescription
V-258461
LOWMEDIUMHIGH
The EMM system supporting the Google Android 13 BYOAD must be configured for autonomous monitoring, compliance, and validation to ensure security/configuration settings of mobile devices do not deviate from the approved configuration baseline.DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored fo...
V-258462
LOWMEDIUMHIGH
The EMM system supporting the Google Android 13 BYOAD must be configured to initiate autonomous monitoring, compliance, and validation prior to granting the Google Android 13 BYOAD access to DOD information and IT resources.DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored fo...
V-258463
LOWMEDIUMHIGH
The EMM system supporting the Google Android 13 BYOAD must be configured to detect if the Google Android 13 BYOAD native security controls are disabled.Examples of indicators that the native device native security controls have been disabled include jailbroken or rooted devices. DOD policy requires B...
V-258464
LOWMEDIUMHIGH
The EMM system supporting the Google Android 13 BYOAD must be configured to detect if known malicious applications, blocked, or prohibited applications are installed on the Google Android 13 BYOAD (DOD-managed segment only).DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored fo...
V-258465
LOWMEDIUMHIGH
The EMM detection/monitoring system must use continuous monitoring of enrolled Google Android 13 BYOAD.DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored fo...
V-258466
LOWMEDIUMHIGH
The Google Android 13 BYOAD must be configured to either disable access to DOD data and IT systems and user accounts or wipe the work profile if the EMM system detects native security controls are disabled.Examples of indicators that the native device security controls have been disabled include jailbroken or rooted devices. When a BYOAD is out of compl...
V-258467
LOWMEDIUMHIGH
The Google Android 13 BYOAD must be configured to either disable access to DOD data and IT systems and user accounts or wipe the work profile if the EMM system detects the Google Android 13 BYOAD device has known malicious, blocked, or prohibited applications, or configured to access nonapproved third-party applications stores in the work profile.When a BYOAD is out of compliance, DOD data and apps must be removed to protect against compromise of sensitive DOD information. Reference: DOD polic...
V-258468
LOWMEDIUMHIGH
The Google Android 13 BYOAD must be configured so that the work profile is removed if the device is no longer receiving security or software updates.When a BYOAD is out of compliance, DOD data and apps must be removed to protect against compromise of sensitive DOD information. Reference: DOD polic...
V-258472
LOWMEDIUMHIGH
The DOD Mobile Service Provider must not allow Google Android 13 BYOADs in facilities where personally owned mobile devices are prohibited.DOD policy requires BYOAD devices with DOD data be managed by a DOD MDM server, MAM server, or VMI system. This ensures the device can be monitored fo...
V-258473
LOWMEDIUMHIGH
The Google Android 13 BYOAD must be configured to disable device cameras and/or microphones when brought into DOD facilities where mobile phone cameras and/or microphones are prohibited.In some DOD operational environments, the use of the mobile device camera or microphone could lead to a security incident or compromise of DOD informa...
V-258471
LOWMEDIUMHIGH
The User Agreement must include a description of what personal data and information is being monitored, collected, or managed by the EMM system or deployed agents or tools.DOD policy states BYOAD owners must sign a user agreement and be made aware of what personal data and activities will be monitored by the Enterprise b...
V-258469
LOWMEDIUMHIGH
The Google Android 13 BYOAD and DOD enterprise must be configured to limit access to only AO-approved, corporate-owned enterprise IT resources.Note: IT resources includes DOD networks and applications (for example, DOD email). The System Administrator must have the capability to limit access...
V-258470
LOWMEDIUMHIGH
The EMM system supporting the Google Android 13 BYOAD must be NIAP validated (included on the NIAP list of compliant products or products in evaluation) unless the DOD CIO has granted an Approved Exception to Policy (E2P).Note: For a VMI solution, both the client and server must be NIAP compliant. Nonapproved EMM systems may not include sufficient controls to protect w...
V-258474
LOWMEDIUMHIGH
The mobile device used for BYOAD must be NIAP validated.Nonapproved mobile devices may not include sufficient controls to protect work data, applications, and networks from malware or adversary attack. Com...