Theory · 9 min · Incident response basics
Contain without destroying evidence
Choose a containment step that stops the harm and keeps the evidence.
Containment stops the damage from growing: isolate a host from the network, revoke sessions, disable an account, block an indicator. Each has a business cost, so the choice is a decision, not a reflex.
Evidence is volatile. RFC 3227 lists the order of volatility: CPU registers and cache, then routing and ARP tables, the process table and memory, then temporary file systems, then disk, then remote logs, then archives. Collect the most volatile first.
That is why EDR isolation is usually better than pulling the power: the host keeps running, memory and processes stay available, and you can still collect from it. Rebooting or reimaging first throws away what was in memory.
Record what you did and when. A containment action without a time stamp makes the timeline harder for everyone after you.
Your turn: put steps in order. Order these sources from most to least volatile (RFC 3227).
Do the interactive check Free, in the browser.
Sources
- RFC 3227: Guidelines for Evidence Collection and Archiving IETF
- SP 800-61 Rev. 3: Incident Response Recommendations (CSF 2.0 Community Profile), April 2025 NIST