Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
iOS security rests on a hardware root of trust, the Secure Enclave, mandatory code signing, and a sandbox that applies to every app, including Apple’s own.

What Is the iOS Security Architecture?
Apple designs iOS as a single system in which silicon, operating system, and distribution model are all under one supplier’s control. The security architecture reflects that: a hardware root of trust in the Boot ROM, a separate Secure Enclave for keys and biometrics, encryption tied to the user’s passcode, mandatory code signing, and a sandbox that constrains every application including Apple’s own.
Power on an iPhone and the first code to run is the Boot ROM, written at manufacture and immutable thereafter. It verifies the iBoot bootloader, which verifies the kernel, which verifies the system volume—a signed sequence with no point at which unsigned code is accepted. The signed system volume added in iOS 15 goes further, mounting the operating system read-only with a cryptographic seal, so tampering is detectable rather than merely difficult.
Immutability cuts both ways. Checkm8, published in 2019, exploited a Boot ROM use-after-free present in A5 through A11 chips, and because the ROM cannot be patched, every affected device—up to the iPhone X—remains permanently jailbreakable with physical access. Apple fixed it in A12 silicon and nowhere else.
Since the A7, Apple ships a separate processor with its own boot ROM, encrypted memory, and a hardware random number generator. The Secure Enclave holds the class keys used for file encryption, performs Face ID and Touch ID matching, and enforces the escalating delays and the ten-attempt wipe limit that make a six-digit passcode worth anything. Biometric templates never leave it; the application processor receives a yes or no, not a fingerprint.
File encryption builds on this through Data Protection classes. A file marked NSFileProtectionComplete is unreadable while the device is locked, because its key is evicted from memory; one marked NSFileProtectionNone is readable whenever the device is on. Keychain items carry the same idea, and the ThisDeviceOnly accessibility attributes keep a secret out of iCloud backups. Developers who store a session token in the wrong class hand an attacker with the device an easy win.
Every app runs inside a container directory under the app sandbox, with a profile that governs file, network, and IPC access, and capabilities granted through entitlements signed into the binary. Pointer Authentication Codes on A12 and later sign return addresses and pointers in hardware, which has demonstrably raised the cost of exploiting memory corruption bugs, and Apple extended that direction with Memory Integrity Enforcement on its 2025 silicon.
Attack surface reduction is now a design theme in its own right. BlastDoor, introduced in iOS 14, parses incoming iMessage content in a tightly sandboxed service after FORCEDENTRY (CVE-2021-30860) showed that a zero-click PDF parsing bug could deliver NSO Group’s Pegasus without any user interaction. Lockdown Mode, added in iOS 16, lets individuals who face targeted mobile spyware disable link previews, most attachment types, and just-in-time JavaScript compilation in exchange for a less convenient device.
Apps have historically reached devices only through the App Store, with review, notarisation, and a signature Apple can revoke. That model changed in the EU on 6 March 2024, when iOS 17.4 implemented the Digital Markets Act and allowed alternative app marketplaces and sideloading under a notarisation regime. Enterprise distribution was always a quieter exception, and a frequently abused one—in 2019 both Facebook and Google were found shipping data-collecting research apps to consumers using enterprise certificates intended for internal staff.
Rapid Security Responses, introduced in iOS 16.4.1, let Apple push targeted patches for actively exploited bugs without a full version update, which matters when a WebKit flaw is already in use.
Supervision through Apple Business Manager and automated device enrolment gives the strongest configuration control, and feeds into mobile device management policies for passcode strength, OS version, and managed app boundaries. The NCSC publishes device security guidance for iOS that aligns with these settings, and Cyber Essentials expects high-risk updates within 14 days and devices still inside the vendor support window. For staff who could plausibly be targeted—journalists, legal teams, senior executives—Lockdown Mode is a legitimate option to offer rather than a curiosity.
At Privia Security, our Mobile Application Security Services assess how your iOS apps use Keychain classes, entitlements, and transport protections under real attack conditions.
The platforms have converged. Both provide hardware-backed key storage, verified boot, app sandboxing, and runtime permissions. Apple controls the hardware and the update path end to end, which gives more consistent patching; Android offers more configuration control and Project Mainline updates through Play. Most real incidents trace to application mistakes or user actions, not to a difference between the two operating systems.
It stores the class keys used for file and Keychain encryption, performs Face ID and Touch ID matching, and enforces passcode retry limits. It runs its own operating system on a separate processor with encrypted memory, so a compromise of the main kernel does not directly expose the keys. Biometric templates stay inside it and are never transmitted or backed up.
People at credible risk of targeted commercial spyware: journalists, human rights workers, senior executives in contested markets, and legal or government staff handling sensitive matters. It disables most message attachments, link previews, and just-in-time JavaScript, which breaks some everyday workflows. For a typical employee the trade-off is not worth it, so offer it selectively rather than enforcing it fleet-wide.
It removes most of them. Jailbreaking disables mandatory code signing and loosens the sandbox, so apps can read each other’s containers and unsigned code can persist. Data Protection keys remain in the Secure Enclave, but anything readable while the device is unlocked becomes accessible. This is why financial apps run jailbreak checks and refuse to operate when they fail.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.