Skip to content

Kernel Outlook Viewers Hands-on Labs

Interactive Lab

Your case: the invoice switch. Finance received a new payment request for invoice 4821. Use both applications to find the original invoice, read the later request and check Casey's response. Save a short note for the incident lead. Allow 15 to 20 minutes; no installation is needed.

The five tasks show you what to click and what to look for. Open Need a hint? for exact steps. Use the two SUSA viewer tabs above the application to move between PST and OST; each keeps its own loaded file and search. The next task appears automatically when you finish the current one. Task 5 includes example answers for your case note. You can explore and try again without losing points.

About the case files and recreated interface

This browser exercise uses the existing fictional SUSA-EM042 messages from Understanding Email Forensics. The case briefing defines two different sets of selected records: an earlier PST export and a later OST cache for Casey's account. Their times and scope are teaching assumptions, not findings from real acquisitions. The source cards inside the lab show those assumptions.

The grey application window recreates the menu, toolbar, Folder List, message list, Simple View, report pane and source and search dialogs shown in SUSA's screenshots and the vendor's PST walkthrough and OST guide. Find results stay in the search dialog; select a subject to open it in the main preview in this exercise. Greyed controls are outside the exercise. Blue instructions, viewer tabs and the notebook belong to SUSA.

No Kernel application runs and no real PST/OST file is parsed. Displayed times use the sample message Date converted to UTC; they do not prove delivery or reading. Complete message exports, attachment opening and property/report analysis are outside this exercise.

Browser based / investigation with both viewers

Kernel Outlook Viewers Interactive Lab

No installation

Full Lab

Use the real applications to examine one conversation in authorised PST and OST working copies. The three activities below help you prepare, investigate and explain your result. Your instructor supplies the files and independent checks; the browser exercise does not provide native mailbox evidence.

Windows VM / examine supplied mailbox files

Kernel Outlook Viewers Full Lab

Both viewers

Mailbox investigation / find, compare, explain

Two files. One question. A finding you can explain.

Finance has reported a request to change a supplier's payment details. Examine the supplied PST and OST, find messages about that request and check for a response. Give the incident lead a short note showing what you found and what still needs checking.

Start with one invoice or conversation chosen by your instructor. Aim for 45 to 60 minutes, plus setup and file loading. You can pause after any activity and return to the saved case folder.

Tick a checkpoint after saving the stated evidence. Progress is saved in this browser when storage is available. These checks cannot inspect your VM or validate your findings.

Investigation brief

Case questionWhat do the mailbox files show about the changed payment request and any response?
Your scope

Two authorised working copies, one relevant conversation and a note another analyst can check.

Real case habit: keep the source file and folder with every observation. A matching subject or display name alone does not identify a sender or prove a payment happened.

Work on copies

Keep originals separate and open verified working copies. Do not connect the recovered mailbox to a live account, send mail, follow recovered links or launch attachments. Use only functions available in your installed edition.

Activity 1: Prepare both sources

Your first winKnow which files you have and make two traceable working copies.
1. Set up the case and verify your copies
  1. Create a new case folder in writable storage. Keep separate working, screenshots and outputs folders inside it. Keep the supplied originals outside working.
  2. Write the case question, authority, source identifiers, accounts and acquisition details in the worksheet. Add the independent checks your instructor supplied.
  3. Make one working copy of each supplied file. Calculate SHA-256 for the original and its copy, then compare the pair. Repeat for the other format. Also compare each original with its supplied source hash. SHA-256 is a file fingerprint: the original and its unchanged copy should match.

Run this PowerShell command for each original and working copy, entering its actual full path. Save the path and hash in the worksheet. Do not type a placeholder filename.

Get-FileHash -Algorithm SHA256 -LiteralPath (Read-Host 'Full path of the authorised PST or OST file')

Look for: a recorded hash for each file, with each original matching its own working copy. If a pair does not match, stop and ask the instructor to check the copy. Matching hashes do not establish that the mailbox itself is complete.

2. Record the tools and time context

Open both applications without loading an original. Record each viewer's version, licence and executable path, plus the installer source. Record the VM's examination time zone and keep the supplied acquisition or export times with their source files.

Look for: two named applications in the worksheet: Kernel Outlook PST Viewer for .pst, and Kernel OST Viewer for .ost. Renaming an extension does not convert a file.

If a required source is absent or unsupported, record the gap and stop that branch. Do not open a personal mailbox to fill it. Keep your notes marked partial / not validated until the missing input is resolved.

Ready to investigatePause point: keep the worksheet and working copies. When returning, confirm that these are the same files before opening them.

Next: find the conversation in each viewer.

Start the search

Activity 2: Find and compare the conversation

Your next winSave a supported observation from each source, with enough detail to find it again.
Before you search

What could a later reply add to the request? Look for the reply if your supplied files contain it. Do not assume a sent message was delivered or read.

1. Find and record an item in the PST
  1. Open Kernel Outlook PST Viewer. Click Select File, choose Open Single File and use Browse to select the PST working copy. Check its path, choose Next, review Process Information and click Finish. Wait for the folders and message list.
  2. Choose a relevant folder in Folder List. Open Find, select the folders and enter the instructor's distinctive subject, sender or recipient term. Start with one term. Click Find Now.
  3. Select a result and read it in Simple View. Record the file identifier, folder, search settings, displayed sender, recipients, subject and date/time. Note the time zone if known. Describe the relevant body text and visible attachment name without opening the attachment.
  4. Save a screenshot showing the source and selected item. Keep the original image. If the free edition offers Save list information in HTML file, save the relevant list under outputs with a clear name such as pst-list.html. Reopen the saved list and check its rows.

Look for: an observation you can locate again using the source, folder and filters. A list export contains rows; it is not a complete message, attachment or forensic evidence package. Record the output path and scope, or the unavailable function.

Record a Message-ID or property only when the installed viewer actually exposes it. Otherwise write not exposed in this version. Keep an attachment name linked to its parent message. Extra property views and reports are optional after the core task.

2. Examine the OST and check the response
  1. Open Kernel OST Viewer and select the OST working copy with Browse. Check the path, choose Next, review the process information and click Finish. Wait for the folders and list.
  2. Search for the same case terms in the relevant folders. Read the matching request in Simple View, if present. Check Sent Items or other supplied folders for a related response. Record what you actually see, including a missing response.
  3. Save a separate OST observation in the worksheet. Record the same fields and search settings as for the PST. Keep the source context with every item rather than mixing the two files' results.
  4. Save a contextual screenshot and any supported HTML list as a separate output, such as ost-list.html. Reopen it to check its rows. Record unavailable exports rather than assuming that the free edition can save full messages or attachments.

Look for: two separate observations, or an explicit record of no matches with the filters used. The files may differ because of export scope, acquisition time or cache limits. A missing item does not by itself prove deletion.

The source wizard, search and preview steps follow the PST interface walkthrough and OST guidance. Record any differences in your installed versions.

Stuck? No results, missing fields or a file that will not open

No search results: check the source and selected folders. Remove extra filters, check spelling and widen the time range if you used one. Record the final search settings and source limits. No match in this file is not proof that a message never existed.

A field or export is unavailable: write that down and keep the visible fields and screenshots. Ask the instructor for an approved alternative if the case needs more. Do not invent a header, attachment hash or export result.

A file will not load: save the exact error, version and attempted action. Recheck the working copy's hash and vendor compatibility. Keep the original unchanged; do not rename, repair or convert it as an unrecorded step.

Two sources, two clear recordsPause point: save your worksheet and screenshots before closing either viewer. You do not need every mailbox item to answer one focused question.

Next: compare only the facts you recorded and explain what remains unknown.

Write the case note

Activity 3: Explain and hand over

Your final winGive the incident lead a short finding they can check against your saved evidence.
1. Compare the observations and check the known results
  1. Check the source accounts, export or acquisition times and scope before comparing the records. If their relationship is not established, say so. Do not describe an earlier/later sequence based only on the file extensions.
  2. Compare the fields you actually observed. A matching subject or display name alone does not prove that two items are identical or genuine. If times differ, record the field and displayed value; compare equivalent fields and offsets.
  3. Compare your results with the instructor's independent checks. Record matches, differences and missing fields. If checks were not supplied, mark the result not validated.
  4. Calculate the working files' SHA-256 hashes again and compare them with your pre-examination values. Investigate unexplained changes with the instructor. Hash any saved exports and record their paths. Keep earlier attempts and errors with a short explanation.

Look for: a comparison supported by source references, with differences and unavailable evidence stated clearly. Do not claim recovery, delivery, reading or a completed payment merely because an item appears in a viewer.

2. Write three short answers and preserve the case folder

Write what you found, what you cannot yet tell and what you would check next. Use your actual observations. This fill-in structure is a prompt, not a supplied finding:

What I found: In [source / folder / item], I observed [relevant fields and text].
The other source shows [supported comparison or gap].
What remains unknown: [specific limit and why it matters].
Next check: Request [evidence or verification] to answer [remaining question].

For this kind of case, useful next checks may include verifying a payment change with the supplier through an established contact, requesting authorised original message/header and mail-flow evidence, and checking finance records. Choose the check that addresses your actual gap.

Save the case note with your worksheet, screenshots, available outputs and integrity records. State whether both sources were examined and whether the independent checks passed. A partial or failed examination needs an explanation, not a confident conclusion.

Close both tools. Before restoring the disposable VM, copy the complete case folder to your approved retained storage and open the copy to check it. Record the closeout. Do not delete the supplied evidence or unsaved outputs while cleaning up.

Look for: a readable note and a complete saved case folder that another analyst could use to repeat the examination.

Ready for another analystCompletion means you saved the evidence for your stated outcome. These browser checks do not certify that a case finding is correct.

Finish with a note supported by your saved records.

Review the case folder

Full Lab evidence checklist

Case folder handoverSave the two checkpoints in each activity.
  • Context and integrityCase question, source and acquisition details, matching original/working hash pairs, final integrity checks, viewer versions, licences and examination time zone.
  • Examination recordsSeparate PST and OST observations, search settings, screenshots and available outputs. Keep errors and unavailable functions with their source context.
  • Finding and next checkYour comparison, validation result, short case note, limits and next evidence request. Explain any partial work.

Before a VM reset: check the retained copy of your complete case folder. A saved browser tick is not a substitute for a saved evidence file.

Retained guidance

Earlier three-decision workflow rehearsal

This previously published rehearsal is retained for continuity. Its evidence slots remain placeholders. The interactive viewer exercise above now provides fictional teaching records; neither exercise supplies native PST/OST evidence for the Full Lab.

Browser based / workflow rehearsal

Kernel Outlook Viewers Interactive Lab

Evidence fixtures unavailable
WORKFLOW
Prepare a PST and OST examinationThree decisions · existing SUSA learning controls · no simulated mailbox results
Step 1 of 3
Mission

Plan how to examine both formats for an instructor's case question. Evidence slots: [instructor-supplied PST], [instructor-supplied OST], and [case question and known checks]. These are placeholders, not downloadable files.

Rehearsal onlyNo Kernel application runs, no mailbox is loaded, and no finding is generated. “Case complete” means the three workflow decisions are complete. Continue to the Full Lab with validated evidence to perform an examination.
  1. 1Preserve
  2. 2Choose viewer
  3. 3Document
Decision 01 · PrepareWhat must be ready before examination?

The evidence slots have not been populated. Plan the source boundary before opening a viewer.

Choose a source preparation action.

Complete the preparation decision to continue.
Earlier interactive exercises for each viewer

The OST exercise and PST exercise remain at their original URLs. Their generic illustrative records are not verified product output or findings for this lab.

Retained Kernel OST Viewer Full Lab guidance

The earlier instructions for this viewer are preserved here. Supply a validated OST and expected checks before using them; their requested outputs are objectives, not supplied results. Record unsupported fields or export options as unavailable.

Self hosted

Kernel OST Viewer Full Lab

Evidence required

Hands on DFIR proof of concept

Prepare it. Examine it. Explain it.

Use Kernel OST Viewer to review a copied OST and identify one relevant message and attachment relationship, retain the evidence trail and write a bounded finding another analyst can review.

Safety boundary

Do not open recovered attachments or links on SUSA. Preserve the source store and exported message provenance.

Evidence

a copied training mail store or message set with account and acquisition context

Success evidence

a message finding supported by identifiers, headers, mailbox context, and safely handled attachments

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 review a copied OST and identify one relevant message and attachment relationship. 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 Kernel OST Viewer 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 review a copied OST and identify one relevant message and attachment relationship.
  2. Follow the Kernel OST Viewer guide and record any necessary difference in paths, labels or behaviour between versions.
  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 preservedKeep the output with the source details, command or settings, and any errors.

03

Activity 3: Review and report

  1. Work from an identified copy and confirm a message finding supported by identifiers, headers, mailbox context, and safely handled attachments.
  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.

  • Good analyst practice

    Supplementary records that improve reproducibility and review quality.

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

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.

Retained Kernel Outlook PST Viewer Full Lab guidance

The earlier instructions for this viewer are preserved here. Supply a validated PST and expected checks before using them; their requested outputs are objectives, not supplied results. Record unsupported fields or export options as unavailable.

Self hosted

Kernel Outlook PST Viewer Full Lab

Evidence required

Hands on DFIR proof of concept

Prepare it. Examine it. Explain it.

Use Kernel Outlook PST Viewer to review a copied PST and preserve one relevant message with context, retain the evidence trail and write a bounded finding another analyst can review.

Safety boundary

Do not open recovered attachments or links on SUSA. Preserve the source store and exported message provenance.

Evidence

a copied training mail store or message set with account and acquisition context

Success evidence

a message finding supported by identifiers, headers, mailbox context, and safely handled attachments

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 review a copied PST and preserve one relevant message with context. 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 Kernel Outlook PST Viewer 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 review a copied PST and preserve one relevant message with context.
  2. Follow the Kernel Outlook PST Viewer guide and record any necessary difference in paths, labels or behaviour between versions.
  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 preservedKeep the output with the source details, command or settings, and any errors.

03

Activity 3: Review and report

  1. Work from an identified copy and confirm a message finding supported by identifiers, headers, mailbox context, and safely handled attachments.
  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.

  • Good analyst practice

    Supplementary records that improve reproducibility and review quality.

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

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.