CyberKit

Mobile Keystore / Secure Enclave

Also called Android Keystore, Secure Enclave, hardware-backed keys, TEE.

Hardware-isolated subsystems that store and use cryptographic keys off the main CPU.

What it is

Mobile platforms protect cryptographic material in dedicated security hardware: Apple's Secure Enclave is an isolated coprocessor handling keys and biometrics, while Android's Keystore can be backed by a Trusted Execution Environment or StrongBox secure element. Keys generated there are designed to be used but never exported in plaintext.

Why it matters

The keys that protect device encryption and app secrets live in hardware and are bound to user authentication, which is why modern phones resist offline attack and why lock state matters so much. For examiners, hardware-backed keys define the boundary of what is feasibly recoverable without the user's credential.

In practice

Because the disk-encryption key was sealed in the Secure Enclave and tied to the passcode, the data stayed inaccessible without the user unlocking the device.

What to look for

  • Keys marked hardware backed or bound to the enclave.
  • Apps storing secrets outside the keystore.
  • Biometric binding settings on stored keys.

Common mistake

Assuming every key uses it. Apps choose, and some store secrets in plain files.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Mobile Verification Toolkit Open source

    Checks iOS and Android backups and file systems for signs of known spyware.

  • iLEAPP Open source

    Parses iOS extractions into readable reports of apps, messages and system logs.

Read next

Sources