Vulnerability Management Life Cycle: The 5 Essential Stages

The vulnerability management life cycle is a continuous process for finding and fixing security weaknesses before attackers use them. A common five-stage version is: 1) discover assets and scan for vulnerabilities, 2) prioritise findings by risk, 3) remediate or mitigate, 4) verify that fixes worked, and 5) report and improve.

May 27, 2025 - 16:04
Updated: 
103.2k

Penetration Testing in Cybersecurity & Ethical Hacking · Lab / project

Cybersecurity Foundations, Cyber Threats, Scams & Online Safety, Ethical Hacking

Vulnerability Management Life Cycle: The 5 Essential Stages

Quick answer: The vulnerability management life cycle is a continuous process for finding and fixing security weaknesses before attackers use them. A common five-stage version is: 1) discover assets and scan for vulnerabilities, 2) prioritise findings by risk, 3) remediate or mitigate, 4) verify that fixes worked, and 5) report and improve. Prioritisation should combine severity (FIRST CVSS), exploitation likelihood (FIRST EPSS), confirmed exploitation (the CISA KEV catalog) and how important the asset is. NIST SP 800-40 Rev. 4 frames patching as routine preventive maintenance. The cycle repeats because new assets and new vulnerabilities appear every day.

Key takeaways

  • You cannot protect assets you do not know about.
  • CVSS measures severity, not the chance of attack.
  • KEV and EPSS help put exploited flaws first.
  • Verification closes the loop; a ticket is not a fix.
  • Metrics show whether the programme actually reduces risk.

Table of Contents

What Is the Vulnerability Management Life Cycle?

It is the repeating loop that keeps exposure low. Vendors describe it with five to seven stages, but the work is the same.

StageMain activityOutput
1. DiscoverInventory assets, scanAsset list and findings
2. PrioritiseRank by riskOrdered remediation queue
3. RemediatePatch, configure, mitigateChanges applied
4. VerifyRescan and testConfirmed closure
5. Report and improveMetrics and reviewsUpdated SLAs and process

For a tool-focused view, see our guide to Qualys vulnerability management. This post covers the process regardless of tool.

How Do You Discover Assets and Vulnerabilities?

  • Build an inventory from CMDB, cloud APIs, EDR and network discovery.
  • Run authenticated scans where possible; they find more than unauthenticated ones.
  • Include cloud, containers, web apps and internet-facing assets.
  • Track vendor and CERT-In advisories for systems scanners miss.

Scanning systems you do not own needs written authorisation; unauthorised access is an offence under Sections 43 and 66 of India's IT Act 2000.

How Should Vulnerabilities Be Prioritised?

SignalWhat it tells youSource
CVSS scoreTechnical severityFIRST CVSS v4.0, NVD
EPSS probabilityEstimated chance of exploitation in the next 30 daysFIRST EPSS
KEV listingConfirmed exploitation in the wildCISA KEV
Decision treeAct, attend, track based on contextCISA SSVC
Asset criticalityBusiness impact if exploitedYour inventory

These signals answer different questions. A flaw with a CVSS score of 9.8 on an isolated test server may matter less than a 7.5 on an internet-facing VPN that appears in KEV. EPSS adds a data-driven estimate for the many vulnerabilities that are not yet in KEV. SSVC turns the inputs into a decision, such as act now or track, which is easier for IT teams to follow than raw scores. Write the rules down as service level targets, for example days to fix by category, so owners know what is expected.

A practical rule: internet-facing assets with KEV-listed flaws go first. US federal agencies must fix KEV entries by set deadlines under BOD 22-01, a useful benchmark for others. Prioritisation feeds your wider risk management process.

What Are the Remediation Options?

  • Remediate: apply the patch or upgrade.
  • Mitigate: apply workarounds, disable features, segment or add WAF rules until a patch is possible.
  • Accept: document risk acceptance with an owner and expiry date.

NIST SP 800-40 Rev. 4 recommends defined maintenance groups and plans, including emergency patching for urgent cases.

How Do You Verify Fixes?

Rescan the asset, confirm the version, and check that services restarted. On Windows, an administrator can list installed updates to confirm a patch:

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

On Debian or Ubuntu, list packages with pending updates:

apt list --upgradable

Close the ticket only after verification passes.

What Should You Report and Measure?

  • Mean time to remediate, by severity and KEV status.
  • Percentage of assets scanned in the last cycle.
  • Open KEV-listed vulnerabilities on internet-facing assets.
  • Overdue items against SLA, and active risk acceptances.

What Are Common Mistakes?

  • Fixing by CVSS score alone.
  • Scanning without a current asset inventory.
  • Closing tickets without rescanning.
  • Letting risk acceptances never expire.

WebAsha offers vulnerability assessment and VAPT training.

References

Frequently Asked Questions

Discover, prioritise, remediate, verify, and report and improve. The cycle then repeats as new assets and vulnerabilities appear.

CVSS rates the technical severity of a vulnerability, while EPSS estimates the probability that it will be exploited soon.

A public list maintained by CISA of vulnerabilities confirmed to be exploited in the wild, useful for deciding what to fix first.

A scan is one activity. Vulnerability management is the whole continuous process, including prioritisation, remediation, verification and reporting.

Apply mitigations such as disabling the affected feature, segmenting the system or adding filtering rules, and track the vendor fix.

At least regularly, such as weekly or monthly, and continuously for internet-facing assets, plus after major changes or urgent advisories.

Stakeholder-Specific Vulnerability Categorization, a decision tree approach promoted by CISA that sorts vulnerabilities into actions based on context.

Yes. Only scan systems you own or have written authorisation to test, as unauthorised access breaks India’s IT Act 2000.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Wow Wow 0
Sad Sad 0
Angry Angry 0
Vaishnavi

Vaishnavi is a skilled tech professional at the Ethical Hacking Training Institute in Pune, responsible for managing and optimizing the technical infrastructure that supports advanced cybersecurity education. With deep expertise in network security, backend operations, and system performance, she ensures that practical labs, online modules, and assessments run smoothly and securely. Her behind-the-scenes contributions play a vital role in delivering a seamless and secure learning experience for aspiring ethical hackers.