0% Complete
0/0 Steps
  1. About

    About Cyber School
  2. About BDO
  3. The CSRP program Syllabus
  4. Module 1
    The Cyber World and CIA Triad
    6 Topics
  5. The OSI Model and Network Layers
    6 Topics
  6. IP Addressing, Subnetting and Routing
    6 Topics
  7. DNS and DHCP
    6 Topics
  8. Windows Server Administration
    6 Topics
  9. Active Directory and Identity Management
    6 Topics
  10. Linux CLI Fundamentals
    6 Topics
  11. Linux Permissions and Hardening
    6 Topics
  12. Module 2 - Defense Technologies and Cyber Tools
    Firewall Architecture and Rule Design
    5 Topics
  13. NAT and Secure Traffic Mapping
    6 Topics
  14. Enterprise VPN Solutions
    6 Topics
  15. IDS and IPS
    5 Topics
  16. Identity and Access Management
    5 Topics
  17. Multi-Factor Authentication
    6 Topics
  18. Data Loss Prevention
    6 Topics
  19. Endpoint Security and EDR
    6 Topics
  20. Mail Security
    6 Topics
  21. Web Proxy and URL Filtering
    6 Topics
  22. Regulation and Compliance
    6 Topics
  23. Cloud Security
    6 Topics
    |
    1 Quiz
  24. Module 3 - Ai in security
    AI in Security
    5 Topics
  25. ML Anomaly Detection
    5 Topics
  26. AI Threats
    5 Topics
  27. LLM Defense
    6 Topics
  28. Module 4 - Offensive Cyber & Vulnerability Scanning
    Cyber Kill Chain and Attacker Mindset
    6 Topics
  29. OSINT and Public Intelligence Gathering
    6 Topics
  30. Network and Port Scanning with Nmap
    6 Topics
  31. Vulnerability Scanning
    6 Topics
  32. Exploitation Fundamentals
    6 Topics
  33. Web Application Security
    5 Topics
  34. Social Engineering
    5 Topics
  35. Password and Hash Cracking
    5 Topics
  36. Module 5 - SOC and Advance Cyber Analyst
    SOC Structure and Operations
    6 Topics
  37. SIEM Fundamentals with Splunk
    6 Topics
  38. Alerting and Dashboards
    6 Topics
  39. Incident Response
    5 Topics
  40. Basic Digital Forensics
  41. Capstone A - The Attack: Breaching Meridian
  42. Capstone B - The Defense: Defending Meridian
  43. ISC2 CC Mock Exam and CSRP Graduation
    2 Quizzes
Lesson Progress
0% Complete

CSRP  —  Cyber Security Responder & Practitioner

Lesson 25: Cyber Kill Chain and Attacker Mindset

Student Lab Guide

Cyber School  ·  BDO Ziv Haft

CSRP LESSON 25 — STUDENT LAB 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


0 · Before you begin

Why you need this (as a cyber professional)

You’ve spent 24 lessons becoming a defender. Today the camera flips. For the next 8 lessons (Module 4), you study what the attacker does — not to attack anyone, but so you defend better.

The Cyber Kill Chain is the shared vocabulary of every SOC, threat-intel report, and red-team briefing in cybersecurity. Learning it gives you a framework to TALK about incidents, READ threat reports, and PRIORITIZE defenses. Without it, you respond to events one at a time and miss the chain. With it, you see the chain and interrupt it early.

This lesson is also the role transition. After Module 3 you’re a Cyber Practitioner — you can BUILD defenses. After Module 4 you’ll be a Cyber Analyst — you can THINK like the attacker, INVESTIGATE incidents, and CORRELATE events. Today is day one.

⚠️ Ethical use — read this carefully

Everything in Module 4 is taught for defensive purposes. Real techniques real attackers use. We practice 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 requires written authorization + scope + rules of engagement. Misuse is illegal. If in doubt — ask before you act.

What you need ready

  • Browser-based documentation workstation (logs + timeline + diagram pre-staged)
  • Cisco Packet Tracer (carryover from L11)
  • Workbook + Textbook open
  • Slack #csrp-l25 open

Modules you’ve already done that feed in

  • L9 Firewall: Delivery / C2 defenses
  • L11 Cisco Packet Tracer: the Lab 25.3 environment
  • L14 MFA: key control mentioned in challenge
  • L15 DLP: Actions-on-Objectives defense
  • L16 EDR: Exploitation + Installation defenses
  • L17 Mail Security: Delivery defenses
  • L18 Web Proxy: Delivery + C2 defenses
  • L22 UEBA: late-phase detection
  • L24 LLM Defense: prompt injection is a new Delivery vector for AI-stack attacks

1 · Quick-Win Lab — Identify ONE Kill Chain Phase (5 min)

Goal: Show that every alert sits in some phase.

Steps

  1. Read this single Sysmon log line:
  2. 2026-05-20 14:23 sysmon ProcessCreate parent=outlook.exe child=powershell.exe -enc <base64>
  1. Vote (Slack poll or hands): which Kill Chain phase?
  2. Debrief — the answer is Exploitation. A user just opened an Outlook attachment (PDF or Office doc with macro); the macro fired and spawned a PowerShell child. That’s the moment the attacker’s code RAN. The base64-encoded command argument is a strong indicator.
  3. Reflect: every alert in your SOC sits in SOME phase. Identifying WHICH tells you what’s already happened and what’s NEXT.

You did it. Move to lecture.


2 · Lab 25.1 — Map an Attack to the Cyber Kill Chain (50 min · Core)

Goal: Read multi-source logs covering a real attack timeline. Map every event to a Kill Chain phase. Write the analyst summary.

Scenario

You’re a SOC analyst at Meridian Corp. An incident occurred over ~36 hours. The SRE team forwarded you the artifacts: an attack timeline (their reconstruction), firewall logs from the perimeter, Windows Event Viewer logs from affected hosts, Linux auth logs from the DMZ web server, and the company network diagram.

Your job: map every event to a Kill Chain phase. Identify which phases the attack used vs. skipped. Write a 200-word analyst summary covering: initial vector, persistence mechanism, exfiltration channel.

What you have

  • /labs/L25/samples/attack_timeline.md — chronological reconstruction (~25 events)
  • /labs/L25/samples/firewall.log — perimeter firewall log (~500 lines)
  • /labs/L25/samples/windows_eventviewer.log — Win Event Viewer (~200 entries)
  • /labs/L25/samples/linux_auth.log — DMZ web server auth log
  • /labs/L25/samples/network_diagram.png — Meridian’s network
  • (Optional) /labs/L25/samples/network_traffic.pcap — Wireshark capture

Step-by-step

Step 1 — Orient (5 min)

cd /labs/L25/samples
cat attack_timeline.md
ls -la

Read the timeline first to get the chronological frame.

Step 2 — Read the logs (15 min)

head -50 firewall.log
head -50 windows_eventviewer.log
head -50 linux_auth.log

Identify the time-aligned events across log sources. Use timestamps to correlate.

Step 3 — Phase tagging (20 min) In /labs/L25/work/lab1_mapping.md, build this table:

#TimeSourceEvent summaryKill Chain phaseWhy
01…firewall…Recon / Weap / Delivery / Exploit / Install / C2 / Actions…
………………

Tag each event with phase + brief justification.

Step 4 — Identify missing phases (5 min) Which phases is the attack NOT visible in? (E.g., Weaponization typically has no log signal.) Note which phases the attack uses vs. skips.

Step 5 — Analyst summary (5 min) Write 200 words covering: – Initial vector (how did the attacker first get in?) – Persistence mechanism (how do they keep access?) – Exfiltration channel (how does data leave?) – One observation about defender visibility (which phases were well-instrumented; which weren’t?)

Submission

Save lab1_mapping.md (table + summary). Lab platform auto-grades on rubric.

Hints

  • Outlook → PowerShell child (with -enc) = Exploitation
  • A user clicking a link in an email arriving from outside = Delivery
  • A new scheduled task / service created = Installation
  • Outbound DNS to non-resolvable / suspicious domain = C2
  • Large outbound HTTP upload to an unusual destination = Actions on Objectives
  • An admin login from a new geographic region = potential lateral movement (mid-Installation / late C2)

3 · Lab 25.2 — Defensive Control Mapping (40 min · Core)

Goal: For the attack mapped in Lab 25.1, build the control matrix. Prioritize the top 5 improvements.

Scenario

The Meridian CISO wants a roadmap based on this incident. “What controls would have stopped (or detected) what stage? What should we invest in?”

Steps

Step 1 — Build the control matrix (20 min)

In /labs/L25/work/lab2_control_matrix.md:

Kill Chain phasePreventive controlsDetective controlsResponse controls
Recon   
Weaponization   
Delivery   
Exploitation   
Installation   
C2   
Actions   

For each row, list applicable controls. Reference CSRP lesson controls where relevant (L9 firewall, L14 MFA, L15 DLP, L16 EDR, L17 mail security, L18 proxy, L22 UEBA, etc.).

Step 2 — Identify what Meridian HAS vs. MISSES (10 min) For each cell, mark [have] or [missing] for Meridian’s current state. (Per syllabus the lesson assumes a baseline; treat anything not explicitly mentioned in artifacts as missing.)

Step 3 — Prioritize Top 5 improvements (5 min) Choose 5 specific controls Meridian should implement. For each: – Which phase does it interrupt? – Why this control (vs. alternatives)? – Estimated effort (low / medium / high)?

Step 4 — Roadmap presentation outline (5 min) Write a 1-page outline you’d present to the CISO. Cover: incident summary, key findings, top 5 controls, expected outcome.

Submission

lab2_control_matrix.md with all sections. Auto-graded.

Hints

  • For Recon, controls are limited but not zero. Honey-tokens, fake LinkedIn profiles, recon-tripwires on canary domains.
  • For Delivery + Exploitation, the L9-L18 stack covers most needs. The interesting question is: which of those does Meridian have well-tuned?
  • For Actions on Objectives, segmentation (L9) + DLP (L15) + UEBA (L22) are the workhorses.

4 · Lab 25.3 — Attack Path Design in Cisco Packet Tracer (25 min · Core)

Goal: Open the layered topology in Packet Tracer. Identify weak segmentation. Draw attacker movement. Recommend control placements.

Scenario

Meridian’s network has 5 zones: Internet, DMZ, Internal LAN, Admin network, Server network. There are intentional segmentation weaknesses. Find them. Show how an attacker could move Internet → Server network. Recommend specific firewall / ACL controls that break the path.

Steps

Step 1 — Open the topology (3 min)

# Locate the topology file
ls /labs/L25/topology/
# Open in Packet Tracer
packettracer /labs/L25/topology/m4_zones.pkt

Step 2 — Identify zones (3 min) Visually mark on the topology (or in your notes): – Where is the Internet boundary? – What’s exposed in the DMZ? – Where are users? – Where are admins? – Where are servers/databases?

Step 3 — Mark exposed services (5 min) In the DMZ, identify what services are reachable from the Internet (HTTP/HTTPS, SSH, RDP, mail, VPN). Note any that shouldn’t be (e.g., admin RDP exposed externally).

Step 4 — Identify weak segmentation (5 min) For each zone-to-zone boundary, check the existing firewall/ACL config: – Is there a firewall between Internet and DMZ? (yes — expected) – Internet → Internal LAN? (no direct — expected; should be blocked) – DMZ → Internal LAN? (one-way or none — depends on config; often a weakness) – Internal LAN → Server network? (should be FILTERED; often a weakness) – Admin → Server / Internal? (should be tightly controlled)

Document weaknesses found.

Step 5 — Draw attack path (5 min) On the topology (or in a sketch in /labs/L25/work/lab3_path.md), draw: – Attacker enters via DMZ web exploit – Lateral move into Internal LAN (which weak boundary?) – Pivot to Admin network (stolen credentials) – Reach Server network (using admin RDP) – Exfiltrate from Server network

Step 6 — Recommend controls (4 min) For each crossing the path uses, recommend ONE control: – Firewall ACL rule (specific source/dest/port) – Segmentation (separate VLAN, no routing) – MFA enforcement on jump host – IDS placement – DLP on egress

Submission

/labs/L25/work/lab3_path.md with: zone summary, exposed-services list, weak-segmentation findings, attack-path drawing, control recommendations.

Hint

The intentional weaknesses include: (a) Internal LAN has direct routing to Server network (no firewall between), (b) DMZ web server can reach Admin RDP, (c) no IDS visibility between zones, (d) admin jump-host has no MFA. Find these (plus any others you spot).


5 · Challenge — Break the Chain (25 min · Independent)

No walkthrough. Three tiered hints at T=8, T=15, T=20.

Brief

Browser-based challenge. You receive a full attack timeline (~30 events over 48 hours) for an attack on Meridian Corp. Logs from multiple sources. Network diagram. Your job:

  1. Map each event to a Kill Chain phase via multiple-choice validation.
  2. Identify the EARLIEST phase where the chain could have been broken with an existing Meridian control.
  3. Identify ONE control that’s missing and would have broken the chain even earlier.

Submit ULC{…} after the validator confirms.

What you have

  • /labs/L25/challenge/timeline.md — 30-event attack reconstruction
  • /labs/L25/challenge/logs/ — multi-source log files
  • /labs/L25/challenge/network_diagram.png
  • Web validator interface for multi-choice phase tagging

What you produce

  • /labs/L25/work/challenge_break_the_chain.md — 30 events tagged + break-point analysis + missing-control recommendation
  • Submit the validator-emitted ULC{<16-hex>} flag

Submission

Run /labs/L25/validate.sh. On pass: validator prints accept message + ULC{…}. Paste flag into LMS.

Tiered hints

  • T=8 (Concept): Think SEQUENTIALLY. Events are roughly time-ordered. Recon happens before Delivery. Persistence happens after Exploitation. C2 happens after Installation. The chain is the structure.
  • T=15 (Pattern): Common signatures: Outlook → PowerShell child = Exploitation; new scheduled task = Installation; outbound DNS to non-resolvable domain = C2; large outbound transfer to unusual destination = Actions on Objectives; first observation of an admin login from an unusual region = potential lateral (late C2 or Installation).
  • T=20 (Near-spoiler): The chain in this scenario could have been broken at Delivery (mail security would have caught the malicious attachment) and again at C2 (egress filtering would have caught the unusual outbound). Missing control: phishing-resistant MFA — would have stopped credential reuse during lateral movement.

Badge

[Kill-Chain-Mapper] issued on validator pass.


6 · Wrap-up

You mapped a 25-event attack timeline to the Kill Chain. You built the control-mapping matrix. You designed an attack path through a layered network and recommended segmentation controls. You broke the chain.

Next lesson (L26): OSINT and Reconnaissance. Today: the framework. Next time: Phase 1 in detail — what an attacker can learn about YOUR organization from public sources, and how to harden against it. Strictly ethical: lab targets only.


7 · Quick reference card

The 7 Kill Chain phases 1. Reconnaissance 2. Weaponization 3. Delivery 4. Exploitation 5. Installation 6. Command & Control (C2) 7. Actions on Objectives

Three control types per phase – Preventive (block) – Detective (alert) – Response (contain)

The defender principle > “Break the chain at ANY phase to stop the attack.”

Where to invest first Cheapest interrupt + earliest phase = highest leverage. Delivery + Exploitation usually win.

The 6 controls that block 80% of real attacks 1. Phishing-resistant MFA (L14) 2. Endpoint patching 3. Mail security (L17) 4. EDR with current signatures (L16) 5. Egress filtering (L9) 6. Segmentation between user and server networks (L9 / L25.3)