Incident response is how an organisation handles a security breach or suspected one: confirming it, limiting the damage, removing the cause, restoring service and learning from it. What separates a calm response from chaos is preparation: roles, contacts, tools and rehearsal decided long before the bad day.
Key concepts
- Phases: prepare, detect and analyse, contain, eradicate and recover, then review what happened.
- Containment: stop the spread, for example by isolating a host or disabling an account, while preserving evidence.
- Scoping: find out which systems, accounts and data are affected before declaring it over.
- Communication: clear, timely and accurate updates to staff, customers and authorities, as obligations differ by country.
- Blameless review: the post-incident report fixes processes and defences rather than hunting for a culprit.
Vocabulary
- Runbook: a written procedure for a known type of incident.
- Triage: deciding what matters most and what to do first.
- Eradication: removing the attacker's access and the root cause.
- Post-mortem: the review held after an incident.
What to study, in order
- Logging and monitoring basics: what you can see on a typical server and network.
- Write an incident response plan for a small imaginary company: roles, contacts, severity levels.
- Run a tabletop exercise with a friend from a short scenario and record the decisions.
- Practise on your own lab: collect volatile data, isolate a machine, and restore from backup.
- Write a blameless post-mortem with a timeline, root cause and a list of fixes with owners.