Skip to content
Tutorials Center
My learning

Topics

Lesson 12 of 31 ยท Vulnerability Assessment

Vulnerability Assessment Workflow

Learn the vulnerability assessment workflow: scanners vs manual review, CVE and CVSS scoring, false positives, risk-based prioritization and the patching cycle.

A vulnerability assessment is a structured search for weaknesses, followed by a ranking of what to fix first. It differs from a penetration test: an assessment aims for breadth and a prioritized list, while a penetration test tries to chain weaknesses to show real impact (The Penetration Test Lifecycle). Most security programs run assessments continuously, because new vulnerabilities are published every day and software changes constantly.

In this lesson you learn the steps of the workflow, the vocabulary (CVE, CVSS, false positive), why a raw score is not a priority, and how to model scoring in Python. The tools on Kali (OpenVAS and others) are covered next in Vulnerability Scanners and Their Reports. Assess only what you are authorized to assess.

The workflow

A repeating cycle

Inventory Know your assets first.
Discover Scan and review for weaknesses.
Prioritize Rank by real risk.
Remediate Patch, configure or accept.

Then verify the fix and start the cycle again.

1 / 2

You cannot protect what you do not know exists, so the first step is an asset inventory: hosts, applications, owners and how important each is to the business. The same scan finding means something different on a public web server and on a lab printer.

Scanners and manual review

An automated scanner compares what it sees (open ports, versions, configuration) with a database of known issues. It is fast and consistent but has blind spots:

  • It finds known problems. Logic flaws, such as "any user can change any order", need a human.
  • It can be wrong in both directions: false positives (reported but not real) and false negatives (real but missed).
  • It sees only what it can reach. An authenticated scan with a read-only account sees installed packages and settings; an unauthenticated one sees only the network surface.

Good practice combines both: scanners for coverage, manual review for the findings that matter most and for anything the scanner cannot judge. Every high-severity finding should be validated before it goes to a system owner.

CVE and CVSS

A CVE (Common Vulnerabilities and Exposures) identifier names one specific flaw, for example CVE-2024-12345 (a made-up number). It lets everyone refer to the same issue. A CVE entry says what is affected and links to advisories.

CVSS (Common Vulnerability Scoring System) rates severity from 0.0 to 10.0. The base score uses properties of the flaw itself:

Metric Question Values
Attack Vector (AV) From where can it be exploited? Network, Adjacent, Local, Physical
Attack Complexity (AC) Do special conditions apply? Low, High
Privileges Required (PR) What access is needed first? None, Low, High
User Interaction (UI) Must a user do something? None, Required
Scope (S) Does it reach beyond the vulnerable component? Unchanged, Changed
Confidentiality / Integrity / Availability How bad is the impact? None, Low, High

The rating bands in CVSS v3.1 are: 0.0 none, 0.1-3.9 low, 4.0-6.9 medium, 7.0-8.9 high and 9.0-10.0 critical. A vector string such as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H records the inputs; that one scores 9.8. CVSS v4.0 exists with different metrics; the ideas here carry over.

A score is not a priority

The base score ignores your environment. Real prioritization also considers:

  • Exposure: is the system reachable from the internet?
  • Exploitation evidence: is the flaw being used in attacks? Public lists of actively exploited vulnerabilities and probability scores such as EPSS help here.
  • Asset value: what data or function is at stake?
  • Compensating controls: does a firewall rule or a disabled feature already block the path?

A "high" on an isolated test box can wait; a "medium" on an internet-facing login page with known exploitation may not.

The patching cycle

Typical remediation choices are patch, change configuration, replace the product, mitigate (for example a temporary firewall rule) or formally accept the risk with an owner and a review date. After the change, rescan to verify, and record the result. Measure time-to-fix by severity, which turns the program into something you can improve.

Stand-in: score and rank sample findings

The first TryIt implements the CVSS v3.1 base score formula, including the specified rounding, and checks it against the 9.8 example. The scoring code is real; the findings are invented.

Python A CVSS v3.1 base score calculator

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second TryIt ranks invented findings by a simple risk score that combines the base score with exposure, known exploitation and asset value. The weights are a teaching choice, not a standard. It also shows how a medium finding can outrank a high one.

Python Rank sample findings by risk

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

In a real program you would document the weights, review them with asset owners and keep the false-positive decision with a note on why.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What is a false positive in a vulnerability scan?

    False positives are reports of problems that do not exist, often because of back-ported patches or incorrect version matching. Missed real issues are false negatives.
  2. 2. Why is the CVSS base score alone not enough to prioritize work?

    Base scores measure the flaw itself. Context, such as internet exposure and known attacks, decides how urgent it is for you.
  3. 3. Which step comes right after remediation in the cycle?

    A rescan confirms the vulnerability is gone and creates a record that the work was done.
  4. 4. What does an authenticated scan add compared with an unauthenticated one?

    With a read-only account, the scanner can inspect local software and settings, which gives far more accurate results.
  5. 5. Which pair of terms is correct?

    A CVE number names one vulnerability, while CVSS gives a 0.0 to 10.0 severity rating.

Summary

  • An assessment finds and ranks weaknesses broadly; a penetration test shows impact by chaining them.
  • The cycle: inventory, discover, prioritize, remediate, verify, repeat.
  • Scanners give coverage but produce false positives and negatives; validate important findings manually.
  • CVE names a flaw; CVSS rates its base severity from 0.0 to 10.0.
  • Prioritize with exposure, active exploitation, asset value and existing controls, not the score alone.
  • The Python code is a stand-in: the scoring formula is real, the findings are invented.

Next: Vulnerability Scanners and Their Reports