|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Secure Enclave Processor"
| Line 5: | Line 5: | ||
==SEP OS== |
==SEP OS== |
||
| − | The SEP has its own OS called SEP OS and there exists a tool called [[seputil]] which is used to communicate with it. |
+ | The SEP has its own OS called SEP OS which is based on seL4[https://www.blackhat.com/docs/us-16/materials/us-16-Mandt-Demystifying-The-Secure-Enclave-Processor.pdf] and there exists a tool called [[seputil]] which is used to communicate with it. |
==Further References== |
==Further References== |
||
Revision as of 07:29, 7 March 2020
The Secure Enclave is part of the A7 and newer chips used for data protection, Touch ID, and Face ID. The purpose of the Secure Enclave is to handle keys and other info such as biometrics that is sensitive enough to not be handled by the AP. It is isolated with a hardware filter so the AP cannot access it. It shares RAM with the AP, but it's portion of the RAM (known as TZ0) is encrypted. The secure enclave itself is a flashable 4MB AKF processor core called the secure enclave processor (SEP) as documented in Apple Patent Application 20130308838. The technology used is similar to ARM's TrustZone/SecurCore but contains proprietary code for Apple KF cores in general and SEP specifically. It is also responsible for generating the UID key on A9 or newer chips that protects user data at rest.
The SEP is located in the devicetree under IODeviceTree:/arm-io/sep and manged by the AppleSEPManager driver as seen here
SEP OS
The SEP has its own OS called SEP OS which is based on seL4[1] and there exists a tool called seputil which is used to communicate with it.
