Process and review USB evidence¶
Examine saved Windows files
Use USB Detective to check which USB devices have been connected to a Windows computer. This guide shows you how to load saved Windows files, read the results and save your findings.
You will work with files collected from the computer you are investigating. You do not need to connect the USB device to your analysis computer.
On a small screen, scroll the tables sideways to see all the columns.
Prepare the files and case folders¶
Keep the original collected files and their hashes. A hash is a file fingerprint you can use to check whether a file has changed. Make copies to work with, and save reports in a separate folder.
Keep each computer's files together. If you collected files from the same computer more than once, keep each collection in its own folder so you know which set you are examining.
| File | Usual location on the computer being examined | What it can tell you |
|---|---|---|
| SYSTEM | Windows\System32\config\SYSTEM |
Contains Windows device records, including USB storage devices. |
| SOFTWARE | Windows\System32\config\SOFTWARE |
Provides Windows version information and other details that help the tool read the records. |
| NTUSER.DAT | Users\<account>\NTUSER.DAT |
Contains settings for a user account, including records that may link the account to a USB volume. Keep the account name and SID, the account's Windows identifier. |
| SetupAPI log | Windows\INF\setupapi.dev.log |
Records device installation activity. It does not record every time a device was connected. |
SYSTEM, SOFTWARE and NTUSER.DAT are Registry hives, files that store Windows settings. Collect them using your forensic collection tool, or follow the Full Lab to save them from a training computer. A .reg file exported from Registry Editor is a different format. Use the hive files for this guide.
Windows can lock hive files while it is running, so copying them with File Explorer may fail. Keep any Registry transaction logs collected with the hives in the same folder as their matching hive. These logs can contain recent changes. Whether USB Detective can read them depends on the edition and how the files were collected. If you use a tool to apply changes from these logs or recover hive data, record what you did.
Keep each NTUSER.DAT in a folder named after its user account, such as Users\Jamie\NTUSER.DAT. When you select a folder, USB Detective also searches its subfolders. Choose a folder containing only the files you want to examine. See the files and folders guide for the tool's input requirements.
Select Files/Folders and process¶
Use this option to examine files you have already collected.
Enter a case name, evidence number and folder for the results.
Check that the files belong to the computer, collection and user account you want to examine.
- Open USB Detective and choose Select Files/Folders. If the selection window is not showing, use the open option in your version. You can also save any earlier results, close the application and open it again.
- Enter the case name, evidence number and case folder. Choose a case folder where you want to save the results, separate from the collected files.
- Select the SYSTEM and SOFTWARE hives, the folder containing the user hives, and the SetupAPI log in the matching fields. If an optional file is missing, leave its field empty and note what is missing. Only use the button that copies a folder path to the other fields when that folder contains all the files you want to process.
- Check the time-zone setting and record it in your notes. This guide and the browser lab use UTC. If the reported incident time is in local time, convert it to UTC before comparing it with UTC results.
- Start processing. When it finishes, check the processing statistics and the log. Confirm that the files you selected were processed before reviewing the device records.
Check the processed files and any errors
Compare the file paths and processed file count with your list of collected files. Check how many devices were found and whether any files were skipped. Save the statistics, warnings and errors with your results.
If a file was skipped, check its path, format and permissions. Also check whether your USB Detective version and edition support it. Keep the failed result and use a new output folder if you try again.
The release notes describe View > Processing Statistics and, in v1.6.4, Export > Skipped Files List. If an option is unavailable in your edition, note that in your case notes.
Read the device grid¶
| Field | What it shows | Keep in mind |
|---|---|---|
| Serial/UID | An identifier you can compare with other device records. Save the full value. | Some identifiers are generated by Windows or may be shared by more than one device. Check other details too. |
| Description | The reported device make, model or description. | Two devices can have the same description. It does not tell you who owns the device. |
| First / Last Connected | The earliest and latest connection times found in the files you supplied. | These fields do not list every session or show that the device stayed connected between those times. |
| Last Disconnected | A recorded disconnection time, when one is available. | A blank field does not tell you whether the device is still connected or was ever removed. |
| Volume Name/Label / VSN | The volume label and volume serial number. Use them with the device identifier when comparing records. | Labels and volume serial numbers can change or be duplicated. |
| Drive Letter(s) | Drive letters recorded for the device. | Windows can assign the same letter, such as E:, to different devices at different times. |
| Last User | A user account linked to the device in the available records. | This does not prove that the account owner connected the device or copied a file. Note where the account information came from. |
Select the device you want to examine. Check any details, tooltips or right-click options available in your edition. If Community Edition does not show the source of a value you need, open the same working hive in Registry Explorer to check it. Save the key path, value and what its timestamp means in your notes.
Check the connection times¶
Keep these times separate:
- The time recorded for the device activity.
- The time you collected the Windows files.
- The time you processed those files in USB Detective.
Running USB Detective today can show device activity from an earlier date. The processing time is not the device's connection time.
Compare the device times with the period you are investigating, using the same time zone. Check what each timestamp records: installation, connection, removal or a change to a Registry key. The Windows version and files you supplied affect which records the tool can find.
USB Detective uses colours to show timestamp consistency, or how well the available sources agree. A high level does not mean that all activity was recorded or tell you why the device was used. The USB Detective overview explains its timestamp checks.
Example: two devices used the same drive letter
The results show device UID SUSA-USB-731 using E: at 09:12 UTC. A backup disk also used E: last week. Check the full UID, description, volume details and recorded times to work out which device fits the period you are investigating.
If you are investigating possible file copying, check other available evidence. Windows shortcuts (LNK files), recent-file lists for applications (Jump Lists), logs from the computer and records of file changes may help. You can also examine the USB device's contents if it is available and covered by the investigation. Check what each record actually shows. A reference to a file, or a record of it being opened, does not by itself prove that it was copied. Note any missing files or logs that were not enabled.
Save the results and your findings¶
Save the processing log and statistics. The vendor's quick-start guide uses File > Save Log. Use the Export or reporting options available in your edition to save the device results. Older guides show Report > Create Report, so the menu name may differ.
Open the saved output and check that it contains the records you intended to save, with the correct time zone. If your edition cannot create a report, save screenshots and write the relevant values in a table. Include where each value came from and note that you recorded it manually.
Keep the tool version and edition, collected file hashes, collection details, input paths, settings, warnings and complete results. You can copy the relevant rows into your notes, but keep the full output so another analyst can check them. Hash the saved output and reopen the files before closing USB Detective.
| Part of your finding | Example |
|---|---|
| What you found | The WS-22 files show device UID SUSA-USB-731 with a last-connected time of 09:12 UTC. |
| What it means | The connection time falls within the period being investigated. |
| What you cannot tell | These device records do not show who used the device or whether files were copied. |
| What to check next | Check available logs for file access on the same computer and volume during that time period. |
Troubleshooting¶
| Problem | What to check |
|---|---|
| The grid is empty | Check that you supplied a valid SYSTEM hive from the correct computer and collection. Review the processing statistics and errors. In a VM lab, check that the USB was connected to Windows inside the VM. Save the empty result with your notes. |
| Last User is blank | Check that you supplied the relevant user's hive. The available records may not link a user account to the device. If you cannot find that link, leave it as unknown. |
| The time does not match your notes | Check UTC versus local time, installation versus reconnection, the computer's clock and when the files were collected. Keep any difference in your notes. |
| Several rows look similar | Compare the full device identifiers, volume details and collection dates. A shared model name or drive letter is not enough to match two records. |
| An option is disabled | Check the tool version, edition and licence. Follow the Community Edition instructions or record the results manually if export is unavailable. |
Continue to the Hands on labs to practise in the browser or use USB Detective with your own training files.