Field Notes

entity

Samsung Knox

StatusStableReviewdue UpdatedStands on8 sourcesSupportsnotes

Samsung Knox is Samsung’s mobile security platform, spanning the TrustZone TEE, the Knox Vault secure subsystem, verified boot with a warranty fuse, enterprise features such as DualDAR, and consumer features such as Auto Blocker and Message Guard. Knox Vault, its hardware core, is a dedicated secure processor with its own SRAM, ROM, and physically separate secure flash, shipping since the Galaxy S21 (2021) — the closest Android analogue to the Titan M secure element and the Apple Secure Enclave.1

Knox Vault architecture and certifications

Knox Vault moves sensitive operations off the application processor entirely: the Knox Vault Processor runs its own secure boot chain, communicates with the SoC over an encrypted, authenticated I2C bus, and stores critical data (PINs, biometric templates, cryptographic keys) in Knox Vault Storage, a separate non-volatile memory rather than the main UFS storage. Hardware sensors monitor for physical tampering. The components are Common Criteria evaluated against BSI PP0084 at EAL4+ or higher, and Samsung’s broader certification portfolio — NIAP MDFPP, NSA CSfC listings, ANSSI CSPN — is the deepest government-deployment credential set of any consumer Android vendor, which is why Knox historically dominates enterprise and defense Android procurement.2

The wider platform adds layers Pixels lack and layers they share: Trusted Boot with the one-time Knox warranty fuse (an irreversible tamper flag that revokes TrustZone device keys and permanently disables Knox features), real-time kernel protection (RKP) on flagships, DualDAR double-encryption for enterprise work profiles, and, on the consumer side, Auto Blocker (blocks sideloading, USB-port commands, and zero-click image vectors via Message Guard).

Samsung Weaver and the offline brute-force floor

Samsung flagships implement Weaver — the same throttled-secret HAL the Titan M secure element uses — running on the Knox Vault Processor, with slot secrets stored encrypted in Knox Vault Storage and a binary exponential back-off enforced by a “non-bypassable secure timer.”3 Credential-encrypted storage is standard Android FBE with the same cheap scrypt pre-stretch.

This means the structural analysis in Offline brute-force resistance of phone disk encryption applies to Samsung nearly unchanged: the throttle secret is stored and released on correct-key presentation, so a Knox Vault compromise opens the same offline regime a Titan M compromise would — with entropy and a weak KDF as the backstop. What Samsung does not have is an equivalent of Apple’s fused-UID design or of GrapheneOS’s userspace compensations (auto-reboot, profile end-session, duress credential).

Why Samsung is extractable when stock Pixel is not

Cellebrite’s exact exploit paths are trade secrets, so the precise reason S24-class devices fall in BFU is not public. The documented components of an answer:

  • Samsung’s TEE is demonstrably patchable once the boot chain breaks. Quarkslab’s end-to-end proof of concept on Samsung devices (A22, MediaTek-based) exploited the boot ROM via the vendor download mode, patched TEEGRIS’s Gatekeeper to accept any credential, leaked the Keymaster intermediate, and brute-forced the credential offline through the scrypt-and-AES-GCM oracle that Android’s design necessarily exposes.4 Samsung runs TEEGRIS across Exynos and MediaTek SoCs, so one Trusted-OS codebase covers most of Samsung’s lineup.
  • Samsung exposes more pre-OS attack surface. Its download mode and the Qualcomm EDL mode on Snapdragon variants give forensic tools boot-level footholds that Pixel’s more locked-down fastboot chain denies.
  • Patch propagation is slower. Samsung lags AOSP on device-specific components, so boot-chain and TEE vulnerabilities remain exploitable longer.
  • Cellebrite invests where the volume is. Samsung flagships dominate law-enforcement seizure pools; Pixel’s smaller share and GrapheneOS’s tiny one get less exploit-development attention.

Whether Cellebrite’s S24 BFU capability works by patching the TEE around Knox Vault’s Weaver, or by an actual Knox Vault Processor exploit, is the piece that is not publicly known. The first is sufficient on paper only if Samsung’s credential path still has a TEE-level oracle that bypasses the Knox Vault throttle; the second would be the first documented secure-element compromise in a commercial tool. GrapheneOS’s reading of the matrices is that brute-force capability “does not bypass hardware-bound key derivation, so a brute force is still rate limited but no longer has an extremely small number of attempts” — consistent with the TEE-oracle interpretation.5

The forensic record: worse than the architecture suggests

The architecture ranks Knox Vault with Titan M2; the leaked forensic matrices do not. Cellebrite’s Inseyets 10.0 update (January 2024) added BFU, AFU, and full-file-system support for the Galaxy S24 series on both Qualcomm and Exynos variants, and the February 2025 matrices list Samsung flagships from the S7 through the S24 as BFU-extractable.6 7 Stock Pixels from the Pixel 6 onward resist BFU extraction. So despite comparable secure-element hardware, current Samsung flagships are demonstrably easier to extract when locked than current stock Pixels — a reminder that the chip is one layer, and that Samsung’s larger attack surface (vendor skin, carrier components, slower propagation of mitigations) dominates the practical outcome. Osservatorio Nessuno’s analysis also notes that a TEE exploit against these devices yields offline brute force, making “any numerical PIN shorter than 10 digits useless” — exactly the weak-floor scenario the offline-derivation note models.

Updates, MTE, and the GrapheneOS question

Samsung’s update commitment now matches Google’s: seven years of OS and security updates from the Galaxy S24 onward, with monthly cadence on flagships (quarterly on mid-range).8 Memory tagging is the notable hardware gap: no shipping Samsung device exposes MTE, but One UI 9 (Android 17) strings show a user-facing MTE toggle in development inside the Auto Blocker app, contingent on ARMv9 hardware.9 GrapheneOS developers have identified Qualcomm’s MTE support as the key blocker for non-Pixel flagships meeting their requirements — the same requirement list the Motorola partnership devices must satisfy.

Samsung hardware cannot run GrapheneOS in practice: North American models ship with non-unlockable bootloaders, and unlocking any Samsung burns the Knox warranty fuse irreversibly. The platform is therefore relevant to the vault as the comparison case that isolates software from hardware — proof that secure-element-class hardware alone does not deliver Pixel-class forensic resistance — and as the enterprise-certified alternative when government or defense procurement requirements outweigh extraction resistance.

  1. Knox Vault fundamentals, Samsung Knox documentation. ↩

  2. Knox security certifications and guidance, Samsung Knox. ↩

  3. Knox Mobile Security White Paper, Samsung, 2025. ↩

  4. Android Data Encryption in depth, Quarkslab, 2023. ↩

  5. GrapheneOS on the Cellebrite Premium July 2024 documentation, GrapheneOS, July 2024. ↩

  6. Now Available: Inseyets 10.0, Cellebrite, January 2024. ↩

  7. A deep dive into Cellebrite: Android support as of February 2025, Osservatorio Nessuno, March 2025. ↩

  8. Samsung Mobile Security, Samsung security updates portal. ↩

  9. Samsung may borrow Google’s memory safety trick for One UI 9, Android Authority, April 2026. ↩

Built on 8 sources (8 external).

Working out connections…