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 Isolation, snapshots and no shared credentials Sample provenance and safe acquisition Hashing and chain of custody Static-only first response and escalation Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 Disposable VM snapshots SHA-256 Isolated virtual network
Hands-on exercise Create a lab safety checklist and verify host/guest isolation without executing samples. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 malware-analysis lab diagram and safety procedure. The outcome must directly demonstrate Malware Analysis, 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 lab has a documented containment plan and no production connectivity. Evidence must be reproducible and tied to Malware Analysis.
Next: Static triage and file identification
✓ 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 File type, hashes and metadata Strings and embedded resources PE/ELF structure concepts Packers and obfuscation indicators Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 file and strings PE-bear or Detect It Easy YARA concepts
Hands-on exercise Triage a benign training sample or provided report and record metadata. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 static-triage worksheet with hashes and observable indicators. The outcome must directly demonstrate Malware Analysis, 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 No sample is executed and findings are evidence-backed. Evidence must be reproducible and tied to Malware Analysis.
Next: Executable formats and code structure
✓ 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 PE headers, sections and imports ELF segments and dynamic linking Disassembly concepts and control flow Symbols, packers and anti-analysis caveats Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 Ghidra Cutter/radare2 PEStudio
Hands-on exercise Inspect a known benign executable and map its imports and sections. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 documented executable-structure analysis. The outcome must directly demonstrate Malware Analysis, 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 Tool output is interpreted with version and sample provenance. Evidence must be reproducible and tied to Malware Analysis.
Next: Controlled dynamic observation
✓ 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 Snapshot-before/run/restore cycle Process, file, registry and network observations Time-boxed monitoring and fake services Safe handling of potentially destructive behaviour Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 Procmon Wireshark FakeNet-NG or equivalent
Hands-on exercise Use a harmless purpose-built training program to practise observation and snapshot restoration. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 behavioural observation report from a benign lab specimen. The outcome must directly demonstrate Malware Analysis, 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 test is repeatable and the host remains isolated. Evidence must be reproducible and tied to Malware Analysis.
Next: Indicators, signatures and detection logic
✓ 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 IOC quality and false-positive considerations YARA structure and test corpus Sigma and endpoint detection concepts Rule versioning and regression tests Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 Sigma Test corpus
Hands-on exercise Write a YARA rule for a benign sample set and measure false positives. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 versioned detection rule with positive/negative test cases. The outcome must directly demonstrate Malware Analysis, 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 rule is tested and does not rely on one incidental string. Evidence must be reproducible and tied to Malware Analysis.
Next: Campaign context and threat intelligence
✓ 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 TTPs vs indicators Source reliability and confidence ATT&CK mapping Threat-intel lifecycle and expiry Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 MITRE ATT&CK MISP concepts STIX/TAXII concepts
Hands-on exercise Map a published training report to behaviours and list attribution uncertainty. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 threat-intelligence note with source confidence and expiration date. The outcome must directly demonstrate Malware Analysis, 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 Attribution claims are qualified and grounded in cited evidence. Evidence must be reproducible and tied to Malware Analysis.
Next: Response integration and remediation
✓ 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 Containment recommendations and approvals Detection deployment and tuning Patch, rebuild and credential rotation Evidence retention and lessons learned Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 SIEM lab Incident playbook Case template
Hands-on exercise Prepare a response plan for a tabletop sample incident using only simulated data. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 remediation and detection package with validation steps. The outcome must directly demonstrate Malware Analysis, 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 Actions have owners, rollback and validation criteria. Evidence must be reproducible and tied to Malware Analysis.
Next: Capstone: safe analysis case
✓ 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 Intake and static triage Controlled observation where authorised Detection validation Defensible report and handover Malware Analysis specialization: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 Isolated VM lab Ghidra YARA Wireshark
Hands-on exercise Analyse a benign training sample and compare observations to a public training write-up. Context for this route: Malware analysis: use isolated snapshots; focus on static triage, safe dynamic observation, indicators and reporting; never execute samples on a production host. 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 complete case report with hashes, environment, findings and defensive recommendations. The outcome must directly demonstrate Malware Analysis, 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 No live malware is run on a production host and all conclusions are reproducible. Evidence must be reproducible and tied to Malware Analysis.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete