Detections
Analytics
GOOG-16-006400 - Google Android 16 must be configured to not allow more than 10 consecutive failed authentication attempts.
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or fewer gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password.SFR ID: FMT_SMF.1.1 #2, FIA_AFL_EXT.1.5
Solution
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()
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Google_Android_16_Y26M04_STIG.zip
Item Details
Audit Name: AirWatch - DISA Google Android 16 COBO STIG v1r2
References: CAT|II, CCI|CCI-000044, Rule-ID|SV-276752r1140048_rule, STIG-ID|GOOG-16-006400, Vuln-ID|V-276752
Plugin: MDM
Control ID: c446e54e1b4223c4b75f2692e7fcbb82c6397debebfebca046d399ff78ac03b7