Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/54 ▾
  1. 1.Architecture & Log Sources0/5
    1. What each log source can and cannot prove
    2. Time synchronization and log normalization
    3. Sensor placement, logging levels and retention
    4. Cloud, containers, serverless and virtual machines
    5. Identity, directory and federation logs
  2. 2.Indicators of Malicious Activity0/5
    1. Network indicators: DNS abuse, odd protocols and unusual volume
    2. Host indicators: process lineage, masquerading and built-in tools
    3. Persistence and anti-forensics on hosts
    4. Identity and application indicators
    5. Cloud indicators: stolen keys and disabled audit trails
  3. 3.Investigation Tools & Threat Hunting0/5
    1. Packet capture, flow data and network monitoring sensors
    2. Endpoint telemetry, file reputation and sandboxes
    3. SIEM correlation rules and email header analysis
    4. Judging and sharing threat intelligence
    5. Running a threat hunt from hypothesis to detection
  4. 4.Process Improvement, Automation & AI0/5
    1. Choosing what to automate in the SOC
    2. Standard processes: playbooks, runbooks and the case record
    3. Integrations, alert tuning and measuring improvement
    4. AI in security operations: good uses and main risks
    5. AI governance: accountability, audit trails and validation
  5. 5.Vulnerability Scanning Methods0/5
    1. Asset inventory, discovery scans and scan scope
    2. Credentialed, non-credentialed and agent-based scanning
    3. Scanner placement: internal, external and what sits in between
    4. Passive scanning, fragile devices and scan scheduling
    5. Web applications, containers, infrastructure-as-code and baselines
  6. 6.Analyzing Scan Output0/5
    1. Validating findings and spotting false positives
    2. False negatives, failed credentials and stale plugin feeds
    3. Present, reachable, mitigated or already compromised
    4. Reading the kind of finding: patch, configuration, end of life or shared source
    5. Consolidating and deduplicating findings
  7. 7.Prioritization, Mitigation & Controls0/5
    1. Severity scores versus risk, and how CVSS v4.0 is organized
    2. Risk-based prioritization: exploitation, exposure and business context
    3. Remediation paths, change control and verifying the fix
    4. Compensating controls, exceptions, acceptance and transfer
    5. Classifying controls by type and by function
  8. 8.Attack Frameworks & the Response Process0/5
    1. Three attack frameworks, three different questions
    2. Using MITRE ATT&CK: tactics, techniques and procedures
    3. The Cyber Kill Chain: stages and where to break them
    4. The incident response lifecycle, old and new framing
    5. Containment, eradication, recovery and post-incident activity
  9. 9.Incident Response Techniques0/5
    1. Triage and scoping an incident
    2. Collecting evidence: order of volatility and safe access
    3. Integrity, chain of custody and legal hold
    4. Containment techniques that keep the evidence
    5. Eradication, recovery and root cause
  10. 10.Vulnerability Reporting & Communication0/5
    1. From raw scan export to an actionable finding
    2. Matching the report to the audience
    3. Metrics that show direction: trends, aging, recurrence and coverage
    4. Risk acceptance, exceptions, action plans and escalation
    5. Credibility: honest severity, controlled disclosure and AI-drafted reports
  11. 11.Incident Reporting & Metrics0/4
    1. Writing a defensible incident record
    2. Communicating while the incident is live
    3. After-action reports, root cause and lessons learned
    4. Response metrics and how they mislead
Saved in this browser. Move it to another device →
← Incident Response Techniques

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 →