HackBlue

Tools · Incident response playbooks · 24 / 27

The incident id is not the hostname

The incident id names the case. A hostname names a machine. Write both, and do not swap them.

9 min read · practice only with authorization

The id names the case record

The incident id is the key the case system uses for this ticket. IR-2026-014 points at the record. It is not a computer, and it will not resolve as a host.

Two notes can share a hostname and still belong to different ids. The id is how you keep those notes from merging.

A hostname is a machine in a note

A hostname appears when someone writes which machine a line is about. lab-web-02 is that machine. It does not name the case, and it does not mean every line in the case is about that machine.

If the host field is empty, write that no host was named. Do not paste the incident id into the blank.

Labels that stay apart

File the incident id and each hostname with those labels. A search for the case uses the id. A search for the machine uses the hostname. Using one string for both returns the wrong pile.

Lab: a case id filed as the host

Ticket IR-2026-014 mentions host lab-web-02 in one note. A draft puts IR-2026-014 in the host column and drops lab-web-02.

The note keeps IR-2026-014 as the case and lab-web-02 as the host. The host column does not contain the case id. No second host is invented.

Snippet
incident id: IR-2026-014
host: lab-web-02
write: case and machine
not: host IR-2026-014

Diagram

The case key and a machine name

They answer different searches.

Incident id

Is. The case record

Example. IR-2026-014

Is not. A hostname

Hostname

Is. A machine named in a note

Example. lab-web-02

Missing. Say no host was named

Check yourself

1. A ticket is IR-2026-014 and a note names lab-web-02. What is IR-2026-014?

2. Which value belongs in the host column?

3. No host is written on the ticket. What do you put in the host field?