The Target of Evaluation (TOE) is Apple iOS 12 on iPhone and iPad devices using the A8/A8X processor (iPhone 6, iPhone 6 Plus, iPad mini 4, iPad Air 2), A9/A9X processor (iPhone 6s Plus, iPhone 6s, iPhone SE, iPad 9.7-inch, iPad Pro 12.9-inch), A10 Fusion/A10X Fusion processor (iPhone7 Plus, iPhone 7, iPad 9.7-inch, iPad Pro 12.9-inch, iPad Pro 10.5-inch), A11 Bionic processor (iPhone 8, iPhone 8 Plus, iPhone X), A12 Bionic (iPhone XS, iPhone XS Max, iPhone XR), A12X Bionic (iPad Pro 11-inch, iPad Pro 12.9-inch)
","evaluation_configuration":"\r\n\r\nDevices Covered by the Evaluation
\r\n| \r\n\r\n | \r\n\r\n Device Name \r\n | \r\n\r\n Model Number \r\n | \r\n
| \r\n A8 \r\n | \r\n\r\n iPhone 6 \r\n | \r\n\r\n A1549 \r\n | \r\n
| \r\n A1586 \r\n | \r\n||
| \r\n A1589 \r\n | \r\n||
| \r\n iPhone 6 Plus \r\n | \r\n\r\n A1522 \r\n | \r\n|
| \r\n A1524 \r\n | \r\n||
| \r\n A1593 \r\n | \r\n||
| \r\n iPad mini 4 \r\n | \r\n\r\n A1538 \r\n | \r\n|
| \r\n A1550 \r\n | \r\n||
| \r\n A8X \r\n | \r\n\r\n iPad Air 2 \r\n | \r\n\r\n A1566 \r\n | \r\n
| \r\n A1567 \r\n | \r\n||
| \r\n A9 \r\n | \r\n\r\n iPhone 6s \r\n | \r\n\r\n A1633 \r\n | \r\n
| \r\n A1688 \r\n | \r\n||
| \r\n A1691 (China) \r\n | \r\n||
| \r\n A1700 (China) \r\n | \r\n||
| \r\n iPhone 6s Plus \r\n | \r\n\r\n A1634 \r\n | \r\n|
| \r\n A1687 \r\n | \r\n||
| \r\n A1690 (China) \r\n | \r\n||
| \r\n A1699 (China) \r\n | \r\n||
| \r\n iPhone SE \r\n | \r\n\r\n A1662 \r\n | \r\n|
| \r\n A1723 (China) \r\n | \r\n||
| \r\n A1724 (China) \r\n | \r\n||
| \r\n iPad 9.7-inch \r\n(5th generation) \r\n | \r\n\r\n A1822 \r\n | \r\n|
| \r\n A1823 \r\n | \r\n||
| \r\n A9X \r\n | \r\n\r\n iPad Pro 12.9-inch \r\n | \r\n\r\n A1584 \r\n | \r\n
| \r\n A1652 \r\n | \r\n||
| \r\n iPad Pro 9.7-inch \r\n | \r\n\r\n A1673 \r\n | \r\n|
| \r\n A1674 \r\n | \r\n||
| \r\n A1675 \r\n | \r\n||
| \r\n A10 Fusion \r\n | \r\n\r\n iPhone 7 \r\n\r\n | \r\n\r\n A1660 \r\n | \r\n
| \r\n A1779 (Japan) \r\n | \r\n||
| \r\n A1780 (China) \r\n | \r\n||
| \r\n A1778 \r\n | \r\n||
| \r\n iPhone 7 Plus \r\n | \r\n\r\n A1661 \r\n | \r\n|
| \r\n A1785 (Japan) \r\n | \r\n||
| \r\n A1786 (China) \r\n | \r\n||
| \r\n A1784 \r\n | \r\n||
| \r\n iPad 9.7-inch | \r\n\r\n A1893 \r\n | \r\n|
| \r\n A1954 \r\n | \r\n||
| \r\n A10X Fusion \r\n | \r\n\r\n iPad Pro 12.9-inch (2nd generation) \r\n | \r\n\r\n A1670 \r\n | \r\n
| \r\n A1671 \r\n | \r\n||
| \r\n A1821 (China) \r\n | \r\n||
| \r\n iPad Pro 10.5-inch \r\n | \r\n\r\n A1701 \r\n | \r\n|
| \r\n A1852 (China) \r\n | \r\n||
| \r\n A1709 \r\n | \r\n||
| \r\n A11 Bionic \r\n | \r\n\r\n iPhone 8 \r\n\r\n | \r\n\r\n A1863 \r\n | \r\n
| \r\n A1906 (Japan) \r\n | \r\n||
| \r\n A1907 \r\n | \r\n||
| \r\n A1905 (GSM) \r\n | \r\n||
| \r\n iPhone 8 Plus \r\n | \r\n\r\n A1864 \r\n | \r\n|
| \r\n A1898 (Japan) \r\n | \r\n||
| \r\n A1899 \r\n | \r\n||
| \r\n A1897 (GSM) \r\n | \r\n||
| \r\n iPhone X \r\n | \r\n\r\n A1865 (Japan) \r\n | \r\n|
| \r\n A1902 (Japan) \r\n | \r\n||
| \r\n A1903 (Japan) \r\n | \r\n||
| \r\n A1901 \r\n | \r\n||
| \r\n A12 Bionic \r\n | \r\n\r\n iPhone XS \r\n | \r\n\r\n A1920 (US/CA/HK) \r\n | \r\n
| \r\n A2097 \r\n | \r\n||
| \r\n A2098 (Japan) \r\n | \r\n||
| \r\n A2099 (Global) \r\n | \r\n||
| \r\n A2100 (China) \r\n | \r\n||
| \r\n iPhone XS Max \r\n | \r\n\r\n A1921 (US/CA) \r\n | \r\n|
| \r\n A2101 (Global) \r\n | \r\n||
| \r\n A2102 (Japan) \r\n | \r\n||
| \r\n A2103 (Global) \r\n | \r\n||
| \r\n A2104 (China/HK) \r\n | \r\n||
| \r\n iPhone XR \r\n | \r\n\r\n A1984 (US/CA) \r\n | \r\n|
| \r\n A2105 (Global) \r\n | \r\n||
| \r\n A2106 (Japan) \r\n | \r\n||
| \r\n A2107 (US/CA) \r\n | \r\n||
| \r\n A2108 (HK/China) \r\n | \r\n||
| \r\n A12X Bionic \r\n | \r\n\r\n iPad Pro 11-inch \r\n | \r\n\r\n A1934 (US/CA) \r\n | \r\n
| \r\n A1979 (China) \r\n | \r\n||
| \r\n A1980 \r\n | \r\n||
| \r\n A2013 (US/CA) \r\n | \r\n||
| \r\n iPad Pro 12.9-inch \r\n | \r\n\r\n A2014 (US/CA) \r\n | \r\n|
| \r\n A1876 \r\n | \r\n||
| \r\n A1895 \r\n | \r\n||
| \r\n A1983 (China) \r\n | \r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process. The criteria against which Apple iOS 12 were judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 R5. The evaluation methodology used by the evaluation team to conduct the evaluation was the Common Methodology for Information Technology Security Evaluation, Version 3.1 R5. The product, when delivered and configured as identified in the Apple iPad and iPhone Mobile Devices with iOS 12 Common Criteria Configuration Guide, meets the requirements of the Protection Profile for Mobile Device Fundamentals Version 3.1; the Extended Package for Mobile Device Management Agents Version 3.0; the Mobile Device Fundamentals Protection Profile Extended Package (EP) Wireless Local Area Network (WLAN) Client Version 1.0; the PP-Module for Virtual Private Network (VPN) Clients Version 2.1.
\r\n\r\n\r\n\r\n
The Apple iPad and iPhone Mobile Devices with iOS 12 Common Criteria Configuration Guide document satisfies all of the security functional requirements stated in the Apple iPad and iPhone Mobile Devices with iOS 12 Security Target V1.6. The evaluation project was subject to CCEVS Validator review. The evaluation was completed in March 2019. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report number CCEVS-VR-VID10937-2019, prepared by CCEVS.
\r\n","environmental_strengths":"\r\n\r\n
The TOE provides cryptographic services for the encryption of data-at rest, for secure communication channels, and for use by applications. In addition, the TOE implements a number of cryptographic protocols that can be used to establish a trusted channel to other IT entities.
\r\nAs noted in the Security Target, section 1.5.2.1 the TOE provides cryptographic services via the following cryptographic modules.
\r\n· Apple CoreCrypto Cryptographic Module for ARM, v9.0 (User Space)
\r\n· Apple CoreCrypto Cryptographic Kernel Module for ARM, v9.0 (Kernel Space)
\r\n· Apple Secure Key Store Cryptographic Module, v9.0
\r\nExcept for making emergency calls, answering calls, using the cameras, and using the flashlight, users need to authenticate using a passcode or a biometric authentication factor (BAF) (fingerprint or face). On power up, or after an update of iOS the user is required to use the passcode authentication mechanism.
\r\nThe passcode can be configured for a minimum length, for dedicated passcode policies, and for a maximum life time. When entered, passcodes are obscured and the frequency of entering passcodes is limited as well as the number of consecutive failed attempts of entering the passcode.
\r\nThe TOE also enters a locked state after a (configurable) time of user inactivity and the user is required to either enter the passcode or use biometric authentication (fingerprint or face) to unlock the TOE.
\r\nExternal entities connecting to the TOE via a secure protocol (Extensible Authentication Protocol Transport Layer Security (EAP-TLS), Transport Layer Security (TLS) and IPsec can be authenticated using X.509 certificates.
\r\nUser data in files is protected using cryptographic functions, ensuring this data remains protected even if the device gets lost or is stolen. Critical data, like passcodes used by applications or application defined cryptographic keys, can be stored in the key chain, which provides additional protection. Passcode protection and encryption ensure that data-at-rest remains protected even in the case of the device being lost or stolen.
\r\nThe Secure Enclave Processor (SEP), a separate CPU that executes a stand-alone operating system and has separate memory, provides protection for critical security data such as keys.
\r\nData can also be protected such that only the application that owns the data can access it.
\r\nThe security functions listed in the Security Target can be managed either by the user or by an authorized administrator through a Mobile Device Management (MDM) system. The Security Target identifies the functions that can be managed and indicates if the management can be performed by the user, by the authorized administrator, or both.
\r\nSome of the functions the TOE implements to protect the TSF and TSF data are:
\r\n· Protection of cryptographic keys—keys used for TOE internal key wrapping and for the protection of data-at-rest are not exportable. There are provisions for fast and secure wiping of key material.
\r\n· Use of memory protection and processor states to separate applications and protect the TSF from unauthorized access to TSF resources—in addition, each device includes a separate system called the \"secure enclave\" which is the only system that can use the Root Encryption Key (REK). The secure enclave is a separate CPU that executes a stand-alone operating system and has separate memory.
\r\n· Digital signature protection of the TSF image—all updates to the TSF need to be digitally signed.
\r\n· Software/firmware integrity self-test upon start-up—the TOE will not go operational when this test fails.
\r\n· Digital signature verification for applications
\r\n· Access to defined TSF data and TSF services only when the TOE is unlocked
\r\nThe TSF provides functions to lock the TOE upon request and after an administrator-configurable time of inactivity.
\r\nAccess to the TOE via a wireless network is controlled by user/administrator defined policy.
\r\nTrusted Path/Channels
\r\nThe TOE supports the use of the following cryptographic protocols that define a trusted channel between itself and another trusted IT product:
\r\n· IEEE 802.11-2012
\r\n· IEEE 802.1X
\r\n· EAP-TLS (1.0, 1.1, 1.2)
\r\n· TLS (1.2)
\r\n· IPsec
\r\n· Bluetooth (4.0, 4.2, 5.0)
\r\nThe TOE provides the ability for responses to be sent from the MDM Device Agent to the MDM Server. These responses are configurable by the organization using a scripting language given in the Over-the-Air Profile Delivery and Configuration document.
","features":[]}