The Incident Response Phases, In Order
Incident response questions are a big part of CompTIA CySA+ and Security+. You'll be asked which phase an action belongs to, what to do FIRST, and in what order to collect evidence. This guide walks through the lifecycle as CySA+ CS0-004 lists it, plus the evidence-handling rules that come up again and again.
The incident response process (CySA+ CS0-004, objective 3.2)
| Phase | What happens | Example actions |
|---|---|---|
| Preparation | Get ready before anything happens | IR plan, playbooks, roles, logging, tabletop exercises |
| Detection | Something is noticed | SIEM alert, user report, threat hunt finding |
| Analysis | Is it real, and how big is it? | Triage, enrichment, scoping, severity, timeline |
| Containment | Stop the spread | Isolate hosts, block C2, disable accounts |
| Eradication | Remove the attacker and the cause | Delete malware and persistence, patch, reset credentials |
| Recovery | Return to normal safely | Restore from clean backups, verify, monitor |
| Post-incident | Learn and improve | Lessons learned, after-action report, root cause analysis |
What to do FIRST
- Ransomware or anything actively spreading: contain first by isolating the affected hosts. Restoring before containment just gets the restored files encrypted again.
- Isolate, don't power off, when you can. Network isolation stops the threat while keeping memory evidence intact.
- Phished credentials: reset the password and revoke active sessions and tokens, then look for new MFA devices and mailbox rules.
- Never wipe or rebuild before preserving evidence, and never close a ticket before verifying the fix.
Order of volatility
Collect the most short-lived evidence first: CPU registers and cache, then memory (running processes, network connections, encryption keys), then temporary and swap files, then disk, then remote logs and monitoring data, and finally backups and archives.
Chain of custody, integrity and legal hold
- Chain of custody records who collected, handled and stored each piece of evidence and when, so it stays admissible.
- Hash a disk image (for example with SHA-256) when you create it. Matching hashes later prove nothing changed.
- Use a write blocker when imaging a drive so the original isn't modified.
- A legal hold suspends normal deletion so data relevant to litigation or an investigation is preserved.
Try 3 free sample questions
Questions are visible below. Pick an answer to reveal the correct one and the explanation.
Q1.An analyst confirms malware on three hosts. Which phase comes next?
Q2.When collecting evidence from a live system, what should be captured first?
Q3.Restoring a server from a backup taken before the intrusion happens in which phase?
Test yourself
Try 10 exam-style questions on incident response, with an explanation for every answer. Free, no signup.
Practice this free on CertiTom
Create a free account to drill unlimited practice questions on this topic across A+, Network+, Security+, and CySA+. Pro members also get the hands-on Incident Response Phases performance-based lab (CySA+) — drag-and-drop practice that mirrors the real exam.
Frequently asked questions
What are the phases of incident response on CySA+?
CySA+ CS0-004 lists preparation, detection, analysis, containment, eradication, recovery and post-incident. Security+ and NIST group detection and analysis together, but the order is the same.
What is the difference between containment and eradication?
Containment stops the incident from spreading, for example by isolating a host. Eradication removes the attacker completely, including malware, backdoor accounts and persistence, and fixes the root cause.
Why is chain of custody important?
It proves who handled evidence and that it wasn't altered, which is required for evidence to hold up in legal or disciplinary proceedings.