Skip to the content ForoHackers
Log inJoin

Incident response: start here

Incident response
#3305 · · Quote · Report

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

  1. Logging and monitoring basics: what you can see on a typical server and network.
  2. Write an incident response plan for a small imaginary company: roles, contacts, severity levels.
  3. Run a tabletop exercise with a friend from a short scenario and record the decisions.
  4. Practise on your own lab: collect volatile data, isolate a machine, and restore from backup.
  5. Write a blameless post-mortem with a timeline, root cause and a list of fixes with owners.

Related tags

#soc #forensics #blue-team #backups #sre

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply