CyberKit

BFU vs AFU State

Also called Before First Unlock, After First Unlock.

Whether a phone was unlocked since boot, which governs how much data is decryptable.

What it is

A device is in Before First Unlock (BFU) state after a reboot until the user first enters their passcode, and in After First Unlock (AFU) state thereafter until it is rebooted or powered off. In BFU most user data remains encrypted and keys are not yet available, whereas in AFU many decryption keys are resident in memory.

Why it matters

The distinction is decisive in mobile acquisition: an AFU device exposes far more decrypted data and is more likely to permit a meaningful file-system extraction, so responders prioritize keeping a seized phone powered and unlocked-since-boot. Letting an AFU device reboot can collapse it to BFU and lock data away.

In practice

Because the seized phone was still in AFU state, a file-system extraction recovered decrypted app databases that a BFU device would have kept encrypted.

What to look for

  • Whether the phone was unlocked since its last restart.
  • Battery level and whether it could reboot before acquisition.
  • Auto-restart features that return the device to before first unlock.

Common mistake

Letting the phone restart. Moving from after first unlock to before first unlock locks away most data.

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