Field Report No. 41, November 2026Incident response and threat research24/7 line +1-555-0187
Field responder pushing a steel cart with an open laptop down a dark data hall aisle while a colleague works at an open rack
§1 How we work

What happens after you call.

One lead, one written record and a report on day 7. This page shows each step, including what we ask of you.

1

lead, from first note to last page

1

written record, kept as decisions are made

0

original disks worked on, only verified copies

Day 7

report in your hands, typical sample case

§2 Engagement steps

Six steps, with both sides written down.

§2.1

The call

Minute one

We answer, ask when you first noticed and open the record.

You tell us who holds the network keys.

§2.2

Triage

First hour

We agree the scope and name your lead responder.

You name one person who can make decisions.

§2.3

Contain

Same day

We stop the spread and copy and hash the evidence first.

You approve each change before it runs.

Responders round laptops at a steel table in a room of racks, an attack path graph on the wall
Incident room, day 3
We rebuild the timeline before we touch a host, so a fix does not erase the trail.
§2.4

Investigate

Days 2–5

We rebuild the timeline from logs, disks and people.

You give us the logs and an hour with the staff involved.

§2.5

Report

Day 7

We deliver findings by severity, what changed and what comes next.

You read the draft and correct any facts.

§2.6

Review

Day 30

We check the fixes against the report and close the case.

You bring whoever owns the fixes.

§3 First 30 days
30

days, and then the case closes.

A report is not the end. The plan runs until someone has checked that the fixes work.

Day 1

Spread stopped. Daily written note begins.

Day 3

First written summary for your lawyer or insurer.

Day 7

Report delivered, findings ranked by severity.

Day 10

Readout with your IT team and leadership.

Day 14

Critical and High fixes checked.

Day 21

New detections handed to your IT team.

Day 30

Review held. Remaining Low findings listed. Case closed.

Sample plan for this demo. Dates move with the size of the case.
WL-26-114, page 3
Demo sample

Timeline of the intrusion

Day 0, 02:14

Login on stale VPN account user withheld

Day 6, 03:40

Admin password taken from host withheld

Day 11, 22:51

Movement to depot file server

Day 17, 23:05

Archive staged, size withheld of shipping records

Day 19, 10:26

Client calls the 24/7 line

Day 19, 14:38

Contained, 4 h 12 min

§4 Deliverables

Five things you keep.

Each one is written for the person who has to use it, and all five belong to you when the case closes.

Deliverable

Who reads it

When

Written record

Your lead and legal counsel

Daily

Evidence log

Lawyer, insurer

Day 7

Case report

Leadership, IT team

Day 7

Fix list by severity

Whoever owns the fixes

Day 7

Closing review

Leadership, board

Day 30

§5 Next step

Read a report before you need one.

Ask for a sample with the names taken out and judge the work for yourself. If it is happening now, call +1-555-0187.

Lead responder standing beside a wall display in a response room, terminals behind him