iOS, the Secure Enclave and extraction

How the Secure Enclave, passcode-derived keys, USB Restricted Mode, Stolen Device Protection and checkm8 shape what can be extracted from an iPhone.

Updated

In short

Apple states that the passcode is entangled with the device UID, so brute-force attempts must be run on the device under attack. The 2021 Johns Hopkins review found no public evidence that extracting the UID from silicon was economically feasible, and the GrapheneOS project said in 2026 that there was not yet a known case of secure-element rate limiting being bypassed on iPhone 12 or later, although older devices had eventually been broken; that is a project claim and cannot be verified from public sources. Elcomsoft describes the checkm8 bootrom exploit as available for chips from the A5 to the A11, and says that on A11 devices file-system access after checkm8 is impossible on iOS 16 if a passcode was ever set after setup. In April 2026 Elcomsoft reported agent coverage of iOS 16.7 through 16.7.15, all of iOS 17 and iOS 18 through 18.7.1 on A11 to A18 chips, less stable on the iPhone 16, with installation needing a trusted connection; every vendor capability statement is that vendor's own claim.

The layers between an examiner and the data

On a current iPhone, user data is protected by file encryption whose keys depend on a hardware key and, for most data, on the passcode. Getting data therefore needs some combination of three things: code running on the device (an exploit or a sideloaded agent), the passcode or a way to guess it, and a lock state in which the needed keys are in memory. This guide covers the mechanisms that control each. For lock states see BFU vs AFU, and for terminology see acquisition types.

The Secure Enclave and passcode-derived keys

Apple's Secure Enclave documentation describes a dedicated processor with its own secure boot, in which a randomly generated UID is fused into the SoC at manufacture. On devices first released in fall 2020 or later (iPhone 12 and later), passcode-protected keys are rooted in entropy held in counter lockboxes in a second-generation Secure Storage Component. On each attempt the counter is incremented, and if it exceeds the maximum attempt value the lockbox is erased. Older Secure Enclave devices use earlier secure-storage designs.

The passcode documentation states that the passcode is entangled with the device UID, so brute-force attempts must be run on the device under attack, and that the iteration count is calibrated so one attempt takes about 80 milliseconds. Escalating delays after failed attempts are enforced by the Secure Enclave and persist across a restart (the timer restarts for the current period). If the user enables Erase Data, ten consecutive incorrect attempts remove all content and settings. Which data classes depend on the passcode is described in the data protection classes page.

The Johns Hopkins review (Zinkus, Jois and Green, 2021) puts the consequence plainly: keys must be derived on the device unless the UID is physically extracted from silicon, and it found no public evidence that this was economically feasible. It also explains why older iPhones were weaker: devices without a Secure Enclave enforced guess limits in the application processor, where bugs and hardware attacks, such as Skorobogatov's 2016 NAND-mirroring attack on the iPhone 5C, defeated the retry counter. The same review inferred, from alleged leaked GrayKey screenshots, that guessing attacks had been run against an iPhone X on iOS 11.2.5, and noted that commercial tools could reach newer devices. The GrapheneOS project, which develops a hardened Android, stated on 2026-08-05 that there was not yet a known case of secure-element rate limiting being bypassed on iPhone 12 or later or Pixel 6 or later, while older devices had eventually been broken. That is a project claim and cannot be verified from public sources.

USB Restricted Mode and Stolen Device Protection

USB Restricted Mode is described in the Johns Hopkins review, which cites Apple's article "Using USB accessories with iOS 11.4.1 and later". Apple's current page says that by default the device must be unlocked before it communicates with an accessory or computer, that once unlocked the accessory stays connected even if the device locks again, and that the device charges from a power adapter even when locked. Devices with USB-C offer four accessory settings (Always Ask, Ask for New Accessories, Automatically Allow When Unlocked, Always Allow); Lightning devices offer two. The review notes that seizing officers keep devices charged and use inexpensive adapters so the restriction does not engage, and that it can be bypassed in some circumstances by booting to DFU and delivering an exploit. Elcomsoft states, for its bootloader-based method on supported older devices, that USB Restricted Mode can be bypassed (vendor page).

Stolen Device Protection (iOS 17.3 or later, Apple) adds requirements when the iPhone is away from familiar locations: some actions need Face ID or Touch ID with no passcode fallback, and some, such as changing the Apple Account password, add a one-hour security delay. It must be turned on before the device is lost. Its main relevance to forensics is indirect: Elcomsoft reports that on iOS 17.3 or later with it enabled, establishing the trusted connection that agent installation needs requires biometric authentication rather than just the passcode (vendor blog).

Inactivity reboot and Lockdown Mode

Since iOS 18.1 the Secure Enclave tracks time since the last unlock and, after 72 hours, triggers a reboot that returns the device to BFU (Classen, 2024-11-17); details and sources are in BFU vs AFU.

Apple describes Lockdown Mode as an optional, extreme protection for the very few people who might be personally targeted by sophisticated threats such as mercenary spyware, and says the device does not function as it normally would when it is on. On 2026-02-04 404 Media reported that a court record indicated the FBI could not get into a reporter's iPhone with Lockdown Mode enabled, and cautioned "at least for now". A single court record is thin evidence; read it as one data point.

checkm8 and what it does not give you

checkm8 is a bootrom exploit published by axi0mX. The ipwndfu README calls it a "permanent unpatchable bootrom exploit for hundreds of millions of iOS devices". Because it lives in read-only boot code, an iOS update cannot fix it. Elcomsoft describes it as available for chips from the A5 (iPhone 4s) to the A11 Bionic (iPhone 8, 8 Plus and iPhone X) (2023-10). The checkra1n jailbreak, built on it, advertised support for iPhone 5s through iPhone X on iOS 12.0 and up (project site). The Johns Hopkins review says these exploits "seem to be widely implemented" in forensic tools in 2020 and infers that Cellebrite is using checkm8; it describes them as working regardless of iOS version up to the iPhone X.

The limits are specific, and they are the point of the Secure Enclave design:

  • A bootrom exploit gives code execution before iOS boots. It does not give control of the Secure Enclave. Elcomsoft quotes the checkra1n developers in 2020: on A10 and later, if a device booted from DFU asks the Secure Enclave to decrypt user data, the Secure Enclave will panic the device. The same passage says a separate Secure Enclave vulnerability ("blackbird") was expected to allow that mitigation to be disabled on A10 and A10X (vendor blog, 2020-09).
  • Apple patched around it on A11 devices. Elcomsoft states that on iPhone 8, 8 Plus and X, file-system access after checkm8 is impossible on iOS 16 if a passcode was ever set after setup, and that iOS 14 and 15 require the passcode to be removed first (2023-10). In April 2026 it restated that, for A11 iPhones, checkm8 extraction works only if a passcode was never configured, and recommended it for A11 devices only on iOS 11 to 13 (2026-04).
  • For locked devices the vendor claims only partial results. Its product page lists "Partial file system & keychain acquisition for BFU, locked and disabled iPhone models" from iPhone 5s through iPhone X (vendor page). In BFU the passcode-derived keys are not in memory, so passcode-protected classes stay encrypted.

The practical result is that checkm8 is a strong tool for A5 to A11 hardware (with the A11 limits above) and not applicable to A12 and later.

Agent-based extraction

An agent is an app sideloaded onto the device that uses an exploit chain to read the file system and keychain. Elcomsoft's description: it elevates privileges, escapes the sandbox, reaches the root of the file system and the keys needed to decrypt the keychain, and opens a channel to the examiner's computer (2026-04). In April 2026, with iOS Forensic Toolkit 10.0, the vendor reported agent coverage of iOS 16.7 through 16.7.15, all of iOS 17 and iOS 18 through 18.7.1 on A11 to A18 devices, with less stable behaviour on the iPhone 16, plus improved extended logical extraction for iOS and iPadOS 26. It also lists operational prerequisites: Developer Mode (requires a reboot), a network connection to validate certificates for newer developer accounts, and a trusted connection. Elcomsoft says installing the agent needs a trusted connection, which on its description means entering the passcode on the device. Its product page separately lists access to locked devices via lockdown records; whether that applies to agent installation is not stated. Johns Hopkins describes the generic requirement: such agents need a kernel compromise or the ability to run unsigned code. See the Elcomsoft iOS Forensic Toolkit tool page.

Every capability statement from a vendor in this guide is that vendor's own claim, dated as shown, and applies to the product versions it names.

Sources

  1. Apple Platform Security Guide, The Secure Enclave
  2. Apple Platform Security Guide, Passcodes and passwords
  3. Apple Platform Security Guide, Data protection classes
  4. Apple Support, Allow USB and other accessories to connect to your iPhone or iPad
  5. Apple Support, About Stolen Device Protection for iPhone
  6. Apple Platform Security Guide, Lockdown Mode security
  7. Zinkus, Jois, Green (Johns Hopkins), Data Security on Mobile Devices: Current State of the Art, Open Problems, and Proposed Solutions (2021)
  8. axi0mX, ipwndfu (checkm8) README
  9. checkra1n project site
  10. Elcomsoft blog, iOS 14 Forensics: What Has Changed Since iOS 13.7? (2020-09, vendor)
  11. Elcomsoft blog, Using and Troubleshooting the checkm8 Exploit (2023-10, vendor)
  12. Elcomsoft blog, Low-Level Extraction for iOS 17 and 18 (2026-04-14, vendor)
  13. Elcomsoft iOS Forensic Toolkit product page (vendor)
  14. GrapheneOS on Mastodon, secure-element rate limiting not known bypassed on iPhone 12+ / Pixel 6+ (2026-08-05, project statement)
  15. Jiska Classen, Reverse engineering iOS 18 inactivity reboot (2024-11-17)
  16. 404 Media, FBI Couldn't Get into WaPo Reporter's iPhone Because It Had Lockdown Mode Enabled (2026-02-04)