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-255167
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 do 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 device and data compromise.
SFR ID: FMT_SMF_EXT.1.1 #1a
SFR ID: FMT_SMF_EXT.1.1 #1a
V-255168
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. The numeric (complex) setting allows the use of a numeric only keyboard for passwords plus enforces the repeating or sequential characters limitation.
SFR ID: FMT_SMF_EXT.1.1 #1b
SFR ID: FMT_SMF_EXT.1.1 #1b
V-255169
medium
The screen-lock timeout helps protect the device from unauthorized access. Devices without a screen-lock timeout provide an 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 and possibly access to DOD networks.
SFR ID: FMT_SMF_EXT.1.1 #2a
SFR ID: FMT_SMF_EXT.1.1 #2a
V-255170
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_EXT.1.1 #2b
SFR ID: FMT_SMF_EXT.1.1 #2b
V-255171
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 less 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_EXT.1.1 #2c, FIA_AFL_EXT.1.5
SFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5
V-255172
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_EXT.1.1 #8a
SFR ID: FMT_SMF_EXT.1.1 #8a
V-255173
medium
The application allow list, 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 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 allow list prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allow list. Failure to configure an application allow list 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 allow list, 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_EXT.1.1 #8b
Core application: Any application integrated into the 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 allow list prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allow list. Failure to configure an application allow list 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 allow list, 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_EXT.1.1 #8b
V-255174
medium
Requiring all authorized applications to be in an application allow list prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allow list. Failure to configure an application allow list 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 allow list, 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 OS by the OS or MD vendors.
Preinstalled application: Additional non-core applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
SFR ID: FMT_SMF_EXT.1.1 #8b
Application note: The application allow list, 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 OS by the OS or MD vendors.
Preinstalled application: Additional non-core applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.
SFR ID: FMT_SMF_EXT.1.1 #8b
V-255175
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 should be disabled.
SFR ID: FMT_SMF_EXT.1.1 #18h
SFR ID: FMT_SMF_EXT.1.1 #18h
V-255176
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 Microsoft Android device to not send notifications to the lock screen mitigates this risk.
SFR ID: FMT_SMF_EXT.1.1 #19
SFR ID: FMT_SMF_EXT.1.1 #19
V-255177
high
The Microsoft Android device must ensure the data being written to the mobile device's removable media is protected from unauthorized access. If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can read removable media directly, thereby circumventing operating system controls. Encrypting the data ensures confidentiality is protected even when the operating system is not running.
SFR ID: FMT_SMF_EXT.1.1 #21, #47f
SFR ID: FMT_SMF_EXT.1.1 #21, #47f
V-255178
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_EXT.1.1 #23, FIA_UAU.5.1
SFR ID: FMT_SMF_EXT.1.1 #23, FIA_UAU.5.1
V-255179
medium
Developer modes expose features of the Microsoft Android device 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_EXT.1.1 #26
SFR ID: FMT_SMF_EXT.1.1 #26
V-255180
low
The Microsoft Android 11 is required to display the DOD-approved system use notification message or banner before granting access to the system 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 KS 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_EXT.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 KS 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_EXT.1.1 #36
V-255181
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_EXT.1.1 #39a
SFR ID: FMT_SMF_EXT.1.1 #39a
V-255182
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_EXT.1.1 #40
SFR ID: FMT_SMF_EXT.1.1 #40
V-255183
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 Microsoft Android device. 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_EXT.1.1 #40
SFR ID: FMT_SMF_EXT.1.1 #40
V-255184
medium
Multi-user mode allows multiple users to share a mobile device by providing a degree of separation between user data. To date, no mobile device with multi-user mode features meets DOD requirements for access control, data separation, and non-repudiation for user accounts. In addition, the MDFPP does not include design requirements for multi-user account services. Disabling multi-user mode mitigates the risk of not meeting DOD multi-user account security policies.
SFR ID: FMT_SMF_EXT.1.1 #47b
SFR ID: FMT_SMF_EXT.1.1 #47b
V-255185
low
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 #22
SFR ID: FMT_MOF_EXT.1.2 #22
V-255186
medium
When a user's device is lost or stolen, it is useful to remotely wipe it as soon as possible to avoid loss of DOD sensitive information. The Administrator must have the capability to force a wipe on a lost or stolen device to reduce the risk of compromise of sensitive DOD data. This capability mitigates that risk.
SFR ID: FMT_SMF_EXT.1.1 #28
SFR ID: FMT_SMF_EXT.1.1 #28
V-255187
medium
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. To be useful, Administrators must have the ability to view the audit logs.
SFR ID: FMT_SMF_EXT.1.1 #32
SFR ID: FMT_SMF_EXT.1.1 #32
V-255188
medium
Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can either be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Requirement Statement lists key events that the system must generate an audit record for.
Application note: Requirement applies only to integrity violation detections that can be logged by the audit logging component.
SFR ID: FMT_SMF_EXT.1.1 #37
Application note: Requirement applies only to integrity violation detections that can be logged by the audit logging component.
SFR ID: FMT_SMF_EXT.1.1 #37
V-255189
medium
The security posture of Android 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 mobile device may become compromised and DOD sensitive data may become compromised.
SFR ID: NA
SFR ID: NA
V-255190
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 #47
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 #47
V-255191
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_EXT.1.1 #47
SFR ID: FMT_SMF_EXT.1.1 #47
V-255192
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-255193
medium
If the user is able to add a personal email account (POP3, IMAP, EAS) to the work email app, it could be used to forward sensitive DOD data to unauthorized recipients. Restricting email account addition to the administrator or restricting email account addition to allow listed accounts mitigates this vulnerability.
SFR ID: FMT_SMF_EXT.1.1 #47
SFR ID: FMT_SMF_EXT.1.1 #47
V-255194
medium
The system application disable list controls user access to/execution of all core and preinstalled applications.
Core application: Any application integrated into Microsoft Android 11 by Google.
Preinstalled application: Additional noncore applications included in the Microsoft Android 11 build by Google, Microsoft, 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_EXT.1.1 #47
Core application: Any application integrated into Microsoft Android 11 by Google.
Preinstalled application: Additional noncore applications included in the Microsoft Android 11 build by Google, Microsoft, 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_EXT.1.1 #47
V-255195
medium
The autofill functionality in the web browser allows the user to complete a form that contains sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill functionality, an adversary who learns a user's Microsoft Android 11 device password, or who otherwise is able to unlock the device, may be able to further 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_EXT.1.1 #47
SFR ID: FMT_SMF_EXT.1.1 #47
V-255196
medium
The autofill services allow the user to complete text inputs that could contain sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill services, an adversary who learns a user's Microsoft Android 11 device password, or who otherwise is able to unlock the device, may be able to further breach other systems by relying on the autofill services to provide information unknown to the adversary. By disabling the autofill services, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated.
Examples of apps that offer autofill services include Samsung Pass, Google, Dashlane, LastPass, and 1Password.
SFR ID: FMT_SMF_EXT.1.1 #47
Examples of apps that offer autofill services include Samsung Pass, Google, Dashlane, LastPass, and 1Password.
SFR ID: FMT_SMF_EXT.1.1 #47
V-255197
medium
Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events.
Periodically synchronizing internal clocks with an authoritative time source is necessary to correctly correlate the timing of events that occur across the enterprise. The three authoritative time sources for Microsoft Android 11 are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DOD network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier.
Time stamps generated by the audit system in Microsoft Android 11 must include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
SFR ID: FMT_SMF_EXT.1.1 #47
Periodically synchronizing internal clocks with an authoritative time source is necessary to correctly correlate the timing of events that occur across the enterprise. The three authoritative time sources for Microsoft Android 11 are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DOD network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier.
Time stamps generated by the audit system in Microsoft Android 11 must include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
SFR ID: FMT_SMF_EXT.1.1 #47
V-255198
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_EXT.1.1 #47
SFR ID: FMT_SMF_EXT.1.1 #47
V-255199
low
Many third-party keyboard applications are known to contain malware.
SFR ID: FMT_SMF_EXT.1.1 #47
SFR ID: FMT_SMF_EXT.1.1 #47
V-255200
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_EXT.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_EXT.1.1 #47
V-264373
high
Microsoft Android 11 is no longer supported by Google and therefore, may contain security vulnerabilities.
Satisfies: FMT_MOF_EXT.1.2 #47
Reference: PP-MDF-991000
Satisfies: FMT_MOF_EXT.1.2 #47
Reference: PP-MDF-991000