Prerequisites Basic computer literacy and a willingness to document experiments.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Case intake and authorisation Chain of custody and evidence identifiers Write blockers and working copies Cryptographic hashing and notes Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools SHA-256 tools Evidence log template Read-only media concepts
Hands-on exercise Create a chain-of-custody log for a provided training image and verify hashes. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project An evidence register with acquisition metadata and integrity checks. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Every evidence item has provenance, hash and handling history. Evidence must be reproducible and tied to Memory Forensics.
Next: Acquisition and file-system artefacts
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Physical vs logical acquisition concepts Partitions, volumes and file-system metadata Deleted-file and artefact limitations Image formats and verification Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Autopsy The Sleuth Kit FTK Imager concepts
Hands-on exercise Analyse a supplied training disk image and document the acquisition context. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A structured file-system triage report using a training image. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria The report separates observable artefacts from assumptions. Evidence must be reproducible and tied to Memory Forensics.
Next: Operating-system artefacts and timelines
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Windows registry, event and shell artefacts Linux auth, system and package logs Browser and application artefacts Time zones, clock drift and timeline normalisation Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Plaso/log2timeline Autopsy Event Viewer or journalctl
Hands-on exercise Build a timeline from a curated evidence pack and annotate time uncertainty. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A timestamp-normalised case timeline with source references. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Each timeline event links to its evidence source and time basis. Evidence must be reproducible and tied to Memory Forensics.
Next: Memory acquisition and analysis
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Memory image formats and acquisition integrity Process, module and handle artefacts Network connections and injected-code indicators as evidence concepts OS profile and symbol requirements Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Volatility 3 Training memory images YARA concepts
Hands-on exercise Analyse a public training memory image and validate findings against known artefacts. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A repeatable memory-analysis notebook and evidence notes. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Commands, versions and artefact offsets are reproducible. Evidence must be reproducible and tied to Memory Forensics.
Next: Network evidence and event correlation
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn PCAP structure and stream reconstruction DNS, TLS and HTTP metadata limits DHCP, firewall and proxy logs Cross-source correlation and clock skew Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Wireshark Zeek NetworkMiner concepts
Hands-on exercise Investigate a training PCAP and correlate findings with synthetic endpoint events. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A cross-source incident timeline with confidence and limitations. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Network conclusions are supported by packet/log evidence. Evidence must be reproducible and tied to Memory Forensics.
Next: Specialist analysis and hypothesis testing
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Artifact validation and alternative explanations Hash and signature reputation caveats Memory/disk/network cross-checks Repeatability and independent review Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools YARA for controlled samples Autopsy Volatility 3
Hands-on exercise Write competing hypotheses for a training case and identify evidence that would falsify each. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A hypothesis matrix and corroboration report. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria The report distinguishes facts, interpretations and unresolved questions. Evidence must be reproducible and tied to Memory Forensics.
Next: Reporting, privacy and legal handover
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Methods and tool/version disclosure Evidence references and reproducibility Privacy minimisation and retention Limitations and defensible language Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Report template Hash manifest Case management
Hands-on exercise Prepare a report that another analyst can independently reproduce. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A final forensic report with appendices and chain-of-custody artefacts. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria Every material conclusion is traceable and uncertainty is disclosed. Evidence must be reproducible and tied to Memory Forensics.
Next: Capstone: complete DFIR investigation
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Case scope and evidence plan Acquisition, timeline and analysis Cross-source validation Recommendations and handover Memory Forensics specialization: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Tools Autopsy Volatility 3 Wireshark Git or case notebook
Hands-on exercise Complete an end-to-end case using only a published training evidence pack. Context for this route: Memory forensics: focus on acquisition integrity, memory formats, OS artefacts, Volatility workflows and evidence notes. Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Suggested project A reproducible DFIR case folder with notes, hashes, timeline and report. The outcome must directly demonstrate Memory Forensics, not merely list tools.
Learning resources Only use systems, identities, devices and data that you own or have explicit written permission to test. Keep offensive exercises inside an isolated training lab.
Completion criteria The complete investigation is auditable and uses only authorised training evidence. Evidence must be reproducible and tied to Memory Forensics.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete