# Incident response

> The rehearsed plan an organization follows when a security attack actually happens.

- Level: Intermediate
- Topics: Security
- URL: https://tidbit.legios.com.ar/incident-response/
- In Spanish: [Respuesta a incidentes](https://tidbit.legios.com.ar/es/incident-response/)

**Incident response** is what a company does from the moment it suspects a security incident (ransomware on a laptop, a stolen password used at 3 a.m., customer data showing up for sale) until things are back to normal and the lesson is written down. The key word is plan: who gets called, who can shut down a server, who talks to lawyers, customers and the press. Deciding that in the middle of the crisis is how small incidents become big ones.

The classic guide is NIST SP 800-61, which describes a cycle. Preparation: contacts, tools, backups and practice drills before anything happens. Detection and analysis: alerts from a SIEM or an EDR, and figuring out what really happened and how far it spread. Containment, eradication and recovery: isolating infected machines, resetting credentials, removing the attacker's foothold and restoring clean systems. Post-incident activity: a postmortem that feeds back into preparation. The 2025 revision of the guide ties this cycle to NIST's broader Cybersecurity Framework 2.0.

Large organizations keep a dedicated team, often called a CSIRT, usually working alongside the security operations center; smaller ones hire an outside firm on retainer, sometimes through their cyber insurance. Two details matter more than people expect: evidence (logs and disk images) must be preserved before systems are wiped, and laws set deadlines. Under the GDPR, for example, a personal data breach generally has to be reported to the authority within 72 hours of becoming aware of it.

## An analogy

A fire drill for computers. Everyone knows where the extinguishers are, who calls the firefighters and which door to use, so when the alarm goes off nobody wastes the first ten minutes arguing.

## Keep in mind

- The plan is written and rehearsed before any attack.
- Typical phases: prepare, detect, contain and recover, learn.
- Preserve logs and evidence before wiping anything.
- Laws like the GDPR set deadlines for reporting breaches.

## Go deeper

- [NIST SP 800-61 Rev. 3: Incident Response Recommendations](https://csrc.nist.gov/pubs/sp/800/61/r3/final)
- [Incident management (UK National Cyber Security Centre)](https://www.ncsc.gov.uk/collection/incident-management)
- [Computer security incident management on Wikipedia](https://en.wikipedia.org/wiki/Computer_security_incident_management)

## Related terms

- [Malware and ransomware](https://tidbit.legios.com.ar/malware-and-ransomware/): Software built to harm you; ransomware locks your files and charges to unlock them.
- [Laptop](https://tidbit.legios.com.ar/laptop/): A whole computer folded into one portable case that runs on a battery.
- [Server](https://tidbit.legios.com.ar/server/): A computer whose job is to answer requests from other computers, all day, every day.
- [Backup](https://tidbit.legios.com.ar/backup/): A separate copy of your data, kept so you can get it back when the original is lost.
- [SIEM](https://tidbit.legios.com.ar/siem/): The system that gathers security logs from everywhere and raises the alarm.
- [EDR](https://tidbit.legios.com.ar/edr/): Security software that watches what each computer does and reacts to signs of attack.
- [Incident postmortem](https://tidbit.legios.com.ar/incident-postmortem/): A written review of what went wrong in an outage and how to avoid a repeat.
- [Cybersecurity](https://tidbit.legios.com.ar/cybersecurity/): Protecting computers, networks and data from theft, damage and disruption.
