Forensic cases: custody of forensic reads
Open a case with its legal basis, add chained reads, close it and issue a signed report.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Diagnostics › More tests › Forensic cases
Important: Read and custody only: nothing here writes to the vehicle, erases crash data or extracts keys from the modules. The report attests who read what, when and with which tool; it does not attest the cause of the accident.
- Press “Open a case”. Choose the legal basis (court order, owner's consent, an insurer's mandate, documented legitimate interest or a safety investigation), write down its reference and confirm that it exists. Without a legal basis no case is opened.
- Enter the chassis number if you have it. By default only an irreversible fingerprint is kept: the number cannot be recovered. Only with a court order, the owner's consent or a safety investigation can you choose to keep it encrypted as well.
- Attach the legal basis document (PDF, PNG or JPEG up to 3 MB). It is optional, but the report warns if it is missing.
- Add the reads: choose a finished read of your organization, what was read and where you were. Each one is joined to the previous one with a fingerprint and can no longer be changed or removed.
- Press “Check the whole chain” whenever you like: it recalculates the fingerprints and checks the stored data again.
- Close the case (the PIN, Face ID or one-time code is needed) and issue the signed report. You can view it on screen, print it or download it as signed JSON or as a printable page.
- Crash data (EDR): it can be read next to the vehicle and, if the settings allow it, also remotely through the tunnel. It is noted on every read and the report flags it. The Emergency center can pause remote reading at once.
- The tool always reads through the diagnostic connector, never through the vehicle's wireless interfaces.
- Only the expert who opened the case changes it. Other people with diagnosis read permission see it, and every view, check and download is kept in the custody log.
- A read of the platform that coincides with a tunnel session is recorded as remote, even if you say you were next to the vehicle.
- A case is not erased: it is voided with a reason and kept until the chosen date. The stored chassis number can be erased whenever needed.
While the case file is open for a tool, that unit is in forensic mode and only reads. An order that writes, runs a routine or erases is refused until you close the case file or register an intervention with its reason; the intervention goes into the chain of custody and the report. More in “Forensic mode and diagnosis mode”.
Important: If any data changed after the case was closed, the chain check points it out. Only the platform can check the chassis number fingerprint; whoever receives the report cannot recalculate it.
More guides in this section
- How a remote session works
- Tunnel plan: connect a tool to the vehicle remotely
- Accept or withdraw remote access to your vehicle
- Collaborating in a session: messages, prompts and photos
- Unit PassThru mode from the app
- PassThru on Mac, Linux and iOS
- Assistance requests, appointments and work orders
- Legacy vehicle configuration and diagnostics: VAG and other makes
- Modern vehicle coding and programming
- How to diagnose each type of vehicle
- Automatic diagnosis: one tap and it explains
- Reading a vehicle and sharing the report
- CANopen diagnostics for machinery
- Vehicle details: identifying it by the VIN
- Live dashboard, service functions and battery test
- v2 procedures: beta and operational
- Control unit images: store, edit and prepare writing
- Forensic mode and diagnosis mode
- Forensic authorizations: who can use the forensic reads
- Quick inspection for authority agents
- Aftertreatment expert review (sensors, monitors and indicators)
- Compatibility notices for your tool
- CAN captures
- Pre-purchase report
- Vehicle report
- Battery health of electric and hybrid cars
- Asking Diaglana for help
- Your first read: understanding the result and what to do
- Diagnosis options: each setting and when to change it
- Workshop settings: requests, orders, network and notices
- Reading: choosing the protocol and understanding the OBD on UDS report
- What a fault code means
- Live data: dashboards, recording and export
- Attaching fault codes to a work order
- Procedures that write, program or authenticate
- ISOBUS: reading and changing an implement's NAME
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates
- AI diagnosis assistant: asking for help with a read
- Connect your AI (Claude or another) to your vehicle