Vulnerability Management Lifecycle
Vulnerability Management Lifecycle
A Vulnerability Management Lifecycle (VML) is the process of finding, assessing, fixing, and
monitoring security weaknesses (vulnerabilities) in a system. This helps organizations stay secure
from cyber threats.
🔹 Types of Vulnerabilities:
✅ Software Bugs – Errors in code (e.g., outdated software).
✅ Weak Passwords – Easy-to-guess passwords like "123456".
✅ Misconfigurations – Incorrect security settings in systems.
✅ Unpatched Systems – Systems missing security updates.
✅ Example: A website using an outdated version of WordPress may have security flaws that
hackers can exploit.
🔹 Tools Used:
✅ Nessus, Qualys, OpenVAS – Automated scanning tools.
✅ Manual Testing – Security experts manually check for vulnerabilities.
✅ Penetration Testing – Ethical hackers simulate real attacks.
✅ Example: A company runs Nessus to scan its servers and finds 10 security vulnerabilities.
🔹 How to Prioritize?
✅ CVSS Score – Rates vulnerabilities from 0 (low) to 10 (critical).
✅ Exploitability – Can hackers easily use this vulnerability?
✅ Impact – Will this vulnerability cause financial or data loss?
✅ Compliance Issues – Does this violate security regulations (GDPR, PCI DSS, etc.)?
✅ Example: A vulnerability with a CVSS score of 9.8 (Critical) gets fixed first, while a CVSS 3.2
(Low) can be scheduled for later.
✅ Example: If a company finds a vulnerability in its web server, they install a security patch to fix
it.
🔹 Steps in Verification:
✅ Test the fix using vulnerability scanners.
✅ Perform penetration testing to see if hackers can still exploit it.
✅ Validate system logs to ensure no suspicious activity remains.
✅ Example: A company applies a security patch and then re-scans to confirm the vulnerability is
gone.
✅ Example: A company schedules Nessus scans every week to catch new vulnerabilities early.
✅ Example: After a security breach, a company updates its security policies to avoid similar
attacks in the future.
🔹 Summary Table 🔹
1.
Scan for security weaknesses. A company uses Nessus to find vulnerabilities.
Identification
Decide which vulnerabilities to A critical bug (CVSS 9.8) gets fixed before a
2. Prioritization
fix first. low-risk bug (CVSS 2.5).
3. Remediation Fix the vulnerabilities found. Install a security patch to fix a software bug.
4. Verification Test if the fix worked. Re-scan the system after applying a patch.
A vulnerability scan is an automated process that checks for security flaws in a network, system,
or application. The scan output provides a report listing detected vulnerabilities.
🔹 What’s in the Scan Report?
✅ Vulnerability Name – The name of the issue (e.g., “SQL Injection Vulnerability”).
✅ Severity Level – Categorized as Low, Medium, High, or Critical.
✅ CVSS Score – A numerical score (0-10) indicating risk level.
✅ Affected Systems – The servers, networks, or applications affected.
✅ Recommended Fixes – Suggested steps to fix the issue.
🔹 Example:
A company runs a Nessus scan and gets the following output:
✅ Vulnerability: OpenSSH Server Outdated
✅ Severity: High
✅ CVSS Score: 8.5
✅ Affected System: Web Server
✅ Fix: Update OpenSSH to the latest version
📌 CVE (Common Vulnerabilities and Exposures) is a public database that keeps track of known
security vulnerabilities. Each vulnerability gets a unique CVE ID for easy reference.
🔹 CVE Format:
CVE-[Year]-[ID Number]
✅ Example: CVE-2023-12345 (A vulnerability discovered in 2023).
🔹 Example:
A security vulnerability is discovered in a company’s database.
✅ Exploitability: Easy to exploit
✅ Impact: Data breach risk
✅ Attack Vector: Can be exploited remotely
✅ User Interaction: No user interaction needed
✅ Final CVSS Score: 9.2 (Critical)
📌 CWE (Common Weakness Enumeration) is a list of common coding mistakes and security
flaws that lead to vulnerabilities. Unlike CVE (which tracks specific vulnerabilities), CWE focuses
on patterns of weaknesses.
🔹 Summary Table 🔹
Concept What It Does? Example
CVE (Common
Public database of known CVE-2021-44228 (Log4Shell
Vulnerabilities and
vulnerabilities. bug).
Exposures)
CVSS (Common
Rates the severity of vulnerabilities A CVSS 9.2 bug is critical and
Vulnerability Scoring
(0-10). needs immediate fixing.
System)
Here are the key factors that make a strong Vulnerability Management Program (VMP):
📌 Scope means deciding what systems, applications, and networks need protection.
🔹 Internal vs. External Systems – Are you securing internal company systems or public-
facing websites?
🔹 Cloud vs. On-Premises – Are your systems in the cloud or on company-owned
servers?
🔹 Critical Assets First – Focus on protecting the most important systems (e.g., customer
databases, payment systems).
✅ Example: A bank may focus on protecting its online banking system first before
securing employee email accounts.
✅ Example: A hospital must follow HIPAA rules to protect patient records from
hackers.
🔹 Automated Scanning – Uses tools like Nessus, Qualys, or OpenVAS to scan systems
for known vulnerabilities.
🔹 Manual Testing – Security experts manually check for weaknesses missed by
scanners.
🔹 Penetration Testing – Ethical hackers simulate real attacks to find critical security
gaps.
🔹 Configuration Reviews – Ensuring systems are set up securely (e.g., no default
passwords).
✅ Example: A company uses Nessus to scan their network weekly for vulnerabilities.
📌 Not all vulnerabilities are equally dangerous. Triaging means deciding which ones to
fix first.
✅ Example: A company fixes a "critical" vulnerability (CVSS 9.8) that allows remote
hackers to take control of their servers before fixing a "low-risk" bug (CVSS 2.0) in an
employee app.
📌 A good security program evolves and gets better based on new threats.
✅ Example: A company updates its security policies every 6 months based on new
hacking techniques.
🔹 Summary Table 🔹