Vulnerability Assessment Basics

What is it?

Vulnerability assessment is the process of matching the detailed service information from enumeration (exact software and version) against databases of known weaknesses — without necessarily proving exploitability yet. This is often assisted by automated vulnerability scanners, but the core idea is simple: compare what’s running against what’s known to be weak.

Why should I learn it?

This phase separates “I think this might be vulnerable” from “here’s evidence this specific version has a known, documented weakness” — a critical distinction for professional, defensible reporting.

How it works

Enumeration provides exact service and version detail → that detail is checked against known vulnerability databases → each match is rated by severity and likely impact → the tester prioritises findings by real risk, not just by how many were found → only findings that fall within the authorized scope move on to the exploitation phase.

Real-world example

Enumeration reveals a web server is running an outdated CMS plugin version. A vulnerability assessment matches that exact version against a known, publicly documented vulnerability — giving the tester (and later, the report) concrete evidence instead of a guess.

Troubleshooting mindset

A vulnerability match doesn’t automatically mean real risk — always check whether the vulnerable service is actually reachable from a meaningful attack path before rating it as high priority.

Common mistake

Do not memorise the definition without connecting it to real engagement practice. Ask: what does this concept mean for what I’m allowed to actually do, and how would I prove I stayed within scope?

Quick recap

• Understand the job of the phase or technique.
• Know where it sits in the overall testing methodology.
• Always tie it back to authorization and scope.
• Connect the topic to the next phase of the engagement.

Interview connection

Explain the concept in simple words first, then connect it to authorization and real engagement practice. That is stronger than repeating a tool name.

References & Further Reading

• AddySec original content — written for the Ethical Hacking track to build practical, interview-ready understanding.