Skip to content

Read and Explain RegShot Results

Start with the case question. Find a relevant record, read both states, then explain what the comparison leaves unanswered.

Read the change type

AddedPresent in the later state

Keep the complete path, value name and data. Presence alone does not make it malicious.

DeletedMissing from the later state

Check the captured scope and errors before describing a deletion.

ModifiedThe recorded data differs

Read the old and new data together. Do not mistake two state values for two separate changes.

Investigate one relevant difference

  1. Check the report's two times, machine and user. Link it to the saved shots, build, settings and your action notes.
  2. Search the report for your exact training branch identifier. Under Values modified, read the before/after data for the setting. Keep related added values with it.
  3. Retain the full report, including unrelated changes. Copy a relevant excerpt into your note with its section and path. A short excerpt is easier to discuss, but the complete report lets someone check your selection.
  4. If you scanned a directory, check its added/modified file records separately. Retain the file and its hash if you need to establish content identity. A file difference is not proof the file was executed.

HKCU versus HKU: a report may identify your current-user setting under HKU\<SID> or HKEY_USERS\<SID>. Match that SID to the test account in your context notes. Do not treat another user's path as the same evidence.

Explain only what the record supports

Observation Supported statement What remains unproven
Mode is Manual before and Assisted after The captured data differs between these two states. The exact write time, writing process and person responsible.
A command-like string appears The string was observed at that location in the later capture. That the command ran, or would be used at that particular key.
A file is listed as added It was observed in the later scanned folder state. Download origin, execution and content identity without further evidence.
No relevant difference appears The captures show no matching difference in their recorded scope. That nothing happened between them; a change could have been reversed.

A Registry snapshot is collected over an interval; it is not an atomic image of every setting at a single instant. Keep scan timing and errors with the result. For a real incident, seek corroborating process records, events, acquired hives or retained files as the question requires.

A short handover example

Found: the training Mode value changed from Manual to Assisted between the saved shots.

Limit: the report does not identify the process that wrote it.

Next: in an incident, request available process or Registry-write telemetry for the test interval and match the host, account and path.

Attach the exact paths, data, shot hashes and times as evidence references rather than filling the three sentences with metadata. The report is a change lead, not a malware verdict.

Save a small evidence package

Capture contextMake it repeatable

Host, account/SID, time zone, build, tool source/hash, scan paths, skip settings and recorded action.

Original resultsKeep the pair and report

Both native saved shots, their hashes, full TXT/HTML report, warnings and screenshots.

Your findingMake it reviewable

A relevant excerpt, short finding, limit, next check and retained training file where applicable.

Continue to the Hands on labs. The browser route teaches the order and scope checks; the Full Lab produces native RegShot captures on your Windows VM.