A RetroVerse Studios tabletop game · v2.2 Playtest Edition

INCIDENT
ZERO

The attacker is already inside. A print-and-play board game where you win by thinking like a security analyst — six modules covering the whole incident lifecycle, from designing the network to facing the auditors.

👥 2–7 players⏱ 30–45 min / module🎲 one d20🖨 a printer💸 free (CC BY-NC-SA)

WANTED — DEAD TIRED OR ALIVE — BREACH IN PROGRESS_ PLAYTESTERS for crimes of curiosity & strategic thinking. Last seen rolling a d20 near a printer. REWARD Your name in the credits · eternal glory + a better security team report sightings → github.com/retroverse-studios

> CHOOSE YOUR MODULE_

🏗 Network Building

30–45 min · the calm before

Design a company network on a budget that can't afford everything. The gaps you leave come back later.

🛡 Hardening

30–45 min · defense-in-depth

Layer defenses for seven turns — then a pentester shows up to find out what you missed.

🔎 Incident Response

30–45 min · the flagship

A hidden attack chain is burning money every turn. Investigate, deploy, and reveal it before the clock runs out.

🚨 Disaster Recovery

30–45 min · crisis mode

The breach happened. Manage five furious stakeholders, a GDPR clock, and the ransom question.

🔬 Forensics

30–45 min · after the fire

Collect evidence, keep the chain of custody clean, and attribute the attack — sloppy handling loses the case.

📋 Audit & Compliance

30–45 min · prove it

Assess six security domains against real frameworks — or argue risk acceptance in the debate variant.

Each download is a single printable file: how-to-play, TO guide, core rules, module rules, all cards, and tracker sheets. Modules play standalone or chain into a full 4–5 hour lifecycle campaign.

> WANTED: PLAYTESTERS_

Download & print.
Grab a module above (Incident Response is the best first game), print the cards and tracker sheet, find a d20 and 2–6 accomplices.
Play it.
The How to Play guide scripts your first two turns. One of you reads the Threat Orchestrator's Guide and becomes the dungeon master.
Claim the reward.
Tell us what broke, what dragged, and what was brilliant via the feedback formGitHub Issues. Reward: your name in the credits.