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

Why we rebuild the timeline before we touch a host

Responders at a steel table beside a server rack, one standing at a wall display showing an attack path graph

Two events an hour apart can mean a stolen account. An average on a dashboard hides that gap. So before anyone cleans a machine, we put every event we have on one line, in order, with its source beside it.

Cleaning first feels responsible, and it destroys the answer. A wiped host cannot tell you how the attacker arrived, and the client will be asked that question by a lawyer, an insurer or a board.

What goes on the line

  • Sign-ins, with the address and the device.
  • Process starts on the hosts we can reach.
  • Mail rules and permission changes.
  • What people remember, marked as memory.

Every host on the attack path gets a name and a time.

Containing without losing it

Containment does not wait for the timeline. We isolate from the network and leave the host running where we can, so memory survives. Then we copy and hash before anyone looks inside.

In the freight carrier case, WL-26-114, the first draft of the line took a day. It showed nineteen days of access in a place nobody had thought to look, and it changed what the client fixed first.

About the author

Tomas built the evidence log and reads a disk the way other people read a diary. Fictional author, demo content.

Related field notes