We use more than one forensic tool because every tool interprets data, and the most reliable way to confirm an important finding is to see it the same way in two independent tools and then in the underlying data. Our lab uses Cellebrite UFED, Cellebrite Physical Analyzer, Magnet AXIOM, Magnet AXIOM Cyber and Magnet Verakey. Each has a different job, and they overlap enough that we can check one against another. This post explains what each tool does, why cross-validation matters, and how to read the tool names you see in someone else's report.
What each tool does
- Cellebrite UFED is an extraction tool. It connects to a phone and acquires its data, using methods that range from a logical extraction to a full file system extraction depending on the device.
- Cellebrite Physical Analyzer is an analysis tool. It decodes an extraction into messages, call logs, locations, app data and deleted records, and produces reports. It can also read extractions made with other tools.
- Magnet Verakey is a consent-based extraction tool for iPhones and Android phones. With the owner's consent and the passcode, it can perform full file system extractions of many current devices, and it records the consent as part of the process.
- Magnet AXIOM is an analysis platform that brings phone, computer and cloud evidence into one case, with views for timelines and for connecting activity across devices.
- Magnet AXIOM Cyber includes the features of Magnet AXIOM and adds remote collection from Windows and Mac computers and collection from business cloud accounts such as Microsoft 365 and Google Workspace.
Why one tool is not enough
A forensic tool does two things that are easy to confuse: it acquires data, and it interprets data. Acquisition is mostly mechanical. Interpretation is not. Messaging apps change their database layouts with updates, timestamps are stored in different formats, and deleted records can be partial. Each vendor writes its own parsers to make sense of that, and parsers occasionally disagree or miss something, especially soon after an app update.
When two independent tools decode the same extraction and agree, that is meaningful. When they disagree, it tells us exactly where to look. Either way, for any finding that matters to the case, we go to the source: the database record, file or log entry the tool read, so we can explain what the artifact is and why it means what we say it means. The tool output is the starting point, not the conclusion.
What this means for the reliability of a report
Courts and opposing experts ask how a finding was verified. A report that rests on one tool's output can be accurate, but it is harder to defend if the parsing is challenged. A report that documents cross-validation can show that the key artifacts were decoded consistently by two tools, checked against the source data, and tied to a hash-verified extraction. That does not make a finding infallible. It makes it testable, which is what reliability means in practice, and it is the standard described on our methodology page.
Cross-validation also catches the opposite problem: a tool reporting something the data does not support. Carved records, which are rebuilt from fragments of raw data, can be assigned the wrong date or the wrong conversation. Checking whether a second tool recovers the same item, and whether the source data supports it, keeps those errors out of our reports.
How to read tool names in an opposing report
When you receive the other side's report, the tool names tell you which questions to ask.
- Which tool acquired the data and which analyzed it? A report may name Cellebrite UFED for extraction and Cellebrite Physical Analyzer or Magnet AXIOM for analysis. These are different steps, and each should be identified with its version number.
- What type of extraction was it? The tool name alone does not say. Look for whether it was a logical or full file system extraction, because that sets the limit on what the report could contain.
- Was the finding checked in a second tool or against the source? If not, it is fair to ask how the examiner verified it.
- Was it a consent-based extraction? A Magnet Verakey extraction requires the passcode and records consent. That documentation should exist and is reasonable to request.
- Was data collected remotely? If a computer or cloud account was collected with Magnet AXIOM Cyber, ask what scope was collected, under what authorization, and whether it was a targeted collection or a full image.
No brand name makes a report right or wrong. These tools are widely used by careful examiners, and every one of them depends on the examiner using it correctly and documenting the work. Our checklist for reviewing an opposing phone extraction report walks through the full list of questions, and our glossary defines the terms you will see.
Our approach
Our examiner, Derick Downs, holds the Cellebrite Certified Operator (CCO) and Cellebrite Certified Physical Analyst (CCPA) certifications. We choose the extraction tool based on the device and what the matter requires, analyze in more than one platform where it matters, verify key artifacts against the source data, and record tool names, versions and hash values in every report. When we testify, we can explain not only what the tools reported but how we confirmed it.
We do this work for attorneys, businesses and individuals across the U.S. and locally in San Diego County, and we examine devices and accounts only with the owner's consent or other legal authority.
Cellebrite, UFED and Physical Analyzer are trademarks of Cellebrite, and Magnet AXIOM, Magnet AXIOM Cyber and Magnet Verakey are trademarks of Magnet Forensics; all trademarks belong to their respective owners.
Related services
More articles
- Reviewing the Other Side's Phone Extraction Report: Questions to Ask
- Validating Text Messages for Court with Digital Forensics
- Authenticating Text Messages in California: What Courts Look For
This article is general information, not legal advice. Every matter is different; contact the examiner to discuss yours.
