Choosing a mobile forensics tool: a neutral framework
A neutral framework for choosing mobile forensic tools: acquisition vs analysis, commercial vs open source, validation, budgeting and legal authority.
Updated
In short
SWGDE 18-F-003-2.0 (version 2.0, 2025-08-21) says tool capabilities may vary with device manufacturer, model and operating system, and SWGDE 18-Q-001-2.1 states that "no mobile forensic tools are capable of acquiring all data from all mobile phones". SWGDE 18-Q-001-2.1 (2024-03-07) bases its testing baseline on a tool's function rather than its origin, whether commercial, open-source or custom-developed, and for mobile device imagers recommends testing before a tool is placed in service, after repair of hardware-based tools and after major updates. SWGDE 18-F-003-2.0 says a single tool may not extract or present all data and that manual review or a second forensic tool can corroborate the results or provide additional data. 404 Media notes that vendors "typically do not release details" of what models their tools can penetrate, and in the US, Riley v. California (2014) held that police generally must get a warrant before searching a cell phone seized incident to arrest.
This guide does not rank products. It sets out questions to answer before spending money or relying on a result, and points to the standards that apply. For product detail, see the individual tool pages.
1. Separate acquisition from analysis
Two different jobs are often sold together. Acquisition gets data off a device: access or unlocking, then extraction at some level (acquisition types). Analysis decodes, parses, searches and reports on what was extracted. This site classifies tools as suites (both jobs), acquisition tools, unlocking tools, analysis tools and parsers, among other categories. Many labs combine a suite with a separate access tool, or with open-source parsers such as the LEAPP family.
Start from your cases, not the tool list:
- Which devices, operating-system versions and lock states do you meet? Lock state alone can decide the outcome (BFU vs AFU).
- Do you need extraction from locked devices, or mainly from unlocked or consenting ones?
- Is the bottleneck getting data off, or understanding it?
SWGDE 18-F-003-2.0 (version 2.0, 2025-08-21) says tool capabilities may vary with device manufacturer, model, operating system, software and/or network provider, so an examiner may need tools from several vendors and acquisitions at several levels to maximise the volume of recovered data. SWGDE 18-Q-001 puts it more bluntly: "no mobile forensic tools are capable of acquiring all data from all mobile phones".
2. Commercial versus open source
| Commercial | Open source | |
|---|---|---|
| Device and app coverage | Vendor-maintained, updated per release | Community-maintained; coverage depends on contributors |
| Documentation of capability | Often customer-only. 404 Media notes vendors "typically do not release details" of what models their tools can penetrate, preferring vague marketing | Source and issue trackers are public, so behaviour can be inspected |
| Support and training | Vendor support and courses | Community support |
| Cost | Licences, subscriptions, hardware | No licence fee, but staff time for installing, testing and keeping current |
| Validation burden | SWGDE 18-Q-001-2.1 recommends testing before a tool is placed in service; results may be adopted from another competent organization | SWGDE bases its baseline on the tool's function, not its origin, so the recommendation does not depend on whether the source is open |
The rows on device and app coverage, support and training, and cost are general observations, not drawn from the cited sources.
Neither column is a quality ranking. SWGDE 18-Q-001-2.1 names commercial, open-source and custom-developed tools as the major sources of forensic tools and says it bases its testing baseline recommendations on the function of the tool, not on the tool origin. Watch the licence terms of tools whose source is published: the MVT licence, for example (this site lists it as source-available), adds a clause restricting use to consensual analysis, and its authors state it is not "free software" by the FSF definition (MVT licence). Open-source parsers can also fail quietly. A preprint (not peer reviewed) found an ALEAPP parser produced incomplete output after controlled schema changes with no visible warning (Bulla); the lesson applies to any parser.
Be cautious with capability claims. A vendor matrix is a dated statement about specific models and builds, and leaked ones are secondary evidence. See GrapheneOS and forensic tools for how to read them.
3. Validation and dual-tool verification
What the standards say. The NIST CFTT project aims to establish a methodology for testing forensic tools through specifications, test procedures, criteria, test sets and hardware, with results meant to inform toolmakers and help users choose and use tools. Its mobile test plan (version 2.0, dated 1 February 2016 on its cover) defines assertions covering connectivity, data acquisition and interpretation, hashing, case-file protection and authentication-mechanism bypass.
SWGDE 18-Q-001-2.1 (2024-03-07) gives baseline testing recommendations. For mobile imaging tools it says to test with a known dataset of representative content, to supplement that with empirical testing, and not to rely on hashing alone because mobile storage can change underneath the examiner. It recommends testing before a tool enters service, after hardware repair, and after major updates, notes that minor updates need not trigger a full re-test, and says testing is not necessarily pass or fail: some faults limit how a tool is used rather than whether. The document says testing may be performed in house or results may be adopted from another competent organization.
Dual-tool verification. SWGDE 18-F-003-2.0 says a single tool may not extract or present all data and that manual review or a second forensic tool can corroborate the results or provide additional data. It also warns that hash values from repeated extractions of the same phone may not match, because mobile storage is dynamic. Two tools only give independent confirmation if they work differently (this guide's inference). Two parsers that make the same assumption about an app's database can share the same blind spot, so spot-check key artefacts in the raw data.
ISO/IEC 17025. In the UK, the Forensic Science Regulator's statutory code states that where it requires accreditation, UKAS assesses forensic units against ISO/IEC 17025:2017, ISO/IEC 17020:2012 or ISO 15189:2022. Check what your jurisdiction and customers require.
4. Budgeting without invented numbers
This site records a price only when the vendor publishes one, and otherwise writes "quote-based". Published figures are snapshots; for example, Elcomsoft's product page listed a "full version" price of $2,199 when checked on 2026-10-29, without the text retrieved making clear what updates it includes. Rather than comparing sticker prices, list the recurring and indirect costs:
- Licence renewals and updates. SWGDE 18-Q-001 notes that mobile device tools change frequently to add support for additional devices, add new functionality and fix bugs.
- Hardware. Some tools are hardware units. SWGDE 18-Q-001 says hardware needs testing on each unit, and SWGDE 18-F-003-2.0 says that data cables can be unique to a particular device and forensic tool.
- Training. NIST SP 800-101r1 ties higher acquisition levels to more advanced training. Vendor courses exist; for example Magnet Forensics lists a Graykey examinations course.
- Validation time. Test data, test devices and re-testing after major updates.
- Storage and workstations for large extractions.
- Open-source labour. Free licences still cost time to deploy, test and keep current.
5. Legal authority
A tool does not create authority to examine a device. Establish it first, in writing, and ask counsel if unsure; this section is general information, not legal advice.
- Law enforcement (US). In Riley v. California (decided 2014-06-25), the Supreme Court held that police generally must get a warrant before searching a cell phone seized incident to arrest. Other questions, such as border searches or compelled unlocking, are outside that holding and this guide.
- Cloud data. The superseded SWGDE 18-F-003 v1.2 (2020-09-17) warned that cloud acquisitions present unique legal considerations because the search may be deemed to occur outside the issuing jurisdiction; that sentence is not in version 2.0 (2025-08-21), which still refers readers to SWGDE's separate guidance on acquisition from cloud service providers.
- Consent-based work. Some tools are built around consent: the MVT licence permits use only with the explicit consent of the person whose data is being extracted or analysed.
- Corporate and private work. Rely on documented consent, employment policy and local law, and record your authority in the case file.
- Other jurisdictions have their own rules on search, interception, data protection and admissibility.
A short checklist
- Define the devices, OS versions and lock states you actually face.
- Decide whether you need acquisition, analysis or both.
- Confirm legal authority and the tool's licence terms.
- Ask vendors for dated, written support for your exact models and builds.
- Test with known data before casework, and again after major updates.
- Plan a second method for key findings.
- Budget for updates, training and validation, not only purchase.
Sources
- SWGDE 18-Q-001-2.1, Minimum Requirements for Testing Tools Used in Digital and Multimedia Forensics (2024-03-07)
- SWGDE 18-F-003-2.0, Best Practices for Mobile Device Evidence Collection & Preservation Handling and Acquisition (Version 2.0, 2025-08-21)
- SWGDE 18-F-003, Best Practices for Mobile Device Evidence Collection & Preservation, Handling, and Acquisition (Version 1.2, 2020-09-17; superseded by 2.0)
- NIST, Computer Forensics Tool Testing Program (CFTT)
- NIST CFTT, Mobile Device Tool Test Assertions and Test Plan, Version 2.0 (2016-02-01)
- NIST SP 800-101 Rev. 1, Guidelines on Mobile Device Forensics (May 2014)
- UK Forensic Science Regulator, Forensic science activities: statutory code of practice, version 2
- Riley v. California, No. 13-132 (U.S. Supreme Court, decided 2014-06-25)
- 404 Media, Leaked Docs Show What Phones Cellebrite Can (and Can't) Unlock (2024-07-17)
- MVT documentation, MVT License
- Bulla, Failure Transparency in Android Forensic Parsing (preprint, not peer reviewed)
- Elcomsoft iOS Forensic Toolkit product page (vendor)
- Magnet Forensics training, GK200 Graykey Examinations (course description, vendor)