Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets and FIPS 140-2 certificate. Verify the devices have a VPN client installed and is FIPS 140-2 validated. Check the NIST certificate for the mobile OS or VPN client. Mark as a finding if the VPN is not FIPS 140-2 validated
Comply with policy requirement.
This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets. Verify AES encryption is enabled for the VPN client. Mark as a finding if AES is not supported or is not enabled
Comply with policy requirement.
This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Verify the VPN client supports CAC authentication to the DoD network (recommend asking the site wireless device administrator to demo this capability). Mark as a finding if CAC authentication is not supported.
Comply with policy requirement.
This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Check to see if the VPN has a setting to disable split tunneling. Verify split tunneling has been disabled. Mark not applicable if the VPN is not used for remote access to a DoD network
Comply with policy requirement.
-Verify the Windows Phone version 6.5 or later: --Log into the Windows Phone. --Go to Settings > General > About >Version. -Verify the Good App version is 6.0.1.x or later: --Log into the Windows Phone device. --Launch the Good app and enter login info. --Go to Preferences > About. Mark as a finding if either version is not as required.
Install required OS version.
Verify the following: For the Apriva SCR, the firmware is 03.30.08 or later and the SCR driver is 01.05.06 or later. For the BAL SCR, the firmware is 1.3.4.12 or later.
Install required SCR software version.
Verify the auto-signature, if used, meets requirements. -Check a random sample of 3-4 devices. -On the handheld, launch the Good client and go to Preferences > Signature. Mark as a finding if the device has been configured with an auto-signature and signature states the email originated from a smartphone.
Ensure the smartphone email auto-signature message does not disclose the email originated from a smartphone or a mobile device (e.g., “Sent From My Wireless Handheld”).
-Select 3-4 random devices managed by the site to review. -Make a list of non-core applications on each device. --Have the user log into the device. View all App icons on the home screen or in folders on the home screen. --If an App is not in the list of core Apps (see below), then note the name of the App. --Verify the site has written approval to use the App from the DAA or site IT CCB. -Mark as a finding if any App has not been approved. A list of standard core Windows Phone 6.5 device Apps can be found in the STIG Configuration Tables document. Note: The DAA or IT CCB should also indicate if location services are approved for any approved applications, including core applications (e.g., camera, maps, etc.).
Have DAA or Command IT CCB review and approve all non-core applications on mobile OS devices.
The following banner is required: “I've read & consent to terms in IS user agreem't.” Check Procedure: Verify that when the Good App is launched the banner is displayed on the screen. The banner must exactly match the required phrase.
Display the required banner during device unlock/logon.