Definition
Vulnerability management is the ongoing process of finding, prioritising, fixing and tracking security weaknesses across your systems and applications. Unlike a one-off scan or test, it is a continuous cycle that aims to shrink the window in which attackers can use a known flaw.
What vulnerability management is
Every organisation has vulnerabilities: missing patches, outdated software, insecure settings and flaws in its own applications. New ones appear every day as vendors publish advisories and systems change. Vulnerability management is the process that keeps up with them. It is not a single tool or a single scan, but a repeating cycle of finding weaknesses, deciding which matter most, fixing them and checking progress.
Guidance such as NIST SP 800-40 treats patching and vulnerability handling as routine maintenance that should be planned, measured and repeated, rather than a reaction to the latest headline.
The vulnerability management lifecycle
- Discover assets. You cannot protect what you do not know about. Build and keep an inventory of systems, applications and internet-facing services, including the ones that were set up and forgotten.
- Identify vulnerabilities. Run a vulnerability assessment with scanners and review configurations to find known weaknesses.
- Prioritise. Rank findings by how severe they are, how likely they are to be attacked and how exposed the affected system is.
- Remediate. Patch, change the configuration or add a compensating control. See remediation for the options.
- Verify and report. Confirm that fixes were applied and track measures such as time to fix and the number of open critical issues.
Then the cycle starts again, because your systems and the threats keep changing.
How to prioritise vulnerabilities
Most teams find far more vulnerabilities than they can fix, so prioritisation is where vulnerability management succeeds or fails. Common inputs are:
- Severity: the CVSS score describes how bad a vulnerability would be if exploited.
- Likelihood: the EPSS score estimates how likely it is to be exploited in the next 30 days.
- Known exploitation: the CISA Known Exploited Vulnerabilities catalog lists flaws already used in real attacks.
- Exposure and business context: a flaw on an internet-facing system that holds customer data matters more than the same flaw on an isolated test machine.
- Exploitability in your environment: whether the flaw can really be used against your systems, alone or combined with others. This is the question scores cannot answer on their own.
Vulnerability management vs vulnerability assessment
A vulnerability assessment is one step: a point-in-time check that produces a list of weaknesses. Vulnerability management is the whole programme around it, including asset inventory, prioritisation, fixing, tracking and reporting. An assessment tells you what is wrong today; vulnerability management makes sure the list keeps getting shorter.
Common pitfalls
- Treating the scanner report as the plan. Long lists ranked only by CVSS lead teams to fix many low-risk items while a few dangerous ones wait.
- Incomplete asset inventory. Forgotten servers and shadow IT never get scanned, so they never get patched.
- Trusting version numbers. Patched packages can keep an old version number, and unrestarted services can keep running old code, so reports can be wrong in both directions.
- Ignoring chained risk. Several medium findings can combine into an attack path that is worse than any single critical one.
- No ownership. Findings without a named owner and a deadline tend to stay open.
Where penetration testing fits
Scanners keep the list complete; penetration testing shows which items on it an attacker could actually use. Adding regular, continuous penetration testing to a vulnerability management programme gives teams evidence for prioritisation instead of guesses, and catches weaknesses scanners miss, such as logic flaws and chained attacks. Broader approaches such as continuous threat exposure management build on the same idea.
How Plainsea fits in
Plainsea adds proof to vulnerability management. Its AI agents attempt real attacks within the scope you set and report only findings confirmed as exploitable, with the evidence and attack path behind each one, so your team knows which weaknesses to fix first. Learn more in AI penetration testing.