View STIG - Apple iOS 12 Security Technical Implementation Guide V1R2

a

Apple iOS must be configured to enforce a minimum password length of six characters.

IA-5 - Low - CCI-000205 - V-81755 - SV-96469r1_rule

RMF Control

IA-5

Severity

Low

CCI

CCI-000205

Version

AIOS-12-000100

Vuln IDs

V-81755

Rule IDs

SV-96469r1_rule

Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. The ability to crack a password is a function of how many attempts an adversary is permitted, how quickly an adversary can do each attempt, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise. SFR ID: FMT_SMF_EXT.1.1 #1a

Checks: C-81535r1_chk

Review configuration settings to confirm the minimum passcode length is six or more characters. This procedure is performed in the Apple iOS management tool and on the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Management tool, verify the "Minimum passcode length" value is set to "6" or greater. Alternatively, verify the text "<key>minLength</key> <integer>6</integer>" appears in the configuration profile (.mobileconfig file). It also is acceptable for the integer value to be greater than "6". On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Tap "Passcode". 7. Verify "Minimum length" is listed as "6" or greater. If the "Minimum passcode length" is less than "6" characters in the iOS management tool, "<key>minLength</key> " has an integer value of less than "6", or the password policy on the Apple iOS device from the Apple iOS management tool does not list "Minimum length" of "6" or fewer, this is a finding.

Fix: F-88603r1_fix

Install a configuration profile to enforce a minimum passcode length value of "6" or greater.

a

Apple iOS must be configured to not allow passwords that include more than two repeating or sequential characters.

CM-6 - Low - CCI-000366 - V-81757 - SV-96471r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-000200

Vuln IDs

V-81757

Rule IDs

SV-96471r1_rule

Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk. SFR ID: FMT_SMF_EXT.1.1 #1b

Checks: C-81537r1_chk

Review configuration settings to confirm that simple passcodes are not allowed. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify the "Allow simple value" is unchecked. Alternatively, verify the text "<key>allowSimple</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Tap "Passcode". 7. Verify "Simple passcodes allowed" is set to "No". If "Allow simple value" is checked in the Apple iOS management tool, "<key>allowSimple</key> <true/>" appears in the Configuration Profile, or the password policy on the Apple iOS device from the Apple iOS management tool does not have "Simple passcodes allowed" set to "No", this is a finding.

Fix: F-88605r1_fix

Install a configuration profile to disallow more than two sequential or repeating numbers or letters in the device unlock password.

b

Apple iOS must be configured to lock the display after 15 minutes (or less) of inactivity.

AC-11 - Medium - CCI-000057 - V-81759 - SV-96473r1_rule

RMF Control

AC-11

Severity

Medium

CCI

CCI-000057

Version

AIOS-12-000300

Vuln IDs

V-81759

Rule IDs

SV-96473r1_rule

The screen lock timeout must be set to a value that helps protect the device from unauthorized access. Having a too-long timeout would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device. Satisfies: PP-MDF-301030, PP-MDF-301040 SFR ID: FMT_SMF_EXT.1.1 #2a & #2b

Checks: C-81539r1_chk

Review configuration settings to confirm the screen lock timeout is set to 15 minutes or less. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the management tool, verify the sum of the values assigned to "Maximum Auto-Lock time" and "Grace period for device lock" is between 1 and 15 minutes. Alternatively, locate the text "<key>maxGracePeriod</key>" and "<key>maxInactivity</key>" and ensure the sum of their integer value is between 1 and 15 in the configuration profile (.mobileconfig file). For example: "<key>maxGracePeriod</key> <integer>5</integer> <key>maxInactivity</key> <integer>5</integer>" Here, 5 + 5 = 10; this meets the requirement. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Tap "Passcode". 7. Verify the sum of the "Max grace period" and "Max inactivity" values is less than 15 minutes. Note: On some iOS devices, it is not possible to have a sum of exactly 15. In these cases, the sum must be less than 15. A sum of 16 does not meet the requirement. On the management server, if the sum of the "Max grace period" and "Max inactivity" values is not between 1 and 15 minutes in the iOS management tool, if the sum of the values assigned to "<key>maxGracePeriod</key>" and "<key>maxInactivity</key>" is not between 1 and 15 minutes in the configuration profile, or on the iOS device, if the sum of the values assigned to "Max grace period" and "Max inactivity" is not between 1 and 15 minutes, this is a finding.

Fix: F-88607r1_fix

Install a configuration profile to lock the device display after 15 minutes (or less) of inactivity. This is done by setting "Maximum Auto-Lock time" and "Grace Period for device lock" so the sum of their values is between 1 and 15 minutes.

a

Apple iOS must be configured to not allow more than 10 consecutive failed authentication attempts.

AC-7 - Low - CCI-000044 - V-81761 - SV-96475r1_rule

RMF Control

AC-7

Severity

Low

CCI

CCI-000044

Version

AIOS-12-000400

Vuln IDs

V-81761

Rule IDs

SV-96475r1_rule

The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or less gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password. SFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5

Checks: C-81541r1_chk

Review configuration settings to confirm that consecutive failed authentication attempts is set to "10" or fewer. This procedure is performed in the Apple iOS management tool and on the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Management tool, verify the "Maximum number of failed attempts" value is set to "10" or fewer. Alternatively, verify the text "<key>maxFailedAttempts</key> <integer>10</integer>" appears in the configuration profile (.mobileconfig file). It also is acceptable for the integer value to be less than "10". On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Tap "Passcode". 7. Verify "Max failed attempts" is listed as "10" or fewer. If the "Maximum number of failed attempts" is more than "10" in the iOS management tool, "<key>maxFailedAttempts</key> " has an integer value of more than "10", or the password policy on the Apple iOS device from the Apple iOS management tool does not list "Max failed attempts" of "10" or fewer, this is a finding.

Fix: F-88609r1_fix

Install a configuration profile to allow only 10 or fewer consecutive failed authentication attempts.

a

If an unmanaged third-party VPN client is installed on the iOS device, it must not be configured with a DoD network (work) VPN profile.

AC-17 - Low - CCI-000068 - V-81763 - SV-96477r1_rule

RMF Control

AC-17

Severity

Low

CCI

CCI-000068

Version

AIOS-12-000800

Vuln IDs

V-81763

Rule IDs

SV-96477r1_rule

Access to the DoD network must be limited for unmanaged apps because they are considered untrusted. SFR ID: FMT_SMF_EXT.1.1 #3

Checks: C-81543r1_chk

Review the list of unmanaged apps installed on the iOS device and determine if any third-party VPN clients are installed. If yes, verify the VPN app is not configured with a DoD network (work) VPN profile. This validation procedure is performed on the iOS device only. On the iOS device, do the following: 1. Under Settings, VPN look to see if any "Personal VPN" exists. 2. If no, requirement has been met. 3. If yes, open each VPN app in turn. Review the list of VPN profiles configured on the VPN client. 4. Verify there are no DoD network VPN profiles configured on the VPN client. If any third-party unmanaged VPN apps are installed (personal VPN) and has a DoD network VPN profile configured on the client, this is a finding. Note: This setting cannot be managed by the MDM administrator and is a User Based Enforcement (UBE) requirement.

Fix: F-88611r1_fix

If a third-party unmanaged VPN app is installed on the iOS 12 device, do not configure the VPN app with a DoD network VPN profile.

b

Apple iOS must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [selection: Apple App Store].

AC-17 - Medium - CCI-000068 - V-81765 - SV-96479r1_rule

RMF Control

AC-17

Severity

Medium

CCI

CCI-000068

Version

AIOS-12-001000

Vuln IDs

V-81765

Rule IDs

SV-96479r1_rule

Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DoD data accessible by these unauthorized/malicious applications. SFR ID: FMT_SMF_EXT.1.1 #8a

Checks: C-81545r1_chk

Review configuration settings to confirm "Allow Trusting New Enterprise App Authors" restriction is disabled. This procedure is performed in the Apple iOS management tool and on the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Management tool, verify the "Allow Trusting New Enterprise App Authors" is disabled. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Verify "Trusting enterprise apps not allowed" is listed. If the "Allow Trusting New Enterprise App Authors" is not disabled in the iOS management tool or on the Apple iOS device, this is a finding.

Fix: F-88613r1_fix

Install a configuration profile to disable "Allow Trusting New Enterprise App Authors".

b

Apple iOS must not include applications with the following characteristics: Siri when the device is locked.

AC-17 - Medium - CCI-000068 - V-81767 - SV-96481r1_rule

RMF Control

AC-17

Severity

Medium

CCI

CCI-000068

Version

AIOS-12-001300

Vuln IDs

V-81767

Rule IDs

SV-96481r1_rule

On Apple iOS devices, users can access the device's contact database or calendar to obtain phone numbers and other information using a human voice even when the mobile device is locked. Often this information is Personally Identifiable Information (PII), which is considered sensitive. It could also be used by an adversary to profile the user or engage in social engineering to obtain further information from other unsuspecting users. Disabling access to the contact database and calendar in these situations mitigates the risk of this attack. The AO may waive this requirement with written notice if the operational environment requires this capability. SFR ID: FMT_SMF_EXT.1.1 #8b

Checks: C-81547r1_chk

Review configuration settings to confirm that Siri is disabled on the Lock screen. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow Siri while device is locked" is unchecked. Alternatively, verify the text "<key>allowAssistantWhileLocked</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Siri while locked not allowed" is listed. If "Allow Siri while device is locked" is checked in the Apple iOS management tool, "<key>allowAssistantWhileLocked</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Siri while locked not allowed", this is a finding.

Fix: F-88615r1_fix

Install a configuration profile to disable Siri while the device is locked.

b

Apple iOS must not include applications with the following characteristics: Voice dialing application if available when MD is locked.

AC-17 - Medium - CCI-000066 - V-81769 - SV-96483r1_rule

RMF Control

AC-17

Severity

Medium

CCI

CCI-000066

Version

AIOS-12-001400

Vuln IDs

V-81769

Rule IDs

SV-96483r1_rule

On Apple iOS devices, users can access the device's contact database or calendar to obtain phone numbers and other information using a human voice even when the mobile device is locked. Often this information is Personally Identifiable Information (PII), which is considered sensitive. It could also be used by an adversary to profile the user or engage in social engineering to obtain further information from other unsuspecting users. Disabling access to the contact database and calendar in these situations mitigates the risk of this attack. SFR ID: FMT_SMF_EXT.1.1 #8b

Checks: C-81551r1_chk

Review configuration settings to confirm that "Allow Voice Dialing when locked" is disabled on the Lock screen. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow voice dialing while device locked" is unchecked. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Voice dialing while locked not allowed" is listed. If "Allow voice dialing when locked not allowed" is checked in the Apple iOS management tool or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Voice dialing while locked not allowed", this is a finding.

Fix: F-88619r1_fix

Install a configuration profile to disable Voice Control while the device is locked.

b

Apple iOS must not display notifications when the device is locked.

CM-6 - Medium - CCI-000366 - V-81771 - SV-96485r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-001800

Vuln IDs

V-81771

Rule IDs

SV-96485r1_rule

Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the MOS to not send notifications to the lock screen mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #19

Checks: C-81553r1_chk

Review configuration settings to confirm "Show Notification Center in Lock screen" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Show Notification Center in Lock screen" is unchecked. Alternatively, verify the text "<key>allowLockScreenNotificationsView</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Restrictions". 6. Verify "Notifications view on lock screen not allowed" is present. If "Show Notification Center in Lock screen" is checked in the Apple iOS management tool, "<key>allowLockScreenNotificationsView</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Notifications View on lock screen not allowed", this is a finding.

Fix: F-88621r1_fix

Install a configuration profile to disable Notification Center from the device Lock screen.

b

Apple iOS must not display notifications (calendar information) when the device is locked.

CM-6 - Medium - CCI-000366 - V-81773 - SV-96487r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-001900

Vuln IDs

V-81773

Rule IDs

SV-96487r1_rule

Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the MOS to not send notifications to the lock screen mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #19

Checks: C-81555r1_chk

Review configuration settings to confirm "Show Today view in Lock screen" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Show Today view in Lock screen" is unchecked. Alternatively, verify the text "<key>allowLockScreenTodayView</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Restrictions". 6. Verify "Today view on lock screen not allowed" is present. If the "Show Today view in Lock screen" is checked in the Apple iOS management tool, "<key>allowLockScreenTodayView</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Today view on lock screen not allowed", this is a finding.

Fix: F-88623r1_fix

Install a configuration profile to disable Notification Center from the device Lock screen.

a

Apple iOS must be configured to display the DoD advisory warning message at start-up or each time the user unlocks the device.

CM-6 - Low - CCI-000366 - V-81775 - SV-96489r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-003600

Vuln IDs

V-81775

Rule IDs

SV-96489r1_rule

Apple iOS is required to display the DoD-approved system use notification message or banner before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Required banners help ensure that DoD can audit and monitor the activities of mobile device users without legal restriction. System use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a "click-through" banner at device unlock (to the extent permitted by the operating system). A "click-through" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating "OK." The approved DoD text must be used exactly as required in the KS referenced in DoDI 8500.01. For devices accommodating banners of 1300 characters, the banner text is: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. For devices with severe character limitations, the banner text is: I've read & consent to terms in IS user agreem't. The administrator must configure the banner text exactly as written without any changes. SFR ID: FMT_SMF_EXT.1.1 #36

Checks: C-81557r1_chk

The DoD warning banner can be displayed by either of the following methods (required text is found in the Vulnerability Description): 1. By placing the DoD warning banner text in the user agreement signed by each iOS device user (preferred method) 2. By creating a background picture with the relevant information and configuring that picture as the background for the lock screen via the Apple iOS management tool (only available for supervised devices) Determine which method is used at the iOS device site and follow the appropriate validation procedure below. Validation Procedure for Method #1: Review the signed user agreements for several iOS device users and verify the agreement includes the required DoD warning banner text. Validation Procedure for Method #2: - In the Apple iOS management tool, verify a picture of the DoD warning banner text has been configured as the background for the lock screen. - On the iOS device, verify a picture of the DoD warning banner text is shown as the background for the locked screen. If, for Method #1, the required warning banner text is not on all signed user agreements reviewed, or for Method #2, the DoD warning banner text is not set as the locked screen background, this is a finding.

Fix: F-88625r1_fix

Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Description): 1. By placing the DoD warning banner text in the user agreement signed by each iOS device user (preferred method) 2. By creating a background picture with the relevant information and configuring that picture as the background for the lock screen via the Apple iOS management tool

b

Apple iOS must not allow backup of managed app data to locally connected systems.

CM-6 - Medium - CCI-000366 - V-81777 - SV-96491r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004000

Vuln IDs

V-81777

Rule IDs

SV-96491r1_rule

Data on mobile devices is protected by numerous mechanisms, including user authentication, access control, and cryptography. When the data is backed up to an external system (either locally connected or cloud-based), many if not all of these mechanisms are no longer present. This leaves the backed-up data vulnerable to attack. Disabling backup to external systems mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #40

Checks: C-81559r1_chk

Review configuration settings to confirm backup in management apps is disabled and iTunes Backup is encrypted. Note: iTunes Backup is implemented by the configuration policy rule "Force encrypted backups", which is included in AIOS-12-010800, and therefore, not included in the procedure below. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify backing up app data is disabled. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Apps". 6. Tap a managed app. 7. Verify "App data will not be backed up" is listed. Note: Steps 6 and 7 must be performed for each managed app. If backing up app data is not disabled in the Apple iOS management tool or "app data will not be backed up" is not listed for each managed app on the Apple iOS device, this is a finding.

Fix: F-88627r2_fix

Install a configuration profile to disable backup of managed apps.

b

Apple iOS must not allow backup to remote systems (iCloud).

CM-6 - Medium - CCI-000366 - V-81779 - SV-96493r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004100

Vuln IDs

V-81779

Rule IDs

SV-96493r1_rule

Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the MOS. Where the remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this case, DoD devices may synchronize DoD-sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 11 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81561r1_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm iCloud Backup is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow iCloud backup" is unchecked. Alternatively, verify the text "<key>allowCloudBackup</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the policy. 5. Tap "Restrictions". 6. Verify "iCloud backup not allowed". If "Allow iCloud backup" is checked in the Apple iOS management tool, "<key>allowCloudBackup</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "iCloud backup not allowed", this is a finding.

Fix: F-88629r1_fix

Install a configuration profile to disable iCloud Backup.

b

Apple iOS must not allow backup to remote systems (iCloud document and data synchronization).

CM-6 - Medium - CCI-000366 - V-81781 - SV-96495r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004200

Vuln IDs

V-81781

Rule IDs

SV-96495r1_rule

Backups to remote systems (including cloud backup and cloud document syncing) can leave data vulnerable to breach on the external systems, which often offer less protection than the MOS. Where the remote backup involves a cloud-based solution, the backup capability is often used to synchronize data across multiple devices. In this case, DoD devices may synchronize DoD-sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 11 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81563r1_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm "Allow iCloud documents & data" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow iCloud documents & data" is unchecked. Alternatively, verify the text "<key>allowCloudDocumentSync</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the policy. 5. Tap "Restrictions". 6. Verify "Documents in the Cloud not allowed". Note: This also verifies that iCloud Drive and iCloud Photo Library is disabled. If "Allow iCloud documents & data" is checked in the Apple iOS management tool, "<key>allowCloudDocumentSync</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Documents in the Cloud not allowed", this is a finding.

Fix: F-88631r1_fix

Install a configuration profile to disable iCloud documents and data.

b

Apple iOS must not allow backup to remote systems (iCloud Keychain).

CM-6 - Medium - CCI-000366 - V-81783 - SV-96497r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004300

Vuln IDs

V-81783

Rule IDs

SV-96497r1_rule

The iCloud Keychain is an Apple iOS function that will store users' account names and passwords in iCloud and then synchronize this data among the users' Macs, iPhones, and iPads. An adversary may use any of the stored iCloud keychain passwords after unlocking one of the synchronized devices. If a user is synchronizing devices, the user must protect all of the devices to prevent unauthorized use of the passcodes. Moreover, the keychain being transmitted through the cloud opens the possibility that a well-resourced, sophisticated adversary could compromise the cloud-transmitted keychain. Not allowing the iCloud Keychain feature mitigates the risk of the encrypted set of passwords being compromised when transmitted through the cloud or synchronized across multiple devices. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 11 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81565r1_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm iCloud keychain is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow iCloud keychain" is unchecked. Alternatively, verify the text "<key>allowCloudKeychainSync</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Verify "iCloud Keychain not allowed" is listed. If "Allow iCloud keychain" is checked in the Apple iOS management tool, "<key>allowCloudKeychainSync</key><true/>" appears in the configuration profile, or "iCloud Keychain not allowed" is not listed on the Apple iOS device, this is a finding.

Fix: F-88633r1_fix

Install a configuration profile to disable iCloud keychain.

b

Apple iOS must not allow backup to remote systems (My Photo Stream).

CM-6 - Medium - CCI-000366 - V-81787 - SV-96501r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004400

Vuln IDs

V-81787

Rule IDs

SV-96501r1_rule

When My Photo Stream is enabled, sensitive photos will be uploaded automatically to Apple-specified servers and available on other Apple iOS devices associated with the same Apple ID, provided that the other device also has My Photo Stream enabled. This potentially places sensitive photos on a server outside of DoD's control and potentially makes them available to non-DoD devices. Disabling My Photo Stream mitigates this risk. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 11 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81571r1_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm "Allow My Photo Stream" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow My Photo Stream" is unchecked. Alternatively, verify the text "<key>allowPhotoStream</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Photo Stream not allowed" is listed. If "Allow Photo Stream" is checked in the Apple iOS management tool, "<key>allowPhotoStream</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Photo Stream not allowed", this is a finding.

Fix: F-88637r1_fix

Install a configuration profile to disable My Photo Stream.

b

Apple iOS must not allow backup to remote systems (iCloud Photo Sharing, also known as Shared Photo Streams).

CM-6 - Medium - CCI-000366 - V-81789 - SV-96503r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-004500

Vuln IDs

V-81789

Rule IDs

SV-96503r1_rule

When "Allow iCloud Photos" is enabled, sensitive photos will be uploaded automatically to Apple-specified servers and available on the Apple IOS devices of other users who have accepted invitations to participate in iCloud Photo Sharing. This potentially places sensitive photos on a server outside of DoD's control and potentially makes them available to non-DoD users and devices. Disabling iCloud Photo Sharing mitigates this risk. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 12 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81573r3_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm "Allow iCloud Photos" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow iCloud Photos" is unchecked. Alternatively, verify the text "<key>allowSharedStream</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Shared streams not allowed" is listed. If "Allow iCloud Photos" is checked in the Apple iOS management tool, "<key>allowSharedStream</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Shared streams not allowed", this is a finding.

Fix: F-88639r3_fix

Install a configuration profile to disable "Allow iCloud Photos".

b

Apple iOS must not allow backup to remote systems (managed applications data stored in iCloud).

AC-8 - Medium - CCI-000051 - V-81791 - SV-96505r1_rule

RMF Control

AC-8

Severity

Medium

CCI

CCI-000051

Version

AIOS-12-004600

Vuln IDs

V-81791

Rule IDs

SV-96505r1_rule

Storing data with a non-DoD cloud provider may leave the data vulnerable to breach. Disabling non-DoD cloud services mitigates this risk. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81575r1_chk

Review configuration settings to confirm "Allow managed apps to store data in iCloud" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow managed apps to store data in iCloud" is unchecked. Alternatively, verify the text "<key>allowManagedAppsCloudSync</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Managed apps cloud sync not allowed" is listed. If "Allow managed apps to store data in iCloud" is checked in the Apple iOS management tool, "<key>allowManagedAppsCloudSync</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Managed apps cloud sync not allowed", this is a finding.

Fix: F-88641r1_fix

Install a configuration profile to prevent DoD applications from storing data in iCloud.

b

Apple iOS must not allow backup to remote systems (enterprise books).

AC-8 - Medium - CCI-000051 - V-81793 - SV-96507r1_rule

RMF Control

AC-8

Severity

Medium

CCI

CCI-000051

Version

AIOS-12-004700

Vuln IDs

V-81793

Rule IDs

SV-96507r1_rule

Enterprise books may contain DoD-sensitive information. When enterprise books are backed up, they are vulnerable to attacks on the backup systems and media. Disabling the backup capability mitigates this risk. If such books are lost, accidentally deleted, or corrupted for any reason, they can be easily retrieved from the original source. SFR ID: FMT_MOF_EXT.1.2 #40

Checks: C-81577r1_chk

Review configuration settings to confirm "Allow backup of enterprise books" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow backup of enterprise books" is unchecked. Alternatively, verify the text "<key>allowEnterpriseBookBackup</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Backing up enterprise books not allowed" is listed. If "Allow backup of enterprise books" is checked in the Apple iOS management tool, "<key>allowEnterpriseBookBackup</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Backing up enterprise books not allowed", this is a finding.

Fix: F-88643r1_fix

Install a configuration profile to prevent backup of enterprise books that could contain DoD-sensitive information.

b

Apple iOS must not allow non-DoD applications to access DoD data.

AC-8 - Medium - CCI-000051 - V-81795 - SV-96509r1_rule

RMF Control

AC-8

Severity

Medium

CCI

CCI-000051

Version

AIOS-12-005600

Vuln IDs

V-81795

Rule IDs

SV-96509r1_rule

Managed apps have been approved for the handling of DoD-sensitive information. Unmanaged apps are provided for productivity and morale purposes but are not approved to handle DoD-sensitive information. Examples of unmanaged apps include apps for news services, travel guides, maps, and social networking. If a document were to be viewed in a managed app and the user had the ability to open this same document in an unmanaged app, this could lead to the compromise of sensitive DoD data. In some cases, the unmanaged apps are connected to cloud backup or social networks that would permit dissemination of DoD-sensitive information to unauthorized individuals. Not allowing data to be opened within unmanaged apps mitigates the risk of compromising sensitive data. SFR ID: FMT_SMF_EXT.1.1 #42, FDP_ACF_EXT.1.2

Checks: C-81579r1_chk

Review configuration settings to confirm "Allow documents from managed apps in unmanaged apps" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, then the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the iOS management tool, verify "Allow documents from managed apps in unmanaged apps" is unchecked. Alternatively, verify the text "<key>allowOpenFromManagedToUnmanaged</key><false/>" appears in the configuration profile (.mobileconfig file). On the iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Opening documents from managed to unmanaged apps not allowed" is listed. If "Allow documents from managed apps in unmanaged apps" is checked in the iOS management tool, "<key>allowOpenFromManagedToUnmanaged</key> <true/>" appears in the configuration profile, or the restrictions policy on the iOS device from the iOS management tool does not list "Opening documents from managed to unmanaged apps not allowed", this is a finding.

Fix: F-88645r1_fix

Install a configuration profile to prevent non-DoD applications from accessing DoD data.

a

Apple iOS must be configured to disable automatic transfer of diagnostic data to an external device other than an MDM service with which the device has enrolled.

SC-28 - Low - CCI-001199 - V-81797 - SV-96511r1_rule

RMF Control

SC-28

Severity

Low

CCI

CCI-001199

Version

AIOS-12-005800

Vuln IDs

V-81797

Rule IDs

SV-96511r1_rule

Many software systems automatically send diagnostic data to the manufacturer or a third party. This data enables the developers to understand real-world field behavior and improve the product based on that information. Unfortunately, it can also reveal information about what DoD users are doing with the systems and what causes them to fail. An adversary embedded within the software development team or elsewhere could use the information acquired to breach mobile operating system security. Disabling automatic transfer of such information mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #47a

Checks: C-81583r1_chk

Review configuration settings to confirm "Allow sending diagnostic and usage data to Apple" is disabled. This check procedure is performed on both the iOS management tool and the iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the iOS management tool, verify "Allow sending diagnostic and usage data to Apple" is unchecked. Alternatively, verify the text "<key>allowDiagnosticSubmission</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Restrictions". 6. Verify "Diagnostic submission not allowed" Note: This setting also disables "Share With App Developers". If "Allow sending diagnostic and usage data to Apple" is checked in the iOS management tool, "<key>allowDiagnosticSubmission</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Diagnostic submission not allowed", this is a finding.

Fix: F-88647r1_fix

Install a configuration profile to disable sending diagnostic data to an organization other than DoD.

b

Apple iOS must implement the management setting: remove managed applications upon unenrollment from MDM (including sensitive and protected data).

CM-6 - Medium - CCI-000366 - V-81799 - SV-96513r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-008900

Vuln IDs

V-81799

Rule IDs

SV-96513r1_rule

When a device is unenrolled from MDM, it is possible to relax the security policies that the MDM had implemented on the device. This may cause apps and data to be more vulnerable than they were prior to enrollment. Removing managed apps (and consequently the data they maintain) upon unenrollment mitigates this risk because on appropriately configured Apple iOS devices, DoD-sensitive information exists only within managed apps. Satisfies: PP-MDF-302510, PP-MDF-302505, PP-MDF-301500, MDF-PP-2500, MDF-PP-301510 SFR ID: FMT_SMF_EXT.2.1, FMT_SMF_EXT.1.1 #47h

Checks: C-81585r1_chk

Note: Not all Apple iOS deployments involve MDM. If the site uses an authorized alternative to MDM for distribution of configuration profiles (Apple Configurator), this check procedure is not applicable. This check procedure is performed on the Apple iOS management tool or on the iOS device. In the Apple iOS management tool, for each managed app, verify the app is configured to be removed when the MDM profile is removed. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Apps". 6. Tap an app and verify "App and data will be removed when device is no longer managed" is listed. Repeat steps 5 and 6 for each managed app in the list. If one or more managed apps are not set to be removed upon device MDM unenrollment, this is a finding.

Fix: F-88649r1_fix

Install a configuration profile to delete all managed apps upon device unenrollment.

c

Apple iOS must require a valid password be successfully entered before the mobile device data is unencrypted.

SC-28 - High - CCI-001199 - V-81807 - SV-96521r1_rule

RMF Control

SC-28

Severity

High

CCI

CCI-001199

Version

AIOS-12-010500

Vuln IDs

V-81807

Rule IDs

SV-96521r1_rule

Passwords provide a form of access control that prevents unauthorized individuals from accessing computing resources and sensitive data. Passwords may also be a source of entropy for generation of key encryption or data encryption keys. If a password is not required to access data, this data is accessible to any adversary who obtains physical possession of the device. Requiring that a password be successfully entered before the mobile device data is unencrypted mitigates this risk. Note: MDF PP v2.0 requires a Password Authentication Factor and requires management of its length and complexity. It leaves open whether the existence of a password is subject to management. This STIGID addresses the configuration to require a password, which is critical to the cybersecurity posture of the device. SFR ID: FIA_UAU_EXT.1.1

Checks: C-81597r1_chk

Review configuration settings to confirm the device is set to require a passcode before use. This procedure is performed on the iOS device. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the password policy. 5. Tap "Restrictions". 6. Verify "Passcode" under PASSWORD POLICY is listed. If "Passcode" is not listed, this is a finding.

Fix: F-88655r1_fix

Install a configuration profile to require a password to unlock the device.

a

Apple iOS must implement the management setting: limit Ad Tracking.

CM-6 - Low - CCI-000366 - V-81809 - SV-96523r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-010600

Vuln IDs

V-81809

Rule IDs

SV-96523r1_rule

Ad Tracking refers to the advertisers' ability to categorize the device and spam the user with ads that are most relevant to the user's preferences. By not "Force limiting ad tracking", advertising companies are able to gather information about the user and device's browsing habits. If "Limit Ad Tracking" is not limited, a database of browsing habits of DoD devices can be gathered and stored under no supervision of the DoD. By limiting ad tracking, this setting does not completely mitigate the risk, but it limits the amount of information gathering. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81601r1_chk

Review configuration settings to confirm "Force limited ad tracking" is checked. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Force limited ad tracking" is checked. Alternatively, verify the text "<key>forceLimitAdTracking</key><true/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Restrictions". 6. Verify "Limit ad tracking enforced" is present. If "limited ad tracking enforced" is missing in the Apple iOS management tool, "<key>forceLimitAdTracking</key><false/>" does not appear in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Limit ad tracking enforced", this is a finding.

Fix: F-88659r1_fix

Install a configuration profile to limit advertisers' ability to track the user's web browsing preferences.

a

Apple iOS must implement the management setting: not allow automatic completion of Safari browser passcodes.

CM-6 - Low - CCI-000366 - V-81811 - SV-96525r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-010700

Vuln IDs

V-81811

Rule IDs

SV-96525r1_rule

The AutoFill functionality in the Safari web browser allows the user to complete a form that contains sensitive information, such as PII, without previous knowledge of the information. By allowing the use of the AutoFill functionality, an adversary who learns a user's Apple iOS device passcode, or who otherwise is able to unlock the device, may be able to further breach other systems by relying on the AutoFill feature to provide information unknown to the adversary. By disabling the AutoFill functionality, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81603r1_chk

Review configuration settings to confirm "Enable autofill" is unchecked. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Enable autofill" is unchecked. Alternatively, verify the text "<key>safariAllowAutoFill</key><false>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the management policy. 5. Tap "Restrictions". 6. Verify "Auto-fill in Safari not allowed" is present. If "Enable autofill" is checked in the Apple iOS management tool, or "<key>safariAllowAutoFill</key><true>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Auto-fill in Safari not allowed", this is a finding.

Fix: F-88661r1_fix

Install a configuration profile to disable the "AutoFill" capability in the Safari app.

b

Apple iOS must implement the management setting: Encrypt iTunes backups.

CM-6 - Medium - CCI-000366 - V-81813 - SV-96527r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-010800

Vuln IDs

V-81813

Rule IDs

SV-96527r1_rule

When syncing an Apple iOS device to a computer running iTunes, iTunes will prompt the user to back up the Apple iOS device. If the performed backup is not encrypted, this could lead to the unauthorized disclosure of DoD-sensitive information if non-DoD personnel are able to access that machine. By forcing the backup to be encrypted, this greatly mitigates the risk of compromising sensitive data. iTunes backup and USB connections to computers are not authorized, but this control provides defense-in-depth for cases in which a user violates policy either intentionally or inadvertently. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81605r1_chk

Review configuration settings to confirm "Force encrypted backups" is enabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Force encrypted backups" is checked. Alternatively, verify the text "<key>forceEncryptedBackup</key><true/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Encrypted backups enforced" is listed. If "Force encrypted backups" is unchecked in the Apple iOS management tool, or "<key>forceEncryptedBackup</key><false/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Encrypted backups enforced", this is a finding.

Fix: F-88663r1_fix

Install a configuration profile to force encrypted backups to iTunes.

a

Apple iOS must implement the management setting: not allow use of Handoff.

CM-6 - Low - CCI-000366 - V-81815 - SV-96529r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-010900

Vuln IDs

V-81815

Rule IDs

SV-96529r1_rule

Handoff permits a user of an Apple iOS device to transition user activities from one device to another. Handoff passes sufficient information between the devices to describe the activity, but app data synchronization associated with the activity is handled though iCloud, which should be disabled on a compliant Apple iOS device. If a user associates both DoD and personal devices to the same Apple ID, the user may improperly reveal information about the nature of the user's activities on an unprotected device. Disabling Handoff mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81607r1_chk

Review configuration settings to confirm "Allow Handoff" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow Handoff" is unchecked. Alternatively, verify the text "<key>allowActivityContinuation</key> <false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Handoff not allowed" is listed. If "Allow Handoff" is checked in the Apple iOS management tool, "<key>allowActivityContinuation</key> <true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Handoff not allowed", this is a finding.

Fix: F-88665r1_fix

Install a configuration profile to disable continuation of activities among devices and workstations.

a

Apple iOS must implement the management setting: require the user to enter a password when connecting to an AirPlay-enabled device for the first time.

AC-17 - Low - CCI-000063 - V-81817 - SV-96531r1_rule

RMF Control

AC-17

Severity

Low

CCI

CCI-000063

Version

AIOS-12-011100

Vuln IDs

V-81817

Rule IDs

SV-96531r1_rule

When a user is allowed to use AirPlay without a password, there is the potential that it may mistakenly associate the Apple iOS device with an AirPlay-enabled device other than the one intended (i.e., by choosing the wrong one from the AirPlay list displayed). This creates the potential that someone in control of a mistakenly associated device may obtain DoD-sensitive information without authorization. Requiring a password before such an association mitigates this risk. Passwords do not require any administration, nor must they comply with any complexity requirements. SFR ID: FMT_SMF_EXT.1.1 #40

Checks: C-81609r1_chk

Review configuration settings to confirm "Require passcode on first AirPlay pairing" is enabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Require passcode on first AirPlay pairing" is checked. Alternatively, verify the text "<key>forceAirPlayOutgoingRequestsPairingPassword</key><false/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "AirPlay outgoing requests pairing password enforced" is listed. If "Require passcode on first AirPlay pairing" is unchecked in the Apple iOS management tool, "<key>forceAirPlayOutgoingRequestsPairingPassword</key><true/>" appears in the configuration profile, or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "AirPlay outgoing requests pairing password enforced", this is a finding.

Fix: F-88667r1_fix

Install a configuration profile to require the user to enter a password when connecting to an AirPlay-enabled device for the first time.

b

Apple iOS must implement the management setting: Disable Allow MailDrop.

CM-6 - Medium - CCI-000366 - V-81819 - SV-96533r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-011200

Vuln IDs

V-81819

Rule IDs

SV-96533r1_rule

MailDrop allows users to send large attachments up to 5 GB in size via iCloud. Storing data with a non-DoD cloud provider may leave the data vulnerable to breach. Disabling non-DoD cloud services mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81611r1_chk

Review configuration settings to confirm "Allow MailDrop" is disabled. This validation procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow MailDrop" is not checked. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Accounts". 6. Tap the mail account. 7. Verify "Mail Drop Enabled" is set to "No". If "Allow MailDrop" is not disabled in the Apple iOS management tool or the restrictions policy on the Apple iOS device from the Apple iOS management tool lists "Mail Drop Enabled" as "Yes", this is a finding.

Fix: F-88669r1_fix

Configure the Apple iOS configuration profile to disable "Allow MailDrop".

b

Apple iOS must implement the management setting: Disable Allow Shared Albums.

CM-7 - Medium - CCI-000381 - V-81821 - SV-96535r1_rule

RMF Control

CM-7

Severity

Medium

CCI

CCI-000381

Version

AIOS-12-011300

Vuln IDs

V-81821

Rule IDs

SV-96535r1_rule

Storing data with a non-DoD cloud provider may leave the data vulnerable to breach. Disabling non-DoD cloud services mitigates this risk. Note: If the AO has approved the use/storage of DoD data in one or more personal (unmanaged) apps, allowing unrestricted activity by the user in downloading and installing personal (unmanaged) apps on the iOS 11 device may not be warranted due to the risk of possible loss of or unauthorized access to DoD data. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81613r5_chk

Note: This requirement is Not Applicable if the AO has approved users' full access to the Apple App Store for downloading unmanaged (personal) apps and syncing personal data on the device with personal cloud data storage accounts (see Section 2.9 of the STIG Supplemental document for more details). The site must have an AO-signed document showing the AO has assumed the risk for users' full access to the Apple App Store. Review configuration settings to confirm "Allow Shared Albums" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow Shared Albums" is not checked. On the Apple iOS device: 1. Open the "Settings" app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "iCloud Photos not allowed" is listed. If "Allow Shared Albums" is not disabled in the Apple iOS management tool or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "iCloud Photos not allowed", this is a finding.

Fix: F-88671r3_fix

Configure the Apple iOS configuration profile to disable "Allow Shared Albums".

c

Apple iOS device must have the latest available iOS operating system installed.

CM-6 - High - CCI-000366 - V-81823 - SV-96537r1_rule

RMF Control

CM-6

Severity

High

CCI

CCI-000366

Version

AIOS-12-011400

Vuln IDs

V-81823

Rule IDs

SV-96537r1_rule

Required security features are not available in earlier OS versions. In addition, there may be known vulnerabilities in earlier versions. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81615r1_chk

Review configuration settings to confirm the most recently released version of iOS is installed. This validation procedure is performed on both the Apple iOS management tool and the Apple iOS device. Go to http://www.apple.com and determine the most current version of iOS released by Apple. In the MDM management console, review the version of iOS installed on a sample of managed devices. This procedure will vary depending on the MDM product. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "About" and view the installed version of iOS. 4. Go back to the "General" screen. Also, tap "Software Update" and verify the following message is shown on the screen: "Your software is up to date." If the installed version of iOS on any reviewed iOS devices is not the latest released by Apple, this is a finding.

Fix: F-88673r1_fix

Install the latest release version of Apple iOS on all managed iOS devices.

b

Apple iOS must implement the management setting: use SSL for Exchange ActiveSync.

IA-2 - Medium - CCI-000764 - V-81825 - SV-96539r1_rule

RMF Control

IA-2

Severity

Medium

CCI

CCI-000764

Version

AIOS-12-011500

Vuln IDs

V-81825

Rule IDs

SV-96539r1_rule

Exchange email messages are a form of data in transit and thus are vulnerable to eavesdropping and man-in-the-middle attacks. Secure Sockets Layer (SSL), also referred to as Transport Layer Security (TLS), provides encryption and authentication services that mitigate the risk of breach. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81617r1_chk

Review configuration settings to confirm "Use SSL" for the Exchange account is enabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Use SSL" is checked under the Exchange payload. Alternatively, verify the text "<key>SSL</key><true/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the Exchange policy. 5. Tap "Accounts". 6. Tap the name of the Exchange account. 7. Verify "SSL" is set to "Yes". If "Use SSL" is unchecked in the Apple iOS management tool, "<key>SSL</key><false/>" appears in the configuration profile, or the Exchange policy on the Apple iOS device from the Apple iOS management tool has "SSL" set to "No", this is a finding.

Fix: F-88675r1_fix

Install a configuration profile to use SSL for Exchange ActiveSync.

b

Apple iOS must implement the management setting: not allow messages in an ActiveSync Exchange account to be forwarded or moved to other accounts in the Apple iOS Mail app.

CM-6 - Medium - CCI-000366 - V-81827 - SV-96541r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-011600

Vuln IDs

V-81827

Rule IDs

SV-96541r1_rule

The Apple iOS Mail app can be configured to support multiple email accounts concurrently. These email accounts are likely to involve content of varying degrees of sensitivity (e.g., both personal and enterprise messages). To prevent the unauthorized and undetected forwarding or moving of messages from one account to another, Mail ActiveSync Exchange accounts can be configured to block such behavior. While users may still send a message from the Exchange account to another account, these transactions must involve an Exchange server, enabling audit records of the transaction, filtering of mail content, and subsequent forensic analysis. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81619r1_chk

Review configuration settings to confirm "Allow messages to be moved" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Allow messages to be moved" is unchecked under the Exchange payload. Alternatively, verify the text "<key>PreventMove</key><true/>" appears in the configuration profile (.mobileconfig file). On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the Exchange policy. 5. Tap "Accounts". 6. Tap the name of the Exchange account. 7. Verify "Prevent Move" is set to "Yes". If "Allow messages to be moved" is checked in the Apple iOS management tool, "<key>PreventMove</key><false/>" appears in the configuration profile, or the Exchange policy on the Apple iOS device from the Apple iOS management tool has "Prevent Move" set to "No", this is a finding.

Fix: F-88677r1_fix

Install a configuration profile to prevent Exchange messages from being moved or forwarded between email accounts.

b

Apple iOS must implement the management setting: Treat Airdrop as an unmanaged destination.

CM-6 - Medium - CCI-000366 - V-81829 - SV-96543r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-011700

Vuln IDs

V-81829

Rule IDs

SV-96543r1_rule

An Airdrop feature is a way to send contact information or photos to other users with this same feature enabled. This feature enables a possible attack vector for adversaries to exploit. Once the attacker has gained access to the information broadcast by this feature, he/she may distribute this sensitive information very quickly and without DoD's control or awareness. By disabling this feature, the risk of mass data exfiltration will be mitigated. Note: If the site uses Apple's optional Device Enrollment Program (DEP), this control is available as a supervised MDM control. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81621r1_chk

Review configuration settings to confirm "Treat AirDrop as an unmanaged destination" is enabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Treat Airdrop as unmanaged destination" is checked. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Sharing managed documents using AirDrop not allowed" is listed. If "Treat Airdrop as unmanaged destination" is disabled in the Apple iOS management tool or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Sharing managed documents using AirDrop not allowed", this is a finding.

Fix: F-88679r1_fix

Install a configuration profile to treat AirDrop as an unmanaged destination.

a

Apple iOS must implement the management setting: not have any Family Members in Family Sharing.

CM-6 - Low - CCI-000366 - V-81831 - SV-96545r1_rule

RMF Control

CM-6

Severity

Low

CCI

CCI-000366

Version

AIOS-12-011800

Vuln IDs

V-81831

Rule IDs

SV-96545r1_rule

Apple's Family Sharing service allows Apple iOS users to create a Family Group whose members have several shared capabilities, including the ability to lock, wipe, play a sound on, or locate the Apple iOS devices of other members. Each member of the group must be invited to the group and accept that invitation. A DoD user's Apple iOS device may be inadvertently or maliciously wiped by another member of the Family Group. This poses a risk that the user could be without a mobile device for a period of time or lose sensitive information that has not been backed up to other storage media. Configuring Apple iOS devices so their associated Apple IDs are not members of Family Groups mitigates this risk. Note: If the site uses Apple's optional Device Enrollment Program (DEP), this control is available as a supervised MDM control. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81623r1_chk

Review configuration settings to confirm Family Sharing is disabled. Note that this is a User based Enforcement (UBE) control, which cannot be managed by an MDM server. This check procedure is performed on the Apple iOS device. On the Apple iOS device: 1. Open the Settings app. 2. At the top of the screen, if "Sign in to your iPhone" is listed, this requirement has been met. 3. If the user profile is signed into iCloud, tap the user name 4. Tap "Family Sharing" 5. Verify no accounts are listed other than the "Organizer" Note: The Apple iOS device must be connected to the Internet to conduct this validation procedure. Otherwise, the device will display the notice "Family information is not available", in which case it cannot be determined if the configuration is compliant. If accounts (names or email addresses) are listed under "FAMILY MEMBERS" on the Apple iOS device, this is a finding. Note: If the site has implemented DEP (not required), this setting can be managed via the MDM (supervised mode).

Fix: F-88681r1_fix

The user must either remove all members from the Family Group on the Apple iOS device or associate the device with an Apple ID that is not a member of a Family Group.

b

Apple iOS must implement the management setting: not share location data through iCloud.

AC-8 - Medium - CCI-000048 - V-81833 - SV-96547r1_rule

RMF Control

AC-8

Severity

Medium

CCI

CCI-000048

Version

AIOS-12-011900

Vuln IDs

V-81833

Rule IDs

SV-96547r1_rule

Sharing of location data is an operations security (OPSEC) risk because it potentially allows an adversary to determine a DoD user's location and movements and patterns in those movements over time. An adversary could use this information to target the user or to gather intelligence on the user's likely activities. Using commercial cloud services to store and handle location data could leave the data vulnerable to breach, particularly by sophisticated adversaries. Disabling the use of such services mitigates this risk. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81625r1_chk

Review configuration settings to confirm "Share My Location" is disabled. Note that this is a User based Enforcement (UBE) control, which cannot be managed by an MDM server. This check procedure is performed on the Apple iOS device only. On the Apple iOS device: 1. Open the Settings app. 2. Tap "Privacy". 3. Tap "Location Services". 4. Tap "Share My Location". 5. Verify "Share My Location" is off. If "Share My Location" is toggled to the right and appears green on the Apple iOS device, this is a finding.

Fix: F-88683r1_fix

The user must configure Apple iOS to disable location sharing through iCloud.

a

Apple iOS must implement the management setting: force Apple Watch wrist detection.

CM-7 - Low - CCI-000381 - V-81835 - SV-96549r1_rule

RMF Control

CM-7

Severity

Low

CCI

CCI-000381

Version

AIOS-12-012100

Vuln IDs

V-81835

Rule IDs

SV-96549r1_rule

Because Apple Watch is a personal device, it is key that any sensitive DoD data displayed on the Apple Watch not be viewable when the watch is not in the immediate possession of the user. This control ensures the Apple Watch screen locks when the user takes the watch off, thereby protecting sensitive DoD data from possible exposure. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81627r1_chk

Review configuration settings to confirm "Force Apple Watch wrist detection" is enabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the Apple iOS management tool, verify "Wrist detection enforced on Apple Watch" is enforced. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the Configuration Profile from the Apple iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Wrist detection enforced on Apple Watch" is listed. If "Wrist detection enforced on Apple Watch" is not enforced in the Apple iOS management tool or the restrictions policy on the Apple iOS device from the Apple iOS management tool does not list "Wrist detection enforced on Apple Watch", this is a finding.

Fix: F-88685r1_fix

Install a configuration profile to force Apple Watch wrist detection.

b

Apple iOS users must complete required training.

CM-6 - Medium - CCI-000366 - V-81837 - SV-96551r1_rule

RMF Control

CM-6

Severity

Medium

CCI

CCI-000366

Version

AIOS-12-012200

Vuln IDs

V-81837

Rule IDs

SV-96551r1_rule

The security posture on iOS devices requires the device user to configure several required policy rules on their device. User Based Enforcement (UBE) is required for these controls. In addition, if the AO has approved users' full access to the Apple App Store, than users must receive training on risks. If a user is not aware of their responsibilities and does not comply with UBE requirements, the security posture of the iOS mobile device may become compromised and DoD sensitive data may become compromised. SFR ID: NA

Checks: C-81629r1_chk

Review a sample of site User Agreements of iOS device users or similar training records and training course content. Verify iOS device users have completed required training. If any iOS device user is found to not have completed required training, this is a finding.

Fix: F-88687r1_fix

Have all iOS device users complete training on the following topics. Users should acknowledge they have received training via a signed User Agreement or similar written record. Training Topics: -Operational security concerns introduced by unmanaged applications including applications utilizing global positioning system (GPS) tracking -Need to ensure no DoD data is saved in an unmanaged app or transmitted from a personal app (for example, from personal email) -If the Purebred key management app is used, users are responsible for maintaining positive control of their credentialed device at all times. The DoD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys, and to report any loss of control so that the credentials can be revoked. Upon device retirement, turn in, or reassignment, ensure a factory data reset is performed prior to device hand off. Follow Mobility service provider decommissioning procedures as applicable. -How to configure the following User Based Enforcement (UBE) controls (users must configure the control) and other controls on the iOS device: **Remove Family Sharing **Disable Shared Location **Disable Wi-Fi Assist **Use AirPrint only with AO-approved printers and print servers (see the Multifunction Device STIG for requirements) **Turn off “Apps” under “AUTOMATIC DOWNLOADS” in the “iTunes & App Store” section of the Settings app on the Apple iOS device **Secure use of Calendar Alarm **Do not configure a DoD network (work) VPN profile on any third-party unmanaged VPN app **iOS device radios should be disabled using controls under "Settings" instead of "Control Center" -AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.)

b

A managed photo app must be used to take and store work related photos.

AC-20 - Medium - CCI-000097 - V-81839 - SV-96553r1_rule

RMF Control

AC-20

Severity

Medium

CCI

CCI-000097

Version

AIOS-12-012300

Vuln IDs

V-81839

Rule IDs

SV-96553r1_rule

The iOS Photos app is unmanaged and may sync photo's with a device user's personal iCloud account. Therefore work related photos should not be taken via the iOS camera app or stored in the Photos app. A managed photo app should be used to take and manage work related photos. SFR ID: NA

Checks: C-81631r1_chk

Review configuration settings to confirm a managed photos app is installed on the iOS device. This check procedure is performed on the Apple iOS device. On the Apple iOS device: 1. Open the Settings app. 2. Tap "General". 3. Tap "Profiles & Device Management". 4. Tap the DoD Configuration Profile from the Apple iOS management tool. 5. Tap "Apps". 6. Verify a photo capture and management app is listed. If a managed photo capture and management app is not installed on the iOS device, this is a finding.

Fix: F-88689r1_fix

Install a managed photos app to take and manage work related photos.

b

Apple iOS must implement the management setting: enable USB Restricted Mode.

AC-20 - Medium - CCI-000097 - V-81841 - SV-96555r1_rule

RMF Control

AC-20

Severity

Medium

CCI

CCI-000097

Version

AIOS-12-012500

Vuln IDs

V-81841

Rule IDs

SV-96555r1_rule

The USB lightning port on an iOS device can be used to access data on the device. The required settings is that this control ensures the iOS device password is entered before a previously trusted USB accessory can connect to the device. SFR ID: FMT_SMF_EXT.1.1 #47

Checks: C-81633r3_chk

Review configuration settings to confirm USB Restricted Mode is enabled. Note that this is a User based Enforcement (UBE) control, unless Supervised mode has been implemented on the iOS device. This check procedure is performed on the Apple iOS device (non-Supervised) or on an Apple iOS management tool (Supervised). If the device is not Supervised, on the Apple iOS device: 1. Open the Settings app. 2. Tap "Touch ID & Passcode" or "Face ID & Passcode". 3. Scroll down to the "USB Accessories" setting. 4. Verify the "USB Accessories" setting is off. If the device is Supervised, in the Apple iOS management tool, verify "Allow USB Accessories while device is locked" is checked (enabled). Note: The label for this configuration setting varies between MDM products. Ensure the setting is configured to disable USB accessory connection unless the device passcode is entered. If the "USB Accessories" setting on the iOS device is not off or "Allow USB Accessories while device is locked" is not checked on the iOS management tool, this is a finding.

Fix: F-88691r1_fix

If the iOS device is not Supervised, the user must disable "USB Accessories" on their iOS device. If the iOS device is Supervised, check (enable) "Allow USB Accessories while device is locked" on the Apple iOS management tool. Note: The label for this configuration setting varies between MDM products. Ensure the setting is configured to disable USB accessory connection unless the device passcode is entered.

a

Apple iOS must not allow managed apps to write contacts to unmanaged contacts accounts.

AC-8 - Low - CCI-000051 - V-81931 - SV-96645r1_rule

RMF Control

AC-8

Severity

Low

CCI

CCI-000051

Version

AIOS-12-012600

Vuln IDs

V-81931

Rule IDs

SV-96645r1_rule

Managed apps have been approved for the handling of DoD-sensitive information. Unmanaged apps are provided for productivity and morale purposes but are not approved to handle DoD-sensitive information. Examples of unmanaged apps include apps for news services, travel guides, maps, and social networking. If a document were to be viewed in a managed app and the user had the ability to open this same document in an unmanaged app, this could lead to the compromise of sensitive DoD data. In some cases, the unmanaged apps are connected to cloud backup or social networks that would permit dissemination of DoD-sensitive information to unauthorized individuals. Not allowing data to be opened within unmanaged apps mitigates the risk of compromising sensitive data. SFR ID: FMT_SMF_EXT.1.1 #42, FDP_ACF_EXT.1.2

Checks: C-81723r2_chk

Review configuration settings to confirm "Allow managed apps to write contacts to unmanaged contacts accounts" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, then the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the iOS management tool, verify "Allow managed apps to write contacts to unmanaged contacts accounts" is unchecked. On the iOS device: 1. Open the "Settings" app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Allow managed apps to write contacts to unmanaged contacts accounts" is not listed. If "Allow managed apps to write contacts to unmanaged contacts accounts" is checked in the iOS management tool or the restrictions policy on the iOS device from the iOS management tool lists "Allow managed apps to write contacts to unmanaged contacts accounts", this is a finding.

Fix: F-88781r1_fix

Install a configuration profile to prevent managed apps writing contacts to unmanaged contacts.

a

Apple iOS must not allow unmanaged apps to read contacts from managed contacts accounts.

AC-8 - Low - CCI-000051 - V-81933 - SV-96647r1_rule

RMF Control

AC-8

Severity

Low

CCI

CCI-000051

Version

AIOS-12-012700

Vuln IDs

V-81933

Rule IDs

SV-96647r1_rule

Managed apps have been approved for the handling of DoD-sensitive information. Unmanaged apps are provided for productivity and morale purposes but are not approved to handle DoD-sensitive information. Examples of unmanaged apps include apps for news services, travel guides, maps, and social networking. If a document were to be viewed in a managed app and the user had the ability to open this same document in an unmanaged app, this could lead to the compromise of sensitive DoD data. In some cases, the unmanaged apps are connected to cloud backup or social networks that would permit dissemination of DoD-sensitive information to unauthorized individuals. Not allowing data to be opened within unmanaged apps mitigates the risk of compromising sensitive data. SFR ID: FMT_SMF_EXT.1.1 #42, FDP_ACF_EXT.1.2

Checks: C-81725r2_chk

Review configuration settings to confirm "Allow unmanaged apps to read contacts from managed contacts accounts" is disabled. This check procedure is performed on both the Apple iOS management tool and the Apple iOS device. Note: If an organization has multiple configuration profiles, then the check procedure must be performed on the relevant configuration profiles applicable to the scope of the review. In the iOS management tool, verify "Allow unmanaged apps to read contacts from managed contacts accounts" is unchecked. On the iOS device: 1. Open the "Settings" app. 2. Tap "General". 3. Tap "Profiles" or "Profiles & Device Management" or "Device Management". 4. Tap the Configuration Profile from the iOS management tool containing the restrictions policy. 5. Tap "Restrictions". 6. Verify "Allow unmanaged apps to read contacts from managed contacts accounts" is not listed. If "Allow unmanaged apps to read contacts from managed contacts accounts" is checked in the iOS management tool or the restrictions policy on the iOS device from the iOS management tool lists "Allow unmanaged apps to read contacts from managed contacts accounts", this is a finding.

Fix: F-88783r1_fix

Install a configuration profile to prevent unmanaged apps to read contacts from managed contacts accounts.

Apple iOS 12 Security Technical Implementation Guide

Compare

View

Checks: C-81535r1_chk

Fix: F-88603r1_fix

Generate Mitigation Statement:

Checks: C-81537r1_chk

Fix: F-88605r1_fix

Generate Mitigation Statement:

Checks: C-81539r1_chk

Fix: F-88607r1_fix

Generate Mitigation Statement:

Checks: C-81541r1_chk

Fix: F-88609r1_fix

Generate Mitigation Statement:

Checks: C-81543r1_chk

Fix: F-88611r1_fix

Generate Mitigation Statement:

Checks: C-81545r1_chk

Fix: F-88613r1_fix

Generate Mitigation Statement:

Checks: C-81547r1_chk

Fix: F-88615r1_fix

Generate Mitigation Statement:

Checks: C-81551r1_chk

Fix: F-88619r1_fix

Generate Mitigation Statement:

Checks: C-81553r1_chk

Fix: F-88621r1_fix

Generate Mitigation Statement:

Checks: C-81555r1_chk

Fix: F-88623r1_fix

Generate Mitigation Statement:

Checks: C-81557r1_chk

Fix: F-88625r1_fix

Generate Mitigation Statement:

Checks: C-81559r1_chk

Fix: F-88627r2_fix

Generate Mitigation Statement:

Checks: C-81561r1_chk

Fix: F-88629r1_fix

Generate Mitigation Statement:

Checks: C-81563r1_chk

Fix: F-88631r1_fix

Generate Mitigation Statement:

Checks: C-81565r1_chk

Fix: F-88633r1_fix

Generate Mitigation Statement:

Checks: C-81571r1_chk

Fix: F-88637r1_fix

Generate Mitigation Statement:

Checks: C-81573r3_chk

Fix: F-88639r3_fix

Generate Mitigation Statement:

Checks: C-81575r1_chk

Fix: F-88641r1_fix

Generate Mitigation Statement:

Checks: C-81577r1_chk

Fix: F-88643r1_fix

Generate Mitigation Statement:

Checks: C-81579r1_chk

Fix: F-88645r1_fix

Generate Mitigation Statement:

Checks: C-81583r1_chk

Fix: F-88647r1_fix

Generate Mitigation Statement:

Checks: C-81585r1_chk

Fix: F-88649r1_fix

Generate Mitigation Statement:

Checks: C-81597r1_chk

Fix: F-88655r1_fix

Generate Mitigation Statement:

Checks: C-81601r1_chk

Fix: F-88659r1_fix

Generate Mitigation Statement:

Checks: C-81603r1_chk

Fix: F-88661r1_fix

Generate Mitigation Statement:

Checks: C-81605r1_chk

Fix: F-88663r1_fix