Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 38 ยท Scanning and Enumeration

Vulnerability Scanning and Triage

Learn how vulnerability scanners work, how to read CVE and CVSS data, separate false positives from real findings, and prioritize what to validate first.

By now you know which hosts are live, which ports are open and which services run. A vulnerability scanner automates the next step: it compares what it finds against a large database of known weaknesses and configuration problems and produces a long list. That list is a starting point, not an answer. Scanners overreport, underreport and cannot judge business context. The skill of a tester is triage: deciding which items are real, which matter and in what order to validate them.

Run scanners only against in-scope systems, at agreed rates, and prefer authenticated scans when the client gives you an account, because they see patch levels directly.

How scanners work

Scanners use several techniques:

  • Version matching: identify a product version and look it up in a vulnerability database. Fast and safe, but prone to false positives (backported fixes) and false negatives (hidden versions).
  • Active checks: send a harmless probe that triggers a distinctive response if the flaw is present. More accurate than version matching alone.
  • Configuration checks: compare settings against a baseline, such as weak TLS or a missing header.
  • Authenticated scanning: log in with a read-only account and read installed packages, patch levels and settings directly. Far more accurate and less noisy on the network.
  • Web application scanning: crawls a site and tests parameters with typical payloads. Good for coverage, weak on logic flaws.

Common tools include Nessus, OpenVAS (Greenbone), Qualys and Nuclei for infrastructure, and ZAP or Burp's scanner for web applications. This course shows their output as read-only examples.

Scan, then think

Scanner Wide, fast, noisy.
Tester Validates and ranks.
Finding Confirmed, with impact.

Never paste raw scanner output into a report.

1 / 2

CVE, CWE and CVSS

Three identifiers appear constantly.

  • CVE (Common Vulnerabilities and Exposures): an ID for one specific known vulnerability, such as CVE-2021-44228. It tells you which flaw.
  • CWE: a category of weakness (for example, SQL injection). It tells you what kind.
  • CVSS (Common Vulnerability Scoring System): a score from 0.0 to 10.0 describing technical severity.

CVSS 3.x severity bands: None 0.0, Low 0.1 to 3.9, Medium 4.0 to 6.9, High 7.0 to 8.9, Critical 9.0 to 10.0. The base score comes from metrics such as attack vector (network or local), attack complexity, privileges required, user interaction, scope, and the impact on confidentiality, integrity and availability. A vector string such as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H encodes them and gives 9.8.

Important limits: a base score ignores your environment. A critical flaw in a service that is not reachable is less urgent than a medium flaw on the public login page. Other inputs help: whether exploit code is public, whether the flaw is known to be exploited in the wild (see the CISA Known Exploited Vulnerabilities list, and the EPSS probability score), and how valuable the asset is.

Read-only: example scanner output

TEXT
Host: 192.0.2.10
Plugin ID  Severity  Name
---------  --------  ----
10863      Medium    SSL Certificate Cannot Be Trusted
51192      Medium    SSL Certificate Signed Using Weak Hashing Algorithm
42873      Medium    SSL Medium Strength Cipher Suites Supported
11219      Info      Nessus SYN scanner

This is example output in a typical format, not a real report. Notice the Info items: many are useful context rather than problems.

Triage workflow

  1. Deduplicate. The same flaw may appear on 200 hosts. Group by plugin or CVE.
  2. Remove noise. Informational items, duplicates and clearly inapplicable results.
  3. Check the evidence. What did the scanner actually observe? A version string alone is weaker than a response that proved the behavior.
  4. Assess exposure. Is the vulnerable service reachable? From where? Does it need authentication?
  5. Consider exploitability. Public exploit code? Known exploitation in the wild? Special conditions?
  6. Consider impact. What does the asset hold or control?
  7. Validate the most promising items safely, with explicit permission when the check could disturb the system.
  8. Record each decision, including why items were dismissed, so you can explain later.

False positives and false negatives

A false positive is a reported issue that is not real. A false negative is a real issue that was not reported. Both happen. False positives waste the client's time and damage trust if they reach the report. False negatives are worse because they give false comfort. Reduce both with authenticated scans, manual validation and a second tool or technique for important systems.

Stand-in: compute CVSS 3.1 base scores

The first example calculates a CVSS 3.1 base score from its metrics. It follows the published formula, so you can see how severity arises. It supports the scope-unchanged case, which covers most examples.

Python Calculate a CVSS 3.1 base score (scope unchanged)

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 first case gives 9.8, the well-known score for a network-reachable, unauthenticated flaw with full impact. The second example ranks scanner results by combining the base score with context, which models the triage step. The weights are a teaching model, not a standard.

Python Triage: rank findings with context

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.

Reporting scan results responsibly

  • Never hand over the raw export as the deliverable. Add your validation notes.
  • Group by root cause (one outdated component) rather than by host count.
  • Present remediation first for the issues that matter, not alphabetically.
  • State scan limits: credentials used, time, rate, areas not scanned.

The chapter ahead, exploitation concepts, picks up the validated items and shows how to demonstrate impact safely. For how scores and ratings reach the client, see the reporting chapter later in this course.

Defender takeaways

  • Scan regularly, with credentials, and track the results over time.
  • Patch by priority: exposed and exploited first.
  • Maintain an asset inventory, since you cannot scan what you do not know about.
  • Feed results into a ticketing system with owners and deadlines.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a CVE identifier represent?

    CVE names a particular vulnerability. CWE names the weakness category and CVSS gives a severity score.
  2. 2. Why prefer authenticated scans when possible?

    Authenticated checks avoid guessing from banners.
  3. 3. A CVSS 9.8 flaw exists on a host that cannot be reached from any untrusted network. How should you view it?

    Scores describe technical severity. Exposure, exploit availability and asset value shape priority.
  4. 4. What is a false positive?

    False positives waste effort. Validate before reporting.

Summary

  • Scanners match versions, run active checks and compare configurations; authenticated scans are the most accurate.
  • CVE names a specific flaw, CWE a weakness class, CVSS a 0 to 10 severity score with Low, Medium, High and Critical bands.
  • Triage: deduplicate, remove noise, check evidence, weigh exposure, exploitability and impact, then validate and record decisions.
  • Expect false positives and false negatives; never deliver raw scanner output.
  • Prioritize by context, not by base score alone.

Next: Continue with exploitation concepts in the Penetration Testing track.