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 →
← Prioritization, Mitigation & Controls

Chapter 7 · Lesson 1 of 5

Severity scores versus risk, and how CVSS v4.0 is organized

1 min read

Scanners attach a severity rating to every finding, usually from the Common Vulnerability Scoring System maintained by FIRST. The current version is CVSS v4.0, published in November 2023. FIRST's own guidance says the Base score measures severity, not risk, and should not be used alone to assess risk.

That single idea answers many exam questions: a critical label tells you how bad exploitation would be, but nothing about whether anyone can reach the host.

  • Base: the intrinsic qualities of the vulnerability. A score built from these alone is labeled CVSS-B.
  • Threat: factors that change over time, such as exploit maturity. It replaces the Temporal group of v3.1, and adding it gives CVSS-BT.
  • Environmental: your own setting, such as the asset's importance and controls already in place. Adding it gives CVSS-BE, or CVSS-BTE with Threat as well.
  • Supplemental: extra descriptive information that does not change the score.

Many scanners and older study materials still show CVSS v3.1 scores, so expect both versions in practice. Whatever the version, a bare base number is a starting input, not a priority order.

Check yourself

1. Four findings are open. A: a high-rated flaw on an air-gapped test bench. B: a medium-rated authentication bypass on the internet-facing customer portal, with exploitation reported in the wild. C: a high-rated flaw on an internal print server whose vulnerable port is already blocked at the firewall. D: a critical-rated flaw on a spare server that is powered off pending decommission. Which is worked FIRST?

2. A weekly scan returns two findings. Finding A is rated critical and sits on a lab server in an isolated segment with no inbound or outbound routing, used only for driver testing. Finding B is rated medium, affects the public web application that fronts the customer payment flow, and working exploit code for it is circulating publicly. Which finding is worked FIRST, and on what basis?

Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, FIRST: CVSS v4.0 Specification Document, FIRST: CVSS v4.0 User Guide, CISA: Known Exploited Vulnerabilities Catalog

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