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 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 found | Kind of failure | Corrective action |
|---|---|---|
| No control was ever deployed | Missing control | Implement it |
| The control ran and missed the activity | Detection miss | Tune it or change the method |
| A correct alert sat unread in the queue | Output not acted on | Fix 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 →