Registry Explorer Hands-on Labs

Choose a lab

Choose the Interactive Lab for a short, guided browser exercise. Try the Full Lab after reviewing the tool guide and preparing an isolated, authorised environment.

How to use these labs

Start with the browser-based route to practise the workflow and evidence decisions without touching a real system. Use the Full Lab only in an isolated, authorised environment, and compare its outcome with the corresponding tool guide.

Interactive Lab

Browser-based · 10–20 min

Registry Explorer Interactive Lab

Expand labOpen in new tab

✓ No installation

Practise a guided Registry Explorer workflow in a safe browser simulation with immediate feedback.

RE

Case SUSA-014: suspicious activityOpen copied hives, map user or system context, and interpret one relevant key.

Task 1 of 4

Safe simulationThis interface models a Registry Explorer workflow. It does not run the product, access an endpoint, or change evidence.

1. 1Source
2. 2Configure
3. 3Review
4. 4Explain

Registry Explorer · Offline Registry explorerSUSA training case / read-only simulation

Task 01 · Select evidence

Choose the authorised, traceable source

The case question is bounded. Select the item that preserves scope and provenance.

Copied hives and transaction logs · WIN11-LABLive Registry opened for editingSingle exported key with no hive context

Select a source to continue.

Full Lab

Self-hosted · 45–90 min

Registry Explorer Full Lab

Evidence required

Hands-on DFIR proof of concept

Prepare it. Examine it. Explain it.

Use Registry Explorer to open copied hives, map user or system context, and interpret one relevant key, retain the evidence trail and write a bounded finding another analyst can review.

⏱ Setup and core exercise: 45–90 min◆ Guided beginner✓ Evidence required

Start the Full Lab

Safety boundary

Never edit source hives. Keep user SID, control-set, and transaction-log context attached.

Evidence

copied Windows Registry hives with their available transaction logs and profile context

Success evidence

a key or value finding linked to its hive, user or system context, parser, and limitations

Recommended first

Beginner Core Lab

Complete one bounded Registry Explorer workflow using the documented source, settings and expected result.

Optional extension

Add a comparison

After the core succeeds, repeat the same focused task with one controlled change and explain the difference without widening the authorised scope.

Full Lab scenario

You are the first analyst reviewing a bounded training case. Your task is to open copied hives, map user or system context, and interpret one relevant key. The result must be understandable to a second analyst who did not watch you perform the work.

01

Activity 1: Prepare the environment

1. Record the case question, authority and the identity of the isolated training system or evidence source.
2. Record the Registry Explorer version, provenance, system time and time zone.
3. Identify the original material, working location and separate output destination. Confirm that there is enough free space.
4. Take or verify a recoverable baseline before changing the training system.

Milestone 1Collection boundary readyThe authorised source, tool, time context, working location, destination and recovery point are recorded.

02

Activity 2: Complete the focused task

1. Restate the investigation question and select only the settings or commands required to open copied hives, map user or system context, and interpret one relevant key.
2. Follow the preserved Registry Explorer guide and record any necessary difference in paths, labels or version-specific behaviour.
3. Record start and finish times, relevant settings, completion status, warnings and errors.
4. Preserve the returned output and keep it attributable to its source and collection context.

Milestone 2Focused result preservedThe selected workflow returned reviewable output without expanding beyond the authorised case question.

03

Activity 3: Review and report

1. Work from an identified copy and confirm a key or value finding linked to its hive, user or system context, parser, and limitations.
2. Separate direct tool observations from analyst interpretation. Record missing fields, unavailable material and alternative explanations.
3. Preserve relevant integrity information, settings or commands and the evidence needed for another analyst to reproduce the result.
4. Write a bounded conclusion with observation, interpretation, confidence and limitations, then clean up the disposable environment.

Milestone 3Finding ready for reviewAnother analyst can reproduce the workflow, locate the supporting output and understand what the result does and does not establish.

Full Lab evidence checklist

This checklist applies to the self-hosted Full Lab. If you completed the Interactive Lab, retain its browser evidence summary instead.

• Core completion

  Required to demonstrate a safe, attributable workflow.

  • Case question, authority, source identity, isolated environment and time context.
  • Registry Explorer version, provenance and relevant configuration.
  • Recorded source, working location and separate output destination.
  • Focused settings or commands used to open copied hives, map user or system context, and interpret one relevant key.
  • Expected output, completion status and retained errors or warnings.
  • Observation, interpretation, confidence, limitations and alternative explanations.

• Good analyst practice

  Supplementary records that improve reproducibility and review quality.

  • Integrity information for retained output and an identified working copy.
  • Cleanup completed and disposable systems restored to their recorded baseline.

0 of 8 recorded Mark each item when you have saved the evidence.Reset

Clean up

Protect retained output and case notes, remove harmless training material, clear temporary credentials or access and restore disposable systems to their recorded baseline. Confirm that no test collection remains active.