Staff login
Technology

Software we built in house

Most investigative firms license the same few databases and forensic suites. We wrote our own search and forensics platforms, plus the system our reports are built in, and every file we work goes through them.

Digital forensics

Bloodhound

Our forensics platform. It works through phone and computer evidence, including disk images, and logs every action taken on that evidence in a custody ledger that can't be altered without it showing.

How the custody ledger works

Each evidence item is hashed when it is acquired and checked against that hash every time it is opened. Every custody event (who accessed what, when, and why) goes into an append-only ledger, and each entry is cryptographically linked to the one before it. If a record is changed, the chain breaks and the break is visible.

If our methodology is challenged, we can produce a signed trail from acquisition through the final report.

What it reads

  • Forensic images (E01/EWF, raw dd, AFF4) and virtual disks, opened read-only
  • iOS backups, encrypted or plain, and Android filesystem and logical extractions
  • Messages, call logs, contacts, browser history, location data, media metadata, and app databases
  • Deleted records recovered from SQLite journals and unallocated space
  1. 01

    Acquire

    Register the item and hash the source before anything else touches it.

  2. 02

    Verify

    The working copy is checked against the original. If they don't match, work stops.

  3. 03

    Parse

    Records are extracted and recovered, with their location in the image kept.

  4. 04

    Correlate

    Timeline and link analysis across all items, plus hash matching.

  5. 05

    Report

    Findings and the custody ledger are signed and exported together.

Tool validation. Bloodhound runs its parsers against known reference data and produces a signed validation report. If tool reliability comes up, the documentation already exists.

Reporting

How our reports are checked

Our asset and locate reports are built in an in-house system that checks each report against our standards and won't print until the problems are fixed.

  • A commercial database hit is never marked "verified" on its own
  • Assessed value is labelled gross until the deed, liens, and payoffs are in hand
  • A "nothing found" result always lists what was searched
  • The collectibility verdict is on page one, with a ledger that won't total while an input is missing
  • When sources disagree, the report shows both and says which is better supported
  • The permissible purpose is recorded on the cover
Evidence capture

Capturing public record pages

Public record pages are captured by our own tool. Each capture is numbered, stamped with its source URL and time, and added to the report as an exhibit.

The tool rejects a capture when the page is an error or block page or is nearly empty. It also rejects one when the identifier it should show (a parcel number, for example) isn't on the page. A screenshot of "Access Denied" never ends up in the exhibit list.

Security testing

Penetration testing and exposure reviews

Authorized engagements run by Kyeson Utley, an OSCP- and CEH-certified penetration tester. Scope is agreed in writing before any testing starts.

  • Penetration testing and vulnerability assessments
  • External attack surface, cloud, and web application reviews
  • Social engineering assessments
  • Findings mapped to MITRE ATT&CK, with remediation priorities
  • OSINT exposure reviews and footprint reduction for executives
  • Hardened phones and secure communications for sensitive matters

Have a file you haven't been able to close?

Introduce your firm. We'll explain which searches we'd run and what the report would cover.