Saltar al contenido ForoHackers

Incident response: start here

Respuesta a incidentes
#3305 · · Citar · Denunciar

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

No has iniciado sesión, así que esto se publica como anónimo: no se guarda con ello ninguna cuenta, nombre ni dirección, y no puede llevar enlaces ni imágenes. Inicia sesión o únete para publicar con tu nombre. Los registros de nuestro servidor web guardan la dirección y la hora de cada petición hasta 14 días; para que la tuya no quede en ellos, usa Tor. Para escribir al equipo de forma confidencial, usa el buzón. Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder