Cybrary ForgeCYBRARY / FORGE
Forge Exercises
powered by Cybrary Forge

The technical answer is only half of it. Practice the other half.

Decisions on a clock, with the consequence of each one carried forward. Messages arrive from alerts, press, regulators and your own staff, obligation deadlines run in the background, and the after-action review shows exactly what each call cost — in money, downtime, exposure and trust.

Scenarios
6 sectors
Decisions
30 scored calls
Messages
46 scripted injects
Obligations
13 deadline clocks

How a run works

Messages arrive on a clock
Alerts, technical updates, staff mail, press calls, social posts, regulator letters, customer complaints and the attacker themselves — nine channels, each with its own tone.
Decisions open and expire
Each decision belongs to a role and has a deadline. Let it lapse and the run takes the lapse consequence instead of a choice.
Obligation clocks run underneath
A 72-hour privacy window, a four-business-day materiality filing, a contractual supplier notice. Miss one and regulatory exposure jumps.
The after-action review adds it up
Every choice replays with its consequence, the meters land, and the five dimensions are scored so the debrief writes itself.

Scored on five dimensions

  • Speed of decision

    How long a decision sat open while the clock ran.

  • Decision quality

    Whether the call held up once its consequence landed.

  • Escalation and authority

    Whether the right person was pulled in, and when.

  • Communication

    What customers, staff, press and partners were told.

  • Regulatory compliance

    Whether the notification windows were satisfied in time.

Four meters the board watches

  • Direct cost

    Ransom, response, overtime and remediation, carried run to run.

  • Downtime

    Hours of business interruption your choices add or avoid.

  • Regulatory exposure

    Rises when an obligation clock is missed or fudged.

  • Public trust

    Moves with every statement, silence and leak.

Seven seats

Chief Executive · CISO · General Counsel · Communications · Chief Financial Officer · Operations · Privacy Officer

Run it as a team, or fill the empty chairs

Whoever starts the exercise owns the clock and can pause, resume and drop in one of 9 surprises — or write their own. Seats nobody takes can be played by an AI colleague with a personality; if the model is slow or off-script, the seat falls back to the persona’s deterministic play, so a run never stalls.

Run it with your team

One seat per role. Empty seats can be played by an AI colleague with a personality, and whoever starts the exercise controls the clock and can drop in surprises.

Steady hand
Decisive
Aggressive containment
Cautious
Legalistic
Customer first

Choose a crisis

Every scenario is fictional — fictional company, fictional regulator’s letter — but the obligation shapes and the trade-offs are the real ones. 26 of the steps hand work to the technical responders on the simulated desktop while the executives decide.

Logistics
5h exercise
6 decisions
3 clocks

Edge appliance breach at Meridian Freight

An internet-facing VPN appliance was exploited eleven days ago. Footholds are spread across the estate and a customer found out before you did.

Seats: Chief Executive, CISO, General Counsel, Communications, Chief Financial Officer, Operations, Privacy Officer

Hands-on track: Forge Chef: decrypt the chain, Persistence Lab, DFIR Tools Lab, DFIR Artifact Lab, Firewall Lab, TCP Lab, Remote Desktop Lab

See the step-by-step path (16 steps)
  1. 1Forge Chef: decrypt the chain
    Hands-on
    00:10 → 01:40

    Unwrap this breach's own artifacts: the appliance exploit request, the encoded scheduled task on the file server and the exfil manifest. The destination host you recover is what the customer notification names. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Infrastructure wants to reimage the appliance tonight. Evidence first?".

  2. 2DFIR Artifact Lab
    Hands-on
    00:10 → 01:40

    Investigate the file server the scheduled task landed on: detonate the sample in isolation, image the disk and carve the artifacts that prove what ran before the rebuild. Open it at: Windows desktop → Start menu → DFIR Artifact Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Infrastructure wants to reimage the appliance tonight. Evidence first?".

  3. 3DFIR Tools Lab
    Hands-on
    00:10 → 01:40

    Image the appliance with dd, walk the partitions with mmls/fls and carve deleted files with foremost before anyone rebuilds it. Open it at: Linux desktop → Start menu → DFIR Tools Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Infrastructure wants to reimage the appliance tonight. Evidence first?".

  4. 4The web shell is live and being used. What happens to the appliance right now?
    Decision
    00:15 → 01:00

    Pulling it offline drops every remote depot and third-party integration. Leaving it up leaves the intruder a front door.

    Leads: CISO · Done when: CISO picks one of 3 options before 01:00. Letting it lapse is scored as a choice.

  5. 5Infrastructure wants to reimage the appliance tonight. Evidence first?
    Decision
    00:40 → 01:40

    The appliance holds the only record of what came in and out. A vendor factory reset destroys it.

    Leads: CISO · Done when: CISO picks one of 3 options before 01:40. Letting it lapse is scored as a choice.

  6. 6Firewall Lab
    Hands-on
    00:50 → 02:25

    Contain the exfil path at the network edge: add the drop rule for the upload destination, prove it blocks with a test connection, and leave legitimate traffic untouched. Open it at: Windows desktop → Start menu → Firewall Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Three footholds are confirmed. How far does the rebuild go?".

  7. 7Persistence Lab
    Hands-on
    00:50 → 02:25

    Find and grade every foothold the intruder left: cron entries, systemd timers, rogue accounts and loaded modules. The count you report drives the rebuild scope. Open it at: Linux desktop → Start menu → Persistence Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Three footholds are confirmed. How far does the rebuild go?".

  8. 8Remote Desktop Lab
    Hands-on
    00:50 → 02:25

    Prove Network Level Authentication is enforced on the file server: show where a non-NLA client and a wrong password each fail. Open it at: Windows desktop → Start menu → Remote Desktop Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Three footholds are confirmed. How far does the rebuild go?".

  9. 9TCP Lab
    Hands-on
    00:50 → 02:25

    Read the SMB session to the file server off the wire: port, retransmissions, the real scaled window and who closed the connection. Open it at: Windows or Linux desktop → Start menu → TCP Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Three footholds are confirmed. How far does the rebuild go?".

  10. 10Preserve evidence before the rebuild
    Obligation
    01:10 → 01:40

    The appliance image has to exist before infrastructure resets the device.

    Leads: CISO · Done when: A decision that satisfies it is made before 01:40.

  11. 11Three footholds are confirmed. How far does the rebuild go?
    Decision
    01:20 → 02:25

    The responders' foothold count from the Persistence lab is the input here: cron, timer, rogue sudo account — and possibly more not yet found.

    Leads: Operations · Done when: Operations picks one of 3 options before 02:25. Letting it lapse is scored as a choice.

  12. 12The customer is invoking their notification clause. What do you send?
    Decision
    01:30 → 02:40

    Contract requires notice of a security incident affecting their data within 24 hours of becoming aware.

    Leads: General Counsel · Done when: General Counsel picks one of 3 options before 02:40. Letting it lapse is scored as a choice.

  13. 13Customer contractual notice within 24 hours of awareness
    Obligation
    02:10 → 02:40

    Modeled as the exercise window; the clause starts at the exfiltration finding.

    Leads: General Counsel · Done when: A decision that satisfies it is made before 02:40.

  14. 14Driver personal data was in the staged archive. Notifiable?
    Decision
    02:20 → 03:35

    Names, addresses and license numbers for roughly 3,100 drivers. Awareness began with the confirmed exfiltration finding.

    Leads: Privacy Officer · Done when: Privacy Officer picks one of 3 options before 03:35. Letting it lapse is scored as a choice.

  15. 15The trade weekly publishes tomorrow. What is your position?
    Decision
    02:55 → 04:10

    Drivers, customers and staff will all read the same story.

    Leads: Communications · Done when: Communications picks one of 3 options before 04:10. Letting it lapse is scored as a choice.

  16. 16Regulator notification within 72 hours of awareness
    Obligation
    03:05 → 03:35

    Personal data in scope means the privacy clock is running.

    Leads: Privacy Officer · Done when: A decision that satisfies it is made before 03:35.

Healthcare
4h exercise
5 decisions
2 clocks

Double extortion at Northwind Health

Encryption across the clinical estate at 02:10, a data-theft claim by breakfast, and press calling before the board convenes.

Seats: Chief Executive, CISO, General Counsel, Communications, Chief Financial Officer, Operations, Privacy Officer

Hands-on track: Forge Chef: decrypt the chain, DFIR Tools Lab, Persistence Lab, Reps: Seeded Payload Drop

See the step-by-step path (11 steps)
  1. 1Forge Chef: decrypt the chain
    Hands-on
    00:00 → 01:20

    Unwrap the four artifacts from this intrusion: the macro loader URL, the encoded beacon launcher, the ransom-note contact block and the ransomware mutex. The C2 and the victim id you recover are what the negotiation and notification calls rest on. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The press has the ransom note. What do you say?".

  2. 2Persistence Lab
    Hands-on
    00:00 → 01:20

    Find every foothold left behind — cron, timers, accounts, modules — so the restore does not put the intruder back with the data. Open it at: Linux desktop → Start menu → Persistence Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The press has the ransom note. What do you say?".

  3. 3Reps: Seeded Payload Drop
    Hands-on
    00:00 → 01:20

    Drop the seeded payload with the framework, then take the artifact into Forge Triage: report the SHA-256 and imphash, the rule that fires on the build marker, the C2 URL and the Run-key, and the injected region in the memory slice. Those indicators are what the containment sweep is written from. Open it at: Windows desktop → Metasploit in the terminal, then Forge Triage (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The press has the ransom note. What do you say?".

  4. 4Clinical systems are degraded. What happens to patient flow?
    Decision
    00:10 → 00:45

    Emergency care is running on paper. Elective imaging is unavailable.

    Leads: Operations · Done when: Operations picks one of 3 options before 00:45. Letting it lapse is scored as a choice.

  5. 5The press has the ransom note. What do you say?
    Decision
    00:30 → 01:20

    Forensics has not yet confirmed exfiltration. The reporter publishes at noon.

    Leads: Communications · Done when: Communications picks one of 3 options before 01:20. Letting it lapse is scored as a choice.

  6. 6Public statement before the story runs
    Obligation
    00:50 → 01:20

    Say something accurate before someone else defines it for you.

    Leads: Communications · Done when: A decision that satisfies it is made before 01:20.

  7. 7DFIR Tools Lab
    Hands-on
    01:05 → 02:50

    Image an encrypted clinical file server, walk the partitions and carve the deleted staging directory to prove what was taken before it was locked. Open it at: Linux desktop → Start menu → DFIR Tools Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Exfiltration of personal data is confirmed. Notify?".

  8. 8Exfiltration of personal data is confirmed. Notify?
    Decision
    01:35 → 02:50

    The clock on notifying the authority runs from the moment you became aware.

    Leads: Privacy Officer · Done when: Privacy Officer picks one of 3 options before 02:50. Letting it lapse is scored as a choice.

  9. 9Pay the ransom?
    Decision
    01:50 → 03:20

    Backups for imaging are 14 hours old and restorable. The archive copy is intact. Legal has flagged sanctions screening.

    Leads: Chief Executive · Done when: Chief Executive picks one of 3 options before 03:20. Letting it lapse is scored as a choice.

  10. 10Notify the data protection authority
    Obligation
    02:20 → 02:50

    Within 72 hours of awareness — modeled here as the exercise window.

    Leads: Privacy Officer · Done when: A decision that satisfies it is made before 02:50.

  11. 11How do you bring the estate back?
    Decision
    02:40 → 03:55

    The initial access vector is a stolen VPN credential without MFA. It has not yet been closed.

    Leads: CISO · Done when: CISO picks one of 2 options before 03:55. Letting it lapse is scored as a choice.

Biotechnology
5h exercise
6 decisions
3 clocks

Privileged insider at Halcyon Bio

A departing platform administrator hid a kernel module on a research host and left with data. You have a notice period, a competitor and a partner contract in play.

Seats: Chief Executive, CISO, General Counsel, Communications, Chief Financial Officer, Operations, Privacy Officer

Hands-on track: Forge Chef: decrypt the chain, Kernel Module Lab, DFIR Tools Lab, Persistence Lab, Privilege Escalation

See the step-by-step path (14 steps)
  1. 1Persistence Lab
    Hands-on
    00:00 → 01:10

    Sweep for the accounts, keys, timers and sudo rules a privileged leaver could keep after their badge stops working. Open it at: Linux desktop → Start menu → Persistence Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "He is still employed and still has privileged access. What do you do with it?".

  2. 2He is still employed and still has privileged access. What do you do with it?
    Decision
    00:20 → 01:10

    Cutting access tips him off and may prejudice an employment process. Leaving it lets him keep working — and keep copying.

    Leads: CISO · Done when: CISO picks one of 3 options before 01:10. Letting it lapse is scored as a choice.

  3. 3Kernel Module Lab
    Hands-on
    00:30 → 02:00

    Stage, load and then detect the hiding module on the research host: compare /proc/modules against sysfs, read the taint flags and the kernel ring buffer, then unload it — after the image is taken. Open it at: Linux desktop → Start menu → Kernel Module Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The hiding module is loaded on a production research host. Remove it now?".

  4. 4Privilege Escalation
    Hands-on
    00:30 → 02:00

    Reproduce how the leaver kept root on the research host — the writable unit behind a sudo rule — then close the hole and restart the service so the fix is proven. Open it at: Linux desktop → Start menu → Privilege Escalation.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The hiding module is loaded on a production research host. Remove it now?".

  5. 5Remove privileged access before the next shift
    Obligation
    00:40 → 01:10

    He is rostered on-call tonight with full cluster rights.

    Leads: CISO · Done when: A decision that satisfies it is made before 01:10.

  6. 6The hiding module is loaded on a production research host. Remove it now?
    Decision
    01:00 → 02:00

    Unloading restores visibility but changes the host. Volatile state is the proof that it was hiding anything.

    Leads: CISO · Done when: CISO picks one of 3 options before 02:00. Letting it lapse is scored as a choice.

  7. 7Forge Chef: decrypt the chain
    Hands-on
    01:10 → 02:45

    Unwrap the masked dmesg line, the leaver's bastion transcript and the sudoers grant behind them. The bucket the assay data landed in is what the partner-contract call turns on. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "How do you pursue the data itself?".

  8. 8DFIR Tools Lab
    Hands-on
    01:10 → 02:45

    Image the administrator's workstation and the research host, then carve deleted archives to establish what left and when. Open it at: Linux desktop → Start menu → DFIR Tools Lab.

    Leads: CISO · Done when: Findings are posted to the room in time to answer "How do you pursue the data itself?".

  9. 9Capture volatile evidence before the host changes
    Obligation
    01:30 → 02:00

    Memory and module state disappear on the next reboot.

    Leads: CISO · Done when: A decision that satisfies it is made before 02:00.

  10. 10How do you pursue the data itself?
    Decision
    01:40 → 02:45

    41 GB on removable media, a named future employer and an employee still inside his notice period.

    Leads: General Counsel · Done when: General Counsel picks one of 3 options before 02:45. Letting it lapse is scored as a choice.

  11. 11Shared break-glass keys include one he generated. Rotate?
    Decision
    02:30 → 03:30

    Rotation needs a maintenance window across the research cluster mid-program.

    Leads: Operations · Done when: Operations picks one of 3 options before 03:30. Letting it lapse is scored as a choice.

  12. 12The research partner is invoking the 48-hour data-incident clause.
    Decision
    03:05 → 04:05

    Jointly owned assay data, milestone payments and an audit right in the agreement.

    Leads: General Counsel · Done when: General Counsel picks one of 3 options before 04:05. Letting it lapse is scored as a choice.

  13. 13Partner notice within the 48-hour clause
    Obligation
    03:35 → 04:05

    Jointly owned data means the alliance agreement clock runs too.

    Leads: General Counsel · Done when: A decision that satisfies it is made before 04:05.

  14. 14The newsletter is going to run the rumor. What do staff and the market hear?
    Decision
    03:45 → 04:45

    Naming an individual before any finding creates its own liability. Saying nothing invites the worst reading.

    Leads: Communications · Done when: Communications picks one of 3 options before 04:45. Letting it lapse is scored as a choice.

Manufacturing
3h exercise
4 decisions
2 clocks

Your payroll provider was breached

A third party holding your employee data is compromised. You own the obligation, they own the facts, and they are not answering.

Seats: CISO, General Counsel, Communications, Privacy Officer, Chief Financial Officer, Operations

Hands-on track: Forge Chef: decrypt the chain

See the step-by-step path (7 steps)
  1. 1Forge Chef: decrypt the chain
    Hands-on
    00:00 → 00:55

    Decode the provider advisory, the SFTP export log and the actor's sample schema. The column names you recover decide whether this is notifiable and who the controller is. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "The provider will not confirm scope. What do you do first?".

  2. 2The provider will not confirm scope. What do you do first?
    Decision
    00:10 → 00:55

    You have no visibility into their environment and no confirmed impact on your data.

    Leads: CISO · Done when: CISO picks one of 3 options before 00:55. Letting it lapse is scored as a choice.

  3. 3Employees have seen the leaked sample. What do they hear from you?
    Decision
    01:05 → 02:00

    The works council is asking, and the sample includes real Meridian rows.

    Leads: Communications · Done when: Communications picks one of 2 options before 02:00. Letting it lapse is scored as a choice.

  4. 4Tell affected employees
    Obligation
    01:30 → 02:00

    High risk to individuals means telling them, not just the regulator.

    Leads: Communications · Done when: A decision that satisfies it is made before 02:00.

  5. 5You are the controller. Do you notify?
    Decision
    01:45 → 02:45

    Scope is partial: you know the sample is real, you do not know the full record count.

    Leads: Privacy Officer · Done when: Privacy Officer picks one of 2 options before 02:45. Letting it lapse is scored as a choice.

  6. 6Payroll runs in four days on a platform you no longer trust.
    Decision
    02:00 → 02:55

    Bank details in the platform may have been altered as well as read.

    Leads: Chief Financial Officer · Done when: Chief Financial Officer picks one of 2 options before 02:55. Letting it lapse is scored as a choice.

  7. 7Controller notification to the authority
    Obligation
    02:15 → 02:45

    The duty is yours regardless of whose systems failed.

    Leads: Privacy Officer · Done when: A decision that satisfies it is made before 02:45.

Financial technology
3h exercise
4 decisions
2 clocks

Is it material?

A listed company, an intrusion of uncertain scope, and a four-business-day disclosure clock that starts the moment you decide it matters.

Seats: Chief Executive, Chief Financial Officer, General Counsel, CISO, Communications

Hands-on track: Forge Chef: decrypt the chain

See the step-by-step path (7 steps)
  1. 1Who owns the materiality determination, and when is it made?
    Decision
    00:15 → 01:10

    The clock starts at determination, and 'we never got round to determining' is itself a finding.

    Leads: General Counsel · Done when: General Counsel picks one of 3 options before 01:10. Letting it lapse is scored as a choice.

  2. 2Materiality determination without unreasonable delay
    Obligation
    00:40 → 01:10

    The filing clock starts here, so the determination itself must be prompt.

    Leads: General Counsel · Done when: A decision that satisfies it is made before 01:10.

  3. 3An analyst is asking before the open. Response?
    Decision
    01:00 → 01:55

    Selective disclosure to one analyst is its own violation.

    Leads: Communications · Done when: Communications picks one of 2 options before 01:55. Letting it lapse is scored as a choice.

  4. 4Forge Chef: decrypt the chain
    Hands-on
    01:25 → 03:00

    Decode the query the intruder ran, the RMM launcher and the persistence service. What data was actually read is the evidence behind the materiality determination. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Forensics says client transaction volumes were queried. Material?".

  5. 5Forensics says client transaction volumes were queried. Material?
    Decision
    01:55 → 03:00

    No financial loss, no manipulation — but competitively sensitive client data and an 11-day dwell time.

    Leads: Chief Financial Officer · Done when: Chief Financial Officer picks one of 3 options before 03:00. Letting it lapse is scored as a choice.

  6. 6File within the disclosure window
    Obligation
    02:30 → 03:00

    Four business days from determination, modeled as the exercise window.

    Leads: Chief Financial Officer · Done when: A decision that satisfies it is made before 03:00.

  7. 7What goes to the board and to employees?
    Decision
    02:30 → 03:15

    Everything written is discoverable. Employees are reading the wire story.

    Leads: Chief Executive · Done when: Chief Executive picks one of 2 options before 03:15. Letting it lapse is scored as a choice.

Logistics
1h exercise
5 decisions
1 clocks

Meridian Freight — Keep Freight Moving (capstone)

A gateway advisory, a suspicious analyst report and a dispatch deadline. Coordinate proportionate containment, protect evidence, tell customers only what you can support and set recovery criteria — in 35 minutes.

Seats: Chief Executive, CISO, Operations, Communications, General Counsel, Chief Financial Officer

Hands-on track: Meridian responder lab: trace the gateway intrusion, Forge Chef: decrypt the chain, Persistence Lab, DFIR Tools Lab, DFIR Artifact Lab, Firewall Lab, TCP Lab, Remote Desktop Lab

See the step-by-step path (14 steps)
  1. 1Customer contract notice (exercise clause)
    Obligation
    00:00 → 00:30

    Supplied fictional clause: decide and route notice once a data impact is reasonably suspected.

    Leads: Communications · Done when: A decision that satisfies it is made before 00:30.

  2. 2Forge Chef: decrypt the chain
    Hands-on
    from 00:00

    Unwrap this breach's own artifacts: the appliance exploit request, the encoded scheduled task on the file server and the exfil manifest. The destination host you recover is what the customer notification names. Open it at: Windows desktop → Forge Chef (launches the graded campaign).

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  3. 3DFIR Artifact Lab
    Hands-on
    from 00:00

    Investigate the file server the scheduled task landed on: detonate the sample in isolation, image the disk and carve the artifacts that prove what ran before the rebuild. Open it at: Windows desktop → Start menu → DFIR Artifact Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  4. 4DFIR Tools Lab
    Hands-on
    from 00:00

    Image the appliance with dd, walk the partitions with mmls/fls and carve deleted files with foremost before anyone rebuilds it. Open it at: Linux desktop → Start menu → DFIR Tools Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  5. 5Firewall Lab
    Hands-on
    from 00:00

    Contain the exfil path at the network edge: add the drop rule for the upload destination, prove it blocks with a test connection, and leave legitimate traffic untouched. Open it at: Windows desktop → Start menu → Firewall Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  6. 6Persistence Lab
    Hands-on
    from 00:00

    Find and grade every foothold the intruder left: cron entries, systemd timers, rogue accounts and loaded modules. The count you report drives the rebuild scope. Open it at: Linux desktop → Start menu → Persistence Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  7. 7Remote Desktop Lab
    Hands-on
    from 00:00

    Prove Network Level Authentication is enforced on the file server: show where a non-NLA client and a wrong password each fail. Open it at: Windows desktop → Start menu → Remote Desktop Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  8. 8Meridian responder lab: trace the gateway intrusion
    Hands-on
    00:00 → 00:15

    Work Meridian's own network: confirm the gateway bypass and web shell, follow the service account to the domain controller and file server, state your confidence about the manifests archive, and name the restore point that is safe to recover from. Open it at: Windows analyst desk MF-SOC-01 → SIEM (launches the graded lab).

    Leads: CISO · Done when: Findings are posted to the room in time to answer "Remote access may be actively abused. Taking the whole gateway offline will disrupt dispatch. What do you authorize, on what evidence, and what would change your mind?".

  9. 9TCP Lab
    Hands-on
    from 00:00

    Read the SMB session to the file server off the wire: port, retransmissions, the real scaled window and who closed the connection. Open it at: Windows or Linux desktop → Start menu → TCP Lab.

    Leads: CISO · Done when: The lab is graded and its findings are posted to the room.

  10. 10First coordination call: who owns what, and when is the next update?
    Decision
    00:06 → 00:10

    You have an advisory, a suspicious event and a dependency on the gateway. Little is confirmed.

    Leads: Chief Executive · Done when: Chief Executive picks one of 3 options before 00:10. Letting it lapse is scored as a choice.

  11. 11Remote access may be actively abused. Taking the whole gateway offline will disrupt dispatch. What do you authorize, on what evidence, and what would change your mind?
    Decision
    00:11 → 00:15

    Options from I04. Preservation status depends on your first call.

    Leads: Chief Executive · Done when: Chief Executive picks one of 3 options before 00:15. Letting it lapse is scored as a choice.

  12. 12Preserve or rebuild first?
    Decision
    00:20 → 00:24

    Rebuilding the gateway fast restores confidence; it also destroys what the image hasn't captured.

    Leads: CISO · Done when: CISO picks one of 2 options before 00:24. Letting it lapse is scored as a choice.

  13. 13Approve a holding statement: confirmed facts, concern, action, next update.
    Decision
    00:25 → 00:29

    The screenshot is unverified. Staging is moderate-confidence; transfer is low-confidence.

    Leads: Communications · Done when: Communications picks one of 3 options before 00:29. Letting it lapse is scored as a choice.

  14. 14Staged recovery or continued containment?
    Decision
    00:32 → 00:35

    One recovery point passes checks; others aren't validated. The service owner hasn't accepted anything yet.

    Leads: Operations · Done when: Operations picks one of 3 options before 00:35. Letting it lapse is scored as a choice.