CSRP — Cyber Security Responder & Practitioner
Lesson 25: Cyber Kill Chain and Attacker Mindset
Teacher Lesson Guide
Cyber School · BDO Ziv Haft
CSRP LESSON 25 — TEACHER LESSON GUIDE
Module 4 — Offensive Cyber & Vulnerability Analysis · Lesson 1 of 8 · Course Lesson 25 of 40 — M4 OPENS Title: Cyber Kill Chain and Attacker Mindset Duration: 4 hours Audience: Cyber Practitioner cohort (post-Module-3) advancing toward Cyber Analyst role Prerequisite: [AI-Practitioner] module badge (Module 3 complete)
1 · Why this lesson exists
L25 is the pivot lesson of CSRP. For 24 lessons the cohort has been a defender — building, monitoring, hardening, verifying. From today through L32, they study the attacker. Not to attack — to UNDERSTAND attack-shaped thinking so they can defend better. Threat hunters, red teamers, incident responders, and even the best defenders all share this fluency.
The Cyber Kill Chain is the canonical structured framework. Lockheed Martin’s 2011 model has stood the test of time as the shared vocabulary of every SOC, threat intel report, and security vendor briefing. It’s not the perfect description of every modern attack (MITRE ATT&CK is more granular, the unified Kill Chain integrates both), but it’s the foundation everyone learns first.
L25 also opens the ethical framing for Module 4. Every offensive technique demonstrated in M4 is paired with the legal and ethical boundaries — authorized targets only, lab environments only, written permission for any “real” pen-testing role learners might later take. Lab 25.3’s Packet Tracer environment is deliberately chosen as a low-risk visualization tool — no real systems involved.
Outcome contract: by the end of L25, every learner can (a) recite the 7 Kill Chain phases with a defender-leverage example for each, (b) map a real-world attack timeline to phases by reading multi-source logs, (c) populate the preventive/detective/response control matrix, (d) design an attack path through a layered network and recommend the segmentation controls that break it, and (e) articulate the “break the chain anywhere” defender principle.
2 · Learning objectives (verbatim)
- Explain the Cyber Kill Chain (Lockheed Martin’s 7-phase model) — what each phase IS, and the defender’s leverage point at each.
- Map a real-world attack timeline to Kill Chain phases by reading firewall + Windows Event + Linux auth logs.
- Map each phase to defensive controls (preventive · detective · response).
- Design an attack path through a layered network (DMZ → internal LAN → admin → servers) and the segmentation controls that break it.
- Prioritize defensive improvements via “break the chain” thinking.
- Apply the offensive-thinking discipline to actual security planning.
3 · Pre-class checklist (T-24h)
| # | Action | Verification |
| 1 | Confirm Oxy lab L25-killchain healthy | Health endpoint 200 |
| 2 | Sample artifacts staged: attack timeline + firewall logs + Windows Event Viewer logs + Linux auth logs + network diagram + optional pcap | ls /labs/L25/samples/ |
| 3 | Cisco Packet Tracer accessible from each seat (carryover from L11) | License + install verified |
| 4 | Pre-built 5-zone topology file (.pkt) available | File present at /labs/L25/topology/m4_zones.pkt |
| 5 | Verify cohort has Module 3 badge gating ([AI-Practitioner]) | LMS report |
| 6 | Challenge validator (validate.sh) works for multiple-choice scoring | Test with known good/bad submissions |
| 7 | M4 ethical-use disclaimer slide ready (mandatory opener) | Slide present in deck |
Hard stop conditions: if Packet Tracer is unavailable, Lab 25.3 falls back to a paper / whiteboard exercise (the topology is provided as a diagram). Don’t skip the lab — visualizing zones is critical.
4 · Time budget (4 hours)
| Block | Time | Activity | Energy |
| 0:00–0:15 | 15 min | M3 recap + M4 framing + ethical use disclaimer | High |
| 0:15–0:30 | 15 min | Quick-win — Identify ONE Kill Chain phase | High |
| 0:30–1:10 | 40 min | Ch.1 7-phase Kill Chain + Ch.2 Attacker Mindset | High |
| 1:10–1:20 | 10 min | Break | — |
| 1:20–2:10 | 50 min | Lab 25.1 — Map an Attack to the Cyber Kill Chain | Working |
| 2:10–2:20 | 10 min | Break | — |
| 2:20–3:00 | 40 min | Ch.3 Control Mapping + Lab 25.2 — Defensive Control Mapping | Working |
| 3:00–3:25 | 25 min | Ch.4 Zones + Lab 25.3 — Attack Path Design in Packet Tracer | Working |
| 3:25–3:30 | 5 min | Ch.5 “Break the Chain” principle | Medium |
| 3:30–3:55 | 25 min | Challenge — Break the Chain | Independent |
| 3:55–4:00 | 5 min | Wrap + L26 preview | Closing |
5 · Teaching beats — by block
Block 0:00–0:15 · M4 framing + ethical disclaimer
Opening line: > “Yesterday you closed Module 3 — you’re Cyber Practitioners. Today the camera flips. For 24 lessons you’ve been defenders. Today through L32 you study the attacker. NOT to attack — to UNDERSTAND. Best defenders think like attackers.”
Mandatory ethical-use disclaimer (verbatim, ~60 seconds): > “Everything in Module 4 is taught for defensive purposes. The techniques we discuss are real techniques real attackers use. We practice them ONLY in authorized lab environments. You do NOT use these techniques on systems you don’t own or don’t have written permission to test. Penetration testing against real organizations requires written authorization, scope, and a clear rules-of-engagement document. Misuse is illegal under Computer Fraud and Abuse Act (US), Computer Misuse Act (UK), Israel’s Computer Law, and equivalent legislation in every country we operate in. If in doubt — ask before you act. Now: let’s learn.”
Walk Module 4 map: 8 lessons. Cyber Analyst role unlocks at end of M4.
Block 0:15–0:30 · Quick-win — Identify ONE phase
Show on screen ONE Sysmon log line:
2026-05-20 14:23 sysmon ProcessCreate parent=outlook.exe child=powershell.exe -enc <base64>
Cohort votes which Kill Chain phase. Answer: Exploitation (Office/PDF macro just fired; PowerShell child spawned).
Reinforce: every alert sits in some phase. Learning to identify WHICH tells you what’s already happened and what’s NEXT.
Block 0:30–1:10 · Ch.1 + Ch.2 lecture
Ch.1 (25 min) — 7 phases. Slow down. For each phase, give: (a) what attacker does; (b) one real example; (c) the defender’s leverage point with a CSRP cross-reference (L17 for Delivery, L16 for Installation, etc.).
Common misconception: learners assume attacks are linear and phase-by-phase. Reinforce: modern attacks parallelize and skip. The PHASES are conceptual buckets; multiple events can fit one phase; some phases get skipped.
Ch.2 (15 min) — Attacker mindset. Walk the three constraints (time × detection × payoff), the low-hanging-fruit principle, living off the land, the patient attacker. End with: “Defender’s job: make every step expensive in time, detection risk, or both.”
Block 1:20–2:10 · Lab 25.1 (50 min)
The anchor lab. Per syllabus: read attack timeline + firewall + Windows Event Viewer + Linux auth logs + network diagram. Map ~25 events to Kill Chain phases. Write analyst summary.
Watch for: – Learners who try to find ALL 7 phases in the data → some attacks skip (e.g., no clear Weaponization log; that’s expected). – Learners who tag an event as the wrong phase because they confuse Exploitation with Installation. Coach: Exploitation = code runs once (the trigger); Installation = persistence is established (the artifact remains). – Learners who write a generic summary → push for SPECIFIC vectors. “Initial vector was X (phishing? exposed RDP? exploit?). Persistence was Y. Exfil channel was Z.”
The “aha” engineered: when a learner sees the chronological log sequence and recognizes the chain pattern. They get the Kill Chain on the FIRST attack timeline — that’s why it’s the canonical model.
Block 2:20–3:00 · Lab 25.2 — Control Mapping (40 min)
Given Lab 25.1’s mapping, build the control matrix. For each of the 7 phases: list preventive · detective · response controls applicable (referencing L9-L24). Then prioritize TOP 5 improvements + roadmap.
Watch for: – Learners who add controls for Recon (“we need recon detection!”). Coach: limited leverage there; spend effort on Delivery / Exploitation. – Learners who don’t differentiate preventive from detective. Push: “Does this BLOCK the attack or just TELL US it happened?” – Learners whose Top-5 is over-optimistic (10 items) or under-specific (“buy a SIEM”). Push for concrete, specific items.
Block 3:00–3:25 · Lab 25.3 — Packet Tracer (25 min)
Open m4_zones.pkt. The 5-zone topology has intentional segmentation weaknesses: – Internal LAN has direct routing to Server network (no firewall between) – DMZ web server can reach Admin network on RDP (over-permissive ACL) – No IDS visibility between zones – Admin jump-host has no MFA enforcement
Learners identify each weakness, draw the attacker path (Internet → DMZ → exploit web → reach Admin via lateral RDP → reach Server via admin creds → exfil), and recommend the firewall/ACL controls that break each crossing.
Watch for: – Learners who skip the “draw the path” step and jump straight to fixes → require the path drawing FIRST. Understanding the path is the lesson. – Learners who recommend “buy product X” → push for specific ACL rules, segmentation policies, MFA enforcement.
Block 3:25–3:30 · Ch.5 — Break the Chain (5 min)
Brief lecture. The “break the chain anywhere” principle. Cite the Pareto reality (6 controls block 80% of attacks). Close with the role-transition: “You ARE the Cyber Analyst now. Today was the framework. The rest of M4 fills it in.”
Block 3:30–3:55 · Challenge — Break the Chain (25 min)
Hand-off: > “25 minutes. Browser challenge. 30 events. Map each to a phase via multiple-choice. Identify the earliest break-point that Meridian’s existing controls would have caught. Identify ONE missing control that would have broken the chain even earlier. Submit ULC{…}. Three tiered hints at T=8, T=15, T=20. Go.”
Block 3:55–4:00 · Wrap + L26 preview
Quick recap: M4 1/8 done. Preview L26 (OSINT — Phase 1 in detail, ethical recon). Award [Kill-Chain-Mapper] to Challenge-pass learners.
6 · Differentiation
| Learner | Symptom | Move |
| Has pen-test background | Restless during Ch.1 | Give them the stretch task: map a 2024 published incident (Snowflake breach, MOVEit, XZ Utils) to Kill Chain. Present to cohort |
| Defense-only background | Struggles with attacker mindset | Pair with attack-savvy peer; remind them their Module 1-3 expertise is intact — Kill Chain just adds structure |
| Cisco Packet Tracer-shaky | Stuck in Lab 25.3 | Use the paper diagram fallback; the topology is the same; the tool isn’t the lesson |
| Hebrew-first | Asks for HE phase names | HE Kill Chain reference card in workbook |
| Ethics-anxious (“are we doing something illegal?”) | Reluctant on offensive exercises | Re-emphasize: lab environment, no real systems, defensive framing. The exercises are all in the CSRP-controlled Oxy lab — no internet-facing targets |
7 · Common pitfalls + recovery scripts
Pitfall 1: “MITRE ATT&CK is better than Kill Chain; why teach the older one?” Recovery: “Both have their place. Kill Chain teaches the lifecycle and the ‘break the chain’ principle. ATT&CK teaches the individual techniques (L26-L32 will use ATT&CK technique IDs). Together they’re complementary.”
Pitfall 2: “Modern attacks don’t follow the Kill Chain cleanly.” Recovery: “Correct. The Kill Chain is a teaching model. Many attacks parallelize, skip, or loop phases. But the underlying defender insight — break the chain anywhere — holds even when the chain is fuzzy.”
Pitfall 3: “I can’t tell Exploitation from Installation.” Recovery: “Exploitation is the CODE RUNNING once. Installation is what PERSISTS afterward. PDF triggers macro → PowerShell runs (Exploitation). PowerShell drops a scheduled task that restarts on reboot → that scheduled task is Installation.”
Pitfall 4: “My Top-5 controls all sound the same as the existing M2 stack.” Recovery: “Good. The point is: the L9-L24 stack you learned IS what breaks the chain. M4 helps you understand WHY each control exists where it does.”
Pitfall 5: “Can we just run a real attack on the lab to see it?” Recovery: “Lab 27 (Nmap) and Lab 29 (Exploitation) are where you’ll DO it. Today we read the artifacts. Building the mental model first is the discipline. Patience.”
8 · Materials checklist
- Gamma deck open
- Textbook PDF accessible
- Workbook digital/printed
- Oxy lab L25-killchain healthy
- Sample artifacts staged (timeline + 3 log sources + network diagram)
- Cisco Packet Tracer + topology file ready
- Slack #csrp-l25 open
- Visible timer for Challenge
- M4 ethical-use disclaimer slide confirmed in deck
- Whiteboard for control-mapping discussion
9 · Assessment & badging
Per-lesson quiz (LMS): 8 questions, 75% pass. Labs 25.1 / 25.2 / 25.3: progress points. Challenge — Break the Chain: required for badge. Submit ULC{…} after validator pass. Badge: [Kill-Chain-Mapper].
10 · Cross-references
- L9-L24: every defensive control gets re-contextualized in the Kill Chain matrix today
- L11 Cisco Packet Tracer: carryover environment for Lab 25.3
- L14 MFA: referenced in “missing control” near-spoiler
- L17 Mail Security: Delivery defenses
- L16 EDR: Exploitation + Installation defenses
- L22 UEBA: late-phase detection
- Forward to L26: Phase 1 (Recon) in detail
- Forward to L29: Phase 4 (Exploitation) in detail
- Forward to L33+ Module 5 SOC: Kill Chain becomes daily SOC vocabulary
11 · Sign-off
| Role | Name | Date |
| Lesson author | ||
| BDO Ziv Haft reviewer | ||
| Pedagogy reviewer | ||
| Cyber technical reviewer | ||
| Ethical-use disclaimer approval | ||
| Approved for cohort delivery |