Specialist · DFIR

For IR Practitioners, DFIR Examiners, and Detection Engineers Who Need Artifact-Level Forensic Depth Beyond Tool Output

Aligned to NIST SP 800-86ISO/IEC 27037MITRE ATT&CKSigma rules

Windows Forensics

Analyze Windows artifacts at the level that survives cross-examination.

Perform deep forensic analysis of Windows systems — MFT parsing, USN Journal analysis, Prefetch and Amcache interpretation, ShellBags and LNK file examination, registry forensics, event log deep analysis, volume shadow copy recovery, and timeline construction. Every artifact is taught at the structural level: understand the raw data, validate tool output, detect anti-forensics, and produce findings you can defend in court.

What you'll deploy
2 full capstone investigations with court-ready forensic reports
Complete Windows artifact analysis workflow across MFT, USN, prefetch, and registry
Timeline reconstruction methodology using multiple artifact sources
Evidence correlation techniques for attribution and scoping
Forensic report writing templates that survive legal scrutiny
Artifact-level analysis skills you can apply to any Windows investigation
FORENSIC ARTIFACT ANALYSIS — THE RAW-FIRST METHOD STEP 1 Identify — What creates this artifact and what does its presence prove? STEP 2 Extract — Raw collection preserving evidence integrity STEP 3 Parse — Binary structure analysis before tool output STEP 4 Correlate — Multi-artifact cross-validation for confidence STEP 5 Conclude — Court-defensible findings with confidence assessment ARTIFACT CATEGORIES FILESYSTEM MFT · USN · LogFile EXECUTION Prefetch · Amcache · Shim USER ACTIVITY ShellBags · LNK · Jumps SYSTEM EventLog · Registry · SRUM 15 modules · 225 subsections · 3 investigation scenarios — Northgate Engineering

The Raw-First Method — every artifact examined at the binary level before tool output, correlated across sources, tested for anti-forensic manipulation.

View Pricing Download Lab Pack Take End of Course Exam → 40 CPE Credits

What you'll be able to do

Parse MFT, USN Journal, Prefetch, Amcache, ShellBags, and registry at the structural level
Detect timestomping and anti-forensic techniques using multi-artifact correlation
Construct super timelines from multiple forensic artifact sources
Validate and challenge tool output using raw artifact analysis
Produce forensic findings that survive cross-examination
Specialist tier | 15 modules across 4 phases | 36–40 hours at your own pace | 40 CPE credits | 2 free modules — no account needed | All tools free | Updated May 2026
Course Agenda View all 15 modules

Who this course is for

“I run KAPE and EZ Tools but I don't understand what the output means at the byte level.” You parse MFT records and Prefetch files with tools, but you can't explain the $SI vs $FN timestamp difference under cross-examination. This course teaches the binary structures behind every artifact so you know what you're looking at, not just what the tool says.

“I can investigate in the cloud but I'm lost when it reaches the endpoint.” IR practitioners who handle sign-in logs and audit trails but struggle when the investigation pivots to a disk image. MFT, USN Journal, registry hives, event logs — you need the artifact analysis skills that complete the cross-domain investigation.

“The attacker timestomped the evidence and I couldn't prove it.” Anti-forensic detection is built into every artifact module. $SI/$FN timestamp mismatches, EventRecordId gaps, selective Prefetch deletion residue — you learn to detect the manipulation that tools alone miss.

“I need my forensic findings to hold up in legal proceedings.” Court-defensible methodology from evidence handling through examination report writing. Chain of custody, confidence assessment, multi-artifact correlation — findings that survive cross-examination because you can explain how you reached them.

“I want to specialize in DFIR but I can't justify expensive forensic tool licenses.” Every tool in this course is free. KAPE, the complete EZ Tools suite (MFTECmd, PECmd, AmcacheParser, SBECmd, EvtxECmd), Arsenal Image Mounter, Timeline Explorer. Professional-depth forensics without vendor lock-in.

“I need to build a timeline across multiple artifact sources, not just read one log.” The capstone investigations require you to correlate MFT entries, Prefetch records, registry timestamps, USN Journal events, and event logs into a single coherent timeline. This is how real investigations reconstruct what happened.

Whatever your background — if the subject interests you and you're willing to put in the work, this course is for you.

Before and after this course

Before

You run MFTECmd and get output. You don't know what the $SI created timestamp means vs the $FN created timestamp — or why the difference matters for proving timestomping.

Your investigation stops at “the file was on disk.” You can't prove when it was executed, by which user, from which parent process, or what it did after execution.

You write investigation reports that document what you found but can't defend how you reached the conclusion under hostile questioning.

Each artifact source tells you a fragment. You can't combine MFT, Prefetch, ShellBags, and event logs into a single timeline that proves the full attack narrative.

After

You read MFT records at the binary level. $SI/$FN mismatches jump out as timestomping indicators. You validate tool output against the raw data and catch what the parser missed.

Prefetch proves execution time and frequency. Amcache proves first execution. ShellBags prove folder access. Event 4688 proves the parent process. You chain five artifact sources to prove the complete sequence.

Your examination reports follow the court-defensible format: evidence collected, analysis performed, findings with confidence assessment. You can explain every step from collection to conclusion.

Your super timeline integrates MFT, USN, Prefetch, ShellBags, registry, event logs, and SRUM into one chronological narrative. The insider investigation and ransomware capstone each require this.

How the course works

The Raw-First Method — every artifact examined at the binary level before tool output, correlated across sources, tested for anti-forensic manipulation:

1
Identify

What creates this artifact? What does its presence prove? What does its absence mean?

2
Extract

Raw collection preserving evidence integrity. Chain of custody from the first byte.

3
Parse

Binary structure analysis before tool output. You understand what the parser reads.

4
Correlate

Multi-artifact cross-validation. One source suggests; two sources confirm; three sources prove.

5
Conclude

Court-defensible findings with confidence assessment. You can explain your methodology under oath.

What the content looks like

This is a real analysis from Module 2. Before you run MFTECmd, you understand what the MFT record looks like in raw hex — so you know exactly what the parser is reading and can detect when the data has been manipulated.

CLI Output — From Module 2: MFT Record Analysis
MFT Entry: 48127 | Sequence: 3 | Flags: IN_USE | FILE
$STANDARD_INFORMATION (0x10):
  Created:    2026-01-15 09:23:47.123  <-- attacker's timestamp
  Modified:   2026-01-15 09:23:47.123  <-- all four identical = timestomped
  MFT Mod:    2026-01-15 09:23:47.123
  Accessed:   2026-01-15 09:23:47.123
$FILE_NAME (0x30):
  Created:    2026-03-22 14:08:31.847  <-- NTFS kernel timestamp
  Modified:   2026-03-22 14:08:31.847  <-- actual file creation date
  FN Flags:   ARCHIVE
$DATA (0x80):
  Size: 287,744 bytes | Resident: No | Runs: 1

The $SI timestamps say January. The $FN timestamps say March. That 66-day gap is the smoking gun — the attacker timestomped $STANDARD_INFORMATION to match a legitimate file, but $FILE_NAME timestamps are set by the NTFS kernel and can't be modified by user-space tools. Every forensic artifact module teaches this level of structural understanding.

Lab Pack — Windows Forensic Analysis

Two investigation scenarios: Insider exfiltration (INC-NE-2026-0915) — 6-week data theft by departing engineer, three USB drives, OneDrive personal account, document renaming. Ransomware (INC-NE-2026-1022) — 72-hour attack across three hosts, phishing to encryption, 10 persistence mechanisms.

Included: 2 PowerShell artifact generators, 10 HTML walkthroughs, 30+ exercises, 10 verification scripts, 4 court-defensible report templates. All tools free (KAPE, EZ Tools suite, Arsenal Image Mounter, Timeline Explorer).

Windows Forensic Analysis Lab Pack v1.0
2 scenarios · 10 walkthroughs · 30+ exercises · 4 report templates
Download Lab Pack (.zip)

Usage rights and disclaimer

Course materials: Licensed for individual professional development. You may not redistribute course content or share account credentials.

Forensic evidence: All lab evidence files are fictional constructs. Validate forensic procedures against your jurisdiction's legal requirements before use in legal proceedings.

Fictional environment: All scenarios use Northgate Engineering. Any resemblance to real organizations is coincidental.

Version and changelog

Current version: 1.0  |  Last updated: 2026

2026 — v1.0: Course launch. 15 modules across 4 phases. Complete Windows forensic artifact analysis from MFT binary structures through court-defensible investigation methodology.

This course is actively maintained.

COURSE ASSESSMENT

End of Course Exam

Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.

40minutes
3phases
100points
1scenario
Take End of Course Exam

Requires 80% course completion. One random scenario per attempt. Certificate issued on pass.