containment
Stopping an incident from spreading or doing more damage, for example by isolating a host, blocking an address or disabling an account.
In more detail
Short-term containment isolates, blocks and disables; long-term containment keeps a system running under watch while a fix is prepared. Choose by weighing damage, evidence, availability, effort, effect and duration. Contained means the last known foothold is cut off, not the first.
Related terms
- eradication — The incident response step that removes every trace of the attacker: malware, accounts, keys, tasks and other footholds.
- host isolation — Cutting a compromised machine off from the network, except for the responders' tools, so the attacker cannot use it or spread from it.
- session revocation — Invalidating a user's existing sessions and tokens so every device and attacker holding them must sign in again.
- mean time to contain — The average time between detecting an incident and stopping the attacker from spreading further.
Taught in
- SOC Operating Models, Tiers & Key Performance Metrics — Security Operations & Threat Hunting (SOC)
- SIEM Architecture: Ingestion Pipelines & Indexing — Security Operations & Threat Hunting (SOC)
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Detection as Code: Authoring & Testing Sigma Rules — Security Operations & Threat Hunting (SOC)
- Windows Event Logs, Sysmon & Linux Auditd Telemetry — Security Operations & Threat Hunting (SOC)
- YARA Rule Authoring & File Signature Matching — 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)
- Containment & Eradication: Host, Net & Identity — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)