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 Reporting & Metrics

Chapter 11 · Lesson 3 of 4

After-action reports, root cause and lessons learned

1 min read

The exam expects you to tell three products apart. Root cause analysis explains why the incident was possible at all, such as an unpatched internet-facing service. A lesson learned is a change to how the team works, such as a new escalation threshold after the on-call path failed.

The after-action report is the formal written record that carries the timeline, scope, actions taken, root cause and recommendations. Patching or reimaging a host is remediation, not a report.

Reports also carry an executive summary for readers who will see nothing else. It gives a plain account of what happened, the business impact known so far, the current status, the decision being requested, and which conclusions are still provisional.

Indicator lists, per-host timelines and framework mappings go in technical annexes, and an unconfirmed root cause is never presented as settled.

What the review foundKind of failureCorrective action
No control was ever deployedMissing controlImplement it
The control ran and missed the activityDetection missTune it or change the method
A correct alert sat unread in the queueOutput not acted onFix triage capacity and alert quality

Reviews change things only when people speak candidly and the output is work someone must finish. Focus on the process rather than individual blame, and turn each lesson into an item with one owner, a specific deliverable, a verification step and a date.

Example: replace the note 'improve monitoring' with 'the detection engineer adds and tests a rule for the observed technique, reviewed by a named peer, by the end of the next sprint.'

Check yourself

1. The review establishes three things: no application allowlisting existed on the affected servers; the mail gateway scanned the attachment and passed it; and the endpoint agent raised a correct alert that sat untriaged in a saturated queue for most of a day. How should these be classified, in order?

2. After an incident the team produces: (1) a finding that an unpatched internet-facing service allowed initial access; (2) a decision to change the escalation threshold because the on-call path failed; (3) a document recording the timeline, scope, actions taken and recommendations. Which mapping is correct?

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

CompTIA CySA+ cheat sheet: every key fact on one page →