|Finding ID||Version||Rule ID||IA Controls||Severity|
|Sensitive DoD data is saved inside the Good app and could be exposed if strong authentication is not implemented.|
|Good Mobility Suite Server (Apple iOS 4) Interim Security Configuration Guide (ISCG)||2011-11-07|
|Check Text ( C-34034r1_chk )|
| This check is not applicable if “Authenticate with CAC PIN” is checked. |
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/ISCG-compliant policy sets and STIG/ISCG-compliant policy sets on the server.
--Log into the Good Mobile Control console.
--Click on the Policies tab.
--View all policy sets on the server.
-Note: STIG-compliant policy sets should be identified as such in the policy title. Examples are as follows: ISCG_iOS_Policy_Set, STIG_WM6-5_Policy_Set, or STIG_Android_Policy_Set. It is recommended that all non-STIG/ISCG 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/ISCG-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 smartphone and click on Handheld Authentication on the left side.
-Verify “Require both letters and numbers” is checked.
Mark as a finding if “Require both letters and numbers” is not checked.
|Fix Text (F-29716r1_fix)|
|Set “Require both letters and numbers” as required for the Good app.|