24/7 incident line +1-555-0187[email protected]

Report WL-0436. Public sector. Contained in 39 minutes.
Public copy, names removed

A city's records, back from a clean restore

§1 Report sheetWL-0436 / Sample report

City data room with an engineer restoring systems at a rack console
Time to contain
39 min
First alert 03:26, contained 04:05

Report sheet

Sector

Public sector, city records service

Scope

900 accounts, 2 file servers, one records service

Findings by severity

2 Critical  2 High  4 Low

Time to contain

39 minutes

Result

Records back in 31 hours from a clean copy

The backup was fine. The restore was the test.

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

§2.1 What happened

At 03:26 thousands of files on a records server at department name removed began to change name. Ransomware was running under an admin account that had been used on a shared desktop.

§2.2 What we did

The night analyst confirmed encryption, called the city IT duty officer at 03:41 and isolated the server with his approval at 03:47. The admin account was disabled at 03:55, and the second file server was found clean.

§2.3 What it means

The city did not pay. Records were rebuilt from an offline copy on a clean network and were back 31 hours after the first alert. The report went to job title removed at 09:00 the same morning.

§3 TimelineWL-0436 / Sample report

Thirty-nine minutes, line by line.

Copied from the incident log. Times are local to the city.

Time

Event

By

Elapsed

03:26

Mass file renames on a records server

Sensor

0 min

03:28

Alert assigned to night analyst

Queue

2 min

03:34

Encryption confirmed on one share

Analyst

8 min

03:41

City IT duty officer called

Analyst

15 min

03:47

Approval given, records server isolated

Client

21 min

03:55

Admin account disabled

Analyst

29 min

03:58

Second file server checked, clean

Analyst

32 min

04:05

Contained. Handover note sent.

Analyst

39 min

After containment

Day 1

Report delivered at 09:00, walked through with the city at 11:30

Lead

6 hr

Day 2

Records restored from the offline copy, clean network

Client IT

31 hr

Day 7

Admin accounts split from daily accounts

Client IT

Closed

Day 21

Quarterly restore test added to the runbook

Client IT

Closed

§4 FindingsWL-0436 / Sample report

Eight findings. Four shown in full.

Severity

Finding

Status

Critical

Ransomware on a records file server

Day 2

Critical

Admin account used on a shared desktop

Day 7

High

Restore never tested end to end

Day 21

High

File server open to all staff subnets

Day 14

Low

finding removed

Closed

Low

finding removed

Closed

Four Low findings are kept in the client's copy. Two shown as removed.
Rack-mounted backup appliance with rows of drive lights, one lit amber
Findings, sample client

Critical

2

High

2

Low

4

§5 Client noteWL-0436 / Sample report

I had the phone call at 3:41 and a plain list of what was happening. By the second morning the counter was open again.

Head of records, city government (fictional client)
What changed

Offline copy, tested every quarter

Admin accounts kept apart from daily ones

File servers closed to staff subnets

§6 More reportsEnd of WL-0436