The key that stays and the key that travels: where a passkey lives on an iPhone and a Mac
The Secure Enclave keeps one key that never leaves the chip. A passkey saved to iCloud Keychain is a different key, stored in the keychain, and it moves between your devices.
By Pavel Nikolov, November 12, 2026A passkey is a pair of keys that replaces a password. When you register with a website, your device creates the pair, keeps the private key and sends the site the public key. To sign in, the site sends a random number called a challenge, your device signs it with the private key, and the site checks the signature with the public key. The private key is never sent anywhere, so a breach of the website leaks nothing that can sign in.
On October 15, 2026, the FIDO Alliance, the industry group behind the passkey standards, estimated that 7 billion passkeys are in use. Its Passkey Index covers 15 large consumer services. MojoAuth’s reading of the report puts passkeys at 36% of successful sign-ins, up from 26% a year earlier, with a 93% success rate against 78% for passwords and older two-step methods. Biometric Update reports that 90% of accounts at those services could use a passkey and 42% have one.
For about a third of sign-ins at those services, the secret used is a key held on the user’s device. That makes the storage question practical. If someone steals the phone, copies the disk or takes over the Apple Account, the answer decides what they get.
The answer I hear most often is that the passkey is stored in the Secure Enclave and Face ID unlocks it. The Secure Enclave is a small separate processor inside Apple’s chips that handles keys and biometric matching. A Corbado help page says passkeys in iCloud Keychain “are stored in the Secure Enclave”. A reply on Apple’s own community forum says the private key is kept in the Secure Enclave and regenerated on each device. A 2023 Hacker News thread argues both sides.
Apple’s documents describe something else. Passkeys sync across a user’s devices using iCloud Keychain. A key created in the enclave through the interface Apple gives developers cannot do that, because Apple’s developer documentation says there is no mechanism to transfer plain-text key data into or out of the Secure Enclave. Since iOS 26, the Passwords app can also export passkeys to another password manager. NIST, the US standards agency, states the logic in one sentence.
“Syncing authentication keys inherently means that the key can be exported.” NIST SP 800-63B-4, Appendix B
In my hardware wallet deep dive I wrote that synced passkeys are, by design, not bound to a single chip, and left it there. This piece follows the passkey to where it does live, and works out what the enclave, Touch ID and Face ID do for it.
The Secure Enclave keeps one key in place
Each Apple chip has a unique key fused in at the factory. By Apple’s account it cannot be read, copied or exported, even by the enclave’s own software. The enclave uses it to lock the secrets stored on a device to that device, and it decides, after a passcode or a biometric match, when to unlock them.
The keychain carries the passkey
The passkey’s private key is a row in an encrypted database on ordinary storage. It syncs to your other devices through iCloud, can be shared with another person, recovered after you lose every device, and exported. It is built to move.
I think of them as two keys. One stays. It is the device’s own key, and nothing about it ever appears outside the chip. The other travels. It is your passkey, and on each device it rests inside a box that only that device’s staying key can open. Touch ID and Face ID are neither key. They are how you tell the enclave to open the box without typing your passcode.
This picture holds for the part Apple documents: where the passkey is stored, how it is encrypted and how it moves. It needs three limits to stay honest. First, Apple does not say which processor computes the signature for a synced passkey, so I do not claim to know. Second, the enclave does create and use some keys entirely inside itself. Chrome’s own Touch ID credentials on a Mac are an example, they begin with the same touch, and Part 2 covers them. Third, “travels” does not mean “exposed”. On a locked, stolen iPhone the passkey is as well protected as anything on the device, and Part 4 shows where that stops being true.
Part 2 explains the key that stays: the enclave, the passcode, Touch ID and Face ID. Part 3 follows the key that travels through the keychain, iCloud sync, escrow and export. Part 4 walks through one sign-in and lists what each kind of attacker needs. Part 5 sets out what to do on your own devices and in a product that accepts passkeys.
Two keys on one timeline, 2013 to 2026
Every event in this piece, newest first. The tag shows which side it belongs to: the enclave and its biometric sensors, the keychain and its sync, the adoption numbers, or the standards that respond. Each name links to its source, and the right-hand link goes to the part that covers it.
Three places, three jobs
On an iPhone or a Mac the pieces of a passkey sign-in sit in three places. The enclave is hardware. The keychain is a file. iCloud is a server that holds the file’s contents in a form it cannot read. Keeping the three apart answers most questions about what an attacker gets from each.
One key that never leaves
A separate processor inside the main chip. It keeps the device’s unique key, uses it to wrap and unwrap other keys, enforces the limit on passcode attempts and matches faces and fingerprints. Apple says it does not include storage of its own.
The passkey, encrypted
A database file on the same flash storage as your photos. The private key of each passkey is a row in it, encrypted with a key that only this device’s enclave can unwrap. Keys the enclave creates are filed here too, as sealed blobs that only that enclave can use.
The same passkey, in transit
An encrypted copy that Apple’s servers pass between your devices. Only devices in your circle of trust can decrypt it. A second escrow copy lets you recover with your passcode.
The first column has a detail that surprised me. Apple writes that the Secure Enclave “doesn’t include storage” and instead protects information kept on storage attached to it. The enclave is a machine for using keys. By Apple’s description, the only keys fixed inside it are its unique key and a group key shared by chips of the same model. Everything else, including keys the enclave itself creates, is stored outside it in encrypted form.
The unique key deserves one caution. Everything I say about it comes from Apple. Apple writes that since the A9 chip the enclave’s own random number generator creates the UID during manufacturing, and that on earlier chips a randomly generated UID is fused in, with no detail on where the number comes from. No hardware security module is involved in Apple’s account. Nobody outside Apple can check these statements directly. The key cannot be read out, so researchers cannot collect UIDs from many devices and test them for randomness or for duplicates.
The nearest outside check is certification. In 2019 the enclave’s key store was validated under the US government’s FIPS 140-2 standard at Security Level 2, and Apple says its independent certifications often verify information in its security guide. In the Apple certification pages I read, nothing says those tests cover the factory step where the UID is fused.
If I assume the validation does cover the UID, Level 2 would mean three things for it. The UID would come from an approved random bit generator, so it could not be predicted from knowledge of the chip. The module would have to protect it from unauthorized disclosure and substitution. And the chip would have to show evidence of physical tampering. Level 2 does not require the chip to resist or respond to tampering, and a validation examines the design and the units submitted for testing, so trust in the factory would remain. This is my summary of the standard from general knowledge. I have not checked it against the standard’s text or Apple’s certificate.
The passkey’s key pair is separate from the UID and is not derived from it. Apple says the operating system creates a unique key pair for each account when you register. The public key goes to the website. The private key goes into the keychain, where the chain of wrapping keys that starts at the UID protects it on that device. So the UID’s quality decides one thing, whether the stored private key can be attacked away from the chip. With a predictable or copied UID, someone holding a copy of the device’s storage could guess passcodes on their own hardware, past the ten-attempt limit that Part 2 describes. On recent devices they would also need a second secret, held in the Secure Storage Component that Part 2 covers.
Trust in the pair comes from elsewhere. The website trusts the public key because a signed-in user registered it, and from then on it trusts the mathematics of the signature. For an iCloud Keychain passkey it receives no proof of what hardware holds the private key, as Part 4 explains, so neither the UID nor any certification enters its decision. Even on the generous reading, “random and unknown to Apple” is a vendor claim with partial third-party testing around it, and it bears only on how well a passkey is protected at rest on one device.
How the UID protects a key it never touches
Encryption is a pair of functions. E(K, m) turns a message m into unreadable data c, and D(K, c) turns c back into m. Both need the same key K. If K is a random 256-bit number there are 2256 candidates, and nobody finds it by trying them. Wrapping is the same operation applied to a key, so the message m is itself a key.
On the device, the passkey’s private key, call it sk, sits at the end of a short chain. The disk holds c1 = E(krow, sk), the private key encrypted under a key that belongs to its keychain row. The disk also holds c2 = E(kclass, krow), the row key encrypted under a class key. The class key is not on the disk in usable form. The enclave rebuilds it when you unlock, as kclass = f(passcode, UID). This is my simplified version of Apple’s design, which has more layers of the same kind and, on recent devices, a further secret held in a second chip.
Someone who copies the disk gets c1 and c2. To read sk they have to work backward. sk needs krow, krow needs kclass, and kclass needs both inputs of f. The passcode is the weak input, since six digits give only 106 possibilities. If the formula were f(passcode) alone, the attacker could run all million guesses on their own computer and test each one against c2. At an illustrative billion guesses per second, that takes a thousandth of a second.
The UID is the second input, and it exists only inside the chip. The enclave behaves like a calculator with a hidden constant. You can give it a passcode and it will compute f(passcode, UID), and it has no button that shows the UID. So every guess has to be entered into that one chip, and on an iPhone the chip stops after ten wrong ones. Against a random six-digit passcode, the attacker’s chance of success drops from certain to 10 / 106, or 1 in 100,000. The UID protects the passkey without ever encrypting it directly, by being an ingredient at the top of the chain that cannot leave the chip. Part 2 covers each link.
What each key does
The two keys differ in what they are, where they live, whether they can leave, and what happens when the device is gone.
| The key that stays | The key that travels | |
|---|---|---|
| What it is | The device’s unique key (UID), random and fused into the chip at manufacturing | The private signing key of one passkey, for one account on one website |
| Where it lives | Inside the Secure Enclave’s hardware, not visible even to the enclave’s own software | In the keychain database on device storage, and encrypted in iCloud Keychain |
| Can it leave the device | No. There is no export path | Yes, by sync, by sharing with people you trust, in a password-protected backup, and since iOS 26 by export to another password manager |
| What protects it | A separate processor, encrypted memory, and circuits that halt the enclave if voltage or clock speed is pushed out of range | Encryption under keys that the enclave unwraps after a passcode, Touch ID or Face ID check |
| If you lose every device | It is gone, and nothing depends on getting it back | Recoverable from iCloud Keychain escrow with the account password, an SMS code and a device passcode |
| Who else can hold a copy | Nobody. Apple says neither it nor its suppliers can read it | Your other devices, people you share it with, and any password manager you export it to |
Sources for the table: The Secure Enclave, Keychain data protection, About the security of passkeys, Set up iCloud Keychain, 9to5Mac on iOS 26.
A passkey is protected on a lost phone because of the first column and useful across devices because of the second. The risk sits where the two meet, at the passcode that tells the staying key to open the box and at the recovery path that lets the traveling key reach a new device.
Continue to Part 2: The key that stays