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 →
← Attack Frameworks & the Response Process

Chapter 8 · Lesson 3 of 5

The Cyber Kill Chain: stages and where to break them

1 min read

Lockheed Martin's model lists seven stages in order: reconnaissance, weaponization, delivery, exploitation, installation, command and control, and actions on objectives. Its main value is control placement. Stopping a campaign at one stage removes every stage after it, so the exam often asks which single control acts earliest.

  • Weaponization happens on the adversary's own systems, so the defender has no internal telemetry for it.
  • Delivery means the payload has arrived but nothing has run, such as an attachment held in quarantine.
  • Exploitation needs code to run against a weakness, and installation needs a foothold such as a service or scheduled task.
  • Command and control still leaves flow and DNS evidence when the channel is encrypted.

Example: a downloaded installer runs, adds a startup service, then calls out to a controller. One budget item is available. Blocking unsigned installers from running acts at exploitation, so installation and command and control never happen. An egress block acts later, at command and control.

The model is linear, and real intrusions often are not. An attacker who logs in with purchased credentials and moves with stolen cloud tokens may skip weaponization and installation and loop back to reconnaissance many times. Forcing that evidence into seven ordered stages invents a story the data does not support.

Check yourself

1. Macro-bearing attachments repeatedly execute on finance workstations; a scheduled task then relaunches the payload at every boot and the host begins contacting an external controller. Management will fund exactly one control. Which choice breaks the chain earliest, described correctly?

2. A review finds that an intruder entered with valid credentials bought from a broker, ran no malware, moved between cloud services using stolen tokens, and returned to reconnaissance repeatedly over six weeks. A manager wants the report laid out as the seven ordered stages. What is the BEST response?

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 →