CreativeCyber Logo
  • Home
  • Knowledge
  • Practitioner Toolkit
Request a walkthrough
creativecyber.in/ knowledge/ bfsi-ai-attack-soc-tabletop
Practitioner Toolkit · Learning Series
Part 1 · See the Attack Part 2 · Break the Chain Part 3 · Detect & Respond Part 4 · Know Every Door Part 5 · Where the Money Moves Part 6 · Harden & Govern Part 7 · The Six-Hour Clock

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 2026 Read time 40 min Level Beginner By CreativeCyber
Share this article: LinkedIn X WhatsApp Copy Link
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.
Incident timeline: detection to containment A timeline from 02:14 to 02:52. First a SIEM (Security Information and Event Management — the tool that collects logs from many systems into one place) alert on an anomalous login, then correlation with a cloud audit event, then a decision point, then containment actions, then a final state of either contained or escalated loss, shaped by the decisions made along the way. 02:14SIEM alert 02:19correlation 02:24decision point 02:40containment action 02:52outcome

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.

In this exercise: how multiple matching signals raised confidence This diagram shows how correlation worked in this specific tabletop scenario, not a universal SOC rule. Three evidence sources — a SIEM login alert, a cloud audit log, and transaction monitoring — fed into a single correlation decision. In this exercise, any one source alone was weak evidence, but the matching signals together raised confidence enough to escalate for incident handling. SIEM: anomalous login weak alone Cloud audit log unscheduled deploy Transaction monitoring ₹1 test transaction In this exercise: matching signals → confidence rises Escalate for incident handling

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

Found this useful?

Share with your security, engineering or risk team.

Share on LinkedIn Post on X Share on WhatsApp Copy Link

Explore all seven parts

Part 1 of 7
How a Machine-Speed BFSI Attack Unfolds: From UAT to Unauthorized Transfer
Part 2 of 7
Breaking the Chain: Controls That Disrupt API and Cloud-Based Financial Attacks
Part 3 of 7 · You are here
The Holiday-Weekend Incident: A SOC Tabletop for Machine-Speed Attacks
Part 4 of 7
Break the Chain, Part 4: Know Every Door, Track Every Key
Part 5 of 7
Break the Chain, Part 5: Where the Money Actually Moves
Part 6 of 7
Break the Chain, Part 6: Harden the Interface, Get the Right People in the Room
Part 7 of 7
Break the Chain, Part 7: The Six-Hour Clock
PRACTITIONER TOOLKIT
Turn This Into Practice
Explore the Practitioner Toolkit workflow, or discuss your incident-response readiness with CreativeCyber.
Explore Practitioner Toolkit
In This Article
The Scenario The IC Role Evidence Discipline Automation vs. Judgment Run the Incident Quick Check