acceptedApple iOS6 Security Technical Implementation GuideDeveloped by DISA for use in the DoD. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.DISA, Field Security OperationsSTIG.DOD.MILRelease: 3 Benchmark Date: 24 Oct 20141I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>Remote access VPN - FIPS 140-2<GroupDescription></GroupDescription>WIR-MOS-iOS-034-01The VPN client on mobile devices used for remote access to DoD networks must be FIPS 140-2 validated. <VulnDiscussion>DoD data could be compromised if transmitted data is not secured with a compliant VPN. FIPS validation provides a level of assurance that the encryption of the device has been securely implemented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install a VPN client that uses FIPS 140-2 validated cryptographic modules to protect data in transit.This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
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 VPN client leverages FIPS 140-2 validated cryptographic modules. It may accomplish this either by using its own FIPS 140-2 validated cryptographic module or the FIPS 140-2 validated Apple iOS CoreCrypto Kernel Module. Only VPN client applications that Apple has granted the VPN entitlement have the capability to leverage this module. Verify the VPN client has the Apple iOS VPN entitlement or check that it has its own FIPS 140-2 certificate.
If the VPN client does not leverage FIPS 140-2 validated cryptography, this is a finding.Remote access VPN - AES encryption<GroupDescription></GroupDescription>WIR-MOS-iOS-034-02All mobile device VPN clients used for remote access to DoD networks must support AES encryption. <VulnDiscussion>DoD data could be compromised if transmitted data is not secured with a compliant VPN.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install an AES Encrypted VPN client. This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets and the configuration of the VPN client. Verify the VPN client supports AES encryption. Verify the VPN client is configured to required AES. Mark as a finding if the VPN does not support AES or is not configured to require AES.Remote access VPN - CAC authentication<GroupDescription></GroupDescription>WIR-MOS-iOS-034-03All mobile device VPN clients used for remote access to DoD networks must be configured to require CAC authentication. <VulnDiscussion>DoD data could be compromised if transmitted data is not secured with a compliant VPN.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install a VPN client that supports CAC authentication and configure the client to require CAC authentication.This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets and verify the VPN client support CAC authentication. Mark as a finding if the VPN does not support CAC authentication or the client is not configured to require CAC authentication.Remote access VPN - split tunneling<GroupDescription></GroupDescription>WIR-MOS-iOS-034-04All mobile device VPN clients must have split tunneling disabled. <VulnDiscussion>DoD data could be compromised if transmitted data is not secured with a compliant VPN. Split tunneling could allow connections from non-secure Internet sites to access data on the DoD network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable split tunneling on VPN client. This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets and verify the VPN client supports disabling split tunneling. Verify the VPN client is configured disable split tunneling. Mark as a finding if the VPN does not support disabling split tunneling or it is not disabled on the client.Use approved SCR software version<GroupDescription></GroupDescription>WIR-MOS-iOS-002Smart Card Readers (SCRs) used with CMDs must have required software version installed.<VulnDiscussion>Required security features are not available in earlier software versions. In addition, there may be known vulnerabilities in earlier versions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install required SCR software version. Detailed Policy Requirements:
If a Bluetooth smart card reader is used, only the following models and firmware versions should be used:
SCR: Biometric Associates, LP (BAL) baiMobile BAL-3000MP Bluetooth Smart Card Reader. Firmware version v2.01.00 or later should be used (version v2.02.00 is recommended).
Bluetooth adapter: Biometric Associates, LP (BAL) baiMobile BAL-BTA001 Bluetooth Adapter. Firmware version 1.4.0 or later should be used (version 1.4.4 is recommended).
Check Procedures:
SCR: The version of the reader firmware is displayed when the user presses and holds the Action button on the reader for a couple of seconds after the CAC is inserted into the reader.
Bluetooth adapter: Model and firmware are printed on the label attached to the adapter.
For wired smart card readers, check to see if the vendor has completed JITC PKI interoperability testing. Ask to see a copy of the JITC certification. The firmware version should be the same as listed in the JITC certification (or later version).
Mark as a finding if the firmware version on the SCR and adapter are not the approved versions.S/MIME installed on CMD<GroupDescription></GroupDescription>WIR-MOS-iOS-003S/MIME must be installed on mobile device, so users can sign/encrypt email.<VulnDiscussion>S/MIME provides the capability for users to send and receive S/MIME email messages from wireless email devices. S/MIME and digital signatures provide assurance the message is authentic and is required by DoD policy. Without S/MIME users will not be able to read encrypted email and will not be able to encrypt email with sensitive information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Provision the mobile email client with S/MIME so users can digitally sign and encrypt email.Launch the mobile email client and verify S/MIME is installed in the client. The exact procedures will depend on which mobile email product is being used.
Mark as a finding if the mobile email client does not have S/MIME configured.
If the mobile email client does not have S/MIME configuration settings that can be viewed on the device, try to send a signed encrypted message to a known recipient and verify the recipient can decrypt and verify the digital signature. Mark as a finding if you are unable to send a signed and encrypted message or if the recipient is unable to decrypt and verify the digital signature.
If the Good Technology client is used:
•Log into the iOS device.
•Open the Good application.
•Go to Preferences.
•Verify Smartcard and S/MIME specific settings are listed.User auto-signature on email<GroupDescription></GroupDescription>WIR-MOS-iOS-004If mobile device email auto signatures are used, the signature message must not disclose the email originated from a CMD (e.g., Sent From My Wireless Handheld). <VulnDiscussion>The disclaimer message may give information which may key an attacker in on the device. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the iOS email auto-signature message, so it does not disclose the email originated from the iOS device (e.g., Sent From My Wireless Handheld).
Launch the mobile email client and verify that if the email auto signature feature is used, it is compliant with the requirement. The exact procedures will depend on which mobile email product is being used. Mark as a finding if not compliant.
If the Good Technology client is used:
•Log into the iOS device.
•Open the Good application.
•Go to Preferences > Signature.Use DoD Internet proxy<GroupDescription></GroupDescription>WIR-MOS-iOS-005The browser must direct all traffic to a DoD Internet proxy gateway.
<VulnDiscussion>When using the DoD Internet proxy for iOS device Internet connections, enclave Internet security controls will filter and monitor iOS device Internet connections and reduce the risk that malware could be downloaded on the mobile device.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECSC-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Use a compliant browser implementation on the iOS device.
There are two acceptable implementations for this requirement:
1. The device uses a mobile VPN to route all data traffic to the DoD enclave, which forces all browser traffic to the DoD Internet gateway. Note: This method is only acceptable if the VPN client is configured so that all data downloaded to the mobile device is saved in a FIPS 140-2 validated encrypted container; otherwise, the data at rest requirements in check V-32707/WIR-MOS-iOS-65-09 are not met.
2. The device browser is installed inside an iOS security container and the security container provides the capability to route all browser traffic to the MDM or authorized proxy server where it will be routed to the DoD Internet gateway.
Using a browser without a mobile VPN and installed outside the iOS device security container is not an approved implementation.
Verify one of the approved browser implementations is used. Talk to the IAO and review 3-4 sample devices.
Mark as a finding if a required browser implementation is not used.Allow only approved mobile OS versions<GroupDescription></GroupDescription>WIR-MOS-iOS-030-01Mobile devices must have the required operating system software version installed. <VulnDiscussion>Unapproved OS versions do not support required security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install the required OS version.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify a compliance rule has been set up defining iOS 6 or later as approved versions.
Mark as a finding if the required compliance rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
If the Good Technology MDM server is used, complete the following:
-Launch the MDM console and click on the Policies tab.
-Select the iOS security policy.
-Verify a compliance rule has been set up defining iOS 6 or later versions.
-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 “OS Version Verification” rule is listed. (Note that 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: iPhone
Check to Run: OS Version Verification
Conditions: 6.0 or later
Failure Action: “Quit Good for Enterprise”
Check Every: “6 hours”
Check: “Permit newer (previously unknown) OS versions”
Require device unlock password/passcode<GroupDescription></GroupDescription>WIR-MOS-iOS-G-010Mobile devices must be configured to require a password/passcode for device unlock.
<VulnDiscussion>Sensitive DoD data could be compromised if a device unlock passcode is not set up on a DoD iOS device.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the MDM server to require a passcode for device unlock.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Require passcode” is checked.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Password/Passcode complexity – Allow simple value<GroupDescription></GroupDescription>WIR-MOS-iOS-G-012-01The iOS device password complexity must be set to the required value.
<VulnDiscussion>iOS provides a security mechanism to prevent users from choosing simple passcodes (e.g., 1111). Implementation of this control is an appropriate defense-in-depth measure to mitigate unauthorized use of the device.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>IAIA-1, ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable (uncheck) "Allow simple value" in the iOS policy on the MDM server.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify “Allow simple value” is not checked.
If the required rule is not set up on the MDM server, this is a finding.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Maximum password/passcode age<GroupDescription></GroupDescription>WIR-MOS-iOS-G-013Maximum passcode age must be set.<VulnDiscussion>Sensitive DoD data could be compromised if a strong device unlock passcode is not set up on a DoD iOS device and the passcode is not changed periodically.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>IAIA-1, ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set maximum passcode age to 120 days or less if the DAA requires this setting. Password expiration is only required if the DAA deems it necessary due to the operational risk and mission need. It is most appropriate when, for whatever reason, the iOS device is outside of the user’s possession and readily accessible to others on a regular or periodic basis. If used, the recommended value is 120 days or less. If used, verify the setting has been set correctly using the following procedure:
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Maximum passcode age" is checked and set to 120 days or less in the iOS security policy.
Mark as a finding if the required rule is not set up on the MDM server, if the DAA requires this setting.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Mobile device inactivity timeout<GroupDescription></GroupDescription>WIR-MOS-iOS-G-016The mobile device must be set to lock the device after a set period of user inactivity. <VulnDiscussion>Sensitive DoD data could be compromised if the CMD does not automatically lock after 15 minutes of inactivity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>PESL-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Enforce the CMD inactivity timeout requirement of 15 minutes or less through a combination of "Auto-Lock" and "Grace period" values that do not sum to greater than 15 minutes. 1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify that "Grace period" is checked and the sum of the "Auto-Lock" and "Grace period" values is 15 minutes or less. Acceptable combinations include a 15-minute "Auto-Lock" and an "Immediate" (or null) "Grace period", or a 5-minute "Auto-Lock" and a 5-minute "Grace period". On some MDM systems, the "Grace period" may be called "Passcode Lock" or a similar label.
If the required rule is not set up on the MDM server, this is a finding.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Password/passcode maximum failed attempts<GroupDescription></GroupDescription>WIR-MOS-iOS-G-017Passcode maximum failed attempts must be set to required value.<VulnDiscussion>A hacker with unlimited attempts can determine the password of an iOS device within a few minutes using password hacking tools, which could lead to unauthorized access to the iOS device and exposure to sensitive DoD data.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set password/passcode maximum failed attempts to 10 or less.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Maximum failed attempts” is checked and set to 10 or less.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Public application store<GroupDescription></GroupDescription>WIR-MOS-iOS-G-019Access to public media stores must be disabled.<VulnDiscussion>Strong configuration management of all media installed on DoD devices is required to ensure the security baseline of the system is maintained. Therefore, the ability for the user to download unapproved applications must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECSC-1, ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable access to public media stores. 1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Allow use of iTunes Music Store” is unchecked.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Mobile device application installation<GroupDescription></GroupDescription>WIR-MOS-iOS-G-020Users ability to download iOS applications must be disabled.<VulnDiscussion>Application download must be disabled so that unauthorized applications are not installed on DoD-managed iOS devices. Unauthorized apps may contain malware or may modify the security baseline of the device. This could lead to the exposure of sensitive DoD data. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1, ECLP-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374On the MDM server, set “Allow installing apps” to disabled (unchecked). 1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify “Allow installing apps” is disabled or not checked.
Mark as a finding if the required rule is not set up on the MDM.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Mobile device camera<GroupDescription></GroupDescription>WIR-MOS-iOS-G-021Mobile device cameras must be used only if documented approval is in the site physical security policy.
<VulnDiscussion>This is an operational security issue. DoD sensitive information could be compromised if cameras are allowed in areas not authorized by the site physical security plan.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><Responsibility>Designated Approving Authority</Responsibility><Responsibility>Information Assurance Manager</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable (uncheck) "Allow use of camera" in the iOS policy on the MDM server unless documented approval exists in the site physical security policy.Note: The site has the ability to disable the camera by using the iPhone profile if camera use is not approved, or allow the use of the camera if use is approved and documented in the site physical security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Determine if “Allow use of camera” is unchecked or checked.
If checked, verify the site physical security policy allows the use of CMD cameras.
Mark as a finding if “Allow use of camera” is checked in the iOS policy on the MDM and the site physical security policy does not allow the use of CMD cameras.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Mobile device screen capture<GroupDescription></GroupDescription>WIR-MOS-iOS-G-022Mobile device screen capture must not be allowed.
<VulnDiscussion>Sensitive data, including FOUO data displayed on the screen, could be saved in unsecure memory on the device.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable (uncheck) "Allow screen capture" in the iOS policy on the MDM server.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Allow screen capture” is unchecked.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Minimum password/passcode length<GroupDescription></GroupDescription>WIR-MOS-iOS-G-011The device minimum password/passcode length must be set. <VulnDiscussion>Sensitive DoD data could be compromised if a device unlock password/passcode is not set to required length on DoD CMDs. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the mobile operating system to enforce a minimum length for the device unlock password. Where a security container application is used in lieu of mobile operating system protections, configure the security container application to enforce a minimum length password for entry into the application. 1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Minimum length of" is set to 8 or more in the iOS security policy.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.CMD Auto-Lock<GroupDescription></GroupDescription>WIR-MOS-iOS-G-014Apple iOS Auto-Lock must be set.<VulnDiscussion>The "Auto-lock" feature enforces an inactivity timeout when coupled with a password lock. Without an inactivity timeout, sensitive DoD data on the device could be easily disclosed to anyone who obtains physical possession of the device. The absence of auto-lock would also facilitate the ability of an adversary to install malware on the device. Finally, the "Auto Lock" feature mitigates the risk of denial of service from battery depletion because less power is needed to light the display when the device automatically locks.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>PESL-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set the CMD Auto-Lock to a value other than "Never". Five minutes or less is recommended.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify "Auto-lock" is set to a value other than "Never".
If the required rule is not set up on the MDM server, this is a finding.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Passcode/password history<GroupDescription></GroupDescription>WIR-MOS-iOS-G-015The mobile device passcode/password history setting must be set.<VulnDiscussion>The passcode would be more susceptible to compromise if the user can select frequently used passcodes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set the mobile device passcode history setting to 3 or more if the DAA requires this setting. Password history is only required if the DAA deems it necessary for passwords to expire due to the operational risk and mission need. If used, the recommended value is 3 or more. If used, verify the setting has been set correctly using the following procedure:
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Passcode history” is checked and set to 3 or more in the iOS security policy.
Mark as a finding if the required rule is not set up on the MDM server, if the DAA requires this setting.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Bluetooth Control<GroupDescription></GroupDescription>WIR-MOS-iOS-040-01The mobile device Bluetooth radio must only connect to authorized Bluetooth peripherals.<VulnDiscussion>The Bluetooth radio can be used by a hacker to connect to the iOS device without the knowledge of the user. Sensitive DoD data could be exposed and the hacker could use the device to attack the enclave.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Train the user to not connect the iOS device to unauthorized Bluetooth peripherals. The list of Bluetooth devices the iOS device has connected to should only contain authorized smart card readers (SCR) and headsets. Currently, only Bluetooth SCRs and headsets manufactured by Biometric Associates (BAI) have been approved.
On a sample of site-managed iOS devices (pick 3-4 random devices), verify the iOS device has only been connected to authorized Bluetooth peripherals.
-Have the user log into the device.
-Go to Settings > Bluetooth.
-Verify only approved devices are listed under “Devices”.
Mark as a finding if unauthorized peripherals have been connected to the iOS device. Required logon banner<GroupDescription></GroupDescription>WIR-MOS-iOS-007All mobile devices must display the required banner during device unlock/logon.
<VulnDiscussion> DoD CIO memo requires all CMDs to have a consent banner displayed during logon/device unlock to ensure users understand their responsibilities to safeguard DoD data. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWM-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Display the required banner during device unlock/logon. The following banner is required:
“I've read & consent to terms in IS user agreem't.”
Check Procedure:
On the iOS device, complete the following:
Check a sample of devices (3-4). The procedure will vary, depending on the MDM server used. For iOS, the banner is only displayed when logging into the security container.
The banner must exactly match the required phrase.
Mark as a finding if the required banner is not configured to display during device unlock/logon.
If the Good Technology MDM server is used, complete the following:
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify either password or CAC authentication has been enabled for the MDM agent.
-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 a "Custom" or "iOS DoD Login Banner" 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 Edit.
-Verify "Failure Action" is set to "Quit Good for Enterprise".
-Verify "Check Every" is set to "6 hours".
-Verify Rule File = disclaimer.xml.iOS Safari<GroupDescription></GroupDescription>WIR-MOS-iOS-G-018-01iOS Safari must be disabled.
<VulnDiscussion>The Safari browser does not support FIPS 140-2 validated encryption and CAC authentication to DoD websites. FIPS validation provides a level of assurance that encrypted sensitive data will not be compromised.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, ECSC-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable (uncheck) "Allow use of Safari" in the iOS policy on the MDM server.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Allow use of Safari” is not checked.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Location services<GroupDescription></GroupDescription>WIR-MOS-iOS-042Location services must be turned off unless authorized for use for particular applications, in which case, location services must only be available to the authorized applications.<VulnDiscussion>Mobile device location services allow applications to gather information about the location of the handheld device and possibly forward it to servers located on the Internet. This is an operational security issue for DoD mobile devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Turn off location services during device provisioning and users will not enable the service unless approved for use. Location based services is a User Based Enforcement (UBE) service.
On a sample of 3-4 devices managed by the site, verify iOS Location Services is disabled for all applications unless the site has a letter/memo stating the DAA or the Command Application Configuration Control Board (CCB) has approved location-based services for specific applications (e.g., Google Maps, Camera, etc.).
Go to Settings > Privacy > Location Services. Verify the service is off for all applications or off for unapproved applications.
Mark as a finding if any application not authorized for location services has location services turned on.Wi-Fi - Ask to Join Networks<GroupDescription></GroupDescription>WIR-iOS-005The iOS device Wi-Fi setting Ask to Join Networks must be set to Off at all times (User Based Enforcement (UBE)).
<VulnDiscussion>When “Ask to Join Networks” is set to on, the user is alerted whenever they are in the vicinity of a Wi-Fi hotspot and could be tempted to connect to an unauthorized public hotspot, which could be managed by a hacker. Although the risk of exposing sensitive DoD data is low, setting this configuration as specified is a security best practice. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Information Assurance Officer</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set "Ask to Join Networks" to "Off".
On a sample of site-managed iOS devices (pick 3-4 random devices), have the user turn on and log into the device.
-Go to Settings > Wi-Fi.
-Touch Wi-Fi.
-Check the setting of "Ask to Join Networks".
Verify "Ask to Join Networks" is set to off (not selected).
Mark as a finding if "Ask to Join Networks" is not set to off.Disable online application purchase<GroupDescription></GroupDescription>WIR-MOS-iOS-G-023Access to online application purchases must be disabled.<VulnDiscussion>Strong configuration management of all applications installed on DoD devices is required to ensure the security baseline of the system is maintained. Otherwise, sensitive DoD data could be compromised. Therefore, the ability for the user to download unapproved applications must be disabled.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>DCCB-1, DCCB-2</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable (uncheck) "Allow In-App Purchases" in the iOS policy on the MDM server.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Allow In-App Purchases” is unchecked.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Enable remote full device wipe<GroupDescription></GroupDescription>WIR-MOS-iOS-G-008Remote full device wipe must be enabled.<VulnDiscussion>Sensitive DoD data could be compromised if mobile OS device data could not be wiped when directed by the system administrator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, ECCR-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Enable remote full device wipe on iOS devices.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify the MDM has a setting that will wipe all data and non-core applications when a wipe commend is sent to managed mobile devices.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
If the Good Technology MDM server is used, complete the following:
-Verify "Enable remote full device wipe" is checked.iOS Siri application<GroupDescription></GroupDescription>WIR-MOS-iOS-50-02iOS Siri application must be disabled.
<VulnDiscussion>The Siri application connects to Apple servers and stores information about the device and user inquiries on those servers. The use of Siri could lead to the compromise of sensitive DoD information.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable Siri in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow Siri" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.iOS Multiplayer Gaming<GroupDescription></GroupDescription>WIR-MOS-iOS-50-03iOS Multiplayer Gaming must be disabled.
<VulnDiscussion>The game function connects to Apple servers and allows the transfer of device data to other iOS devices. The use of the game function could lead to the compromise of sensitive DoD information.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable multiplayer gaming in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow multiplayer gaming" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.iOS Game Center<GroupDescription></GroupDescription>WIR-MOS-iOS-50-04Adding Game Center Friends must be disabled.
<VulnDiscussion>The game function connects to Apple servers and allows the transfer of device data to other iOS devices. The use of the game function could lead to the compromise of sensitive DoD information.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable Adding Game Center Friends in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Adding Game Center Friends" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
iOS iCloud Backup<GroupDescription></GroupDescription>WIR-MOS-iOS-50-05iCloud Backup must be disabled. <VulnDiscussion>The iCloud feature (and associated iCloud setting in iOS) stores iOS device data on Apple controlled servers. Sensitive DoD data saved on the iOS device could be compromised when it is stored on the Apple servers. Acceptable backup methods include backup to the MDM server or backup to a DoD PC via a USB connection.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable iCloud Backup in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow iCloud Backup" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
iOS iCloud Document Syncing<GroupDescription></GroupDescription>WIR-MOS-iOS-50-06Document Syncing must be disabled. <VulnDiscussion>The iCloud feature (and associated iCloud setting in iOS) stores iOS device data on Apple controlled servers. Sensitive DoD data saved on the iOS device could be compromised when it is stored on the Apple servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable Document Syncing in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow Document Syncing" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.iOS iCloud Photo Stream<GroupDescription></GroupDescription>WIR-MOS-iOS-50-07Photo Stream must be disabled.
<VulnDiscussion>The iCloud feature (and associated iCloud setting in iOS) stores iOS device data on Apple controlled servers. Sensitive DoD data saved on the iOS device could be compromised when it is stored on the Apple servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable Photo Stream in the iOS security policy.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow Photo Stream" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.iOS Diagnostic Data<GroupDescription></GroupDescription>WIR-MOS-iOS-50-08Diagnostic Data must not be sent to Apple or other unauthorized entity.<VulnDiscussion>Sensitive DoD information could be compromised if this setting is not implemented. DoD mobile device diagnostic data could be considered sensitive data and should not be sent to Apple and reside on Apple servers.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWM-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable "Allow Diagnostic Data to be Sent to Apple" in the iOS security policy.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow Diagnostic Data to be Sent to Apple" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.VPN timeout<GroupDescription></GroupDescription>WIR-MOS-iOS-034-05All mobile device VPN clients must timeout after a set period of inactivity.
<VulnDiscussion>DoD data and the DoD network could be compromised if transmitted data is not secured with a compliant VPN. A VPN provides an open connection to the DoD network. If the VPN client does not timeout after the required period of inactivity, and a hacker is able to bypass the device password controls, they would have access to the DoD network.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the VPN client to timeout a session after 4 hours of inactivity.This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets. Verify the VPN client is configured to timeout an inactive session after a set period of inactivity. The check procedures will vary depending on the VPN client used.
Mark as a finding if the VPN client is not configured to timeout after 4 hours.VPN credential cache<GroupDescription></GroupDescription>WIR-MOS-iOS-034-06The mobile operating system must not cache smart card or certificate store passwords used by the VPN client for more than two hours.
<VulnDiscussion>DoD data could be compromised if transmitted data is not secured with a compliant VPN. User authentication credentials (CAC PIN) may be compromised if a hacker credential cache is not wiped on a periodic basis.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the VPN client to timeout an inactive session of 2 hours or less.
This check is not applicable if the installed VPN client is not used for remote access to DoD networks. Note: Use of a VPN to access DoD email on a mobile device is not required.
Interview the IAO and/or site wireless device administrator and inspect a sample (3-4) of site devices. Review VPN client specification sheets. Verify the VPN client is inactive session timeout has been set to 2 hours or less, if this parameter is configurable. If the specification sheets do not provide evidence of this capability, authenticate the VPN, wait two hours, and verify the system prompts the user for fresh credentials.
Mark as a finding if the timeout period is not set as required.iOS management agents<GroupDescription></GroupDescription>WIR-MOS-60MDM, MAM, and integrity validation agent(s) must be installed on the mobile OS device. <VulnDiscussion>The MDM, MAM, and integrity scanning agents all perform various security management functions on the iOS devices (some products integrate all three functions into one agent). If these agents are not on the mobile device, key security controls may not be enforced, which could lead to the compromise of sensitive DoD data.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install MDM, MAM, and integrity validation agent(s) on the iOS device.Check the list of applications in Settings on a sample of 2-3 iOS devices. Verify an MDM, MAM, and integrity validation agent are installed on the device.
Note that one or more agents may be used. Some agents may perform one or more of these functions. Ask the site for the name of the product(s) used. Mark as a finding if any of the required agent(s) are not installed.iOS security policy<GroupDescription></GroupDescription>WIR-MOS-iOS-65-01The mobile operating system must not permit a user to disable or modify the security policy or enforcement mechanisms on the device.
<VulnDiscussion>The integrity of the security policy and enforcement mechanisms is critical to the IA posture of the operating system. If a user can modify a device's security policy or enforcement mechanisms, then a wide range of subsequent attacks are possible, including unauthorized access to information and networks. Access controls that prevent a user from making modifications such as these mitigate the risk of operating system compromise.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Use an MDM profile to manage the security policy on site-managed iOS devices.Apple iOS 6 meets this requirement if an MDM profile is used on the iOS device to manage the device security policy. Verify an MDM profile is installed on a sample of devices (3-4): Settings > General > Profiles.
Mark as a finding if the site does not use an MDM profile to manage the security policy on site-managed iOS devices (it has already been verified that iOS 6 does not permit a user to modify the MDM profile).
Authentication<GroupDescription></GroupDescription>WIR-MOS-iOS-65-02The mobile operating system must provide mutual authentication between the provisioning server and the provisioned device during a trusted over-the-air (OTA) provisioning session.
<VulnDiscussion>When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system. Mutual authentication ensures both that the device is authorized for provisioning and that a rogue provisioning server is not used to obtain software.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the mobile operating system to authenticate the provisioning server prior to accepting provisioned software.
The link between iOS 6 and Apple meets this requirement for iOS updates from Apple.
Review the software loading process between the mobile device and the provisioning server (MDM and/or MAM) to determine if it meets the necessary assurance for mutual authentication. Acceptable mutual authentication mechanisms may include PKI or shared secret based systems. A review of product documentation may be necessary. Mark as a finding if the trusted loading process does not meet the criteria.OTA provisioning<GroupDescription></GroupDescription>WIR-MOS-iOS-65-03The mobile operating system must protect the confidentiality of the provisioning data downloaded to the handheld device during a trusted over-the-air (OTA) provisioning session.
<VulnDiscussion>Provisioning data may be sensitive and therefore must be adequately protected. An adversary within the general proximity of the mobile device can eavesdrop on OTA transactions, making them particularly vulnerable to attack if confidentiality protections are not in place. Proper use of cryptography provides strong assurance that provisioning data is protected against confidentiality attacks.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the operating system to use cryptography providing confidentiality for provisioning downloads.
The link between iOS 6 and Apple meets this requirement for iOS updates from Apple.
Review system documentation and operating system configuration to determine if there is appropriate cryptography protecting the confidentiality of OTA provisioning between the mobile device and the provisioning server (MDM and/or MAM). AES encryption is one example of an acceptable cryptography. A review of product documentation may be needed. If the provisioning data is not protected by cryptographic means during an OTA provisioning procedure, this is a finding.OTA provisioning data integrity<GroupDescription></GroupDescription>WIR-MOS-iOS-65-04The mobile operating system must protect the integrity of the provisioning data downloaded to the handheld device during a trusted over-the-air (OTA) provisioning session.
<VulnDiscussion>Provisioning data may be sensitive and therefore must be adequately protected. It may be possible for an adversary within the general proximity of the mobile device to hijack provisioning sessions and modify data transmitted during the provisioning process. Proper use of cryptography provides strong assurance that provisioning data is protected against integrity attacks.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Configure the operating system to use cryptography providing integrity for provisioning downloads.
The link between iOS 6 and Apple meets this requirement for iOS updates from Apple.
Review system documentation and operating system configuration to determine if there are appropriate integrity mechanisms protecting the confidentiality of OTA provisioning between the mobile device and the provisioning server (MDM and/or MAM). A review of product documentation may be needed. Appropriate integrity mechanisms generally involve the use of FIPS validated cryptographic modules implementing algorithms that provide integrity services. If there are no such mechanisms present, this is a finding.Disable OTA provisioning<GroupDescription></GroupDescription>WIR-MOS-iOS-65-05The mobile operating system must support the capability for the system administrator to disable over-the-air (OTA) provisioning.
<VulnDiscussion>In some environments, the risk of OTA provisioning may outweigh any convenience benefit it offers. In addition, some OTA mechanisms do not provide appropriate authentication and cryptographic integrity measures. In such cases, the administrator should have the ability to disable OTA provisioning to ensure secure breaches do not occur from use of this technique.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable OTA provisioning if threat conditions warrant this action. Review system documentation and operating system configuration to determine if the system administrator has the ability to disable OTA provisioning on the MDM and/or MAM server.
The Good Technology server meets this requirement.Data in transit encryption - FIPS 140-2<GroupDescription></GroupDescription>WIR-MOS-iOS-65-08The cryptographic module supporting encryption of data in transit (including email and attachments) must be FIPS 140-2 validated.
<VulnDiscussion>The most common vulnerabilities with cryptographic modules are those associated with poor implementation. FIPS 140 validation provides assurance that the relevant cryptography has been implemented correctly. FIPS validation is also a strict requirement for use of cryptography in the Federal Government.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>DCNR-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Stop using the operating system until the vendor has obtained FIPS validation, or install a third-party product that has a FIPS 140-2 validated cryptographic module.Review a sample of site-managed devices (3-4), interview the IAO, and review product documentation.
Note: iOS does not currently provide a FIPS 140-2 validated cryptographic module for application services. Accordingly, third-party applications transmitting or receiving DoD sensitive information (MDM agent, email client, or browser) that leverage FIPS 140-2 validated cryptographic modules must be used to meet the requirement. VPN clients that do not possess the Apple VPN entitlement must also use a third-party FIPS 140-2 validated cryptographic module.
If a site uses an application that transmits or receives sensitive DoD information, verify the application (MDM agent, email client, browser, or VPN client) leverages a FIPS 140-2 validated cryptographic module for this purpose. Review system documentation to identify the FIPS 140-2 certificate for the cryptographic module. Visit the NIST website at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm to verify the certificate is still valid.
If a site uses a third-party application that handles data in transit (MDM agent, email client, or browser) using cryptography that has not been FIPS 140-2 validated, this is a finding. Browser configuration<GroupDescription></GroupDescription>WIR-MOS-iOS-65-11The mobile operating system must prevent a user from using a browser that does not direct its traffic to a DoD proxy server.
<VulnDiscussion>Proxy servers can inspect traffic for malware and other signs of a security attack. Allowing a mobile device to access the public Internet without proxy server inspection forgoes the protection that the proxy server would otherwise provide. Malware downloaded onto the device could have a wide variety of malicious consequences, including loss of sensitive DoD information. Forcing traffic to flow through a proxy server greatly mitigates the risk of access to public Internet resources.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable browsers that do not support a feature to direct all traffic to a DoD proxy server. Configure browsers that support this functionality to direct all traffic to a DoD proxy server.
Review the operating system and browser configuration to determine if traffic is forced through DoD proxy servers.
If greater assurance is required, access a number of Internet web sites and verify traffic flows through a DoD proxy server by viewing the traffic using a network protocol analyzer or by communicating with personnel that manage the proxy server.
Note: Although in iOS 6, Safari can be configured to meet this requirement, Safari encryption is not FIPS 140-2 validated and cannot be used in the DoD. Therefore, a third-party browser must be used.
There are two acceptable implementations for this requirement.
1. The device uses a mobile VPN to route all data traffic to the DoD enclave, which forces all browser traffic to the DoD Internet gateway.
2. The device browser supports a proxy server setting that forces all traffic to a specified the proxy server when configured to do so. The configuration must be from an MDM server and not user modifiable. In some implementations, the user may enter a container application to access the browser functionality.
Verify that none of the unauthorized browsers can be used. On a sample of 3-4 devices, identify the browsers on the device. If any are unauthorized, verify they are not functional.
Mark as a finding if any non-compliant browser is functional. Malware controls<GroupDescription></GroupDescription>WIR-MOS-iOS-65-15The mobile operating system must employ a DoD-approved anti-malware protections.<VulnDiscussion>In order to minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can result in the disclosure of sensitive information or cause a denial of service. Anti-virus applications are not common on mobile operating systems but one or more methods to mitigate the risk of malware must be in place to protect DoD information and networks.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECVP-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Install MDIS and MAM servers in the system architecture.
The method for meeting this requirement using an iOS device is by implementing MDIS and MAM servers in the system architecture.
Verify the site has implemented both the MDIS and MAM servers by reviewing system documentation and interviewing the IAO and verify the MDIS and MAM agents are installed on a sample (3-4) of site-managed devices.
Mark as a finding if an MDIS and MAM server are not installed in the system architecture.iOS iCloud photo stream sharing<GroupDescription></GroupDescription>WIR-MOS-iOS-70-01Shared Photo Stream must be disabled. <VulnDiscussion>The iCloud feature (and associated iCloud setting in iOS) stores iOS device data on Apple controlled servers. Sensitive DoD data saved on the iOS device could be compromised when it is stored on the Apple servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable Shared Photo Stream in the iOS security policy.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify "Allow Shared Photo Stream" is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.iOS Passbook<GroupDescription></GroupDescription>WIR-MOS-iOS-70-02Access to iOS Passbook applications must be disabled.<VulnDiscussion>iOS Passbook allows applications to be accessed after the iOS device is locked. The icons for passbook enabled apps are shown on the device screen after the device is locked. Any sensitive data stored in the available application would be available if the iOS device is lost or stolen. Therefore, sensitive DoD data could be exposed. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Disable access to Passbook in the iOS security policy.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify “Allow Passbook” is not enabled.
Mark as a finding if not set as required.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Bluetooth sharing<GroupDescription></GroupDescription>WIR-MOS-iOS-70-03The iOS device user must not allow applications to share data between iOS devices via Bluetooth.<VulnDiscussion>The iOS device Bluetooth sharing feature allows applications to share data saved on the iOS device with other iOS devices via Bluetooth connections between the devices. This feature allows the wireless transmission of sensitive DoD data without using FIPS 140-2 validated encryption as required by DoD policy and could expose sensitive DoD data to unauthorized individuals.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Delete all applications listed on the Bluetooth sharing screen or disable sharing of these applications.This is a User-Based Enforcement (UBE) control.
On a sample of site-managed iOS devices (pick 3-4 random devices), check that no applications have been enabled for Bluetooth sharing.
-Have the user log into the device.
-Go to Settings > Privacy > Bluetooth Sharing.
-Verify there are no applications listed.
Mark as a finding if any applications are listed on the Bluetooth sharing screen.Wi-Fi Profile<GroupDescription></GroupDescription>WIR-MOS-iOS-70-04A Wi-Fi profile must be set up on managed iOS devices to disable access to any public Wi-Fi network that iOS may otherwise auto-join. <VulnDiscussion>iOS has the capability to “auto-join” public Wi-Fi networks that are pre-configured in iOS. This feature is available in iOS to improve a user’s experience when connecting to the Internet. The “attwifi” public network has been found to be monitored by hackers and easily spoofed, so users do not know if they are connecting to the real network or the hacker-controlled network. Sensitive DoD data could be exposed if a DoD user’s iOS device is connected to a hacker-controlled Wi-Fi network. An iOS GSM device from ATT will attempt to auto-join any attwifi network in the vicinity of the device. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set up a Wi-Fi profile on the MDM server security policy to disable attwifi network connections.This check is not applicable if the site does not use any iOS devices from ATT.
1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to, and in turn, verify the required settings are in the policy. Verify a Wi-Fi profile has been set up in the security policy with the following features:
•SSID: attwifi.
•Passphrase: any eight-character or larger passphrase.
•Auto-join: set to off.
(Note: This setting effectively stops the iOS device from automatically connecting to the attwifi network when in range of a network access point and also disables the ability of a user from connecting the network.)
Mark as a finding if the required Wi-Fi profile is not set up in the security policy and it does not have the required configuration.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
On the Good Technology MDM server, the Wi-Fi profile is found in the “WiFi” tab of the “iOS Configuration” section of the security policy.iCloud wipe of device<GroupDescription></GroupDescription>WIR-MOS-iOS-70-05The ability to wipe a DoD iOS device via an iCloud account must be disabled.<VulnDiscussion>If a DoD iOS device is associated with an iCloud account, a user of that iCloud account, or anyone who gains access to that iCloud account, can send a device wipe command to the iOS device and the device will wipe itself. This will cause a Denial-Of-Service (DOS) attack on the device. There are two possible mitigations for this vulnerability:
1. Disable all personal email on the iOS device via an iOS Restriction. This is the recommended method. The use of personal email on iOS devices could cause sensitive DoD data to be saved on the device outside the security container if a DoD email message with sensitive data is forwarded to a personal email account and that email message is viewed on the device. Disabling all personal email also disables "Find My iPhone" which, if functional, would have the capability of wiping a DoD iOS device from an iCloud account, which is configured to a personal email address.
2. Disable "Find My iPhone" via an iOS Restriction. This method should only be used if there is a mission need for a user to have personal email accounts set up on their DoD iOS device and use of personal email has been approved by the DAA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set up the required Restriction policy on each site-managed iOS device.Interview the site IAO and iOS device system administrator. Also, perform the following actions on a random sample of site-managed iOS devices (3-4 devices, iPhone and iPad).
-Verify an iOS restriction has been placed on the iOS devices and the system administrator has assigned a four character passcode, so the user cannot remove it. The iOS Restriction passcode must meet the same complexity requirements as the device unlock passcode: no sequential numbers and no repeating numbers.
*Have the site iOS system administrator show that a Restriction policy is on the device. Go to Settings > General > Restrictions. Mark as a finding if no Restriction exists.
*Have the site iOS system administrator log into the Restriction policy. Mark as a finding if the restriction passcode is not 4 characters and does not meet the complexity requirements.
*Interview several users and determine if they have been given the Restriction passcode by the system administrator. If yes, mark as a finding.
-After the system administrator opens the Restriction, verify the following configuration setting has been set in the Restriction policy to disable the capability for a device wipe command to be initiated on the device when received from an iCloud account:
----Allow Changes > Accounts > Don't Allow Changes (If the DAA has not approved the use of personal email, this setting must be checked. If not checked, ask to see documentation showing DAA approval of personal email on site-managed iOS devices.)
-If personal email is allowed, verify the following configuration setting has been set in the Restriction policy:
----Privacy > Location Services > Find My iPhone set to Off.
Mark as a finding if any of these settings is not set as required.iOS iMessage<GroupDescription></GroupDescription>WIR-MOS-iOS-70-06The iOS device iMessage service must be set to Off at all times (User Based Enforcement (UBE)). <VulnDiscussion>iOS iMessage service provides the potential for the exposure of private and possibly sensitive DoD information. When a DoD iOS device is transferred to a new user or disposed of, the device may still receive iMessages sent to the previous DoD user. iMessage phone numbers on a specific iOS device can persist after a SIM has been removed from the phone. For example, SIM A is placed in phone, activated on iMessage, and then swapped out for SIM B. That phone will receive iMessages bound for the phone numbers on both SIM A and B until the iMessage service on the phone has been turned off and then back on again. This vulnerability exists for GSM devices but not for CDMA devices. When the original device user receives messages via their iMessage account, the message will be displayed on their old iOS device. The wipe procedure for the iOS device must include specific procedures (outlined in the STIG Overview) to mitigate this risk.
</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>Other</Responsibility><IAControls>ECWN-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Set "iMessage" to "Off".On a sample of site-managed iOS devices (pick 3-4 random devices), have the user turn on and log into the device.
-Go to Settings > Messages > iMessage.
-Check the setting of "iMessage".
Verify "iMessage" is set to off (not selected).
Mark as a finding if "iMessage" is not set to off.
Passcode complexity - alphanumeric<GroupDescription></GroupDescription>WIR-MOS-iOS-G-024The iOS Passcode must contain at least one alphabetic and one numeric character.<VulnDiscussion>Sensitive DoD data could be compromised if a device unlock password/passcode is not set to the required complexity on DoD CMDs. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Select the “Alphanumeric” configuration setting in the MDM security policy.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify "Alphanumeric” is checked in the policy.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.Passcode complexity complex characters<GroupDescription></GroupDescription>WIR-MOS-iOS-G-025The iOS Passcode must contain at least one complex (non-alphanumeric) character.<VulnDiscussion>Sensitive DoD data could be compromised if a device unlock password/passcode is not set to the required complexity on DoD CMDs. The DoD CMD password requirements for protecting sensitive data are that the password must be at least 8 characters in length and contain at least one lowercase letter, one uppercase letter, and one number. In addition, sequential characters/numbers may not be used in the password. It is not currently possible to require both an uppercase letter and lowercase letter for the iOS passcode, or to enforce the sequential character restriction, so the iOS passcode must contain a special character to approximate the same password strength as the DoD-specified password complexity rules.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility>System Administrator</Responsibility><IAControls>ECWN-1, IAIA-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374Select the “Minimum number of complex characters” and “1 character” configuration settings in the MDM iOS security policy.1. Make a list of all iOS security policies listed on the MDM server that have been assigned to iOS devices and review each policy.
2. Select each security policy iOS devices are assigned to and, in turn, verify the required settings are in the policy. Verify "Minimum number of complex characters” is checked and at least “1 character” is selected in the iOS security policy.
Mark as a finding if the required rule is not set up on the MDM server.
Note: If there is a finding, note the name of the policy in the Findings Details section in VMS/Component Provided Tracking Database.
Unsupported Mobile Operating System<GroupDescription></GroupDescription>WIR-MOS-iOS-500Apple iOS operating systems that are no longer supported by the vendor for security updates must not be installed on a system.<VulnDiscussion>Apple iOS operating systems that are no longer supported by Apple for security updates are not evaluated or updated for vulnerabilities, leaving them open to potential attack. Organizations must transition to a supported operating system to ensure continued support.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls>DCSQ-1</IAControls>DPMS Target Apple iOS 6DISA FSODPMS TargetApple iOS 62374CCI-000366Upgrade iOS6 mobile devices to a supported operating system.Apple support for iOS6 ended 18 September 2013. If iOS6 is installed on a mobile device, this is a finding.