CyberKit

iOS Backup Artifacts

Also called MobileSync, iTunes/Finder backup, Manifest.db.

The structured backup an iPhone produces, a rich offline source of app and system data.

What it is

When synced to a computer, an iPhone writes a backup under the MobileSync/Backup directory in which files are stored under hashed names indexed by a Manifest.db SQLite catalog, with Info.plist and Status.plist describing the device and backup. Encrypted backups (recommended by Apple) protect the contents with a user password but also include extra data like saved credentials.

Where it lives

~/Library/Application Support/MobileSync/Backup/ (macOS); %USERPROFILE%\Apple\MobileSync\Backup\ (Windows, Apple Devices app) or %AppData%\Apple Computer\MobileSync\Backup\ (classic iTunes)

Why it matters

Backups are a practical, consent-friendly way to obtain message databases, call history, app data, and system plists without a deep device acquisition. Mapping the hashed filenames back to real paths via Manifest.db is the key skill, and an encrypted backup's password materially changes what is recoverable.

In practice

Resolving Manifest.db pointed an examiner to the SMS database inside an iPhone backup, recovering the full text thread under review.

What to look for

  • Manifest.db listing every file in the backup.
  • Encrypted backups, which include more data such as keychain items.
  • Messages, call history and app databases.

Common mistake

Skipping encryption. An encrypted backup holds more evidence than an unencrypted one.

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