Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 8 · Lesson 5 of 5
Containment, eradication, recovery and post-incident activity
1 min read
These phases have a strict logic, and most wrong answers break it. Containment limits the intruder's reach, eradication removes the threat and the condition that let it in, and recovery returns systems to service and proves they can be trusted.
- Containment works only against the full scope, so every affected host, account and cloud resource is found first.
- Immediate containment, such as disabling accounts or blocking a controller address, cuts reach while the threat is still present; long-term containment uses compensating controls when a fix is not yet possible.
- Shutting down a business service is a trade-off the incident lead and business owner decide against the declared severity.
- Recovery restores from a point before the compromise, validates function and adds heightened monitoring.
Example: a team restores six web servers from backup on Monday but plans to patch the exploited flaw on Thursday. The backups contain the same vulnerable software, so the servers go back online exposed and are likely to be compromised again.
Eradication, including closing the entry path, must come first. Post-incident activity then feeds lessons back into preparation as updated playbooks, new detections and corrective actions with owners and dates, without assigning personal blame.
Check yourself
1. While the investigation continues, the team disables the intruder's two accounts, blocks the controller addresses at the egress firewall, and moves an affected cloud instance into a restricted network group. Into which phase does this work fall?
2. The intruder's persistence mechanisms have been removed, the exploited service has been patched, and the affected credentials have been rotated. The team now wants the systems back in production. What must the recovery phase establish?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management (2025), NIST CSRC: Incident response project (CSF 2.0 life cycle model)
CompTIA CySA+ cheat sheet: every key fact on one page →