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

Study guide · Chapter 11 of 11

Incident Reporting & Metrics Study Guide — CompTIA CySA+

19 free practice questions

This part of the CySA+ CS0-004 exam is about what responders write down and say during and after an incident, and how a security operation measures itself. Questions ask how to word a finding, who should be told what and through which channel, what a post-incident review should produce, and which metric answers a given question. The right answer is usually the one that keeps the record honest and turns findings into tracked work.

Key takeaways

  • Keep what was observed separate from what was concluded, and give every conclusion a confidence level and the evidence still missing.
  • Record each response action with who did it, when it took effect and which system it touched.
  • During an incident, one coordinator sends scheduled updates on a channel the attacker cannot reach.
  • A post-incident review examines the process, not individuals, and every lesson leaves with an owner, a deliverable and a date.
  • Mean time to detect, respond, remediate and close each measure a different interval, and a timing metric is always read next to a quality measure.

Lessons in this chapter

4 short lessons · 4 min read

  1. 1Writing a defensible incident record1 min
  2. 2Communicating while the incident is live1 min
  3. 3After-action reports, root cause and lessons learned1 min
  4. 4Response metrics and how they mislead1 min
View all questions & answers →

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 →

Practice questions based on the CompTIA CySA+ exam objectives. This site is not affiliated with or endorsed by CompTIA, and these are not real exam questions. CompTIA refreshes this exam periodically, runs two versions side by side during a transition, and sets the exam length, passing standard and eligibility terms — confirm the current objectives and the live exam code with CompTIA before you register. The real exam also includes performance-based items that a multiple-choice bank cannot reproduce, so pair this with hands-on practice. Official CySA+ exam objectives →