CS0-003 Vulnerability Management Practice Question
A security analyst is prioritizing vulnerabilities for remediation. Which THREE factors from the CISA Known Exploited Vulnerabilities (KEV) catalog should the analyst consider? (Select THREE.)
⚠ Common exam trap
The trap is confusing KEV catalog fields with external metrics like EPSS and CVSS — candidates pick those because they are familiar, but they are not part of the KEV catalog itself.
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
✓
Date the vulnerability was added to the catalog
The CISA KEV catalog entry for each vulnerability includes the date it was added to the catalog (option B), which indicates how long the vulnerability has been known to be actively exploited and helps prioritize remediation urgency. It also lists the vulnerability name or CVE ID (option D), which uniquely identifies the specific flaw so the analyst can map it to affected systems and track remediation. The affected vendor or product (option E) is likewise a core KEV field, telling the analyst which technologies are at risk and whether they are present in the environment. EPSS probability score (option A) is not part of the KEV catalog; it comes from the separate EPSS model maintained by FIRST. CVSS base score (option C) is also not a KEV catalog field; it is published by NVD or the vendor and is not included in KEV entries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
EPSS probability score
Why it's wrong here
EPSS (Exploit Prediction Scoring System) is a separate, data-driven threat scoring model that predicts the probability a vulnerability will be exploited in the wild, often using CVE attributes and real-world threat intelligence. However, the CISA KEV catalog only lists vulnerabilities that have been confirmed as actively exploited and does not include EPSS probability scores as one of its fields. While EPSS can be a supplementary source for prioritization, it is not the correct data element from the KEV catalog.
- ✓
Date the vulnerability was added to the catalog
Why this is correct
The KEV catalog includes a 'Date Added' field that records when a vulnerability was first identified as known exploited, allowing security teams to prioritize based on how recent and relevant the active exploitation is. This date is crucial because newer entries often warrant immediate attention, as attackers may be actively leveraging them. In contrast to CVSS or EPSS scores, this date is a distinct component of the KEV record itself, making it the right field when consulting the catalog for prioritization.
- ✗
CVSS base score
Why it's wrong here
CVSS base scores are static severity metrics derived from intrinsic vulnerability characteristics such as attack vector and impact, but they do not indicate whether a vulnerability has been exploited in the wild. The KEV catalog does not store CVSS scores; it focuses on confirmed exploitation status, using its own fields like the addition date. Relying solely on CVSS would overlook the real-world exploitation context that KEV is designed to provide.
- ✓
Vulnerability name or CVE ID
Why this is correct
Each KEV entry is identified by its CVE ID, often accompanied by a short name or description of the vulnerability, which is essential for referencing and tracking the specific technical issue. While these identifiers are mandatory for cataloging and communication, they do not convey a sense of prioritization or urgency on their own. The prioritization decision comes from other fields, such as the date the entry was added, rather than from the identifier itself.
- ✓
Affected vendor or product
Why this is correct
The KEV catalog records the affected vendor and product for each vulnerability, enabling organizations to quickly check their asset inventory for exposure to a known exploited issue. This field is valuable for scoping remediation efforts and determining impact, but it does not indicate a vulnerability's relative priority compared with others in the catalog. Prioritization is better driven by date-related or other exploit context, not simply by the product name.
Go deeper
Related to this question
Learn chapter
Splunk SPL Queries for Security Analysts
Key term
CVSS
The Common Vulnerability Scoring System (CVSS) is a standardized framework used to rate the severity of security vulnerabilities on a scale from 0 to 10.
Key term
Remediation
Remediation is the process of fixing or eliminating vulnerabilities, misconfigurations, or security weaknesses in an IT environment.
About these practice questions
This CS0-004 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.