Resources

Detection packs & triage sheets

Things to deploy and things to print. Everything here carries a date and a version, because a detection rule with no date on it cannot be tuned: you cannot tell whether the false positives you are seeing were budgeted for or arrived with a product update.

Deployable rule packs

Sigma, YARA and Snort, published as dated packs. Every rule ships with its false-positive notes, because a rule deployed without them is a rule that gets switched off in a fortnight.

One-page triage sheets

Built for a printer and for somebody who is standing up. These are pages rather than PDF binaries on purpose: when an event ID moves on a new build, a PDF on a desk stays wrong forever and a page can be corrected.

PDF • 1-PAGE A4 • PRINT-READY

Active Directory Compromise Triage

You have credible reason to believe a domain account has been compromised, or that someone has domain-level access they should not have.

  1. 1.Establish scope, before you change anything
  2. 2.Collect, in this order
  3. 3.Containment that does not tip off the operator
  4. 4.The two resets, in order

Updated 2026-09-01

PDF • 1-PAGE A4 • PRINT-READY

Windows Host Triage, First 60 Minutes

One Windows host is suspect. You have access, and you do not yet know whether it is compromised, what it ran, or whether anything is still live on it.

  1. 1.Volatile first, in this order
  2. 2.Execution evidence
  3. 3.Persistence, the five that cover most of it
  4. 4.Logs worth pulling before they roll

Updated 2026-09-01

PDF • 1-PAGE A4 • PRINT-READY

Ransomware, First Hour

Files are encrypting now, or encryption has stopped and you do not yet know whether the operator is still in the estate.

  1. 1.Stop the spread, without destroying evidence
  2. 2.Capture while it is still there
  3. 3.Find the entry, it is usually one of these
  4. 4.Before anyone says the word "restore"

Updated 2026-09-01

PDF • 1-PAGE A4 • PRINT-READY

Linux Host Triage, First 60 Minutes

A Linux server is behaving oddly, has been flagged by a detection, or turned up in somebody else’s incident as a destination.

  1. 1.Volatile first, in this order
  2. 2.Persistence, the places that are actually used
  3. 3.Accounts and access
  4. 4.Filesystem, where the noise is lowest

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

Microsoft 365 Account Compromise Triage

A sign-in you cannot account for, an inbox rule nobody created, or a user reporting that a colleague is sending them things the colleague did not send.

  1. 1.Contain, in this order
  2. 2.Scope, before the logs roll
  3. 3.Spread
  4. 4.Before you close it

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

The Retention Clock: What Expires, and When

An incident with a start date more than a fortnight ago, and a decision about what to export right now before it stops existing.

  1. 1.Cloud identity and productivity, typical defaults
  2. 2.On the endpoint, where the clock is fastest
  3. 3.Network, usually the thinnest
  4. 4.The order to export in

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

Memory: Acquire It Before It Is Gone

A host you suspect is compromised is still running, and somebody is about to be helpful and reboot it.

  1. 1.Before you touch the keyboard
  2. 2.Acquire
  3. 3.Alongside memory, in the same window
  4. 4.First pass, once you have the image

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

macOS Host Triage, First 60 Minutes

A Mac has been flagged, or turned up in an incident, and most of your Windows instincts do not transfer.

  1. 1.Live state
  2. 2.Persistence, in the order operators actually use
  3. 3.Accounts and access
  4. 4.What to collect before you leave

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

Evidence Handling and Chain of Custody

You are collecting something that may end up in an employment matter, an insurance claim, a regulatory response or a court.

  1. 1.Record at the moment of collection
  2. 2.Every time it changes hands
  3. 3.Working practice
  4. 4.The questions you will be asked

Updated 2026-09-12

PDF • 1-PAGE A4 • PRINT-READY

AWS Account Compromise Triage

Credentials you did not issue, resources nobody created, or a provider notice that a key of yours is public.

  1. 1.Contain, in this order
  2. 2.Scope
  3. 3.The things that are easy to miss
  4. 4.Before you close it

Updated 2026-09-12