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 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 →