{
"stig": {
"date": "2019-12-18",
"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.",
"findings": {
"V-98921": {
"checkid": "C-97757r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device is enforcing a minimum password length of six characters.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console:\n1. Open password requirements.\n2. Open device password section.\n3. Ensure the minimum password length is set to 6 characters.\n\nOn the Android 10 device, do the following:\n\n1. Open Settings >> Security >> Screen lock.\n2. Enter current password.\n3. Tap \"Password\".\n4. Verify Password length listed is at least 6.\n\nIf the device password length is not set to six characters or more on MDM console or on the Android 10 device, this is a finding.",
"description": "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 is, 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #1a",
"fixid": "F-104597r1_fix",
"fixtext": "Configure the Google Android device to enforce a minimum password length of six characters.\n\nOn the MDM console:\n1. Open password requirements.\n2. Open device password section.\n3. Enter in the number of characters as \"6\".",
"iacontrols": null,
"id": "V-98921",
"ruleID": "SV-108025r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enforce a minimum password length of six characters.",
"version": "GOOG-10-000100"
},
"V-98923": {
"checkid": "C-97759r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device is prohibiting passwords with more than two repeating or sequential characters.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\nOn the MDM console:\n1. Open password requirements.\n2. Open device password section.\n3. Ensure the password quality is set to \"Numeric (Complex)\".\n\nOn the Android 10 device, do the following:\n\n1. Open Settings >> Security >> Screen lock.\n2. Enter current password.\n3. Tap \"Password\".\n4. Verify Password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed.\n\nIf the MDM console device policy is set to a password with more than two repeating or sequential characters or on the Android 10 device, the device policy is set to a password with more than two repeating or sequential characters, this is a finding.\n\nNote: Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #1b",
"fixid": "F-104599r1_fix",
"fixtext": "Configure the Google Android device to prevent passwords from containing more than two repeating or sequential characters.\n\nOn the MDM console:\n1. Open password requirements.\n2. Open device password section.\n3. Set password quality to \"Numeric (Complex)\".\n\nNote: Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.",
"iacontrols": null,
"id": "V-98923",
"ruleID": "SV-108027r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to not allow passwords that include more than two repeating or sequential characters.",
"version": "GOOG-10-000200"
},
"V-98925": {
"checkid": "C-97761r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device is enforcing a screen-lock policy that will lock the display after a period of inactivity.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n1. Open password requirements.\n2. Open device password section.\n3. Ensure \"Max time to screen lock\" is set to any number desired. Units are in Seconds.\n\nOn the Android 10 device, do the following:\n1. Open Settings >> Display.\n2. Tap \"Screen timeout\".\n3. Ensure the Screen timeout value is set to the desired value and cannot be set to a larger value.\n\nIf the MDM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity or on the Android 10 device, the device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #2a",
"fixid": "F-104601r1_fix",
"fixtext": "Configure the Google Android device to enable a screen-lock policy that will lock the display after a period of inactivity.\n\nOn the MDM Console:\n1. Open password requirements.\n2. Open device password section.\n3. Set \"Max time to screen lock\" to any number desired. Units are in Seconds.",
"iacontrols": null,
"id": "V-98925",
"ruleID": "SV-108029r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enable a screen-lock policy that will lock the display after a period of inactivity.",
"version": "GOOG-10-000300"
},
"V-98927": {
"checkid": "C-97763r2_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has the screen lock timeout set to 15 minutes or less.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open passcode requirement\n2. Open device passcode section.\n3. Ensure \"Max time to screen lock\" is set to any number between 1 and 15.\n\nOn the Android 10 device, do the following:\n1. Open settings >> Security.\n2. Tap on \"Screen timeout\".\n3. Ensure the Screen timeout value is set to between 0 and 15 minutes.\n\nIf the MDM console device policy is not set to 15 minutes or less for the screen lock timeout or on the Android 10 device, the device policy is not set to 15 minutes or less for the screen lock timeout, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #2b",
"fixid": "F-104603r1_fix",
"fixtext": "Configure the Google Android device to lock the device display after 15 minutes (or less) of inactivity.\n\nOn the MDM Console:\n1. Open password requirements.\n2. Open device password section.\n3. Set \"Max time to screen lock\" to any number between 1 and 15.",
"iacontrols": null,
"id": "V-98927",
"ruleID": "SV-108031r2_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to lock the display after 15 minutes (or less) of inactivity.",
"version": "GOOG-10-000400"
},
"V-98929": {
"checkid": "C-97765r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has the maximum number of consecutive failed authentication attempts set at 10 or fewer. \n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \nOn the MDM console, do the following:\n\n1. Open password requirements.\n2. Open device password section.\n3. Review the policy configuration that was pushed down to the device and ensure the \"Max password failures for local wipe\" is set between 1 and 10.\n\nOn the Android 10 device, do the following:\n1. Open Setting >> Security >> Managed device info. \n2. Verify \"Failed password attempts before deleting all device data\" is set to 10 or fewer attempts.\n\nIf the MDM console device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, or if on the Android 10 device the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5",
"fixid": "F-104605r1_fix",
"fixtext": "Configure the Google Android device to allow only 10 or fewer consecutive failed authentication attempts.\n\nOn the MDM Console:\n1. Open password requirements.\n2. Open device password section.\n3. Set \"Max password failures for local wipe\" to a number between 1 and 10.",
"iacontrols": null,
"id": "V-98929",
"ruleID": "SV-108033r1_rule",
"severity": "low",
"title": "Google Android 10 must be configured to not allow more than 10 consecutive failed authentication attempts.",
"version": "GOOG-10-000500"
},
"V-98931": {
"checkid": "C-97767r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has only approved application repositories (DoD-approved commercial app repository, MDM server, and/or mobile application store).\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n1. Open Restrictions Section.\n2 Toggle \"Disallow installs from unknown sources globally\" to on.\n\nOn the Google device, do the following:\n1. Open Settings >> Apps and notifications >> Advanced >> Special app access.\n2. Open Install unknown apps.\n3. Ensure the list of apps is blank or if an app is on the list, \"Disabled by admin\" is listed under the app name.\n\nIf the MDM console device policy is not set to allow connections to only approved application repositories or on the Android 10 device, the device policy is not set to allow connections to only approved application repositories, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #8a",
"fixid": "F-104607r1_fix",
"fixtext": "Configure the Google Android device to disable unauthorized application repositories.\n\nOn the MDM Console:\n1. Open Restrictions section.\n2 Toggle \"Disallow installs from unknown sources globally\" to on.",
"iacontrols": null,
"id": "V-98931",
"ruleID": "SV-108035r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: DoD-approved commercial app repository, MDM server, mobile application store].",
"version": "GOOG-10-000800"
},
"V-98933": {
"checkid": "C-97769r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has an application whitelist configured. Verify all applications listed on the whitelist have been approved by the Approving Official (AO).\n\nThis validation procedure is performed only on the MDM Administration Console.\n\nOn the MDM console, do the following:\n1. Go to the Android app catalog for managed Google Play.\n2. Verify all selected apps are AO approved.\n\nNOTE: Managed Google Play is always a Whitelisted App Store.\n\nIf on the MDM console the list of selected Managed Google Play apps included non-approved apps, this is a finding.\n\nNote: The application whitelist will include approved core applications (included in the OS by the OS vendor) and pre-installed 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 pre-installed applications. For Google Android, there are no pre-installed applications.",
"description": "The application whitelist, 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 pre-installed applications. \n\nCore application: Any application integrated into the OS by the OS or MD vendors.\n\nPre-installed application: Additional non-core applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.\n\nRequiring all authorized applications to be in an application whitelist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the whitelist. Failure to configure an application whitelist 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.\n\nThe application whitelist, 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 pre-installed 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 pre-installed applications.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b",
"fixid": "F-104609r1_fix",
"fixtext": "Configure the Google Android device to use an application whitelist.\n\nOn the MDM Console:\n1. Go to the Android app catalog for managed Google Play.\n2. Select apps to be available (only approved apps).\n3. Push updated policy to the device.\n\nNOTE: Managed Google Play is always a Whitelisted App Store.",
"iacontrols": null,
"id": "V-98933",
"ruleID": "SV-108037r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enforce an application installation policy by specifying an application whitelist that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version].",
"version": "GOOG-10-001000"
},
"V-98935": {
"checkid": "C-97771r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has an application whitelist configured and that the application whitelist does not include applications with the following characteristics:\n\n- back up MD data to non-DoD cloud servers (including user and application access to cloud backup services);\n- transmit MD diagnostic data to non-DoD servers;\n- voice assistant application if available when MD is locked;\n- voice dialing application if available when MD is locked;\n- allows synchronization of data or applications between devices associated with user;\n- payment processing; and\n- allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers.\n\nThis validation procedure is performed only on the MDM Administration Console.\n\nOn the MDM console, do the following:\n\n1. Review the list of selected Managed Google Play apps.\n2. Review the details and privacy policy of each selected app to ensure the app does not include prohibited characteristics.\n\nIf the MDM console device policy includes applications with unauthorized characteristics, this is a finding.",
"description": "Requiring all authorized applications to be in an application whitelist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the whitelist. Failure to configure an application whitelist 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.\n\nApplication note: The application whitelist, 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 pre-installed applications.\n\nCore application: Any application integrated into the OS by the OS or MD vendors.\n\nPre-installed application: Additional non-core applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b",
"fixid": "F-104611r1_fix",
"fixtext": "Configure the Google Android device application whitelist to exclude applications with the following characteristics:\n\n- back up MD data to non-DoD cloud servers (including user and application access to cloud backup services);\n- transmit MD diagnostic data to non-DoD servers;\n- voice assistant application if available when MD is locked;\n- voice dialing application if available when MD is locked;\n- allows synchronization of data or applications between devices associated with user;\n- payment processing; and\n- allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs, display screens (screen mirroring), or printers.\n\nOn the MDM Console:\n1. Go to the Android app catalog for managed Google Play.\n2. Before selecting an app, review the app details and privacy policy to ensure the app does not include prohibited characteristics.",
"iacontrols": null,
"id": "V-98935",
"ruleID": "SV-108039r1_rule",
"severity": "medium",
"title": "Google Android 10 whitelist must be configured to not include applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs or printers.",
"version": "GOOG-10-001100"
},
"V-98937": {
"checkid": "C-97773r1_chk",
"checktext": "Determine if the AO has approved the use of Bluetooth at the site.\n\nIf the AO has not approved the use of Bluetooth, verify Bluetooth has been disabled:\nOn the MDM console, do the following:\n\n1. Open restrictions Section.\n2. Ensure \"Disallow Bluetooth\" is set.\n\nOn the Android 10 device, do the following:\n\n1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth.\n2. Ensure that it is set to Off and cannot be toggled to On.\n\nIf the AO has approved the use of Bluetooth, on the Google Android 10 device do the following:\n\n1. Go to Settings >> Connected Devices.\n2. Verify only approved Bluetooth connected devices using approved profiles are listed.\n\nIf the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an MDM managed device policy, this is a finding.\nIf the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under \"Connected devices\", this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #18h",
"fixid": "F-104613r1_fix",
"fixtext": "Configure the Google Android device to disable Bluetooth or if the AO has approved the use of Bluetooth (for example, for car hands-free use), train the user to connect to only authorized Bluetooth devices using only HSP, HFP, or SPP Bluetooth capable devices (User Based Enforcement [UBE]).\n\nTo disable Bluetooth use the following procedure:\nOn the MDM Console:\n1. Open restrictions section.\n2. Toggle \"Disallow Bluetooth\" to on.\n\nThe user training requirement is satisfied in requirement GOOG-10-008700.",
"iacontrols": null,
"id": "V-98937",
"ruleID": "SV-108041r1_rule",
"severity": "low",
"title": "Google Android 10 must be configured to disable Bluetooth or configured via User Based Enforcement (UBE) to allow Bluetooth for only Headset Profile (HSP), HandsFree Profile (HFP), and Serial Port Profile (SPP).",
"version": "GOOG-10-001400"
},
"V-98939": {
"checkid": "C-97775r1_chk",
"checktext": "Review Google Android device settings to determine if the Google Android device displays (work container) notifications on the lock screen. Notifications of incoming phone calls are acceptable even when the device is locked. \n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open restrictions Section.\n2. Open Work Managed Section.\n3. Ensure \"Disable Unredacted Notifications\" is selected.\n\nOn the Android 10 device, do the following:\n\n1. Go to Settings >> Display >> Advanced. \n2. Tap on Lock screen display.\n3. Ensure \"Hide sensitive work content\" is listed under \"When work profile is locked\".\n\nIf the MDM console device policy allows work notifications on the lock screen, or the Android 10 device allows work notifications on the lock screen, this is a finding.",
"description": "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 Google Android device to not send notifications to the lock screen mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #19",
"fixid": "F-104615r1_fix",
"fixtext": "Configure the Google Android device to not display (work profile) notifications when the device is locked.\n\nOn the MDM console:\n\n1. Open restrictions section.\n2. Open Work Managed Section.\n3. Select \"Disable Unredacted Notifications\".",
"iacontrols": null,
"id": "V-98939",
"ruleID": "SV-108043r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to not display the following (work profile) notifications when the device is locked: [selection: - email notifications - calendar appointments - contact associated with phone call notification - text message notification - other application-based notifications - all notifications].",
"version": "GOOG-10-001600"
},
"V-98941": {
"checkid": "C-97781r1_chk",
"checktext": "Review device configuration settings to confirm that trust agents are disabled. \n\nThis procedure is performed on both the MDM Administration console and the Google Android 10 device. \n\nOn the MDM console:\n1. Open restrictions section.\n2. Set \"Disable trust agents\" to on.\n\nOn the Google Android 10 device: \n1. Open Settings. \n2. Tap \"Security\". \n3. Tap \"Advanced\". \n4. Tap \"Trust agents\". \n5. Verify that all listed trust agents are disabled and cannot be enabled. \n\nIf on the MDM console \"disable trust agents\" is not selected, or on the Android 10 device a trust agent can be enabled, this is a finding.",
"description": "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 non-password authentication mechanisms, users are forced to use passcodes that meet DoD passcode requirements.\n\nSFR ID: FMT_SMF_EXT.1.1 #23, FIA_UAU.5.1",
"fixid": "F-104617r1_fix",
"fixtext": "Configure Google Android 10 to disable trust agents. \n\nOn the MDM console:\n1. Open Lock screen restrictions section.\n2. Set \"Disable trust agents\" to on.",
"iacontrols": null,
"id": "V-98941",
"ruleID": "SV-108045r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disable trust agents. Note: This requirement is not applicable (NA) for specific biometric authentication factors included in the products Common Criteria evaluation.",
"version": "GOOG-10-002300"
},
"V-98943": {
"checkid": "C-97783r1_chk",
"checktext": "Review Google Android device configuration settings to determine whether a developer mode is enabled.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open restrictions section.\n2. Open Restrictions section.\n3. Toggle \"Disallow debugging Features\" to on.\n\nOn the Android 10 device, do the following:\n\n1. Go to Settings >> System.\n2. Ensure Developer Options is not listed.\n\nIf the MDM console device policy is not set to disable developer mode or on the Android 10 device, the device policy is not set to disable developer mode, this is a finding.",
"description": "Developer modes expose features of the Google 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #26",
"fixid": "F-104619r1_fix",
"fixtext": "Configure the Google Android device to disable developer modes.\n\nOn the MDM Console:\n1. Open restrictions section.\n2. Open Restrictions section.\n3. Toggle \"Disallow debugging Features\" to on.",
"iacontrols": null,
"id": "V-98943",
"ruleID": "SV-108047r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disable developer modes.",
"version": "GOOG-10-002800"
},
"V-98945": {
"checkid": "C-97785r1_chk",
"checktext": "The DoD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Description):\n\n1. By placing the DoD warning banner text in the user agreement signed by each Google Android device user (preferred method).\n2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device.\n\nDetermine which method is used at the Google Android device site and follow the appropriate validation procedure below.\n\nValidation Procedure for Method #1:\nReview the signed user agreements for several Google Android device users and verify the agreement includes the required DoD warning banner text.\n\nValidation Procedure for Method #2:\nOn the MDM console, do the following:\nEnsure \"Lock Screen Message\" and the appropriate banner text is included.\n\nIf, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the MDM console device policy is not set to display a warning banner with the appropriate designated wording or on the Android 10 device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.",
"description": "The Google Android 10 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.\n\nSystem 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.\"\n\nThe 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: \n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n-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. \n-At any time, the USG may inspect and seize data stored on this IS. \n-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. \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n-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.\n\nFor devices with severe character limitations, the banner text is: \n\nI've read & consent to terms in IS user agreem't.\n\nThe administrator must configure the banner text exactly as written without any changes.\n\nSFR ID: FMT_SMF_EXT.1.1 #36",
"fixid": "F-104621r1_fix",
"fixtext": "Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Description):\n\n1. By placing the DoD warning banner text in the user agreement signed by each Google Android device user (preferred method).\n2. By configuring the warning banner text on the MDM console and installing the banner on each managed mobile device.\n\nOn the MDM Console:\nEnable \"Lock Screen Message\" and enter the banner text.",
"iacontrols": null,
"id": "V-98945",
"ruleID": "SV-108049r1_rule",
"severity": "low",
"title": "Google Android 10 must be configured to display the DoD advisory warning message at start-up or each time the user unlocks the device.",
"version": "GOOG-10-003400"
},
"V-98947": {
"checkid": "C-97787r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device has a USB mass storage mode and whether it has been disabled. \n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open User restrictions.\n2. Open User restrictions.\n3. Ensure \"Disallow usb file transfer\" is selected.\n\nOn the Android 10 device, do the following:\n\n1. Plug a USB cable into Android 10 device and connect to a non-DoD network-managed PC. \n2. Go to Settings >> Connected devices >> USB.\n3. Ensure \u201cNo data transfer\u201d is selected.\n\nIf the MDM console device policy is not set to disable USB mass storage mode or on the Android 10 device, the device policy is not set to disable USB mass storage mode, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #39a",
"fixid": "F-104623r1_fix",
"fixtext": "Configure the Google Android device to disable USB mass storage mode.\n\nOn the MDM console:\n\n1. Open User restrictions.\n2. Open User restrictions.\n3. Select \"Disallow usb file transfer\".",
"iacontrols": null,
"id": "V-98947",
"ruleID": "SV-108051r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disable USB mass storage mode.",
"version": "GOOG-10-003500"
},
"V-98949": {
"checkid": "C-97789r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the capability to back up to a locally connected system has been disabled. \n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open User restrictions.\n2. Select \"Disallow usb file transfer\".\n\nOn the Android 10 device, do the following:\n\n1. Plug a USB cable into Android 10 device and connect to a non-DoD network-managed PC. \n2. Go to Settings >> Connected devices >> USB.\n3. Ensure \u201cNo data transfer\u201d is selected.\n\nIf the MDM console device policy is not set to disable the capability to back up to a locally connected system or on the Android 10 device, the device policy is not set to disable the capability to back up to a locally connected system, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40",
"fixid": "F-104625r1_fix",
"fixtext": "Configure the Google Android device to disable backup to locally connected systems.\n\nNOTE: On Restrictions, the backup features for Google are not in the framework.\n\nOn the MDM console:\n\n1. Open User restrictions.\n2. Select \"Disallow usb file transfer\".",
"iacontrols": null,
"id": "V-98949",
"ruleID": "SV-108053r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.",
"version": "GOOG-10-003700"
},
"V-98951": {
"checkid": "C-97791r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the capability to back up to a remote system has been disabled. \n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open User restrictions.\n2. Ensure \"Disallow backup servicer\" is not selected.\n\nOn the Android 10 device, do the following:\n\n1. Go to Settings >> System.\n2. Ensure Backup is set to \"Off\".\n\nIf the MDM console device policy is not set to disable the capability to back up to a remote system or on the Android 10 device, the device policy is not set to disable the capability to back up to a remote system, this is a finding.",
"description": "Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the Google 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40",
"fixid": "F-104627r1_fix",
"fixtext": "Configure the Google Android device to disable backup to remote systems (including commercial clouds).\n\nNOTE: On a Restrictions, data in the work profile cannot be backed up by default.\n\nOn the MDM console:\n\n1. Open User restrictions.\n2. Ensure \"Enable backup service\" is not selected.",
"iacontrols": null,
"id": "V-98951",
"ruleID": "SV-108055r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to not allow backup of all applications and configuration data to remote systems.",
"version": "GOOG-10-003900"
},
"V-98953": {
"checkid": "C-97793r1_chk",
"checktext": "Review documentation on the Google Android device and inspect the configuration on the Google Android device to verify the access control policy that prevents [selection: application processes] from accessing [selection: all] data stored by other [selection: application processes] is enabled.\n\nThis validation procedure is performed only on the MDM Administration Console. \n\nOn the MDM console, do the following:\n\n1. Open User restrictions.\n2. Select \"Disallow cross profile copy/paste\".\n3. Select \"Disallow sharing data into the profile\".\n\nIf the MDM console device policy is not set to disable data sharing between profiles, this is a finding.",
"description": "App data sharing gives apps the ability to access the data of other apps for enhanced user functionality. However, sharing also poses a significant risk that unauthorized users or apps will obtain access to DoD sensitive information. To mitigate this risk, there are data sharing restrictions. If a user is allowed to make exceptions to the data sharing restriction policy, the user could enable unauthorized sharing of data, leaving it vulnerable to breach. Limiting the granting of exceptions to either the Administrator or common application developer mitigates this risk.\n\nCopy/paste of data between applications in different application processes or groups of application processes is considered an exception to the access control policy and therefore, the Administrator must be able to enable/disable the feature. Other exceptions include allowing any data or application sharing between process groups.\n\nSFR ID: FMT_SMF_EXT.1.1 #42, FDP_ACF_EXT.1.2",
"fixid": "F-104629r1_fix",
"fixtext": "Configure the Google Android 10 to enable the access control policy that prevents [selection: application processes, groups of application processes] from accessing [selection: all, private] data stored by other [selection: application processes, groups of application processes].\n\nNOTE: All application data is inherently sandboxed and isolated from other applications. In order to disable copy/paste on the MDM Console:\n\n1. Open User restrictions.\n2. Select \"Disallow cross profile copy/paste\".\n3. Select \"Disallow sharing data into the profile\".",
"iacontrols": null,
"id": "V-98953",
"ruleID": "SV-108057r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disable exceptions to the access control policy that prevents application processes from accessing all data stored by other application processes.",
"version": "GOOG-10-004500"
},
"V-98955": {
"checkid": "C-97795r1_chk",
"checktext": "Review documentation on the Google Android device and inspect the configuration on the Google Android device to disable multi-user modes.\n\nThis validation procedure is performed on both the MDM Administration Console and the Android 10 device. \n\nOn the MDM console, do the following:\n\n1. Open the User restrictions.\n2. Open user settings.\n3. Confirm \"Disallow Add User\" is selected.\n\nOn the Android 10 device, do the following:\n\n1. Go to Settings >> System >> Advanced >> Multiple users.\n2. Ensure that there is no option to add a user.\n\nIf the MDM console device policy is not set to disable multi-user modes or on the Android 10 device, the device policy is not set to disable multi-user modes, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47b",
"fixid": "F-104631r1_fix",
"fixtext": "Configure the Google Android 10 to disable multi-user modes.\n\nOn the MDM console:\n\n1. Open the User restrictions.\n2. Open user settings.\n3. Select \"Disallow Add User\".",
"iacontrols": null,
"id": "V-98955",
"ruleID": "SV-108059r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disable multi-user modes.",
"version": "GOOG-10-004700"
},
"V-98957": {
"checkid": "C-97797r1_chk",
"checktext": "Review documentation on the Google Android device and inspect the configuration on the Google Android device to enable audit logging.\n\nThis validation procedure is performed on only on the MDM Administration Console. \n\nOn the MDM console, do the following:\n\n1. Open the User restrictions.\n2. Open user settings.\n3. Select \"Enable security logging\".\n4. Select \"Enable network logging\".\n\nIf the MDM console device policy is not set to enable audit logging, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #32",
"fixid": "F-104633r1_fix",
"fixtext": "Configure the Google Android 10 to enable audit logging.\n\nOn the MDM console:\n\n1. Open the User restrictions.\n2. Open user settings.\n3. Select \"Enable security logging\".\n4. Select \"Enable network logging\".",
"iacontrols": null,
"id": "V-98957",
"ruleID": "SV-108061r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enable audit logging.",
"version": "GOOG-10-005505"
},
"V-98959": {
"checkid": "C-97799r1_chk",
"checktext": "Review Google Android device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: detected integrity violations.\n\nThis validation procedure is performed only on the MDM Administration Console. \n\nOn the MDM console, do the following:\n1. Go to Policy management.\n2. Confirm Security Logging is enabled.\n\nIf the MDM console device policy is not set to enable security logging, this is a finding.",
"description": "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.\n\nApplication note: Requirement applies only to integrity violation detections that can be logged by the audit logging component.\n\nSFR ID: FMT_SMF_EXT.1.1 #37",
"fixid": "F-104635r1_fix",
"fixtext": "Configure the Google Android device to generate audit records for the following auditable events: detected integrity violations.\n\nOn the MDM console, do the following:\n\nOn the MDM Console:\n1. Go to Policy management.\n2. Enable Security Logging.",
"iacontrols": null,
"id": "V-98959",
"ruleID": "SV-108063r1_rule",
"severity": "low",
"title": "Google Android 10 must be configured to generate audit records for the following auditable events: detected integrity violations.",
"version": "GOOG-10-006100"
},
"V-98961": {
"checkid": "C-97801r1_chk",
"checktext": "Review a sample of site User Agreements for Google device users or similar training records and training course content. \n\nVerify that Google device users have completed the required training. The intent is that required training is renewed on a periodic basis in a time period determined by the AO. \n\nIf any Google device user has not completed the required training, this is a finding.",
"description": "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.\n\nSFR ID: NA",
"fixid": "F-104637r1_fix",
"fixtext": "All Google device users must complete training on the following training topics. (Users must acknowledge that they have reviewed training via a signed User Agreement or similar written record): \n\n- Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. \n- Need to ensure no DoD data is saved to the personal space or transmitted from a personal app (for example, from personal email). \n- If the Purebred key management app is used, users are responsible for maintaining positive control of their credentialed device at all times. The DoD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and to report any loss of control so the credentials can be revoked. Upon device retirement, turn-in, or reassignment, ensure that a factory data reset is performed prior to device hand-off. Follow mobility service provider decommissioning procedures as applicable.\n- How to configure the following UBE controls (users must configure the control) on the Google device: \n**Secure use of Calendar Alarm \n**Local screen mirroring and Mirroring procedures (authorized/not authorized for use) \n**Do not upload DoD contacts via smart call and caller ID services \n**Do not remove DoD intermediate and root PKI digital certificates \n**Disable Wi-Fi Sharing \n**Do not configure a DoD network (work) VPN profile on any third-party VPN client installed in the personal space \n**If Bluetooth connections are approved for mobile device, types of allowed connections (for example car hands-free, but not Bluetooth wireless keyboard)\n- AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.) in the Google device personal space.",
"iacontrols": null,
"id": "V-98961",
"ruleID": "SV-108065r1_rule",
"severity": "medium",
"title": "Google Android 10 users must complete required training.",
"version": "GOOG-10-008700"
},
"V-98963": {
"checkid": "C-97803r1_chk",
"checktext": "Review device configuration settings to confirm Wi-Fi Sharing is disabled. \n\nMobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the Authorizing Official (AO) has not approved Mobile Hotspot, and it has been verified as disabled on the MDM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to verify Wi-Fi Sharing is disabled: \n\nOn the MDM console:\n1. Open the User restrictions setting.\n2. Verify \"Disallow config tethering\" to on.\n\nOn the Google Android 10 device, do the following: \n1. Open Settings. \n2. Tap \"Networks & internet\". \n3. Verify that \"Hotspots & tethering\" is disabled. \n\nIf on the Google Android 10 device \"Wi-Fi sharing\" is enabled, this is a finding.",
"description": "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. \n\nWi-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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104639r1_fix",
"fixtext": "Configure Google Android 10 to disable Wi-Fi Sharing. \n\nMobile Hotspot must be enabled in order to enable Wi-Fi Sharing. If the AO has not approved Mobile Hotspot, and it has been disabled on the MDM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: \n\nOn the MDM console:\n1. Open the User restrictions setting.\n2. Set \"Disallow config tethering\" to on.",
"iacontrols": null,
"id": "V-98963",
"ruleID": "SV-108067r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to enforce that Wi-Fi Sharing is disabled.",
"version": "GOOG-10-008800"
},
"V-98965": {
"checkid": "C-97805r1_chk",
"checktext": "Review device configuration settings to confirm that the DoD root and intermediate PKI certificates are installed.\n\nThis procedure is performed on both the MDM Administration console and the Google Android 10 device. \n\nThe current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet). \n\nOn the MDM console verify that the DoD root and intermediate certificates are part of a device and/or work profile that is being pushed down to the devices.\n\nOn the Google Android 10 device, do the following: \n1. Open Settings. \n2. Tap \"Security\". \n3. Tap \"Advanced\".\n4. Tap \"Encryption & credentials\".\n5. Tap \"Trusted credentials\".\n6. Verify that DoD root and intermediate PKI certificates are listed under the User tab in the Work section.\n\nIf on the MDM console the DoD root and intermediate certificates are not listed in a profile, or the Google Android 10 device does not list the DoD root and intermediate certificates under the user tab, this is a finding.",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104641r1_fix",
"fixtext": "Configure Google Android 10 to install DoD root and intermediate certificates. \n\nOn the MDM console upload DoD root and intermediate certificates as part of a device and/or work profile.\n\nThe current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet).",
"iacontrols": null,
"id": "V-98965",
"ruleID": "SV-108069r1_rule",
"severity": "medium",
"title": "Google Android 10 must have the DoD root and intermediate PKI certificates installed.",
"version": "GOOG-10-009000"
},
"V-98967": {
"checkid": "C-97807r1_chk",
"checktext": "Review the device configuration to confirm that the user is unable to remove DoD root and intermediate PKI certificates.\n\nOn the MDM console:\n1. Open the User restrictions setting.\n2. Verify that \"Disallow config credentials\" to on for the work profile.\n\nOn the Google Android 10 device, do the following: \n1. Open Settings. \n2. Tap \"Security\". \n3. Tap \"Advanced\".\n4. Tap \"Encryption & credentials\".\n5. Tap \"Trusted credentials\".\n6. Verify that the user is unable to untrust or remove any work certificates.\n\nIf on the Google Android 10 device the user is able to remove certificates, this is a finding.",
"description": "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.\n\nSFR ID: FMT_MOF_EXT.1.2 #47",
"fixid": "F-104643r1_fix",
"fixtext": "Configure Google Android 10 to prevent a user from removing DoD root and intermediate PKI certificates.\n\nOn the MDM console:\n1. Open User restrictions.\n2. Set \"Disallow config credentials\" to on for the work profile.",
"iacontrols": null,
"id": "V-98967",
"ruleID": "SV-108071r1_rule",
"severity": "medium",
"title": "Google Android 10 must allow only the administrator (MDM) to install/remove DoD root and intermediate PKI certificates.",
"version": "GOOG-10-009100"
},
"V-98969": {
"checkid": "C-97809r1_chk",
"checktext": "Review the Google Android 10 Work Profile configuration settings to confirm that users are prevented from adding personal email accounts to the work email app. \n\nThis procedure is performed on both the MDM Administrator console and the Google Android 10 device. \n\nOn the MDM console:\n1. Open User restrictions.\n2. Verify that \"Disallow modify accounts\" is set to on.\n\nOn the Google Android 10 device, do the following: \n1. Open Settings. \n2. Tap \"Accounts\". \n3. Verify that \"Add account\" is grayed out under the Work section.\n\nIf on the MDM console the restriction to \"Disallow modify accounts\" is not set, or on the Google Android 10 device the user is able to add an account in the Work section, this is a finding.",
"description": "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 whitelisted accounts mitigates this vulnerability.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104645r1_fix",
"fixtext": "Configure Google Android 10 Work Profile to prevent users from adding personal email accounts to the work email app. \n\nOn the MDM console, for the Work Profile, do the following: \n1. Open User restrictions.\n2. Set \"Disallow modify accounts\" to on.\n\nRefer to the MDM documentation to determine how to provision users' work email accounts for the work email app.",
"iacontrols": null,
"id": "V-98969",
"ruleID": "SV-108073r1_rule",
"severity": "medium",
"title": "The Google Android 10 Work Profile must be configured to prevent users from adding personal email accounts to the work email app.",
"version": "GOOG-10-009200"
},
"V-98971": {
"checkid": "C-97811r1_chk",
"checktext": "Review the Google Android 10 Work Profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. What needs to happen is to verify only approved system apps have been placed on the core whitelist.\n\nThis procedure is performed on the MDM Administrator console. \n\nReview the system app white list and verify only approved apps are on the list.\n\nIf on the MDM console the system app white list contains unapproved core apps, this is a finding.",
"description": "The system application disable list controls user access to/execution of all core and preinstalled applications. \n\nCore application: Any application integrated into Google Android 10 by Google. \n\nPreinstalled application: Additional noncore applications included in the Google Android 10 build by Google or the wireless carrier. \n\nSome 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. \n\nThe 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104647r1_fix",
"fixtext": "Configure Google Android 10 Work Profile to enforce the system application disable list. \n\nThe required configuration is the default configuration when the device is enrolled. If the device configuration is changed, use the following procedure to bring the device back into compliance:\n\nOn the MDM, configure a list of approved Google core and preinstalled apps in the core app white list.",
"iacontrols": null,
"id": "V-98971",
"ruleID": "SV-108075r1_rule",
"severity": "medium",
"title": "Google Android 10 work profile must be configured to enforce the system application disable list.",
"version": "GOOG-10-009400"
},
"V-98973": {
"checkid": "C-97813r1_chk",
"checktext": "Review that Google Android 10 is configured as Corporate Owned Work Managed.\n\nThis procedure is performed on both the MDM Administrator console and the Google Android 10 device. \n\nOn the MDM console, verify that the default enrollment is set to Corporate Owned Work Managed.\n\nOn the Google Android 10 device, do the following: \n1. Go to the application drawer.\n2. Ensure a Personal tab and a Work tab are present.\n\nIf on the MDM console the account the default enrollment is set to Corporate Owned Work Managed or on the Google Android 10 device the user does not see a Work tab, this is a finding.",
"description": "The Android Enterprise Work Profile is the designated application group for the COPE use case.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104649r1_fix",
"fixtext": "Configure Google Android 10 in a Corporate Owned Work Managed configuration.\n\nOn the MDM console, configure the default enrollment as Corporate Owned Work Managed.\n\nRefer to the MDM documentation to determine how to configure the device to enroll as Corporate Owned Work Managed.",
"iacontrols": null,
"id": "V-98973",
"ruleID": "SV-108077r1_rule",
"severity": "medium",
"title": "Google Android 10 must be provisioned as a fully managed device and configured to create a work profile.",
"version": "GOOG-10-009600"
},
"V-98975": {
"checkid": "C-97815r1_chk",
"checktext": "Review Chrome Browser in Google Android 10 Work Profile autofill setting.\n\nThis procedure is performed only on the MDM Administrator console. \n\nOn the MDM console, for the Work Profile, do the following: \n1. Open the Chrome Browser Settings.\n2. Verify \"Enable autofill\" is set to off.\n\nIf on the MDM console autofill is set to on in the Chrome Browser Settings, this is a finding.",
"description": "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 Google Android 10 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104651r1_fix",
"fixtext": "Configure Chrome Browser in Google Android 10 Work Profile to disable autofill.\n\nOn the MDM console, for the Work Profile, do the following: \n1. Open the Chrome Browser Settings.\n2. Set \"Enable autofill\" to off.\n\nRefer to the MDM documentation to determine how to configure Chrome Browser Settings.",
"iacontrols": null,
"id": "V-98975",
"ruleID": "SV-108079r1_rule",
"severity": "medium",
"title": "Google Android 10 work profile must be configured to disable automatic completion of work space Internet browser text input.",
"version": "GOOG-10-009800"
},
"V-98977": {
"checkid": "C-97817r1_chk",
"checktext": "Review the Google Android 10 Workspace configuration settings to confirm that autofill services are disabled. \n\nThis procedure is performed only on the MDM Administration console. \n\nOn the MDM console, for the Workspace, in the \"Android user restrictions\" group, under the work profile, verify that \"disallow autofill\" is selected. \n\nIf on the MDM console \"disallow autofill\" is selected, this is a finding.",
"description": "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 Google Android 10 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. \n\nExamples of apps that offer autofill services include Samsung Pass, Google, Dashlane, LastPass, and 1Password.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104653r1_fix",
"fixtext": "Configure Google Android 10 Workspace to disable the autofill services. \n\nOn the MDM console, in the Android work profile restrictions, select \"disallow autofill\".",
"iacontrols": null,
"id": "V-98977",
"ruleID": "SV-108081r1_rule",
"severity": "medium",
"title": "Google Android 10 Work Profile must be configured to disable the autofill services.",
"version": "GOOG-10-010000"
},
"V-98979": {
"checkid": "C-97819r1_chk",
"checktext": "Review the Google Android 10 Work Profile configuration settings to confirm that autofill services are disabled. \n\nThis procedure is performed on both the MDM Administration console and the Google Android 10 device. \n\nOn the MDM console, verify that \"Set auto (network) time required to on\" is selected.\n\nOn the Google Android 10 device, do the following: \n1. Open Settings. \n2. Tap \"System\". \n3. Tap \"Date & times\". \n4. Verify that \"User network-provided time\" is grayed out.\n\nIf on the MDM console \"Set auto (network) time required\" to \"on\", or on the Google Android 10 device \"User network-provided time\" is grayed out, this is a finding.",
"description": "Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events. \n\nPeriodically 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 Google Android 10 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. \n\nTime stamps generated by the audit system in Google Android 10 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104655r1_fix",
"fixtext": "Configure Google Android 10 Work Profile to set auto network time.\n\nOn the MDM console, in the Android user restrictions section, select \"Set auto (network) time required\" to on\".",
"iacontrols": null,
"id": "V-98979",
"ruleID": "SV-108083r1_rule",
"severity": "medium",
"title": "Google Android 10 must be configured to disallow configuration of date and time.",
"version": "GOOG-10-010200"
},
"V-98981": {
"checkid": "C-97821r1_chk",
"checktext": "Review device configuration settings to confirm that the Google Android device recently released version of Google Android 10 is installed. \n\nThis procedure is performed on both the MDM console and the Google Android 10 device.\n\nIn the MDM management console, review the version of Google Android 10 installed on a sample of managed devices. This procedure will vary depending on the MDM product. \n\nOn the Google Android 10 device, to see the installed operating system version: \n1. Open Settings. \n2. Tap \"About phone\". \n3. Verify \"Build number\". \n\nIf the installed version of the Android operating system on any reviewed Google devices is not the latest released by Google, this is a finding. \n\nGoogle's Android operating system patch website: https://source.android.com/security/bulletin/",
"description": "Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104657r1_fix",
"fixtext": "Install the latest released version of the Google Android 10 operating system on all managed Google devices.\n\nNote: Google Android device operating system updates are released directly by Google or can be distributed via the MDM.",
"iacontrols": null,
"id": "V-98981",
"ruleID": "SV-108085r1_rule",
"severity": "high",
"title": "Google Android 10 devices must have the latest available Google Android 10 operating system installed.",
"version": "GOOG-10-010800"
},
"V-98983": {
"checkid": "C-97823r1_chk",
"checktext": "Review device configuration settings to confirm that no third-party keyboards are enabled. \n\nThis procedure is performed on both the MDM console and the Google Android 10 device.\n\nIn the MDM management console, review the user restrictions section.\nSelect \"Set input methods\" and insure no third-party keyboards are installed.\n\nOn the Google Android 10 device, to see if a third-party keyboard is enabled:\n1. Open Settings>>System>>Languages & input. \n2. Tap \"Virtual keyboard\". \n3. Tap \"Manage keyboard\". \n4. Ensure no third-party keyboards are listed, or if third-party keyboards are present they are \"Disabled by admin\".\n\nIf third-party keyboards are enabled, this is a finding. \n\nGoogle's Android operating system patch website: https://source.android.com/security/bulletin/",
"description": "Many third-party keyboard applications are known to contain malware.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-104659r1_fix",
"fixtext": "Configure Google Android 10 device to disallow the use of third-party keyboards. \n\nOn the MDM console, in the Android user restrictions section, select \"Set input methods\" and ensure no third-party keyboards are installed.",
"iacontrols": null,
"id": "V-98983",
"ruleID": "SV-108087r1_rule",
"severity": "low",
"title": "Google Android 10 devices must be configured to disable the use of third-party keyboards.",
"version": "GOOG-10-011000"
}
},
"profiles": {
"MAC-1_Classified": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-1_Classified",
"title": "I - Mission Critical Classified"
},
"MAC-1_Public": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-1_Public",
"title": "I - Mission Critical Public"
},
"MAC-1_Sensitive": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-1_Sensitive",
"title": "I - Mission Critical Sensitive"
},
"MAC-2_Classified": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-2_Classified",
"title": "II - Mission Support Classified"
},
"MAC-2_Public": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-2_Public",
"title": "II - Mission Support Public"
},
"MAC-2_Sensitive": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-2_Sensitive",
"title": "II - Mission Support Sensitive"
},
"MAC-3_Classified": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-3_Classified",
"title": "III - Administrative Classified"
},
"MAC-3_Public": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-3_Public",
"title": "III - Administrative Public"
},
"MAC-3_Sensitive": {
"description": "",
"findings": {
"V-98921": "true",
"V-98923": "true",
"V-98925": "true",
"V-98927": "true",
"V-98929": "true",
"V-98931": "true",
"V-98933": "true",
"V-98935": "true",
"V-98937": "true",
"V-98939": "true",
"V-98941": "true",
"V-98943": "true",
"V-98945": "true",
"V-98947": "true",
"V-98949": "true",
"V-98951": "true",
"V-98953": "true",
"V-98955": "true",
"V-98957": "true",
"V-98959": "true",
"V-98961": "true",
"V-98963": "true",
"V-98965": "true",
"V-98967": "true",
"V-98969": "true",
"V-98971": "true",
"V-98973": "true",
"V-98975": "true",
"V-98977": "true",
"V-98979": "true",
"V-98981": "true",
"V-98983": "true"
},
"id": "MAC-3_Sensitive",
"title": "III - Administrative Sensitive"
}
},
"slug": "google_android_10.x",
"title": "Google Android 10.x Security Technical Implementation Guide",
"version": "1"
}
}