Cybersecurity-Mastery

Home › Labs › Boss Lab 5 — Incident: Triage a Compromised Host

Boss Lab 5 — Incident: Triage a Compromised Host

A host is suspected compromised. Investigate the evidence, extract IOCs, identify the malware and initial access, and produce an incident report with detections.
DifficultyAdvanced
Est. time~5 hours
TracksForensics, Malware, Defensive

Environment

The Forensics part environment (dfir-box) plus a provided memory + disk image of a compromised host (use a public DFIR dataset).

Everything is local and isolated. This is a capstone: it assumes you've worked the related chapters below.

Objectives (capture the flags)

Stages

Work them in order. Each stage has a hint — try hard before opening it.

Stage 1 — Memory triage

Find the malicious process, its network connections and injected code.

Hint

Volatility: pslist/psscan, netscan, malfind, cmdline.

Stage 2 — Disk timeline

Build a super timeline and find initial access and persistence.

Hint

plaso/log2timeline + the browser/email/download artefacts.

Stage 3 — Identify the malware

Extract the artefact and triage it in isolation; classify the family.

Hint

strings/capa/YARA on the dumped module — do not run it on your host.

Stage 4 — Extract IOCs & detections

Produce hashes, domains, mutexes; write YARA + Sigma.

Hint

Turn every artefact into something a defender can hunt with.

Stage 5 — Report

Write the IR report: timeline, root cause, impact, containment, and recommendations.

Hint

Defensible narrative + the one control that would have prevented initial access.

Debrief

What was the initial access, and which single preventive control (patch, macro policy, egress filter) would have stopped the whole incident?

Chapters this draws on

← Back to the Labs campaign

Cybersecurity-Mastery — interactive security learning · runs locally