What is the difference between CVE and CVSS?
CVE is the identifier for a vulnerability. CVSS is the score that rates its severity.

Exam objectiveExplain various activities associated with vulnerability management
Objective 4.3 covers the vulnerability management cycle: identify weaknesses, analyze and prioritize them, remediate or accept them, validate the fix, and report.
Identification. Vulnerability scans list potential weaknesses, credentialed (logged in) or non-credentialed. Application security testing includes static analysis of code at rest, dynamic analysis of the running application, and package monitoring of third-party components. Threat feeds come from open-source intelligence (OSINT), proprietary or third-party sources, information-sharing organizations, and the dark web. Penetration testing is authorized exploitation by a person, responsible disclosure programs (including bug bounties) take reports from outside researchers, and system or process audits round out the methods.
Analysis. Findings are confirmed as real, false positives (reported but not real), or false negatives (real but missed). CVE is the identifier for a flaw and CVSS is its severity score. Prioritizing also weighs vulnerability classification, exposure factor, environmental variables, industry or organizational impact, and risk tolerance.
Response, validation, and reporting. Patching applies the vendor fix. Segmentation limits which systems can reach the vulnerable service, reducing exposure while the flaw stays in place, a compensating control gives comparable protection when the fix cannot be applied, insurance transfers part of the financial loss, and an exception or exemption records an approved decision to leave the flaw in place. Validation by rescanning, audit, and verification proves the fix worked, and reporting keeps decision makers informed.
Exam scenarios give scan results or a business constraint and ask what to do next, often which remediation fits when patching is impossible.
This page is the map. Knotch is where you drill it until it sticks.
A false positive is a finding that does not exist, so it wastes time. A false negative is a real flaw the tool missed, so it stays unfixed.
A scan is automated detection that lists potential weaknesses. A penetration test is authorized exploitation by a person.
CVE is the identifier for a vulnerability. CVSS is the severity score.
An agent-based assessment uses software installed on the host, which reports from inside wherever the host goes. Agentless assessment installs nothing on the target: network scanners need a path to it, while cloud tools may inspect disk snapshots or use provider APIs.
The full set of look-alike pairs for this objective is inside Knotch.
A newly disclosed flaw affects a logging library that dozens of the company's applications include. The team wants to be alerted whenever a library it ships gets a newly disclosed flaw.
Which practice would deliver those alerts?
Package monitoring, helped by a software bill of materials, tracks components and flags new disclosures.
Package monitoring keeps an inventory of third-party components and alerts when one has a new disclosed vulnerability.
Why not A: Dynamic analysis tests behavior at runtime and does not alert on new disclosures in components.
Why not C: Static analysis reviews the code the company wrote, not new disclosures in outside libraries.
Why not D: A yearly test cannot alert the team when a disclosure appears between tests.
CVE is the identifier for a vulnerability. CVSS is the score that rates its severity.
Options include segmentation to isolate the system, a compensating control such as a virtual patch on a web application firewall, insurance to transfer part of the financial loss, or a formal, approved exception.
Responsible disclosure is the channel for outside researchers to report flaws. A bug bounty adds payment.
