Learning paths › Security Engineer › 03. Network Traffic Analysis
03. Network Traffic Analysis
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.
Lessons
- Sensor Placement: Why Half Your Traffic Is Not In These Logs
- Connection Log Literacy: Reading conn_state Before Anything Else
- DNS Evidence: What A Query Proves, And What NXDOMAIN Is Telling You
- HTTP Evidence: Method, Host, URI, Status — And The User Agent
- TLS Metadata: The Columns That Survive Encryption, And The One That Does Not
- Evidence Pivots: Carrying A uid Between Four Logs
- Baselines: Counting Before Looking, So Normal Has A Shape
- Scanning: Reading A Sweep From Its Failures
- Periodic Traffic: Why Regularity Is A Question, Not A Verdict
- Possible Data Transfer: What 18MB Outbound Does And Does Not Establish
- Lab 1: Join Four Logs Without Inventing A Single Field
- Lab 2: Separate The Approved Heartbeat From The Unexplained One
- Case: More Outbound Data After Unusual File Access
More in Security Engineer
- 00. Prerequisites: Packets, Protocols & Log Reading
- 01. Security Fundamentals & SOC Workflow
- 02. Firewall & Perimeter Rule Logic
- 04. Intrusion Detection
- 05. SIEM & Log Correlation
- 06. Vulnerability Management
- 07. Multi-Source Incident Response (Capstone)
- Cisco ASA
- Cisco Firepower (FTD)
- Fortinet FortiGate
- Splunk for Network & Security Operations
- Snort & Suricata IDS/IPS
- Security Scenarios & Capstone
- Zscaler: Secure Web & Private Access