Learning paths › Security Engineer
Network Security Engineer: Detect, Triage, Contain
The defensive side of the same networks you just built: who gets on, what the policy actually permits, and how an incident gets found and contained with half the evidence you’d want.
Level: Advanced · Provider: Vendor-neutral
What you will be able to do
Work a security event from first signal to containment, and show the evidence behind every decision.
- Establish what normal traffic looks like before trying to spot abnormal.
- Control access at the port, the device and the perimeter, and prove what a policy permits.
- Build detections from real telemetry, then triage and contain a live event without breaking more than the incident did.
Skills
- Access control
- Firewall policy
- Telemetry
- Detection
- Incident response
Courses
- 00. Prerequisites: Packets, Protocols & Log Reading (9 lessons) — Networking read from the evidence side: which layer a log actually captured, what a prefix really permits, how to tell the client from the server in a connection record, and what survives encryption. It ends with the readiness exercise — real records from four sensors — which is the gate into module 1.
- 01. Security Fundamentals & SOC Workflow (15 lessons) — The vocabulary a SOC actually runs on, and the loop it runs: classify the failure, separate weakness from consequence, map the controls and their shared dependencies, then turn an alert into a question, a proportionate containment and a named owner.
- 02. Firewall & Perimeter Rule Logic (14 lessons) — Default deny, state, rule order and NAT — read as a rule base you have to audit rather than a product you have to click. Every lesson works one organisation's perimeter at a different revision in the Perimeter Rule Desk, a simulated rule table: the field names are a real firewall platform's, the decision is a teaching model of its rule order, and no firewall is running.
- 03. Network Traffic Analysis (13 lessons) — Connection, DNS, HTTP and TLS evidence: where a sensor has to sit to see anything, what a baseline is for, and how to pivot between records without inventing the link. Every lesson works the same estate in a simulated Zeek-style viewer over fixed records — the field names are Zeek's, the records are hand-written, and no capture is processed.
- 04. Intrusion Detection (8 lessons) — Where the sensor has to sit before any rule can work, what a rule header can possibly see, writing a signature that matches what you meant, and the tuning decisions — threshold, detection filter, suppress, or rewrite the rule — that decide whether anyone is still reading its alerts next month. Two labs are live: rules are parsed by idstools, the real library, and replayed against synthetic fixtures.
- 05. SIEM & Log Correlation (14 lessons) — Getting logs in, making them mean the same thing, and correlating across sources without a clock skew quietly reversing cause and effect. The module spends its first half on the pipeline, because that is where detection estates actually fail — a learner who only ever writes rules spends a career lowering thresholds. Every lesson works a simulated correlation console over authored fixtures; no agent, manager or indexer runs.
- 06. Vulnerability Management (8 lessons) — Scoping a scan and knowing what it could not see, telling a verified finding from a banner guess, scoring one as eight claims you can defend, and ranking by exposure and exploitation rather than by the decimal. It ends on remediation, exceptions, honest measurement and writing the finding somebody actually fixes. The scoring lab is live: vectors are scored by the cvss library, the real implementation.
- 07. Multi-Source Incident Response (Capstone) (10 lessons) — The whole loop over every evidence source at once, structured on NIST SP 800-61 Revision 3: validate and triage, scope and preserve, reconstruct the sequence, find what made it possible, contain proportionately, eradicate, verify recovery, and write the report that changes something. Revision 3 deliberately stopped prescribing one linear process, so the phases are taught as the usual order rather than a procedure. It ends with two full cases, unassisted and graded.
- Cisco ASA (8 lessons) — Inspect interfaces, ACLs, NAT, connections and VPN state to explain permitted and rejected ASA traffic.
- Cisco Firepower (FTD) (8 lessons) — Correlate management state, access policy, inspection, NAT and event evidence in a bounded FTD console.
- Fortinet FortiGate (8 lessons) — Trace routing, firewall policy, sessions, NAT and VPN dependencies through FortiGate operational checks.
- Splunk for Network & Security Operations (8 lessons) — Search structured network and security events, build useful pivots, and distinguish supporting evidence from unsupported conclusions.
- Snort & Suricata IDS/IPS (8 lessons) — Inspect detection rules and alerts, test intended matches and exclusions, and tune noisy signatures without hiding useful events.
- Security Scenarios & Capstone (6 lessons) — Build an evidence-led incident handoff spanning segmentation, detection, investigation and controlled recovery.
- Zscaler: Secure Web & Private Access (6 lessons) — ZIA's policy chain — URL Filtering, SSL/TLS Inspection, Cloud Firewall and DLP — and ZPA's per-application access model, each lesson opening the real Zscaler admin console into its own distinct, injected policy fault.
Other learning paths
- Cisco CCNA: Wire It, Route It, Secure It
- Visual Modules: The CCNA, Drawn And Narrated
- Juniper JNCIA-Junos: One Candidate Config At A Time
- Arista EOS: Build The Switched Campus, Port By Port
- HPE Aruba AOS-CX: Campus Switching, Routed Both Ways
- Palo Alto PAN-OS: Everything Before You Touch Prod
- Fortinet FortiSwitch: Switching Under The Firewall's Thumb
- Linux For Network Engineers: The Shell Is The Interface
- Network Automation: Never Type The Same Change Twice
- Cloud Networking: Where The Packet Actually Goes
- Juniper Professional: Past The Associate, Into The Weeds
- Cisco CCNP Enterprise: Where The WAN Actually Lives
- Cisco CCNP Security: Lock Down What’s Already Live
- Cisco CCNP Data Center: Keep The Fabric Breathing
- BGP In Practice: The Protocol The Internet Runs On
- Enterprise Scenarios: Isolate The Fault, Then Defend The Call