A compliance rule must be set up on the server defining required Good client versions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-26728	WIR-GMMS-AND-010-04	SV-34968r1_rule	ECWN-1	Low

Description
Older software versions do not support required security features.

STIG	Date
Good Mobility Suite Server (Android OS) Security Technical Implementation Guide	2011-12-14

Details

Check Text ( C-34845r1_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 sets on the server. -Note: STIG-compliant policy sets should be identified as such in the policy title. Examples are as follows: STIG_iOS_Policy_Set, STIG_WM6-5_Policy_Set, or STIG_Android_Policy_Set. It is recommended that all non-STIG 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 a policy set to review and click on the policy. -On the left tab, select Compliance Manager. -Verify the “Client Version Verification” rule is listed. (Note: The rule title does not have to be exact.) -Open the rule by checking the box next to the rule, and then click on Edit. -Verify the following are set: Platform: Android Check to Run: Hardware Model Verification -Verify the client version checked is at least 1.7.x. -Verify "Failure Action" is set to "Quit Good for Enterprise". -Verify "Check Every" is set to "1 hour". Mark as a finding if the “Client Version Verification” rule has not been set up or is not configured as required.

Check Text ( C-34845r1_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 sets on the server.

-Note: STIG-compliant policy sets should be identified as such in the policy title. Examples are as follows: STIG_iOS_Policy_Set, STIG_WM6-5_Policy_Set, or STIG_Android_Policy_Set. It is recommended that all non-STIG 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 a policy set to review and click on the policy.

-On the left tab, select Compliance Manager.
-Verify the “Client Version Verification” rule is listed. (Note: The rule title does not have to be exact.)
-Open the rule by checking the box next to the rule, and then click on Edit.

-Verify the following are set:
Platform: Android
Check to Run: Hardware Model Verification

-Verify the client version checked is at least 1.7.x.

-Verify "Failure Action" is set to "Quit Good for Enterprise".

-Verify "Check Every" is set to "1 hour".

Mark as a finding if the “Client Version Verification” rule has not been set up or is not configured as required.

Fix Text (F-30027r1_fix)
Set up a compliance rule to check the version of the Good client.