This studio turns a device backup or a connected phone into a normalized, hashed, signed
bundle that Forge Studio ingests into the case timeline. It's a single page β no tabs.
1 Β· Set your API key
Open β Settings and paste the key (from extraction-studio/.apikey). Engines, devices,
and jobs only load once the key is set β that's why they look empty beforehand.
2 Β· Process a backup you already have
- Put the server-side path to a backup folder / disk image / triage collection.
- Leave Processor on auto-detect (or pick one). Encrypted iOS backup? add the password.
- Hit βΆ Start job. Watch it under Jobs; click a job for its log + artifact manifest.
3 Β· Acquire from a connected device (iMazing-style)
Plug in + unlock + trust an iPhone (or enable Android USB debugging). It appears under
Connected devices β click Acquire β it makes a fresh backup and parses it.
Native vs Docker (USB). Acquisition is optional β it's easy on a laptop with native
tools (incl. ours run natively). Live acquisition needs the phone plugged into the same machine
running the app (USB can't cross the network, so the remote demo can't see a phone on your laptop).
In Docker on a Linux host, add the USB overlay
(-f docker-compose.local-usb.yml); on Mac/Windows Docker can't pass USB through, so
run it natively. Processing a backup (a path) works anywhere β no USB needed.
4 Β· Engines
The Engines card lists the installed parsers (iLEAPP/ALEAPP for iOS/Android, mvt to decrypt,
imessage-exporter for chat.db, RLEAPP for carrier returns, Unified Logs). They're the installed tools β
not device-dependent β so they show as soon as the key is set.
5 Β· Ingest into the case
Each job writes a bundle (manifest.json + per-artifact SHA-256 + Ed25519 signature). In Forge β
Add data, paste the bundle's server path β it's auto-detected and ingested into the timeline.
6 Β· Smart acquisition + full-filesystem
Click π Detect & Recommend to fingerprint a connected device and auto-pick the path:
- iOS checkm8 (A9βA11 = iPhone 6sβ¦X) β palera1n full-filesystem β iLEAPP.
- iOS A12+ (XS+): no BootROM exploit β install the iOS-version-specific public jailbreak on the device
(Detect & Recommend names it: Dopamine/Fugu15 for iOS 15β16.6.1, unc0ver/Taurine for iOS 14.x), enable SSH,
then it pulls the FFS over SSH β iLEAPP. Partial/semi-untethered (one-boot β don't reboot). iOS 17+ = commercial only.
- Android MediaTek β mtkclient BROM dump Β· Qualcomm β EDL firehose Β· rooted β live /data tar β ALEAPP.
π§ Advise asks a local model for step-by-step DFU/BROM operator guidance. It is a
leads/operator aid β NOT evidence; every filed fact must trace to a deterministic parser run on the raw data.
7 Β· Windows machines β what to grab & where
Attach the drive and mount the Windows (NTFS) partition read-only, then point a processor at it.
The artifacts that matter, and where they live on the drive:
- Event logs (the big one) β
\Windows\System32\winevt\Logs\ β files ending .evtx
(Security, System, Applicationβ¦). They record logons, account changes, service installs, PowerShell, USB.
Point windows_evtx at that Logs folder β Hayabusa scans them with thousands of Sigma rules.
- Registry hives β
\Windows\System32\config\ (SYSTEM, SOFTWARE, SAM, SECURITY) and each
user's \Users\<name>\NTUSER.DAT β installed software, USB history, run-key persistence,
accounts. windows_dissect reads these from the whole drive automatically.
- Program-run evidence β
\Windows\Prefetch\*.pf, Amcache. User files / browser β
\Users\<name>\ (Downloads, Documents, AppData β Chrome/Edge history).
Don't know the layout? Just run windows_dissect on the whole disk/image β it finds the registry,
users, services and autoruns for you. (windows_evtx needs the Logs folder specifically.)