View STIG - Google Android 15 COBO Security Technical Implementation Guide V1R2

b

Google Android 15 must be configured to enable audit logging.

AU-6 - Medium - CCI-000154 - V-267430 - SV-267430r1031475_rule

RMF Control

AU-6

Severity

Medium

CCI

CCI-000154

Version

GOOG-15-002800

Vuln IDs

V-267430

Rule IDs

SV-267430r1031475_rule

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. SFRID: FMT_SMF.1.1 #32

Checks: C-71354r1031473_chk

Inspect the configuration on the managed Google Android 15 device to enable audit logging. This validation procedure is performed only on the EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Verify that "Enable security logging" is toggled to "ON". If the EMM console device policy is not set to enable audit logging, this is a finding.

Fix: F-71257r1031474_fix

Configure the Google Android 15 device to enable audit logging. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Toggle "Enable security logging" to "ON".

b

Google Android 15 must be configured to enforce a minimum password length of six characters.

- Medium - CCI-004066 - V-267431 - SV-267431r1031478_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-15-006000

Vuln IDs

V-267431

Rule IDs

SV-267431r1031478_rule

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 in device and data compromise. SFRID: FMT_SMF.1.1 #1

Checks: C-71355r1031476_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device is enforcing a minimum password length of six characters. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Verify Numeric Complex, Alphabetic, Alphanumeric, or Complex is selected. 5. Open "Minimum password length". 6. Verify "6" is set for number of characters. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify "Minimum password quality" is set to Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Verify the number of characters is set to "6" or higher. _____________________________ On the managed Google Android 15 device: COBO and COPE: 1. Open Settings >> Security & privacy >> Device unlock >> Screen lock. 2. Enter current password. 3. Tap "Pin or Password". 4. Verify Password length required is at least "6". If the device password length is not set to six characters or more on EMM console or on the managed Google Android 15 device, this is a finding.

Fix: F-71258r1031477_fix

Configure the Google Android 15 device to enforce a minimum password length of six characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Open "Minimum password quality". 4. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 5. Open "Minimum password length". 6. Enter in the number of characters as "6". COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Open "Minimum password quality". 5. Choose Numeric Complex, Alphabetic, Alphanumeric, or Complex. 6. Open "Minimum password length". 7. Enter in the number of characters as "6".

b

Google Android 15 must be configured to not allow passwords that include more than four repeating or sequential characters.

- Medium - CCI-004066 - V-267432 - SV-267432r1031481_rule

RMF Control

Severity

Medium

CCI

CCI-004066

Version

GOOG-15-006100

Vuln IDs

V-267432

Rule IDs

SV-267432r1031481_rule

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. SFRID: FMT_SMF.1.1 #1

Checks: C-71356r1031479_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device is prohibiting passwords with more than four repeating or sequential characters. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Verify that quality is set to "Numeric (Complex)" or higher. COPE: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Select "Personal Profile". 4. Verify that quality is set to "Numeric (Complex)" or higher. ____________________________ On the managed Google Android 15 device: COBO and COPE: 1. Open Settings >> Security >> Screen lock. 2. Enter current password. 3. Select "PIN". 4. Try to enter a new PIN with repeating numbers. 5. Verify Password complexity requirements are listed: Ascending, descending, or repeated sequence of digits is not allowed. If the EMM console device policy is set to a password with more than two repeating or sequential characters or on the managed Google Android 15 device, the device policy is set to a password with more than two repeating or sequential characters, this is a finding. Note: 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.

Fix: F-71259r1031480_fix

Configure the Google Android 15 device to prevent passwords from containing more than four repeating or sequential characters. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Password constraints". 3. Set password quality to "Numeric (Complex)". COPE: 1. Open "Password constraints". 2. Select "Personal Profile". 3. Set password quality to "Numeric (Complex)". Note: 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.

b

Google Android 15 must be configured to lock the display after 15 minutes (or less) of inactivity.

AC-11 - Medium - CCI-000057 - V-267433 - SV-267433r1031484_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000057

Version

GOOG-15-006300

Vuln IDs

V-267433

Rule IDs

SV-267433r1031484_rule

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. SFRID: FMT_SMF.1.1 #2

Checks: C-71357r1031482_chk

Review managed 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 15 minutes or less of inactivity. Note: Google Android 15 Settings User Interface (UI) does not support the 15-minute increment, but this value can be set by the MDM. This validation procedure is performed on both the EMM Administration Console and the Android 15 device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Max time to screen lock" is set to "900". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Max time to screen lock" is set to "900". Note: The units are in seconds. If the EMM console device policy is not set to enable a screen-lock policy that will lock the display after a period of inactivity of 900 seconds, this is a finding.

Fix: F-71260r1031483_fix

Configure the Google Android 15 device to enable a screen-lock policy of 15 minutes for the max period of inactivity. Note: Google Android 15 Settings User Interface (UI) does not support the 15-minute increment, but this value can be set by the MDM. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Set "Max time to screen lock" to "900". Note: The units are in seconds. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Set "Max time to screen lock" to 900". Note: The units are in seconds.

b

Google Android 15 must be configured to not allow more than 10 consecutive failed authentication attempts.

AC-7 - Medium - CCI-000044 - V-267434 - SV-267434r1033027_rule

RMF Control

AC-7

Severity

Medium

CCI

CCI-000044

Version

GOOG-15-006400

Vuln IDs

V-267434

Rule IDs

SV-267434r1033027_rule

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. SFRID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5

Checks: C-71358r1033026_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has the maximum number of consecutive failed authentication attempts set at 10 or fewer. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Verify that "Max password failures for local wipe" is set to a number between 1 and 10. On the managed Google Android 15 device: COBO and COPE: 1. Lock the device screen. 2. Attempt to unlock the screen and validate that the device autowipes after specified number of invalid entries. Note: Perform this verification only with a test phone set up with a production profile. If the EMM console device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, or if on the managed Google Android 15 device the device policy is not set to the maximum number of consecutive failed authentication attempts at 10 or fewer, this is a finding.

Fix: F-71261r1031486_fix

Configure the Google Android 15 device to allow only 10 or fewer consecutive failed authentication attempts. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Set "Max password failures for local wipe" to a number between 1 and 10. COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Personal Profile". 4. Set "Max password failures for local wipe" to a number between 1 and 10.

b

Google Android 15 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].

CM-6 - Medium - CCI-000366 - V-267435 - SV-267435r1031490_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-006500

Vuln IDs

V-267435

Rule IDs

SV-267435r1031490_rule

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. SFRID: FMT_SMF.1.1 #8

Checks: C-71359r1031488_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has only approved application repositories (DOD-approved commercial app repository, EMM server, and/or mobile application store). This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow install unknown sources" is toggled to "ON". 3. Verify that "Disallow installs from unknown sources globally" is toggled to "ON". On the Google Android 15 device: COBO and COPE: 1. Open Settings >> Apps >> Special app access. 2. Open Install unknown apps. 3. Ensure the list of apps is blank or if an app is on the list, "Disabled by admin" is listed under the app name. If the EMM console device policy is not set to allow connections to only approved application repositories or on the managed Google Android 15 device, the device policy is not set to allow connections to only approved application repositories, this is a finding.

Fix: F-71262r1031489_fix

Configure the Google Android 15 device to disable unauthorized application repositories. On the EMM console: COBO and COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow install unknown sources" to "ON". 3. Toggle "Disallow installs from unknown sources globally" to "ON".

b

Google Android 15 must be configured to enforce an application installation policy by specifying an application allow list that restricts applications by the following characteristics: [selection: list of digital signatures, cryptographic hash values, names, application version].

CM-7 - Medium - CCI-001764 - V-267436 - SV-267436r1033112_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-001764

Version

GOOG-15-006600

Vuln IDs

V-267436

Rule IDs

SV-267436r1033112_rule

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. SFRID: FMT_SMF.1.1 #8

Checks: C-71360r1033110_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has an application allow list configured. Verify all applications on the allow list have been approved by the authorizing official (AO). On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Verify all selected apps are AO approved. On the managed Google Android 15 device: COBO and COPE: 1. Open the managed Google Play Store. 2. Verify that only the approved apps are visible. Note: Managed Google Play is an allowed App Store. If the EMM console list of selected managed Google Play apps includes nonapproved apps, this is a finding. Note: The application allow list will include approved 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. For Google Android, there are no preinstalled applications.

Fix: F-71263r1033111_fix

Configure the Google Android 15 device to use an application allow list. On the EMM console: COBO and COPE: 1. Go to the Android app catalog for managed Google Play. 2. Select apps to be available (only approved apps). 3. Push updated policy to the device. Note: Managed Google Play is an allowed App Store.

b

Google Android 15 allow list must be configured to not include applications with the following characteristics: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs or printers; and - Backs up its own data to a remote system.

IA-7 - Medium - CCI-000803 - V-267437 - SV-267437r1033032_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-15-006700

Vuln IDs

V-267437

Rule IDs

SV-267437r1033032_rule

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 noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier. SFRID: FMT_SMF.1.1 #8

Checks: C-71361r1033030_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has an application allow list configured and that the application allow list does not include applications with the following characteristics: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs or printers; and - Backs up its own data to a remote system. This validation procedure is performed only on the EMM Administration Console. On the EMM console: 1. Review the list of selected Managed Google Play apps. 2. Review the details and privacy policy of each selected app to ensure the app does not include prohibited characteristics. If the EMM console device policy includes applications with unauthorized characteristics, this is a finding.

Fix: F-71264r1033031_fix

Configure the Google Android 15 device application allow list to exclude applications with the following characteristics: - Backs up MD data to non-DOD cloud servers (including user and application access to cloud backup services); - Transmits 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; - Payment processing; - Allows unencrypted (or encrypted but not FIPS 140-2/140-3 validated) data sharing with other MDs or printers; and - Backs up its own data to a remote system. On the EMM console: 1. Go to the Android app catalog for managed Google Play. 2. Before selecting an app, review the app details and privacy policy to ensure the app does not include prohibited characteristics.

b

Google Android 15 allow list must be configured to not include artificial intelligence (AI) applications that process device data in the cloud, including Google Gemini.

IA-7 - Medium - CCI-000803 - V-267438 - SV-267438r1042520_rule

RMF Control

IA-7

Severity

Medium

CCI

CCI-000803

Version

GOOG-15-006750

Vuln IDs

V-267438

Rule IDs

SV-267438r1042520_rule

Sensitive DOD data could be exposed when an AI app processes device data in the cloud. SFRID: FMT_SMF.1.1 #8

Checks: C-71362r1042518_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has an AI application that processes device data in the cloud, including Google Gemini. This validation procedure is performed only on the EMM Administration Console. On the EMM console: 1. Review the list of selected Managed Google Play apps. 2. Verify no AI applications that process device data in the cloud, including Google Gemini, are included. If the EMM console device policy includes AI applications that process device data in the cloud, including Google Gemini, this is a finding. Note: This restriction does not include Gemini Nano. Gemini Nano is a built-in capability of Android 15 and processes device data on the device. Refer to Section 2, Artificial Intelligence Restrictions, of the STIG Supplemental document for more information.

Fix: F-71265r1042519_fix

Configure the Google Android 15 device application allow list to exclude AI applications that process device data in the cloud, including Google Gemini. Note: This restriction does not include Gemini Nano. Gemini Nano is a built-in capability of Android 15 and processes device data on the device. See Section 2 "Artificial Intelligence Restrictions" of the STIG Supplemental document for more information.

b

Google Android 15 must be configured to not display the following (work profile) notifications when the device is locked: [selection: a. email notifications b. calendar appointments c. contact associated with phone call notification d. text message notification e. other application-based notifications f. all notifications].

AC-11 - Medium - CCI-000060 - V-267439 - SV-267439r1031502_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000060

Version

GOOG-15-006800

Vuln IDs

V-267439

Rule IDs

SV-267439r1031502_rule

Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the mobile operating system (MOS) to not send notifications to the lock screen mitigates this risk. SFRID: FMT_SMF.1.1 #18

Checks: C-71363r1031500_chk

Review managed Google Android 15 device settings to determine if the Google Android 15 device displays (work profile) notifications on the lock screen. Notifications of incoming phone calls are acceptable even when the device is locked. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Verify that "Disable unredacted notifications" is toggled to "ON". COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Verify that "Disable unredacted notifications" is toggled to "ON". ___________________________ On the managed Google Android 15 device: COBO: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "Privacy". 3. Verify that "Show sensitive content only when unlocked" is selected. COPE: 1. Go to Settings >> Display >> Lock screen. 2. Tap on "When work profile is locked". 3. Verify that "Hide sensitive work content" is selected. If the EMM console device policy allows work notifications on the lock screen, or the managed Google Android 15 device allows work notifications on the lock screen, this is a finding.

Fix: F-71266r1031501_fix

Configure the Google Android 15 device to not display (work profile) notifications when the device is locked. On the EMM console: COBO: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Toggle "Disable unredacted notifications". COPE: 1. Open "Lock screen" settings. 2. Open "Lock screen restrictions". 3. Select "Work Profile". 4. Toggle "Disable unredacted notifications".

b

Google Android 15 must be configured to disable trust agents.

IA-2 - Medium - CCI-000767 - V-267440 - SV-267440r1031505_rule

RMF Control

IA-2

Severity

Medium

CCI

CCI-000767

Version

GOOG-15-007200

Vuln IDs

V-267440

Rule IDs

SV-267440r1031505_rule

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. SFRID: FMT_SMF.1.1 #22, FIA_UAU.5.1

Checks: C-71364r1031503_chk

Review device configuration settings to confirm that trust agents are disabled. This procedure is performed on both the EMM Administration console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Verify that "Disable trust agents" is toggled to "ON". COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Verify that "Disable trust agents" is toggled to "ON". 4. Select "Work Profile". 5. Verify that "Disable trust agents" is toggled to "ON". ____________________________ On the managed Google Android 15 device: COBO and COPE: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the EMM console, "disable trust agents" is not selected, or on the managed Google Android 15 device a trust agent can be enabled, this is a finding.

Fix: F-71267r1031504_fix

Configure the Google Android 15 device to disable trust agents. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Toggle "Disable trust agents" to "ON". COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Toggle "Disable trust agents" to "ON". 4. Select "Work Profile". 5. Toggle "Disable trust agents" to "ON".

b

Google Android 15 must be configured to disable developer modes.

CM-7 - Medium - CCI-000381 - V-267441 - SV-267441r1033036_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-000381

Version

GOOG-15-007400

Vuln IDs

V-267441

Rule IDs

SV-267441r1033036_rule

Developer modes expose features of the mobile operating system (MOS) 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. SFRID: FMT_SMF.1.1 #26

Checks: C-71365r1033035_chk

Review managed Google Android 15 device configuration settings to determine whether a developer mode is enabled. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow debugging features" is toggled to "ON". 3. Open "Set user restrictions on parent". 4. Verify that "Disallow debugging features" is toggled to "ON". On the managed Google Android 15 device: COBO and COPE: 1. Go to Settings >> System. 2. Ensure "Developer Options" is not listed. 3. Go to Settings >> About Phone. 4. Tap on the Build Number to try to enable Developer Options and validate that action is blocked. If the EMM console device policy is not set to disable developer mode or on the managed Google Android 15 device, the device policy is not set to disable developer mode, this is a finding.

Fix: F-71268r1031507_fix

Configure the Google Android 15 device to disable developer modes. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow debugging features" to "ON". 3. Open "Set user restrictions on parent". 4. Toggle "Disallow debugging features" to "ON".

a

Google Android 15 must be configured to display the DOD advisory warning message at startup or each time the user unlocks the device.

AC-8 - Low - CCI-000048 - V-267442 - SV-267442r1031511_rule

RMF Control

AC-8

Severity

Low

CCI

CCI-000048

Version

GOOG-15-007700

Vuln IDs

V-267442

Rule IDs

SV-267442r1031511_rule

Before granting access to the system, the mobile operating system is required to display the DOD-approved system use notification message or banner that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Required banners help ensure that DOD can audit and monitor the activities of mobile device users without legal restriction. System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a "click-through" banner at device unlock (to the extent permitted by the operating system). A "click-through" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating "OK." The approved DOD text must be used exactly as required in the Knowledge Service referenced in DODI 8500.01. For devices accommodating banners of 1300 characters, the banner text is: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. For devices with severe character limitations, the banner text is: I've read & consent to terms in IS user agreem't. The administrator must configure the banner text exactly as written without any changes. SFRID: FMT_SMF.1.1 #36

Checks: C-71366r1031509_chk

The DOD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each managed Android 15 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each managed Android 15 mobile device. Determine which method is used at the Google Android 15 device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several Google Android 15 device users and verify the agreement includes the required DOD warning banner text. Validation Procedure for Method #2: On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Verify the message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Verify the message. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the EMM console device policy is not set to display a warning banner with the appropriate designated wording or on the managed Google Android 15 device, the device policy is not set to display a warning banner with the appropriate designated wording, this is a finding.

Fix: F-71269r1031510_fix

Configure the DOD warning banner by either of the following methods (required text is found in the Vulnerability Discussion): 1. By placing the DOD warning banner text in the user agreement signed by each Google Android 15 device user (preferred method). 2. By configuring the warning banner text on the EMM console and installing the banner on each Google Android 15 mobile device. On the EMM console: COBO: 1. Open "Lock screen restrictions". 2. Select "Lock screen message". 3. Enter the message. COPE: 1. Open "Lock screen restrictions". 2. Select "Personal Profile". 3. Select "Lock screen message". 4. Enter the message.

b

Google Android 15 must be configured to generate audit records for the following auditable events: Detected integrity violations.

AU-12 - Medium - CCI-000169 - V-267443 - SV-267443r1031514_rule

RMF Control

AU-12

Severity

Medium

CCI

CCI-000169

Version

GOOG-15-007800

Vuln IDs

V-267443

Rule IDs

SV-267443r1031514_rule

Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Requirement Statement lists key events for which the system must generate an audit record. Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component. SFRID: FMT_SMF.1.1 #37

Checks: C-71367r1031512_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: Detected integrity violations. This validation procedure is performed only on the EMM Administration Console. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Verify that "Enable security logging" is toggled to "ON". If the EMM console device policy is not set to enable security logging, this is a finding.

Fix: F-71270r1031513_fix

Configure the Google Android 15 device to generate audit records for the following auditable events: Detected integrity violations. On the EMM console: COBO and COPE: 1. Open "Device owner management" section. 2. Toggle "Enable security logging" to "ON".

b

Google Android 15 must be configured to disable USB mass storage mode.

SC-41 - Medium - CCI-002546 - V-267444 - SV-267444r1031517_rule

RMF Control

SC-41

Severity

Medium

CCI

CCI-002546

Version

GOOG-15-008400

Vuln IDs

V-267444

Rule IDs

SV-267444r1031517_rule

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. SFRID: FMT_SMF.1.1 #39

Checks: C-71368r1031515_chk

Review managed Google Android 15 device configuration settings to determine if the mobile device has a USB mass storage mode and whether it has been disabled. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify that "Disallow USB file transfer" is toggled to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Verify "Disallow USB file transfer" is toggled to "ON". ______________________________ On the managed Google Android 15 device: 1. Connect a USB cable to the managed Google Android 15 device and connect to a non-DOD network-managed PC. 2. Go to Settings >> Connected devices >> USB. 3. Verify "No data transfer" is selected. If the EMM console device policy is not set to disable USB mass storage mode or on the managed Google Android 15 device, the device policy is not set to disable USB mass storage mode, this is a finding.

Fix: F-71271r1031516_fix

Configure the Google Android 15 device to disable USB mass storage mode. On the EMM console: COBO: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow USB file transfer" to "ON". COPE: 1. Open "User restrictions". 2. Open "Set user restrictions on parent". 3. Toggle "Disallow USB file transfer" to "ON".

b

Google Android 15 must be configured to not allow backup of [all applications, configuration data] to locally connected systems.

SC-4 - Medium - CCI-001090 - V-267445 - SV-267445r1031520_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-15-008500

Vuln IDs

V-267445

Rule IDs

SV-267445r1031520_rule

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. SFRID: FMT_SMF.1.1 #40

Checks: C-71369r1031518_chk

Review managed Google Android 15 device configuration settings to determine if the capability to back up to a locally connected system has been disabled. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify "Enable backup service" is toggled to "OFF". On the managed Google Android 15 device: COBO: 1. Go to Settings >> System >> Backup. 2. Verify Backup settings is "Not available". COPE: 1. Go to Settings >> System >> Backup. 2. Select "Work". 3. Verify Backup settings is "Not available". If the EMM console device policy is not set to disable the capability to back up to a locally connected system or on the managed Google Android 15 device, the device policy is not set to disable the capability to back up to a locally connected system, and this is a finding.

Fix: F-71272r1031519_fix

Configure the Google Android 15 device to disable backup to locally connected systems. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to "OFF".

b

Google Android 15 must be configured to not allow backup of [all applications, configuration data] to remote systems.

SC-4 - Medium - CCI-001090 - V-267446 - SV-267446r1031523_rule

RMF Control

SC-4

Severity

Medium

CCI

CCI-001090

Version

GOOG-15-008600

Vuln IDs

V-267446

Rule IDs

SV-267446r1031523_rule

Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system (MOS). 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. SFRID: FMT_SMF.1.1 #40

Checks: C-71370r1031521_chk

Review managed Google Android 15 device configuration settings to determine if the capability to back up to a remote system has been disabled. Note: Since personal accounts cannot be added to the work profile (GOOG-15-009800), this control only impacts personal profile accounts. Site can allow backup based on local policy. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Verify "Enable backup service" is toggled to "OFF". On the managed Google Android 15 device: COBO: 1. Go to Settings >> System >> System >> Backup. 2. Verify Backup settings is "Not available". COPE: 1. Go to Settings >> System >> System >> Backup. 2. Select "Work". 3. Verify Backup settings is "Not available". If the EMM console device policy is not set to disable the capability to back up to a remote system or on the managed Google Android 15 device, the device policy is not set to disable the capability to back up to a remote system, this is a finding.

Fix: F-71273r1031522_fix

Configure the Google Android 15 device to disable backup to remote systems (including commercial clouds). On the EMM console: COBO and COPE: 1. Open "Device owner management". 2. Toggle "Enable backup service" to "OFF". Note: Since personal accounts cannot be added to the work profile (GOOG-15-009800), this control only impacts personal profile accounts. Site can allow backup based on local policy.

b

Google Android 15 must be configured to enable authentication of personal hotspot connections to the device using a preshared key.

AC-18 - Medium - CCI-001443 - V-267447 - SV-267447r1033115_rule

RMF Control

AC-18

Severity

Medium

CCI

CCI-001443

Version

GOOG-15-008700

Vuln IDs

V-267447

Rule IDs

SV-267447r1033115_rule

If no authentication is required to establish personal hotspot connections (Wi-Fi and Bluetooth), an adversary may be able to use that device to perform attacks on other devices or networks without detection. A sophisticated adversary may also be able to exploit unknown system vulnerabilities to access information and computing resources on the device. Requiring authentication to establish personal hotspot connections mitigates this risk. Application note: If hotspot functionality is permitted, it must be authenticated via a preshared key. There is no requirement to enable hotspot functionality, and it is recommended this functionality be disabled by default. SFRID: FMT_SMF.1.1 #41

Checks: C-71371r1033113_chk

This is a User-Based Enforcement (UBE) control. Check a sample of Pixel phones at the site and verify the Wi-Fi hotspot preshared key (password) is set to "WPA2/WPA3-Personal" or "WPA3-Personal". 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. Tap on the words to the left of the slide called "Wi-Fi Hotspot" to show the configuration options. 4. Click the "Security" link and verify either “WPA2/WPA3-Personal” or "WPA3-Personal" is selected. If the Wi-Fi hotspot security is not set to “WPA2/WPA3-Personal” or "WPA3-Personal", this is a finding.

Fix: F-71274r1033114_fix

This is a User-Based Enforcement (UBE) control. Train users to not change the default Wi-Fi hotspot security setting: 15-character complex Wi-Fi hotspot preshared key (password) ("WPA2/WPA3-Personal" or WPA3-Personal"). (GOOG-15-009800). If the required preshared key is not set up, train users to use the following procedure to set up the required setting: 1. Go to Settings >> Network & Internet >> Hotspot & tethering. 2. Enable "Wi-Fi hotspot". 3. Tap on the words to the left of the slide called "Wi-Fi Hotspot" to show the configuration options. 4. Click the "Security" link and select “WPA2/WPA3-Personal” or "WPA3-Personal".

b

Google Android 15 must be configured to disable multiuser modes.

AC-2 - Medium - CCI-002110 - V-267448 - SV-267448r1033039_rule

RMF Control

AC-2

Severity

Medium

CCI

CCI-002110

Version

GOOG-15-009000

Vuln IDs

V-267448

Rule IDs

SV-267448r1033039_rule

Multiuser mode allows multiple users to share a mobile device by providing a degree of separation between user data. To date, no mobile device with multiuser mode features meets DOD requirements for access control, data separation, and nonrepudiation for user accounts. In addition, the MDFPP does not include design requirements for multiuser account services. Disabling multiuser mode mitigates the risk of not meeting DOD multiuser account security policies. SFRID: FMT_SMF.1.1 #47a

Checks: C-71372r1033037_chk

Review documentation on the managed Google Android 15 device and inspect the configuration on the Google Android device to disable multiuser modes. This validation procedure is performed on both the EMM Administration Console and the managed Google Android 15 device. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Verify "Disallow modify accounts" is toggled to "ON". On the managed Google Android 15 device: COBO and COPE: 1. Go to Settings >> Passwords, passkeys & accounts >> Accounts for Owner. 2. Tap "Add account" (work profile). 3. Verify the action is not allowed. If the EMM console device policy is not set to disable multiuser modes or on the managed Google Android 15 device, the device policy is not set to disable multiuser modes, this is a finding.

Fix: F-71275r1033038_fix

Configure the Google Android 15 device to disable multiuser modes. On the EMM console: COBO and COPE: 1. Open "User restrictions". 2. Open "Set user restrictions". 3. Toggle "Disallow modify accounts" to "ON".

a

Google Android 15 must be configured to disable all Bluetooth profiles except for HSP (Headset Profile), HFP (Hands-Free Profile), SPP (Serial Port Profile), A2DP (Advanced Audio Distribution Profile), AVRCP (Audio/Video Remote Control Profile), and PBAP (Phone Book Access Profile).

CM-7 - Low - CCI-000381 - V-267449 - SV-267449r1031532_rule

RMF Control

CM-7

Severity

Low

CCI

CCI-000381

Version

GOOG-15-009400

Vuln IDs

V-267449

Rule IDs

SV-267449r1031532_rule

Some Bluetooth profiles provide the capability for remote transfer of sensitive DOD data without encryption or otherwise do not meet DOD IT security policies and therefore must be disabled. SFRID: FMT_SMF_EXT.1.1/BLUETOOTH BT-8

Checks: C-71373r1031530_chk

Determine if the authorizing official (AO) has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify Bluetooth has been disabled. On the EMM console: COBO: 1. Open "User restrictions" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". COPE: 1. Open "User restrictions on parent" section. 2. Verify "Disallow Bluetooth" is toggled to "ON". On the managed Google Android 15 device: COBO and COPE: 1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth. 2. Verify "Use Bluetooth" is set to OFF and cannot be toggled to "ON". If the AO has approved the use of Bluetooth, on the managed Android 15 device: 1. Go to Settings >> Connected Devices. 2. Verify only approved Bluetooth connected devices using approved profiles are listed. If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an EMM-managed device policy, this is a finding. If 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.

Fix: F-71276r1031531_fix

Configure the Google Android 15 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 (UBE). To disable Bluetooth use the following procedure: On the EMM console: COBO: 1. Open "User restrictions" section. 2. Toggle "Disallow Bluetooth" to "ON". COPE: 1. Open "User restrictions on parent" section. 2. Toggle "Disallow Bluetooth" to "ON". The user training requirement is satisfied in requirement GOOG-15-009800.

b

Google Android 15 must be configured to disable ad hoc wireless client-to-client connection capability.

SC-40 - Medium - CCI-002536 - V-267450 - SV-267450r1042523_rule

RMF Control

SC-40

Severity

Medium

CCI

CCI-002536

Version

GOOG-15-009500

Vuln IDs

V-267450

Rule IDs

SV-267450r1042523_rule

Ad hoc wireless client-to-client connections allow mobile devices to communicate with each other directly, circumventing network security policies and making the traffic invisible. This could allow the exposure of sensitive DOD data and increase the risk of downloading and installing malware of the DOD mobile device. SFRID: FMT_SMF_EXT.1.1/WLAN

Checks: C-71374r1042521_chk

Review the configuration to determine if the Google Android devices are disallowing Wi-Fi Direct. This validation procedure is performed on both the management tool and the Google Android device. On the management tool, in the user restrictions, verify "Wi-Fi Direct" has been set to "Disallow": COBO: 1. Find "User Restrictions" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and verify it is set to "ON". COPE: 1. Find "User Restrictions on Parent" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and verify it is set to "ON". On the Google Android device: 1. Open Settings >> Connections >> Wi-Fi. 2. From the hamburger menu, select Wi-Fi Direct. 3. Verify that Wi-Fi Direct cannot be selected. If on the management tool "Wi-Fi Direct" is not set to "Disallow", or on the Google Android device a Wi-Fi Direct device is listed that can be connected to, this is a finding.

Fix: F-71277r1042522_fix

Configure the Google Android devices to disallow Wi-Fi Direct. On the management tool, do the following: COBO: 1. Find "User Restrictions" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and toggle that to "ON". COPE: 1. Find "User Restrictions on Parent" and select "Set User Restrictions". 2. Scroll down to "Disallow Wi-Fi Direct" and toggle that to "ON".

b

Google Android 15 users must complete required training.

CM-6 - Medium - CCI-000366 - V-267451 - SV-267451r1033041_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-009800

Vuln IDs

V-267451

Rule IDs

SV-267451r1033041_rule

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. SFRID: NA

Checks: C-71375r1031536_chk

Review a sample of site User Agreements for Google Android 15 device users or similar training records and training course content. Verify that the Google Android 15 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. If any Google Android 15 device user has not completed the required training, this is a finding.

Fix: F-71278r1033040_fix

All Google Android 15 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): - Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. - Need to ensure no DOD data is saved to the personal space or transmitted from a personal app (for example, from personal email). - 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. - How to configure the following UBE controls (users must configure the control) on the Google device: **Secure use of Calendar Alarm. **Local screen mirroring and mirroring procedures (authorized/not authorized for use). **Do not upload DOD contacts via smart call and caller ID services. **Do not configure a DOD network (work) VPN profile on any third-party VPN client installed in the personal space. **If Bluetooth connections are approved for mobile device, types of allowed connections (for example car hands-free, but not Bluetooth wireless keyboard). **How to perform a full device wipe. **Use default Wi-Fi hotspot password: 15-character complex Wi-Fi hotspot preshared password enabled ("WPA2/WPA3-personal"). - 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.

b

Google Android 15 must be configured to disable Wi-Fi Sharing.

CM-6 - Medium - CCI-000366 - V-267452 - SV-267452r1031541_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-009900

Vuln IDs

V-267452

Rule IDs

SV-267452r1031541_rule

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. SFRID: FMT_SMF_EXT.1.1 / WLAN #3

Checks: C-71376r1031539_chk

Review device configuration settings to confirm Wi-Fi Sharing is disabled. Mobile Hotspot must be enabled to enable Wi-Fi Sharing. If the Authorizing Official (AO) has not approved Mobile Hotspot, and it has been verified as disabled on the EMM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to verify Wi-Fi Sharing is disabled: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow sharing admin configured Wi-Fi" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". If on the EMM console, "Disallow sharing admin configured Wi-Fi" is not enabled, this is a finding.

Fix: F-71279r1031540_fix

Configure the Google Android 15 device to disable Wi-Fi Sharing. Mobile Hotspot must be enabled to enable Wi-Fi Sharing. If the AO has not approved Mobile Hotspot, and it has been disabled on the EMM console, no further action is needed. If Mobile Hotspot is being used, use the following procedure to disable Wi-Fi Sharing: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow sharing admin configured Wi-Fi" to "ON".

b

Google Android 15 must be configured to enforce a password for Wi-Fi and Bluetooth hotspot, if approved for use by the approving authority (AO). If not approved for use, Wi-Fi and Bluetooth hotspot must be disabled.

CM-6 - Medium - CCI-000366 - V-267453 - SV-267453r1031544_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-009950

Vuln IDs

V-267453

Rule IDs

SV-267453r1031544_rule

Wi-Fi and Bluetooth hotspot use may increase the risk for exposing sensitive DOD data for some use cases, therefore it should be disabled unless approved by the AO. When a DOD mobile phone is used as a Wi-Fi or Bluetooth hotspot, a hotspot password must be enabled, otherwise unauthorized devices could connect to the DOD hotspot which may increase the risk of exposure of sensitive DOD data and/or a performance degradation of the DOD mobile phone. SFRID: FMT_SMF_EXT.1.1 / WLAN #3

Checks: C-71377r1031542_chk

Review device configuration, user training, and determine if the AO has approved hotspot use. If the AO has not approved hotspot use, verify hotspot use has been disabled: On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow config tethering" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON". On the managed Google Android 15 device: COBO and COPE: 1. Go to Settings >> Network & Internet. 2. Verify "Hotspot & tethering" is "Controlled by admin". 3. Verify that tapping "Hotspot & tethering" provides a prompt to the user specifying "Action not allowed". If on the managed Google Android 15 device "Hotspot & tethering" is enabled, this is a finding. If hotspot use has been approved, verify the user has been trained to use the default hotspot password. Refer to GOOG-15-009800 for procedure. If users are not trained to use the default hotspot password, this is a finding.

Fix: F-71280r1031543_fix

Disable hotspot functions on the DOD phone if not approved by the AO. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config tethering" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config tethering" to "ON". If the use of Wi-Fi and Bluetooth hotspots has been approved by the AO, train the user to not change the default hotspot password (refer to GOOG-15-009800). (By default, when Wi-Fi Hotspot is enabled, a 15-character complex password is automatically configured for the hotspot.

b

Google Android 15 must have the DOD root and intermediate PKI certificates installed.

CM-6 - Medium - CCI-000366 - V-267454 - SV-267454r1031547_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-010000

Vuln IDs

V-267454

Rule IDs

SV-267454r1031547_rule

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. SFRID: FMT_SMF.1.1 #11

Checks: C-71378r1031545_chk

Review device configuration settings to confirm that the DOD root and intermediate PKI certificates are installed. This procedure is performed on both the EMM Administration console and the managed Google Android 15 device. The current DOD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet). On the EMM 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. On the managed Google Android 15 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "Advanced". 4. Tap "More security & privacy". 5. Tap "Encryption & credentials". 6. Tap "Trusted credentials". 7. Verify that DOD root and intermediate PKI certificates are listed under the "User" tab in the "Work" section. If on the EMM console the DOD root and intermediate certificates are not listed in a profile, or the managed Android 15 device does not list the DOD root and intermediate certificates under the user tab, this is a finding.

Fix: F-71281r1031546_fix

Configure the Google Android 15 device to install DOD root and intermediate certificates. On the EMM console, upload DOD root and intermediate certificates as part of a device and/or work profile. The current DOD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://cyber.mil/pki-pke (for NIPRNet).

b

The Google Android 15 work profile must be configured to enforce the system application disable list.

CM-6 - Medium - CCI-000366 - V-267455 - SV-267455r1033044_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-010200

Vuln IDs

V-267455

Rule IDs

SV-267455r1033044_rule

The system application disable list controls user access to/execution of all core and preinstalled applications. Core application: Any application integrated into Google Android 15 by Google. Preinstalled application: Additional noncore applications included in the Google Android 15 build by Google or the wireless carrier. Some system applications can compromise DOD data or upload users' information to non-DOD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DOD data or DOD user information. The site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DOD use by configuring the system application disable list. SFRID: FMT_SMF.1.1 #47

Checks: C-71379r1033042_chk

Review the managed Google Android 15 work profile configuration settings to confirm the system application disable list is enforced. This setting is enforced by default. Verify only approved system apps have been placed on the core allow list. This procedure is performed on the EMM Administrator console. Review the system app allow list and verify only approved apps are on the list. COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Verify package names of apps are listed. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Verify package names of apps are listed. If on the EMM console the system app allow list contains unapproved core apps, this is a finding.

Fix: F-71282r1033043_fix

Configure the Google Android 15 device to enforce the system application disable list. The 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: On the EMM console: COBO: 1. Open "Apps management" section. 2. Select "Hide apps". 3. Enter package names of apps to hide. COPE: 1. Open "Apps management" section. 2. Select "Hide apps on parent". 3. Enter package names of apps to hide. Configure a list of approved Google core and preinstalled apps in the core app allow list.

b

The Google Android 15 work profile must be configured to disable automatic completion of workspace internet browser text input.

CM-6 - Medium - CCI-000366 - V-267456 - SV-267456r1031553_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-010400

Vuln IDs

V-267456

Rule IDs

SV-267456r1031553_rule

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 Android 15 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. SFRID: FMT_SMF.1.1 #47

Checks: C-71380r1031551_chk

Review the work profile Chrome Browser app on the Google Android 15 autofill setting. This procedure is performed only on the EMM Administrator console. On the EMM console: COBO: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify "PasswordManagerEnabled" is turned "OFF". 4. Verify "AutofillAddressEnabled" is turned "OFF". 5. Verify "AutofillCreditCardEnabled" is turned "OFF". COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Verify "PasswordManagerEnabled" is turned "OFF". 4. Verify "AutofillAddressEnabled" is turned "OFF". 5. Verify "AutofillCreditCardEnabled" is turned "OFF". If on the EMM console any of the browser autofill settings are set to "On" in the Chrome Browser Settings, this is a finding.

Fix: F-71283r1031552_fix

Configure the Chrome browser on the Google Android 15 device work profile to disable autofill. On the EMM console: COBO: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "PasswordManagerEnabled" is turned "OFF". 4. Ensure "AutofillAddressEnabled" is turned "OFF". 5. Ensure "AutofillCreditCardEnabled" is turned "OFF". COPE: 1. Open "Managed Configurations" section. 2. Select the Chrome Browser version from the work profile. 3. Ensure "PasswordManagerEnabled" is turned "OFF". 4. Ensure "AutofillAddressEnabled" is turned "OFF". 5. Ensure "AutofillCreditCardEnabled" is turned "OFF". Refer to the EMM documentation to determine how to configure Chrome Browser Settings.

b

The Google Android 15 work profile must be configured to disable the autofill services.

CM-6 - Medium - CCI-000366 - V-267457 - SV-267457r1031556_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-010500

Vuln IDs

V-267457

Rule IDs

SV-267457r1031556_rule

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 Android 15 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. SFRID: FMT_SMF.1.1 #47

Checks: C-71381r1031554_chk

Review the Google Android 15 work profile configuration settings to confirm that autofill services are disabled. This procedure is performed only on the EMM Administration console. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disable autofill" is toggled to "ON". COPE: 1. Open "Set user restrictions". 2. Verify "Disable autofill" is toggled to "ON". If on the EMM console "disallow autofill" is not selected, this is a finding.

Fix: F-71284r1031555_fix

Configure the Google Android 15 device work profile to disable the autofill services. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disable autofill" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disable autofill" to "ON".

b

Google Android 15 must be configured to disallow configuration of date and time.

CM-6 - Medium - CCI-000366 - V-267458 - SV-267458r1031559_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

GOOG-15-010600

Vuln IDs

V-267458

Rule IDs

SV-267458r1031559_rule

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 Google Android 15 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), the Global Positioning System (GPS), or the wireless carrier. Time stamps generated by the audit system in Google Android 15 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. SFRID: FMT_SMF.1.1 #47

Checks: C-71382r1031557_chk

Review the managed Google Android 15 device configuration settings to confirm that autofill services are disabled. This procedure is performed on both the EMM Administration console and the managed Google Android 15 device. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow config date time" is toggled to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Verify "Disallow config date time" is toggled to "ON". On the managed Google Android 15 device: COBO and COPE: 1. Open Settings. 2. Tap "System". 3. Tap "Date & time". 4. Verify "Set time automatically" is greyed out and is "Enabled by admin". If on the EMM console "Disallow config date time" is not set to "On", or on the managed Android 15 device "Set time automatically" is not greyed out, this is a finding.

Fix: F-71285r1031558_fix

Configure the Google Android 15 device to set auto network time. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow config date time" to "ON". COPE: 1. Open "Set user restrictions on parent". 2. Toggle "Disallow config date time" to "ON".

c

Android 15 devices must have the latest available Google Android 15 operating system installed.

CM-6 - High - CCI-000366 - V-267459 - SV-267459r1031562_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

GOOG-15-010800

Vuln IDs

V-267459

Rule IDs

SV-267459r1031562_rule

Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions. SFRID: FMT_SMF.1.1 #47

Checks: C-71383r1031560_chk

Review device configuration settings to confirm the Google Android device has the most recently released version of managed Google Android 15 installed. This procedure is performed on both the EMM console and the managed Google Android 15 device. In the EMM management console, review the version of Google Android 15 installed on a sample of managed devices. This procedure will vary depending on the EMM product. On the managed Google Android 15 device, to determine the installed operating system version: COBO and COPE: 1. Open "Settings". 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Google Android 15 operating system on any reviewed device is not the latest released by Google, this is a finding. Google's Android operating system patch website: https://source.android.com/security/bulletin/. Android versions for Pixel devices: https://developers.google.com/android/images.

Fix: F-71286r1031561_fix

Install the latest released version of the Google Android 15 operating system on all managed Google devices. Note: Google Android device operating system updates are released directly by Google or can be distributed via the EMM. Check each device manufacturer and/or carriers for current updates.

a

Android 15 devices must be configured to disable the use of third-party keyboards.

CM-6 - Low - CCI-000366 - V-267460 - SV-267460r1033046_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-15-010900

Vuln IDs

V-267460

Rule IDs

SV-267460r1033046_rule

Many third-party keyboard applications are known to contain malware. SFRID: FMT_SMF.1.1 #47

Checks: C-71384r1031563_chk

Review the managed Google Android 15 configuration settings to confirm that no third-party keyboards are enabled. This procedure is performed on the EMM console. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Verify only the approved keyboards are selected. If third-party keyboards are allowed, this is a finding.

Fix: F-71287r1033045_fix

Configure the Google Android 15 device to disallow the use of third-party keyboards. On the EMM console: COBO and COPE: 1. Open "Input methods". 2. Tap "Set input methods". 3. Select only the approved keyboard. Additionally, Admins can configure application allow lists for Google Play that do not have any third-party keyboards for user installation.

a

Android 15 devices must be configured to enable Common Criteria Mode (CC Mode).

CM-6 - Low - CCI-000366 - V-267461 - SV-267461r1031568_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

GOOG-15-011000

Vuln IDs

V-267461

Rule IDs

SV-267461r1031568_rule

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. SFRID: FMT_SMF.1.1 #47

Checks: C-71385r1031566_chk

Review the managed Google Android 15 configuration settings to confirm CC mode is enabled. This procedure is performed on the EMM console. COBO and COPE: 1. Open Device owner management. 2. Verify "Enable Common Criteria mode" is toggled to "ON". If CC mode is not enabled, this is a finding.

Fix: F-71288r1031567_fix

Configure the Google Android 15 device to implement CC Mode. On the EMM console: COBO and COPE: 1. Open Device owner management. 2. Toggle "Enable Common Criteria mode" to "ON".

b

Google Android 15 must be configured to disable all data signaling over [assignment: list of externally accessible hardware ports (for example, USB)].

AC-6 - Medium - CCI-002235 - V-267462 - SV-267462r1033049_rule

RMF Control

AC-6

Severity

Medium

CCI

CCI-002235

Version

GOOG-15-012200

Vuln IDs

V-267462

Rule IDs

SV-267462r1033049_rule

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. SFRID: FMT_MOF_EXT.1.2 #24

Checks: C-71386r1033047_chk

Review the device configuration to confirm that the USB port is disabled except for charging the device. On the EMM console: 1. Open "Set user restrictions". 2. Verify “Disallow USB file transfer” is set to "ON". If on EMM console the USB port is not disabled (“Disallow USB file transfer” is set to "ON"), this is a finding.

Fix: F-71289r1033048_fix

Configure Google Android 15 device to disable the USB port (except for charging the device). COPE and COBO: On the EMM console: 1. Open "Set user restrictions". 2. Toggle “Disallow USB file transfer” to "ON".

b

The Google Android 15 must allow only the administrator (EMM) to install/remove DOD root and intermediate PKI certificates.

CM-6 - Medium - CCI-000370 - V-267463 - SV-267463r1033052_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000370

Version

GOOG-15-012300

Vuln IDs

V-267463

Rule IDs

SV-267463r1033052_rule

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. SFRID: FMT_MOF_EXT.1.2 #47

Checks: C-71387r1033050_chk

Review the device configuration to confirm that the user is unable to remove DOD root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Verify "Disallow config credentials" is toggled to "ON". On the Google Android 15 device: 1. Open Settings. 2. Tap "Security & privacy". 3. Tap "More security & privacy". 4. Tap "Encryption & credentials". 5. Tap "Trusted credentials". 6. Verify the user is unable to untrust or remove any work certificates. If on the Google Android 15 device the user is able to remove certificates, this is a finding.

Fix: F-71290r1033051_fix

Configure Google Android 15 device to prevent a user from removing DOD root and intermediate PKI certificates. On the EMM console: 1. Open "Set user restrictions". 2. Toggle "Disallow config credentials" to "ON".

a

Google Android 15 must allow only the administrator (MDM) to perform the following management function: Disable Phone Hub.

SC-4 - Low - CCI-001090 - V-267464 - SV-267464r1033054_rule

RMF Control

SC-4

Severity

Low

CCI

CCI-001090

Version

GOOG-15-012400

Vuln IDs

V-267464

Rule IDs

SV-267464r1033054_rule

It may be possible to transfer work profile data on a DOD Android device to an unauthorized Chromebook if the user has the same Google Account set up on the Chromebook and in the work profile on the Android device. This may result in the exposure of sensitive DOD data. SFRID: FMT_MOF_EXT.1.2 #47

Checks: C-71388r1033053_chk

Review the EMM configuration to confirm phone hub has been disabled. On the management tool: 1. Open "Nearby notification streaming policy". 2. Verify "Nearby notification streaming policy" is set to "Disabled". 3. Open "Nearby app streaming policy". 4. Verify "Nearby app streaming policy" is set to "Disabled". If on the management tool the "Nearby Streaming Policy" is not set to "Disabled" and "Nearby app streaming policy" is not set to "Disabled", this is a finding. Note: From a Chromebook, if a device is connected to the Phone Hub, try to set up the Notifications. It will fail to connect to the device to complete the setup if phone hub has been disabled on the DOD Android device.

Fix: F-71291r1031576_fix

Configure Google Android 15 device to disable the nearby notification streaming policy to disable Phone Hub. COPE and COBO: On the EMM console: 1. Open "Nearby notification streaming policy". 2. Set "Nearby notification streaming policy" to "Disabled". 3. Open "Nearby app streaming policy". 4. Set "Nearby app streaming policy" to "Disabled".

c

Google Android 15 must be configured to disable "Private Space" use.

CM-6 - High - CCI-000370 - V-269100 - SV-269100r1033116_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000370

Version

GOOG-15-012500

Vuln IDs

V-269100

Rule IDs

SV-269100r1033116_rule

Private Space is an Android feature that provides a separate encrypted container on the mobile device. Apps in Private Space show up in a separate container in the launcher and are hidden from the "Recents" view, notifications, settings, and other apps when the Private Space is locked. In addition, MDM server allow list or blocklist cannot control the installation of apps into Private Space. Malware and other unauthorized apps could be installed on a DOD mobile device, which could lead to the compromise of DOD sensitive information or to an attack on the DOD network. SFRID: FMT_MOF_EXT.1.2 #47

Checks: C-73131r1032063_chk

Review the Google Android 15 work profile configuration settings to confirm that Private Space is disabled. This procedure is performed only on the EMM Administration console. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify "Disallow add private profile" is set to "ON". COPE: 1. Open "Set user restrictions". 2. Verify "Disallow add private profile" is set to "ON". If on the EMM console "Disallow add private profile" is not selected, this is a finding.

Fix: F-73032r1032064_fix

Configure the Google Android 15 device to disable "Private Space". On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON".

Google Android 15 COBO Security Technical Implementation Guide

Compare

View

Checks: C-71354r1031473_chk

Fix: F-71257r1031474_fix

Generate Mitigation Statement:

Checks: C-71355r1031476_chk

Fix: F-71258r1031477_fix

Generate Mitigation Statement:

Checks: C-71356r1031479_chk

Fix: F-71259r1031480_fix

Generate Mitigation Statement:

Checks: C-71357r1031482_chk

Fix: F-71260r1031483_fix

Generate Mitigation Statement:

Checks: C-71358r1033026_chk

Fix: F-71261r1031486_fix

Generate Mitigation Statement:

Checks: C-71359r1031488_chk

Fix: F-71262r1031489_fix

Generate Mitigation Statement:

Checks: C-71360r1033110_chk

Fix: F-71263r1033111_fix

Generate Mitigation Statement:

Checks: C-71361r1033030_chk

Fix: F-71264r1033031_fix

Generate Mitigation Statement:

Checks: C-71362r1042518_chk

Fix: F-71265r1042519_fix

Generate Mitigation Statement:

Checks: C-71363r1031500_chk

Fix: F-71266r1031501_fix

Generate Mitigation Statement:

Checks: C-71364r1031503_chk

Fix: F-71267r1031504_fix

Generate Mitigation Statement:

Checks: C-71365r1033035_chk

Fix: F-71268r1031507_fix

Generate Mitigation Statement:

Checks: C-71366r1031509_chk

Fix: F-71269r1031510_fix

Generate Mitigation Statement:

Checks: C-71367r1031512_chk

Fix: F-71270r1031513_fix

Generate Mitigation Statement:

Checks: C-71368r1031515_chk

Fix: F-71271r1031516_fix

Generate Mitigation Statement:

Checks: C-71369r1031518_chk

Fix: F-71272r1031519_fix

Generate Mitigation Statement:

Checks: C-71370r1031521_chk

Fix: F-71273r1031522_fix

Generate Mitigation Statement:

Checks: C-71371r1033113_chk

Fix: F-71274r1033114_fix

Generate Mitigation Statement:

Checks: C-71372r1033037_chk

Fix: F-71275r1033038_fix

Generate Mitigation Statement:

Checks: C-71373r1031530_chk

Fix: F-71276r1031531_fix

Generate Mitigation Statement:

Checks: C-71374r1042521_chk

Fix: F-71277r1042522_fix

Generate Mitigation Statement:

Checks: C-71375r1031536_chk

Fix: F-71278r1033040_fix

Generate Mitigation Statement:

Checks: C-71376r1031539_chk

Fix: F-71279r1031540_fix

Generate Mitigation Statement:

Checks: C-71377r1031542_chk

Fix: F-71280r1031543_fix

Generate Mitigation Statement:

Checks: C-71378r1031545_chk

Fix: F-71281r1031546_fix

Generate Mitigation Statement:

Checks: C-71379r1033042_chk

Fix: F-71282r1033043_fix