Being writtenOperations & response

Incident response for small teams

What to do in the first hour when there is no security team to escalate to.

LevelPractitioner
Material3 modules, 10 lessons
Reading time1 h 50 m
StatusBeing written — not open

This course is not available yet

It is being written. The outline below is what it will cover, and it is unlikely to change much. There is no enrolment and no date — when it is ready it will be on this page. Several of the lessons are built around tools on this site that already work, so you can practise the measurements today.

If you need this capability now rather than later, Incident response is the service that covers it, or talk to us.

Who it is for

IT staff at organisations without a security function, who will be the incident response team whether or not anyone has said so.

Practitioner. For people who administer these systems day to day.

No prerequisites. Nothing is assumed beyond using a computer at work.

What you will be able to do

  • Decide whether what you are looking at is an incident, and say why
  • Contain a compromised account or endpoint without destroying the evidence
  • Preserve the logs and artefacts an investigation will need, before they age out
  • Run a communication line to management that does not require a second incident
  • Write up what happened in a form that changes something

Outline

3 modules, 10 lessons, 1 h 50 m of material. The times are the sum of the lessons rather than a round figure.

01Before anything happens

The preparation that takes an afternoon and saves the week.

The contact list, offline8 m

Who to call, including the people whose systems you do not run — and a copy that survives the incident.

Knowing what logs you keep12 m

Retention windows, and discovering them now rather than on the day.

What "contained" will mean10 m

Deciding the thresholds in advance, when nobody is shouting.

02The first hour

Ordered so that the irreversible steps come after the reversible ones.

Is this an incident?10 m

Triage, and the bias towards treating it as one.

Containing an account compromise14 m

Sessions, tokens, mail rules, and why a password reset alone is not containment.

Containing an endpoint12 m

Isolating rather than wiping, and what is lost by rebuilding too early.

Preserving evidence12 m

What to collect before it rotates, and how not to contaminate it.

03Afterwards

The part that is skipped, and the only part that changes the next one.

Reporting to management10 m

What they need, when, and in how much detail.

Notification obligations12 m

Where the duty to notify comes from, and why legal advice belongs early.

The write-up that changes something10 m

Timeline, cause, and two or three changes that are actually going to happen.

Format. Written lessons built around a worked scenario followed from alert to write-up. Delivery mechanism is not built yet.

Practise it now, free

These tools run the same checks the course teaches, and they work today. No account, and the ones marked as running in your browser send nothing anywhere.

Would you rather we just did it?

This course exists because the work behind it is work we do. If you need the result rather than the skill, incident response is the service that covers it.