CS0-003 Vulnerability Management Practice Question
A security analyst is prioritizing vulnerabilities for a critical internet-facing application server. The analyst has CVSS scores, EPSS scores, and access to the CISA KEV catalog. Which TWO factors should the analyst consider as the most important for determining remediation priority? (Select TWO)
⚠ Common exam trap
CS0-004 often tests the misconception that CVSS base score alone is sufficient for prioritization, ignoring the need to incorporate asset criticality and active exploitation evidence like KEV.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Asset criticality and business context
Remediation priority must reflect the value and exposure of the affected system; a critical internet-facing application server supporting key business functions warrants higher priority than a low-value internal host, regardless of raw severity scores. Option E (CISA Known Exploited Vulnerabilities (KEV) catalog) is correct because KEV lists vulnerabilities known to be actively exploited in the wild, which is the strongest evidence of immediate real-world risk and should drive urgent remediation. CVSS base score (B) measures intrinsic technical severity but not exploit likelihood or business impact, so it is only one input and not the top priority factor. EPSS score (D) estimates the probability of exploitation but does not capture asset importance or confirmed exploitation like KEV does. The number of plugins detecting the vulnerability (C) is a scanner artifact and has no bearing on actual risk or remediation priority.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Asset criticality and business context
Why this is correct
Asset criticality and business context are central to vulnerability prioritization because they determine the potential impact on operations, data confidentiality, and compliance. A critical internet-facing server, for example, represents a higher risk to the organization if compromised, even when the vulnerability's severity is moderate. Contextual factors such as exposure, sensitive data, and required availability turn a generic technical finding into a prioritized business risk.
- ✗
CVSS base score
Why it's wrong here
The CVSS base score provides a standardized, vendor-agnostic measure of inherent severity using exploitability and impact parameters; however, it is a static rating that ignores whether a vulnerability is actively exploited in the wild. It also lacks asset-specific context, so a critical CVSS score on an isolated, non-critical system could lead to wasted effort. Thus, using CVSS alone would misalign remediation with actual business risk.
- ✗
Number of plugins detecting the vulnerability
Why it's wrong here
The number of plugins detecting the same vulnerability is a byproduct of scanner configuration and signature duplication, not a direct measure of exploitability or impact. Multiple detection rules can reference the same CVE, inflating the count without adding risk information. This metric can help identify detection gaps but should not drive urgency or prioritization decisions.
- ✗
EPSS score
Why it's wrong here
EPSS estimates the likelihood that a vulnerability will be exploited in the future using heuristic and machine-learned models, but it does not confirm current, real-world exploitation. While a high EPSS score can inform relative prioritization, a KEV listing is definitive: it signals that attackers are already exploiting the flaw today, making EPSS a useful supplement rather than a primary trigger for immediate action.
- ✓
CISA Known Exploited Vulnerabilities (KEV) catalog
Why this is correct
The CISA Known Exploited Vulnerabilities catalog is a curated, authoritative list of vulnerabilities with confirmed evidence of active exploitation in the wild, removing the guesswork from vulnerability prioritization. This ground-truth intelligence, coupled with asset criticality, directly supports urgent remediation because the attack is ongoing and organizations must act immediately. It is a leading element in federal vulnerability management directives and modern risk-based decision-making.
Go deeper
Related to this question
Learn chapter
Vulnerability Management Workflow
Key term
Likelihood
Likelihood is the estimated probability that a specific threat will exploit a vulnerability, causing harm to an IT asset or system.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
About these practice questions
Courseiva writes every CS0-004 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CS0-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CS0-004 exam.