The Holiday-Weekend Incident: A SOC Tabletop for Machine-Speed Attacks
It's a long weekend. An alert fires at 2 a.m. You're the incident commander. What you decide in the next few minutes can make the difference between this staying a near-miss and becoming a loss.
Published Nov 2026Read time 40 minLevel BeginnerBy CreativeCyber
What this page is (and isn't). This is an educational interpretation of a public advisory from CERT-In (the Indian Computer Emergency Response Team, India's national cybersecurity incident-response agency). It does not imply CERT-In endorsement. The “Illustrative BFSI Entity” (a fictional Banking, Financial Services and Insurance organisation), its SOC (Security Operations Centre — the team that monitors for and responds to security incidents), and this incident are entirely fictional teaching material. CERT-In's CSIRT-Fin (its Computer Security Incident Response Team for the finance sector) has designated the threat actor behind the campaign this advisory describes “CRAFTY FALCON.” Source: CERT-In Advisory CIAD-2026-0058, 4 Nov 2026.
Figure 1. 38 minutes, start to outcome — the decisions in between are what this exercise is about. Illustrative timeline
Holiday
CERT-In flags attacks timed to weekends and holidays specifically
Source: CIAD-2026-0058
24×7
CERT-In's recommended monitoring window
Source: CIAD-2026-0058
38 min
Illustrative time from first alert to outcome in this tabletop
Illustrative example — not live incident data
4
Decision points this exercise walks you through
Illustrative example — not live incident data
You don't need to have run a SOC before. This exercise walks you through what an incident commander actually does: staying calm, not guessing — working through a short, repeatable decision sequence under time pressure.
Figure 2. In this exercise, no single source alone was enough — multiple matching signals raised confidence enough to escalate. This is how correlation played out in this scenario, not a fixed rule for every alert. Illustrative diagram