Password/passcode maximum failed attempts must be set to required value.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-25011	WIR-MOS-AND-G-017	SV-35024r1_rule	IAIA-1	Medium

Description
A hacker with unlimited attempts can determine the password of a smartphone within a few minutes using password hacking tools, which could lead to unauthorized access to the smartphone and exposure to sensitive DoD data.

STIG	Date
Android 2.2 (Dell) Security Technical Implementation Guide	2011-11-28

Details

Check Text ( C-34900r1_chk )
This is a Good security policy set check. Recommend all checks related to Good security policy set rules be reviewed using the following procedure. 1. Make a list of all Good security policy sets assigned to smartphone user accounts on the Good server using the following procedure: --Have the SA identify any non STIG-compliant policy sets and STIG-compliant policy sets on the server. --Log into the Good Mobile Control console. --Click on the Policies tab. --View all policy set on the server. -Note: STIG-compliant policy sets should be identified as such in the policy title, for example, STIG_Android_Policy_Set. It is recommended all non STIG-compliant policy sets be deleted. 2. Select each policy set users are assigned to, and in turn, verify the required settings are in the policy set. Note: If there is a finding, note the name of the non STIG-compliant policy set in the Findings Details section in VMS/Component Provided Tracking Database. --------------------- -Launch the Good Mobile Control Web console and click on the Policies tab. -Select the policy set for the Android devices and click on Android Configuration on the left side. -Click the Passcode tab. -Verify “Maximum failed attempts” is checked and set to 10 or less. Mark as a finding if configuration is not set as required.

Check Text ( C-34900r1_chk )

This is a Good security policy set check. Recommend all checks related to Good security policy set rules be reviewed using the following procedure.

1. Make a list of all Good security policy sets assigned to smartphone user accounts on the Good server using the following procedure:

--Have the SA identify any non STIG-compliant policy sets and STIG-compliant policy sets on the server.
--Log into the Good Mobile Control console.
--Click on the Policies tab.
--View all policy set on the server.

-Note: STIG-compliant policy sets should be identified as such in the policy title, for example, STIG_Android_Policy_Set. It is recommended all non STIG-compliant policy sets be deleted.

2. Select each policy set users are assigned to, and in turn, verify the required settings are in the policy set.

Note: If there is a finding, note the name of the non STIG-compliant policy set in the Findings Details section in VMS/Component Provided Tracking Database.
---------------------

-Launch the Good Mobile Control Web console and click on the Policies tab.
-Select the policy set for the Android devices and click on Android Configuration on the left side.
-Click the Passcode tab.
-Verify “Maximum failed attempts” is checked and set to 10 or less.

Mark as a finding if configuration is not set as required.

Fix Text (F-27662r2_fix)
Set password/passcode maximum failed attempts to required value.