All simulations

Honeypot

Six SOC analysts. One incident. The logs don't lie - but you have to read them.
Get the Teacher Code - Free Already have the code? Go to your dashboard →
Computer Science / Cybersecurity Grades 9-12 6 roles 55 min 1 class period
Computer Science / Cybersecurity Grades 9-12 6 roles 55 min 1 class period
Brightline Logistics, a Midwest freight company, 2:14 AM. A canary token tripped on a sensitive HR file. The night-shift SOC has 49 minutes to figure out what is happening before the attacker finishes the job.

Cooperative SOC incident-response sim. Students play security analysts hunting a cyber attack with real shell commands in a sandboxed terminal. First CS game in the catalog.

Get Free Teacher Access Already have access? Go to Dashboard

Class Time

49 minutes

Designed For

1 class period

Roles

6 roles

Class Sizes

Core (4 roles), Standard (5 roles), Full SOC (6 roles)

Learning Objectives

6 objectives

Standards

5 standards aligned

Where This Fits in Your Curriculum

Drop this into a cybersecurity, networking, or AP Computer Science Principles unit once students have seen a command line and know what a log file is. They need to be able to read output without panicking at a terminal. They do not need grep, jq, or awk syntax, and they do not need any security vocabulary going in, because the commands are handed to them and the terminal is sandboxed, so nothing they type can break anything. Underneath the intrusion, the real skill is investigative reasoning: holding partial evidence, deciding what it rules out, and trading depth of attribution against speed of containment while a 72-hour notification clock runs. It serves CS teachers building toward a security unit, CTE and IT-pathway instructors who need an authentic scenario, and any teacher who wants students to feel why 'we are still investigating' is sometimes the honest answer.

What Students Will Learn

Social & Emotional Learning (CASEL)

Aligned to the CASEL framework's core competencies. These are the SEL skills students actively practice while playing.

Flexible Class Sizes

Core (4 roles)
Minimum playable set. Commander, Network, Endpoint, Threat Intel. Forensics evidence folded into Endpoint. No Comms seat, so no 72-hour regulatory clock.
Standard (5 roles)
Adds Forensics Analyst for deep dives on auth logs, bash history, and the MFT.
Full SOC (6 roles)
All six roles including Comms / Legal Liaison who owns the 72-hour regulatory notification clock. Recommended once the team has played once.

How the Game Plays Out

Turn 1: Triage
Three alerts. One canary. Where do we start?
"What just happened, and is it real?"
Turn 2: Scope
How far did they get?
"Where else is the attacker, and do we cut the first host off the network NOW?"
Turn 3: Hunt
What is the attacker doing right now?
"Are they still inside, and if so, what are they reaching for?"
Turn 4: Contain
Pull the plug, set the trap, or wait?
"What do we trade for what?"
Turn 5: Attribute and Report
What do we tell the executives, and what really happened?
"Did we get it right?"

Roles Your Students Will Play

6 teams. The teacher assigns students to teams when the game starts.

Incident Commander
Network Analyst
Endpoint / DFIR Analyst
Threat Intel Analyst
Forensics Analyst
Comms / Legal Liaison

Hand Each Student Their Own Sheet

One click on the teacher dashboard prints a dossier for every role - background, goals, key facts, and their confidential briefing - plus the primary-source packet and a vocabulary sheet. Print them, or save as PDF, so each student reads their role on paper instead of huddling around one screen. The app still runs the votes and the action; the paper just carries the reading.

Primary Sources

Every role includes real historical documents. Students read them because they need the information to make their case.

NIST SP 800-61r2 - Computer Security Incident Handling Guide
Brightline firewall log excerpt (recent 1000 lines)
Brightline EDR alert queue
Brightline intel feed - known-bad IOCs
Master File Table excerpt
GDPR Article 33 and US state breach laws (simplified)

Key Terms Students Will Learn

SOCSIEMEDRIOCTTPMITRE ATT&CKphishinglateral movementexfiltrationC2beaconhashgrepjqregexcontainmentattributionAPTplaybookMFTcanary tokendwell time

After the Game: Debrief Questions

  1. Which piece of evidence mattered most for your role? Why that one and not the others?
  2. Commander: what was your Round 4 call (Isolate, Eradicate, Monitor and Trace, or none), what evidence did you weigh, and what would have changed your mind?
  3. The 72-hour notification rule: it is often said that late notification adds fines and lawsuits on top of the breach. What does that mean, and is it true?
  4. The attacker was Specter, a criminal crew whose attack tools many other criminals also use. Why does naming the actor matter if the tools are the same regardless of who sent them?
  5. The terminals in this game take grep, jq, awk and the unix pipe. Why is that the daily toolkit instead of a fancy GUI? When would a GUI tool be better?

Ready to run this in your classroom?

Get free teacher access in 30 seconds. No account needed - just a passcode that unlocks the full game library, teacher guides, and session tools.