Who this roadmap suits
This path suits learners who already have some grounding in networking or systems administration and want to specialize in defense: monitoring, detection logic, hardening, and response, rather than moving toward penetration testing.
Prerequisite skills
- Comfort with Windows and Linux administration, including user permissions, services, and basic scripting.
- Networking fundamentals: TCP/IP, common ports and protocols, and how traffic is normally routed and filtered.
- Familiarity with logs from at least one platform (operating system, firewall, or web server).
Staged learning path
1. Foundations
Solidify networking and OS administration, and review the CIA triad and defense-in-depth concepts if you have not already.
2. Core skills
- Detection engineering basics: how detection rules are written and tuned to reduce false positives.
- Threat modeling: identifying what you are protecting and from whom, at a conceptual level.
- System hardening: secure configuration baselines, patch management, and least-privilege access.
- Incident response fundamentals: the identification-containment-eradication-recovery-lessons-learned cycle.
3. Tools
- SIEM and log aggregation platforms for centralized visibility.
- Endpoint detection and response (EDR) concepts -- what they monitor on a host and how alerts are generated.
- Network monitoring tools for traffic visibility (see our Network Monitoring project idea in Projects & Labs).
- Vulnerability scanners used defensively to find and prioritize weaknesses in your own environment.
4. Practice
Set up a small lab following our Cybersecurity Home Lab Guide, intentionally misconfigure a machine, then practice hardening it and documenting each change. This builds the habit of thinking like a defender rather than only reacting to alerts.
5. Portfolio
Write up a short 'before and after' hardening exercise, and one incident response tabletop exercise you ran against a simulated scenario.
6. Interview readiness
You should be able to describe a detection rule you would write for a specific behavior, and explain trade-offs between sensitivity and alert fatigue.
Key concepts to master
- Defense in depth and layered controls.
- The difference between prevention, detection, and response controls.
- MITRE ATT&CK as a shared vocabulary for describing adversary behavior (used defensively to map detections, not to plan attacks).
- Log correlation across multiple sources to build a fuller picture of an event.
Hands-on labs to attempt
- Harden a test virtual machine against a security baseline and document each change.
- Build simple detection logic for a suspicious but simulated behavior in a lab SIEM.
- Run a tabletop incident response exercise using a written scenario.
- Try our Threat Hunting Lab and Incident Response Simulation project ideas in Projects & Labs.
Certifications worth considering
General security certifications and more specialized blue-team or defensive-focused certificates are commonly referenced for this path. As with any certification, check the current syllabus against your goals and treat it as a study aid, not a promise of a role.
How to know you are ready to apply
- You can explain a hardening change you made and why it reduces risk.
- You have run at least one simulated incident response exercise, even informally.
- You understand how detection rules are tuned to balance coverage and noise.
Stay defensive
Everything in this roadmap is about protecting systems, not attacking them. If a resource teaches offensive techniques, make sure you also understand the defensive lens: what would this look like in your logs, and how would you detect it?