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 Windows/Linux/network event sources Time synchronisation and host identity Log formats and field semantics Coverage gaps and retention Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Wazuh or Splunk lab Syslog Event source catalogue
Hands-on exercise Collect a small set of host and network logs and map fields to a common schema. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 telemetry source matrix with ownership and retention. The outcome must directly demonstrate Threat Hunting, 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 source has a purpose, timestamp and coverage limitations. Evidence must be reproducible and tied to Threat Hunting.
Next: Ingestion, parsing & normalisation
✓ 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 Collectors and forwarders Parsing and field extraction Normalisation and enrichment Dropped events and pipeline health Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Wazuh agents/manager or Splunk forwarders Syslog Parser test fixtures
Hands-on exercise Send known test events and verify expected fields and ingestion counts. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 parser package and ingestion health dashboard. The outcome must directly demonstrate Threat Hunting, 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 Events are searchable and parse failures are detectable. Evidence must be reproducible and tied to Threat Hunting.
Next: Search language & investigation workflow
✓ 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 Time windows and field filters Grouping, stats and correlation Saved searches and investigation notes False positives and context gathering Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Splunk SPL or Wazuh queries Sample datasets
Hands-on exercise Investigate a curated event sequence and reconstruct the activity timeline. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 saved-search library with investigation notes. The outcome must directly demonstrate Threat Hunting, 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 Queries are reproducible and distinguish signal from noise. Evidence must be reproducible and tied to Threat Hunting.
Next: Detection engineering & alert quality
✓ 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 Detection logic and rule structure MITRE ATT&CK mapping Thresholds, suppression and deduplication Test fixtures and rule tuning Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Detection rules Sigma concepts ATT&CK knowledge base
Hands-on exercise Create a rule for a benign simulated event and tune it against noisy fixtures. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 expected positive/negative cases. The outcome must directly demonstrate Threat Hunting, 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 detection has test evidence, context and an owner. Evidence must be reproducible and tied to Threat Hunting.
Next: Dashboards, response & case handoff
✓ 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 SOC dashboards and health views Alert prioritisation and enrichment Case notes and evidence linkage Escalation and SLA Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Dashboard panels Ticketing system Incident templates
Hands-on exercise Run a simulated shift exercise and document one escalated case. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 SOC dashboard plus response handoff template. The outcome must directly demonstrate Threat Hunting, 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 An analyst can understand the alert and next action quickly. Evidence must be reproducible and tied to Threat Hunting.
Next: Scale, retention & platform security
✓ 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 Index/storage lifecycle and retention Role-based access and tenant separation High availability and resource sizing Backup, upgrade and secure configuration Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 administration Storage metrics RBAC
Hands-on exercise Test role restrictions and estimate storage using observed event volume. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 platform operations plan with retention/capacity estimates. The outcome must directly demonstrate Threat Hunting, 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 Access, retention and capacity are measurable and reviewed. Evidence must be reproducible and tied to Threat Hunting.
Next: Threat hunting & continuous improvement
✓ 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 Hypothesis-driven hunts Baseline and anomaly interpretation Detection coverage mapping Purple-team feedback and metrics Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 ATT&CK Navigator SIEM search Hunt worksheet
Hands-on exercise Conduct a bounded hunt on an approved dataset and state what evidence would disprove the hypothesis. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 hunt report and a detection improvement proposal. The outcome must directly demonstrate Threat Hunting, 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 hunt is evidence-based and records uncertainty. Evidence must be reproducible and tied to Threat Hunting.
Next: Capstone: operational SIEM service
✓ 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 Source onboarding and normalisation Tested detections and dashboards Access, retention and availability Runbooks and service metrics Threat Hunting specialization: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 Wazuh or Splunk lab Test event corpus Documentation
Hands-on exercise Demonstrate event ingestion, a detection, analyst triage and a documented handoff. Context for this route: Track-specific focus: Threat Hunting. Use the tools and standards named in this path; avoid treating this route as a generic overview of Cybersecurity. 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 SIEM service design with parsers, detection tests and SOC runbooks. The outcome must directly demonstrate Threat Hunting, 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 A reviewer can replay the scenario and inspect evidence end to end. Evidence must be reproducible and tied to Threat Hunting.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete