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 9 · Lesson 4 of 5
Containment techniques that keep the evidence
1 min read
The preferred containment for a host with an active intruder is network isolation: disable the interface or move it to a quarantine segment and leave it running. That stops lateral movement and data theft while memory and running processes survive for capture.
Powering off destroys that state, a single perimeter block leaves the host free to move internally, and changing a local password does not end a session already open.
Identity containment follows the same idea. Session and refresh tokens outlive a password change, so a cloud account takeover is contained by revoking sessions, removing any added sign-in methods, resetting the credential and re-enrolling the device.
Example: an attacker has created a hidden forwarding rule in a mailbox. Warning the user by email to that mailbox alerts the attacker, so revoke the sessions, remove the rule and reach the user by phone or another channel the attacker cannot read.
- A system that cannot stop, such as a production controller, gets compensating containment: allow only required traffic, block the command channel, and watch it closely.
- Short-term containment stops exploitation now, for example by filtering the exploit path at a reverse proxy; long-term containment keeps that filter and closer monitoring in place until the patch, which is eradication work under change control.
- Taking a revenue service offline is escalated to the incident commander and business owner, while the analyst applies the containment within their authority.
- Automated playbooks can enrich and open tickets freely, but isolating a critical host needs analyst approval, and AI-generated findings are checked against source telemetry before action.
Check yourself
1. After a cloud account compromise the team reset the user's password six hours ago, yet the attacker is still sending mail and reading files from the same account. Which explanation and fix is correct?
2. A post-incident review establishes this chain: a contractor clicked a phishing link and entered credentials; the attacker signed in to the remote access service, which required no second factor; an unpatched server then allowed lateral movement. Which finding is the root cause of the unauthorized access?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, IETF RFC 3227: Guidelines for Evidence Collection and Archiving
CompTIA CySA+ cheat sheet: every key fact on one page →