STIGQter: STIG Summary: Google Android 16 COPE Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 13 May 2026:

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

DISA Rule

SV-276854r1140354_rule

Vulnerability Number

V-276854

Group Title

PP-MDF-333040

Rule Version

GOOG-16-006400

Severity

CAT II

CCI(s)

• CCI-000044 - Enforce the organization-defined limit of consecutive invalid logon attempts by a user during the organization-defined time period.

Weight

10

Fix Recommendation

Configure the Google Android 16 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.

Configuration API: setMaximumFailedPasswordsForWipe()

Check Contents

Review managed Google Android 16 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 16 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 16 device:

COBO and COPE:

1. Lock the device screen.
2. Attempt to unlock the screen and validate that the device autowipes after the 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 for a maximum number of consecutive failed authentication attempts of 10 or fewer, or if on the managed Google Android 16 device the device policy is not set for a maximum number of consecutive failed authentication attempts of 10 or fewer, this is a finding.

Vulnerability Number

V-276854

Documentable

False

Rule Version

GOOG-16-006400

Severity Override Guidance

Review managed Google Android 16 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 16 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 16 device:

COBO and COPE:

1. Lock the device screen.
2. Attempt to unlock the screen and validate that the device autowipes after the 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 for a maximum number of consecutive failed authentication attempts of 10 or fewer, or if on the managed Google Android 16 device the device policy is not set for a maximum number of consecutive failed authentication attempts of 10 or fewer, this is a finding.

Check Content Reference

M

Target Key

5717