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 1 of 4
Writing a defensible incident record
1 min read
An incident record will be read later by managers, auditors and sometimes lawyers, so a reader must be able to tell what was measured from what was inferred. A byte count in a proxy log or a process launch in endpoint telemetry is an observation.
A statement that customer data was stolen is an assessment, and it belongs in the record as one, with a confidence level and a note of what evidence would confirm or overturn it.
Example: a draft says the attacker did not move beyond three servers. Endpoint telemetry covers the servers but only about 60 percent of laptops.
The defensible version states the confirmed three servers, says the absence of lateral movement applies only to systems that send telemetry, and names the unmonitored laptop group. That turns an overclaim into a bounded finding and documents a real visibility gap.
- Write each containment action as its own entry: who performed it, the exact time it took effect, and the system it was applied to.
- Keep interim notes in the case record, even ones later proven wrong; they are part of the timeline.
- When counsel says an outside notification duty applies, capture facts, times, actors and decisions as they happen and preserve them under legal review.
Check yourself
1. An analyst is writing the incident record. The evidence is a proxy log entry showing 1.8 GB sent from a workstation to an unfamiliar external host over TLS, and an endpoint log showing an archive utility ran on that workstation minutes earlier. No inventory of the archive's contents exists. How should the record state this?
2. The team reports that the intrusion was limited to two servers and that there is no evidence of lateral movement. Authentication logging is centralized for the server estate, but roughly a third of workstations forward no endpoint telemetry. How should the scope section be written?
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 →