Search filters the loaded procedure list locally. Separate terms must all match (use quotes for an exact phrase). Cached STIG Search results apply when you arrive from Search.
Objective ID
Severity
Discussion
V-276748
medium
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. For the audit logs to be useful, administrators must have the ability to view them.
SFR ID: FMT_SMF.1.1 #32
SFR ID: FMT_SMF.1.1 #32
V-276749
medium
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 function of how many attempts an adversary is permitted, how quickly an adversary can perform each attempt, and the size of the password space. The longer the minimum length of the password, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting in device and data compromise.
SFR ID: FMT_SMF.1.1 #1
SFR ID: FMT_SMF.1.1 #1
V-276750
medium
Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk.
SFR ID: FMT_SMF.1.1 #1
SFR ID: FMT_SMF.1.1 #1
V-276751
medium
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 window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device.
SFR ID: FMT_SMF.1.1 #2
SFR ID: FMT_SMF.1.1 #2
V-276752
medium
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 the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or fewer gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password.
SFR ID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5
SFR ID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5
V-276753
medium
Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DOD data accessible by these unauthorized/malicious applications.
SFR ID: FMT_SMF.1.1 #8
SFR ID: FMT_SMF.1.1 #8
V-276754
medium
The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the mobile device (MD) must provide an alternate method of restricting user access/execution to core and preinstalled applications.
Core application: Any application integrated into the operating system (OS) by the OS or MD vendors.
Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications.
The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core applications (included in the OS by the OS vendor) and preinstalled applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.
SFR ID: FMT_SMF.1.1 #8
Core application: Any application integrated into the operating system (OS) by the OS or MD vendors.
Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications.
The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core applications (included in the OS by the OS vendor) and preinstalled applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.
SFR ID: FMT_SMF.1.1 #8
V-276755
medium
Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DOD data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DOD data or have features with no known application in the DOD environment.
Application note: The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.
Core application: Any application integrated into the operating system (OS) by the OS or MD vendors.
Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
SFR ID: FMT_SMF.1.1 #8
Application note: The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.
Core application: Any application integrated into the operating system (OS) by the OS or MD vendors.
Preinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
SFR ID: FMT_SMF.1.1 #8
V-276756
medium
Sensitive DOD data could be exposed when an AI app processes device data in the cloud.
SFR ID: FMT_SMF.1.1 #8
SFR ID: FMT_SMF.1.1 #8
V-276757
medium
Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the mobile operating system not to send notifications to the lock screen mitigates this risk.
SFR ID: FMT_SMF.1.1 #18
SFR ID: FMT_SMF.1.1 #18
V-276758
medium
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 Bluetooth device or in a user-selected location. This technology would allow unauthorized users to have access to DOD sensitive data if compromised. By not permitting the use of nonpassword authentication mechanisms, users are forced to use passcodes that meet DOD passcode requirements.
SFR ID: FMT_SMF.1.1 #22, FIA_UAU.5.1
SFR ID: FMT_SMF.1.1 #22, FIA_UAU.5.1
V-276759
medium
Developer modes expose features of the mobile operating system that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DOD sensitive information. Disabling developer modes mitigates this risk.
SFR ID: FMT_SMF.1.1 #26
SFR ID: FMT_SMF.1.1 #26
V-276760
low
Before granting access to the system, the mobile operating system is required to display the DOD-approved system use notification message or banner that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Required banners help ensure that DOD can audit and monitor the activities of mobile device users without legal restriction.
System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a "click-through" banner at device unlock (to the extent permitted by the operating system). A "click-through" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating "OK."
The approved DOD text must be used exactly as required in the Knowledge Service referenced in DODI 8500.01. For devices accommodating banners of 1300 characters, the banner text is:
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
For devices with severe character limitations, the banner text is:
I've read & consent to terms in IS user agreem't.
The administrator must configure the banner text exactly as written without any changes.
SFR ID: FMT_SMF.1.1 #36
System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a "click-through" banner at device unlock (to the extent permitted by the operating system). A "click-through" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating "OK."
The approved DOD text must be used exactly as required in the Knowledge Service referenced in DODI 8500.01. For devices accommodating banners of 1300 characters, the banner text is:
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.
For devices with severe character limitations, the banner text is:
I've read & consent to terms in IS user agreem't.
The administrator must configure the banner text exactly as written without any changes.
SFR ID: FMT_SMF.1.1 #36
V-276761
medium
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Rule Title lists key events for which the system must generate an audit record.
Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component.
SFR ID: FMT_SMF.1.1 #37
Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component.
SFR ID: FMT_SMF.1.1 #37
V-276762
medium
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 is enabled on a mobile device, it becomes a potential vector for malware and unauthorized data exfiltration. Prohibiting USB mass storage mode mitigates this risk.
SFR ID: FMT_SMF.1.1 #39
SFR ID: FMT_SMF.1.1 #39
V-276763
medium
Data on mobile devices is protected by numerous mechanisms, including user authentication, access control, and cryptography. When the data is backed up to an external system (either locally connected or cloud based), many if not all of these mechanisms are no longer present. This leaves the backed-up data vulnerable to attack. Disabling backup to external systems mitigates this risk.
SFR ID: FMT_SMF.1.1 #40
SFR ID: FMT_SMF.1.1 #40
V-276764
medium
Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system. Where the remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this case, DOD devices may synchronize DOD sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk.
SFR ID: FMT_SMF.1.1 #40
SFR ID: FMT_SMF.1.1 #40
V-276765
medium
If no authentication is required to establish personal hotspot connections (Wi-Fi and Bluetooth), an adversary may be able to use that device to perform attacks on other devices or networks without detection. A sophisticated adversary may also be able to exploit unknown system vulnerabilities to access information and computing resources on the device. Requiring authentication to establish personal hotspot connections mitigates this risk.
Application note: If hotspot functionality is permitted, it must be authenticated via a preshared key. There is no requirement to enable hotspot functionality, and it is recommended this functionality be disabled by default.
SFR ID: FMT_SMF.1.1 #41
Application note: If hotspot functionality is permitted, it must be authenticated via a preshared key. There is no requirement to enable hotspot functionality, and it is recommended this functionality be disabled by default.
SFR ID: FMT_SMF.1.1 #41
V-276766
medium
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 multiuser mode features meets DOD requirements for access control, data separation, and nonrepudiation for user accounts. In addition, the MDFPP does not include design requirements for multiuser account services. Disabling multiuser mode mitigates the risk of not meeting DOD multiuser account security policies.
SFR ID: FMT_SMF.1.1 #47a
SFR ID: FMT_SMF.1.1 #47a
V-276767
low
Some Bluetooth profiles provide the capability for remote transfer of sensitive DOD data without encryption or otherwise do not meet DOD IT security policies and therefore must be disabled.
SFR ID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8
SFR ID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8
V-276768
medium
Ad hoc wireless client-to-client connections allow mobile devices to communicate with each other directly, circumventing network security policies and making the traffic invisible. This could allow the exposure of sensitive DOD data and increase the risk of downloading and installing malware on the DOD mobile device.
SFR ID: FMT_SMF_EXT.1.1/WLAN
SFR ID: FMT_SMF_EXT.1.1/WLAN
V-276769
medium
The security posture of Google devices requires the device user to configure several required policy rules on their device. User-Based Enforcement (UBE) is required for these controls. In addition, if the authorizing official (AO) has approved the use of an unmanaged personal space, the user must receive training on risks. If a user is not aware of their responsibilities and does not comply with UBE requirements, the security posture of the Google mobile device may become compromised, and DOD sensitive data may become compromised.
SFR ID: NA
SFR ID: NA
V-276770
medium
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 wirelessly connected devices instead of its mobile (cellular) connection.
Wi-Fi Sharing grants the other device access to a corporate Wi-Fi network and may possibly bypass the network access control mechanisms. This risk can be partially mitigated by requiring the use of a preshared key for personal hotspots.
SFR ID: FMT_SMF_EXT.1.1 / WLAN #3
Wi-Fi Sharing grants the other device access to a corporate Wi-Fi network and may possibly bypass the network access control mechanisms. This risk can be partially mitigated by requiring the use of a preshared key for personal hotspots.
SFR ID: FMT_SMF_EXT.1.1 / WLAN #3
V-276771
medium
Wi-Fi and Bluetooth hotspot use may increase the risk for exposing sensitive DOD data for some use cases; therefore, it should be disabled unless approved by the AO. When a DOD mobile phone is used as a Wi-Fi or Bluetooth hotspot, a hotspot password must be enabled; otherwise, unauthorized devices could connect to the DOD hotspot, which may increase the risk of exposure of sensitive DOD data and/or a performance degradation of the DOD mobile phone.
SFR ID: FMT_SMF_EXT.1.1 / WLAN #3
SFR ID: FMT_SMF_EXT.1.1 / WLAN #3
V-276772
medium
DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the DOD root and intermediate PKI certificates greatly diminishes the risk of this attack.
SFR ID: FMT_SMF.1.1 #11
SFR ID: FMT_SMF.1.1 #11
V-276773
medium
The system application disable list controls user access to/execution of all core and preinstalled applications.
Core application: Any application integrated into Google Android 16 by Google.
Preinstalled application: Additional noncore applications included in the Google Android 16 build by Google or the wireless carrier.
Some system applications can compromise DOD data or upload users' information to non-DOD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DOD data or DOD user information.
The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DOD use by configuring the system application disable list.
SFR ID: FMT_SMF.1.1 #47
Core application: Any application integrated into Google Android 16 by Google.
Preinstalled application: Additional noncore applications included in the Google Android 16 build by Google or the wireless carrier.
Some system applications can compromise DOD data or upload users' information to non-DOD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DOD data or DOD user information.
The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DOD use by configuring the system application disable list.
SFR ID: FMT_SMF.1.1 #47
V-276774
medium
The autofill functionality in the web browser allows the user to complete a form that contains sensitive information, such as personally identifiable information, without previous knowledge of the information. By allowing the use of autofill functionality, an adversary who learns a user's Android 16 device password, or who otherwise is able to unlock the device, may be able to breach other systems by relying on the autofill feature to provide information unknown to the adversary. By disabling the autofill functionality, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated.
SFR ID: FMT_SMF.1.1 #47
SFR ID: FMT_SMF.1.1 #47
V-276775
high
Wi-Fi Aware allows direct connections between nearby devices for fast data transfer, video streaming, and multiplayer gaming. It allows full peer-to-peer device discovery and communication where two or more devices are publishing and/or subscribing to the same known service name. There is risk that sensitive DOD information could be transferred from a DOD mobile device to a non-DOD device or from Work Profile apps on a DOD device to Personal Profile apps on a non-DOD device.
V-276776
high
Authorizing official (AO) approval is required before the Google device Bluetooth radio can be enabled. All AO approvals must be documented and based on critical mission need. Use of Bluetooth may lead to the exposure of sensitive DOD information in some operational environments.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276777
high
Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions.
SFR ID: FMT_SMF.1.1 #47
SFR ID: FMT_SMF.1.1 #47
V-276778
low
Many third-party keyboard applications are known to contain malware.
SFR ID: FMT_SMF.1.1 #47
SFR ID: FMT_SMF.1.1 #47
V-276779
low
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 device will not be operating in the NIAP-certified compliant CC Mode of operation.
CC Mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi keys are stored using different types of encryption.
SFR ID: FMT_SMF.1.1 #47
CC Mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi keys are stored using different types of encryption.
SFR ID: FMT_SMF.1.1 #47
V-276780
medium
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 information systems. An adversary could exploit vulnerabilities created by the weaker configuration to compromise DOD sensitive information.
SFR ID: FMT_MOF_EXT.1.2 #24
SFR ID: FMT_MOF_EXT.1.2 #24
V-276781
medium
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 to remove root and intermediate certificates, the user could allow an adversary to falsely sign a certificate in such a way that it could not be detected. Restricting the ability to remove DOD root and intermediate PKI certificates to the administrator mitigates this risk.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276782
low
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 on the Chromebook and in the work profile on the Android device. This may result in the exposure of sensitive DOD data.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276783
high
Private Space is an Android feature that provides a separate encrypted container on the mobile device. Apps in Private Space show up in a separate container in the launcher and are hidden from the "Recents" view, notifications, settings, and other apps when the private space is locked. In addition, an MDM server allowlist or blocklist cannot control the installation of apps into Private Space. Malware and other unauthorized apps could be installed on a DOD mobile device, which could lead to the compromise of DOD sensitive information or to an attack on the DOD network.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276784
medium
This feature must be disabled to comply with DOD electronic records retention requirements for mobile devices. Otherwise, mobile device users could wipe the device, which would violate DOD policy.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276785
low
The use of assistants could expose sensitive DOD data to cloud-based servers during the processing of assistant requests.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276786
low
Wireless printing allows the printing of sensitive DOD documents to non-DOD controlled printers, which may lead to the exposure of sensitive DOD information.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276787
low
The screen capture feature could lead to the exposure of sensitive DOD information.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276788
medium
DOD mobile devices are in constant risk of cyber threats. MTD apps mitigate these risks by providing real-time threat detection, malware prevention, and vulnerability analysis.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47
V-276789
medium
Authorizing official (AO) approval is required before the mobile device camera can be enabled for a specific user or group of users, based on a risk assessment of the operational environment. Camera use may lead to the exposure of sensitive DOD information in some operational environments.
SFR ID: FMT_MOF_EXT.1.2 #47
SFR ID: FMT_MOF_EXT.1.2 #47