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 →
← Vulnerability Reporting & Communication

Chapter 10 · Lesson 3 of 5

Metrics that show direction: trends, aging, recurrence and coverage

1 min read

A single count of open findings on the last day of the month is a snapshot. It cannot show whether exposure is shrinking, because the same total can hide a team that closes nothing or one that closes as fast as new findings arrive.

Leadership needs findings opened against findings closed each month, plus how long the open ones have been open.

Example: a backlog of 400 receives 120 new findings in a month and the teams close 100. The closure number sounds healthy, yet the backlog grew by 120 − 100 = 20 to 420.

  • Aging by severity: if low-severity items close within a week while most high-severity items sit open for months, effort is flowing to the easiest fixes.
  • Recurrence: a configuration fixed on production servers that reappears on servers built afterwards points to the build image or change process, so the report should recommend fixing that origin.
  • Coverage: a remediation rate only describes what was scanned, so a large coverage gap belongs at the top of the report, not in a footnote.

Example: a headline of 95% remediated on time sits on a scan that reached 70% of a 1,200-asset inventory. The other 30%, or 360 assets, produced no findings at all to remediate.

Check yourself

1. A report breaks open findings down by age. Most high-severity findings have been open more than 180 days, while low-severity findings close within a week, and the total number of open findings has not changed. What does this profile MOST likely indicate?

2. A monthly vulnerability report has always shown one number: open findings on the last day of the month. Leadership says it cannot tell whether exposure is being reduced. Which addition does the MOST to answer that question?

Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning

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