TRIAGE
Review the available data, identify the most useful sources, and decide where the investigation should begin.
Analyze logs and evidence, identify the compromise, trace the attacker’s activity, and reconstruct the incident before your investigation window closes.
HUNT THE ATTACKER
A compromised environment leaves traces. Teams must work from logs, host evidence, network activity, and investigative clues to determine what happened and how far the attacker reached.
The strongest teams will connect individual observations into a defensible incident narrative. Speed matters, but conclusions must be supported by evidence.
Review the available data, identify the most useful sources, and decide where the investigation should begin.
Query logs and evidence for unusual behavior, suspicious access, persistence, and attacker movement.
Connect events across users, hosts, services, and time to separate meaningful activity from background noise.
Determine the initial access path, affected systems, actions taken, and how the compromise expanded.
Build a clear timeline that explains the sequence of attacker behavior from entry to impact.
Submit supported findings, indicators, scope, and response priorities in a concise incident summary.
Teams earn points for accurate, evidence-supported answers about the compromise, attacker behavior, scope, timeline, and recommended response. Final question weights, submission format, and tie-break rules will be published before the event.
Practice reading Windows and Linux logs, authentication records, web and network events, endpoint telemetry, and common indicators of compromise. Build comfort with filtering, timelines, and cross-source correlation.
Good notes matter. Track hypotheses, record supporting evidence, normalize timestamps, and revisit assumptions when new evidence changes the story.
Bootcamp information →SEPTEMBER 20 · ADDIS ABABA