{ "name": "stig_apple_ios_9_interim_security_configuration_guide", "date": "2015-12-07", "description": "This Interim Security Configuration Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.", "title": "Apple iOS 9 Interim Security Configuration Guide", "version": "1", "item_syntax": "^\\w-\\d+$", "section_separator": null, "items": [ { "id": "V-61567", "title": "Apple iOS must lock the display after 15 minutes (or less) of inactivity.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #01b", "severity": "medium" }, { "id": "V-61889", "title": "Apple iOS must enforce a minimum password length of 6 characters.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #01a", "severity": "low" }, { "id": "V-61891", "title": "Apple iOS must not allow more than 10 consecutive failed authentication attempts.", "description": "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 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #02", "severity": "low" }, { "id": "V-61893", "title": "Apple iOS must require a valid password be successfully entered before the mobile device data is unencrypted.", "description": "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, then 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.\n\nNote: MDF PP v.2.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.\n\nSFR ID: FIA_UAU_EXT.1.1", "severity": "high" }, { "id": "V-61895", "title": "Apple iOS must not allow passwords that include more than two repeating or sequential characters.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #01b", "severity": "low" }, { "id": "V-61897", "title": "Apple iOS must not allow backup to remote systems (iCloud).", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61899", "title": "Apple iOS must not allow backup to remote systems (iCloud document and data synchronization).", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61901", "title": "Apple iOS must not allow backup to remote systems (iCloud keychain).", "description": "The iCloud Keychain is an Apple iOS function that will store users' account names and passwords in iCloud, and then synchronize this data between 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61903", "title": "Apple iOS must not allow backup to remote systems (My Photo Stream).", "description": "When My Photo Stream is enabled, sensitive photos will be automatically uploaded 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61905", "title": "Apple iOS must not allow backup to remote systems (iCloud Photo Sharing (also known as Shared Photo Streams)).", "description": "When iCloud Photo Sharing is enabled, sensitive photos will be automatically uploaded 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61907", "title": "Apple iOS must disable automatic transfer of diagnostic data to an external device other than an MDM service with which the device has enrolled.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1#45", "severity": "low" }, { "id": "V-61909", "title": "Apple iOS must implement the management setting: limit Ad Tracking.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61911", "title": "Apple iOS must not display notifications when the device is locked.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #21", "severity": "medium" }, { "id": "V-61913", "title": "Apple iOS must not display notifications (calendar information) when the device is locked.", "description": "Many mobile devices display notifications (including calendar information) 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #21", "severity": "medium" }, { "id": "V-61915", "title": "Apple iOS must not include applications with the following characteristics: Siri when the device is locked.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #10b", "severity": "medium" }, { "id": "V-61917", "title": "Apple iOS must not include applications with the following characteristics: Voice dialing application if available when MD is locked.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #10b", "severity": "medium" }, { "id": "V-61919", "title": "Apple iOS must be configured to disable Touch ID.", "description": "Many mobile devices now permit a user to unlock the user's device by presenting a fingerprint to an embedded fingerprint reader. Other biometrics and token-based systems are feasible as well. None of these alternatives are currently evaluated in a Common Criteria evaluation of a mobile device against the Security Target based on the Mobile Device Fundamentals Protection Profile. Many have known vulnerabilities. Until there are DoD-approved assurance activities to evaluate the efficacy of these alternatives, they are significant potential vulnerabilities to DoD information and information systems. Disabling them mitigates the risk of their use. Touch ID is a fingerprint reader that has been installed on some models of Apple iOS devices.\n\nSFR ID: FMT_SMF_EXT.1.1 #33", "severity": "medium" }, { "id": "V-61921", "title": "Apple iOS must implement the management setting: not allow automatic completion of Safari browser passcodes.", "description": "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 comprising other systems is significantly mitigated.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61923", "title": "Apple iOS must implement the management setting: Encrypt iTunes backups.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "high" }, { "id": "V-61925", "title": "Apple iOS must not allow backup to remote systems (enterprise books).", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61927", "title": "Apple iOS must implement the management setting: not allow use of Handoff.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61929", "title": "Apple iOS must not allow backup to remote systems (managed applications data stored in iCloud)).", "description": "Storing data with a non-DoD cloud provider may leave the data vulnerable to breach. Disabling non-DoD cloud services mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61931", "title": "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.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "low" }, { "id": "V-61933", "title": "Apple iOS must implement the management setting: Disable Allow MailDrop.", "description": "MailDrop allows users to send large attachments in up to 5GB 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61935", "title": "Apple iOS must implement the management setting: Disable Allow iCloud Photo Library.", "description": "Storing data with a non-DoD cloud provider may leave the data vulnerable to breach. Disabling non-DoD cloud services mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61939", "title": "Apple iOS must implement the management setting: use SSL for Exchange Active Sync.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61941", "title": "Apple iOS must implement the management setting: not allow messages in an Active Sync Exchange account to be forwarded or moved to other accounts in the Apple iOS Mail app.", "description": "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. \n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61943", "title": "Apple iOS must implement the management setting: disable Airdrop.", "description": "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.\n\nNote, if the site uses Apple's optional Device Enrollment Program (DEP), this control is available as a supervised MDM control.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61945", "title": "Apple iOS must implement the management setting: not have any Family Members in Family Sharing.", "description": "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 their 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 that their associated Apple IDs are not members of Family Groups mitigates this risk.\n\nNote, if the site uses Apple's optional Device Enrollment Program (DEP), this control is available as a supervised MDM control.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61947", "title": "Apple iOS must implement the management setting: not share location data through iCloud.", "description": "Sharing of location data is an 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61949", "title": "Apple iOS must not include applications with the following characteristics: payment processing (Apple Pay).", "description": "Apple Pay is a mobile payment technology that enables users to make purchases with their Apple iOS devices, provided that the vendor supports the required Near Field Communications (NFC) interface to Apple Pay. If the payment system is vulnerable to breach, a user's charge cards may be used for unauthorized payments, including charges to government-issued cards. Disabling or avoiding use of Apple Pay mitigates this risk. The use of a GFE mobile device as a personal payment system is not authorized.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61951", "title": "Apple iOS must implement the management setting: remove managed applications upon unenrollment from MDM.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61953", "title": "Apple iOS must implement the management setting: not allow a user to remove Apple iOS configuration profiles that enforce DoD security requirements.", "description": "Configuration profiles define security policies on Apple iOS devices. If a user is able to remove a configuration profile, the user can then change the configuration that had been enforced by that policy. Relaxing security policies may introduce vulnerabilities that the profiles had mitigated. Configuring a profile to never be removed mitigates this risk. \n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "medium" }, { "id": "V-61955", "title": "Apple iOS must enable VPN protection.", "description": "A key characteristic of a mobile device is that they typically will communicate wirelessly and are often expected to reside in locations outside the physical security perimeter of a DoD facility. In these circumstances, the threat of eavesdropping is substantial. Virtual private networks (VPNs) provide confidentiality and integrity protection for data transmitted over untrusted media (e.g., air) and networks (e.g., the Internet). They also provide authentication services to ensure that only authorized users are able to use them. Consequently, enabling VPN protection counters threats to communications to and from mobile devices. \n\nNote, if the site uses Apple's optional Device Enrollment Program (DEP), the Always-on VPN control is available as a supervised MDM control.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-61957", "title": "Apple iOS must not allow backup to locally connected systems.", "description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #40", "severity": "medium" }, { "id": "V-61959", "title": "Apple iOS must wipe protected or sensitive data upon unenrollment from MDM.", "description": "When a mobile device is no longer going to be managed by MDM technologies, its protected/sensitive data must be sanitized because it will no longer be protected by the MDM software, so it is at much greater risk of unauthorized access and disclosure.\n\nSFR ID: FMT_SMF_EXT.2.1", "severity": "medium" }, { "id": "V-61961", "title": "Apple iOS must implement the management setting: force Apple Watch wrist detection.", "description": "As a personal device, it is key that any DoD sensitive 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, therefore, protecting sensitive DoD data from possible exposure.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "low" }, { "id": "V-64705", "title": "Apple iOS must not allow non-DoD applications to access DoD data.", "description": "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.\n\nSFR ID: FMT_SMF.1.1 #42", "severity": "medium" }, { "id": "V-64709", "title": "Apple iOS device must have the latest available iOS operating system installed.", "description": "Required security features are not available in earlier OS versions. In addition, there are known vulnerabilities in earlier versions.\n\nSFR ID: FMT_SMF_EXT.1.1 #45", "severity": "high" } ] }