Field Report No. 41, November 2026Incident response and threat research24/7 line +1-555-0187

Report WL-26-098 · Ransomware · Contained in 3 h 40 min
Public copy, names removed

Stopped on the backup host before encryption

Responder pulling a drive tray from a disk shelf in a backup room, a laptop on a steel cart beside her
Time to contain
3 h 40 min
First call 22:17, contained 01:57
Report sheet WL-26-098
Sample

Sector

Healthcare group, 3 hospitals

Scope

3 hospitals, 900 hosts

Findings

Critical 1 · High 3 · Low 8

Result

Stopped before encryption

§2 Summary

A quiet week on a backup host. Then a phone call.

Written for the client's board. Names, sites and hostnames are removed from this copy.

§2.1 What happened

A healthcare group's night IT lead saw a backup job fail on a host at site withheld and found tools nobody had installed. The crew had spent a week preparing, and the backup host was where they meant to start.

§2.2 What we did

We isolated the host with its power left on and revoked the account behind the tools. Then we checked the other hosts it had reached, one hospital at a time, before anyone went home.

§2.3 What it means

Nothing was encrypted and clinical systems kept running. The backups were sound. The decision on who to notify stayed with the group and its counsel, and they had our facts to work from.

§3 Timeline
WL-26-098, sample report

Three hours forty minutes, line by line.

Copied from the case record. Times are local to the hospitals.

Time

Event

By

Elapsed

22:17

Client calls the 24/7 line

Client

0 min

22:30

Lead named, scope agreed

Lead

13 min

22:58

Unknown tools confirmed on the backup host

Analyst

41 min

23:24

Client approves isolating the host

Client

1 h 07 min

23:31

Backup host off the network, power left on

Lead

1 h 14 min

00:12

Account behind the tools revoked

Lead

1 h 55 min

01:05

Memory capture logged

Forensics

2 h 48 min

01:57

Contained. Other hosts checked, nothing encrypted.

Lead

3 h 40 min

After containment

Day 2

Week of staging rebuilt from the logs

Analyst

Closed

Day 7

Report delivered, lead signs the last page

Lead

Closed

Day 14

Backup hosts moved to their own network

Client IT

Closed

Day 30

Closing review with leadership

Lead

Closed

§4 Findings

Twelve findings. Four shown in full.

Severity

Finding

Status

Critical

Backup host reachable with an everyday admin account

Day 14

High

No alert on new tools on servers

Day 10

High

Admin sign-ins allowed from any desktop

Day 21

High

Backup copies not held offline

Day 30

Low

finding withheld

Closed

Low

finding withheld

Closed

Eight Low findings are kept in the client's copy. Two shown as removed.
Hands labelling a sealed emergency access kit with two hardware security keys on a steel bench beside a dark laptop
Findings
Sample

Critical

1

High

3

Low

8

§5 Client note
WL-26-098, sample report

The backup job failed at ten at night. By two in the morning I knew what they had touched and what they had not.

Head of IT, healthcare group (fictional client)
What changed

Backup hosts on their own network

A separate admin account for backups

One offline copy, tested each quarter

§6 More reports
End of WL-26-098