incident response
The organised work of detecting, analysing, containing, removing and recovering from a security incident, then learning from it.
In more detail
NIST SP 800-61 describes incident response as preparation, detection and analysis, containment, eradication and recovery, and post-incident activity. SOCs number cases with an IR prefix, such as IR-62. Responders work from playbooks and runbooks under a named incident lead.
Related terms
- security incident — An event that actually or potentially harms the confidentiality, integrity or availability of systems or data, or that breaks security policy.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
- escalation policy — A written rule for who is told about a problem, in what order and how quickly, when the person first responsible cannot or does not act.
- runbook — A written, step-by-step procedure for a routine operation or for responding to a known kind of incident.
- incident — An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
- NIST SP 800-61 — NIST's guide to incident response; its well-known lifecycle runs preparation, detection and analysis, containment eradication and recovery, and post-incident activity.
- containment — Stopping an incident from spreading or doing more damage, for example by isolating a host, blocking an address or disabling an account.
- eradication — The incident response step that removes every trace of the attacker: malware, accounts, keys, tasks and other footholds.
- recovery — Returning systems to normal, trusted operation after an incident: restoring from clean backups, rebuilding hosts and watching them closely.
- audit trail — A record of who did what and when, kept so actions can be reviewed and investigated later.
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
- SBOM — A list of every software package and version inside an image, like an ingredients label.
Taught in
- Security Governance vs Security Management — Cybersecurity Fundamentals, GRC & Cryptography
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Detecting Persistence: Tasks, Registry & Services — Security Operations & Threat Hunting (SOC)
- NIST SP 800-61 Incident Lifecycle & Management — Security Operations & Threat Hunting (SOC)
- Incident Triage, Severity Scoping & Communication — Security Operations & Threat Hunting (SOC)
- Containment & Eradication: Host, Net & Identity — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)
- Forensics Principles, Custody & Imaging — Security Operations & Threat Hunting (SOC)
- Moving To A Secret Manager — Application Security & Threat Modeling for Engineers
- Software Bill Of Materials — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers